Skip to content

Commit

Permalink
docs(faq): Remove Extra Word / Tweak Spacing (#2192)
Browse files Browse the repository at this point in the history
[skip ci]
  • Loading branch information
qaiken authored and evocateur committed Jul 22, 2019
1 parent 6770cee commit 64b60a1
Showing 1 changed file with 7 additions and 5 deletions.
12 changes: 7 additions & 5 deletions 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?

Expand All @@ -19,19 +19,19 @@ as normal to create the `package.json` for your new package.
You can use [`lerna import <package>`][import] to transfer an existing package
into your Lerna repository; this command will preserve the commit history.

[`lerna import <package>`][import] takes a local path rather than a URL. In this
[`lerna import <package>`][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
[import]: https://github.com/lerna/lerna/blob/master/commands/import/README.md

## 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?

Expand All @@ -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.

Expand All @@ -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",
Expand All @@ -79,6 +80,7 @@ Example root `package.json`:
```

Example CircleCI's configuration file (`circle.yml`):

```yml
dependencies:
post:
Expand Down

0 comments on commit 64b60a1

Please sign in to comment.