This repository has been archived by the owner. It is now read-only.

Join GitHub today

GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.

Comments

commented Oct 14, 2016

What's the feature?

Add an options to forcibly not save a dependency to package.json when running npm install

What problem is the feature intended to solve?

Since users are able to use this config npm config set save true to have all their dependencies saved by default, we need a way to optionally not save some of them. I have a script that locally installs some extra dependencies for dev purposes only but I do not want them saved.

Is the absence of this feature blocking you or your team? If so, how?

It's an extra step to verify packages don't get saved

Is this feature similar to an existing feature in another tool?

I don't think so

Is this a feature you're prepared to implement, with support from the npm CLI team?

It looks like yarn does not pass node-gyp flags to native packages the way npm does. For example when attempting to install sqlite3@3.1.6 with: npm install sqlite3@3.1.6 --build-from-source. Also supported are --noflag to set it to false and --flag=true or --flag=false or --flag=0 or --flag=1 or --flag=f or --flag=t flags.defineInteger - Must take a value and will be cast to a Number. Passing a non-integer arg will throw. Npm install [email protected]'>=0.1.0 npm install @myorg/[email protected]'>=0.1.0 npm install: Installs the package from the hosted git provider, cloning it with git. For a full git remote url, only that URL will be attempted.

Then npm update will install [email protected], because that is the highest-sorting version that satisfies ^0.4.0 (>= 0.4.0 npm update -g will apply the update action to each globally installed package that is outdated -- that is, has a version that is different from latest. This site is a work in progress. If you find bugs in the docs or have documentation-related feature requests, please let us know. Submit npm issues in the npm.community 'bugs' topic.

commented Oct 14, 2016

This already works for me. Have you tried this yourself?

commented Oct 17, 2016

Yes, sorry this does work. I could find any documentation around it so I assumed it didn't exist.

commented Oct 17, 2016

@ssylvia Yeah, you can append 'no' to any config to make it false, so --no-save, --no-optional, --no-progress all set their respective configs to false.

added a commit to huan/npm-programmatic that referenced this issue Jul 5, 2018

Fix options for `save: false`

Verified

Npm Install Flags

Npm Install Cli Flags

This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.

GPG key ID: 4AEE18F83AFDEB23Learn about signing commits

added a commit to huan/npm-programmatic that referenced this issue Jul 5, 2018

Fix options for `save: false`

Verified

This commit was created on GitHub.com and signed with a verified signature using GitHub’s key.

Npm Install Flag-icon-css

GPG key ID: 4AEE18F83AFDEB23Learn about signing commits

Npm Download

Merged

Join GitHub today

Comments

commented Oct 14, 2016

What's the feature?

What problem is the feature intended to solve?

Is the absence of this feature blocking you or your team? If so, how?

Is this feature similar to an existing feature in another tool?

Is this a feature you're prepared to implement, with support from the npm CLI team?

commented Oct 14, 2016

commented Oct 17, 2016

commented Oct 17, 2016

Npm Install Flags

Npm Install Cli Flags

Npm Install Flag-icon-css

Npm Download

Npm Install Famfamfam-flags