Update babel monorepo #1036

renovate · 2025-01-11T15:02:08Z

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@babel/cli (source)	`7.26.4` -> `7.27.2`
@babel/core (source)	`7.26.0` -> `7.27.1`
@babel/eslint-parser (source)	`7.25.9` -> `7.27.1`
@babel/preset-env (source)	`7.26.0` -> `7.27.2`

Release Notes

babel/babel (@babel/cli)

`v7.27.2`

Compare Source

🐛 Bug Fix

babel-parser
- #17289 fix: @babel/parser/bin/index.js contains node: protocol require (@liuxingbaoyu)
- #17291 fix: Private class method not found when TS and estree (@liuxingbaoyu)
babel-plugin-transform-object-rest-spread
- #17281 Fix: improve object rest handling in array pattern (@JLHwung)
babel-plugin-transform-modules-commonjs, babel-template
- #17284 fix(babel-template): Properly handle empty string replacements (@magic-akari)

🏃‍♀️ Performance

babel-cli
- #17285 Enable Node compile cache for @babel/cli (@JLHwung)

`v7.27.1`

Compare Source

👓 Spec Compliance

babel-parser
- #17254 Allow using of as lexical declaration within for (@JLHwung)
- #17230 Disallow get/set in TSPropertySignature (@JLHwung)
babel-parser, babel-types
- #17193 Stricter TSImportType options parsing (@JLHwung)

🐛 Bug Fix

babel-plugin-proposal-destructuring-private, babel-plugin-proposal-do-expressions, babel-traverse
- #17137 fix: do expressions should allow early exit (@kermanx)
babel-helper-wrap-function, babel-plugin-transform-async-to-generator
- #17251 Fix: propagate argument evaluation errors through async promise chain (@magic-akari)
babel-helper-remap-async-to-generator, babel-plugin-transform-async-to-generator
- #17231 fix apply()/call() annotated as pure (@Lacsw)
babel-helper-fixtures, babel-parser
- #17233 Create ChainExpression within TSInstantiationExpression (@JLHwung)
babel-generator, babel-parser
- #17226 Fill optional AST properties when both estree and typescript parser plugin are enabled (Part 2) (@JLHwung)
babel-parser
- #17224 Fill optional AST properties when both estree and typescript parser plugin are enabled (Part 1) (@JLHwung)
- #17080 Fix start of TSParameterProperty (@JLHwung)
babel-compat-data, babel-preset-env
- #17228 Update firefox bugfix compat data (@JLHwung)
babel-traverse
- #17156 fix: Objects and arrays with multiple references should not be evaluated (@liuxingbaoyu)
babel-generator
- #17216 Fix: support const type parameter in generator (@JLHwung)

💅 Polish

babel-plugin-bugfix-v8-spread-parameters-in-optional-chaining, babel-plugin-proposal-decorators, babel-plugin-transform-arrow-functions, babel-plugin-transform-class-properties, babel-plugin-transform-destructuring, babel-plugin-transform-object-rest-spread, babel-plugin-transform-optional-chaining, babel-plugin-transform-parameters, babel-traverse
- #17221 Reduce generated names size for the 10th-11th (@nicolo-ribaudo)

🏠 Internal

babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
- #17263 Remove unused regenerator-runtime dep in @babel/runtime (@nicolo-ribaudo)
babel-compat-data, babel-preset-env
- #17256 Tune plugin compat data (@JLHwung)
babel-compat-data, babel-standalone
- #17236 migrate babel-compat-data build script to mjs (@JLHwung)
Other
- #17232 Bump typescript-eslint to 8.29.1 (@JLHwung)
- #17219 test: add basic typescript-eslint integration tests (@JLHwung)
- #17205 Inline regenerator in the relevant packages (@nicolo-ribaudo)
babel-register
- #16844 Migrate @babel/register to cts (@liuxingbaoyu)
babel-cli, babel-compat-data, babel-core, babel-generator, babel-helper-compilation-targets, babel-helper-fixtures, babel-helper-module-imports, babel-helper-module-transforms, babel-helper-plugin-test-runner, babel-helper-transform-fixture-test-runner, babel-helpers, babel-node, babel-parser, babel-plugin-transform-modules-amd, babel-plugin-transform-modules-commonjs, babel-plugin-transform-modules-systemjs, babel-plugin-transform-modules-umd, babel-plugin-transform-react-display-name, babel-plugin-transform-regenerator, babel-plugin-transform-runtime, babel-plugin-transform-typeof-symbol, babel-plugin-transform-typescript, babel-preset-env, babel-register, babel-standalone, babel-types
- #17207 Enforce node protocol import (@JLHwung)
babel-plugin-transform-regenerator
- #17205 Inline regenerator in the relevant packages (@nicolo-ribaudo)
- #17205 Inline regenerator in the relevant packages (@nicolo-ribaudo)
babel-helpers, babel-plugin-transform-async-generator-functions, babel-plugin-transform-regenerator, babel-preset-env, babel-runtime-corejs3
- #17205 Inline regenerator in the relevant packages (@nicolo-ribaudo)
babel-helpers, babel-plugin-transform-regenerator
- #17205 Inline regenerator in the relevant packages (@nicolo-ribaudo)
- #17205 Inline regenerator in the relevant packages (@nicolo-ribaudo)
babel-helpers
- #17205 Inline regenerator in the relevant packages (@nicolo-ribaudo)

