-
-
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
v2.0.0 #408
Conversation
# Conflicts: # .babelrc # CHANGELOG.md # package.json # src/core/getExports.js # src/rules/export.js # src/rules/namespace.js # src/rules/no-duplicates.js # src/rules/no-unresolved.js # tests/src/core/resolve.js # utils/resolve.js
# Conflicts: # .travis.yml # CHANGELOG.md
# Conflicts: # CHANGELOG.md # README.md # package.json # src/core/getExports.js # src/core/ignore.js # src/rules/no-named-as-default-member.js # utils/parse.js
they may have always been broken (aka meaningless) in master
We should probably drop support for Node v4 (if it's not already done) and update the rules to the latest format (http://eslint.org/blog/2016/07/eslint-new-rule-format). Willing to do the work, but that should not appear on master before we're close to releasing. |
I'm up for the new format, but it wasn't obvious to me that it's urgently necessary, since the older format is still supported and updating the rules should not be a noticeable change for users, right? Also: isn't ESLint still supporting Node v4? |
Sorry, meant dropping support for Node < v4. The older format is still supported, and the new format is supported by the latest 2.x versions. I consider it a breaking change, even if I haven't encountered any problems with it. Most plugins I've seen that have made the jump released a major version for it, though they almost all also started using ES2015 features supported by Node v4. |
Let's knock it out, then. Feel free to push updated rules to this branch. And yeah, this branch is v4+. 😎 |
# Conflicts: # package.json # src/index.js
- converted all rules using eslint-transforms tool - updated no-unresolved + namespace to match tool output (module.exports vs. exports.{meta,create})
@jfmengels anything else you can think of that we should address before publishing this? I'm thinking of publishing as |
Ah, good job for the rule format. I think we could take a look at updating the recommended config, so that we can at least give a taste of the useful rules that don't need config. I'm thinking no-unresolved, no-extraneous-dependencies, etc. Not opiniated rules, just helpful and probable errors. |
@jfmengels I'll try to merge this over the weekend or early next week. |
Cool! :) |
🎉 |
#2.0!
First real breaking change! tracking progress here. Most discussion should probably occur on the individual issue pages.
core package (eslint-module-utils)
Pull out src/core into eslint-module-utils, to be published separately for other plugins to leverage.
(copied from #234, closes #233)