Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Adds a note that yarn install doesn't generate a node_modules folder #6216

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Adds a note that yarn install doesn't generate a node_modules folder #6216

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
5 changes: 5 additions & 0 deletions packages/docusaurus/docs/getting-started/basics/usage.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,11 @@ sidebar_position: 4
If you're coming from npm, the main changes are:

- Running `yarn` is enough to run an install! It's an alias to `yarn install`.

:::note
By default `yarn install` uses the [Plug'n'Play](/features/pnp) install strategy, which doesn't generate a `node_modules` folder. This can be changed using the `nodeLinker` configuration setting.
:::

- Adding or updating a dependency to a single package is done with `yarn add`.
- Upgrading a dependency across the whole project is done with `yarn up`.
- Your scripts are aliased. Calling `yarn build` is the same as `yarn run build`!
Expand Down