-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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 v2.19.0 #1556
Merged
Merged
Release v2.19.0 #1556
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…n groups Fixes import-js#1406. Fixes import-js#389. Closes import-js#629. Closes import-js#1105. Closes import-js#1360. Co-Authored-By: dannysindra <als478@cornell.edu> Co-Authored-By: Radim Svoboda <radim.svoboda@socialbakers.com> Co-Authored-By: Soma Lucz <luczsoma@gmail.com> Co-Authored-By: Randall Reed, Jr <randallreedjr@gmail.com> Co-Authored-By: Jordan Harband <ljharb@gmail.com>
- Add guards to avoid crashing older versions of ESLint - Note that no-namespace's --fix requires ESLint 5+ - Prevent no-namespace --fix tests from running under ESLint < 5
[eslint] make CI lint tests, utils, resolvers, ...etc
…se positives when using some webpack loaders. Fixes import-js#1107.
…space A typescript namespace may be declared multiple times, it is then merged together and considered to be a single declaration from consuming code. In the case where a merged namespace is assigned as the export from a module then the declarations from all the instances of the namespace in the AST need to be considered as exported.
Fixes import-js#1252. - Reordering import statement to line below ignores uncrossable statements - Add more tests for ordering around function call
…ack` This enables users to change the lookup of the webpack module for the resolve functionality should it not be in the user's local node_modules. This pertains to the case of a CLI where the CLI may be in charge of webpack, and the user's repo doesn't have it. Co-Authored-By: Jordan Harband <ljharb@gmail.com>
Co-Authored-By: Matt Seccafien <matt@studiocartogram.com>
… `interpret`, `lodash`, `resolve`, `semver`
I'll ff-merge this and publish it later tonight. Appveyor test failures are expected, due to #1513. |
4 similar comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v2.19.0 of the main package.
This includes already-published v2.5.0 of eslint-module-utils and v0.12.0 of the webpack resolver.