aube update on mac breaks CI on linux which uses npm

[krombel]

When running e.g aube add vite on a mac it only adds the current os and cpu type into package-lock.json
npm ci then does not install the linux required dependency
=> I get e.g. the following error

> vite build
failed to load config from /workspace/org/proj1/vite.config.ts
error during build:
Error: The package "@esbuild/linux-x64" could not be found, and is needed by esbuild.
If you are installing esbuild with npm, make sure that you don't specify the
"--no-optional" or "--omit=optional" flags. The "optionalDependencies" feature
of "package.json" is used by esbuild to install the correct binary executable
for your current platform.
    at generateBinPath (/workspace/org/proj1/node_modules/esbuild/lib/main.js:1750:15)
    at esbuildCommandAndArgs (/workspace/org/proj1/node_modules/esbuild/lib/main.js:1820:33)
    at ensureServiceIsRunning (/workspace/org/proj1/node_modules/esbuild/lib/main.js:1977:25)
    at build (/workspace/org/proj1/node_modules/esbuild/lib/main.js:1876:26)
    at bundleConfigFile (file:///workspace/org/proj1/node_modules/vite/dist/node/chunks/dep-Dm0c1Wj2.js:49448:24)
    at async bundleAndLoadConfigFile (file:///workspace/org/proj1/node_modules/vite/dist/node/chunks/dep-Dm0c1Wj2.js:49432:19)
    at async loadConfigFromFile (file:///workspace/org/proj1/node_modules/vite/dist/node/chunks/dep-Dm0c1Wj2.js:49396:44)
    at async resolveConfig (file:///workspace/org/proj1/node_modules/vite/dist/node/chunks/dep-Dm0c1Wj2.js:48891:24)
    at async createBuilder (file:///workspace/org/proj1/node_modules/vite/dist/node/chunks/dep-Dm0c1Wj2.js:46866:18)
    at async CAC.<anonymous> (file:///workspace/org/proj1/node_modules/vite/dist/node/cli.js:862:23)
  ❌  Failure - Main Build website
exitcode '1': failure

When running npm add vite I see

this

"node_modules/@esbuild/aix-ppc64": { "version": "0.27.7", "resolved": "https://registry.npmjs.org/@esbuild/aix-ppc64/-/aix-ppc64-0.27.7.tgz", "integrity": "sha512-EKX3Qwmhz1eMdEJokhALr0YiD0lhQNwDqkPYyPhiSwKrh7/4KRjQc04sZ8db+5DVVnZ1LmbNDI1uAMPEUBnQPg==", "cpu": [ "ppc64" ], "dev": true, "license": "MIT", "optional": true, "os": [ "aix" ], "engines": { "node": ">=18" } }, "node_modules/@esbuild/android-arm": { "version": "0.27.7", "resolved": "https://registry.npmjs.org/@esbuild/android-arm/-/android-arm-0.27.7.tgz", "integrity": "sha512-jbPXvB4Yj2yBV7HUfE2KHe4GJX51QplCN1pGbYjvsyCZbQmies29EoJbkEc+vYuU5o45AfQn37vZlyXy4YJ8RQ==", "cpu": [ "arm" ], "dev": true, "license": "MIT", "optional": true, "os": [ "android" ], "engines": { "node": ">=18" } }, [...]

added for each os and cpu (whereas aube only adds it for mac).

Is there a flag "all archs" or similar? How to make this case work?

[false200]

@krombel yeah, this is the platform-filtering difference between aube and npm, not esbuild itself.

npm locks every @esbuild/* optional platform package into package-lock.json. aube defaults to host-only when writing foreign lockfiles like package-lock.json (same idea as pnpm). So on mac you get @esbuild/darwin-*, linux CI runs npm ci, and @esbuild/linux-x64 was never locked.

No --all-archs flag. Use supportedArchitectures to widen what gets locked:

{
  "aube": {
    "supportedArchitectures": {
      "os": ["current", "linux", "win32"],
      "cpu": ["current", "x64", "arm64"],
      "libc": ["current", "glibc", "musl"]
    }
  }
}

(pnpm.supportedArchitectures works too — same merge rules.)

Add that before aube add / aube update, then regenerate the lockfile:

aube install --lockfile-only

You should see all the @esbuild/* entries npm would have written. Commit that lockfile and npm ci on linux should be fine.

Minimal version if CI is just linux x64 glibc:

"supportedArchitectures": { "os": ["current", "linux"], "cpu": ["current", "x64"], "libc": ["glibc"] }

Other paths:

• aube-lock.yaml - cross-platform matrix is the default there; aube ci in CI instead of npm ci if you can switch the lockfile.
• One-off repair - run npm install --package-lock-only on linux (or in CI once) to merge the missing platform entries back in.
• Upgrade aube - older versions had add/update ignoring the settings pipeline and collapsing native optionals to host-only even when configured (fix(update): preserve cross-platform optionals and time entries #637). Worth being on a recent release.

Also double-check CI isn't passing --omit=optional - esbuild needs those optional platform packages.

[jdx]

Agreed that package-lock.json should behave differently here. I opened #942 to make npm lockfile writes follow npm's cross-platform optional-native semantics: aube will record the foreign optional native packages in package-lock.json, while still filtering them out before fetch/link for the current host.

Once that lands, a macOS aube add / aube update followed by Linux npm ci should keep the esbuild/Vite native package entries without needing supportedArchitectures. Until it is released, the workaround above still applies: set supportedArchitectures or regenerate/repair the npm lockfile on the Linux target.

This comment was generated by Codex.

[krombel]

Nice! I didnt expect a fix so fast! Thanks a lot