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

Can't install using "npm install webtorrent" #1498

Closed
sg-s opened this issue Sep 5, 2018 · 2 comments
Closed

Can't install using "npm install webtorrent" #1498

sg-s opened this issue Sep 5, 2018 · 2 comments

Comments

@sg-s
Copy link

@sg-s sg-s commented Sep 5, 2018

What version of WebTorrent?

current

What operating system and Node.js version?

OS: Ubuntu 17.10
node v6.11.4

What browser and version? (if using WebTorrent in the browser)

n/a

What did you expect to happen?

Tried

npm install webtorrent

expected it to install

What actually happened?

did not install, got this error message instead:

> bufferutil@4.0.0 install /home/sgs/node_modules/bufferutil
> node-gyp-build

make: Entering directory '/home/sgs/node_modules/bufferutil/build'
  CC(target) Release/obj.target/bufferutil/src/bufferutil.o
../src/bufferutil.c:2:10: fatal error: node_api.h: No such file or directory
 #include <node_api.h>
          ^~~~~~~~~~~~
compilation terminated.
bufferutil.target.mk:94: recipe for target 'Release/obj.target/bufferutil/src/bufferutil.o' failed
make: *** [Release/obj.target/bufferutil/src/bufferutil.o] Error 1
make: Leaving directory '/home/sgs/node_modules/bufferutil/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/share/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
gyp ERR! System Linux 4.13.0-45-generic
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/sgs/node_modules/bufferutil
gyp ERR! node -v v6.11.4
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 
npm WARN install:bufferutil@4.0.0 bufferutil@4.0.0 install: `node-gyp-build`
npm WARN install:bufferutil@4.0.0 Exit status 1

> utf-8-validate@5.0.1 install /home/sgs/node_modules/utf-8-validate
> node-gyp-build

make: Entering directory '/home/sgs/node_modules/utf-8-validate/build'
  CC(target) Release/obj.target/validation/src/validation.o
../src/validation.c:2:10: fatal error: node_api.h: No such file or directory
 #include <node_api.h>
          ^~~~~~~~~~~~
compilation terminated.
validation.target.mk:94: recipe for target 'Release/obj.target/validation/src/validation.o' failed
make: *** [Release/obj.target/validation/src/validation.o] Error 1
make: Leaving directory '/home/sgs/node_modules/utf-8-validate/build'
gyp ERR! build error 
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/share/node-gyp/lib/build.js:276:23)
gyp ERR! stack     at emitTwo (events.js:106:13)
gyp ERR! stack     at ChildProcess.emit (events.js:191:7)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:219:12)
gyp ERR! System Linux 4.13.0-45-generic
gyp ERR! command "/usr/bin/node" "/usr/bin/node-gyp" "rebuild"
gyp ERR! cwd /home/sgs/node_modules/utf-8-validate
gyp ERR! node -v v6.11.4
gyp ERR! node-gyp -v v3.4.0
gyp ERR! not ok 
npm WARN install:utf-8-validate@5.0.1 utf-8-validate@5.0.1 install: `node-gyp-build`
npm WARN install:utf-8-validate@5.0.1 Exit status 1

@sg-s sg-s changed the title Can't install using "npn install webtorrent" Can't install using "npm install webtorrent" Sep 5, 2018
@DiegoRBaquero

This comment has been minimized.

Copy link
Member

@DiegoRBaquero DiegoRBaquero commented Sep 5, 2018

@sg-s

This comment has been minimized.

Copy link
Author

@sg-s sg-s commented Sep 6, 2018

thanks, using node v8 fixed this

@sg-s sg-s closed this Sep 6, 2018
@lock lock bot locked as resolved and limited conversation to collaborators Dec 5, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.