Thank you for this workaround... SVG issue.
Open
bug
- Dominant language
- JavaScript
- Stars
- 91
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I currently have a project that has globalCSS in npm components and this workaround is what I'm attempting to use.
Unfortunately, I also use the next-images package for important images of all file types (including SVGs).
No matter what, running next-global-css attempts to also parse SVG files and always errors with:
error - SyntaxError: Unexpected token '<'
Is there a way to exclude SVG files easily from next-global-css, or make it skip them entirely by default?
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.