🔬 Output optimization

babel-helpers, babel-plugin-transform-modules-commonjs, babel-runtime-corejs3
- #16538 Reduce interopRequireWildcard size (@liuxingbaoyu)
babel-helpers, babel-plugin-transform-async-generator-functions, babel-plugin-transform-regenerator, babel-preset-env, babel-runtime-corejs3
- #17213 Reduce regeneratorRuntime size (@liuxingbaoyu)

`v7.27.0`

Compare Source

👓 Spec Compliance

babel-generator, babel-parser
- #16977 Default importAttributesKeyword to with (@JLHwung)

🚀 New Feature

babel-helper-create-class-features-plugin, babel-traverse, babel-types
- #17169 Allow traverseFast to exit early (@liuxingbaoyu)
babel-parser, babel-types
- #17110 Add ImportAttributes to Standardized and move its parser test fixtures (@JLHwung)
babel-generator
- #17100 fix(babel-generator): add named export of generate function (@vovkasm)
babel-parser, babel-template
- #17149 Add allowYieldOutsideFunction to parser (@liuxingbaoyu)
babel-plugin-transform-typescript, babel-traverse
- #17102 feat: Add upToScope parameter to hasBinding (@liuxingbaoyu)
babel-parser
- #17082 Support ESTree AccessorProperty (@JLHwung)
babel-types
- #17162 feat(babel-types): Add support for BigInt literal conversion in valueToNode (@ishchhabra)

🐛 Bug Fix

babel-helper-create-class-features-plugin, babel-plugin-transform-class-properties
- #16816 fix: Class reference in type throws error (@liuxingbaoyu)
babel-traverse
- #17170 fix: Reset child scopes when scope.crawl() (@liuxingbaoyu)
babel-helpers, babel-preset-typescript, babel-runtime-corejs2, babel-runtime-corejs3, babel-runtime
- #17118 Fix: align behaviour to tsc rewriteRelativeImportExtensions (@JLHwung)
babel-cli
- #17182 fix: @babel/cli generates duplicate inline source maps (@liuxingbaoyu)
babel-plugin-transform-named-capturing-groups-regex, babel-types
- #17175 Generate computed proto key (@JLHwung)

🏃‍♀️ Performance

babel-types
- #16870 perf: Improve builders of @babel/types (@liuxingbaoyu)
babel-helper-create-regexp-features-plugin
- #17176 fix: improve duplicate named groups check (@JLHwung)

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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

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

renovate · 2025-01-11T15:02:09Z

⚠️ 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: javascript/two-fer/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_21_187Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_21_187Z-debug-0.log

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

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (@babel/eslint-parser, eslint-plugin-import)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_23_954Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_23_954Z-debug-0.log

File name: javascript/simple-cipher/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_27_576Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_27_576Z-debug-0.log

File name: javascript/reverse-string/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_30_578Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_30_578Z-debug-0.log

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

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_33_484Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_33_484Z-debug-0.log

File name: javascript/nucleotide-count/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_35_532Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_35_532Z-debug-0.log

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

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_38_438Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_38_438Z-debug-0.log

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

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_41_269Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_41_269Z-debug-0.log

File name: javascript/collatz-conjecture/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_43_744Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_43_744Z-debug-0.log

File name: javascript/atbash-cipher/package-lock.json

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_46_608Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_46_608Z-debug-0.log

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

npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error   node_modules/@eslint-community/eslint-utils
npm error     @eslint-community/eslint-utils@"^4.2.0" from [email protected]
npm error   2 more (eslint-plugin-import, @babel/eslint-parser)
npm error
npm error Could not resolve dependency:
npm error peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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: [email protected]
npm error node_modules/eslint
npm error   peer eslint@"^7.32.0 || ^8.2.0" from [email protected]
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 /runner/cache/others/npm/_logs/2025-05-06T16_03_48_922Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-05-06T16_03_48_922Z-debug-0.log

socket-security · 2025-01-11T15:02:44Z

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	babel-plugin-transform-builtin-extend@1.1.2
	merge@2.1.1
	babel-preset-env@1.7.0
	eslint-config-airbnb-base@15.0.0

View full report

socket-security · 2025-01-11T15:02:46Z

Caution

Review the following alerts detected in dependencies.

According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.

