-
-
Notifications
You must be signed in to change notification settings - Fork 78.8k
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
angular 13+ compilation : legend+* -> Cannot read properties of undefined (reading 'type') v5.1.3 #36136
Comments
no matters, Angular is abandoned |
Angular is not abandoned 😅 I suspect an issue with your compiler or something. This CSS compiles fine everywhere so that's very likely your tooling (compiler, linter, loader...) which struggles. This CSS selector is old enough to not be an issue anywhere (that's CSS 2.1, 20 years ago 😄) so there can't be an issue. Moreover that's only a warning, so I'm closing this for now — but feel free to comment again with any information you'd grab, if needed. |
AngularJS is not the same as Angular. 🙂 |
I have the problem after updating angular/cli 13.3.2->13.3.7. Using bootstrap 5.1.3 |
Imagine getting confused and still recommending angularJs |
Same problem here, any news or fix for this issue? |
For reference, this is the root cause: GoogleChromeLabs/critters#103 |
Prerequisites
I have searched for duplicate or closed issues
I have validated any HTML to avoid common problems
I have read the contributing guidelines
Describe the issue
Hi Team,
I am getting that watning when i compile my angular 13.2.1 project :
Warning: 2 rules skipped due to selector errors:
legend+* -> Cannot read properties of undefined (reading 'type')
legend+* -> Cannot read properties of undefined (reading 'type')
Reduced test cases
If i comment the import of bootstrap i have no longer that warning.
Looking forward for your valuable response.
What operating system(s) are you seeing the problem on?
windows 10
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
v5.1.3
The text was updated successfully, but these errors were encountered: