You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On a none-darwin-arm64 system (because @esbuild/darwin-x64 is included in package-lock.json):
Prefetch node dependencies using information from package-lock.json
Build using npm with offline mode and from prefetched caches
Encounter failure due to missing @esbuild/{platform} in the cache.
Expected Result
All platform specific optional dependencies be present in package-lock.json for reproducible builds.
Actual Result
Starting from 2025.1.2, and likely due to an upstream bug npm/cli#4828, platform specific optional dependencies, e.g. @esbuild/linux-x64 are not locked in package-lock.json, preventing downstream packaging (namely Nix in my case) from working correctly.
In the meantime, it seems that the correct, complete package-lock.json can be generated by purging node_modules and package-lock.json and then running npm run build
Screenshots or Videos
No response
Additional Context
No response
Operating System
Linux
Operating System Version
No response
Installation method
Other
Build Version
2025.1.2
Issue Tracking Info
I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Steps To Reproduce
On a none-darwin-arm64 system (because
@esbuild/darwin-x64
is included inpackage-lock.json
):package-lock.json
@esbuild/{platform}
in the cache.Expected Result
All platform specific optional dependencies be present in
package-lock.json
for reproducible builds.Actual Result
Starting from 2025.1.2, and likely due to an upstream bug npm/cli#4828, platform specific optional dependencies, e.g.
@esbuild/linux-x64
are not locked inpackage-lock.json
, preventing downstream packaging (namely Nix in my case) from working correctly.In the meantime, it seems that the correct, complete
package-lock.json
can be generated by purgingnode_modules
andpackage-lock.json
and then runningnpm run build
Screenshots or Videos
No response
Additional Context
No response
Operating System
Linux
Operating System Version
No response
Installation method
Other
Build Version
2025.1.2
Issue Tracking Info
The text was updated successfully, but these errors were encountered: