Bug fix for py-jupyter-server and hidden npm/node dependency #417
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add variant typescript for
py-jupyter-server@:1
, which then requiresnpm
/node
. Patch the build system for~typescript
so that it doesn't autodetect any systemnpm
/node
installations. That is because if it does findnpm
somewhere in the path, it attempts to build the typescript extension even though it shouldn't, and this can cause problems as described in JCSDA/spack-stack#995, JCSDA/spack-stack#928, and spack#41899.Note that the build backend has changed from
py-packaging
topy-hatch
betweenpy-jupyter-server
versions 1 and 2, therefore this bug fix is restricted to version 1.Corresponding spack develop PR: spack#43279 (merged 2024/03/20)
Testing
I tested installing
[email protected]
on my macOS with a broken localnpm
/node
installation (to mimick the problem described in JCSDA/spack-stack#995. I was able to install it successfully with the default variant~typescript
, and also with+typescript
(which addednpm
andnode
as dependencies).It also fixed the problem on Narwhal with the existing but broken
npm
/node
installation.Also testing default
~typescript
in JCSDA/spack-stack#1033Issue(s) addressed
Resolves JCSDA/spack-stack#995
Resolves JCSDA/spack-stack#928
Dependencies
n/a
Impact
n/a
Checklist