From 64b60a1831a6fc5f0d31ec8721f68fbc834e8caa Mon Sep 17 00:00:00 2001 From: Quinton Aiken Date: Mon, 22 Jul 2019 09:50:48 -0700 Subject: [PATCH] docs(faq): Remove Extra Word / Tweak Spacing (#2192) [skip ci] --- FAQ.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/FAQ.md b/FAQ.md index a9a840b692..440e71429a 100644 --- a/FAQ.md +++ b/FAQ.md @@ -1,6 +1,6 @@ # Frequently asked questions -*This document is a work in progress.* +_This document is a work in progress._ ## How do I add a package to my Lerna repository? @@ -19,7 +19,7 @@ as normal to create the `package.json` for your new package. You can use [`lerna import `][import] to transfer an existing package into your Lerna repository; this command will preserve the commit history. -[`lerna import `][import] takes a local path rather than a URL. In this +[`lerna import `][import] takes a local path rather than a URL. In this case you will need to have the repo you wish to link to on your file system. [bootstrap]: https://github.com/lerna/lerna/blob/master/commands/bootstrap/README.md @@ -27,11 +27,11 @@ case you will need to have the repo you wish to link to on your file system. ## How do I retry publishing if `publish` fails? -Sometimes, `lerna publish` does not work. Your network may have had a hiccup, you may have not been logged on to npm, etc. +Sometimes, `lerna publish` does not work. Your network may have had a hiccup, you may have not been logged on to npm, etc. If the `lerna.json` has not yet been updated, simply try `lerna publish` again. -If it has been updated, you can force re-publish. `lerna publish --force-publish $(ls packages/)` +If it has been updated, you can force re-publish. `lerna publish --force-publish $(ls packages/)` ## The bootstrap process is really slow, what can I do? @@ -46,7 +46,7 @@ In combination with that you may increase the bootstrap performance even more by ## Root `package.json` The root `package.json`, at the very least, is how you install `lerna` locally during a CI build. -You should also put there your testing, linting and similar tasks there to run them from root +You should also put your testing, linting and similar tasks there to run them from root as running them separately from each package is slower. The root can also hold all the "hoisted" packages, which speeds up bootstrapping when using the [`--hoist`][hoist] flag. @@ -61,6 +61,7 @@ As mentioned above root `package.json` is responsible for installing `lerna` loc This can be achieved by putting it as npm script to use it during CI phases. Example root `package.json`: + ```json { "name": "my-monorepo", @@ -79,6 +80,7 @@ Example root `package.json`: ``` Example CircleCI's configuration file (`circle.yml`): + ```yml dependencies: post: