question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

`npm i --prefix test` fail - puppeteer

See original GitHub issue

Describe the bug

Cannot install the test packages. npm i --prefix test fail. Seems to be something related with puppeteer

To Reproduce

Steps to reproduce the behavior:

  1. Checkout the dev branch
  2. npm install
  3. npm i --prefix test
$ npm install

removed 28 packages, and audited 590 packages in 2s

72 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
$ npm i --prefix test
npm ERR! code 1
npm ERR! path /home/remmel/workspace/three.js/test/node_modules/puppeteer
npm ERR! command failed
npm ERR! command sh -c node install.js

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/remmel/.npm/_logs/2022-03-08T19_44_42_678Z-debug-0.log

Log : 2022-03-08T19_44_42_678Z-debug-0.log

Extract

207 info run puppeteer@13.1.2 install node_modules/puppeteer node install.js
...
217 verbose stack Error: command failed
217 verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js:64:27)
217 verbose stack     at ChildProcess.emit (node:events:520:28)
217 verbose stack     at maybeClose (node:internal/child_process:1092:16)
217 verbose stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)

Platform:

  • OS: Ubuntu 20.04 LTS
  • Npm 8.3.0
  • Node v16.14.4
  • Three.js version: [dev]

Issue Analytics

  • State:closed
  • Created 2 years ago
  • Comments:5 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
mrdoobcommented, Mar 8, 2022

I wish there was a way to detect if test/node_modules exists so we can tell the developer what to do.

0reactions
remmelcommented, Mar 8, 2022

I’ll close, the workaround is OK for me. Thanks for help!

Read more comments on GitHub >

github_iconTop Results From Across the Web

npm install puppeteer failed on Windows Pro · Issue #5587
Oops, was simply fixed by removing node_modules and installing back, then do npm i -D puppeteer again.
Read more >
How to solve npm install error “npm ERR! code 1”
If your Node.js version is very recent, try downgrading. The stable version 14.16.1 worked.
Read more >
puppeteer - npm
A high-level API to control headless Chrome over the DevTools Protocol. Latest version: 19.3.0, last published: 12 days ago.
Read more >
Testing UI and SEO using Jest and Puppeteer. - Hatchd
With the release of nodejs making it possible to run JS on the server on top of the move from handling all presentation...
Read more >
Getting Started - CodeceptJS
For instance, to use Puppeteer API inside a test use ... retry 2 times if error with message 'Node not visible' happens I.retry({...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found