Skip to content

Thank you for this workaround... SVG issue. #12

@gfmjr

Description

@gfmjr

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?

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions