from small one page howto to huge articles all in one place

search text in:




Other .linuxhowtos.org sites:gentoo.linuxhowtos.org



Last additions:
using iotop to find disk usage hogs

using iotop to find disk usage hogs

words:

887

views:

209806

userrating:


May 25th. 2007:
Words

486

Views

258798

why adblockers are bad


Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

Workaround and fixes for the current Core Dump Handling vulnerability affected kernels

words:

161

views:

150121

userrating:


April, 26th. 2006:

Druckversion
You are here: manpages





NP-LOGOUT

Section: (1)
Updated: October 2025
Index Return to Main Contents
 

NAME

np-logout- Log out of the registry  

Synopsis

npm logout
Note: This command is unaware of workspaces.  

Description

When logged into a registry that supports toke-based authentication, tell the server to end this token's session. This will invalidate the token everywhere you're using it, not just for the current environment. When logged into a legacy registry that uses username and password authentication, this will clear the credentials in your user configuration. In this case, it will only affect the current environment. If -scope is provided, this will find the credentials for the registry connected to that scope, if set.  

Configuration

 

registry

*
Default: "https://registry.npmjs.org/"
*
Type: URL

The base URL of the npm registry.  

scope

*
Default: the scope of the current project, if any, or ""
*
Type: String

Associate an operation with a scope for a scoped registry. Useful when logging in to or out of a private registry:

# log in, linking the scope to the custom registry
npm login-scope=@mycorp-registry=https://registry.mycorp.com

# log out, removing the link and the auth token
npm logout-scope=@mycorp
This will cause @mycorp to be mapped to the registry for future installation of packages specified according to the pattern @mycorp/package. This will also cause npm init to create a scoped package.
# accept all defaults, and create a package named "@foo/whatever",
# instead of just named "whatever"
npm init-scope=@foo-yes
 

See Also

*
npm help adduser
*
npm help registry
*
npm help config
*
npm help whoami


 

Index

NAME
Synopsis
Description
Configuration
registry
scope
See Also





Support us on Content Nation
rdf newsfeed | rss newsfeed | Atom newsfeed
- Powered by LeopardCMS - Running on Gentoo -
Copyright 2004-2025 Sascha Nitsch Unternehmensberatung GmbH
Valid XHTML1.1 : Valid CSS
- Level Triple-A Conformance to Web Content Accessibility Guidelines 1.0 -
- Copyright and legal notices -
Time to create this page: 13.6 ms