Update dependency eslint-plugin-import to v2.31.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
eslint-plugin-import	2.29.1 -> 2.31.0

---

Release Notes

import-js/eslint-plugin-import (eslint-plugin-import)

v2.31.0

Compare Source

Added

• support eslint v9 ([#​2996], thanks [@​G-Rath] [@​michaelfaith])
• [order]: allow validating named imports ([#​3043], thanks [@​manuth])
• [extensions]: add the checkTypeImports option ([#​2817], thanks [@​phryneas])

Fixed

• ExportMap / flat config: include languageOptions in context ([#​3052], thanks [@​michaelfaith])
• [no-named-as-default]: Allow using an identifier if the export is both a named and a default export ([#​3032], thanks [@​akwodkiewicz])
• [export]: False positive for exported overloaded functions in TS ([#​3065], thanks [@​liuxingbaoyu])
• exportMap: export map cache is tainted by unreliable parse results ([#​3062], thanks [@​michaelfaith])
• exportMap: improve cacheKey when using flat config ([#​3072], thanks [@​michaelfaith])
• adjust "is source type module" checks for flat config ([#​2996], thanks [@​G-Rath])

Changed

• [Docs] [no-relative-packages]: fix typo ([#​3066], thanks [@​joshuaobrien])
• [Performance] [no-cycle]: dont scc for each linted file ([#​3068], thanks [@​soryy708])
• [Docs] [no-cycle]: add disableScc to docs ([#​3070], thanks [@​soryy708])
• [Tests] use re-exported RuleTester ([#​3071], thanks [@​G-Rath])
• [Docs] [no-restricted-paths]: fix grammar ([#​3073], thanks [@​unbeauvoyage])
• [Tests] [no-default-export], [no-named-export]: add test case (thanks [@​G-Rath])

v2.30.0

Compare Source

Added

• [dynamic-import-chunkname]: add allowEmpty option to allow empty leading comments ([#​2942], thanks [@​JiangWeixian])
• [dynamic-import-chunkname]: Allow empty chunk name when webpackMode: 'eager' is set; add suggestions to remove name in eager mode ([#​3004], thanks [@​amsardesai])
• [no-unused-modules]: Add ignoreUnusedTypeExports option ([#​3011], thanks [@​silverwind])
• add support for Flat Config ([#​3018], thanks [@​michaelfaith])

Fixed

• [no-extraneous-dependencies]: allow wrong path ([#​3012], thanks [@​chabb])
• [no-cycle]: use scc algorithm to optimize ([#​2998], thanks [@​soryy708])
• [no-duplicates]: Removing duplicates breaks in TypeScript ([#​3033], thanks [@​yesl-kim])
• [newline-after-import]: fix considerComments option when require ([#​2952], thanks [@​developer-bandi])
• [order]: do not compare first path segment for relative paths ([#​2682]) ([#​2885], thanks [@​mihkeleidast])

Changed

• [Docs] no-extraneous-dependencies: Make glob pattern description more explicit ([#​2944], thanks [@​mulztob])
• [no-unused-modules]: add console message to help debug [#​2866]
• [Refactor] ExportMap: make procedures static instead of monkeypatching exportmap ([#​2982], thanks [@​soryy708])
• [Refactor] ExportMap: separate ExportMap instance from its builder logic ([#​2985], thanks [@​soryy708])
• [Docs] order: Add a quick note on how unbound imports and --fix ([#​2640], thanks [@​minervabot])
• [Tests] appveyor -> GHA (run tests on Windows in both pwsh and WSL + Ubuntu) ([#​2987], thanks [@​joeyguerra])
• [actions] migrate OSX tests to GHA ([ljharb#37], thanks [@​aks-])
• [Refactor] exportMapBuilder: avoid hoisting ([#​2989], thanks [@​soryy708])
• [Refactor] ExportMap: extract "builder" logic to separate files ([#​2991], thanks [@​soryy708])
• [Docs] [order]: update the description of the pathGroupsExcludedImportTypes option ([#​3036], thanks [@​liby])
• [readme] Clarify how to install the plugin ([#​2993], thanks [@​jwbth])

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/babel-plugin-transform-builtin-extend@1.1.2	Transitive: environment, eval, filesystem, network	+18	3.01 MB	loganfsmyth
npm/babel-preset-env@1.7.0	Transitive: environment, eval, filesystem, network	+62	5.73 MB	existentialism
npm/eslint-config-airbnb-base@15.0.0	None	+1	97.9 kB	ljharb
npm/eslint-plugin-import@2.31.0	environment, filesystem, unsafe Transitive: eval	+108	6.49 MB	ljharb

🚮 Removed packages: npm/@typescript-eslint/eslint-plugin@6.21.0, npm/@typescript-eslint/parser@6.21.0, npm/eslint-plugin-import@2.29.1, npm/eslint@8.57.1

View full report↗︎

[socket-security]

🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎

To accept the risk, merge this PR and you will not be notified again.

Alert	Package	Note	Source	CI
Environment variable access	npm/debug@2.6.9	Env Vars: DEBUG_FD Location: Package overview	javascript/atbash-cipher/package-lock.json javascript/atbash-cipher/package.json	🚫
Filesystem access	npm/debug@2.6.9	Module: fs Location: Package overview	javascript/atbash-cipher/package-lock.json javascript/atbash-cipher/package.json	🚫
Uses eval	npm/is-generator-function@1.0.10	Eval Type: Function Location: Package overview	javascript/space-age/package-lock.json javascript/space-age/package.json	🚫
Uses eval	npm/is-async-function@2.0.0	Eval Type: Function Location: Package overview	javascript/space-age/package-lock.json javascript/space-age/package.json	🚫
Environment variable access	npm/@babel/core@7.21.0	Location: Package overview	javascript/space-age/package-lock.json javascript/space-age/package.json	🚫
Environment variable access	npm/@babel/core@7.21.0	Env Vars: NODE_DEBUG Location: Package overview	javascript/space-age/package-lock.json javascript/space-age/package.json	🚫
Critical CVE	npm/babel-traverse@6.26.0	CVE: GHSA-67hx-6x53-jw92 Babel vulnerable to arbitrary code execution when compiling specifically crafted malicious code (CRITICAL) Affected versions: < 7.23.2 Patched version: No patched versions	javascript/atbash-cipher/package-lock.json javascript/atbash-cipher/package.json	🚫
Environment variable access	npm/babel-traverse@6.26.0	Env Vars: NODE_ENV Location: Package overview	javascript/atbash-cipher/package-lock.json javascript/atbash-cipher/package.json	🚫
Deprecated	npm/core-js@2.5.7	Reason: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.	javascript/atbash-cipher/package-lock.json javascript/atbash-cipher/package.json	🚫
Uses eval	npm/core-js@2.5.7	Eval Type: Function Location: Package overview	javascript/atbash-cipher/package-lock.json javascript/atbash-cipher/package.json	🚫
Uses eval	npm/core-js@2.5.7	Eval Type: Function Location: Package overview	javascript/atbash-cipher/package-lock.json javascript/atbash-cipher/package.json	🚫
Environment variable access	npm/eslint-plugin-import@2.31.0	Env Vars: key Location: Package overview	javascript/space-age/package-lock.json javascript/space-age/package.json	🚫

View full report↗︎

Next steps

What is environment variable access?

Package accesses environment variables, which may be a sign of credential stuffing or data theft.

Packages should be clear about which environment variables they access, and care should be taken to ensure they only access environment variables they claim to.

What is filesystem access?

Accesses the file system, and could potentially read sensitive data.

If a package must read the file system, clarify what it will read and ensure it reads only what it claims to. If appropriate, packages can leave file system access to consumers and operate on data passed to it instead.

What is dynamic code execution?

Package uses dynamic code execution (e.g., eval()), which is a dangerous practice. This can prevent the code from running in certain environments and increases the risk that the code may contain exploits or malicious behavior.

Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code.

What is a critical CVE?

Contains a Critical Common Vulnerability and Exposure (CVE).

Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies.

What is a deprecated package?

The maintainer of the package marked it as deprecated. This could indicate that a single version should not be used, or that the package is no longer maintained and any new vulnerabilities will not be fixed.

Research the state of the package and determine if there are non-deprecated versions that can be used, or if it should be replaced with a new, supported solution.

Take a deeper look at the dependency

Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev.

Remove the package

If you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency.

Mark a package as acceptable risk

To ignore an alert, reply with a comment starting with @SocketSecurity ignore followed by a space separated list of ecosystem/package-name@version specifiers. e.g. @SocketSecurity ignore npm/foo@1.0.0 or ignore all packages with @SocketSecurity ignore-all

• @SocketSecurity ignore npm/debug@2.6.9
• @SocketSecurity ignore npm/is-generator-function@1.0.10
• @SocketSecurity ignore npm/is-async-function@2.0.0
• @SocketSecurity ignore npm/@babel/core@7.21.0
• @SocketSecurity ignore npm/babel-traverse@6.26.0
• @SocketSecurity ignore npm/core-js@2.5.7
• @SocketSecurity ignore npm/eslint-plugin-import@2.31.0

[renovate]

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: typescript/rna-transcription/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/eslint-plugin@6.21.0
npm error Found: eslint@9.16.0
npm error node_modules/eslint
npm error   dev eslint@"9.16.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/utils@6.21.0
npm error     node_modules/@typescript-eslint/eslint-plugin/node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"6.21.0" from @typescript-eslint/eslint-plugin@6.21.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"6.21.0" from the root project
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from eslint@9.16.0
npm error   1 more (eslint-plugin-import)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.0.0 || ^8.0.0" from @typescript-eslint/eslint-plugin@6.21.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"6.21.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.1
npm error node_modules/eslint
npm error   peer eslint@"^7.0.0 || ^8.0.0" from @typescript-eslint/eslint-plugin@6.21.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"6.21.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-08T22_21_57_613Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-08T22_21_57_613Z-debug-0.log

File name: typescript/resistor-color-duo/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @typescript-eslint/eslint-plugin@6.21.0
npm error Found: eslint@9.16.0
npm error node_modules/eslint
npm error   dev eslint@"9.16.0" from the root project
npm error   peer eslint@"^6.0.0 || ^7.0.0 || >=8.0.0" from @eslint-community/eslint-utils@4.4.0
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.4.0" from @typescript-eslint/utils@6.21.0
npm error     node_modules/@typescript-eslint/eslint-plugin/node_modules/@typescript-eslint/utils
npm error       @typescript-eslint/utils@"6.21.0" from @typescript-eslint/eslint-plugin@6.21.0
npm error       node_modules/@typescript-eslint/eslint-plugin
npm error         dev @typescript-eslint/eslint-plugin@"6.21.0" from the root project
npm error       1 more (@typescript-eslint/type-utils)
npm error     @eslint-community/eslint-utils@"^4.2.0" from eslint@9.16.0
npm error   1 more (eslint-plugin-import)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.0.0 || ^8.0.0" from @typescript-eslint/eslint-plugin@6.21.0
npm error node_modules/@typescript-eslint/eslint-plugin
npm error   dev @typescript-eslint/eslint-plugin@"6.21.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.1
npm error node_modules/eslint
npm error   peer eslint@"^7.0.0 || ^8.0.0" from @typescript-eslint/eslint-plugin@6.21.0
npm error   node_modules/@typescript-eslint/eslint-plugin
npm error     dev @typescript-eslint/eslint-plugin@"6.21.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-08T22_22_01_405Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-08T22_22_01_405Z-debug-0.log

File name: javascript/triangle/package-lock.json

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-airbnb-base@15.0.0
npm error Found: eslint@9.16.0
npm error node_modules/eslint
npm error   dev eslint@"9.16.0" from the root project
npm error   peer eslint@"^7.5.0 || ^8.0.0 || ^9.0.0" from @babel/eslint-parser@7.25.9
npm error   node_modules/@babel/eslint-parser
npm error     dev @babel/eslint-parser@"7.25.9" from the root project
npm error   2 more (@eslint-community/eslint-utils, eslint-plugin-import)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from eslint-config-airbnb-base@15.0.0
npm error node_modules/eslint-config-airbnb-base
npm error   dev eslint-config-airbnb-base@"15.0.0" from the root project
npm error
npm error Conflicting peer dependency: eslint@8.57.1
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from eslint-config-airbnb-base@15.0.0
npm error   node_modules/eslint-config-airbnb-base
npm error     dev eslint-config-airbnb-base@"15.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-12-08T22_22_12_846Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-12-08T22_22_12_846Z-debug-0.log