Why would anyone use the path package from npm instead of Node’s path module?
https://www.npmjs.com/package/path
Just found it in one of my own projects, where I'm the only contributor… 😅
Contents tagged “Node”
There are 8 contents with this tag:
-
-
If Puppeteer fills your hard drive with many copies of Chromium, you can
- either use
puppeteer-coreinstead - or add
puppeteer_skip_chromium_download=trueto your.npmrcand also setpuppeteer_executable_pathwith Chrome path
- either use
-
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.0in an.nvmrcfile -
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 installa freshly checked out… -
Updating npm packages versions in package.json
I chose to use
npm-check-updatesto check for available updates of packages in mypackage.jsonfiles, and it always works without issues, so I guess I can recommend it. I'm also using this as a reminder for my own use… 😁
![screenshot of Installation notes for [node-gyp on] macOS Catalina](https://res.cloudinary.com/nho/image/fetch/q_auto,f_auto,w_auto:100:384,c_limit/https://image.thum.io/get/width/1200/crop/800/noanimate/https://github.com/nodejs/node-gyp/blob/master/macOS_Catalina.md)
See all tags.