If Puppeteer fills your hard drive with many copies of Chromium, you can
- either use
puppeteer-core
instead - or add
puppeteer_skip_chromium_download=true
to your.npmrc
and also setpuppeteer_executable_path
with Chrome path
There are 7 contents with this tag:
If Puppeteer fills your hard drive with many copies of Chromium, you can
puppeteer-core
insteadpuppeteer_skip_chromium_download=true
to your .npmrc
and also set puppeteer_executable_path
with Chrome path
You may have this issue with Node 16.5.1 on #Netlify: This setting is no longer used. npm stores temporary files in a special location in the cache…
Quick fix: put 16.5.0
in an .nvmrc
file
Had once again to reinstall node-gyp
, even if I'm on Big Sur, this must be a running joke… 🤷♂️
I'm using an SVG sprite on this site to make sure I don't repeat SVG code for icons that are used multiple times, and I inline it so the rendering doesn't depend on another resource loading. Here's how I build this sprite from individual SVG icons.
I'm already using #Jest to test images-responsiver
, my #Node package for easier responsive images, but I wonder how to use it to test my plugin wrapping it for #Eleventy… 🤔
node-gyp
Installation notes for [node-gyp on] macOS Catalina
I was confronted with this error at least once a month for several months (once again yesterday) when trying to npm install a freshly checked out Node.js project:
Updating npm packages versions in package.json
I chose to use npm-check-updates to check for available updates of packages in my package.json files, and it always works without issues, so I guess I can recommend it.
See all tags.