/home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/docs/content/commands/
/home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/docs/content/commands
NameSizeModeActions
npm-access.md33590644editdlrm
npm-adduser.md23150644editdlrm
npm-audit.md143210644editdlrm
npm-bin.md8980644editdlrm
npm-bugs.md29630644editdlrm
npm-cache.md29990644editdlrm
npm-ci.md94810644editdlrm
npm-completion.md9090644editdlrm
npm-config.md37050644editdlrm
npm-dedupe.md81600644editdlrm
npm-deprecate.md17370644editdlrm
npm-diff.md89710644editdlrm
npm-dist-tag.md50790644editdlrm
npm-docs.md29410644editdlrm
npm-doctor.md47600644editdlrm
npm-edit.md10770644editdlrm
npm-exec.md112090644editdlrm
npm-explain.md27930644editdlrm
npm-explore.md10040644editdlrm
npm-find-dupes.md60640644editdlrm
npm-fund.md36050644editdlrm
npm-help-search.md7540644editdlrm
npm-help.md10020644editdlrm
npm-hook.md23900644editdlrm
npm-init.md89860644editdlrm
npm-install-ci-test.md77630644editdlrm
npm-install-test.md78400644editdlrm
npm-install.md231330644editdlrm
npm-link.md110010644editdlrm
npm-logout.md17460644editdlrm
npm-ls.md82020644editdlrm
npm-org.md19670644editdlrm
npm-outdated.md57690644editdlrm
npm-owner.md31000644editdlrm
npm-pack.md34420644editdlrm
npm-ping.md7670644editdlrm
npm-pkg.md78150644editdlrm
npm-prefix.md12400644editdlrm
npm-profile.md38990644editdlrm
npm-prune.md54100644editdlrm
npm-publish.md72890644editdlrm
npm-query.md50690644editdlrm
npm-rebuild.md42640644editdlrm
npm-repo.md27210644editdlrm
npm-restart.md14690644editdlrm
npm-root.md10800644editdlrm
npm-run-script.md73550644editdlrm
npm-search.md34020644editdlrm
npm-set-script.md23970644editdlrm
npm-shrinkwrap.md9230644editdlrm
npm-star.md17070644editdlrm
npm-stars.md7410644editdlrm
npm-start.md16630644editdlrm
npm-stop.md13370644editdlrm
npm-team.md40580644editdlrm
npm-test.md12300644editdlrm
npm-token.md42130644editdlrm
npm-uninstall.md40210644editdlrm
npm-unpublish.md43700644editdlrm
npm-unstar.md15680644editdlrm
npm-update.md110850644editdlrm
npm-version.md68270644editdlrm
npm-view.md52690644editdlrm
npm-whoami.md7980644editdlrm
npm.md55860644editdlrm
npx.md57300644editdlrm
Edit: /home/techb158/.nvm/versions/node/v16.20.2/lib/node_modules/npm/docs/content/commands/npm-pack.md (3442B)
--- title: npm-pack section: 1 description: Create a tarball from a package --- ### Synopsis ```bash npm pack ``` ### Configuration #### `dry-run` * Default: false * Type: Boolean Indicates that you don't want npm to make any changes and that it should only report what it would have done. This can be passed into any of the commands that modify your local installation, eg, `install`, `update`, `dedupe`, `uninstall`, as well as `pack` and `publish`. Note: This is NOT honored by other network related commands, eg `dist-tags`, `owner`, etc. #### `json` * Default: false * Type: Boolean Whether or not to output JSON data, rather than the normal output. * In `npm pkg set` it enables parsing set values with JSON.parse() before saving them to your `package.json`. Not supported by all npm commands. #### `pack-destination` * Default: "." * Type: String Directory in which `npm pack` will save tarballs. #### `workspace` * Default: * Type: String (can be set multiple times) Enable running a command in the context of the configured workspaces of the current project while filtering by running only the workspaces defined by this configuration option. Valid values for the `workspace` config are either: * Workspace names * Path to a workspace directory * Path to a parent workspace directory (will result in selecting all workspaces within that folder) When set for the `npm init` command, this may be set to the folder of a workspace which does not yet exist, to create the folder and set it up as a brand new workspace within the project. This value is not exported to the environment for child processes. #### `workspaces` * Default: null * Type: null or Boolean Set to true to run the command in the context of **all** configured workspaces. Explicitly setting this to false will cause commands like `install` to ignore workspaces altogether. When not set explicitly: - Commands that operate on the `node_modules` tree (install, update, etc.) will link workspaces into the `node_modules` folder. - Commands that do other things (test, exec, publish, etc.) will operate on the root project, _unless_ one or more workspaces are specified in the `workspace` config. This value is not exported to the environment for child processes. #### `include-workspace-root` * Default: false * Type: Boolean Include the workspace root when workspaces are enabled for a command. When false, specifying individual workspaces via the `workspace` config, or all workspaces via the `workspaces` flag, will cause npm to operate only on the specified workspaces, and not on the root project. This value is not exported to the environment for child processes. ### Description For anything that's installable (that is, a package folder, tarball, tarball url, git url, name@tag, name@version, name, or scoped name), this command will fetch it to the cache, copy the tarball to the current working directory as `-.tgz`, and then write the filenames out to stdout. If the same package is specified multiple times, then the file will be overwritten the second time. If no arguments are supplied, then npm packs the current package folder. ### See Also * [package spec](/using-npm/package-spec) * [npm-packlist package](http://npm.im/npm-packlist) * [npm cache](/commands/npm-cache) * [npm publish](/commands/npm-publish) * [npm config](/commands/npm-config) * [npmrc](/configuring-npm/npmrc)