Action	Severity	Alert (click for details)
Block		`[email protected]` has a Critical CVE. 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 From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is a critical CVE? Next steps: 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 `[email protected]`. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has a High CVE. CVE: GHSA-c2qf-rxjj-qqgw semver vulnerable to Regular Expression Denial of Service (HIGH) Affected versions: < 5.7.2 Patched version: 5.7.2 From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is a CVE? Next steps: 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 `[email protected]`. Suggestion: Remove or replace dependencies that include known high severity CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` is Deprecated. 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. From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is a deprecated package? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` Uses eval. Eval Type: Function Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is dynamic code execution? Next steps: 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 `[email protected]`. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` Uses eval. Eval Type: Function Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is dynamic code execution? Next steps: 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 `[email protected]`. Suggestion: Avoid packages that use dynamic code execution like eval(), since this could potentially execute any code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Shell access. Module: child_process Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/@babel/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is shell access? Next steps: 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 `[email protected]`. Suggestion: Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Environment variable access. Env Vars: NODE_ENV Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is environment variable access? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Environment variable access. Env Vars: DEBUG_FD Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is environment variable access? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Filesystem access. Module: fs Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is filesystem access? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Filesystem access. Module: fs Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is filesystem access? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Environment variable access. Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is environment variable access? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Environment variable access. Env Vars: key Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is environment variable access? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Filesystem access. Module: fs Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is filesystem access? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Debug access. Module: module Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is debug access? Next steps: 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 `[email protected]`. Suggestion: Removing the use of debug will reduce the risk of any reflection and dynamic code execution. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Block		`[email protected]` has Filesystem access. Module: fs Location: Package overview From: javascript/etl/package-lock.json → `npm/[email protected]` → `npm/[email protected]` → `npm/@babel/[email protected]` → `npm/[email protected]` ℹ Read more on: This package \| This alert \| What is filesystem access? Next steps: 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 `[email protected]`. Suggestion: 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. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment `@SocketSecurity ignore npm/[email protected]`. You can also ignore all packages with `@SocketSecurity ignore-all`. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

renovate bot force-pushed the renovate/babel-monorepo branch from 1e228ef to 48f38dc Compare January 18, 2025 16:47

renovate bot force-pushed the renovate/babel-monorepo branch from 48f38dc to 743c831 Compare January 26, 2025 09:25

renovate bot changed the title ~~Update dependency @babel/eslint-parser to v7.26.5~~ Update babel monorepo Jan 26, 2025

renovate bot force-pushed the renovate/babel-monorepo branch from 743c831 to 016197b Compare February 8, 2025 13:55

renovate bot changed the title ~~Update babel monorepo~~ Update babel monorepo to v7.26.8 Feb 8, 2025

renovate bot force-pushed the renovate/babel-monorepo branch 2 times, most recently from a1e5ae2 to b2949a7 Compare February 14, 2025 15:03

renovate bot changed the title ~~Update babel monorepo to v7.26.8~~ Update babel monorepo Feb 14, 2025

renovate bot force-pushed the renovate/babel-monorepo branch from b2949a7 to f4bf234 Compare March 1, 2025 22:27

renovate bot force-pushed the renovate/babel-monorepo branch from f4bf234 to fb2918c Compare March 11, 2025 19:14

renovate bot force-pushed the renovate/babel-monorepo branch from fb2918c to 833b43a Compare March 24, 2025 23:16

renovate bot force-pushed the renovate/babel-monorepo branch from 833b43a to d06e7ba Compare April 30, 2025 16:04

renovate bot changed the title ~~Update babel monorepo~~ Update babel monorepo to v7.27.1 Apr 30, 2025

Update babel monorepo

22a65ef

renovate bot force-pushed the renovate/babel-monorepo branch from d06e7ba to 22a65ef Compare May 6, 2025 16:03

renovate bot changed the title ~~Update babel monorepo to v7.27.1~~ Update babel monorepo May 6, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update babel monorepo #1036

Update babel monorepo #1036

renovate bot commented Jan 11, 2025 •

edited

Loading

renovate bot commented Jan 11, 2025 •

edited

Loading

socket-security bot commented Jan 11, 2025 •

edited

Loading

socket-security bot commented Jan 11, 2025 •

edited

Loading

Update babel monorepo #1036

Are you sure you want to change the base?

Update babel monorepo #1036

Conversation

renovate bot commented Jan 11, 2025 • edited Loading

Release Notes

v7.27.2

🐛 Bug Fix

🏃‍♀️ Performance

v7.27.1

👓 Spec Compliance

🐛 Bug Fix

💅 Polish

🏠 Internal

🔬 Output optimization

v7.27.0

👓 Spec Compliance

🚀 New Feature

🐛 Bug Fix

🏃‍♀️ Performance

Configuration

renovate bot commented Jan 11, 2025 • edited Loading

⚠️ Artifact update problem

File name: javascript/two-fer/package-lock.json

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

File name: javascript/simple-cipher/package-lock.json

File name: javascript/reverse-string/package-lock.json

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

File name: javascript/nucleotide-count/package-lock.json

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

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

File name: javascript/collatz-conjecture/package-lock.json

File name: javascript/atbash-cipher/package-lock.json

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

socket-security bot commented Jan 11, 2025 • edited Loading

socket-security bot commented Jan 11, 2025 • edited Loading

renovate bot commented Jan 11, 2025 •

edited

Loading

`v7.27.2`

`v7.27.1`

`v7.27.0`

renovate bot commented Jan 11, 2025 •

edited

Loading

socket-security bot commented Jan 11, 2025 •

edited

Loading

socket-security bot commented Jan 11, 2025 •

edited

Loading