fix(compiler-cli): show a more specific error for Ivy NgModules#41534
Closed
alxhub wants to merge 1 commit intoangular:masterfrom
Closed
fix(compiler-cli): show a more specific error for Ivy NgModules#41534alxhub wants to merge 1 commit intoangular:masterfrom
alxhub wants to merge 1 commit intoangular:masterfrom
Conversation
When an Ivy NgModule is imported into a View Engine build, it doesn't have metadata.json files that describe it as an NgModule, so it appears to VE builds as a plain, undecorated class. The error message shown in this situation generic and confusing, since it recommends adding an @NgModule annotation to a class from a library. This commit adds special detection into the View Engine compiler to give a more specific error message when an Ivy NgModule is imported.
7c45335 to
87defbb
Compare
AndrewKushnir
approved these changes
Apr 12, 2021
AndrewKushnir
approved these changes
Apr 12, 2021
Contributor
AndrewKushnir
left a comment
There was a problem hiding this comment.
Reviewed-for: public-api
petebacondarwin
approved these changes
Apr 12, 2021
Contributor
petebacondarwin
left a comment
There was a problem hiding this comment.
Reviewed-for: public-api
|
You can preview 7c45335 at https://pr41534-7c45335.ngbuilds.io/. |
atscott
reviewed
Apr 12, 2021
|
|
||
| 2) the library was published for Angular Ivy and v12+ applications only. Check its peer dependencies carefully and ensure that you're using a compatible version of Angular. | ||
|
|
||
| See https://angular.io/errors/NG6999 for more information. |
Contributor
There was a problem hiding this comment.
Is there a corresponding PR that adds this page?
Member
Author
There was a problem hiding this comment.
Not yet - I reached out to devrel about what content we want to add here.
jessicajaniuk
approved these changes
Apr 13, 2021
Contributor
jessicajaniuk
left a comment
There was a problem hiding this comment.
LGTM 🍪
reviewed-for: public-api
zarend
approved these changes
Apr 13, 2021
zarend
pushed a commit
that referenced
this pull request
Apr 13, 2021
When an Ivy NgModule is imported into a View Engine build, it doesn't have metadata.json files that describe it as an NgModule, so it appears to VE builds as a plain, undecorated class. The error message shown in this situation generic and confusing, since it recommends adding an @NgModule annotation to a class from a library. This commit adds special detection into the View Engine compiler to give a more specific error message when an Ivy NgModule is imported. PR Close #41534
alxhub
added a commit
to alxhub/angular
that referenced
this pull request
Apr 13, 2021
…lar#41534) When an Ivy NgModule is imported into a View Engine build, it doesn't have metadata.json files that describe it as an NgModule, so it appears to VE builds as a plain, undecorated class. The error message shown in this situation generic and confusing, since it recommends adding an @NgModule annotation to a class from a library. This commit adds special detection into the View Engine compiler to give a more specific error message when an Ivy NgModule is imported. PR Close angular#41534
zarend
pushed a commit
that referenced
this pull request
Apr 14, 2021
…) (#41598) When an Ivy NgModule is imported into a View Engine build, it doesn't have metadata.json files that describe it as an NgModule, so it appears to VE builds as a plain, undecorated class. The error message shown in this situation generic and confusing, since it recommends adding an @NgModule annotation to a class from a library. This commit adds special detection into the View Engine compiler to give a more specific error message when an Ivy NgModule is imported. PR Close #41534 PR Close #41598
|
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 file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
7 participants
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.
When an Ivy NgModule is imported into a View Engine build, it doesn't have
metadata.json files that describe it as an NgModule, so it appears to VE
builds as a plain, undecorated class. The error message shown in this
situation generic and confusing, since it recommends adding an @NgModule
annotation to a class from a library.
This commit adds special detection into the View Engine compiler to give a
more specific error message when an Ivy NgModule is imported.