should yarn.lock and .yarnclean file follow git versioning?
I have integrated yarn manager in my node.js application. Now Through yarn yarn.lock and .yarnclean files are generated. Should I put them in .gitignore or should they follow git versioning?
yarnpkg
add a comment |
I have integrated yarn manager in my node.js application. Now Through yarn yarn.lock and .yarnclean files are generated. Should I put them in .gitignore or should they follow git versioning?
yarnpkg
add a comment |
I have integrated yarn manager in my node.js application. Now Through yarn yarn.lock and .yarnclean files are generated. Should I put them in .gitignore or should they follow git versioning?
yarnpkg
I have integrated yarn manager in my node.js application. Now Through yarn yarn.lock and .yarnclean files are generated. Should I put them in .gitignore or should they follow git versioning?
yarnpkg
yarnpkg
asked Mar 18 '17 at 13:57
user7510478
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
.yarnclean You can put into .gitignore file
You should add yarn.lock to your git, don't ignore it.
When you run either yarn or yarn add , Yarn will generate a yarn.lock file within the root directory of your package. You don’t need to read or understand this file - just check it into source control. When other people start using Yarn instead of npm, the yarn.lock file will ensure that they get precisely the same dependencies as you have.
answered Mar 21 '17 at 9:57
KasiriveniKasiriveni
1,9631126
add a comment |
Both files should be part of your version control.
.yarnclean is generated by running the yarn clean command. From the docs:
Yarn will create a
.yarncleanfile that should be added to version control.
yarn.lock is used to get consistent installs of dependencies across machines — it contains extra information that package.json does not which allows yarn to do this (one of the main advantages over npm and something that other projects like npm-shrinkwrap have tried to address.
As the yarn docs say,
All yarn.lock files should be checked into source control (e.g. git or mercurial)
answered May 25 '17 at 20:14
Steve RiceSteve Rice
1086
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%2f42875288%2fshould-yarn-lock-and-yarnclean-file-follow-git-versioning%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
.yarnclean You can put into .gitignore file
You should add yarn.lock to your git, don't ignore it.
When you run either yarn or yarn add , Yarn will generate a yarn.lock file within the root directory of your package. You don’t need to read or understand this file - just check it into source control. When other people start using Yarn instead of npm, the yarn.lock file will ensure that they get precisely the same dependencies as you have.
answered Mar 21 '17 at 9:57
KasiriveniKasiriveni
1,9631126
add a comment |
.yarnclean You can put into .gitignore file
You should add yarn.lock to your git, don't ignore it.
When you run either yarn or yarn add , Yarn will generate a yarn.lock file within the root directory of your package. You don’t need to read or understand this file - just check it into source control. When other people start using Yarn instead of npm, the yarn.lock file will ensure that they get precisely the same dependencies as you have.
answered Mar 21 '17 at 9:57
KasiriveniKasiriveni
1,9631126
add a comment |
.yarnclean You can put into .gitignore file
You should add yarn.lock to your git, don't ignore it.
When you run either yarn or yarn add , Yarn will generate a yarn.lock file within the root directory of your package. You don’t need to read or understand this file - just check it into source control. When other people start using Yarn instead of npm, the yarn.lock file will ensure that they get precisely the same dependencies as you have.
answered Mar 21 '17 at 9:57
KasiriveniKasiriveni
1,9631126
.yarnclean You can put into .gitignore file
You should add yarn.lock to your git, don't ignore it.
When you run either yarn or yarn add , Yarn will generate a yarn.lock file within the root directory of your package. You don’t need to read or understand this file - just check it into source control. When other people start using Yarn instead of npm, the yarn.lock file will ensure that they get precisely the same dependencies as you have.
answered Mar 21 '17 at 9:57
KasiriveniKasiriveni
1,9631126
answered Mar 21 '17 at 9:57
KasiriveniKasiriveni
1,9631126
answered Mar 21 '17 at 9:57
KasiriveniKasiriveni
1,9631126
answered Mar 21 '17 at 9:57
KasiriveniKasiriveni
1,9631126
1,9631126
add a comment |
add a comment |
Both files should be part of your version control.
.yarnclean is generated by running the yarn clean command. From the docs:
Yarn will create a
.yarncleanfile that should be added to version control.
yarn.lock is used to get consistent installs of dependencies across machines — it contains extra information that package.json does not which allows yarn to do this (one of the main advantages over npm and something that other projects like npm-shrinkwrap have tried to address.
As the yarn docs say,
All yarn.lock files should be checked into source control (e.g. git or mercurial)
answered May 25 '17 at 20:14
Steve RiceSteve Rice
1086
add a comment |
Both files should be part of your version control.
.yarnclean is generated by running the yarn clean command. From the docs:
Yarn will create a
.yarncleanfile that should be added to version control.
yarn.lock is used to get consistent installs of dependencies across machines — it contains extra information that package.json does not which allows yarn to do this (one of the main advantages over npm and something that other projects like npm-shrinkwrap have tried to address.
As the yarn docs say,
All yarn.lock files should be checked into source control (e.g. git or mercurial)
answered May 25 '17 at 20:14
Steve RiceSteve Rice
1086
add a comment |
Both files should be part of your version control.
.yarnclean is generated by running the yarn clean command. From the docs:
Yarn will create a
.yarncleanfile that should be added to version control.
yarn.lock is used to get consistent installs of dependencies across machines — it contains extra information that package.json does not which allows yarn to do this (one of the main advantages over npm and something that other projects like npm-shrinkwrap have tried to address.
As the yarn docs say,
All yarn.lock files should be checked into source control (e.g. git or mercurial)
answered May 25 '17 at 20:14
Steve RiceSteve Rice
1086
Both files should be part of your version control.
.yarnclean is generated by running the yarn clean command. From the docs:
Yarn will create a
.yarncleanfile that should be added to version control.
yarn.lock is used to get consistent installs of dependencies across machines — it contains extra information that package.json does not which allows yarn to do this (one of the main advantages over npm and something that other projects like npm-shrinkwrap have tried to address.
As the yarn docs say,
All yarn.lock files should be checked into source control (e.g. git or mercurial)
answered May 25 '17 at 20:14
Steve RiceSteve Rice
1086
answered May 25 '17 at 20:14
Steve RiceSteve Rice
1086
answered May 25 '17 at 20:14
Steve RiceSteve Rice
1086
answered May 25 '17 at 20:14
Steve RiceSteve Rice
1086
1086
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%2f42875288%2fshould-yarn-lock-and-yarnclean-file-follow-git-versioning%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
