Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Chunk optimizer drops a chunk shared between the main bundle and a web worker

Ouverte
  • Quelque chose ne va pas ?
#34,292 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
Active
Stack technique
typescript
Domaine
build-system, frontend

Piste de recherche

Start with the reproduction repo and run NG_BUILD_OPTIMIZE_CHUNKS=false against it to confirm the baseline, then look at bundleWebWorker in compiler-plugin.js and the chunk optimizer that runs over the main bundle. Done means that sh check-missing-chunks.sh reports nothing missing with the optimizer enabled, and that the worker's shared chunk still exists in dist. The issue leaves open whether to exclude worker-referenced chunks from removal or to optimize worker outputs with the main bundle, so the design choice needs a maintainer.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area: @angular/build
Command

build

Is this a regression?
  • Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was

No response

Description

When a web worker and the main application dynamically import the same modules, and those modules share a dependency, the production build emits worker chunks that import a chunk that is not written to the output directory.

The worker is bundled separately (bundleWebWorker in compiler-plugin.js) with the same chunk-[hash] naming as the main bundle. Because the content is identical, the worker's shared chunk gets the same file name as a chunk of the main bundle. The chunk optimizer then rewrites the main bundle's chunks with Rolldown and the original esbuild chunk is no longer emitted. The worker chunks still reference it, so the file is missing from dist.

At runtime, the worker's dynamic import requests a chunk that returns 404 on the server.

With NG_BUILD_OPTIMIZE_CHUNKS=false every referenced chunk is emitted and the worker works.

Real-world case: a report worker that lazily loads jspdf and write-excel-file, which both depend on fflate. The fflate chunk was missing, so PDF and XLSX generation in the worker failed in production only.

Minimal Reproduction

Repository: https://github.com/jsandrea88/worker-chunk-repro

  1. pnpm install
  2. pnpm exec ng build
  3. sh check-missing-chunks.sh. This lists every ./chunk-*.js import in dist/**/browser that has no matching file.

Output:

MISSING: chunk-46XWIMCN.js imports chunk-I4HABNO6.js
MISSING: chunk-HAJXH3QZ.js imports chunk-I4HABNO6.js
  1. NG_BUILD_OPTIMIZE_CHUNKS=false pnpm exec ng build followed by sh check-missing-chunks.sh reports nothing missing.

Code:

// zip-a.ts
import { zipSync } from 'fflate';
export const zipA = () => zipSync({ 'a.txt': new Uint8Array([97]) });

// zip-b.ts
import { unzipSync, zipSync } from 'fflate';
export const zipB = () => unzipSync(zipSync({ 'b.txt': new Uint8Array([98]) }));

// zip.worker.ts
addEventListener('message', async () => {
  const [{ zipA }, { zipB }] = await Promise.all([import('./zip-a'), import('./zip-b')]);
  postMessage(`${zipA().length} ${Object.keys(zipB()).length}`);
});

// app.ts (main bundle): dynamic imports of the same modules, plus a third lazy
// chunk to reach the default optimization threshold of 3 lazy chunks
await Promise.all([import('./zip-a'), import('./zip-b'), import('./lazy-c')]);
new Worker(new URL('./zip.worker', import.meta.url), { type: 'module' });

If the worker imports fflate directly, without the two shared intermediate modules, the problem does not reproduce.

Exception or Error
No build error. The output contains chunks that import a file that does not exist (see the reproduction output). In the browser, the worker's dynamic import fails with a 404 for that chunk.
Your Environment
Angular CLI       : 22.2.2
Angular           : 22.2.1
Node.js           : 24.18.1
Package Manager   : pnpm 11.5.3
Operating System  : win32 x64

@angular/build            22.2.2
@angular/cli              22.2.2
@angular/core             22.2.1
typescript                6.0.3
Anything else relevant?

Workaround: NG_BUILD_OPTIMIZE_CHUNKS=false.

Possible fixes: exclude chunks referenced by web worker outputs from the optimizer's removal, or run the optimizer over the worker outputs together with the main bundle.

Regression status: not bisected. The chunk optimizer has been enabled by default since 22.0.0 (cd2ad3c19), so I expect builds before that to be unaffected, but I have not verified it.

Langage dominant
TypeScript
Étoiles
27k
Forks
11.8k
Merge moyen
1 j 32 min
PR mergées (30 j)
138

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de angular/angular-cli

Toutes les issues de angular/angular-cli

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.