Split out test dependencies

未关闭
#285 3 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

@arbrandes 已经在做这个了。

开始于 2026年8月28日。

评估

这个 Issue 还没有评估数据。

描述

As we discussed and put into OEP-67:

To keep installation and deployment of our MFEs as fast as possible, the “dependencies” field in package.json should reference only the packages needed to build the bundle of the MFE (this includes webpack via frontend-build, as well as any dependencies used in the actual MFE/React code). Any dependencies used only for testing, linting, formatting, or other development tasks should be put into “devDependencies” (e.g. Jest, eslint, TypeScript, @types/ packages, etc.).

However, this repo currently has almost all its dependencies, including the huge jest test runner ecosystem, in dependencies.

If this is just an oversight, things like jest, estlint, react-refresh, webpack-bundle-analyzer, etc. should be moved into devDependencies.

If this is because we want that tooling installed for use by consuming MFEs, I think those should be moved into a separate frontend-testing package, or even better, a frontend-testing sub-package within this same repository.

主要语言
TypeScript
星标
4
派生
13
平均合并
3 天 5 小时
30 天内合并 PR
4

环境准备

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

从这里开始

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

openedx/frontend-base 的其他 Issue

查看 openedx/frontend-base 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

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