Lines Matching full:package

3 \fBnpx\fR - Run a command from a local or remote npm package
9 npx --package=<pkg>\[lB]@<version>\[rB] -- <cmd> \[lB]args...\[rB]
11 npx --package=foo -c '<cmd> \[lB]args...\[rB]'
16 This command allows you to run an arbitrary command from an npm package (either one installed local…
18 …--package\fR option will be provided in the \fBPATH\fR of the executed command, along with any loc…
22 Package names provided without a specifier will be matched with whatever version exists in the loca…
24 …mand string. If no \fB--package\fR options are provided, then npm will attempt to determine the ex…
27 If the package has a single entry in its \fBbin\fR field in \fBpackage.json\fR, or if all entries a…
29 If the package has multiple \fBbin\fR entries, and one of them matches the unscoped portion of the …
31 …se there are no bin entries, or none of them match the \fBname\fR of the package), then \fBnpm exe…
35 …he named binary, specify one or more \fB--package\fR options, which will prevent npm from inferrin…
44 $ npx foo@latest bar --package=@npmcli/foo
48 In this case, npm will resolve the \fBfoo\fR package name, and run the following command:
52 $ foo bar --package=@npmcli/foo
56 Since the \fB--package\fR option comes \fIafter\fR the positional arguments, it is treated as an ar…
62 $ npm exec foo@latest bar --package=@npmcli/foo
66 In this case, npm will parse the \fB--package\fR option first, resolving the \fB@npmcli/foo\fR pack…
78 $ npm exec -- foo@latest bar --package=@npmcli/foo
92 …and \fIother than\fR the command whose name matches the package name by specifying a \fB--package\…
96 $ npm exec --package=foo -- bar --bar-argument
98 $ npx --package=foo bar --bar-argument
112 The \fBnpx\fR binary was rewritten in npm v7.0.0, and the standalone \fBnpx\fR package deprecated a…
119 To prevent security and user-experience problems from mistyping package names, \fBnpx\fR prompts be…
125 The \fB-p\fR argument is a shorthand for \fB--parseable\fR in npm, but shorthand for \fB--package\f…