Skip to content
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 46 commits into from Dec 9, 2019
Merged

Release v2.19.0 #1556

merged 46 commits into from Dec 9, 2019

Conversation

ljharb
Copy link
Member

@ljharb ljharb commented Dec 8, 2019

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.

duncanbeevers and others added 30 commits May 17, 2018 16:42
…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>
@ljharb ljharb requested a review from benmosher December 8, 2019 23:14
@ljharb
Copy link
Member Author

ljharb commented Dec 8, 2019

I'll ff-merge this and publish it later tonight.

Appveyor test failures are expected, due to #1513.

@ljharb ljharb self-assigned this Dec 8, 2019
@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 96.441% when pulling 9b76635 on ljharb:release-2.19.0 into 1a90a20 on benmosher:release.

4 similar comments
@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 96.441% when pulling 9b76635 on ljharb:release-2.19.0 into 1a90a20 on benmosher:release.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 96.441% when pulling 9b76635 on ljharb:release-2.19.0 into 1a90a20 on benmosher:release.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 96.441% when pulling 9b76635 on ljharb:release-2.19.0 into 1a90a20 on benmosher:release.

@coveralls
Copy link

Coverage Status

Coverage increased (+1.1%) to 96.441% when pulling 9b76635 on ljharb:release-2.19.0 into 1a90a20 on benmosher:release.

@ljharb ljharb merged commit 9b76635 into import-js:release Dec 9, 2019
@ljharb ljharb deleted the release-2.19.0 branch December 9, 2019 06:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

None yet