Skip to content

Commit 14bdb28

Browse files
devversionclydin
authored andcommitted
test: update chunk file name to reflect new name
It seems that the chunk deterministic name has changed after recent node module /lock file changes. It's unclear what specifically is involved in Webpack's chunk name generation, but the output and all other tests still look good; which makes this is a rather safe update to the new chunk name. Consulting with CLI team members explained that this can happen quite often.
1 parent b3e3c85 commit 14bdb28

File tree

1 file changed

+1
-2
lines changed

1 file changed

+1
-2
lines changed

packages/angular_devkit/build_angular/src/builders/browser/tests/options/named-chunks_spec.ts

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ import { BASE_OPTIONS, BROWSER_BUILDER_INFO, describeBuilder } from '../setup';
1111

1212
const MAIN_OUTPUT = 'dist/main.js';
1313
const NAMED_LAZY_OUTPUT = 'dist/src_lazy-module_ts.js';
14-
const UNNAMED_LAZY_OUTPUT = 'dist/358.js';
14+
const UNNAMED_LAZY_OUTPUT = 'dist/414.js';
1515

1616
describeBuilder(buildWebpackBrowser, BROWSER_BUILDER_INFO, (harness) => {
1717
describe('Option: "namedChunks"', () => {
@@ -61,7 +61,6 @@ describeBuilder(buildWebpackBrowser, BROWSER_BUILDER_INFO, (harness) => {
6161
const { result } = await harness.executeOnce();
6262

6363
expect(result?.success).toBe(true);
64-
debugger;
6564
harness.expectFile(MAIN_OUTPUT).toExist();
6665
harness.expectFile(NAMED_LAZY_OUTPUT).toNotExist();
6766
harness.expectFile(UNNAMED_LAZY_OUTPUT).toExist();

0 commit comments

Comments
 (0)