Native Federation on Windows - frequent issues with @oxc-parser/binding-win32-x64-msvc

[OldShaterhan]

With what library do you have an issue?

native-federation

Reproduction of the bug/regression with instructions

I noticed on Windows, that running npm i does not install @oxc-parser/binding-win32-x64-msvc, hovewer when I try to run app, I'm getting

 ERRR  Error building federation artefacts
 ERRR  Cannot find module '@oxc-parser/binding-win32-x64-msvc'
Require stack:
- <repo_path>\node_modules\oxc-parser\index.js

It shows on A21.

Expected behavior

Builds & npm install work properly on Windows environment.

Versions of Native/Module Federation, Angular, Node, Browser, and operating system

Native: 21.2.3
Angular: 21.2.x
Node: 24.13.0
OS: Windows 11

Other information

No response

I would be willing to submit a PR to fix this issue

• Yes
• No

[nlegncn]

I encountered the same issue yesterday. And it's blocking me a lot right now. What should we do? @manfredsteyer

[OldShaterhan]

At this point I'm basically having a copy of that in separate directory and I'm copying in to node_modules, but any npm install basically removes it from there.

[nlegncn]

I added as optionalDependencies like:

npm install @oxc-parser/binding-win32-x64-msvc --save-optional

but still I can not build my project with angular 21 update because of other issues. But you can use maybe with temp solution

[OldShaterhan]

This one nuxt/nuxt#33480 looks a bit similar?

[lmoesch]

Same problem here - have to install it manually on every windows dev environment but cannot add it to the main package.json since this would obv. break linux builds

[OldShaterhan]

@lmoesch I may be wrong, but this package probably has OS set, so it probably would install only on Windows if it would be in optionalDependencies in package.json, that's what my Copilot & Gemini suggested, but I haven't tested it yet.

Nevertheless, it should be covered on the lower level than our apps.

[PCASME]

Same issue here using Angular version 21.2.9 and @angular-architects/native-federation version 21.2.3.

I don't know if it will shed any light, but I was using pnpm to install dependencies with no problem but had need to change to npm due to internal requirements and now have the issue when build the project.

The strange thing is that I have several projects with the same setup and this wasn't happening a few days ago.

[Aukevanoost]

Hi all!
What npm/pnpm version's are you using? I read on the oxc-parser issues that this might be a specific npm version bug?
oxc-project/oxc#14598

[OldShaterhan]

Hi all! What npm/pnpm version's are you using? I read on the oxc-parser issues that this might be a specific npm version bug? oxc-project/oxc#14598

npm 11.12.1, so it's higher than 11.3 and even 11.11 which also had some issues with dependency tree in some cases

[Aukevanoost]

I did a little bit of digging and I suspect it has something to do with the version of oxc-parser (>0.9.0). Because when I force it to be at least 0.13.0 (package.json):

{
  "overrides": {
    "oxc-parser":"^0.13.0"
  }
}

It will solve the issue.

You will have to remove the package-lock.json and node_modules and reinstall though. And ofcourse there was a breaking change so in node_modules/@chialab/estransform/lib/parser.js you'll need to update this line:

import { parse as parseAsync } from 'oxc-parser';

Now, I also added a PR for a permanent fix on chialab/rna#228 but until then, I am curious.

Does this fix also work for you? @OldShaterhan and everyone else having this issue

[OldShaterhan]

I'll have to check, as far as I remember I put some manual override, but I think it was somehow different than yours suggestion. Nevertheless, would be great to have this fixed.

[berkon]

I'm seeing this too. It suddenly popped up. Neither npm ci, nor removing node_modules and packag-lock.json helped, even though I did not change anything related to the dependencies.

[Aukevanoost]

Hi @berkon,

Are you on version v21.2.5? That version contains the oxc-parser dependency update.

[berkon]

Hi @Aukevanoost,

no I'm already on v21.2.13.

Adding it to optional dependencies solves the issue. But I don't know if its good to keep it there.

[Aukevanoost]

@berkon Sorry I meant @angular-architects/native-federation@v21.2.5