npm @angular/cli 12.0.0-next.9

latest releases: 17.3.2, 16.2.13, 15.2.11...
2 years ago

Commits

@angular-devkit/build-angular (12.0.0-next.9)

Commit Description Notes
upgrade to Webpack 5 throughout the build system
support processing component inline CSS styles
support specifying stylesheet language for inline component styles
update karma builder to use non-deprecated API
disable webpack cache when using `NG_BUILD_CACHE`
remove duplicate application bundle generation complete message
mark programmatic builder execution functions as experimental

@angular-devkit/build-webpack (0.1200.0-next.9)

Commit Description Notes
support Webpack 5

@angular-devkit/core (12.0.0-next.9)

Commit Description Notes
update schema validator

@angular/cli (12.0.0-next.9)

Commit Description Notes
add message update updating from non LTS versions of the CLI

@ngtools/webpack (12.0.0-next.9)

Commit Description Notes
support multiple plugin instances per compilation
support generating data URIs for inline component styles in JIT
support processing inline component styles in AOT

@schematics/angular (12.0.0-next.9)

Commit Description Notes
configure new libraries to be published in Ivy partial mode
update `jasmine-spec-reporter` to version 7
migrate web workers to support Webpack 5
update web-worker to support Webpack 5

Breaking Changes

@angular-devkit/core: update schema validator (0875313)

support for JSON Schema draft-04 and draft-06 is removed. If you have schemas using the `id` keyword replace them with `$id`. For an interim period we will auto rename any top level `id` keyword to `$id`.

NB: This change only effects schematics and builders authors.

@angular-devkit/build-angular: upgrade to Webpack 5 throughout the build system (d883ce5)

Webpack 5 generates similar but differently named files for lazy loaded JavaScript files in development configurations (when the `namedChunks` option is enabled). For the majority of users this change should have no effect on the application and/or build process. Production builds should also not be affected as the `namedChunks` option is disabled by default in production configurations. However, if a project's post-build process makes assumptions as to the file names then adjustments may need to be made to account for the new naming paradigm. Such post-build processes could include custom file transformations after the build, integration into service-side frameworks, or deployment procedures. Example development file name change: `lazy-lazy-module.js` --> `src_app_lazy_lazy_module_ts.js`

@angular-devkit/build-angular: upgrade to Webpack 5 throughout the build system (d883ce5)

Webpack 5 now includes web worker support. However, the structure of the URL within the `Worker` constructor must be in a specific format that differs from the current requirement. Web worker usage should be updated as shown below (where `./app.worker` should be replaced with the actual worker name):

Before:

new Worker('./app.worker', ...)

After:

new Worker(new URL('./app.worker', import.meta.url), ...)

Special Thanks

Alan Agius, Charles Lyding, Keen Yee Liau, Doug Parker, Douglas Parker

Don't miss a new cli release

NewReleases is sending notifications on new releases.