[pull] master from angular:master #79
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![pull[bot]](https://avatars.githubusercontent.com/in/12910?s=60&v=4){kind=small}
…4.0.2 Fixes builds with extractLicenses enabled when using dynamic exports Fixes #22662
…t-i18n`. BREAKING CHANGE: Deprecated `ng x18n` and `ng i18n-extract` commands have been removed in favor of `ng extract-i18n`.
The currently recommended best practice for Github action workflows is to set top-level permissions to read only. And if the job uses the automatic `GITHUB_TOKEN`, fine-grained permissions for each job based on the job's requirements should also be added. All existing workflows in the repository now have top-level read only permission blocks. Only the `scorecard` workflow currently requires additional job level permissions and the minimum set of permissions were already present for the job.
…zer package This API golden file is no longer needed as the `@angular-devkit/build-optimizer` package has been removed as of v14.
The `seedrandom` dependency is not currently used within the package or project. As a result, it has been removed to prevent unneeded packages from being installed during development.
The Dockerfile at the root of the repository is both outdated (uses Node.js v10) and unused by current development processes.
7.17.3 is breaking vendor sourcemaps in windows. See: https://app.circleci.com/pipelines/github/angular/angular-cli/20692/workflows/9fc4f39e-d2f2-47c3-af01-f3a01c1bf542/jobs/288690 Related to babel/babel#14277
… Windows The `glob`-based check when adding the sourcemap support packages to the karma setup was incorrectly skipping the files due to Windows pathing issues. The `glob`-based check, however, is unneeded due to the already present `require.resolve` checks for the sourcemap support packages which will throw if the packages are not present.
…current in optionTransforms
…from OptionTransform type
Preparation for the framework repo as outlined our planning document.
…schematics package The string helpers are predominantly used within schematics that will already depend and import from the `@angular-devkit/schematics` package. By re-exporting from `@angular-devkit/schematics`, the need to directly depend and import `@angular-devkit/core` within a schematic can be reduced and in many cases eliminated.
…ular-devkit/schematics` By using the `strings` re-export from `@angular-devkit/schematics` instead of from `@angular-devkit/core`, the number of imports from `@angular-devkit/core` has been reduced and lowers the direct dependency count for many of the individual schematics.
…vkit/core` imports Several imported types and values from `@angular-devkit/core` could be removed while still maintaining the same functionality. This further reduces the schematics direct dependence on the `@angular-devkit/core` package.
…-based application browser builder An experimental browser application builder (`browser-esbuild`) has been introduced that leverages esbuild as the bundler. This new builder is compatible with options of the current browser application builder (`browser`) and can be enabled for experimentation purposes by replacing the `builder` field of `@angular-devkit/build-angular:browser` from an existing project to `@angular-devkit/build-angular:browser-esbuild`. The builder will generate an ESM-based application and provides support for ES2015+ compatible output with ES2020 as the default. This builder is considered experimental and is not recommended for production applications. Currently not all `browser` builder options and capabilities are supported with this experimental builder. Additional support for these options may be added in the future. The following options and capabilities are not currently supported: * Stylesheet Preprocessors (only CSS styles are supported) * Angular JIT mode (only AOT is supported) * Localization [`localize`] * Watch and dev-server modes [`watch`, `poll`, etc.] * File replacements [`fileReplacements`] * License text extraction [`extractLicenses`] * Bundle budgets [`budgets`] * Global scripts [`scripts`] * Build stats JSON output [`statsJson`] * Deploy URL [`deployURL`] * CommonJS module warnings (no warnings will be generated for CommonJS package usage) * Web Workers * Service workers [`serviceWorker`, `ngswConfigPath`]
The basic suite of E2E tests are now run against the newly introduced experimental esbuild-based builder (`browser-esbuild`). Several tests are currently ignored based on the current feature set of the builder.
Webpack provides built-in support for creating hashes using the xxhash64 algorithm via a WebAssembly module. This can be significantly faster than the previously used md5 algorithm. The Webpack peer dependency has also been update to a minimum of 5.54.0 to ensure xxhash64 supported is available.
…ly from a Tree The schematics `Tree` now contains an additional `readText` method that supports directly reading the content of a file as UTF-8 text. This avoids the need to manually decode a Buffer within a schematic when text content is needed. If a file path does not exist, an exception will be thrown. While this differs from the semantics of `read`, it helps reduce the amount of code needed for common schematic use cases.
…ly from a Tree The schematics `Tree` now contains an additional `readJSON` method that supports directly reading and parsing the content of a file as UTF-8 JSON with comment support. This avoids the need to manually decode a Buffer, parse and handle JSON comments within a schematic when JSON content is needed. If a file path does not exist, an exception will be thrown. While this differs from the semantics of `read`, it helps reduce the amount of code needed for common schematic use cases. JSON parse errors will also result in an exception being thrown with a message detailing the error.
… and `readJSON` functionality Code related to decoding buffers into strings and parsing content into JSON can now be removed by using the support provided directly from the Tree instance for the executing schematic.
…worker configuration file Paths within the `angular.json` file should be relative to the location of the `angular.json` file. The `ngswConfigPath` option was incorrectly using the current working directory for a base path when a relative configuration path was specified. Most of the time this would work as a build command usually is executed from the root of the workspace. However, this may not always be the case and for those cases the actual workspace root is now used to resolve the full path for the service worker configuration file.
Adds the `--standalone` flag when generating components, directives or pipes through `ng generate`.
Updates dev-infra to the latest snapshot, supporting for the new migrate to main helper command.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot]
Can you help keep this open source service alive? 💖 Please sponsor : )