Repository navigation
Publish in custom artifactory #424
Description
After spending lot of time, I looked into the code & found that, the regex pattern is always matching for only registries pointing to npm. In my case we have a custom artifactory the URL that looks like //art01.spotifycloud.io
Lines 62 to 64 in 31ff97e
Suggested solution
we can generalized the Regex and avoid hardcoding
const authLine = userNpmrcContent.split("\n").find((line) => {
// Dynamically adapt to any registry by looking for :_authToken= pattern
return /^\s*\/\/.*\/:[_-]authToken=/i.test(line);
});
Activity
fix: changesets#424 - Publish in custom artifactory
fix Publish in custom artifactory changesets#424
Andarist commentedon Nov 21, 2024
Shouldn't it just work if you create
.npmrcwith a content like this?I don't understand when the logic falls apart right now.
gethari commentedon Nov 21, 2024
@Andarist , I already had created my
.npmrcas you suggested, but the catch here I forgot to highlight is, I am using a Auth_authvariable & not_authToken& I think that is also one of the reason's the code is going into theelse..conditionI have updated my PR for this fix as well, thanks for the input 👍
fix: Publish in custom artifactory changesets#424 with `auth` or `aut…