Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
Add Hyper CLI to user PATH without reboot needing #2823
Comments
Would make it work the first time Hyper launches, granted, not outside of it, but is that that important? |
I think that's the better workaround @Stanzilla |
I have just installed and used hyper for the first time. Anything I am missing, or its a know issue? |
@buffos Hyper CLI is only available on our canary release (upcoming v2) |
FYI I created a more generic version of this issue back in 2016 |
@Stanzilla I think this is important to have |
@chabou my idea was mainly meant as a workaround, since we can't easily refresh the environment at Hyper launch BUT we can add it to That means we have the following scenario: Current: User installs Hyper After the change: User installs Hyper I don't really see a downside to it? |
For Windows, what about using the refreshenv.cmd that chocolately includes? I ran it upon first opening of hyper and it worked excellently. So the install could run it or hyper could run on first open? (have not dug into the app so I'm not familiar with how exactly it would be best implemented). https://github.com/chocolatey/choco/blob/master/src/chocolatey.resources/redirects/RefreshEnv.cmd
|
Hey just wanted to check if this was in 3 or if I needed to do a manual refresh of my env variables in Windows? |
Is this issue still open? I am first time contributer. |
We are currently adding Hyper CLI path to user PATH in Windows registry: https://github.com/zeit/hyper/blob/262eb8ad9b7b9b15351f331765151538d67a09e2/app/utils/cli-install.js#L49-L91
A caveat is that environment variables are cached and users should open and validate "Edit environment variables for your account" dialog to force a cache refresh (or simply reboot their workstation).

@Stanzilla gave a link that could help to improve this: https://stackoverflow.com/a/11955920