Both gnu and musl core distributions installed for Ubuntu Linux

[JoshuaKGoldberg]

Describe the bug

After npm i @swc/jest in a project, there are two core distributions available in node_modules:

$ du -sh node_modules/@swc/*
444K    node_modules/@swc/core
74M     node_modules/@swc/core-linux-x64-gnu
78M     node_modules/@swc/core-linux-x64-musl
24K     node_modules/@swc/jest

Input code

npm i @swc/jest

Config

n/a

Playground link

No response

Expected behavior

Both of these are >70M in size. Ideally only one would be installed at a time.

Actual behavior

Both packages have the same system dependencies listed in their package.json files:

{
  // ...
  "os": [
    "linux"
  ],
  "cpu": [
    "x64"
  ],
  // ...
}

...and so both get installed on Linux x64 systems.

Version

1.2.143

Additional context

I'm not familiar enough with npm/node OS & CPU identifiers to know whether a more granular description could be used. If there is, I would love to send a PR to fix this. 😄

If not, it might be the case that npm/rfcs#519 blocks a real resolution?

Context: typescript-eslint/tslint-to-eslint-config#1367. WSL 2.0 in an Ubuntu drive.

[kdy1]

cc @Brooooooklyn Is there a way to fix this?

[Brooooooklyn]

As mentioned above, we need to wait npm/rfcs#519 landed to fix this issue.
There is a workaround that may reduce the install size: vercel/next.js#32850

[erawk]

Hey @kdy1 @Brooooooklyn - this is causing some NexJS deployment issues on Vercel, as reported in this issue

1. Vercel uses Linux x64, so both @swc/core-linux-x64-(gnu|musl) folders are added
2. In 13.0.2+ of NextJS, Prisma is added as an external and thus included in builds
3. The combined weight of Prisma + 2x @swc/core exceeds the 50MB limit

Here's a screenshot from Vercel build log:

My current super hacky fix with gnarly consequences:

Add a postbuild.sh script that runs to zero-out the unnecessary musl version:

# Make the large files zero bytes for the `musl` SWC
echo "Nuking unnecessary @swc/core files in node_modules/@swc/core-linux-x64-musl"
DISK_USAGE_MUSL_BEFORE=`du -h node_modules/@swc/core-linux-x64-musl/*`
echo "${DISK_USAGE_MUSL_BEFORE}"
echo '' > node_modules/@swc/core-linux-x64-musl/swc
echo '' > node_modules/@swc/core-linux-x64-musl/swc.linux-x64-musl.node
DISK_USAGE_MUSL_AFTER=`du -h node_modules/@swc/core-linux-x64-musl/*`
echo "${DISK_USAGE_MUSL_AFTER}"

This gets us under the threshold but opens us up to failure if indeed musl is needed.

Are there any alternatives you suggest? Anything else downstream we can do to avoid this double inclusion?

[kylemh]

I'm really confused why all of the distributions are being included.

[kdy1]

This is not a bug of swc

[kwonoj]

npm/rfcs#438 (comment)

Latest npm claims this issue is fixed, so closing. In any case this is techinically pkg mgr issue.

[swc-bot]

This closed issue has been automatically locked because it had no new activity for a month. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.