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

Why you should use package-lock.json

Kostas Bariotis

Recent posts:

Nx Adoption Guide: Overview, Examples, And Alternatives

Nx adoption guide: Overview, examples, and alternatives

Let’s explore Nx features, use cases, alternatives, and more to help you assess whether it’s the right tool for your needs.

Andrew Evans
Mar 28, 2024 â‹… 9 min read
Understanding Security In React Native Applications

Understanding security in React Native applications

Explore the various security threats facing React Native mobile applications and how to mitigate them.

Wisdom Ekpotu
Mar 27, 2024 â‹… 10 min read
Warp Adoption Guide: Overview, Examples, And Alternatives

warp adoption guide: Overview, examples, and alternatives

The warp web framework for Rust offers many enticing features. Let’s see when and why you should consider using warp in your projects.

Ukeje Goodness
Mar 26, 2024 â‹… 8 min read
Integrating Next Js And Signalr For Enhanced Real Time Web App Capabilities

Integrating Next.js and SignalR to build real-time web apps

In this tutorial, you’ll learn how to integrate Next.js and SignalR to build an enhanced real-time web application.

Clara Ekekenta
Mar 25, 2024 â‹… 8 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