Repository navigation
v2.10.1 fixes several workspace bugs in aube update, aube remove, aube audit and aube sbom, closes more pnpm compatibility gaps, and makes network access more reliable on VPN/split-DNS setups and unstable connections.
Changed
- Smaller, faster store compression on APFS (#1930, @jdalton): on macOS, aube now tries LZFSE before LZVN and compresses blocks in parallel. On three ARM64 native addons (Oxlint, Rolldown, Lightning CSS), this used 5% less disk space, compressed 23% faster, and used up to 6.4 MB less memory. Decoding of zstd-packed napi addons is now bounded. File contents and store keys do not change.
- System CA store is authoritative (#1932, @jdx): aube no longer adds its bundled Mozilla root certificates on top of the OS trust store. A CA that an OS update or enterprise policy removes is now also distrusted by aube. On Linux and other Unix systems, aube uses the bundled roots only when it cannot load any system roots, for example in a minimal container without
ca-certificates. It then printsWARN_AUBE_BUNDLED_ROOTS_FALLBACK.SSL_CERT_FILE,SSL_CERT_DIR,NODE_EXTRA_CA_CERTS,cafileandcawork as before.
Fixed
Workspaces
aube removewith a shared lockfile (#1952, @jdx): removals now go through the workspace install. Before, removing a dependency from a member with aworkspace:dependency failed withno version of lib matches range workspace:*afterpackage.jsonhad already been rewritten. Removing from other members wrote a stray member lockfile, and removing a root dependency re-resolved every member's locked versions.workspace:links afteraube update(#1969, @jdx, with @ruandre): a member'sworkspace:dependency was written relative to the workspace root, which left itsnode_modulessymlink broken. The path also grew longer with each update. This affected bothaube-lock.yamlandpnpm-lock.yaml. To repair a lockfile that an earlier version already broke, runaube install --fix-lockfile.- Optional peer bindings in the lockfile (#1941, #1970, @jdx, with @ruandre): an unrelated
aube add(a regression in 2.10.0) oraube update --no-save <pkg>no longer drops locked optional-peer bindings. For example,fdir@6.5.0(picomatch@4.0.4)no longer turns into a barefdir@6.5.0. This also covers a peer that only a different workspace member provides. - Peers provided by
workspace:dependencies (#1954, @jdx): a registry package whose peer comes from aworkspace:*orworkspace:^dependency is now linked to that workspace package. Before, the install failed understrictPeerDependencies, orrequire()threwMODULE_NOT_FOUNDat runtime. aube now also reads pnpm lockfiles that record these peers aslink:.aube updatecan still drop this link in some cases. aube audit --fix=update(#1968, @jdx, with @ruandre): an advisory now stays reported, and the command exits 1, while a workspace member still uses the vulnerable version, even if the root uses a safe one.aube sbom(#1967, @jdx, with @ruandre): the SBOM now includes packages that only workspace members depend on, including with--exclude-peers.
Resolution and lockfiles
aube update <transitive-dep>(#1976, @jdx): updating a package that is only a transitive dependency now moves it to the newest version its parents' ranges allow. Before, the command printedUpdating: <name>but left the locked version unchanged.- pnpm
settings:header (#1953, @jdx): aube now writes thepnpm-lock.yamlsettings header from the current configuration. Before, it copied old values, which could makepnpm install --frozen-lockfilefail withERR_PNPM_LOCKFILE_CONFIG_MISMATCH. aube now writesaddMissingPeerTypes,dedupePeers,injectWorkspacePackagesandpeersSuffixMaxLengthwhere pnpm does. Withlockfile.includeResolutionSettings: true, it also writes the resolution settings. aube now recognizesaddMissingPeerTypes,injectWorkspacePackages,autoDedupeanddedupeInjectedDeps, but only records them in the lockfile for pnpm compatibility. Changing only these settings now refreshes the lockfile onaube install.aube-lock.yamloutput is unchanged. strictPeerDependenciesmatches pnpm (#1940, @jdx): a prerelease now satisfies a range that its base release satisfies, soreact@19.0.0-rc.1satisfies^19.0.0.peerDependencyRules.allowedVersionsnow acceptsparent@range>peerkeys, and a*value allows prereleases.peerDependencyRules: allowedVersions: use-sync-external-store@1>react: "19"
- Patches with stripped trailing whitespace (#1939, @jdx): a
patchedDependenciespatch failed witherror applying hunkafter an editor or hook removed trailing whitespace from a context line. When an exact match fails, aube now uses pnpm's looser matching, which ignores trailing whitespace and searches up to 20 lines around the recorded position. Patches whose content really differs still fail. useDefaultTrustedDependenciesinpnpm-workspace.yaml(#1965, @jdx, with @ruandre): aube ignored this setting when it was in the workspace YAML. It is now read from there, as pnpm does. Use an unquoted YAML boolean.
trustPolicy=no-downgrade
- Staged publish to trusted publishing (#1957, @jdx): a version with a trusted publisher and provenance is no longer rejected as a downgrade from an earlier staged-publish release. Unlike pnpm, aube accepts this switch. Switching from staged publish to provenance only, or to no trust evidence, is still rejected.
- Vercel CLI (#1933, @shawnyeager): the default exclusions now cover the
@vercel/*packages in theverceldependency tree that publish without provenance. Releases before each cutoff version are still checked.
Commands and networking
aube execruns commands fromPATH(#1950, @jdx):aube exec node ...andaube exec bash ...no longer fail withbinary not foundwhen no project bin provides the command. Project bins still take precedence. This also applies to-r,--filterand--parallel.- Activated shims stay on
PATH(#1935, @jdx): afteraube activate, commands started byaube exec,aube dlx/aubxandaube run <bin>now resolvenpm,pnpmandyarnto aube's shims, as package scripts already did. Tools that runnpm install, such asshadcn, now go through aube. - DNS hangs with VPN or split DNS (#1943, @jdx): when a lookup through the built-in resolver times out, for example because
/etc/resolv.conflists a nameserver only the OS can reach, aube now falls back to the system resolver. It warns once (WARN_AUBE_DNS_HICKORY_TIMEOUT) and uses the system resolver for the rest of the run. Before,aube installandaube dlxappeared to hang. - Interrupted tarball downloads (#1974, @jdx): a connection that drops partway through a tarball download is now retried with backoff instead of failing the install with
end of file before message length reached. - Concurrent installs with a shared global virtual store (#1949, @jdx): two projects installing at the same time no longer fail with
File exists (os error 17)while linking the shared hidden hoist. aube auditwith npm aliases (#1971, @jdx, with @ruandre): aliased dependencies such as"odd-alias": "npm:is-odd@3.0.1"are now checked under their real package name. Before, aube looked them up under the alias.aube audit --fixin override mode still does not fix aliased dependencies;--fix=updatedoes.
Full Changelog: v2.10.0...v2.10.1
💚 Sponsor aube
aube is built and maintained by @jdx, an open source developer at entire.io, the title sponsor of his open source work.
If aube saves your team install time or CI minutes, please consider becoming an individual or company sponsor. Your support funds ongoing development and helps keep aube fast, free, and independent.