npm package not updating minor versions
I'm trying to figure out why rollup is not updating. in my package file I have:
"devDependencies":
"rollup": "^0.62.0",
Running npm outdated shows:
package Current Wanted Latest
rollup 0.62.0 0.62.0 0.67.1
If the carat indicates that everything but major versions can be updated, and in this specific case the latest version is only a minor version, why wouldn't it update with npm update rollup?
I realise that the Wanted is preventing the update, but why?
npm
asked Nov 13 '18 at 2:12
sansSpoonsansSpoon
623416
add a comment |
I'm trying to figure out why rollup is not updating. in my package file I have:
"devDependencies":
"rollup": "^0.62.0",
Running npm outdated shows:
package Current Wanted Latest
rollup 0.62.0 0.62.0 0.67.1
If the carat indicates that everything but major versions can be updated, and in this specific case the latest version is only a minor version, why wouldn't it update with npm update rollup?
I realise that the Wanted is preventing the update, but why?
npm
asked Nov 13 '18 at 2:12
sansSpoonsansSpoon
623416
Possible duplicate of NPM caret doesn't bring in newest minor version
– Andre Figueiredo
Nov 13 '18 at 2:31
add a comment |
I'm trying to figure out why rollup is not updating. in my package file I have:
"devDependencies":
"rollup": "^0.62.0",
Running npm outdated shows:
package Current Wanted Latest
rollup 0.62.0 0.62.0 0.67.1
If the carat indicates that everything but major versions can be updated, and in this specific case the latest version is only a minor version, why wouldn't it update with npm update rollup?
I realise that the Wanted is preventing the update, but why?
npm
asked Nov 13 '18 at 2:12
sansSpoonsansSpoon
623416
I'm trying to figure out why rollup is not updating. in my package file I have:
"devDependencies":
"rollup": "^0.62.0",
Running npm outdated shows:
package Current Wanted Latest
rollup 0.62.0 0.62.0 0.67.1
If the carat indicates that everything but major versions can be updated, and in this specific case the latest version is only a minor version, why wouldn't it update with npm update rollup?
I realise that the Wanted is preventing the update, but why?
npm
npm
asked Nov 13 '18 at 2:12
sansSpoonsansSpoon
623416
asked Nov 13 '18 at 2:12
sansSpoonsansSpoon
623416
asked Nov 13 '18 at 2:12
sansSpoonsansSpoon
623416
asked Nov 13 '18 at 2:12
sansSpoonsansSpoon
623416
asked Nov 13 '18 at 2:12
sansSpoonsansSpoon
623416
623416
Possible duplicate of NPM caret doesn't bring in newest minor version
– Andre Figueiredo
Nov 13 '18 at 2:31
add a comment |
Possible duplicate of NPM caret doesn't bring in newest minor version
– Andre Figueiredo
Nov 13 '18 at 2:31
Possible duplicate of NPM caret doesn't bring in newest minor version
– Andre Figueiredo
Nov 13 '18 at 2:31
Possible duplicate of NPM caret doesn't bring in newest minor version
– Andre Figueiredo
Nov 13 '18 at 2:31
add a comment |
1 Answer
1
active
oldest
votes
From https://github.com/npm/node-semver#caret-ranges-123-025-004,
[Carets] Allows changes that do not modify the left-most non-zero digit in the [major, minor, patch] tuple. In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >=0.1.0, and no updates for versions 0.0.X.
If you know that you want the latest versions 0.67.1, you could specify your dependency as
"devDependencies":
"rollup": "0.x",
answered Nov 13 '18 at 2:31
BishalBishal
556216
add a comment |
Your Answer
StackExchange.ifUsing("editor", function ()
StackExchange.using("externalEditor", function ()
StackExchange.using("snippets", function ()
StackExchange.snippets.init();
);
);
, "code-snippets");
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "1"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272782%2fnpm-package-not-updating-minor-versions%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
From https://github.com/npm/node-semver#caret-ranges-123-025-004,
[Carets] Allows changes that do not modify the left-most non-zero digit in the [major, minor, patch] tuple. In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >=0.1.0, and no updates for versions 0.0.X.
If you know that you want the latest versions 0.67.1, you could specify your dependency as
"devDependencies":
"rollup": "0.x",
answered Nov 13 '18 at 2:31
BishalBishal
556216
add a comment |
From https://github.com/npm/node-semver#caret-ranges-123-025-004,
[Carets] Allows changes that do not modify the left-most non-zero digit in the [major, minor, patch] tuple. In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >=0.1.0, and no updates for versions 0.0.X.
If you know that you want the latest versions 0.67.1, you could specify your dependency as
"devDependencies":
"rollup": "0.x",
answered Nov 13 '18 at 2:31
BishalBishal
556216
add a comment |
From https://github.com/npm/node-semver#caret-ranges-123-025-004,
[Carets] Allows changes that do not modify the left-most non-zero digit in the [major, minor, patch] tuple. In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >=0.1.0, and no updates for versions 0.0.X.
If you know that you want the latest versions 0.67.1, you could specify your dependency as
"devDependencies":
"rollup": "0.x",
answered Nov 13 '18 at 2:31
BishalBishal
556216
From https://github.com/npm/node-semver#caret-ranges-123-025-004,
[Carets] Allows changes that do not modify the left-most non-zero digit in the [major, minor, patch] tuple. In other words, this allows patch and minor updates for versions 1.0.0 and above, patch updates for versions 0.X >=0.1.0, and no updates for versions 0.0.X.
If you know that you want the latest versions 0.67.1, you could specify your dependency as
"devDependencies":
"rollup": "0.x",
answered Nov 13 '18 at 2:31
BishalBishal
556216
answered Nov 13 '18 at 2:31
BishalBishal
556216
answered Nov 13 '18 at 2:31
BishalBishal
556216
answered Nov 13 '18 at 2:31
BishalBishal
556216
556216
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53272782%2fnpm-package-not-updating-minor-versions%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Possible duplicate of NPM caret doesn't bring in newest minor version
– Andre Figueiredo
Nov 13 '18 at 2:31