[js] Update eslint-plugin-import: 2.25.3 → 2.26.0 (minor)#497
Closed
depfu[bot] wants to merge 1 commit intomasterfrom
Closed
[js] Update eslint-plugin-import: 2.25.3 → 2.26.0 (minor)#497depfu[bot] wants to merge 1 commit intomasterfrom
depfu[bot] wants to merge 1 commit intomasterfrom
Conversation
depfu
bot
force-pushed
the
depfu/update/yarn/eslint-plugin-import-2.26.0
branch
from
9150972 to
5ec71ce
Compare
depfu
bot
force-pushed
the
depfu/update/yarn/eslint-plugin-import-2.26.0
branch
from
5ec71ce to
30560fb
Compare
Author
|
Closed in favor of #620. |
1 similar comment
Author
|
Closed in favor of #620. |
Author
|
Closed in favor of #620. |
This file contains hidden or 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
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.
Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ eslint-plugin-import (2.25.3 → 2.26.0) · Repo · Changelog
Release Notes
2.26.0 (from changelog)
2.25.4 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 55 commits:
Bump to 2.26.0[Deps] update `tsconfig-paths`[Docs] `no-unresolved`: fix link[Docs] `order`: TS code examples should use TS code blocks[Deps] update `tsconfig-paths`[Fix] `no-unused-modules`: avoid a crash when processing re-exports[Docs] make rule doc titles consistent[Refactor] `namespace`: try to improve performance[Deps] update `minimatch`[Dev Deps] update `@angular-eslint/template-parser`, `chai`[New] `no-relative-packages`: add fixer[Fix] `no-duplicates`: Ignore duplicate modules in different TypeScript module declarations[Refactor] `export`: clean up rule, tests[Fix] `export`: false positive for typescript namespace merging[Deps] update `eslint-module-utils`[Tests] consolidate eslint config[Tests] handle eslint v8.8 adding `suppressedMessages` property[Fix] `default`: `typescript-eslint-parser`: avoid a crash on exporting as namespaceutils: v2.7.3[New] `no-dynamic-require`: support dynamic import with espree[Tests] export resolved `espree` path[Docs] `no-unresolved`: Fix RegExp escaping in readme[Tests] test on `@typescript-eslint/parser@5`[Tests] export resolved parsers for cleaner comparison[Deps] update `resolve`[New] `no-unused-modules`: support arbitrary module namespace names[New] `namespace`: support arbitrary module namespace names[New] `named`: support arbitrary module namespace names[New] `export`: support arbitrary namespace names[New] `no-named-export`: support arbitrary module namespace names[New] `prefer-default-export`: support arbitrary module namespace names[New] `no-default-export`: support arbitrary module namespace names[New] `no-named-default`: support arbitrary module namespace names[Tests] `default`, `no-anonymous-default-export`, `no-mutable-exports`, `no-named-as-default-member`, `no-named-as-default`: add tests for arbitrary module namespace names[Tests] configure ESLint overrides to parse arbitrary module namespace names[Tests] `no-nodejs-modules`: add tests for node protocol URL[Deps] update `is-core-module`, `resolve`[utils] [Fix] `parse`: restore compatibility by making the return value `ast` againBump to v2.25.4[Dev Deps] update `safe-publish-latest`[Deps] update `eslint-module-utils`utils: v2.7.2[utils] [Refactor] inline `pkgDir` implementation; remove `pkg-dir`[utils] [patch] Fix `@babel/eslint-parser` 8 compatibility[Fix] `named`/`ExportMap`: handle named imports from CJS modules that use dynamic import[Fix] `importType`: properly resolve `@/*`-aliased imports as internal[Docs] `prefer-default-export`: fix typo[Tests] fix OSX tests[Fix] `first`: prevent crash when parsing angular templates[Tests] `packages`: run on multiple eslint versions[Deps] update `tsconfig-paths`[Docs] `order`: Remove duplicate mention of default[Fix] `no-default-import`: report on the token "default" instead of the entire node[Refactor] `no-default-export`: tweak rule[Fix] `importType`: avoid crashing on a non-stringDepfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands