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

Unable to install @latest via npm #691

Open
siaccarino opened this issue Sep 11, 2023 · 5 comments
Open

Unable to install @latest via npm #691

siaccarino opened this issue Sep 11, 2023 · 5 comments

Comments

@siaccarino
Copy link
Contributor

The installation log is filled with lot of deprecation warnings and at the end the puppeteer dependency fails to install with:

npm ERR! ERROR: Failed to set up Chromium r1011831! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download.

a simple version bumping fails due to breaking API changes

the full log:

npm WARN deprecated @fortawesome/[email protected]: Please upgrade to 6.1.0. https://fontawesome.com/docs/changelog/
npm WARN deprecated @fortawesome/[email protected]: Please upgrade to 6.1.0. https://fontawesome.com/docs/changelog/
npm WARN deprecated @babel/[email protected]: 🚨 This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (https://babeljs.io/docs/en/babel-polyfill) for more information.
npm WARN deprecated [email protected]: < 19.4.0 is no longer supported
npm WARN deprecated [email protected]: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.
npm ERR! code 1
npm ERR! path I:\test\thirdparty\nodejs\node_modules\asciidoctor-pdf\node_modules\puppeteer
npm ERR! command failed
npm ERR! command C:\Windows\system32\cmd.exe /d /s /c node install.js
npm ERR! ERROR: Failed to set up Chromium r1011831! Set "PUPPETEER_SKIP_DOWNLOAD" env variable to skip download.
npm ERR! [Error: EISDIR: illegal operation on a directory, realpath 'I:\test\thirdparty\nodejs\node_modules\asciidoctor-pdf\node_modules\puppeteer\.local-chromium\win64-1011831'] {
npm ERR!   errno: -4068,
npm ERR!   code: 'EISDIR',
npm ERR!   syscall: 'realpath',
npm ERR!   path: 'I:\\test\\thirdparty\\nodejs\\node_modules\\asciidoctor-pdf\\node_modules\\puppeteer\\.local-chromium\\win64-1011831'
npm ERR! }

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\secret\AppData\Local\npm-cache\_logs\2023-09-11T12_18_35_675Z-debug-0.log
@siaccarino
Copy link
Contributor Author

If I manually bump only puppeteer to 21.1.1 it will work but I assume that the result will be unpredictable

@ggrossetie
Copy link
Owner

Puppeteer is relatively stable, I think we can use the latest version. We have a few (visual) tests so we can probably safely upgrade.

@siaccarino
Copy link
Contributor Author

But then:

  Puppeteer old Headless deprecation warning:
    In the near future `headless: true` will default to the new Headless mode
    for Chrome instead of the old Headless implementation. For more
    information, please see https://developer.chrome.com/articles/new-headless/.
    Consider opting in early by passing `headless: "new"` to `puppeteer.launch()`
    If you encounter any bugs, please report them to https://github.com/puppeteer/puppeteer/issues/new/choose.

@siaccarino
Copy link
Contributor Author

And your pagedjs fork will also somehow react strange and produces overflows - https://gitlab.coko.foundation/pagedjs/pagedjs/-/issues/357 - at least my detection method "if (child.tagName === "P" && child.offsetTop >= pageHeight)" gets triggered.

@siaccarino
Copy link
Contributor Author

siaccarino commented Sep 12, 2023

I guess #672 is related but tests are failing. However: the windows version of the old chromium seems to be take offline. The Linux version is still up.

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