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

docs(injected): more accurate description #471

Merged
merged 1 commit into from
Oct 27, 2023
Merged

docs(injected): more accurate description #471

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.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 4 additions & 2 deletions docs/package_json.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,9 @@ Additional meta information used for dependencies declared inside `dependencies`

### dependenciesMeta.*.injected

If this is set to true for a local dependency, the package will be hard linked to the modules directory, not symlinked.
If this is set to `true` for a local dependency, the package will be hard linked to the virtual store (`node_modules/.pnpm`) and symlinked from the virtual store to the modules directory.

If this is set to `false` or not set for a local dependency, the package will be symlinked directly from its location in the workspace to the module directory.

For instance, the following `package.json` in a workspace will create a symlink to `button` in the `node_modules` directory of `card`:

Expand Down Expand Up @@ -278,7 +280,7 @@ The referenced package does not need to match the overridden one:
"overrides": {
"bar": "$foo"
}
}
}
}
```

Expand Down