Issue accessing NodeJS when using Powershell
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 44.7k
- Forks
- 3.6k
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
- I am on the latest Hyper.app version
- I have searched the issues of this repo and believe that this is not a duplicate
- OS version and name: MacOS 13.3 (22E252)
- Hyper.app version: 3.4.1
- Link of a Gist with the contents of your hyper.json:
- Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere):
- The issue is reproducible in vanilla Hyper.app:
Issue
I have NodeJS installed via nvm. I am trying to use NodeJS via Powershell inside Hyper. I am able to invoke NodeJS when running it from the default terminal as well as Powershell inside the default terminal. However, when I set Powershell as my shell in Hyper, it is not able to recognize NodeJS or any other NPM packages installed. It does however recognize pyenv and such.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The report names Hyper.app, PowerShell, NodeJS installed through nvm, and npm packages but no source file or test. Start by reproducing the difference between Hyper's PowerShell session and the default terminal, then inspect how Hyper launches the configured shell and initializes its environment. Done means NodeJS and installed npm packages are discoverable in PowerShell inside Hyper.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- nodejs, powershell
- Domain
- cli, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100