Skip to content

bug: Angular starters updated to current version do not start #136

Open

Description

@michael-small

Steps

  • Create new Stackblitz Angular starter
  • ng update @angular/cli @angular/core to get to the latest version (22.2.3)
  • Start project with the standard starter npm install && npm start
  • I did the trick at the end of the console error about the npm binding bug. Did not work.

edit: additional reproduction: open an Angular Material example project, which are set to 22.2.0: https://material.angular.dev/components/badge/examples. I used them the other day and it was not a problem, same for other frozen projects of mine which worked recently

Here is a repro after being updated, and the output of the console: https://stackblitz.com/edit/stackblitz-starters-ki4mfjac?file=package.json

~/projects/stackblitz-starters-ki4mfjac
❯ npm install && npm start

added 276 packages in 2s

75 packages are looking for funding
  run `npm fund` for details
 
> start
> ng serve

Prebundling has been configured but will not be used because caching has been disabled.
[rolldown] Downloading @rolldown/binding-wasm32-wasi@1.2.8 on WebContainer...
Progress: resolved 1, reused 0, downloaded 0, added 0
Packages: +7
+++++++
Packages: +7
+++++++
Progress: resolved 7, reused 0, downloaded 7, added 7, done

dependencies:
+ @oxc-parser/binding-wasm32-wasi 0.150.0 (0.155.0 is available)

 WARN  Issues with peer dependencies found
.
└─┬ @oxc-parser/binding-wasm32-wasi 0.150.0
  └─┬ @napi-rs/wasm-runtime 1.2.6
    ├── ✕ unmet peer @emnapi/core@"^1.7.1 || 2.0.0-beta.2": found 2.0.0-alpha.3 in @oxc-parser/binding-wasm32-wasi
    └── ✕ unmet peer @emnapi/runtime@"^1.7.1 || 2.0.0-beta.2": found 2.0.0-alpha.3 in @oxc-parser/binding-wasm32-wasi

Progress: resolved 7, reused 0, downloaded 7, added 7, done

dependencies:
+ @rolldown/binding-wasm32-wasi 1.2.8 (1.2.15 is available)

 WARN  Issues with peer dependencies found
.
└─┬ @rolldown/binding-wasm32-wasi 1.2.8
  └─┬ @napi-rs/wasm-runtime 1.2.6
    ├── ✕ unmet peer @emnapi/core@"^1.7.1 || 2.0.0-beta.2": found 2.0.0-alpha.4 in @rolldown/binding-wasm32-wasi
    └── ✕ unmet peer @emnapi/runtime@"^1.7.1 || 2.0.0-beta.2": found 2.0.0-alpha.4 in @rolldown/binding-wasm32-wasi

Done in 6.6s
An unhandled exception occurred: Cannot find native binding. npm has a bug related to optional dependencies (https://github.com/npm/cli/issues/4828). Please try `npm i` again after removing both package-lock.json and node_modules directory.
See "/tmp/ng-xXIaRk/angular-errors.log" for further details.
(node:12) ExperimentalWarning: WASI is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
[oxc-parser] Downloading @oxc-parser/binding-wasm32-wasi@0.150.0 on WebContainer...
Error [ERR_REQUIRE_CYCLE_MODULE]: Cannot require() ES Module /home/projects/stackblitz-starters-ki4mfjac/node_modules/oxc-parser/src-js/index.js in a cycle. (from /home/projects/stackblitz-starters-ki4mfjac/node_modules/@angular/build/src/tools/oxc/oxc-transform.js) A cycle involving require(esm) is not allowed to maintain invariants mandated by the ECMAScript specification. Try making at least part of the dependency in the graph lazily loaded.
    at ModuleLoader.importSyncForRequire (node:internal/modules/esm/loader:169:3960)
    at loadESMFromCJS (node:internal/modules/cjs/loader:160:19002)
    at Module._compile (node:internal/modules/cjs/loader:160:19068)
    at Module._extensions..js (node:internal/modules/cjs/loader:160:20043)
    at Module.load (node:internal/modules/cjs/loader:160:17661)
    at Module._load (node:internal/modules/cjs/loader:160:15179)
    at wrapModuleLoad (node:internal/modules/cjs/loader:160:4199)
    at Module.require (node:internal/modules/cjs/loader:160:17842)
    at require2 (node:internal/modules/helpers:177:3126) {
  code: 'ERR_REQUIRE_CYCLE_MODULE'
}

Node.js v22.22.3

Activity

  1. bolt-new-by-stackblitz commented on Oct 25, 2026

    @bolt-new-by-stackblitz
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions