We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
build
Today applications that have $localize and no localize config (or localize/init polyfill) fail at runtime with .
$localize
This might be not a big problem for single-app repositories, but it quickly becomes a bigger issue for monorepositories with multiple buildable apps.
Instead of runtime error application build could fail. This would allow easier/earlier detection of the issue.
This would be very helpful change for monorepos as internal libraries with $localize/i18n would be identified in build time.
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Command
build
Description
Today applications that have
$localize
and no localize config (or localize/init polyfill) fail at runtime with .This might be not a big problem for single-app repositories, but it quickly becomes a bigger issue for monorepositories with multiple buildable apps.
Describe the solution you'd like
Instead of runtime error application build could fail. This would allow easier/earlier detection of the issue.
This would be very helpful change for monorepos as internal libraries with $localize/i18n would be identified in build time.
Describe alternatives you've considered
No response
The text was updated successfully, but these errors were encountered: