Update eslint-plugin-import 2.27.5 → 2.28.0 (minor) #42
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.27.5 → 2.28.0) · Repo · Changelog
Release Notes
2.28.0 (from changelog)
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 49 commits:
Bump to 2.28.0[Refactor] `order`: use `object.groupby`[Refactor] `no-internal-modules`: simplify a reduce[Refactor] `no-useless-path-segments`: use `.filter` instead of `.reduce`[Refactor] `no-anonymous-default-export`: use `fromEntries` instead of `reduce`[Refactor] `no-duplicates`, `no-unused-modules`: use `flatMap` instead of `map` + `filter`[Tests] allow WSL builds to fail, for now[Fix] `no-unused-modules`: report error on binding instead of parent export[Tests] `no-unused-modules`: document error reported on entire `export` statement[Fix] `no-unused-modules`: improve schema[Tests] `no-unused-modules`: properly skip in mocha 3[eslint] enable `array-bracket-spacing`[Fix] `extensions`: handle `.` and `..` properly[Fix] `no-duplicates`: Prefer combined type and regular imports when using `prefer-inline`[Deps] update `semver`[Fix] guard against empty parent[Refactor] `no-unused-modules`: use `array.prototype.flatmap`[Refactor] `no-anonymous-default-export`: use `object.fromentries`[Refactor] `exports-last`: use `array.prototype.findlastindex`[meta] Add "eslint-plugin" to the list of keywords in package.json[Deps] update `is-core-module`Fix invalid YAML in import/parsers example[Refactor] `ExportMap`: rename `tsConfig` to `tsconfig`[Tests] switch some files to unix line endings[Deps] update `eslint-module-utils`[utils] v2.8.0[Tests] fix tests for older nodes[Deps] update `resolve`[meta] add missing CHANGELOG entry[Fix] `order`: partial fix for #2687[deps] update `is-core-module`, `resolve`[resolvers] [*] [deps] update `is-core-module`, `resolve`[eslint] tighten up rules[Fix] `no-extraneous-dependencies`/TypeScript: do not error when importing inline type from dev dependencies[perf] `ExportMap`: Improve ExportMap.for performance on larger codebases[utils] [new] `parse`: support flat configRevert "[Fix] TypeScript config: fix resolver extension settings"[utils] [perf] Performance of fullResolve[Docs] `extensions`: reference node ESM behavior[Tests] `no-extraneous-dependencies`: add passing test[Fix] `consistent-type-specifier-style`: fix accidental removal of comma in certain cases[Deps] update `tsconfig-paths`[Dev Deps] update `@angular-eslint/template-parser`, `chai`, `eslint-doc-generator`, `glob`[Docs] `group-exports`: fix syntax highlighting[Fix] TypeScript config: fix resolver extension settings[Fix] `no-duplicates`: remove duplicate identifiers in duplicate importsRevert "[Tests] update nvm in travis"[Docs] `no-duplicates`: fix example schema[Tests] `order`: add a passing test👉 No CI detected
You don't seem to have any Continuous Integration service set up!
Without a service that will test the Depfu branches and pull requests, we can't inform you if incoming updates actually work with your app. We think that this degrades the service we're trying to provide down to a point where it is more or less meaningless.
This is fine if you just want to give Depfu a quick try. If you want to really let Depfu help you keep your app up-to-date, we recommend setting up a CI system:
* [Circle CI](https://circleci.com), [Semaphore ](https://semaphoreci.com) and [Github Actions](https://docs.github.com/actions) are all excellent options. * If you use something like Jenkins, make sure that you're using the Github integration correctly so that it reports status data back to Github. * If you have already set up a CI for this repository, you might need to check your configuration. Make sure it will run on all new branches. If you don’t want it to run on every branch, you can whitelist branches starting with `depfu/`.Depfu 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