Upgrade Babel to 8 together with Jest's Babel deps (#7252)

未关闭
  • 哪里不对？
#7,277 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
52/100
Issue 类型
重构
描述清晰度
基本清楚
活跃度
活跃
技术栈
javascript, nodejs
领域
testing-qa, tooling

调研方向

Start by checking whether the Jest/Babel versions in the project’s dependency files support Babel 8, then read babel.config.js and .github/dependabot.yml. Follow the applicable task path: coordinate compatible dependency upgrades and run npm run test, or configure Dependabot’s ignore rule and close #7252 if support is unavailable. Done means the selected path is implemented and the test-toolchain install issue is addressed.

由索引模型根据 Issue 内容生成。

描述

dependencies Difficulty: Intermediate Help Wanted javascript 🧪 Tests

Problem

Dependabot's #7252 bumps @babel/core from 7.29.7 to 8.0.7. It fails npm_lint, rspec and docker at npm install with ERESOLVE, before any test runs:

babel-jest@"30.5.1" from [email protected]
dev @babel/preset-env@"^7.29.7" from the root project

babel-jest (Jest 30) and @babel/preset-env@^7 both need @babel/core 7, so @babel/core can't move to 8 by itself.

Context

  • Babel is only used for Jest (babel.config.js; npm run test). The app's JS is bundled by ESBuild (bin/asset_bundling_scripts/build_js.js), which doesn't use Babel. So this only affects the test toolchain, never production code.

Tasks

  • Find out whether babel-jest / Jest and @babel/preset-env have releases that support Babel 8 yet
  • If yes: one PR bumping @babel/core, @babel/preset-env and babel-jest/Jest together. Check babel.config.js against the Babel 8 migration guide, and make sure npm run test passes.
  • If no: add an ignore for @babel/* major versions to the npm entry in .github/dependabot.yml (with a comment linking this issue), and close #7252
  • Optional: try whether Jest can drop Babel entirely, e.g. via a native ESM or ESBuild-based transform

Difficulty: intermediate. Good for someone who likes JS tooling.

主要语言
Ruby
星标
382
派生
547
平均合并
2 天 22 小时
30 天内合并 PR
46

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue，再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库，在一个分支上完成修改。
  4. 提交 Pull Request，并在描述里引用这个 Issue 编号。

rubyforgood/casa 的其他 Issue

查看 rubyforgood/casa 的全部 Issue

相似的 Issue

更多 Ruby Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。