Lines Matching full:init
3 <title>npm-init</title>
139 <h1 id="npm-init">npm-init</h1>
145 …init-author-name"><code>init-author-name</code></a></li><li><a href="#init-author-url"><code>init-…
149 <pre><code class="language-bash">npm init <package-spec> (same as `npx <package-spec>`)
150 npm init <@scope> (same as `npx <@scope>/create`)
155 <p><code>npm init <initializer></code> can be used to set up a new or existing npm
161 <p>The init command is transformed to a corresponding <code>npm exec</code> operation as
164 <li><code>npm init foo</code> -> <code>npm exec create-foo</code></li>
165 <li><code>npm init @usr/foo</code> -> <code>npm exec @usr/create-foo</code></li>
166 <li><code>npm init @usr</code> -> <code>npm exec @usr/create</code></li>
167 <li><code>npm init @usr@2.0.0</code> -> <code>npm exec @usr/create@2.0.0</code></li>
168 <li><code>npm init @usr/foo@2.0.0</code> -> <code>npm exec @usr/create-foo@2.0.0</code></li>
170 <p>If the initializer is omitted (by just calling <code>npm init</code>), init will fall
171 back to legacy init behavior. It will ask you a bunch of questions, and
178 globally installed, that will be what <code>npm init</code> uses. If you want npm
182 <li><code>npm init foo@latest</code> # fetches and runs the latest <code>create-foo</code> from
184 <li><code>npm init foo@1.2.3</code> # runs <code>create-foo@1.2.3</code> specifically</li>
187 <p>Any additional options will be passed directly to the command, so <code>npm init foo -- --hello<…
192 <li><code>npm init foo -y --registry=<url> -- --hello -a</code></li>
198 <pre><code class="language-bash">$ npm init react-app ./my-react-app
203 $ npm init esm --yes
205 <p>Generate a plain old package.json using legacy init:</p>
207 $ git init
208 $ npm init
211 <pre><code class="language-bash">$ npm init -y
215 <code>workspace</code> config option. When using <code>npm init -w <dir></code> the cli will
223 <p>You may generate a new workspace using the legacy init:</p>
224 <pre><code class="language-bash">$ npm init -w packages/a
234 <p>The workspaces init also supports the <code>npm init <initializer> -w <dir></code>
241 <pre><code class="language-bash">npm init -w packages/my-react-app react-app .
259 <h4 id="init-author-name"><code>init-author-name</code></h4>
264 <p>The value <code>npm init</code> should use by default for the package author's name.</p>
265 <h4 id="init-author-url"><code>init-author-url</code></h4>
270 <p>The value <code>npm init</code> should use by default for the package author's
272 <h4 id="init-license"><code>init-license</code></h4>
277 <p>The value <code>npm init</code> should use by default for the package license.</p>
278 <h4 id="init-module"><code>init-module</code></h4>
280 <li>Default: "~/.npm-init.js"</li>
283 <p>A module that will be loaded by the <code>npm init</code> command. See the
285 <a href="https://github.com/npm/init-package-json">init-package-json</a> module for
286 more information, or <a href="../commands/npm-init.html">npm init</a>.</p>
287 <h4 id="init-version"><code>init-version</code></h4>
292 <p>The value that <code>npm init</code> should use by default for the package version
320 <li>Implicitly set <code>--yes</code> during <code>npm init</code>.</li>
342 <p>This will also cause <code>npm init</code> to create a scoped package.</p>
345 npm init --scope=@foo --yes
362 <p>When set for the <code>npm init</code> command, this may be set to the folder of a
402 <li><a href="http://npm.im/init-package-json">init-package-json module</a></li>
411 <a href="https://github.com/npm/cli/edit/latest/docs/content/commands/npm-init.md">