-
-
Notifications
You must be signed in to change notification settings - Fork 72
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
@import
linter for bundlers
#1083
@import
linter for bundlers
#1083
Conversation
…my-marmoset-dcd64d6c43
…my-marmoset-dcd64d6c43
…my-marmoset-dcd64d6c43
This comment was marked as resolved.
This comment was marked as resolved.
…my-marmoset-dcd64d6c43
const url = new URL(uri, 'https://454c178c-dadf-429e-8d9c-88e032826008.com'); | ||
if (url.host && url.host !== '454c178c-dadf-429e-8d9c-88e032826008.com') { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why this domain? Clever though!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I wanted something that is extremely unlikely to be used in a real url and generating a new uuid is easy :)
I really which there was some builtin API to detect if a given string is a full url or only a relative path.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This LGTM! Nice to be able to lint these!
This covers the main issues authors can encounter when bundling CSS :
https://
) and local importsWe might add some more later, but I think this is already a good base set of issues it can detect.