Split out test dependencies

Aperta
#285 3 commenti 0 reazioni 1 assegnatario Vedi su GitHub

@arbrandes ci sta già lavorando.

Dal 28/8/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

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.

Lingua principale
TypeScript
Stelle
4
Fork
13
Merge medio
3g 5h
PR unite (30g)
4

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di openedx/frontend-base

Tutte le issue di openedx/frontend-base

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.