Skip to content
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

document the which constraint for the shimming strategy #9

Open
dherman opened this issue Jan 24, 2018 · 0 comments
Open

document the which constraint for the shimming strategy #9

dherman opened this issue Jan 24, 2018 · 0 comments

Comments

@dherman
Copy link
Contributor

dherman commented Jan 24, 2018

An important constraint: some Node packages use which to determine whether a particular tool is installed, so it's important for those tools to become invisible to the running Node process. (For example, testing whether Yarn is installed by shelling out to which yarn.)

Another, even more subtle constraint: we still want to be able to hook installation of global packages when shelling out from a Node process. So we may want to have version-specific shim directories for each Node version. This also needs to be reconciled with the Windows Path environment variable semantics (i.e., that system-wide Path supersedes user Path).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant