Skip to content

[BUG] npm publish uses different registry then npm unpublish #559

Closed
Closed
[BUG] npm publish uses different registry then npm unpublish#559
Labels
Bugthing that needs fixing

Description

@mbazalik
mbazalik
opened on Dec 5, 2019

What / Why

This seems to be a duplicate of npm/npm#3032 even though the last comment claims the problem is resolved

In short, when the package contains both .npmrc and publishConfig setup it seems that npm publish is respecting setup from publishConfig while npm unpublish is using .npmrc

When

The project is using both .npmrc to define which registry to use to pull packages from and publishConfig to define to which registry the package should be pushed to

Example:
.npmrc

@dazn:registry=https://example.com/

package.json

{
..."name": "@dazn/daznid",
"version": "2.0.1-rc00002",
"publishConfig": {
"@dazn:registry": "https://registry.npmjs.org/",
"access": "restricted"
},
...
}

npm publish --loglevel verbose output:

npm publish --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'publish',
npm verb cli '--loglevel',
npm verb cli 'verbose' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm verb npm-session 7920cfe554e24b7a
npm verb publish [ '.' ]
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublish: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepare: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run build:prod (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepack: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpack: @dazn/daznid@2.0.1-rc00002
npm notice npm notice package: @dazn/daznid@2.0.1-rc00002
npm notice === Tarball Contents === npm notice 314B dist/index.html
npm notice 21.8kB dist/daznid.js npm notice 1.3kB package.json npm notice 1.3kB README.md npm notice 117B CHANGELOG.yml npm notice === Tarball Details === npm notice name: @dazn/daznid npm notice version: 2.0.1-rc00002 npm notice package size: 9.4 kB npm notice unpacked size: 24.8 kB npm notice shasum: 94bbabe79081807a6d768a9eb5debf282a969c00
npm notice integrity: sha512-6GW6ARu37UeAm[...]gSjZ6cxVvXkRw==
npm notice total files: 5 npm notice npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms
npm info lifecycle @dazn/daznid@2.0.1-rc00002~publish: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~publish: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run publish:ftp & git push --tags (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpublish: @dazn/daznid@2.0.1-rc00002
+ @dazn/daznid@2.0.1-rc00002
npm verb exit [ 0, true ]
npm timing npm Completed in 4073ms
npm info ok

npm unpublish -f --loglevel verbose @dazn/daznid@2.0.1-rc00002

npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'unpublish',
npm verb cli '-f',
npm verb cli '--loglevel',
npm verb cli 'verbose',
npm verb cli '@dazn/daznid@2.0.1-rc00002' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm WARN using --force I sure hope you know what you are doing.
npm verb npm-session 9f0285a83a8cd55c
npm http fetch GET 401 https://example.com/@dazn%2fdaznid?write=true 105ms
npm verb stack Error: Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb stack at res.buffer.catch.then.body (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
npm verb stack at process._tickCallback (internal/process/next_tick.js:68:7)
npm verb statusCode 401
npm verb pkgid @dazn/daznid@2.0.1-rc00002
npm verb cwd /drone/src/github.com/getndazn/com-daznid
npm verb Linux 4.14.128-87.105.amzn1.x86_64
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "unpublish" "-f" "--loglevel" "verbose" "@dazn/daznid@2.0.1-rc00002"
npm verb node v10.17.0
npm verb npm v6.11.3
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb exit [ 1, true ]
npm timing npm Completed in 328ms
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-05T15_17_19_217Z-debug.log

Where

  • npm enterprise

Current Behavior

npm publish uses registry defined in publishConfig
NOTICE npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms in above example

npm unpublish uses registry defined in .npmrc
NOTICE npm http fetch GET 401 https://example.com/`@dazn%2fdaznid?write=true 105ms

Steps to Reproduce

See above

Expected Behavior

npm publish and npm unpublish to use same setup (preferably one which allow to have different registry for pull and push)

Who

  • n/a

References

Related to npm/npm#3032

Metadata

Metadata

Assignees

No one assigned

    Labels

    Bugthing that needs fixing

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

      , 'i'); if (__m === '*' || __re.test(location.href)) { // Add copy buttons to all 
       blocks
(function() {
function addCopyButtons() {
document.querySelectorAll('pre code').forEach(function(codeBlock) {
if (codeBlock.parentElement.hasAttribute('data-copy-added')) return;
codeBlock.parentElement.setAttribute('data-copy-added', 'true');
var btn = document.createElement('button');
btn.textContent = 'Copy';
btn.style.cssText = 'position:absolute;top:4px;right:4px;padding:2px 8px;font-size:11px;background:#4ecdc4;border:none;border-radius:4px;color:#1a1a2e;cursor:pointer;opacity:0.7;transition:opacity 0.2s;';
btn.onmouseover = function() { this.style.opacity = '1'; };
btn.onmouseout = function() { this.style.opacity = '0.7'; };
btn.onclick = function() {
navigator.clipboard.writeText(codeBlock.textContent).then(function() {
btn.textContent = 'Copied!';
setTimeout(function() { btn.textContent = 'Copy'; }, 1500);
});
};
codeBlock.parentElement.style.position = 'relative';
codeBlock.parentElement.appendChild(btn);
});
}
addCopyButtons();
// Re-run on dynamic content
var observer = new MutationObserver(addCopyButtons);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Add Copy Buttons to Code Blocks]', __e); }
})();
(function(){
try {
var __m = "github.com";
var __re = new RegExp('^' + "github\\.com" + '
[BUG] `npm publish` uses different registry then `npm unpublish` · Issue #559 · npm/cli · GitHub
      Skip to content
      [BUG] npm publish uses different registry then npm unpublish #559
      Closed
      Closed
      [BUG] npm publish uses different registry then npm unpublish#559
      Labels
      Bugthing that needs fixing
      Description
      @mbazalik
      mbazalik
      opened on Dec 5, 2019
      What / Why
      This seems to be a duplicate of npm/npm#3032 even though the last comment claims the problem is resolved
      In short, when the package contains both .npmrc and publishConfig setup it seems that npm publish is respecting setup from publishConfig while npm unpublish is using .npmrc
      When
      The project is using both .npmrc to define which registry to use to pull packages from and publishConfig to define to which registry the package should be pushed to
      Example:
      
.npmrc
      @dazn:registry=https://example.com/

      package.json
      {
..."name": "@dazn/daznid",
"version": "2.0.1-rc00002",
"publishConfig": {
"@dazn:registry": "https://registry.npmjs.org/",
"access": "restricted"
},
...
}
      npm publish --loglevel verbose output:
      npm publish --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'publish',
npm verb cli '--loglevel',
npm verb cli 'verbose' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm verb npm-session 7920cfe554e24b7a
npm verb publish [ '.' ]
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublish: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepare: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run build:prod (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepack: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpack: @dazn/daznid@2.0.1-rc00002
npm notice npm notice package: @dazn/daznid@2.0.1-rc00002
npm notice === Tarball Contents === npm notice 314B dist/index.html
npm notice 21.8kB dist/daznid.js npm notice 1.3kB package.json npm notice 1.3kB README.md npm notice 117B CHANGELOG.yml npm notice === Tarball Details === npm notice name: @dazn/daznid npm notice version: 2.0.1-rc00002 npm notice package size: 9.4 kB npm notice unpacked size: 24.8 kB npm notice shasum: 94bbabe79081807a6d768a9eb5debf282a969c00
npm notice integrity: sha512-6GW6ARu37UeAm[...]gSjZ6cxVvXkRw==
npm notice total files: 5 npm notice npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms
npm info lifecycle @dazn/daznid@2.0.1-rc00002~publish: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~publish: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run publish:ftp & git push --tags (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpublish: @dazn/daznid@2.0.1-rc00002
+ @dazn/daznid@2.0.1-rc00002
npm verb exit [ 0, true ]
npm timing npm Completed in 4073ms
npm info ok 
      npm unpublish -f --loglevel verbose @dazn/daznid@2.0.1-rc00002
      npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'unpublish',
npm verb cli '-f',
npm verb cli '--loglevel',
npm verb cli 'verbose',
npm verb cli '@dazn/daznid@2.0.1-rc00002' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm WARN using --force I sure hope you know what you are doing.
npm verb npm-session 9f0285a83a8cd55c
npm http fetch GET 401 https://example.com/@dazn%2fdaznid?write=true 105ms
npm verb stack Error: Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb stack at res.buffer.catch.then.body (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
npm verb stack at process._tickCallback (internal/process/next_tick.js:68:7)
npm verb statusCode 401
npm verb pkgid @dazn/daznid@2.0.1-rc00002
npm verb cwd /drone/src/github.com/getndazn/com-daznid
npm verb Linux 4.14.128-87.105.amzn1.x86_64
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "unpublish" "-f" "--loglevel" "verbose" "@dazn/daznid@2.0.1-rc00002"
npm verb node v10.17.0
npm verb npm v6.11.3
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb exit [ 1, true ]
npm timing npm Completed in 328ms
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-05T15_17_19_217Z-debug.log

      Where
      • npm enterprise
      Current Behavior
      npm publish uses registry defined in publishConfig
      
NOTICE npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms in above example
      npm unpublish uses registry defined in .npmrc
      
NOTICE npm http fetch GET 401 https://example.com/`@dazn%2fdaznid?write=true 105ms
      Steps to Reproduce
      See above
      Expected Behavior
      npm publish and npm unpublish to use same setup (preferably one which allow to have different registry for pull and push)
      Who
      • n/a
      References
      Related to npm/npm#3032
      Metadata
      Metadata
      Assignees
      No one assigned
        Labels
        Bugthing that needs fixing
        Type
        No type
        Projects
        No projects
          Milestone
          No milestone
          Relationships
          None yet
          Development
          No branches or pull requests
          Issue actions
          
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Force GitHub README to respect dark mode
(function() {
var style = document.createElement('style');
style.textContent = '
.markdown-body {
color-scheme: dark light;
}
.markdown-body pre { background: #161b22 !important; }
.markdown-body code { background: rgba(110, 118, 129, 0.4) !important; }
.markdown-body table th, .markdown-body table td { border-color: #30363d !important; }
.markdown-body img { background: #0d1117; }
.markdown-body blockquote { border-left-color: #8b949e; }
.markdown-body hr { border-color: #30363d; }
';
document.head.appendChild(style);
})();
}
} catch(__e) { console.warn('[Userscript:GitHub Dark Mode README Fix]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[BUG] `npm publish` uses different registry then `npm unpublish` · Issue #559 · npm/cli · GitHub
          Skip to content
          [BUG] npm publish uses different registry then npm unpublish #559
          Closed
          Closed
          [BUG] npm publish uses different registry then npm unpublish#559
          Labels
          Bugthing that needs fixing
          Description
          @mbazalik
          mbazalik
          opened on Dec 5, 2019
          What / Why
          This seems to be a duplicate of npm/npm#3032 even though the last comment claims the problem is resolved
          In short, when the package contains both .npmrc and publishConfig setup it seems that npm publish is respecting setup from publishConfig while npm unpublish is using .npmrc
          When
          The project is using both .npmrc to define which registry to use to pull packages from and publishConfig to define to which registry the package should be pushed to
          Example:
          
.npmrc
          @dazn:registry=https://example.com/

          package.json
          {
..."name": "@dazn/daznid",
"version": "2.0.1-rc00002",
"publishConfig": {
"@dazn:registry": "https://registry.npmjs.org/",
"access": "restricted"
},
...
}
          npm publish --loglevel verbose output:
          npm publish --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'publish',
npm verb cli '--loglevel',
npm verb cli 'verbose' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm verb npm-session 7920cfe554e24b7a
npm verb publish [ '.' ]
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublish: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepare: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run build:prod (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepack: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpack: @dazn/daznid@2.0.1-rc00002
npm notice npm notice package: @dazn/daznid@2.0.1-rc00002
npm notice === Tarball Contents === npm notice 314B dist/index.html
npm notice 21.8kB dist/daznid.js npm notice 1.3kB package.json npm notice 1.3kB README.md npm notice 117B CHANGELOG.yml npm notice === Tarball Details === npm notice name: @dazn/daznid npm notice version: 2.0.1-rc00002 npm notice package size: 9.4 kB npm notice unpacked size: 24.8 kB npm notice shasum: 94bbabe79081807a6d768a9eb5debf282a969c00
npm notice integrity: sha512-6GW6ARu37UeAm[...]gSjZ6cxVvXkRw==
npm notice total files: 5 npm notice npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms
npm info lifecycle @dazn/daznid@2.0.1-rc00002~publish: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~publish: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run publish:ftp & git push --tags (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpublish: @dazn/daznid@2.0.1-rc00002
+ @dazn/daznid@2.0.1-rc00002
npm verb exit [ 0, true ]
npm timing npm Completed in 4073ms
npm info ok 
          npm unpublish -f --loglevel verbose @dazn/daznid@2.0.1-rc00002
          npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'unpublish',
npm verb cli '-f',
npm verb cli '--loglevel',
npm verb cli 'verbose',
npm verb cli '@dazn/daznid@2.0.1-rc00002' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm WARN using --force I sure hope you know what you are doing.
npm verb npm-session 9f0285a83a8cd55c
npm http fetch GET 401 https://example.com/@dazn%2fdaznid?write=true 105ms
npm verb stack Error: Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb stack at res.buffer.catch.then.body (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
npm verb stack at process._tickCallback (internal/process/next_tick.js:68:7)
npm verb statusCode 401
npm verb pkgid @dazn/daznid@2.0.1-rc00002
npm verb cwd /drone/src/github.com/getndazn/com-daznid
npm verb Linux 4.14.128-87.105.amzn1.x86_64
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "unpublish" "-f" "--loglevel" "verbose" "@dazn/daznid@2.0.1-rc00002"
npm verb node v10.17.0
npm verb npm v6.11.3
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb exit [ 1, true ]
npm timing npm Completed in 328ms
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-05T15_17_19_217Z-debug.log

          Where
          • npm enterprise
          Current Behavior
          npm publish uses registry defined in publishConfig
          
NOTICE npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms in above example
          npm unpublish uses registry defined in .npmrc
          
NOTICE npm http fetch GET 401 https://example.com/`@dazn%2fdaznid?write=true 105ms
          Steps to Reproduce
          See above
          Expected Behavior
          npm publish and npm unpublish to use same setup (preferably one which allow to have different registry for pull and push)
          Who
          • n/a
          References
          Related to npm/npm#3032
          Metadata
          Metadata
          Assignees
          No one assigned
            Labels
            Bugthing that needs fixing
            Type
            No type
            Projects
            No projects
              Milestone
              No milestone
              Relationships
              None yet
              Development
              No branches or pull requests
              Issue actions
              
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Highlight search terms from Google/DuckDuckGo/Bing referrer
(function() {
var ref = document.referrer;
var terms = [];
if (ref.includes('google.com') || ref.includes('duckduckgo.com') || ref.includes('bing.com')) {
var url = new URL(ref);
var q = url.searchParams.get('q') || url.searchParams.get('p');
if (q) {
terms = q.split(/\s+/).filter(function(t) { return t.length > 2; });
}
}
if (terms.length === 0) return;
var style = document.createElement('style');
style.textContent = '.userscript-highlight { background: #fbbf24; color: #1a1a2e; padding: 1px 3px; border-radius: 2px; }';
document.head.appendChild(style);
function highlight(node) {
if (node.nodeType === 3) { // text node
var text = node.textContent;
var found = false;
terms.forEach(function(term) {
var regex = new RegExp('(' + term.replace(/[.*+?^${}()|[\]\\]/g, '\\') + ')', 'gi');
if (regex.test(text)) {
found = true;
var frag = document.createDocumentFragment();
var parts = text.split(regex);
parts.forEach(function(part, i) {
if (i % 2 === 0) {
frag.appendChild(document.createTextNode(part));
} else {
var span = document.createElement('span');
span.className = 'userscript-highlight';
span.textContent = part;
frag.appendChild(span);
}
});
node.parentNode.replaceChild(frag, node);
}
});
} else if (node.nodeType === 1 && node.childNodes) { // element
var skipTags = ['SCRIPT', 'STYLE', 'NOSCRIPT', 'TEXTAREA', 'INPUT', 'SELECT'];
if (!skipTags.includes(node.tagName)) {
Array.from(node.childNodes).forEach(highlight);
}
}
}
highlight(document.body);
// Re-highlight on dynamic content
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1 || node.nodeType === 3) highlight(node);
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Highlight Search Terms]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[BUG] `npm publish` uses different registry then `npm unpublish` · Issue #559 · npm/cli · GitHub
              Skip to content
              [BUG] npm publish uses different registry then npm unpublish #559
              Closed
              Closed
              [BUG] npm publish uses different registry then npm unpublish#559
              Labels
              Bugthing that needs fixing
              Description
              @mbazalik
              mbazalik
              opened on Dec 5, 2019
              What / Why
              This seems to be a duplicate of npm/npm#3032 even though the last comment claims the problem is resolved
              In short, when the package contains both .npmrc and publishConfig setup it seems that npm publish is respecting setup from publishConfig while npm unpublish is using .npmrc
              When
              The project is using both .npmrc to define which registry to use to pull packages from and publishConfig to define to which registry the package should be pushed to
              Example:
              
.npmrc
              @dazn:registry=https://example.com/

              package.json
              {
..."name": "@dazn/daznid",
"version": "2.0.1-rc00002",
"publishConfig": {
"@dazn:registry": "https://registry.npmjs.org/",
"access": "restricted"
},
...
}
              npm publish --loglevel verbose output:
              npm publish --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'publish',
npm verb cli '--loglevel',
npm verb cli 'verbose' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm verb npm-session 7920cfe554e24b7a
npm verb publish [ '.' ]
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublish: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepare: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run build:prod (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepack: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpack: @dazn/daznid@2.0.1-rc00002
npm notice npm notice package: @dazn/daznid@2.0.1-rc00002
npm notice === Tarball Contents === npm notice 314B dist/index.html
npm notice 21.8kB dist/daznid.js npm notice 1.3kB package.json npm notice 1.3kB README.md npm notice 117B CHANGELOG.yml npm notice === Tarball Details === npm notice name: @dazn/daznid npm notice version: 2.0.1-rc00002 npm notice package size: 9.4 kB npm notice unpacked size: 24.8 kB npm notice shasum: 94bbabe79081807a6d768a9eb5debf282a969c00
npm notice integrity: sha512-6GW6ARu37UeAm[...]gSjZ6cxVvXkRw==
npm notice total files: 5 npm notice npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms
npm info lifecycle @dazn/daznid@2.0.1-rc00002~publish: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~publish: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run publish:ftp & git push --tags (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpublish: @dazn/daznid@2.0.1-rc00002
+ @dazn/daznid@2.0.1-rc00002
npm verb exit [ 0, true ]
npm timing npm Completed in 4073ms
npm info ok 
              npm unpublish -f --loglevel verbose @dazn/daznid@2.0.1-rc00002
              npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'unpublish',
npm verb cli '-f',
npm verb cli '--loglevel',
npm verb cli 'verbose',
npm verb cli '@dazn/daznid@2.0.1-rc00002' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm WARN using --force I sure hope you know what you are doing.
npm verb npm-session 9f0285a83a8cd55c
npm http fetch GET 401 https://example.com/@dazn%2fdaznid?write=true 105ms
npm verb stack Error: Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb stack at res.buffer.catch.then.body (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
npm verb stack at process._tickCallback (internal/process/next_tick.js:68:7)
npm verb statusCode 401
npm verb pkgid @dazn/daznid@2.0.1-rc00002
npm verb cwd /drone/src/github.com/getndazn/com-daznid
npm verb Linux 4.14.128-87.105.amzn1.x86_64
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "unpublish" "-f" "--loglevel" "verbose" "@dazn/daznid@2.0.1-rc00002"
npm verb node v10.17.0
npm verb npm v6.11.3
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb exit [ 1, true ]
npm timing npm Completed in 328ms
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-05T15_17_19_217Z-debug.log

              Where
              • npm enterprise
              Current Behavior
              npm publish uses registry defined in publishConfig
              
NOTICE npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms in above example
              npm unpublish uses registry defined in .npmrc
              
NOTICE npm http fetch GET 401 https://example.com/`@dazn%2fdaznid?write=true 105ms
              Steps to Reproduce
              See above
              Expected Behavior
              npm publish and npm unpublish to use same setup (preferably one which allow to have different registry for pull and push)
              Who
              • n/a
              References
              Related to npm/npm#3032
              Metadata
              Metadata
              Assignees
              No one assigned
                Labels
                Bugthing that needs fixing
                Type
                No type
                Projects
                No projects
                  Milestone
                  No milestone
                  Relationships
                  None yet
                  Development
                  No branches or pull requests
                  Issue actions
                  
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Strip utm_, fbclid, gclid, etc. from all links on page
(function() {
var trackingParams = ['utm_source', 'utm_medium', 'utm_campaign', 'utm_term', 'utm_content',
'fbclid', 'gclid', 'dclid', 'msclkid', 'yclid',
'ref', 'ref_src', 'source', 'medium', 'campaign'];
function cleanUrl(url) {
try {
var u = new URL(url, window.location.origin);
var changed = false;
trackingParams.forEach(function(p) {
if (u.searchParams.has(p)) {
u.searchParams.delete(p);
changed = true;
}
});
return changed ? u.toString() : url;
} catch (e) {
return url;
}
}
function cleanLinks() {
document.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
cleanLinks();
var observer = new MutationObserver(function(mutations) {
mutations.forEach(function(m) {
m.addedNodes.forEach(function(node) {
if (node.nodeType === 1) {
if (node.tagName === 'A') cleanLinks();
node.querySelectorAll('a[href]').forEach(function(a) {
var clean = cleanUrl(a.href);
if (clean !== a.href) a.href = clean;
});
}
});
});
});
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:Remove Tracking Parameters from Links]', __e); }
})();
(function(){
try {
var __m = "youtube.com";
var __re = new RegExp('^' + "youtube\\.com" + '
[BUG] `npm publish` uses different registry then `npm unpublish` · Issue #559 · npm/cli · GitHub
                  Skip to content
                  [BUG] npm publish uses different registry then npm unpublish #559
                  Closed
                  Closed
                  [BUG] npm publish uses different registry then npm unpublish#559
                  Labels
                  Bugthing that needs fixing
                  Description
                  @mbazalik
                  mbazalik
                  opened on Dec 5, 2019
                  What / Why
                  This seems to be a duplicate of npm/npm#3032 even though the last comment claims the problem is resolved
                  In short, when the package contains both .npmrc and publishConfig setup it seems that npm publish is respecting setup from publishConfig while npm unpublish is using .npmrc
                  When
                  The project is using both .npmrc to define which registry to use to pull packages from and publishConfig to define to which registry the package should be pushed to
                  Example:
                  
.npmrc
                  @dazn:registry=https://example.com/

                  package.json
                  {
..."name": "@dazn/daznid",
"version": "2.0.1-rc00002",
"publishConfig": {
"@dazn:registry": "https://registry.npmjs.org/",
"access": "restricted"
},
...
}
                  npm publish --loglevel verbose output:
                  npm publish --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'publish',
npm verb cli '--loglevel',
npm verb cli 'verbose' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm verb npm-session 7920cfe554e24b7a
npm verb publish [ '.' ]
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublish: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepare: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run build:prod (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepack: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpack: @dazn/daznid@2.0.1-rc00002
npm notice npm notice package: @dazn/daznid@2.0.1-rc00002
npm notice === Tarball Contents === npm notice 314B dist/index.html
npm notice 21.8kB dist/daznid.js npm notice 1.3kB package.json npm notice 1.3kB README.md npm notice 117B CHANGELOG.yml npm notice === Tarball Details === npm notice name: @dazn/daznid npm notice version: 2.0.1-rc00002 npm notice package size: 9.4 kB npm notice unpacked size: 24.8 kB npm notice shasum: 94bbabe79081807a6d768a9eb5debf282a969c00
npm notice integrity: sha512-6GW6ARu37UeAm[...]gSjZ6cxVvXkRw==
npm notice total files: 5 npm notice npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms
npm info lifecycle @dazn/daznid@2.0.1-rc00002~publish: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~publish: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run publish:ftp & git push --tags (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpublish: @dazn/daznid@2.0.1-rc00002
+ @dazn/daznid@2.0.1-rc00002
npm verb exit [ 0, true ]
npm timing npm Completed in 4073ms
npm info ok 
                  npm unpublish -f --loglevel verbose @dazn/daznid@2.0.1-rc00002
                  npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'unpublish',
npm verb cli '-f',
npm verb cli '--loglevel',
npm verb cli 'verbose',
npm verb cli '@dazn/daznid@2.0.1-rc00002' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm WARN using --force I sure hope you know what you are doing.
npm verb npm-session 9f0285a83a8cd55c
npm http fetch GET 401 https://example.com/@dazn%2fdaznid?write=true 105ms
npm verb stack Error: Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb stack at res.buffer.catch.then.body (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
npm verb stack at process._tickCallback (internal/process/next_tick.js:68:7)
npm verb statusCode 401
npm verb pkgid @dazn/daznid@2.0.1-rc00002
npm verb cwd /drone/src/github.com/getndazn/com-daznid
npm verb Linux 4.14.128-87.105.amzn1.x86_64
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "unpublish" "-f" "--loglevel" "verbose" "@dazn/daznid@2.0.1-rc00002"
npm verb node v10.17.0
npm verb npm v6.11.3
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb exit [ 1, true ]
npm timing npm Completed in 328ms
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-05T15_17_19_217Z-debug.log

                  Where
                  • npm enterprise
                  Current Behavior
                  npm publish uses registry defined in publishConfig
                  
NOTICE npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms in above example
                  npm unpublish uses registry defined in .npmrc
                  
NOTICE npm http fetch GET 401 https://example.com/`@dazn%2fdaznid?write=true 105ms
                  Steps to Reproduce
                  See above
                  Expected Behavior
                  npm publish and npm unpublish to use same setup (preferably one which allow to have different registry for pull and push)
                  Who
                  • n/a
                  References
                  Related to npm/npm#3032
                  Metadata
                  Metadata
                  Assignees
                  No one assigned
                    Labels
                    Bugthing that needs fixing
                    Type
                    No type
                    Projects
                    No projects
                      Milestone
                      No milestone
                      Relationships
                      None yet
                      Development
                      No branches or pull requests
                      Issue actions
                      
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Auto-enable theater mode on YouTube
(function() {
function tryTheater() {
var btn = document.querySelector('button[aria-label="Theater mode"], ytd-player #player button[title="Theater mode"]');
if (btn && !btn.classList.contains('activated')) {
btn.click();
}
}
// Try immediately
tryTheater();
// Try after navigation (SPA)
var lastUrl = location.href;
setInterval(function() {
if (location.href !== lastUrl) {
lastUrl = location.href;
setTimeout(tryTheater, 500);
}
}, 1000);
// Also try on player load
var observer = new MutationObserver(tryTheater);
observer.observe(document.body, { childList: true, subtree: true });
})();
}
} catch(__e) { console.warn('[Userscript:YouTube Theater Mode Default]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[BUG] `npm publish` uses different registry then `npm unpublish` · Issue #559 · npm/cli · GitHub
                      Skip to content
                      [BUG] npm publish uses different registry then npm unpublish #559
                      Closed
                      Closed
                      [BUG] npm publish uses different registry then npm unpublish#559
                      Labels
                      Bugthing that needs fixing
                      Description
                      @mbazalik
                      mbazalik
                      opened on Dec 5, 2019
                      What / Why
                      This seems to be a duplicate of npm/npm#3032 even though the last comment claims the problem is resolved
                      In short, when the package contains both .npmrc and publishConfig setup it seems that npm publish is respecting setup from publishConfig while npm unpublish is using .npmrc
                      When
                      The project is using both .npmrc to define which registry to use to pull packages from and publishConfig to define to which registry the package should be pushed to
                      Example:
                      
.npmrc
                      @dazn:registry=https://example.com/

                      package.json
                      {
..."name": "@dazn/daznid",
"version": "2.0.1-rc00002",
"publishConfig": {
"@dazn:registry": "https://registry.npmjs.org/",
"access": "restricted"
},
...
}
                      npm publish --loglevel verbose output:
                      npm publish --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'publish',
npm verb cli '--loglevel',
npm verb cli 'verbose' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm verb npm-session 7920cfe554e24b7a
npm verb publish [ '.' ]
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublish: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepare: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run build:prod (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepack: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpack: @dazn/daznid@2.0.1-rc00002
npm notice npm notice package: @dazn/daznid@2.0.1-rc00002
npm notice === Tarball Contents === npm notice 314B dist/index.html
npm notice 21.8kB dist/daznid.js npm notice 1.3kB package.json npm notice 1.3kB README.md npm notice 117B CHANGELOG.yml npm notice === Tarball Details === npm notice name: @dazn/daznid npm notice version: 2.0.1-rc00002 npm notice package size: 9.4 kB npm notice unpacked size: 24.8 kB npm notice shasum: 94bbabe79081807a6d768a9eb5debf282a969c00
npm notice integrity: sha512-6GW6ARu37UeAm[...]gSjZ6cxVvXkRw==
npm notice total files: 5 npm notice npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms
npm info lifecycle @dazn/daznid@2.0.1-rc00002~publish: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~publish: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run publish:ftp & git push --tags (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpublish: @dazn/daznid@2.0.1-rc00002
+ @dazn/daznid@2.0.1-rc00002
npm verb exit [ 0, true ]
npm timing npm Completed in 4073ms
npm info ok 
                      npm unpublish -f --loglevel verbose @dazn/daznid@2.0.1-rc00002
                      npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'unpublish',
npm verb cli '-f',
npm verb cli '--loglevel',
npm verb cli 'verbose',
npm verb cli '@dazn/daznid@2.0.1-rc00002' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm WARN using --force I sure hope you know what you are doing.
npm verb npm-session 9f0285a83a8cd55c
npm http fetch GET 401 https://example.com/@dazn%2fdaznid?write=true 105ms
npm verb stack Error: Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb stack at res.buffer.catch.then.body (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
npm verb stack at process._tickCallback (internal/process/next_tick.js:68:7)
npm verb statusCode 401
npm verb pkgid @dazn/daznid@2.0.1-rc00002
npm verb cwd /drone/src/github.com/getndazn/com-daznid
npm verb Linux 4.14.128-87.105.amzn1.x86_64
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "unpublish" "-f" "--loglevel" "verbose" "@dazn/daznid@2.0.1-rc00002"
npm verb node v10.17.0
npm verb npm v6.11.3
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb exit [ 1, true ]
npm timing npm Completed in 328ms
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-05T15_17_19_217Z-debug.log

                      Where
                      • npm enterprise
                      Current Behavior
                      npm publish uses registry defined in publishConfig
                      
NOTICE npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms in above example
                      npm unpublish uses registry defined in .npmrc
                      
NOTICE npm http fetch GET 401 https://example.com/`@dazn%2fdaznid?write=true 105ms
                      Steps to Reproduce
                      See above
                      Expected Behavior
                      npm publish and npm unpublish to use same setup (preferably one which allow to have different registry for pull and push)
                      Who
                      • n/a
                      References
                      Related to npm/npm#3032
                      Metadata
                      Metadata
                      Assignees
                      No one assigned
                        Labels
                        Bugthing that needs fixing
                        Type
                        No type
                        Projects
                        No projects
                          Milestone
                          No milestone
                          Relationships
                          None yet
                          Development
                          No branches or pull requests
                          Issue actions
                          
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Remove or un-stick sticky/fixed headers that block content
(function() {
function unstick() {
document.querySelectorAll('header, nav, [role="banner"], .header, .navbar, .sticky, .fixed-top, [style*="position: fixed"], [style*="position:sticky"]').forEach(function(el) {
if (el.style.position === 'fixed' || el.style.position === 'sticky' || getComputedStyle(el).position === 'fixed' || getComputedStyle(el).position === 'sticky') {
el.style.position = 'static';
el.style.top = 'auto';
el.style.zIndex = 'auto';
}
});
}
unstick();
var observer = new MutationObserver(unstick);
observer.observe(document.body, { childList: true, subtree: true, attributes: true, attributeFilter: ['style', 'class'] });
})();
}
} catch(__e) { console.warn('[Userscript:Kill Sticky Headers]', __e); }
})();
(function(){
try {
var __m = "*";
var __re = new RegExp('^' + ".*" + '
[BUG] `npm publish` uses different registry then `npm unpublish` · Issue #559 · npm/cli · GitHub
                          Skip to content
                          [BUG] npm publish uses different registry then npm unpublish #559
                          Closed
                          Closed
                          [BUG] npm publish uses different registry then npm unpublish#559
                          Labels
                          Bugthing that needs fixing
                          Description
                          @mbazalik
                          mbazalik
                          opened on Dec 5, 2019
                          What / Why
                          This seems to be a duplicate of npm/npm#3032 even though the last comment claims the problem is resolved
                          In short, when the package contains both .npmrc and publishConfig setup it seems that npm publish is respecting setup from publishConfig while npm unpublish is using .npmrc
                          When
                          The project is using both .npmrc to define which registry to use to pull packages from and publishConfig to define to which registry the package should be pushed to
                          Example:
                          
.npmrc
                          @dazn:registry=https://example.com/

                          package.json
                          {
..."name": "@dazn/daznid",
"version": "2.0.1-rc00002",
"publishConfig": {
"@dazn:registry": "https://registry.npmjs.org/",
"access": "restricted"
},
...
}
                          npm publish --loglevel verbose output:
                          npm publish --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'publish',
npm verb cli '--loglevel',
npm verb cli 'verbose' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm verb npm-session 7920cfe554e24b7a
npm verb publish [ '.' ]
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublish: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepare: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run build:prod (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepack: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpack: @dazn/daznid@2.0.1-rc00002
npm notice npm notice package: @dazn/daznid@2.0.1-rc00002
npm notice === Tarball Contents === npm notice 314B dist/index.html
npm notice 21.8kB dist/daznid.js npm notice 1.3kB package.json npm notice 1.3kB README.md npm notice 117B CHANGELOG.yml npm notice === Tarball Details === npm notice name: @dazn/daznid npm notice version: 2.0.1-rc00002 npm notice package size: 9.4 kB npm notice unpacked size: 24.8 kB npm notice shasum: 94bbabe79081807a6d768a9eb5debf282a969c00
npm notice integrity: sha512-6GW6ARu37UeAm[...]gSjZ6cxVvXkRw==
npm notice total files: 5 npm notice npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms
npm info lifecycle @dazn/daznid@2.0.1-rc00002~publish: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~publish: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run publish:ftp & git push --tags (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpublish: @dazn/daznid@2.0.1-rc00002
+ @dazn/daznid@2.0.1-rc00002
npm verb exit [ 0, true ]
npm timing npm Completed in 4073ms
npm info ok 
                          npm unpublish -f --loglevel verbose @dazn/daznid@2.0.1-rc00002
                          npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'unpublish',
npm verb cli '-f',
npm verb cli '--loglevel',
npm verb cli 'verbose',
npm verb cli '@dazn/daznid@2.0.1-rc00002' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm WARN using --force I sure hope you know what you are doing.
npm verb npm-session 9f0285a83a8cd55c
npm http fetch GET 401 https://example.com/@dazn%2fdaznid?write=true 105ms
npm verb stack Error: Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb stack at res.buffer.catch.then.body (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
npm verb stack at process._tickCallback (internal/process/next_tick.js:68:7)
npm verb statusCode 401
npm verb pkgid @dazn/daznid@2.0.1-rc00002
npm verb cwd /drone/src/github.com/getndazn/com-daznid
npm verb Linux 4.14.128-87.105.amzn1.x86_64
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "unpublish" "-f" "--loglevel" "verbose" "@dazn/daznid@2.0.1-rc00002"
npm verb node v10.17.0
npm verb npm v6.11.3
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb exit [ 1, true ]
npm timing npm Completed in 328ms
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-05T15_17_19_217Z-debug.log

                          Where
                          • npm enterprise
                          Current Behavior
                          npm publish uses registry defined in publishConfig
                          
NOTICE npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms in above example
                          npm unpublish uses registry defined in .npmrc
                          
NOTICE npm http fetch GET 401 https://example.com/`@dazn%2fdaznid?write=true 105ms
                          Steps to Reproduce
                          See above
                          Expected Behavior
                          npm publish and npm unpublish to use same setup (preferably one which allow to have different registry for pull and push)
                          Who
                          • n/a
                          References
                          Related to npm/npm#3032
                          Metadata
                          Metadata
                          Assignees
                          No one assigned
                            Labels
                            Bugthing that needs fixing
                            Type
                            No type
                            Projects
                            No projects
                              Milestone
                              No milestone
                              Relationships
                              None yet
                              Development
                              No branches or pull requests
                              Issue actions
                              
, 'i');
if (__m === '*' || __re.test(location.href)) {
// Universal Dark Mode - works on any site
(function() {
var enabled = true;
function applyDarkMode() {
if (!enabled) return;
// Create style element if it doesn't exist
var style = document.getElementById('universal-dark-mode-style');
if (!style) {
style = document.createElement('style');
style.id = 'universal-dark-mode-style';
document.head.appendChild(style);
}
// Dark mode CSS - inverts colors but preserves images/video
style.textContent = '
/* Invert everything except media */
html {
filter: invert(1) hue-rotate(180deg) !important;
background: #1a1a2e !important;
}
/* Restore images, videos, iframes, canvas */
img, video, iframe, canvas, svg, picture, [style*="background-image"] {
filter: invert(1) hue-rotate(180deg) !important;
}
/* Preserve specific elements that should not be inverted */
.no-dark-mode, .no-dark-mode *,
[data-theme="light"], [data-theme="light"],
.ace_editor, .ace_editor *,
.CodeMirror, .CodeMirror *,
.monaco-editor, .monaco-editor *,
.markdown-body pre, .markdown-body pre *,
.highlight, .highlight *,
pre code, pre code * {
filter: none !important;
}
/* Fix common UI elements */
.modal, .popup, .dropdown-menu, .tooltip, .popover {
filter: invert(1) hue-rotate(180deg) !important;
background: #2d2d44 !important;
border-color: #444 !important;
}
/* Scrollbars */
::-webkit-scrollbar { background: #1a1a2e !important; }
::-webkit-scrollbar-thumb { background: #444 !important; }
::-webkit-scrollbar-thumb:hover { background: #555 !important; }
/* Selection */
::selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
::-moz-selection { background: #4ecdc4 !important; color: #1a1a2e !important; }
';
}
function removeDarkMode() {
var style = document.getElementById('universal-dark-mode-style');
if (style) style.remove();
}
// Toggle with Alt+Shift+D
document.addEventListener('keydown', function(e) {
if (e.altKey && e.shiftKey && e.key === 'D') {
e.preventDefault();
enabled = !enabled;
if (enabled) {
applyDarkMode();
console.log('[Universal Dark Mode] Enabled');
} else {
removeDarkMode();
console.log('[Universal Dark Mode] Disabled');
}
}
});
// Apply on load
applyDarkMode();
// Re-apply on dynamic content
var observer = new MutationObserver(function(mutations) {
if (enabled && !document.getElementById('universal-dark-mode-style')) {
applyDarkMode();
}
});
observer.observe(document.head, { childList: true });
console.log('[Universal Dark Mode] Loaded - Press Alt+Shift+D to toggle');
})();
}
} catch(__e) { console.warn('[Userscript:Universal Dark Mode]', __e); }
})();
})();
[BUG] `npm publish` uses different registry then `npm unpublish` · Issue #559 · npm/cli · GitHub
                              Skip to content
                              [BUG] npm publish uses different registry then npm unpublish #559
                              Closed
                              Closed
                              [BUG] npm publish uses different registry then npm unpublish#559
                              Labels
                              Bugthing that needs fixing
                              Description
                              @mbazalik
                              mbazalik
                              opened on Dec 5, 2019
                              What / Why
                              This seems to be a duplicate of npm/npm#3032 even though the last comment claims the problem is resolved
                              In short, when the package contains both .npmrc and publishConfig setup it seems that npm publish is respecting setup from publishConfig while npm unpublish is using .npmrc
                              When
                              The project is using both .npmrc to define which registry to use to pull packages from and publishConfig to define to which registry the package should be pushed to
                              Example:
                              
.npmrc
                              @dazn:registry=https://example.com/

                              package.json
                              {
..."name": "@dazn/daznid",
"version": "2.0.1-rc00002",
"publishConfig": {
"@dazn:registry": "https://registry.npmjs.org/",
"access": "restricted"
},
...
}
                              npm publish --loglevel verbose output:
                              npm publish --loglevel verbose
npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'publish',
npm verb cli '--loglevel',
npm verb cli 'verbose' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm verb npm-session 7920cfe554e24b7a
npm verb publish [ '.' ]
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublish: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepare: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~prepublishOnly: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run build:prod (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~prepack: @dazn/daznid@2.0.1-rc00002
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpack: @dazn/daznid@2.0.1-rc00002
npm notice npm notice package: @dazn/daznid@2.0.1-rc00002
npm notice === Tarball Contents === npm notice 314B dist/index.html
npm notice 21.8kB dist/daznid.js npm notice 1.3kB package.json npm notice 1.3kB README.md npm notice 117B CHANGELOG.yml npm notice === Tarball Details === npm notice name: @dazn/daznid npm notice version: 2.0.1-rc00002 npm notice package size: 9.4 kB npm notice unpacked size: 24.8 kB npm notice shasum: 94bbabe79081807a6d768a9eb5debf282a969c00
npm notice integrity: sha512-6GW6ARu37UeAm[...]gSjZ6cxVvXkRw==
npm notice total files: 5 npm notice npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms
npm info lifecycle @dazn/daznid@2.0.1-rc00002~publish: @dazn/daznid@2.0.1-rc00002
npm WARN lifecycle @dazn/daznid@2.0.1-rc00002~publish: cannot run in wd @dazn/daznid@2.0.1-rc00002 npm run publish:ftp & git push --tags (wd=.)
npm info lifecycle @dazn/daznid@2.0.1-rc00002~postpublish: @dazn/daznid@2.0.1-rc00002
+ @dazn/daznid@2.0.1-rc00002
npm verb exit [ 0, true ]
npm timing npm Completed in 4073ms
npm info ok 
                              npm unpublish -f --loglevel verbose @dazn/daznid@2.0.1-rc00002
                              npm info it worked if it ends with ok
npm verb cli [ '/usr/local/bin/node',
npm verb cli '/usr/local/bin/npm',
npm verb cli 'unpublish',
npm verb cli '-f',
npm verb cli '--loglevel',
npm verb cli 'verbose',
npm verb cli '@dazn/daznid@2.0.1-rc00002' ]
npm info using npm@6.11.3
npm info using node@v10.17.0
npm WARN using --force I sure hope you know what you are doing.
npm verb npm-session 9f0285a83a8cd55c
npm http fetch GET 401 https://example.com/@dazn%2fdaznid?write=true 105ms
npm verb stack Error: Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb stack at res.buffer.catch.then.body (/usr/local/lib/node_modules/npm/node_modules/npm-registry-fetch/check-response.js:94:17)
npm verb stack at process._tickCallback (internal/process/next_tick.js:68:7)
npm verb statusCode 401
npm verb pkgid @dazn/daznid@2.0.1-rc00002
npm verb cwd /drone/src/github.com/getndazn/com-daznid
npm verb Linux 4.14.128-87.105.amzn1.x86_64
npm verb argv "/usr/local/bin/node" "/usr/local/bin/npm" "unpublish" "-f" "--loglevel" "verbose" "@dazn/daznid@2.0.1-rc00002"
npm verb node v10.17.0
npm verb npm v6.11.3
npm ERR! code E401
npm ERR! Unable to authenticate, need: Basic realm="Artifactory Realm"
npm verb exit [ 1, true ]
npm timing npm Completed in 328ms
npm ERR! A complete log of this run can be found in:
npm ERR! /root/.npm/_logs/2019-12-05T15_17_19_217Z-debug.log

                              Where
                              • npm enterprise
                              Current Behavior
                              npm publish uses registry defined in publishConfig
                              
NOTICE npm http fetch PUT 200 https://registry.npmjs.org/@dazn%2fdaznid 3769ms in above example
                              npm unpublish uses registry defined in .npmrc
                              
NOTICE npm http fetch GET 401 https://example.com/`@dazn%2fdaznid?write=true 105ms
                              Steps to Reproduce
                              See above
                              Expected Behavior
                              npm publish and npm unpublish to use same setup (preferably one which allow to have different registry for pull and push)
                              Who
                              • n/a
                              References
                              Related to npm/npm#3032
                              Metadata
                              Metadata
                              Assignees
                              No one assigned
                                Labels
                                Bugthing that needs fixing
                                Type
                                No type
                                Projects
                                No projects
                                  Milestone
                                  No milestone
                                  Relationships
                                  None yet
                                  Development
                                  No branches or pull requests
                                  Issue actions