{"bugs":{"url":"https://github.com/lerna/lerna/issues"},"dist":{"shasum":"70da53112325172a109707a21ecf5b1d6fb40e0a","tarball":"https://registry.npmjs.org/@lerna/publish/-/publish-3.10.5.tgz","fileCount":17,"integrity":"sha512-26wjTtRbcUXlG8Na7goI0X1trMYivbuLT1bAXHNvuDaHYs7iE6LRjU4NCTNAmrdVnqagHkTxMuGRFn3r1NgcKg==","signatures":[{"sig":"MEUCIQDnzwbJCT4hcZGulyC2Z724dRr99yWCkHBdyykrMtoJ6gIgESuOx/L1yXCKdMSmPw1Y2GMoUHpX6kyJKBE9ksIaAI8=","keyid":"SHA256:jl3bwswu80PjjokCgh0o2w5c2U4LhQAE57gj9cz1kzA"}],"unpackedSize":71774,"npm-signature":"-----BEGIN PGP SIGNATURE-----\r\nVersion: OpenPGP.js v3.0.4\r\nComment: https://openpgpjs.org\r\n\r\nwsFcBAEBCAAQBQJcN+6ACRA9TVsSAnZWagAA2VkP+gP1bD+DG9N7ul7bl210\njkFthVecaAZXzD7nx8NESXewYkCB/9t/omDTRVDygteiDvnpr05tU2bqjP9l\ncpR6H77uGviA8nFhi3wcJA65Wllm7w0dWU9amBNjrhB/XEke0gQSsk7sqTml\ngnL+BXSFtkl5QBpLC9ePQORXO/TYPPy3s78pfdGJNmEYqkX/F7AMxmFjppxQ\nHbj60fv/tauVQhUNCGxdGh4T/6eF7bwjQAvRGqo7KPWZFBUQJHCjsZZcCgXU\n+1nEq+3QqZ08wb4HvAn8N10PeBuKPUPNNt1d5OtU3aRM7swQb6xMg15gz+2r\nMSmIkLHLKCUu8VUT3JsUJJ/OGmrF5KBYOwtXMOJGdVvNkr2Lwmklbn5VIeYb\nHQCz1BLgEFUJnELAZkBzEvQIVNetZcIwmQdEs40jykDCwur+9m37HgWIZkZt\nmHyXJwTbCHeCMHwaTqIgQL54vUHzPGQitpL92HmJRFGmUZ1OVr1e6lnxfGMb\nVpn7xxPJCKkQ1RVMIGXycj3CN7Jkhg0lzlns3te5xyyiEx2UA3aHKa/Wkupe\nbFU4vy6YCAwFKp0gNF9lY4DTKtyxX4Y120b5yMs908G4k3h5ns6V8Iom7ZKK\nEG3ZsSls2IqKQwyvdFnmpymAMUnE2bU/lsFKjSt6hZASSbc1kCjI/xboiDrR\nQfTd\r\n=Yry0\r\n-----END PGP SIGNATURE-----\r\n"},"main":"index.js","name":"@lerna/publish","author":{"url":"https://github.com/evocateur","name":"Daniel Stockman"},"readme":"# `@lerna/publish`\n\n> Publish packages in the current project\n\n## Usage\n\n```sh\nlerna publish              # publish packages that have changed since the last release\nlerna publish from-git     # explicitly publish packages tagged in the current commit\nlerna publish from-package # explicitly publish packages where the latest version is not present in the registry\n```\n\nWhen run, this command does one of the following things:\n\n- Publish packages updated since the last release (calling [`lerna version`](https://github.com/lerna/lerna/tree/master/commands/version#readme) behind the scenes).\n  - This is the legacy behavior of lerna 2.x\n- Publish packages tagged in the current commit (`from-git`).\n- Publish packages in the latest commit where the version is not present in the registry (`from-package`).\n- Publish an unversioned \"canary\" release of packages (and their dependents) updated in the previous commit.\n\n> Lerna will never publish packages which are marked as private (`\"private\": true` in the `package.json`).\n\nCheck out [Per-Package Configuration](#per-package-configuration) for more details about publishing scoped packages, custom registries, and custom dist-tags.\n\n## Positionals\n\n### bump `from-git`\n\nIn addition to the semver keywords supported by [`lerna version`](https://github.com/lerna/lerna/tree/master/commands/version#positionals),\n`lerna publish` also supports the `from-git` keyword.\nThis will identify packages tagged by `lerna version` and publish them to npm.\nThis is useful in CI scenarios where you wish to manually increment versions,\nbut have the package contents themselves consistently published by an automated process.\n\n### bump `from-package`\n\nSimilar to the `from-git` keyword except the list of packages to publish is determined by inspecting each `package.json`\nand determining if any package version is not present in the registry. Any versions not present in the registry will\nbe published.\nThis is useful when a previous `lerna publish` failed to publish all packages to the registry.\n\n## Options\n\n`lerna publish` supports all of the options provided by [`lerna version`](https://github.com/lerna/lerna/tree/master/commands/version#options) in addition to the following:\n\n- [`--canary`](#--canary)\n- [`--contents <dir>`](#--contents-dir)\n- [`--dist-tag <tag>`](#--dist-tag-tag)\n- [`--no-git-reset`](#--no-git-reset)\n- [`--no-verify-access`](#--no-verify-access)\n- [`--registry <url>`](#--registry-url)\n- [`--temp-tag`](#--temp-tag)\n- [`--yes`](#--yes)\n\n### `--canary`\n\n```sh\nlerna publish --canary\n# 1.0.0 => 1.0.1-alpha.0+${SHA} of packages changed since the previous commit\n# a subsequent canary publish will yield 1.0.1-alpha.1+${SHA}, etc\n\nlerna publish --canary --preid beta\n# 1.0.0 => 1.0.1-beta.0+${SHA}\n\n# The following are equivalent:\nlerna publish --canary minor\nlerna publish --canary preminor\n# 1.0.0 => 1.1.0-alpha.0+${SHA}\n```\n\nWhen run with this flag, `lerna publish` publishes packages in a more granular way (per commit). Before publishing to npm, it creates the new `version` tag by taking the current `version`, bumping it to the next _minor_ version, adding the provided meta suffix (defaults to `alpha`) and appending the current git sha (ex: `1.0.0` becomes `1.1.0-alpha.81e3b443`).\n\n> The intended use case for this flag is a per commit level release or nightly release.\n\n### `--contents <dir>`\n\nSubdirectory to publish. Must apply to ALL packages, and MUST contain a package.json file.\nPackage lifecycles will still be run in the original leaf directory.\nYou should probably use one of those lifecycles (`prepare`, `prepublishOnly`, or `prepack`) to _create_ the subdirectory and whatnot.\n\nIf you're into unnecessarily complicated publishing, this will give you joy.\n\n```sh\nlerna publish --contents dist\n# publish the \"dist\" subfolder of every Lerna-managed leaf package\n```\n\n### `--dist-tag <tag>`\n\n```sh\nlerna publish --dist-tag next\n```\n\nWhen run with this flag, `lerna publish` will publish to npm with the given npm [dist-tag](https://docs.npmjs.com/cli/dist-tag) (defaults to `latest`).\n\nThis option can be used to publish a [`prerelease`](http://carrot.is/coding/npm_prerelease) or `beta` version under a non-`latest` dist-tag, helping consumers avoid automatically upgrading to prerelease-quality code.\n\n> Note: the `latest` tag is the one that is used when a user runs `npm install my-package`.\n> To install a different tag, a user can run `npm install my-package@prerelease`.\n\n### `--no-git-reset`\n\nBy default, `lerna publish` ensures any changes to the working tree have been reset.\n\nTo avoid this, pass `--no-git-reset`. This can be especially useful when used as part of a CI pipeline in conjunction with the `--canary` flag. For instance, the `package.json` version numbers which have been bumped may need to be used in subsequent CI pipeline steps (such as Docker builds).\n\n```sh\nlerna publish --no-git-reset\n```\n\n### `--no-verify-access`\n\nBy default, `lerna` will verify the logged-in npm user's access to the packages about to be published. Passing this flag will disable that check.\n\nIf you are using a third-party registry that does not support `npm access ls-packages`, you will need to pass this flag (or set `command.publish.verifyAccess` to `false` in lerna.json).\n\n> Please use with caution\n\n### `--registry <url>`\n\nWhen run with this flag, forwarded npm commands will use the specified registry for your package(s).\n\nThis is useful if you do not want to explicitly set up your registry\nconfiguration in all of your package.json files individually when e.g. using\nprivate registries.\n\n### `--temp-tag`\n\nWhen passed, this flag will alter the default publish process by first publishing\nall changed packages to a temporary dist-tag (`lerna-temp`) and then moving the\nnew version(s) to the dist-tag configured by [`--dist-tag`](#--dist-tag-tag) (default `latest`).\n\nThis is not generally necessary, as Lerna will publish packages in topological\norder (all dependencies before dependents) by default.\n\n### `--yes`\n\n```sh\nlerna publish --canary --yes\n# skips `Are you sure you want to publish the above changes?`\n```\n\nWhen run with this flag, `lerna publish` will skip all confirmation prompts.\nUseful in [Continuous integration (CI)](https://en.wikipedia.org/wiki/Continuous_integration) to automatically answer the publish confirmation prompt.\n\n## Deprecated Options\n\n### `--skip-npm`\n\nCall [`lerna version`](https://github.com/lerna/lerna/tree/master/commands/version#readme) directly, instead.\n\n## Per-Package Configuration\n\nA leaf package can be configured with special [`publishConfig`](https://docs.npmjs.com/files/package.json#publishconfig) that in _certain_ circumstances changes the behavior of `lerna publish`.\n\n### `publishConfig.access`\n\nTo publish packages with a scope (e.g., `@mycompany/rocks`), you must set [`access`](https://docs.npmjs.com/misc/config#access):\n\n```json\n  \"publishConfig\": {\n    \"access\": \"public\"\n  }\n```\n\n- If this field is set for a package _without_ a scope, it **will** fail.\n- If you _want_ your scoped package to remain private (i.e., `\"restricted\"`), there is no need to set this value.\n\n  Note that this is **not** the same as setting `\"private\": true` in a leaf package; if the `private` field is set, that package will _never_ be published under any circumstances.\n\n### `publishConfig.registry`\n\nYou can customize the registry on a per-package basis by setting [`registry`](https://docs.npmjs.com/misc/config#registry):\n\n```json\n  \"publishConfig\": {\n    \"registry\": \"http://my-awesome-registry.com/\"\n  }\n```\n\n- Passing [`--registry`](#--registry-url) applies globally, and in some cases isn't what you want.\n\n### `publishConfig.tag`\n\nYou can customize the dist-tag on a per-package basis by setting [`tag`](https://docs.npmjs.com/misc/config#tag):\n\n```json\n  \"publishConfig\": {\n    \"tag\": \"flippin-sweet\"\n  }\n```\n\n- Passing [`--dist-tag`](#--dist-tag-tag) will _overwrite_ this value.\n- This value is _always_ ignored when [`--canary`](#--canary) is passed.\n","engines":{"node":">= 6.9.0"},"gitHead":"713f72d1d5bd358147bb50df65b203b43a4667f8","license":"MIT","scripts":{"test":"echo \"Run tests from root\" && exit 1"},"_npmUser":{"name":"evocateur","email":"daniel.stockman@gmail.com"},"homepage":"https://github.com/lerna/lerna","keywords":["lerna","command"],"deprecated":"Package no longer supported. Contact Support at https://www.npmjs.com/support for more info.","repository":{"url":"git+https://github.com/lerna/lerna.git","type":"git"},"_npmVersion":"lerna/3.10.4/node@v10.15.0+x64 (darwin)","description":"Publish packages in the current project","directories":{},"maintainers":[{"name":"evocateur","email":"daniel.stockman@gmail.com"},{"name":"hzoo","email":"hi@henryzoo.com"}],"_nodeVersion":"10.15.0","dependencies":{"p-map":"^1.2.0","libnpm":"^2.0.1","p-pipe":"^1.2.0","semver":"^5.5.0","fs-extra":"^7.0.0","p-reduce":"^1.0.0","p-finally":"^1.0.0","@lerna/output":"3.6.0","@lerna/prompt":"3.6.0","figgy-pudding":"^3.5.1","@lerna/command":"3.10.0","@lerna/version":"3.10.5","@lerna/npm-conf":"3.7.0","@lerna/log-packed":"3.6.0","@lerna/npm-publish":"3.10.5","@lerna/describe-ref":"3.10.0","@lerna/npm-dist-tag":"3.8.5","@lerna/child-process":"3.3.0","@lerna/run-lifecycle":"3.10.5","@lerna/batch-packages":"3.10.0","@lerna/pack-directory":"3.10.5","@lerna/collect-updates":"3.10.1","@lerna/pulse-till-done":"3.7.1","@lerna/validation-error":"3.6.0","@lerna/check-working-tree":"3.10.0","@lerna/run-parallel-batches":"3.0.0"},"publishConfig":{"access":"public"},"_hasShrinkwrap":false,"readmeFilename":"README.md","_npmOperationalInternal":{"tmp":"tmp/publish_3.10.5_1547169407996_0.6117468745924752","host":"s3://npm-registry-packages"},"_id":"@lerna/publish@3.10.5","version":"3.10.5"}