[Bug]: Pupeeteer does not launch in latest version #9121

Thomblin · 2022-10-15T20:09:46Z

Bug description

I am running pupeteer in WSL, ubuntu 20.04. I was able to run puppeteer v 18.1.0 by adding my chrome.exe from Windows to $PATH and launching puppeteer with

browser = await puppeteer.launch({ 
      executablePath: 'chrome.exe', 
      headless: true,
      args: ['--no-sandbox', '--disable-setuid-sandbox']
    });

However in the latest version (18.2.1) I get the error

FAIL src/App.e2e.test.js
● Test suite failed to run

Cannot find module 'puppeteer-core/internal/common/DeviceDescriptors.js' from 'node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js'

Require stack:
  node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js
  src/App.e2e.test.js

  at Resolver.resolveModule (node_modules/jest-resolve/build/resolver.js:324:11)
  at Object.<anonymous> (node_modules/puppeteer/src/puppeteer.ts:18:1)

Puppeteer version

18.2.1

Node.js version

16.17.0

npm version

8.19.2

What operating system are you seeing the problem on?

Windows

Relevant log output

No response

The text was updated successfully, but these errors were encountered:

jrandolf-2 · 2022-10-16T12:11:00Z

Could you try the latest version?

Thomblin · 2022-10-16T18:30:04Z

Thanks for the hint. I upgraded to 19.0.0 and get almost the same error:

FAIL src/App.e2e.test.js
● Test suite failed to run

Cannot find module 'puppeteer-core/internal/common/Device.js' from 'node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js'

Require stack:
  node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js
  src/App.e2e.test.js

  at Resolver.resolveModule (node_modules/jest-resolve/build/resolver.js:324:11)
  at Object.<anonymous> (node_modules/puppeteer/src/puppeteer.ts:18:1)

jrandolf-2 · 2022-10-17T08:49:32Z

Ah, jest-resolver... my old nemesis. Your jest version is too old. It needs exports resolution that was introduced in Node 12. I believe Jest versions >= 28 will work.

Thomblin · 2022-10-17T18:43:03Z

Not sure, if that is possible. I am using react-script and the latest version 5.0.1 comes along with "jest": "^27.4.3", if I see that correctly. So far I was not able to force the usage of v29. I am open for ideas how to upgrade or how to replace jest with something else

petrvecera · 2022-11-06T11:00:29Z

Hm we are running into the same problem.

@integration-tests/spartacus: FAIL test/spartacus-integration.test.js
@integration-tests/spartacus:   ● Test suite failed to run
@integration-tests/spartacus:     Cannot find module 'puppeteer-core/internal/common/Device.js' from '../../node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js'
@integration-tests/spartacus:     Require stack:
@integration-tests/spartacus:       /home/runner/work/xdn/xdn/node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js
@integration-tests/spartacus:       test/spartacus-integration.test.js
@integration-tests/spartacus:       at Resolver.resolveModule (../../node_modules/jest-resolve/build/index.js:306:11)
@integration-tests/spartacus:       at Object.<anonymous> (../../node_modules/puppeteer/src/puppeteer.ts:18:1)

Version 18.2.1 is OK. It started happening in the upgrade to version 19.x. No Idea why.
We running this in GitHub Actions - ubuntu latest.

We are gonna stick with version 18.x for now.

lysender · 2022-11-12T01:26:47Z

We are using nestjs but we're not using the latest nestjs version yet. Luckily, jest 28.1.3 works and all our e2e tests passed.

I just copied the jest versions from the latest nestjs app to our current app.

"@types/jest": "28.1.8",
"jest": "28.1.3",
"ts-jest": "28.0.8",

hitesh22b · 2022-11-23T10:02:17Z

I am facing the same issue even after upgrading jest to the latest version

"puppeteer": "^19.2.2",
 "@types/jest": "^29.2.3",
 "@types/jest": "^29.2.3",
"jest": "^29.3.1"

viditganpi · 2022-11-29T06:36:41Z

Any resolution for this?

white-wolf97 · 2022-11-30T18:44:59Z

Hi, why is it closed? I think the problem is not resolved, it is happenning to me right now.
I have react-scripts 5.0.1 too, with puppeteer 19.3.0

