Skip to content

docs: fix link to the portal protocol #5852

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

Merged
merged 1 commit into from
Oct 24, 2023
Merged
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -15,4 +15,4 @@ yarn add imgs@link:./static/imgs

Since the target referenced by `link:` may not exist until postinstall scripts have run, and since Yarn guarantees a predictable behavior regardless of the execution order, we need to disambiguate *packages* (which contain `package.json` files, and may list dependencies of their own) from *arbitrary folders* (which may not).

In practice, this means that `link:` dependencies can only point to arbitrary folders - in other words, whatever it references cannot have a `package.json` file, and thus can't have dependencies. If you need to symlink to a *package*, use [portals](/protocols/portal) instead.
In practice, this means that `link:` dependencies can only point to arbitrary folders - in other words, whatever it references cannot have a `package.json` file, and thus can't have dependencies. If you need to symlink to a *package*, use [portals](/protocol/portal) instead.