Ionic1项目编译异常求助：提示不执行构建且更改未保存

Hey there, let's work through this annoying problem with your Ionic 1 project. That warning about not performing an Ionic build and your changes not saving can put a halt to development, so here are actionable steps to resolve both issues:

1. Use a Compatible Ionic CLI Version #

Ionic 1 is a legacy framework, and newer Ionic CLI versions (4+) don't support building it natively—this is exactly what that warning is flagging. Stick with Ionic CLI 3.x, the last version that fully supports Ionic 1:

• Install the global CLI:

  npm install -g ionic@3.20.0
  

• Install the same version locally in your project to avoid conflicts:

  npm install ionic@3.20.0 --save-dev
  

2. Skip Ionic Build & Use Cordova Directly #

Since the Ionic CLI won't handle the build for Ionic 1, use Cordova commands directly to compile for iOS:

cordova build ios

Make sure you're running this from your project's root directory. Also, verify your Cordova version is compatible—Cordova 8.x works best with Ionic 1. Install it if needed:

npm install -g cordova@8.1.2

3. Fix Unsaved Changes Not Reflecting #

This is often tied to caching or permission issues:

• Clear Ionic's cache: If you're using ionic serve, reload with no cache to force changes to show up:

  ionic serve --no-cache
  

• Check file permissions: Ensure you have read/write access to all project files. On macOS/Linux, you can run:

  sudo chown -R $USER:$USER ./your-project-directory
  

• Rebuild the www folder: The www directory stores compiled assets. Delete it (back it up first if needed) and recompile with ionic build or cordova build ios—this ensures your latest src changes get compiled into the output.

4. Validate Project Configuration #

Double-check your project files to rule out misconfiguration:

• Open config.xml and confirm there are no invalid entries that might break the build process.
• Check package.json to ensure you're using Ionic 1 dependencies (e.g., ionic-angular should be a version like 1.3.3, not 2+).

5. Refresh Dependencies #

Corrupted or conflicting node modules can cause odd behavior. Try a clean install:

1. Delete the node_modules folder
2. Delete package-lock.json (or yarn.lock if using Yarn)
3. Run npm install to reinstall all dependencies
4. Attempt the build again

内容的提问来源于stack exchange，提问作者jperez