Strato · 2022-12-05T10:11:27Z

I just had the same problem and upgrading Jest from v27 to v29 worked for me, as expected.

So you either have to upgrade Jest to v28 if you can, or downgrade Puppeteer to v18.1.

omergal99 · 2022-12-12T12:27:56Z

npm install [email protected]

TamilSelvanKumaravel · 2022-12-12T16:28:12Z

npm install [email protected]

It's working

Sineaggi · 2023-02-07T23:08:05Z

In our case, a previous version of jest was being invoked by our test runner. I was able to debug that via jest's showConfig. After updating that dependency's version of jest we were set.

juanmirocks · 2023-03-14T16:11:44Z

I get a similar error with [email protected]:
Error: Could not resolve module "puppeteer-core/internal/puppeteer-core.js" (same error as in: Studiosity/grover#182)

In my case, I'm not using jest. I'm calling puppeteer through a parcel plugin ([email protected]).

Rolling back to:

npm install [email protected] ✅ works
npm install [email protected] ❌ fails with a similar (though not equal) error:
Error: Could not resolve module "puppeteer-core/internal/common/DeviceDescriptors.js"

Note that [email protected] (#9023) (f42336c) separated puppeteer and puppeteer-core. Likely a bug was introduced; not directly related to jest or parcel or any other library.

In my humble opinion, this issue is still open.

HerRA17 · 2023-05-09T15:39:44Z

Hi there,
so for an exercise that I am following I am facing the bug mentioned and this is the response:

Cannot find module 'puppeteer-core/internal/puppeteer-core.js' from 'node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js'

    Require stack:
      node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js
      src/test/EndToEnd.test.js

      at Resolver.resolveModule (node_modules/jest-resolve/build/resolver.js:324:11)
      at Object.<anonymous> (node_modules/puppeteer/src/puppeteer.ts:19:1)

I have puppeteer: ^19.4.0, I tried with 18.1.0 as suggested but received a no longer supported.
This are other dependencies that we are using:
"@wojtekmaj/enzyme-adapter-react-17": "^0.8.0",
"enzyme": "^3.11.0",
"jest-cucumber": "^3.0.1"

turbolego · 2023-06-08T10:15:35Z

npm install [email protected] works for me too.

With [email protected] i got the error [ERR_PACKAGE_PATH_NOT_EXPORTED]

Now i get: Downloading Chromium r1045629 - 189.9 Mb [===== ] 26% 16.9s

AS360 · 2023-07-06T10:56:18Z

#_Facing This Issue in in server side(after deploy) - 'puppeteer' Working in local machine properly.
Any Solution ??

Error: Failed to launch the browser process!
/home/abp/.cache/puppeteer/chrome/linux-1108766/chrome-linux/chrome: error while loading shared libraries: libnss3.so: cannot open shared object file: No such file or directory

TROUBLESHOOTING: https://pptr.dev/troubleshooting

at Interface.onClose (/home/abp/abpwedcrmapis-manager/abpwedcrmapis-manager/node_modules/@puppeteer/browsers/lib/cjs/launch.js:262:24)

at Interface.emit (node:events:525:35)
at Interface.emit (node:domain:489:12)
at Interface.close (node:readline:590:8)
at Socket.onend (node:readline:280:10)
at Socket.emit (node:events:525:35)
at Socket.emit (node:domain:489:12)
at endReadableNT (node:internal/streams/readable:1358:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)

pigping88 · 2023-09-04T08:14:37Z

node 18 npm 9, puppeteer 21
error:
the dependency can not find

puppeteer-core/internal/node/PuppeteerNode.js in ./node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js * puppeteer-core/internal/puppeteer-core.js in ./node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js

townxelliot · 2023-11-08T11:59:41Z

I'm not sure why this is closed, as this is still a problem on Puppeteer > 18.1.0 (which is out of support) where you are using ESM module loading, e.g. with Puppeteer 18.2.1:

% node -r esm
Welcome to Node.js v20.5.1.
Type ".help" for more information.
> require('puppeteer');
/Users/elliot.smith/projects/opg-pdf-service/node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js:1
Uncaught Error: Cannot find module 'puppeteer-core/internal/puppeteer-core.js'
Require stack:
- /Users/elliot.smith/projects/opg-pdf-service/node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js
- <repl>
    at Object.<anonymous> (/Users/elliot.smith/projects/opg-pdf-service/node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js:33:14)
    at Generator.next (<anonymous>) {
  code: 'MODULE_NOT_FOUND',
  requireStack: [
    '/Users/elliot.smith/projects/opg-pdf-service/node_modules/puppeteer/lib/cjs/puppeteer/puppeteer.js',
    '<repl>'
  ]
}
>

The problem appears to be the -r esm flag, as this works fine for me without it:

% node       
Welcome to Node.js v20.5.1.
Type ".help" for more information.
> require('puppeteer');
{
  connect: [Function: bound bound connect],
  defaultArgs: [Function: bound defaultArgs],
  executablePath: [Function: bound executablePath],
  launch: [Function: bound launch],
  trimCache: [Function: bound trimCache] AsyncFunction,
  WEB_PERMISSION_TO_PROTOCOL_PERMISSION: [Getter],
...

We are using jest, but our version is up to date (29.7.0), and I'm not sure why that would be involved in a straight require('puppeteer'); call anyway.

twointo2 · 2024-02-09T06:09:10Z

Hi!
Is there any update on this issue? I am still getting Cannot find module 'puppeteer-core/internal/puppeteer-core.js' on the following config:

"esm": "^3.2.25"
"puppeteer": "^22.0.0"

@townxelliot were you able to find any solution for this?

bradytrudeau · 2024-03-06T19:37:08Z

Has anyone figured out how to resolve this?

talhakhadim · 2024-03-21T19:15:53Z

For me the issue is fixed by upgrading my jest to v:29.7.0

abnerAlexis · 2024-04-01T00:59:25Z

I am also having the same issue.
I upgraded jest to v29.7.0
node version: 20.9.0
OS: Mac
I tried so many versions (22s to 18.1.0) of puppeteer but none worked.
Any suggestion would be appreciated.

luan-nvg · 2024-09-25T18:03:56Z

same problem.
"puppeteer": "18.1.0",
"puppeteer-core": "18.1.0",
"esm": "^3.2.25",

Saeidmogadam1 · 2024-09-27T03:32:42Z

I have been looking for a Chrome extension for so long

sawamotokai · 2024-09-30T16:33:50Z

Same problem here. I don't use jest.

{
  "name": "road-test-registrator",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "dependencies": {
    "@sendgrid/mail": "^8.1.3",
    "dotenv": "^16.4.5",
    "moment": "^2.30.1",
    "npm-check-updates": "^17.1.3",
    "puppeteer": "^18.1.0",
    "twilio": "^5.3.2"
  }
}

bradytrudeau · 2024-09-30T17:46:11Z

I ended up having my lambda download the correct version of chromium each time it executed. Probably not the most efficient way to handle it, but it works:

browser = await puppeteer.launch({
args: [...chromium.args, '--disable-dev-shm-usage'],
defaultViewport: chromium.defaultViewport,
headless: 'new',
executablePath: await chromium.executablePath('https://github.com/Sparticuz/chromium/releases/download/v123.0.1/chromium-v123.0.1-pack.tar'),
protocolTimeout: 240_000,
ignoreHTTPSErrors: true,
});

When I run it locally, I just point it at version of Chrome (which will more than likely only work until I update Chrome). Probably not a forever solution, but it'll have to work until I have the bandwidth to put in a bigger fix.

Michael-Osas · 2024-10-07T08:00:40Z

executablePath: await chromium.executablePath('https://github.com/Sparticuz/chromium/releases/download/v123.0.1/chromium-v123.0.1-pack.tar'),

How were you able to achieve this. I keep getting this error
The input directory \"/tmp/chromium-pack\" does not exist.

Thomblin added the bug label Oct 15, 2022

jrandolf-2 added the needs-feedback label Oct 16, 2022

jrandolf-2 closed this as completed Oct 17, 2022

croesnick mentioned this issue Nov 21, 2022

Update puppeteer dependency (v19) argos-ci/jest-puppeteer#498

Closed

ahayes91 mentioned this issue Jan 3, 2023

[Bug]: Update Jest in @storybook/addon-storyshots-puppeteer for compatibility with latest version of puppeteer storybookjs/storybook#20479

Closed

nicks6853 mentioned this issue Mar 1, 2023

Cannot find module 'puppeteer-core/internal/puppeteer-core.js Studiosity/grover#182

Closed

raineorshine mentioned this issue Apr 26, 2024

Puppeteer v22 cybersemics/em#1837

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

[Bug]: Pupeeteer does not launch in latest version #9121

[Bug]: Pupeeteer does not launch in latest version #9121

Thomblin commented Oct 15, 2022

jrandolf-2 commented Oct 16, 2022

Thomblin commented Oct 16, 2022

jrandolf-2 commented Oct 17, 2022

Thomblin commented Oct 17, 2022

petrvecera commented Nov 6, 2022

lysender commented Nov 12, 2022 •

edited

Loading

hitesh22b commented Nov 23, 2022 •

edited

Loading

viditganpi commented Nov 29, 2022

white-wolf97 commented Nov 30, 2022 •

edited

Loading

Strato commented Dec 5, 2022

omergal99 commented Dec 12, 2022

TamilSelvanKumaravel commented Dec 12, 2022

Sineaggi commented Feb 7, 2023 •

edited

Loading

juanmirocks commented Mar 14, 2023

HerRA17 commented May 9, 2023

turbolego commented Jun 8, 2023

AS360 commented Jul 6, 2023

pigping88 commented Sep 4, 2023 •

edited

Loading

townxelliot commented Nov 8, 2023 •

edited

Loading

twointo2 commented Feb 9, 2024

bradytrudeau commented Mar 6, 2024

talhakhadim commented Mar 21, 2024

abnerAlexis commented Apr 1, 2024

luan-nvg commented Sep 25, 2024

Saeidmogadam1 commented Sep 27, 2024

sawamotokai commented Sep 30, 2024

bradytrudeau commented Sep 30, 2024 •

edited

Loading

Michael-Osas commented Oct 7, 2024

[Bug]: Pupeeteer does not launch in latest version #9121

[Bug]: Pupeeteer does not launch in latest version #9121

Comments

Thomblin commented Oct 15, 2022

Bug description

Puppeteer version

Node.js version

npm version

What operating system are you seeing the problem on?

Relevant log output

jrandolf-2 commented Oct 16, 2022

Thomblin commented Oct 16, 2022

jrandolf-2 commented Oct 17, 2022

Thomblin commented Oct 17, 2022

petrvecera commented Nov 6, 2022

lysender commented Nov 12, 2022 • edited Loading

hitesh22b commented Nov 23, 2022 • edited Loading

viditganpi commented Nov 29, 2022

white-wolf97 commented Nov 30, 2022 • edited Loading

Strato commented Dec 5, 2022

omergal99 commented Dec 12, 2022

TamilSelvanKumaravel commented Dec 12, 2022

Sineaggi commented Feb 7, 2023 • edited Loading

juanmirocks commented Mar 14, 2023

HerRA17 commented May 9, 2023

turbolego commented Jun 8, 2023

AS360 commented Jul 6, 2023

pigping88 commented Sep 4, 2023 • edited Loading

townxelliot commented Nov 8, 2023 • edited Loading

twointo2 commented Feb 9, 2024

bradytrudeau commented Mar 6, 2024

talhakhadim commented Mar 21, 2024

abnerAlexis commented Apr 1, 2024

luan-nvg commented Sep 25, 2024

Saeidmogadam1 commented Sep 27, 2024

sawamotokai commented Sep 30, 2024

bradytrudeau commented Sep 30, 2024 • edited Loading

Michael-Osas commented Oct 7, 2024

lysender commented Nov 12, 2022 •

edited

Loading

hitesh22b commented Nov 23, 2022 •

edited

Loading

white-wolf97 commented Nov 30, 2022 •

edited

Loading

Sineaggi commented Feb 7, 2023 •

edited

Loading

pigping88 commented Sep 4, 2023 •

edited

Loading

townxelliot commented Nov 8, 2023 •

edited

Loading

bradytrudeau commented Sep 30, 2024 •

edited

Loading