Skip to content

feat(deps): Upgrade babel dependencies#33

Merged
scttcper merged 1 commit intomainfrom
scttcper/upgrade-babel
Feb 10, 2026
Merged

feat(deps): Upgrade babel dependencies#33
scttcper merged 1 commit intomainfrom
scttcper/upgrade-babel

Conversation

@scttcper
Copy link
Copy Markdown
Member

@scttcper scttcper commented Feb 10, 2026

silence security warning about babel regen runtime

fixes https://linear.app/getsentry/issue/CORE-140

silence security warning about babel regen runtime
@scttcper scttcper changed the title deps: Upgrade babel dependencies feat(deps): Upgrade babel dependencies Feb 10, 2026
@linear
Copy link
Copy Markdown

linear bot commented Feb 10, 2026

"@typescript-eslint/parser": "^4.4.1",
"autoprefixer": "^10.4.8",
"babel-loader": "^8.2.5",
"babel-loader": "^10.0.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Bug: The engines field in package.json is incompatible with the new babel-loader dependency, requiring Node.js >=18.20.0 but stating >=14.0.0, which will break local builds for some developers.
Severity: MEDIUM

Suggested Fix

Update the engines.node field in package.json to ">=18.20.0" to match the minimum version required by the updated babel-loader dependency and ensure a consistent development environment.

Prompt for AI Agent
Review the code at the location below. A potential bug has been identified by an AI
agent.
Verify if this is a real issue. If it is, propose a fix; if not, explain why it's not
valid.

Location: package.json#L69

Potential issue: The `package.json` file specifies a Node.js engine requirement of
`>=14.0.0`. However, this change upgrades the `babel-loader` dependency to version
`10.0.0`, which requires a newer Node.js version (`^18.20.0 || ^20.10.0 || >=22.0.0`).
This mismatch will cause build failures for developers running Node.js versions between
14.0.0 and 18.19.0. While CI may pass because it uses a compatible Node.js version,
local development environments that adhere to the documented engine requirement will
fail during the build step when `babel-loader` is executed.

Did we get this right? 👍 / 👎 to inform future reviews.

@scttcper scttcper merged commit e7b0dca into main Feb 10, 2026
7 checks passed
@scttcper scttcper deleted the scttcper/upgrade-babel branch February 10, 2026 00:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants