2019-10-08
985
Kostas Bariotis
7393
Oct 8, 2019 â‹… 3 min read

Why you should use package-lock.json

Kostas Bariotis

Recent posts:

Leveraging Parallel Computing In Node.js

Leveraging parallel computing in Node.js

Use parallel computing in Node.js with worker threads to optimize performance, handle CPU-intensive tasks, and utilize multi-core processors.

David Omotayo
Feb 13, 2025 â‹… 8 min read

A guide to modern frontend architecture patterns

Frontend architecture is the foundation of your frontend codebase. Here’s how to optimize the pattern that you choose.

Shalitha Suranga
Feb 12, 2025 â‹… 9 min read
A Guide To Graceful Degradation In Web Development

A guide to graceful degradation in web development

Implement graceful degradation in frontend apps by handling failures, mitigating API timeouts, and ensuring a seamless UX with fallbacks.

Rosario De Chiara
Feb 11, 2025 â‹… 4 min read
Building High-Performance Websites Using Htmx And Go

Building high-performance websites using htmx and Go

Use htmx and Go to build high-performance websites, leveraging server-side rendering and minimal JavaScript for fast and efficient applications.

Abhinav Anshul
Feb 10, 2025 â‹… 11 min read
View all posts

2 Replies to "Why you should use package-lock.json"

  1. Thanks for the article. Using `npm ci` even in local development sounds like good advice, but I find it really annoying, that this will cause the Node modules to be installed on every invocation of `npm ci`. I guess it’s rather common to run install/ci on container start to not have to worry about having to update or install new packages (if necessary). Makes it a lengthy process not being able to avoid these re-installations.

Leave a Reply