Npm install and add to package.json

Viewed 19k times. Improve this question. Soviut Soviut Did you ever find a solution to this? The low bandwidth solution seems to be very carefully checking the npm website for the current versions and manually adding them to your package.

Add a comment. Active Oldest Votes. Improve this answer. Arfeo Arfeo 6 6 silver badges 20 20 bronze badges. Interestingly combining --package-lock-only with --no-package-lock seems to do this npm install --package-lock-only --no-package-lock PACKAGE This does not create or update the package-lock.

Epeli Epeli This was a bug and is now fixed in npm 6. I've hardly ever seen a more blatant case of "it's not a bug Is it really a bug? Using npm 6. Is it confirmed if its a bug or not?? I'm using the same on 6. There is no way to do that with npm that I'm aware of.

RyanZim RyanZim 5, 1 1 gold badge 25 25 silver badges 39 39 bronze badges. Note that both packages npm-add and adddep depend on the npm package which is enormous. AlexanderMills npm v6. It's not really about the size for me. For those new to the party, npm and yarn are package managers for Node. They both leverage the package. If you already have Node. Depending on your system, you could also consult with your friendly neighborhood package manager and install things that way.

Not all dependencies are created equal, as some are only required while doing development. These dependencies, while important, can slow down production deployments since they take time to install and the code will never be touched. Examples of development dependencies would be testing utilities like mocha or jest. For those types of dependencies, we can install them as such, and have them added to the devDependencies section of our package. We call these production dependencies and tend to includes packages like express or react.

Adding a production dependency to a project is just as easy as adding a development one, but it will be added to the dependencies section of our package. These are installed globally and are great for packages that also include command-line utilities that you want to run alongside your other command-line utilities:. To remove either a development or production dependency from a project, we simply uninstall or remove it:. You can configure the application to wait for the debugger to attach before starting execution by setting the inspectMode property to break in the docker-run: debug task in tasks.

In the Containers tab, right-click on your container and choose View Logs. This article guides you through what Docker configuration changes are required as well as what workloads and components you can install in a container. For example, you can mount your source code into a container to be built by a customized environment while you continue to use Visual Studio or other tools to write your code.

You can use containers for runtime consistency as well, which is common for micro-services using multiple containers with an orchestration system; however, is beyond the scope of this article. If Visual Studio Build Tools does not have what you require to build your source code, these same steps can be used for other Visual Studio products. Do note, however, that Windows containers do not support an interactive user interface so all commands must be automated.

Some familiarity with Docker is assumed below. If you're not already familiarwith running Docker on Windows, read about how to install and configure the Docker engine on Windows. The base image below is a sample and may not work for your system. Read Windows container version compatibilityto determine which base image you should use for your environment. Save the following example Dockerfile to a new file on your disk. If the file is named simply 'Dockerfile', it is recognized by default.

Earlier releases cause the build command to fail. NET Framework might not install properly and no install error is indicated.

Managed code might not run after the install is complete. Also note that images that are tagged version 4. Visual Studio version No error is displayed. See Windows container version compatibility to see which container OS versions are supported on which host OS versions, and Known issues for containers for known issues.

Error code is used to indicate success with a reboot required, see MsiExec. This command builds the Dockerfile in the current directory using 2 GB of memory. The default 1 GB is not sufficient when some workloads are installed; however, you might be able to build with only 1 GB of memory depending on your build requirements. The final image is tagged 'buildtoolslatest' so you can easily run it in a container as 'buildtools' since the 'latest' tag is the default if no tag is specified.

If you want to use a specific version of Visual Studio Build Tools in a more advanced scenario, you might instead tag the container with a specific Visual Studio build number as well as 'latest' so containers can use a specific version consistently.

The final image is tagged 'buildtools:latest' so you can easily run it in a container as 'buildtools' since the 'latest' tag is the default if no tag is specified.