Is version field on package.json being used by libraries dependencies (yarn, npm…)?
I've been having problems when trying to update custom libraries stored in a git repo targeting those libraries on package.json like:
"dependencies": {
"awesomeLibrary": "git+https://awesome-library-url.git"
}
If I go to awesomeLibrary repo and push new changes, there are sometimes where I don't get the latest version. I need to remark that I do not change the version field on the package.json of awesomeLibrary.
Can this behaviour be affecting yarn upgrade awesomeLibrary or npm update awesomeLibrary?
Cheers,
Javi.
npm version package.json yarnpkg
edited Jul 20 '18 at 16:41
tk421
3,82351627
asked Jul 18 '18 at 6:18
Javier RodriguezJavier Rodriguez
557
add a comment |
I've been having problems when trying to update custom libraries stored in a git repo targeting those libraries on package.json like:
"dependencies": {
"awesomeLibrary": "git+https://awesome-library-url.git"
}
If I go to awesomeLibrary repo and push new changes, there are sometimes where I don't get the latest version. I need to remark that I do not change the version field on the package.json of awesomeLibrary.
Can this behaviour be affecting yarn upgrade awesomeLibrary or npm update awesomeLibrary?
Cheers,
Javi.
npm version package.json yarnpkg
edited Jul 20 '18 at 16:41
tk421
3,82351627
asked Jul 18 '18 at 6:18
Javier RodriguezJavier Rodriguez
557
add a comment |
I've been having problems when trying to update custom libraries stored in a git repo targeting those libraries on package.json like:
"dependencies": {
"awesomeLibrary": "git+https://awesome-library-url.git"
}
If I go to awesomeLibrary repo and push new changes, there are sometimes where I don't get the latest version. I need to remark that I do not change the version field on the package.json of awesomeLibrary.
Can this behaviour be affecting yarn upgrade awesomeLibrary or npm update awesomeLibrary?
Cheers,
Javi.
npm version package.json yarnpkg
edited Jul 20 '18 at 16:41
tk421
3,82351627
asked Jul 18 '18 at 6:18
Javier RodriguezJavier Rodriguez
557
I've been having problems when trying to update custom libraries stored in a git repo targeting those libraries on package.json like:
"dependencies": {
"awesomeLibrary": "git+https://awesome-library-url.git"
}
If I go to awesomeLibrary repo and push new changes, there are sometimes where I don't get the latest version. I need to remark that I do not change the version field on the package.json of awesomeLibrary.
Can this behaviour be affecting yarn upgrade awesomeLibrary or npm update awesomeLibrary?
Cheers,
Javi.
npm version package.json yarnpkg
npm version package.json yarnpkg
edited Jul 20 '18 at 16:41
tk421
3,82351627
asked Jul 18 '18 at 6:18
Javier RodriguezJavier Rodriguez
557
edited Jul 20 '18 at 16:41
tk421
3,82351627
asked Jul 18 '18 at 6:18
Javier RodriguezJavier Rodriguez
557
edited Jul 20 '18 at 16:41
tk421
3,82351627
edited Jul 20 '18 at 16:41
tk421
3,82351627
edited Jul 20 '18 at 16:41
tk421
3,82351627
3,82351627
asked Jul 18 '18 at 6:18
Javier RodriguezJavier Rodriguez
557
asked Jul 18 '18 at 6:18
Javier RodriguezJavier Rodriguez
557
asked Jul 18 '18 at 6:18
Javier RodriguezJavier Rodriguez
557
557
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
If you plan to publish awesomeLibrary package or want to reference it from another project by pointing awesomeLibrary field in package.json to the package's repo, then yes, you'll have to add the name and version fields.
Otherwise it's optional.
Check "Configuring npm" from npm's official documentation for more details: link
Note from their documentation: "Version must be parseable by node-semver"
answered Nov 22 '18 at 15:09
Consta GorganConsta Gorgan
14614
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%2f51394835%2fis-version-field-on-package-json-being-used-by-libraries-dependencies-yarn-npm%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
If you plan to publish awesomeLibrary package or want to reference it from another project by pointing awesomeLibrary field in package.json to the package's repo, then yes, you'll have to add the name and version fields.
Otherwise it's optional.
Check "Configuring npm" from npm's official documentation for more details: link
Note from their documentation: "Version must be parseable by node-semver"
answered Nov 22 '18 at 15:09
Consta GorganConsta Gorgan
14614
add a comment |
If you plan to publish awesomeLibrary package or want to reference it from another project by pointing awesomeLibrary field in package.json to the package's repo, then yes, you'll have to add the name and version fields.
Otherwise it's optional.
Check "Configuring npm" from npm's official documentation for more details: link
Note from their documentation: "Version must be parseable by node-semver"
answered Nov 22 '18 at 15:09
Consta GorganConsta Gorgan
14614
add a comment |
If you plan to publish awesomeLibrary package or want to reference it from another project by pointing awesomeLibrary field in package.json to the package's repo, then yes, you'll have to add the name and version fields.
Otherwise it's optional.
Check "Configuring npm" from npm's official documentation for more details: link
Note from their documentation: "Version must be parseable by node-semver"
answered Nov 22 '18 at 15:09
Consta GorganConsta Gorgan
14614
If you plan to publish awesomeLibrary package or want to reference it from another project by pointing awesomeLibrary field in package.json to the package's repo, then yes, you'll have to add the name and version fields.
Otherwise it's optional.
Check "Configuring npm" from npm's official documentation for more details: link
Note from their documentation: "Version must be parseable by node-semver"
answered Nov 22 '18 at 15:09
Consta GorganConsta Gorgan
14614
answered Nov 22 '18 at 15:09
Consta GorganConsta Gorgan
14614
answered Nov 22 '18 at 15:09
Consta GorganConsta Gorgan
14614
answered Nov 22 '18 at 15:09
Consta GorganConsta Gorgan
14614
14614
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%2f51394835%2fis-version-field-on-package-json-being-used-by-libraries-dependencies-yarn-npm%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
