now there is an older project, and the dependent version of the dependency package in package-lock.json is fixed: but once npm I , all the dependent versions circled in the red box above are changed to ^ x.x.x or ~ x.x.x . How can these depen...
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 tim...
two puzzles: 1 are production dependencies and development dependencies not duplicated? Does that mean local development depends on production + development? 2 won t executing build type dependencies into packages in development dependencies when the ...
recently used ...
recently, in the process of learning webpack4, I went deep into the details that I had never paid attention to before, and found some problems that I didn t quite understand. Now my package.json configuration file refers to webpack,webpack-cli,html-web...
basic information npm version 5.6.0 yarn version 1.8.0 node version 8.9.4 the dependencies section of package.json is as follows "dependencies": { "baz": "git+http: foo.com bar baz.git" }, problem description ...
set as follows "scripts": { "dev": "webpack-dev-server --inline --progress --config build webpack.dev.conf.js", "build": "node build build.js", "analyz": "set NODE_ENV=production &a...
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...