Contents tagged “npm”

There are 7 contents with this tag:

1. • Nicolas Hoizey
   • 7 January 2023
   • JavaScript, npm
   • permalink

   Which (stable, lightweight, maintained, etc.) npm package would you recommend to transform any RSS or Atom feeds to a standard JSON Feed format?

2. • Nicolas Hoizey
   • 3 August 2022
   • Cloudflare, npm
   • permalink

   To have different builds for #Cloudflare Pages previews, I found if-env and the CF_PAGES_BRANCH variable:

   {
     "scripts": {
       "build": "if-env CF_PAGES_BRANCH=main && npm run main || npm run preview"
     }
   }

3. • Nicolas Hoizey
   • 8 July 2022
   • CodePen, GitHub, npm, Web Component
   • 10 reactions
   • permalink

   In one single day, I created my first Web Component (vanilla flavor), put the code on #GitHub, published it on #npm, and made a demo on #CodePen… 💪

   https://codepen.io/nhoizey/pen/YzawBrq

   BTW, it's made to responsively use videos as background of content!

4. • Nicolas Hoizey
   • 28 June 2022
   • npm
   • 3 reactions
   • permalink

   I don't understand how npm outdated works.

   On my machine, packages from both dependencies and devDependencies are listed.

   In a GitHub Action, I only get packages from dependencies, but duplicated, and with status MISSING…

   

   🤷‍♂️

5. • Nicolas Hoizey
   • 24 June 2021
   • image, JavaScript, npm, responsive
   • 11 reactions
   • permalink

   This migration from basicHTML to LinkeDOM in images-responsiver looks good! 😍

   

   I have yet to find if this behavior with HTML entities is an issue.

   +@markboulton

6. • Nicolas Hoizey
   • 3 September 2020
   • Eleventy, Git, image, npm
   • 2 reactions
   • permalink

   Should I use a monorepo for images-responsiver and eleventy-plugin-images-responsiver, the #Eleventy plugin? 🤔

   Might be better to manage dependencies and sync releases, and easier for users to find/add issues.

7. Updating npm packages versions in package.json

   • Nicolas Hoizey
   • 6 March 2020
   • Node, npm
   • 5 reactions

   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.