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

Installing on Raspbian #233

Open
smibrandon opened this issue Mar 10, 2021 · 1 comment
Open

Installing on Raspbian #233

smibrandon opened this issue Mar 10, 2021 · 1 comment

Comments

@smibrandon
Copy link

I've installed Assistant Relay (sudo run npm start) in my assistant relay folder. Package.json is indeed in that folder. However, when installing, I receive this error:

npm ERR! path /package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/package.json'
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2021-03-07T20_02_45_366Z-debug.log

Here's the aforementioned log:

0 info it worked if it ends with ok
1 warn npm npm does not support Node.js v10.24.0
2 warn npm You should probably upgrade to a newer version of node as we
3 warn npm can't make any promises that npm will work with this version.
4 warn npm Supported releases of Node.js are the latest release of 4, 6, 7, 8, 9.
5 warn npm You can find the latest version at https://nodejs.org/
6 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'run', 'start' ]
7 info using npm@5.8.0
8 info using node@v10.24.0
9 verbose stack Error: ENOENT: no such file or directory, open '/package.json'
10 verbose cwd /
11 verbose Linux 5.10.17-v7+
12 verbose argv "/usr/bin/node" "/usr/bin/npm" "run" "start"
13 verbose node v10.24.0
14 verbose npm  v5.8.0
15 error path /package.json
16 error code ENOENT
17 error errno -2
18 error syscall open
19 error enoent ENOENT: no such file or directory, open '/package.json'
20 error enoent This is related to npm not being able to find a file.
21 verbose exit [ -2, true ]

@ryancasler
Copy link
Contributor

ryancasler commented Mar 13, 2021

Did you first run sudo npm run setup? Did you download the release.zip file and not copy the whole repo?

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

2 participants