Angular 14

[jattasNI]

Pull Request

🤨 Rationale

This is required to upgrade applications to 14 from 13. With Ivy partial compilation it may not always be required in the future. To avoid an issue with npm involving conditional versioning, an additional version will be published supporting Angular 13 in #708.

Developers are welcome to pull this branch and run the tests and application. This branch includes pre-built packages of dependencies with peer dependencies on angular-eslint, ESLint, TypeScript, etc. These packages will be replaced with published versions before submitting.

An upgrade guide will be published detailing the steps taken to perform the upgrade. It will recommend upgrading from 12 to 14 in lock-step but all at once to address builds and tests only once, with version 14.

👩‍💻 Implementation

1. Upgrade to Angular 14.
2. Enumerate the update list .
3. Update unmanaged asset exports from libraries.
   • Nimble Angular doesn't declare its unmanaged exports #694
4. Update library options in tsconfig.json.
5. Compile libraries with Ivy partial compilation.
6. Remove all tilde (~) SCSS imports in style files.
7. Enable the build cache.
8. Remove the default project (deprecated).
9. Fix linter errors that I think are do to changes in the implementation of a few rules that were already enabled?

Remaining Work Items

1. add docs describing our Angular support policy. consider whether we should try supporting multiple versions at once or just link to changelog to access previously supported versions
2. discuss if there are other dependencies to update (e.g. tslib) or not update (e.g. typescript)
3. Publish a new version of the styleguide PR#82.

🧪 Testing

• Verified that the linter passes
• Verified that the build passes
• Verified that the automated tests pass
• Verified that the example application works correctly

✅ Checklist

• I have updated the project documentation to reflect my changes or determined no changes are needed.

[TrevorKarjanis]

2. add docs describing our Angular support policy. consider whether we should try supporting multiple versions at once or just link to changelog to access previously supported versions

@jattasNI In this upgrade we are publishing two versions of the package to support 13 and 14 individually. Moving forward, partial complication states, "This is a compilation mode for ngc which produces compiled Angular code that is not tied to a specific Angular runtime version." That sounds sexy but only testing will show. Therefore, Nimble's policy may not be the same as the approach taken here.

3. discuss if there are other dependencies to update (e.g. tslib) or not update (e.g. typescript)

Angular upgrades TypeScript.