Update dependency @cloudfour/eslint-config to v27 - #2499
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
✅ Deploy Preview for cloudfour-patterns ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
renovate
Bot
force-pushed
the
renovate/major-eslint
branch
from
September 19, 2026 04:38
9a294fb to
f8aa2c4
Compare
renovate
Bot
force-pushed
the
renovate/major-eslint
branch
from
September 19, 2026 16:25
f8aa2c4 to
92b423b
Compare
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.
This PR contains the following updates:
26.1.0→27.0.0Release Notes
cloudfour/eslint-config (@cloudfour/eslint-config)
v27.0.0Compare Source
Major Changes
Update
eslint-config-xoto v2, which moveseslint-plugin-unicornfromv73 to v74. The bump adds, removes and reconfigures no unicorn rule — v74's
changes are fixes to rules we already run. Measured against a real consumer
project, it produced three fewer reports across 64 TypeScript files, where
unicorn/prefer-number-coercionandunicorn/prefer-string-replace-allhadbeen flagging cases they misread.
n/prefer-process-get-builtin-moduleis now on, added by xo v2. It reportsrequire('node:fs')andawait import('node:fs')for built-in modules andwants
process.getBuiltinModule('node:fs')instead. It is not auto-fixable,so whatever it catches has to be edited by hand. This is the only rule the
upgrade turns on, and the only source of new errors in it.
Most projects will never see it. The rule switches itself off unless the
nearest
package.jsondeclares anengines.nodefalling entirely within^20.16.0 || >=22.3.0— the versions whereprocess.getBuiltinModuleisguaranteed to exist. A package with no
engines.nodeat all, or one as looseas
>=20, is left alone.Where it does apply, the payoff is in ES modules, where it removes the need
for
createRequire. It fires in CommonJS too, whererequireis the nativeidiom and the rewrite buys nothing, so build scripts and
.cjsfiles are thelikeliest place to meet it. Turn it off for those paths in your own config if
it is noisy:
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ 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.
This PR was generated by Mend Renovate. View the repository job log.