[lskramarov]

Summary

Both ng add @koobiq/components and ng update to 21 are broken in the published 21.0.0: the schematics in dist/components/schematics fail to load, for two independent reasons.

1. Shared chunks are not shipped. Rollup puts every util imported by several entries without an entry of its own into a hashed chunk at the root of packages/schematics/dist (package-config-*.js, replacement-driver-*.js, signal-members-migration-*.js, …). copy-meta-to-dist.js copies only ng-add/, migrations/ and utils/, so ng-add, two util facades and all 88 migrations require a file that is not in the package (MODULE_NOT_FOUND).
2. CommonJS in an ESM package. ng-packagr 21 writes "type": "module" into dist/components/package.json (packageJson.type ??= 'module'). The schematics are CommonJS .js, so Node loads them as ES modules and fails with exports is not defined in ES module scope. This error hides the first one: fixing only the module type still leaves MODULE_NOT_FOUND.

List of notable changes:

• updated rollup.config.js: the build emits .cjs, which Node loads as CommonJS whatever the package type (as @angular/core ships its schematics). Every src/utils/*.ts except specs, .d.ts and testing.ts is an entry of its own; any other module shared by several entries goes into utils/[name]-[hash].cjs. The build fails when shipped code imports test tooling (vitest, */testing).
• updated copy-meta-to-dist.js: starts from an empty dist/components/schematics, copies the .cjs modules and writes collection.json / migrations.json with .cjs factories (require.resolve() does not try .cjs; the sources stay extension-less for the specs).
• added scripts/check-dist.mjs, run at the end of build:schematics: no .js module ships; every require() / import() (read from the syntax tree) names a file of the package or a package consumers have — non-optional peers, tslib, @angular-devkit/schematics, @schematics/angular, @angular/compiler, typescript — and resolves, import() with the ESM conditions; the collections are found through the manifest's schematics and ng-update.migrations, every factory loads with a plain require() (as ExportStringRef does) and exports a function, every schema parses.
• updated tools/check-npm-resolution: packs with --json and fails when the tarball leaves out a file of schematics/.

What should reviewers focus on?

• build:schematics relies on build:components having run first (the copy step writes into dist/components); build-packages already runs them in that order.
• Verified: the check fails on each regression put back (a .js module, a package consumers lack, a missing util, a factory-less entry, a broken schema); require('…') inside strings and comments is ignored; a stale migration directory is removed by the copy step; rollup rejects a util that imports @angular-devkit/schematics/testing and ignores a .d.ts; a module shared by two migrations ships as utils/<name>-<hash>.cjs; check-npm-resolution fails when .npmignore drops a schematics file. A tarball from npm pack of the fixed dist/components runs ng-add and all 82 ng update migrations through SchematicTestRunner; the published 21.0.0 fails on every one.
• 20.4.x, 20.3.x, 19.x and 18.x are not affected (ng-packagr < 21 sets no type, and every util there has an entry), so there are no backports.
• The 21.0.0 release needs a follow-up patch release.

[github-actions]

Visit the preview URL for this PR (updated for commit 8443fe5):

https://koobiq-next--prs-2262-d8zqm75w.web.app

_{(expires Fri, 30 Oct 2026 18:57:44 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: c9e37e518febda70d0317d07e8ceb35ac43c534c}