Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

As a replacement of npm version, there is no control with the version?

See original GitHub issue

npm version allows me to control the version to be a major/minor/patch release.

But standard-version just bump the major version part, like v1.2.0 => v2.0.0

Issue Analytics

State:
Created 7 years ago
Comments:6 (5 by maintainers)

Top GitHub Comments

1reaction

stevemaocommented, Sep 20, 2016

reopen if anyone disagree 😃

0reactions

Tapppicommented, Sep 20, 2016

@ggranum @e-cloud So this is a combination of #83 and #84? #83 should make it possible to do pre-releases and #84 is just a previous issue on the releaseAs option. We can close this as a duplicate and move the discussion there?

Top Results From Across the Web

How can I change the version of npm using nvm?

This command will work regardless of which version of Node you've installed with nvm, because of the -g flag. When you switch versions...

npm-version

This behavior is controlled by git-tag-version (see below), and can be disabled on the command line by running npm --no-git-tag-version version . It...

How to Use Semantic Versioning in NPM | heynode.com

By default, when installing an npm package without specifying a version, npm installs the latest version published to the NPM registry.

nvm-sh/nvm: Node Version Manager - POSIX-compliant bash ...

This will first use "nvm version node" to identify the current version you're migrating packages from. Then it resolves the new version to...

Semver explained - why is there a caret (^) in my package.json?

There is a dedicated command npm update for checking and installing newer versions satisfying semver pattern in package.json . npm update. Or, if...