-
-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
release v1.14.0 #504
release v1.14.0 #504
Conversation
* always ignore invalid extensions if `import/extensions` is set (fixes #478) * reboot of npm `watch` script
…(i.e. node_modules)
You should probably create an issue to discuss this, so that people interested by this participate and give their meaning. I've left you a comment here https://github.com/benmosher/eslint-plugin-import/pull/503/files#r75605034, but LGTM otherwise. |
Yeah, this is where I ended up as well, thinking through it. Globs are great, and very expressive, but I feel like >95% of the time, one or two file extensions will be totally sufficient. |
cc @jfmengels. I want to get
import/parsers
published so I can use it at work.Also I clearly forgot to do this for 1.13.0 😳, only changes are the bugfix for #416 (PR #499) and
import/parsers
via #503. I have QA'd.PR summary:
namespace
rule runtime crash #499: fix Cannot read property 'namespace' of undefined #416import/parsers
to support ES-module-compliant alt-JS interopIt'd probably be good if you took a look at the
import/parsers
config schema. Though v2 is on the horizon so we could break it if needed/desired as part of that release... only thing I'm thinking is whether it should be glob- or regex-based instead of array-of-extensions. I like AoE mostly for consistency withimport/extensions
, and it's easy to grok. Con: less powerful, but could be enhanced to support glob/regex later if desired.