Mixing
How to exclude a module from the package-lock.json?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
How to exclude a module from the package-lock.json?
I need to exclude an specific module in order to not be versioned in the package-lock.json. Is this possible?
My problem is that I have a local module (packaged in a different project). For my convenience, I always export this module with the same name: localmodule-1.1.1.tgz.
Then I import it in another project like that:
...
"dependencies": {
"localmodule": "file:../LocalModule/dist/localmodule-1.1.1.tgz"
},
...
Every time I change the contents of the module, the project that is importing it breaks with the error Unhandled rejection Error: Integrity check failed. The checksum doesn't match because the content has changed (the checksum is stored in the package-lock.json).
Is it possible to not include this module inside the package-lock.json?
I would like to avoid changing the name of the module every time I change any of its contents.
Disclaimer: I am not talking about the versioning of the package-lock.json. The file will be versioned. I am just interested in excluding an specific module from the content of the file itself.
node.js npm
asked Jan 3 at 7:28
miqrcmiqrc
17029
add a comment |
How to exclude a module from the package-lock.json?
I need to exclude an specific module in order to not be versioned in the package-lock.json. Is this possible?
My problem is that I have a local module (packaged in a different project). For my convenience, I always export this module with the same name: localmodule-1.1.1.tgz.
Then I import it in another project like that:
...
"dependencies": {
"localmodule": "file:../LocalModule/dist/localmodule-1.1.1.tgz"
},
...
Every time I change the contents of the module, the project that is importing it breaks with the error Unhandled rejection Error: Integrity check failed. The checksum doesn't match because the content has changed (the checksum is stored in the package-lock.json).
Is it possible to not include this module inside the package-lock.json?
I would like to avoid changing the name of the module every time I change any of its contents.
Disclaimer: I am not talking about the versioning of the package-lock.json. The file will be versioned. I am just interested in excluding an specific module from the content of the file itself.
node.js npm
asked Jan 3 at 7:28
miqrcmiqrc
17029
just don't save the dependency then ¯_(ツ)_/¯
– GottZ
Jan 3 at 7:32
What do you mean? I need this dependency and it should be included in the package.json to be installed with an ¨npm install¨. If you are referring to install it manually every time it is not really a solution.
– miqrc
Jan 3 at 8:33
add a comment |
How to exclude a module from the package-lock.json?
I need to exclude an specific module in order to not be versioned in the package-lock.json. Is this possible?
My problem is that I have a local module (packaged in a different project). For my convenience, I always export this module with the same name: localmodule-1.1.1.tgz.
Then I import it in another project like that:
...
"dependencies": {
"localmodule": "file:../LocalModule/dist/localmodule-1.1.1.tgz"
},
...
Every time I change the contents of the module, the project that is importing it breaks with the error Unhandled rejection Error: Integrity check failed. The checksum doesn't match because the content has changed (the checksum is stored in the package-lock.json).
Is it possible to not include this module inside the package-lock.json?
I would like to avoid changing the name of the module every time I change any of its contents.
Disclaimer: I am not talking about the versioning of the package-lock.json. The file will be versioned. I am just interested in excluding an specific module from the content of the file itself.
node.js npm
asked Jan 3 at 7:28
miqrcmiqrc
17029
How to exclude a module from the package-lock.json?
I need to exclude an specific module in order to not be versioned in the package-lock.json. Is this possible?
My problem is that I have a local module (packaged in a different project). For my convenience, I always export this module with the same name: localmodule-1.1.1.tgz.
Then I import it in another project like that:
...
"dependencies": {
"localmodule": "file:../LocalModule/dist/localmodule-1.1.1.tgz"
},
...
Every time I change the contents of the module, the project that is importing it breaks with the error Unhandled rejection Error: Integrity check failed. The checksum doesn't match because the content has changed (the checksum is stored in the package-lock.json).
Is it possible to not include this module inside the package-lock.json?
I would like to avoid changing the name of the module every time I change any of its contents.
Disclaimer: I am not talking about the versioning of the package-lock.json. The file will be versioned. I am just interested in excluding an specific module from the content of the file itself.
node.js npm
node.js npm
asked Jan 3 at 7:28
miqrcmiqrc
17029
asked Jan 3 at 7:28
miqrcmiqrc
17029
asked Jan 3 at 7:28
miqrcmiqrc
17029
asked Jan 3 at 7:28
miqrcmiqrc
17029
asked Jan 3 at 7:28
miqrcmiqrc
17029
17029
just don't save the dependency then ¯_(ツ)_/¯
– GottZ
Jan 3 at 7:32
What do you mean? I need this dependency and it should be included in the package.json to be installed with an ¨npm install¨. If you are referring to install it manually every time it is not really a solution.
– miqrc
Jan 3 at 8:33
add a comment |
just don't save the dependency then ¯_(ツ)_/¯
– GottZ
Jan 3 at 7:32
What do you mean? I need this dependency and it should be included in the package.json to be installed with an ¨npm install¨. If you are referring to install it manually every time it is not really a solution.
– miqrc
Jan 3 at 8:33
just don't save the dependency then ¯_(ツ)_/¯
– GottZ
Jan 3 at 7:32
just don't save the dependency then ¯_(ツ)_/¯
– GottZ
Jan 3 at 7:32
What do you mean? I need this dependency and it should be included in the package.json to be installed with an ¨npm install¨. If you are referring to install it manually every time it is not really a solution.
– miqrc
Jan 3 at 8:33
What do you mean? I need this dependency and it should be included in the package.json to be installed with an ¨npm install¨. If you are referring to install it manually every time it is not really a solution.
– miqrc
Jan 3 at 8:33
add a comment |
0
active
oldest
votes
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%2f54018043%2fhow-to-exclude-a-module-from-the-package-lock-json%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
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%2f54018043%2fhow-to-exclude-a-module-from-the-package-lock-json%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
just don't save the dependency then ¯_(ツ)_/¯
– GottZ
Jan 3 at 7:32
What do you mean? I need this dependency and it should be included in the package.json to be installed with an ¨npm install¨. If you are referring to install it manually every time it is not really a solution.
– miqrc
Jan 3 at 8:33