Note from 3 February 2021

Had once again to reinstall node-gyp, even if I'm on Big Sur, this must be a running joke… 🤷‍♂️

• older note:
  Note from 3 February 2021
• newer note:
  Note from 25 February 2021

---

Related contents with similar topics

1. • Nicolas Hoizey
   • 1 August 2022
   • Chrome, Node, Puppeteer
   • 8 reactions
   • permalink

   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 set puppeteer_executable_path with Chrome path

2. • Nicolas Hoizey
   • 4 June 2022
   • Netlify, Node
   • permalink

   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

3. How I build my SVG sprites

   • Nicolas Hoizey
   • 15 October 2020
   • SVG, WebPerf, Node
   • 38 reactions

   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.

4. • Nicolas Hoizey
   • 17 September 2020
   • Eleventy, Jest, Node, plugin, test
   • 2 reactions
   • permalink

   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… 🤔

   https://github.com/nhoizey/images-responsiver/issues/95

5. 

   node-gyp

   Installation notes for [node-gyp on] macOS Catalina

   • Nicolas Hoizey
   • 27 August 2020
   • Node

   I was confronted with this error at least once a month for several months (once again yesterday) when trying to a freshly checked out Node.js project:…