Angular CLI 6.0 Workspace Configuration Migration Guide: Resolving 'angular.json' Not Found Error

Problem Background and Error Analysis

In Angular project development, when upgrading from Angular CLI 1.7.4 to 6.0.0-rc.3, many developers encounter build failures in continuous integration environments like Travis CI. The error message clearly states: "Local workspace file ('angular.json') could not be found." This error originates from a major change introduced in Angular CLI 6.0—the format and name of workspace configuration files have been modified.

Angular CLI 6.0 Configuration Format Changes

According to the Angular CLI official release notes, starting from version 6.0.0-rc.2, a new workspace configuration format was introduced. Older versions of Angular CLI (1.x) used .angular-cli.json as the configuration file, while the new version uses angular.json (also supporting .angular.json). This change aims to provide more flexible project structure and build configuration management.

Solution: Project Migration Steps

To resolve this issue, execute the project migration command to convert old configuration to the new format:

ng update @angular/cli --migrate-only --from=1.7.4

This command performs the following operations:

• Automatically detects the current project's Angular CLI version
• Migrates configuration from the specified source version (1.7.4)
• Removes the old .angular-cli.json file
• Generates a new angular.json workspace configuration file

Version Compatibility Handling

In some cases, if the project still uses Angular CLI 1.7.4, it may be necessary to first install the new version CLI:

npm install --save-dev @angular/cli@v6.0.0-rc.4

After installation, execute the migration command again to ensure proper configuration conversion. This process ensures project configuration compatibility with the new version CLI.

Special Considerations in Travis CI Environment

In continuous integration environments, build failures often occur because configuration migration was not properly executed. Ensure that build scripts include configuration migration steps, or complete the migration locally and commit the updated configuration files to the code repository. Referring to the case in the Q&A data, the project failed to execute migration after updating the CLI version, causing Travis CI builds to unable to find the new configuration file.

Additional Considerations

Besides configuration format changes, other potential causes for similar errors include:

• Not executing commands in the correct project directory (as mentioned in Answer 2)
• Configuration files being accidentally deleted or moved
• Permission issues preventing file access

Developers should ensure executing Angular CLI commands in the project root directory and verify the integrity of configuration files.

Technical Implementation Principles

From a code perspective, the error occurs in the WorkspaceLoader._getProjectWorkspaceFilePath method. This method is responsible for locating the workspace configuration file and throws an exception when angular.json cannot be found. The new CLI loads workspace and architect configurations through logic in architect-command.js, which relies on correct workspace file paths.

Best Practice Recommendations

To avoid similar issues, it is recommended when upgrading Angular CLI to:

• Carefully read version release notes to understand breaking changes
• Back up important configuration files before upgrading
• Test migration processes in local environments before deploying to CI/CD pipelines
• Maintain dependency version consistency, avoiding mixing Angular packages from different major versions