-
Notifications
You must be signed in to change notification settings - Fork 27k
fix(localize): add @angular/localize/init as polyfill in angular.json
#56300
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
…son` This commit addresses an issue where the `@angular/localize/init` polyfill is not included when there are no polyfills specified in the `angular.json` file.
This commit addresses an issue where the `@angular/localize/init` polyfill is not included when there are no polyfills specified in the `angular.json` file. However, this approach has a drawback: the localize polyfill will always be added if it is found in a monorepo, even if an application does not use i18n. As a result, we will issue a warning to inform users about this behavior and encourage them to explicitly add it to their `polyfills` configuration. The `ng add` schematic will also be updated to add the polyfill as in the builders config, see: angular/angular#56300 Closes: angular#27786
This commit addresses an issue where the `@angular/localize/init` polyfill is not included when there are no polyfills specified in the `angular.json` file. However, this approach has a drawback: the localize polyfill will always be added if it is found in a monorepo, even if an application does not use i18n. As a result, we will issue a warning to inform users about this behavior and encourage them to explicitly add it to their `polyfills` configuration. The `ng add` schematic will also be updated to add the polyfill as in the builders config, see: angular/angular#56300 Closes: angular#27786
This commit addresses an issue where the `@angular/localize/init` polyfill is not included when there are no polyfills specified in the `angular.json` file. However, this approach has a drawback: the localize polyfill will always be added if it is found in a monorepo, even if an application does not use i18n. As a result, we will issue a warning to inform users about this behavior and encourage them to explicitly add it to their `polyfills` configuration. The `ng add` schematic will also be updated to add the polyfill as in the builders config, see: angular/angular#56300 Closes: angular#27786
This commit addresses an issue where the `@angular/localize/init` polyfill is not included when there are no polyfills specified in the `angular.json` file. However, this approach has a drawback: the localize polyfill will always be added if it is found in a monorepo, even if an application does not use i18n. As a result, we will issue a warning to inform users about this behavior and encourage them to explicitly add it to their `polyfills` configuration. The `ng add` schematic will also be updated to add the polyfill as in the builders config, see: angular/angular#56300 Closes: angular#27786
This commit addresses an issue where the `@angular/localize/init` polyfill is not included when there are no polyfills specified in the `angular.json` file. However, this approach has a drawback: the localize polyfill will always be added if it is found in a monorepo, even if an application does not use i18n. As a result, we will issue a warning to inform users about this behavior and encourage them to explicitly add it to their `polyfills` configuration. The `ng add` schematic will also be updated to add the polyfill as in the builders config, see: angular/angular#56300 Closes: angular#27786
This commit addresses an issue where the `@angular/localize/init` polyfill is not included when there are no polyfills specified in the `angular.json` file. However, this approach has a drawback: the localize polyfill will always be added if it is found in a monorepo, even if an application does not use i18n. As a result, we will issue a warning to inform users about this behavior and encourage them to explicitly add it to their `polyfills` configuration. The `ng add` schematic will also be updated to add the polyfill as in the builders config, see: angular/angular#56300 Closes: angular#27786
This commit addresses an issue where the `@angular/localize/init` polyfill is not included when there are no polyfills specified in the `angular.json` file. However, this approach has a drawback: the localize polyfill will always be added if it is found in a monorepo, even if an application does not use i18n. As a result, we will issue a warning to inform users about this behavior and encourage them to explicitly add it to their `polyfills` configuration. The `ng add` schematic will also be updated to add the polyfill as in the builders config, see: angular/angular#56300 Closes: angular#27786
AndrewKushnir
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@alan-agius4 looks great, I've just added a couple minor comments.
b3e0c88 to
9742b21
Compare
9742b21 to
bfdcf4a
Compare
AndrewKushnir
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
|
This PR was merged into the repository by commit 81486c2. |
It can be re-enabled now that angular/angular#56300 have been released in v18.1.0-next.2
It can be re-enabled now that angular/angular#56300 have been released in v18.1.0-next.2
It can be re-enabled now that angular/angular#56300 have been released in v18.1.0-next.2
It can be re-enabled now that angular/angular#56300 have been released in v18.1.0-next.2
It can be re-enabled now that angular/angular#56300 have been released in v18.1.0-next.2
It can be re-enabled now that angular/angular#56300 have been released in v18.1.0-next.2 (cherry picked from commit 355ae1a)
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
This commit addresses an issue where the
@angular/localize/initpolyfill is not included when there are no polyfills specified in theangular.jsonfile.