Go to main content

man pages section 1: User Commands

Exit Print View

Updated: Wednesday, July 27, 2022
 
 

npm-logout (1)

Name

npm-logout - Log out of the registry Synopsis npm logout Note: This command is unaware of workspaces. Description When logged into a registry that supports token-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 configura- tion. 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 o Default: "https://registry.npmjs.org/" o Type: URL The base URL of the npm registry. scope o Default: the scope of the current project, if any, or "" o 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 instal- lation 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 o npm help adduser o npm help registry o npm help config o npm help whoami

Synopsis

Please see following description for synopsis

Description

NPM-LOGOUT(1)                                                    NPM-LOGOUT(1)



NAME
       npm-logout - Log out of the registry

   Synopsis
         npm logout

       Note: This command is unaware of workspaces.

   Description
       When  logged  into a registry that supports token-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 configura-
       tion.  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
       o Default: "https://registry.npmjs.org/"

       o Type: URL


       The base URL of the npm registry.

   scope
       o Default: the scope of the current project, if any, or ""

       o 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 instal-
       lation 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
       o npm help adduser

       o npm help registry

       o npm help config

       o npm help whoami




ATTRIBUTES
       See attributes(7) for descriptions of the following attributes:


       +---------------+--------------------------+
       |ATTRIBUTE TYPE |     ATTRIBUTE VALUE      |
       +---------------+--------------------------+
       |Availability   | runtime/nodejs/nodejs-18 |
       +---------------+--------------------------+
       |Stability      | Pass-thru volatile       |
       +---------------+--------------------------+

NOTES
       Source  code  for open source software components in Oracle Solaris can
       be found at https://www.oracle.com/downloads/opensource/solaris-source-
       code-downloads.html.

       This     software     was    built    from    source    available    at
       https://github.com/oracle/solaris-userland.   The  original   community
       source    was   downloaded   from    https://github.com/nodejs/node/ar-
       chive/v18.1.0.zip.

       Further information about this software can be found on the open source
       community website at https://github.com/nodejs/node.



                                  April 2022                     NPM-LOGOUT(1)