New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mismatch between npm and node #122
Comments
Huh! Yeah we should be using the JLL, but I will look through the code again and see what's going on... |
julia> using NodeJS_20_jll
julia> npm
"/Users/anshul/.julia/artifacts/e972793fde0fa31a7fc77a58fa34e5ebd54e6658/bin/npm"
julia> NodeJS_20_jll.npm |> typeof
String so this doesn't adjust the PATH appropriately. Looks like an error on the NodeJS_jll end... |
This fixes LuxDL/DocumenterVitepress.jl#122 where the PATH was not adjusted appropriately.
JuliaPackaging/Yggdrasil#8595 should fix this issue, we will have to restrict compat for NodeJS_20_jll to v20.12.2 and above here. |
Horray! Thanks 🥇 |
Update: the Yggdrasil PR would have been breaking for users of NodeJS_20_jll, so I opted to use |
* [NodeJS_20_jll] Update version + make all products executable This fixes LuxDL/DocumenterVitepress.jl#122 where the PATH was not adjusted appropriately. * Revert executableproduct change
Hi, I'm afraid that I don't have a simple reproducer, but I occasionally seem to get some error that seems to arise from a version mismatch between npm and node:
I get that pretty randomly in CI and I have a colleague who had another issue that indicated that 'npm istall' in
DocumenterVitepress.jl/src/writer.jl
Line 186 in 79acc70
was trying to use a nonexistent global
node
in/usr/....
rather than the asset in~/.julia/artifacts/.../bin/node
that we should get from NodeJS_20_jll. I figure that this might explain how one can get a node / npm version mismatch like the error msg indicates.My colleagues stacktrace:
It's a bit annoying to get an issue without a reproducer, but maybe someone here has some idea of how to fix this anyway.
Thanks for your efforts!
The text was updated successfully, but these errors were encountered: