0% -> Unmatched selector: %
See original GitHub issueThis is happening in an angular12 project, which is using critters under the hood I assume.
1 rules skipped due to selector errors:
0% -> Unmatched selector: %
In my styles.scss file I have:
@keyframes bounce {
from {
opacity: 0.10;
transform: scale(0.9);
}
to {
opacity: 1;
transform: scale(1);
}
}
If I remove this code, the warning disappears.
Probably the scss compiler is turning the from
into a 0%
, this is just a guess.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:7
- Comments:5
Top Results From Across the Web
typescript - Angular build - Unmatched selector
When I run npm run build which executes ng build -c production build will be completed as expected. But command prompt will be...
Read more >Generating index html...2 rules skipped due to selector ...
Copying assets complete. ⠋ Generating index html...2 rules skipped due to selector errors: 0 @@ .ui-grid -> Unmatched selector: @@ .ui-grid
Read more >Angular 12 production build warning (MDB4 12)
Generating index html...8 rules skipped due to selector errors: .custom-file-input:lang(en)~.custom-file-label -> unmatched pseudo-class :lang ...
Read more >Angular Universal 'Rules skipped due to selector errors'
I added Angular Universal to my project recently but I get the following error when running ssr: 2 rules skipped due to selector...
Read more >Cheerio unmatched selector error while selecting plain text ...
[Solved]-Cheerio unmatched selector error while selecting plain text-node.js. Search. score:0. Your element has class foo and selector not:
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Ran into this as well after updating to Angular 13. This change to the location @developit mentioned fixed it for me:
Awesome, thanks @benz-netapp and @JessicaSachs! I’ve just merged the fix, and published it as critters@0.0.16 / critters-webpack-plugin@3.0.2.