package.json

问题 I am running npm install I have a machine specific package.json and package-lock.json so I cannot change it. I am on linux I do not have sudo access the errors npm WARN notice [SECURITY] static-eval has the following vulnerability: 1 moderate. Go here for more details: https://nodesecurity.io/advisories?search=static-eval&version=2.0.2 - Run `npm i npm@latest -g` to upgrade your npm version, and then `npm audit` to get more info. npm WARN notice [SECURITY] timespan has the following

问题 Currently, all node modules in package.json are using * as the version number, my application is quite stable with those node modules, so I want to fix their version numbers in package.json, so that I can run npm install in other places to install node modules with expected versions. Is there a way to do it quickly instead of changing them one by one manually? Such as some console commands, npm fixversion module_a module_b ... ? 回答1: You're looking for npm shrinkwrap See the documentation

问题 Currently, all node modules in package.json are using * as the version number, my application is quite stable with those node modules, so I want to fix their version numbers in package.json, so that I can run npm install in other places to install node modules with expected versions. Is there a way to do it quickly instead of changing them one by one manually? Such as some console commands, npm fixversion module_a module_b ... ? 回答1: You're looking for npm shrinkwrap See the documentation

问题 Currently, all node modules in package.json are using * as the version number, my application is quite stable with those node modules, so I want to fix their version numbers in package.json, so that I can run npm install in other places to install node modules with expected versions. Is there a way to do it quickly instead of changing them one by one manually? Such as some console commands, npm fixversion module_a module_b ... ? 回答1: You're looking for npm shrinkwrap See the documentation

问题 Currently, all node modules in package.json are using * as the version number, my application is quite stable with those node modules, so I want to fix their version numbers in package.json, so that I can run npm install in other places to install node modules with expected versions. Is there a way to do it quickly instead of changing them one by one manually? Such as some console commands, npm fixversion module_a module_b ... ? 回答1: You're looking for npm shrinkwrap See the documentation

问题 I'm having issues with the proxy I set up. This is my root package.json file: "scripts": { "client": "cd client && yarn dev-server", "server": "nodemon server.js", "dev": "concurrently --kill-others-on-fail \"yarn server\" \"yarn client\"" } My client package.json file: "scripts": { "serve": "live-server public/", "build": "webpack", "dev-server": "webpack-dev-server" }, "proxy": "http://localhost:5000/" I've set up express on my server side to run on port 5000. Whenever I make a request to

问题 I'm using Docker for Mac and Docker Compose for development of a Node.js application and I'm experiencing an error with the package.json file being locked. The specific error after running npm install --save <package> within a running container is: npm WARN saveError EBUSY: resource busy or locked, rename '/Example/package.json.1647356251' -> '/Example/package.json' The simplified package structure is: ▾ docker/ Dockerfile docker-compose.yaml package.json The Dockerfile contains: FROM node:9

问题 I would like to create a package.json build script that executes slightly different set of commands when run from Windows, Linux, Mac. The problem is that I cannot find a way to put it in package.json file that will run without problems at every system. Here is an example that I would like to have: "scripts" : { "build.windows" : "echo do windows specific stuff", "build.linux" : "echo do linux specific stuff", "build.mac" : "echo do mac specific stuff", "build" : "??????????????" <- what to

问题 I have this issue, and whenever I do npm init the file package.json is created, but it is formatted in one line. As you can imagine this is not practical to work with and I end up formatting it myself, which is not the best task in the world. EDIT I have noticed that when I do npm install the file gets reformatted again to one line. This is very annoying and I'm sure it must be some configuration that I cannot find. What should I change to have the file formatted from the beginning? Thanks!

问题 Is there a way to specify subsets of dependencies in npm, with an alias or "feature tag"? That is, if someone knows that they will only be using some limited subset of the features of my package, they can specify those features and, on npm install , only download the dependencies relevant to those features? My package has a very large number of dependencies and takes nearly half an hour to install, but most users only need a subset of their functionality. I'm thinking of something like how