Lines Matching +full:packages +full:- +full:dir
1 .TH "NPM-INIT" "1" "February 2024" "" ""
3 \fBnpm-init\fR - Create a package.json file
8 npm init <package-spec> (same as `npx <package-spec>`)
18 …-<initializer>\fR, which will be installed by npm help npm-exec, and then have its main bin execut…
23 \fBnpm init foo\fR -> \fBnpm exec create-foo\fR
25 \fBnpm init @usr/foo\fR -> \fBnpm exec @usr/create-foo\fR
27 \fBnpm init @usr\fR -> \fBnpm exec @usr/create\fR
29 \fBnpm init @usr@2.0.0\fR -> \fBnpm exec @usr/create@2.0.0\fR
31 \fBnpm init @usr/foo@2.0.0\fR -> \fBnpm exec @usr/create-foo@2.0.0\fR
35 …t were already set. You can also use \fB-y\fR/\fB--yes\fR to skip the questionnaire altogether. If…
37 \fINote:\fR if a user already has the \fBcreate-<initializer>\fR package globally installed, that w…
40 \fBnpm init foo@latest\fR # fetches and runs the latest \fBcreate-foo\fR from the registry
42 \fBnpm init foo@1.2.3\fR # runs \fBcreate-foo@1.2.3\fR specifically
48 foo -- --hello\fR will map to \fBnpm exec -- create-foo --hello\fR.
53 \fBnpm init foo -y --registry=<url> -- --hello -a\fR
55 \fBnpm exec -y --registry=<url> -- create-foo --hello -a\fR
60 Create a new React-based project using \fB\fBcreate-react-app\fR\fR \fI\(lahttps://npm.im/create-re…
64 $ npm init react-app ./my-react-app
68 Create a new \fBesm\fR-compatible package using \fB\fBcreate-esm\fR\fR \fI\(lahttps://npm.im/create…
72 $ mkdir my-esm-lib && cd my-esm-lib
73 $ npm init esm --yes
81 $ mkdir my-npm-pkg && cd my-npm-pkg
91 $ npm init -y
96 …oject by using the \fBworkspace\fR config option. When using \fBnpm init -w <dir>\fR the cli will …
103 +-- package.json
111 $ npm init -w packages/a
115 That will generate a new folder and \fBpackage.json\fR file, while also updating your top-level \fB…
120 +-- package.json
121 `-- packages
122 `-- a
123 `-- package.json
127 …-w <dir>\fR syntax, following the same set of rules explained earlier in the initial \fBDescriptio…
131 npm init -w packages/my-react-app react-app .
135 …ame followed with a dot to represent the current directory in that context, e.g: \fBreact-app .\fR:
140 +-- package.json
141 `-- packages
142 +-- a
143 | `-- package.json
144 `-- my-react-app
145 +-- README
146 +-- package.json
147 `-- ...
151 .SS "\fBinit-author-name\fR"
161 .SS "\fBinit-author-url\fR"
171 .SS "\fBinit-license\fR"
181 .SS "\fBinit-module\fR"
184 Default: "~/.npm-init.js"
190 …command. See the documentation for the \fBinit-package-json\fR \fI\(lahttps://github.com/npm/init-…
191 .SS "\fBinit-version\fR"
223 Allow clobbering non-npm files in global installs.
229 Allow installing packages that have an \fBengines\fR declaration requiring a different version of n…
231 Allow installing packages that have an \fBengines\fR declaration requiring a different version of \…
233 …it fix\fR to install modules outside your stated dependency range (including SemVer-major changes).
239 Implicitly set \fB--yes\fR during \fBnpm init\fR.
243 Allow unpublishing of entire packages (not just a single version).
264 npm login --scope=@mycorp --registry=https://registry.mycorp.com
267 npm logout --scope=@mycorp
271 This will cause \fB@mycorp\fR to be mapped to the registry for future installation of packages spec…
279 npm init --scope=@foo --yes
321 …all, update, etc.) will link workspaces into the \fBnode_modules\fR folder. - Commands that do oth…
326 .SS "\fBworkspaces-update\fR"
336 .SS "\fBinclude-workspace-root\fR"
355 \fBinit-package-json module\fR \fI\(lahttp://npm.im/init-package-json\(ra\fR
357 \fBpackage.json\fR \fI\(la/configuring-npm/package-json\(ra\fR