-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Don't try to read imported JSON files #267
Comments
You got those errors on a |
No, here's the relevant statement: https://github.com/sindresorhus/got/blob/67ee190881f4ba9c498708dc41c1d71c5b6039a2/test/headers.js#L3 |
Ah, okay, that makes sense. I think it probably makes sense to handle this in the Node resolver and return I am assuming you're not expecting it to attempt to lint a |
Correct. |
Actually, I suddenly think it would make more sense to have a parseable extension whitelist ( Might make sense to also make a rule to flag imports of files that don't match that list, I would want some way to avoid having accidental |
I like the idea of such option, but should default to |
Sure. Maybe a better expression of the default would have been |
Bumped out of |
* import/extensions setting: parser whitelist. fixes #267 * default to all extensions valid to avoid breaking change until semver-next
In Node.js, this is valid and a common pattern:
I got errors when I ran this plugin on
got
:The text was updated successfully, but these errors were encountered: