Pewarta Proxy

📋 Server Request & Proxy Logs

Loading active proxy settings...
Developed by Khairul Adha (adhexa.id)
Mengambil log server...

⚙️ Pengaturan Proxy Target

Skip to content

build: ERR_REQUIRE_CYCLE_MODULE when loading oxc-parser in StackBlitz / WebContainer #34524

Open
#34551
Open
build: ERR_REQUIRE_CYCLE_MODULE when loading oxc-parser in StackBlitz / WebContainer#34524
#34551
Labels
area: @angular/build
Milestone
needsTriage

Description

@JeanMeche
JeanMeche
opened on Oct 25, 2026

Command

build, serve

Is this a regression?

Yes, this behavior used to work in the previous version

Description

In StackBlitz (WebContainer), running an Angular application with @angular/build fails during ng serve / ng build with:

(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'
}

Parent issue: stackblitz/starters#136

Analysis & Root Cause

  1. No actual cyclic dependency in the code:
    The module graph (oxc-transform.ts -> oxc-parser, oxc-transform.ts -> traversal.ts -> oxc-parser) is an acyclic DAG.
    The ERR_REQUIRE_CYCLE_MODULE error is a known misleading error in Node.js's synchronous require(esm) loader (Node.js issues #55516 and #57172). When an ES module throws an error during synchronous require(esm) evaluation, Node's loader frequently shadows the real underlying exception and reports that the module was required in a cycle.

  2. WebContainer Fallback Failure:

    • StackBlitz WebContainer cannot run native .node addons.
    • oxc-parser's optionalDependencies only list platform-specific native addons (@oxc-parser/binding-linux-x64-gnu, etc.) and do not list @oxc-parser/binding-wasm32-wasi. Consequently, package managers running in WebContainer never install the WASI binding.
    • At runtime, oxc-parser/src-js/bindings.js detects WebContainer and falls back to webcontainer-fallback.cjs, which attempts to run childProcess.execFileSync("pnpm", ["i", "@oxc-parser/binding-wasm32-wasi@..."], { cwd: "/tmp/..." }).
    • Running this synchronous subprocess from a worker thread inside WebContainer fails (or fails to initialize the multi-threaded WASI runtime), causing the synchronous require(esm) evaluation of oxc-parser to fail and surface as ERR_REQUIRE_CYCLE_MODULE.

Proposed Solution (Option 4A: Add @oxc-parser/binding-wasm32-wasi to @angular/build optionalDependencies)

In oxc-parser/src-js/bindings.js, before falling back to webcontainer-fallback.cjs, it checks:

__napiWasiResolveCandidate('@oxc-parser/binding-wasm32-wasi', true, undefined)

If @oxc-parser/binding-wasm32-wasi is already present in node_modules, oxc-parser directly loads it and bypasses webcontainer-fallback.cjs and the dynamic pnpm i in /tmp entirely.

A viable solution (Option 4A) is to declare @oxc-parser/binding-wasm32-wasi in @angular/build's optionalDependencies (similar to how lmdb is declared).
This ensures that package managers install the WASI binding up-front alongside @angular/build, preventing the runtime dynamic installation and the resulting failure in WebContainer.

Minimal Reproduction

  1. Open https://stackblitz.com/edit/stackblitz-starters-ki4mfjac?file=package.json (or update any StackBlitz Angular starter to Angular CLI v22.2+).
  2. Run npm install && npm start (or ng serve).
  3. Notice the build fails with ERR_REQUIRE_CYCLE_MODULE: Cannot require() ES Module .../oxc-parser/src-js/index.js in a cycle.

Exception or Error

(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

Your Environment

Angular CLI: 22.2.3
Node: 22.22.3 (WebContainer)
OS: linux x64 (WebContainer)

Anything else relevant?

Parent issue: stackblitz/starters#136

Activity

  1. angular-robot
    added
    area: @angular/build
    on Oct 25, 2026
  2. angular-robot
    added this to the needsTriage milestone on Oct 25, 2026

  3. mrotteveel commented on Oct 27, 2026

    @mrotteveel
    mrotteveel
    on Oct 27, 2026

    This issue also affects https://angular.dev/playground and the various tutorials on https://angular.dev/tutorials

  4. alan-agius4
    added a commit that references this issue on Oct 27, 2026

    fix(@angular/build): include the oxc-parser WASI binding as an option…

    f25cdbe
  5. alan-agius4
    linked a pull request that will close this issuefix(@angular/build): include the oxc-parser WASI binding as an optional dependency #34551on Oct 28, 2026
  6. alan-agius4
    added a commit that references this issue on Oct 28, 2026

    fix(@angular/build): include the oxc-parser WASI binding as an option…

    6298fb8
  7. alan-agius4
    closed this as completedon Oct 28, 2026

  8. msmallest commented on Oct 29, 2026

    @msmallest
    msmallest
    on Oct 29, 2026

    Is there any other related packages that projects embedded in web containers need to bump along with this change in 22.2.5?

    I forked a Material example with ^ v22.2 deps and had the same error. I then set them all to their exact versions without ^ and used the CLI 22.2.5 version with this fix. I still have the same problem in Stackblitz: https://stackblitz.com/edit/rsoem61h?file=package.json

    The adev playground still has the same problem too https://angular.dev/playground?templateId=0-hello-world, but I think that just needs to be bumped to 22.2.5 in the CLI: https://github.com/angular/angular/blob/main/adev/package.json

  9. JeanMeche
    reopened this on Oct 29, 2026

  10. JeanMeche commented on Oct 29, 2026

    @JeanMeche
    JeanMeche
    on Oct 29, 2026
    MemberAuthor

    Renovate already took care of bumping the versions. Looks like the issue still isn't fixed.

  11. alan-agius4 commented on Oct 29, 2026

    @alan-agius4
    alan-agius4
    on Oct 29, 2026
    Collaborator

    @JeanMeche not quite, since the versions in the examples/playground https://github.com/angular/angular/blob/main/adev/src/content/tutorials/playground/common/package.json are not pinned the new version will only get consumed when there is a lock-file update.

    angular/angular#71732 should do it.

  12. alan-agius4 commented on Oct 29, 2026

    @alan-agius4
    alan-agius4
    on Oct 29, 2026
    Collaborator

    Looks like it still didn't solve it https://ng-dev-previews-fw--pr-angular-angular-71732-adev-prev-2oicbcjm.web.app/playground?templateId=0-hello-world

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

    area: @angular/build

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions