Skip to content

chore(deps-dev): keep esign-react's @babel/preset-react on Babel 7 - #119

Merged
blink-admin merged 1 commit into
mainfrom
fix/react-babel-7
Sep 30, 2026
Merged

blink-admin merged 1 commit into
mainfrom
fix/react-babel-7

Conversation

@grimen

@grimen grimen commented Sep 30, 2026

Copy link
Copy Markdown
Collaborator

Unblocks #114 (npm-minor-patch group), where every packages/esign-react suite fails Unit / Coverage with:

[BABEL] packages/esign-react/jest.setup.ts: Requires Babel "^7.0.0-0", but was loaded with "8.0.1".
(While processing: node_modules/@babel/preset-env/lib/index.js)

Why

#11 moved esign-react's @babel/preset-react to 8 while its preset-env and preset-typescript stayed on 7. The @babel/* major ignore in dependabot.yml arrived later. That nests @babel/core@8.0.1 in packages/esign-react/node_modules.

main only works because jest and babel-jest are hoisted to the root, where they resolve the root @babel/core@7.29.7. #114's jest 30.5.1 → 30.5.2 changes that: npm nests jest and babel-jest per workspace, so in esign-react babel-jest picks up core 8, and preset-env 7 refuses it.

What this does

Puts @babel/preset-react back on ^7.29.7 and relocks. There is now one @babel/core (7.29.7) in the tree. The existing @babel/* major ignore keeps it from drifting again.

Verification

#114 also needs #118: its vitest bump alone hits ERESOLVE against coverage-v8 4.

#11 moved preset-react to 8 while preset-env and preset-typescript stayed
on 7 (the @babel/* major ignore in dependabot.yml came later). That nests
@babel/core 8 in packages/esign-react; main only works because babel-jest
is hoisted and resolves the root core 7. Once jest is nested per workspace
(the jest 30.5.2 bump in #114), babel-jest picks up core 8 and preset-env 7
refuses it: every esign-react suite fails with "Requires Babel ^7.0.0-0".
@blink-admin
blink-admin merged commit e811677 into main Sep 30, 2026
16 of 17 checks passed
@blink-admin
blink-admin deleted the fix/react-babel-7 branch September 30, 2026 20:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants