Split out test dependencies

Abierto
#285 3 comentarios 0 reacciones 1 asignado Ver en GitHub

@arbrandes ya está trabajando en esto.

Desde el 28/8/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
4
Forks
13
Merge medio
3 d 5 h
PR fusionados (30 d)
4

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de openedx/frontend-base

Todos los issues de openedx/frontend-base

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.