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

Error, cannot find electron/path.txt #13

Open
ghost opened this issue Oct 21, 2016 · 8 comments
Open

Error, cannot find electron/path.txt #13

ghost opened this issue Oct 21, 2016 · 8 comments

Comments

@ghost
Copy link

ghost commented Oct 21, 2016

installed demokit, ran demokit new foo which worked fine, but running demokit ./foo/index.js gives this error:

Error: ENOENT: no such file or directory, open '/usr/local/lib/node_modules/demokit/electron/node_modules/electron/path.txt'

@tolmasky
Copy link
Owner

Could you tell me npm version, node version, and OS version.

Thanks,

Francisco

@EcutDavid
Copy link

Same to me,
MAC version: 10.12.1
npm 2.14.2
node 4.0.0

Thanks!

@wmhafiz
Copy link

wmhafiz commented Jul 25, 2017

Same here! Solved it by not using sudo when installing npm kit globally (sudo npm i -g demokit )

my environment

npm 5.4.0
node 8.0.0

@nahmjordan
Copy link

nahmjordan commented Jul 31, 2017

Not sure about my logic but I noticed that demokit would mentioning version @1.0.0 so I specified the latest version (@7.0.0 in this case) and now the demokit window opens when I run:

demokit ./path/to/demo-file.js

@tolmasky
Copy link
Owner

It was installing 1.0.0 from just doing npm install demekit?

@nahmjordan
Copy link

@tolmasky my terminal command was "sudo npm install -g demokit" and when I googled pieces of the errors I was getting I found websockets/bufferutil#22 mentioning out of date dependencies. I saw in my error response " [email protected] install: node-gyp rebuild " and " Failed at the [email protected] install script. " so with what limited knowledge I have I tried "sudo npm install -g [email protected]" and it seems like things are running correctly now.

@tolmasky
Copy link
Owner

This is a lot of help, thanks. If you happen to have time, could you answer these questions:

  1. Had you tried installing demekit in the past? (maybe for some reason 1.0.0 was cached on your machine?)
  2. If you npm uninstall -g demokit and then npm install -g demokit@latest, does it work?
  3. If you npm uninstall -g demokitand then just try npm install -g demokit, doe sit continue to not work?

I'm just trying to figure out why it was giving you 1.0.0 instead of 7.0.0.

@nahmjordan
Copy link

Sorry for the late reply!

  1. no this would be the first install
  2. demokit still works
  3. demokit installs with messages containing the 7.0.0 version number and appears to work properly

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

4 participants