Upgrade Babel to 8

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

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

调研方向

Start with babel.config.js, which re-exports kolibri-build/babel.config and sets useBuiltIns, then check the peer ranges in pnpm-lock.yaml and jest_config/jest.conf.js. Done means pnpm install resolves one @babel/core major, pnpm build and pnpm test pass, and the CI frontend jobs are green. The issue states it is not open for contribution, so confirm with maintainers before starting.

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

描述

dependencies DEV: frontend

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

Dependabot PR #6013 bumped @babel/core 7.29.6 → 8.0.9, @babel/preset-env 7.29.5 → 8.0.7, @babel/plugin-transform-runtime 7.29.0 → 8.0.6 and @babel/plugin-syntax-import-assertions 7.28.6 → 7.29.7. It was closed unmerged because every webpack build and Jest run failed. Babel 8 removes preset-env's useBuiltIns, which our shared config still sets, and several build and test packages only accept Babel 7.

Complexity: Medium
Target branch: unstable

Context
  • babel.config.js re-exports kolibri-build/babel.config, which sets useBuiltIns. On #6013 both "Build frontend assets" and "Frontend tests" fail with: 
    The 'useBuiltIns' option has been removed
  • kolibri-build 1.0.0 depends on its own @babel/core 7.29.7, preset-env 7.29.7, plugin-transform-runtime 7.29.7 and babel-loader 10.1.1. With #6013 applied, two Babel cores load: webpack's babel-loader runs on 7.29.7 while the root preset-env 8.0.7 expects 8.x.
  • Packages whose peer range rejects @babel/core 8, per pnpm-lock.yaml:
    • babel-jest 29.7.0 (^7.8.0); 30.x accepts ^8.0.0-0
    • @vue/vue2-jest 29.2.6 (@babel/core: 7.x, babel-jest: 29.x), used for .vue files in jest_config/jest.conf.js
    • babel-core 7.0.0-bridge.0 (^7.0.0-0)
  • Other Babel 8 breaking changes to check: modules: "auto" now assumes ESM support, and @babel/runtime-corejs3 no longer has corejs exports.
The Change
  • Polyfill injection should move from useBuiltIns to babel-plugin-polyfill-corejs3, the replacement Babel 8 names, either in kolibri-build or overridden in Studio's babel.config.js.
  • These must move to Babel 8 together, since each one's Babel 7 copy or peer range breaks the others: @babel/core, @babel/preset-env, @babel/plugin-transform-runtime, kolibri-build's Babel dependencies, babel-jest, @vue/vue2-jest, and babel-core (bridge), the last removed if nothing still needs it.
  • @babel/plugin-syntax-import-assertions 7.29.7 is a minor bump and can land on its own.
Acceptance Criteria
  • pnpm install resolves a single @babel/core major, with no unmet Babel peer warnings
  • pnpm build succeeds, and the production bundle still includes the core-js polyfills it ships today for the browserslist targets
  • pnpm test passes, including .vue component specs
  • CI "Build frontend assets" and "Frontend tests" pass

AI usage

rtibblesbot (Claude Code) reviewed #6013, read its CI logs and the lockfile peer ranges, and drafted this issue.

Filed from #6013's review.

主要语言
Python
星标
211
派生
317
平均合并
4 天 2 小时
30 天内合并 PR
23

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

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

learningequality/studio 的其他 Issue

查看 learningequality/studio 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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