# Npm lockfileVersion 2

**URL:** <https://community.gladysassistant.com/t/npm-lockfileversion-2/7338>\
**Category:** Développement\
**Created:** [June 1, 2022, 6:22am UTC](https://community.gladysassistant.com/t/npm-lockfileversion-2/7338 "2022-06-01T06:22:46Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![AlexTrovato](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/alextrovato/32/10705_2.png) [@AlexTrovato](https://community.gladysassistant.com/u/AlexTrovato)\
**Post date:** [June 1, 2022, 6:22am UTC](https://community.gladysassistant.com/t/npm-lockfileversion-2/7338/1 "2022-06-01T06:22:46Z")

</div>

Hello everyone,  
since I moved to npm \> 6 (currently on 8), the `npm i` command changes all `package-lock.json` files to version 2.

> **[package-lock.json | npm Docs](https://docs.npmjs.com/cli/v8/configuring-npm/package-lock-json/)**
>
> A manifestation of the manifest

This seems to be backwards-compatible, and apparently I’m the only one in this situation, but that could change, so I think we should bring this up to decide whether to upgrade npm.

@pierre-gilles @VonOx any thoughts?

---

<div class="post-metadata">

**Author:** ![AlexTrovato](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/alextrovato/32/10705_2.png) [@AlexTrovato](https://community.gladysassistant.com/u/AlexTrovato)\
**Post date:** [June 1, 2022, 6:55am UTC](https://community.gladysassistant.com/t/npm-lockfileversion-2/7338/2 "2022-06-01T06:55:30Z")

</div>

Ok, my bad… it’s because of the attempted migration to Node.js 16…

---

<div class="post-metadata">

**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\
**Post date:** [June 1, 2022, 6:55am UTC](https://community.gladysassistant.com/t/npm-lockfileversion-2/7338/3 "2022-06-01T06:55:36Z")

</div>

Hi Alex

I need to check the impact on the Docker images (v14 npm6)

It seems like we’re pinning the npm version in the package.json files.

---

<div class="post-metadata">

**Author:** ![AlexTrovato](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/alextrovato/32/10705_2.png) [@AlexTrovato](https://community.gladysassistant.com/u/AlexTrovato)\
**Post date:** [June 1, 2022, 6:58am UTC](https://community.gladysassistant.com/t/npm-lockfileversion-2/7338/4 "2022-06-01T06:58:17Z")

</div>

The version is recommended, but it’s not strictly enforced.

> <https://stackoverflow.com/questions/29349684/how-can-i-specify-the-required-node-js-version-in-package-json>

Info on version compatibility: [https://nodejs.org/dist/index.json](https://nodejs.org/dist/index.json)

---

<div class="post-metadata">

**Author:** ![VonOx](https://gladys-assistant-community.b-cdn.net/user_avatar/community.gladysassistant.com/vonox/32/10128_2.png) [@VonOx](https://community.gladysassistant.com/u/VonOx)\
**Post date:** [June 1, 2022, 7:01am UTC](https://community.gladysassistant.com/t/npm-lockfileversion-2/7338/5 "2022-06-01T07:01:15Z")

</div>

Ah yes, Node 16 — I think there’s an impact on crypto.