@swc/core installing two distributions

[privatenumber]

Describe the bug

When installing @swc/core it seems to install two distributions: @swc/core-linux-x64-musl and @swc/core-linux-x64-gnu, inflating the install size to 100MB+:
https://pkg-size.dev/@swc%2Fcore

I'm wondering if this is a limitation in the environment WebContainers mock, or in swc's postinstall script.

Link to the blitz that caused the error

https://pkg-size.dev/@swc%2Fcore

Sorry, I don't have a Stackblitz reproduction since I wasn't sure how to quickly measure the node_modules size but pkg-size.dev does a plain and simple npm install on WebContainers.

Steps to reproduce

See link

Expected behavior

Locally, when I install @swc/core, it's about 35MB.

Ideally it just installs one distribution.

Parity with Local

• I have run the project in my local machine and I could not reproduce the issue.

Screenshots

No response

Platform

No response

Additional context

privatenumber/pkg-size.dev#21

As a side, wondering how esbuild's postinstall is executed in WebContainers. It felt like there was some custom logic overwriting it to force install the WASM distribution but I wasn't sure. Seems two distributions are installed too: wasm & linux-x64

Is there something swc could do in their postinstall script to play nicely with WebContainers?

[privatenumber]

Did some research. There's actually no bug here.

npm installs optionalDependencies based on this criteria. However, npm v9.4.2 (used by WebContainers) doesn't support looking at the libc property. Which led to installing distributions that match up until the libc property:

• https://unpkg.com/@swc/core-linux-x64-gnu/package.json
• https://unpkg.com/@swc/[email protected]/package.json

Currently, all package managers support libc:

• yarn added support in 2022 Jan: Adds support for the libc field in package.json yarnpkg/berry#3981
• pnpm added support in 2022 Mar: Support libc field in package.json pnpm/pnpm#4454
• npm added support 2023 July: [RRFC] Add libc fields to select optionalDependencies should be installed or skipped npm/rfcs#438

However, WebContainers does not have npm v9.6.5 yet. Is there a ballpark timeline for when I can expect npm to be upgraded?

As a potential solution on my end, I could either swap npm to use pnpm/yarn. Or perform a post-installation step to remove any packages with libc !== 'gnu'.

[Nemikolh]

Hey @privatenumber! Thanks a lot for investigating this. 😃 (Love the links in particular, super useful 🙏)

I can't give you a precise timeline yet but we will definitely upgrade npm to the latest version in the next couple of months or so. It might be coming sooner but we're focusing first on other things such as upgrading to node 18.

[privatenumber]

Good to know! I'll implement something on my end then. Thanks!