Why does a diff occur?

[YangYongAn]

Although this issue is not directly related to the current repository, the current repository depends on @clack/prompts, which in turn depends on is-unicode-supported. I am using npm (not yarn or pnpm) because I want to keep the cost lowest for the team during usage, as npm is bundled with Node.js, while others need to be installed separately.

So here is the issue: I uploaded package-lock.json to the project's Git repository. When checking out from Git for the first time, there is no node_modules folder. Running npm i to install will modify package-lock.json and create a diff. Specifically, it will set dev to true in node_modules/@clack/prompts/node_modules/is-unicode-supported. Running npm i again, the previous dev setting disappears and becomes "extraneous": true. This has left me puzzled, unsure if it's an npm issue or a problem with how a dependency author has set up their package release.

---

虽然这个问题和当前 repo 没有直接关系。但是当前 repo 依赖了 @clack/prompts ，在 @clack/prompts 中依赖了 is-unicode-supported ，我使用的是 npm （没有使用 yarn 或者的 pnpm 的原因是想让团队在使用过程中成本最低，因为 node 捆绑的 npm 一定有，其他的需要额外安装）

于是就出现了一个问题：我上传了package-lock.json 到项目的 git 库，在从git 检出的时候，第一次是没有 node_modules 的，运行 npm i 安装出来会修改 package-lock.json 产生 diff，具体细节是会把 node_modules/@clack/prompts/node_modules/is-unicode-supported 中 dev 设置为 true，再次运行 npm i ，刚刚的 dev 不见了，变成了 "extraneous": true, 这让我很困惑，不知道是 npm 的问题，还是某个依赖作者在发包的设置问题。