NPM lockfiles/shrinkwrap get random “dl” parameter tacked on to the “resolved” URL
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
Our company uses an Artifactory repository for storing internally-published packages and as a proxy for the NPM registry. Sometimes the resolved field in lockfiles/shrinkwrap files is as expected, containing URLs for our internal repository, but occasionally they show up as something like this (line break added for clarity):
https://our.repository.com/artifactory/api/npm/some-repo/lodash/-/lodash-3.10.1.tgz
?dl=https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz
Then, from pull request to pull requests, these dl parameters constantly oscillate to being present or removed depending on which developer does an npm install, leading to a lot of pull request & commit noise.
I'm guessing it's Artifactory that's adding this dl param, since I fail to see it in a code search in the npm code base.
Why does this happen? Can we disable this behavior? And is it safe to strip this parameter as a postshrinkwrap script workaround?
npm artifactory lockfile npm-shrinkwrap
asked Nov 2 '18 at 23:57
JacobJacob
57.1k19118195
add a comment |
Our company uses an Artifactory repository for storing internally-published packages and as a proxy for the NPM registry. Sometimes the resolved field in lockfiles/shrinkwrap files is as expected, containing URLs for our internal repository, but occasionally they show up as something like this (line break added for clarity):
https://our.repository.com/artifactory/api/npm/some-repo/lodash/-/lodash-3.10.1.tgz
?dl=https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz
Then, from pull request to pull requests, these dl parameters constantly oscillate to being present or removed depending on which developer does an npm install, leading to a lot of pull request & commit noise.
I'm guessing it's Artifactory that's adding this dl param, since I fail to see it in a code search in the npm code base.
Why does this happen? Can we disable this behavior? And is it safe to strip this parameter as a postshrinkwrap script workaround?
npm artifactory lockfile npm-shrinkwrap
asked Nov 2 '18 at 23:57
JacobJacob
57.1k19118195
1
Hey Jacob! did you progress on that by any chance?
– ciekawy
Nov 16 '18 at 17:10
1
Nope, it's still a mystery. Will try a bounty.
– Jacob
Nov 16 '18 at 18:25
1
@ciekawy: What's your setup? Maybe there's some common elements with our org that will help us narrow it down?
– Jacob
Nov 16 '18 at 21:50
We're just suffering from this as a dev team so I am not sure about the artifactory setup. Raised that on our company slack - will follow up upon any new info.
– ciekawy
Nov 16 '18 at 22:11
I am having this same problem with my company's artifactory as well.
– Tri Nguyen
Feb 11 at 20:32
add a comment |
Our company uses an Artifactory repository for storing internally-published packages and as a proxy for the NPM registry. Sometimes the resolved field in lockfiles/shrinkwrap files is as expected, containing URLs for our internal repository, but occasionally they show up as something like this (line break added for clarity):
https://our.repository.com/artifactory/api/npm/some-repo/lodash/-/lodash-3.10.1.tgz
?dl=https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz
Then, from pull request to pull requests, these dl parameters constantly oscillate to being present or removed depending on which developer does an npm install, leading to a lot of pull request & commit noise.
I'm guessing it's Artifactory that's adding this dl param, since I fail to see it in a code search in the npm code base.
Why does this happen? Can we disable this behavior? And is it safe to strip this parameter as a postshrinkwrap script workaround?
npm artifactory lockfile npm-shrinkwrap
asked Nov 2 '18 at 23:57
JacobJacob
57.1k19118195
Our company uses an Artifactory repository for storing internally-published packages and as a proxy for the NPM registry. Sometimes the resolved field in lockfiles/shrinkwrap files is as expected, containing URLs for our internal repository, but occasionally they show up as something like this (line break added for clarity):
https://our.repository.com/artifactory/api/npm/some-repo/lodash/-/lodash-3.10.1.tgz
?dl=https://registry.npmjs.org/lodash/-/lodash-3.10.1.tgz
Then, from pull request to pull requests, these dl parameters constantly oscillate to being present or removed depending on which developer does an npm install, leading to a lot of pull request & commit noise.
I'm guessing it's Artifactory that's adding this dl param, since I fail to see it in a code search in the npm code base.
Why does this happen? Can we disable this behavior? And is it safe to strip this parameter as a postshrinkwrap script workaround?
npm artifactory lockfile npm-shrinkwrap
npm artifactory lockfile npm-shrinkwrap
asked Nov 2 '18 at 23:57
JacobJacob
57.1k19118195
asked Nov 2 '18 at 23:57
JacobJacob
57.1k19118195
asked Nov 2 '18 at 23:57
JacobJacob
57.1k19118195
asked Nov 2 '18 at 23:57
JacobJacob
57.1k19118195
asked Nov 2 '18 at 23:57
JacobJacob
57.1k19118195
57.1k19118195
1
Hey Jacob! did you progress on that by any chance?
– ciekawy
Nov 16 '18 at 17:10
1
Nope, it's still a mystery. Will try a bounty.
– Jacob
Nov 16 '18 at 18:25
1
@ciekawy: What's your setup? Maybe there's some common elements with our org that will help us narrow it down?
– Jacob
Nov 16 '18 at 21:50
We're just suffering from this as a dev team so I am not sure about the artifactory setup. Raised that on our company slack - will follow up upon any new info.
– ciekawy
Nov 16 '18 at 22:11
I am having this same problem with my company's artifactory as well.
– Tri Nguyen
Feb 11 at 20:32
add a comment |
1
Hey Jacob! did you progress on that by any chance?
– ciekawy
Nov 16 '18 at 17:10
1
Nope, it's still a mystery. Will try a bounty.
– Jacob
Nov 16 '18 at 18:25
1
@ciekawy: What's your setup? Maybe there's some common elements with our org that will help us narrow it down?
– Jacob
Nov 16 '18 at 21:50
We're just suffering from this as a dev team so I am not sure about the artifactory setup. Raised that on our company slack - will follow up upon any new info.
– ciekawy
Nov 16 '18 at 22:11
I am having this same problem with my company's artifactory as well.
– Tri Nguyen
Feb 11 at 20:32
1
1
Hey Jacob! did you progress on that by any chance?
– ciekawy
Nov 16 '18 at 17:10
Hey Jacob! did you progress on that by any chance?
– ciekawy
Nov 16 '18 at 17:10
1
1
Nope, it's still a mystery. Will try a bounty.
– Jacob
Nov 16 '18 at 18:25
Nope, it's still a mystery. Will try a bounty.
– Jacob
Nov 16 '18 at 18:25
1
1
@ciekawy: What's your setup? Maybe there's some common elements with our org that will help us narrow it down?
– Jacob
Nov 16 '18 at 21:50
@ciekawy: What's your setup? Maybe there's some common elements with our org that will help us narrow it down?
– Jacob
Nov 16 '18 at 21:50
We're just suffering from this as a dev team so I am not sure about the artifactory setup. Raised that on our company slack - will follow up upon any new info.
– ciekawy
Nov 16 '18 at 22:11
We're just suffering from this as a dev team so I am not sure about the artifactory setup. Raised that on our company slack - will follow up upon any new info.
– ciekawy
Nov 16 '18 at 22:11
I am having this same problem with my company's artifactory as well.
– Tri Nguyen
Feb 11 at 20:32
I am having this same problem with my company's artifactory as well.
– Tri Nguyen
Feb 11 at 20:32
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%2f53127140%2fnpm-lockfiles-shrinkwrap-get-random-dl-parameter-tacked-on-to-the-resolved-u%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%2f53127140%2fnpm-lockfiles-shrinkwrap-get-random-dl-parameter-tacked-on-to-the-resolved-u%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
1
Hey Jacob! did you progress on that by any chance?
– ciekawy
Nov 16 '18 at 17:10
1
Nope, it's still a mystery. Will try a bounty.
– Jacob
Nov 16 '18 at 18:25
1
@ciekawy: What's your setup? Maybe there's some common elements with our org that will help us narrow it down?
– Jacob
Nov 16 '18 at 21:50
We're just suffering from this as a dev team so I am not sure about the artifactory setup. Raised that on our company slack - will follow up upon any new info.
– ciekawy
Nov 16 '18 at 22:11
I am having this same problem with my company's artifactory as well.
– Tri Nguyen
Feb 11 at 20:32