Skip to content

docs(essentials): elaborate on install process #4430

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.

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

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

Conversation

eric-burel
Copy link

@eric-burel eric-burel commented May 4, 2022

What's the problem this PR addresses?

Yarn install is doing a lot more in v2+ than it use to do in classic. It makes lerna bootstrap or npm prune obsolete. Yet the documentation is quite terse about that.

How did you fix it?

  • make it clear that packages are pruned (no need for "npm prune" or removing "node_modules", just running "yarn install" cleans up the repo)
  • make it clear that you don't need things like "lerna bootstrap", as yarn already handle the links between workspaces / creating symlinks

Checklist

  • I have set the packages that need to be released for my changes to be effective.
  • I will check that all automated PR checks pass before the PR gets reviewed.

- make it clear that packages are pruned (no need for "npm prune" or removing "node_modules", just running "yarn install" cleans up the repo)
- make it clear that you don't need things like "lerna bootstrap", as yarn already handle the links between workspaces / creating symlinks
Comment on lines +29 to +31
Packages present in the `node_modules` folder but not in the `package.json` will be automatically pruned.

If you are using workspaces, the installation process will respect their topology and create appropriate symlinks.
Copy link
Member

@merceyz merceyz May 4, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is specific to the node-modules linker, not installs in general. We should instead reword This command sets up your project if needed to indicate that the linker might remove stuff.

We should also remove the Note that running this command is not part of the recommended workflow section as it was written a long time ago and isn't accurate anymore.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks! I'll have to dig a bit more the node-modules linker before being able to improve that or put it in the right place, I only had the chance to do a quick read of the "pnp" doc

@merceyz merceyz changed the title Elaborate on install process docs(essentials): elaborate on install process May 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants