How to modify the name version of package.json

is currently writing a project generation tool for the front end of vue"s nodejs project.
there are no other problems with the project I generated, but the name and version in package.json are generated dynamically according to the project at that time.
results show that npm install cannot be executed after the dynamically generated name, version is modified. Error:

npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN Invalid version: "1.0"
npm WARN webapp No description
npm WARN webapp No repository field.
npm WARN webapp No README data
npm WARN webapp No license field.

it is OK not to change the name, not to change the edition. Ask the great god for advice

{
"name": "test",
"version": "1.0",
" private ": true
}

Package.json node.js

Jan.08,2022

package-lock.json is used to check in source control. If you use npm5 ( npm install-g npm@latest ), you can see the following bold text on the command line: created a lockfile as package-lock.json. You should commit this file. is derived from npm help package-lock.json :

package-lock.json is automatically generated for any action by npm that modifies the node_modules tree or package.json. It describes the exact tree generated so that subsequent installations can generate the same tree, regardless of intermediate dependency updates.

this file is intended to be submitted to the source code base and for various purposes:

describes a single representation of a dependency tree, which ensures that members, deployment, and continuous integration can install exactly the same dependencies.
provides a tool for users to "traverse" the previous state of node_modules without committing the directory itself.
promotes greater visibility of trees through readable source control extensions.
and optimize the installation process to allow npm to skip duplicate metadata parsing for installed packages.

A key detail about package-lock.json is that it cannot be published and will be ignored if it is found anywhere other than the top-level package. It shares the format with npm-shrinkwrap.json (5) , which is basically the same file, but allows publishing. This is not recommended unless you deploy CLI tools or otherwise use the release process to produce production packages.

if package-lock.json and npm-shrinkwrap.json both exist in the root directory of a package, package-lock.json will be completely ignored.

Previous: How to use a msyql statement to put several tables with the same table structure into a table and finally export it?

Next: Vue @ click and the occasional failure of router-link

How does npm publish ignore files?
when using npm to publish a package, there are some files under the current folder that you do not want to publish, such as the node_modules folder. You must install and rely on them when you test them. It is obviously not good to release these files as...

Package.json node.js npm

Mar.04,2021
Package.json attribute problem
recently used ...

Package.json node.js javascript

May.22,2021