mirror of https://github.com/lukechilds/node.git
Browse Source
This is a roll-up release that includes all changes to npm since 2.13.4. PR-URL: https://github.com/nodejs/node/pull/3684 Reviewed-By: Jeremiah Senkpiel <fishrock123@rocketmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>v0.12-staging
committed by
James M Snell
979 changed files with 20346 additions and 53262 deletions
@ -1,2 +0,0 @@ |
|||
save-prefix = ~ |
|||
proprietary-attribs = false |
@ -1,6 +1,19 @@ |
|||
:: Created by npm, please don't edit manually. |
|||
@IF EXIST "%~dp0\node.exe" ( |
|||
"%~dp0\node.exe" "%~dp0\.\node_modules\npm\bin\npm-cli.js" %* |
|||
) ELSE ( |
|||
node "%~dp0\.\node_modules\npm\bin\npm-cli.js" %* |
|||
) |
|||
:: Created by npm, please don't edit manually. |
|||
@ECHO OFF |
|||
|
|||
SETLOCAL |
|||
|
|||
SET "NODE_EXE=%~dp0\node.exe" |
|||
IF NOT EXIST "%NODE_EXE%" ( |
|||
SET "NODE_EXE=node" |
|||
) |
|||
|
|||
SET "NPM_CLI_JS=%~dp0\node_modules\npm\bin\npm-cli.js" |
|||
FOR /F "delims=" %%F IN ('CALL "%NODE_EXE%" "%NPM_CLI_JS%" prefix -g') DO ( |
|||
SET "NPM_PREFIX_NPM_CLI_JS=%%F\node_modules\npm\bin\npm-cli.js" |
|||
) |
|||
IF EXIST "%NPM_PREFIX_NPM_CLI_JS%" ( |
|||
SET "NPM_CLI_JS=%NPM_PREFIX_NPM_CLI_JS%" |
|||
) |
|||
|
|||
"%NODE_EXE%" "%NPM_CLI_JS%" %* |
|||
|
@ -0,0 +1,55 @@ |
|||
npm-team(1) -- Manage organization teams and team memberships |
|||
============================================================= |
|||
|
|||
## SYNOPSIS |
|||
|
|||
npm team create <scope:team> |
|||
npm team destroy <scope:team> |
|||
|
|||
npm team add <scope:team> <user> |
|||
npm team rm <scope:team> <user> |
|||
|
|||
npm team ls <scope>|<scope:team> |
|||
|
|||
npm team edit <scope:team> |
|||
|
|||
## DESCRIPTION |
|||
|
|||
Used to manage teams in organizations, and change team memberships. Does not |
|||
handle permissions for packages. |
|||
|
|||
Teams must always be fully qualified with the organization/scope they belond to |
|||
when operating on them, separated by a colon (`:`). That is, if you have a |
|||
`developers` team on a `foo` organization, you must always refer to that team as |
|||
`developers:foo` in these commands. |
|||
|
|||
* create / destroy: |
|||
Create a new team, or destroy an existing one. |
|||
|
|||
* add / rm: |
|||
Add a user to an existing team, or remove a user from a team they belong to. |
|||
|
|||
* ls: |
|||
If performed on an organization name, will return a list of existing teams |
|||
under that organization. If performed on a team, it will instead return a list |
|||
of all users belonging to that particular team. |
|||
|
|||
## DETAILS |
|||
|
|||
`npm team` always operates directly on the current registry, configurable from |
|||
the command line using `--registry=<registry url>`. |
|||
|
|||
In order to create teams and manage team membership, you must be a *team admin* |
|||
under the given organization. Listing teams and team memberships may be done by |
|||
any member of the organizations. |
|||
|
|||
Organization creation and management of team admins and *organization* members |
|||
is done through the website, not the npm CLI. |
|||
|
|||
To use teams to manage permissions on packages belonging to your organization, |
|||
use the `npm access` command to grant or revoke the appropriate permissions. |
|||
|
|||
## SEE ALSO |
|||
|
|||
* npm-access(1) |
|||
* npm-registr(7) |
@ -0,0 +1,90 @@ |
|||
npm-orgs(7) -- Working with Teams & Orgs |
|||
======================================== |
|||
|
|||
## DESCRIPTION |
|||
|
|||
There are three levels of org users: |
|||
|
|||
1. Super admin, controls billing & adding people to the org. |
|||
2. Team admin, manages team membership & package access. |
|||
3. Developer, works on packages they are given access to. |
|||
|
|||
The super admin is the only person who can add users to the org because it impacts the monthly bill. The super admin will use the website to manage membership. Every org has a `developers` team that all users are automatically added to. |
|||
|
|||
The team admin is the person who manages team creation, team membership, and package access for teams. The team admin grants package access to teams, not individuals. |
|||
|
|||
The developer will be able to access packages based on the teams they are on. Access is either read-write or read-only. |
|||
|
|||
There are two main commands: |
|||
|
|||
1. `npm team` see npm-access(1) for more details |
|||
2. `npm access` see npm-team(1) for more details |
|||
|
|||
## Team Admins create teams |
|||
|
|||
* Check who you’ve added to your org: |
|||
|
|||
``` |
|||
npm team ls <org>:developers |
|||
``` |
|||
|
|||
* Each org is automatically given a `developers` team, so you can see the whole list of team members in your org. This team automatically gets read-write access to all packages, but you can change that with the `access` command. |
|||
|
|||
* Create a new team: |
|||
|
|||
``` |
|||
npm team create <org:team> |
|||
``` |
|||
|
|||
* Add members to that team: |
|||
|
|||
``` |
|||
npm team add <org:team> <user> |
|||
``` |
|||
|
|||
## Publish a package and adjust package access |
|||
|
|||
* In package directory, run |
|||
|
|||
``` |
|||
npm init --scope=<org> |
|||
``` |
|||
to scope it for your org & publish as usual |
|||
|
|||
* Grant access: |
|||
|
|||
``` |
|||
npm access grant <read-only|read-write> <org:team> [<package>] |
|||
``` |
|||
|
|||
* Revoke access: |
|||
|
|||
``` |
|||
npm access revoke <org:team> [<package>] |
|||
``` |
|||
|
|||
## Monitor your package access |
|||
|
|||
* See what org packages a team member can access: |
|||
|
|||
``` |
|||
npm access ls-packages <org> <user> |
|||
``` |
|||
|
|||
* See packages available to a specific team: |
|||
|
|||
``` |
|||
npm access ls-packages <org:team> |
|||
``` |
|||
|
|||
* Check which teams are collaborating on a package: |
|||
|
|||
``` |
|||
npm access ls-collaborators <pkg> |
|||
``` |
|||
|
|||
## SEE ALSO |
|||
|
|||
* npm-team(1) |
|||
* npm-access(1) |
|||
* npm-scope(7) |
@ -0,0 +1,45 @@ |
|||
<!doctype html> |
|||
<html> |
|||
<title>npm-submodule</title> |
|||
<meta http-equiv="content-type" value="text/html;utf-8"> |
|||
<link rel="stylesheet" type="text/css" href="../../static/style.css"> |
|||
<link rel="canonical" href="https://www.npmjs.org/doc/api/npm-submodule.html"> |
|||
<script async=true src="../../static/toc.js"></script> |
|||
|
|||
<body> |
|||
<div id="wrapper"> |
|||
|
|||
<h1><a href="../api/npm-submodule.html">npm-submodule</a></h1> <p>Add a package as a git submodule</p> |
|||
<h2 id="synopsis">SYNOPSIS</h2> |
|||
<pre><code>npm.commands.submodule(packages, callback) |
|||
</code></pre><h2 id="description">DESCRIPTION</h2> |
|||
<p>For each package specified, npm will check if it has a git repository url |
|||
in its package.json description then add it as a git submodule at |
|||
<code>node_modules/<pkg name></code>.</p> |
|||
<p>This is a convenience only. From then on, it's up to you to manage |
|||
updates by using the appropriate git commands. npm will stubbornly |
|||
refuse to update, modify, or remove anything with a <code>.git</code> subfolder |
|||
in it.</p> |
|||
<p>This command also does not install missing dependencies, if the package |
|||
does not include them in its git repository. If <code>npm ls</code> reports that |
|||
things are missing, you can either install, link, or submodule them yourself, |
|||
or you can do <code>npm explore <pkgname> -- npm install</code> to install the |
|||
dependencies into the submodule folder.</p> |
|||
<h2 id="see-also">SEE ALSO</h2> |
|||
<ul> |
|||
<li>npm help json</li> |
|||
<li>git help submodule</li> |
|||
</ul> |
|||
|
|||
</div> |
|||
|
|||
<table border=0 cellspacing=0 cellpadding=0 id=npmlogo> |
|||
<tr><td style="width:180px;height:10px;background:rgb(237,127,127)" colspan=18> </td></tr> |
|||
<tr><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td colspan=6 style="width:60px;height:10px;background:#fff"> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td></tr> |
|||
<tr><td colspan=2 style="width:20px;height:30px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=4 colspan=2> </td><td style="width:10px;height:20px;background:rgb(237,127,127)" rowspan=2> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=3 colspan=2> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td></tr> |
|||
<tr><td style="width:10px;height:10px;background:#fff" rowspan=2> </td></tr> |
|||
<tr><td style="width:10px;height:10px;background:#fff"> </td></tr> |
|||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> |
|||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> |
|||
</table> |
|||
<p id="footer">npm-submodule — npm@1.4.29</p> |
@ -0,0 +1,45 @@ |
|||
<!doctype html> |
|||
<html> |
|||
<title>npm-install-test</title> |
|||
<meta http-equiv="content-type" value="text/html;utf-8"> |
|||
<link rel="stylesheet" type="text/css" href="../../static/style.css"> |
|||
<link rel="canonical" href="https://www.npmjs.org/doc/cli/npm-install-test.html"> |
|||
<script async=true src="../../static/toc.js"></script> |
|||
|
|||
<body> |
|||
<div id="wrapper"> |
|||
|
|||
<h1>npm <a href="../cli/install-test.html">install-test</a></h1> <p>Install package(s) and run tests</p> |
|||
<h2 id="synopsis">SYNOPSIS</h2> |
|||
<pre><code>npm install-test (with no args, in package dir) |
|||
npm install-test [<@scope>/]<name> |
|||
npm install-test [<@scope>/]<name>@<tag> |
|||
npm install-test [<@scope>/]<name>@<version> |
|||
npm install-test [<@scope>/]<name>@<version range> |
|||
npm install-test <tarball file> |
|||
npm install-test <tarball url> |
|||
npm install-test <folder> |
|||
|
|||
alias: npm it |
|||
common options: [--save|--save-dev|--save-optional] [--save-exact] [--dry-run] |
|||
</code></pre><h2 id="description">DESCRIPTION</h2> |
|||
<p>This command runs an <code>npm install</code> followed immediately by an <code>npm test</code>. It |
|||
takes exactly the same arguments as <code>npm install</code>.</p> |
|||
<h2 id="see-also">SEE ALSO</h2> |
|||
<ul> |
|||
<li><a href="../cli/npm-install.html">npm-install(1)</a></li> |
|||
<li><a href="../cli/npm-test.html">npm-test(1)</a></li> |
|||
</ul> |
|||
|
|||
</div> |
|||
|
|||
<table border=0 cellspacing=0 cellpadding=0 id=npmlogo> |
|||
<tr><td style="width:180px;height:10px;background:rgb(237,127,127)" colspan=18> </td></tr> |
|||
<tr><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td><td style="width:40px;height:10px;background:#fff" colspan=4> </td><td rowspan=4 style="width:10px;height:10px;background:rgb(237,127,127)"> </td><td colspan=6 style="width:60px;height:10px;background:#fff"> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=4> </td></tr> |
|||
<tr><td colspan=2 style="width:20px;height:30px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=4 colspan=2> </td><td style="width:10px;height:20px;background:rgb(237,127,127)" rowspan=2> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:20px;height:10px;background:#fff" rowspan=3 colspan=2> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td><td style="width:10px;height:10px;background:#fff" rowspan=3> </td><td style="width:10px;height:10px;background:rgb(237,127,127)" rowspan=3> </td></tr> |
|||
<tr><td style="width:10px;height:10px;background:#fff" rowspan=2> </td></tr> |
|||
<tr><td style="width:10px;height:10px;background:#fff"> </td></tr> |
|||
<tr><td style="width:60px;height:10px;background:rgb(237,127,127)" colspan=6> </td><td colspan=10 style="width:10px;height:10px;background:rgb(237,127,127)"> </td></tr> |
|||
<tr><td colspan=5 style="width:50px;height:10px;background:#fff"> </td><td style="width:40px;height:10px;background:rgb(237,127,127)" colspan=4> </td><td style="width:90px;height:10px;background:#fff" colspan=9> </td></tr> |
|||
</table> |
|||
<p id="footer">npm-install-test — npm@3.4.0</p> |
Some files were not shown because too many files changed in this diff
Loading…
Reference in new issue