vercel / vercel/hyper

Error updating plugins. env: node: No such file or directory

Open
#5,590 2 comments 2 reactions 0 assignees View on GitHub

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: <OS X 11.13.1>
  • Hyper.app version: <3.0.2> <3.1.0-canary.4>
  • Link of a Gist with the contents of your .hyper.js: https://gist.github.com/eyeseaevan/5d544bb849904a9be72ad39b8a3fa1b5 (Default, only updated with my shell)
  • Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): <N/A (not sure how to find)>
  • The issue is reproducible in vanilla Hyper.app: Yes

Issue

I am using Node and NPM with n. I do not wish to use the Homebrew npm, although I do have node also installed with Homebrew just to have checked if that fixes it - and it doesn't. I downloaded Hyper off of Github. This has been an issue for me ever since I started using Hyper, even after reinstalling OS X. Not sure what it is. Possibly I can somehow set the environment variable in the config to my node (in /usr/local/bin), although there is no documentation as to how. I have no plugins installed, but when I did, I had the same issue. I attempted to remove all pre-existing Hyper files and to reinstall with both the Canary and Stable release versions, neither of which fixed the issue. Hyper updates themselves are working, but I am unable to install plugins :(

My Node installation is a system node, although I also tried with the Homebrew node.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing plugin installation or updating on macOS with the reported Node and n setup, then inspect how Hyper resolves the Node executable for plugin operations. Done means plugin installation succeeds without the “env: node: No such file or directory” error; the issue provides no named files or tests to begin with.

Written by the indexing model from the issue text.

Assessment

Tech stack
node.js
Domain
desktop
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.