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.

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

Peer dependencies are not linked #68

Open
aleclarson opened this issue Dec 17, 2024 · 1 comment
Open

Peer dependencies are not linked #68

aleclarson opened this issue Dec 17, 2024 · 1 comment
Labels
bug Something isn't working has workaround A workaround for this bug is known pnpm Related to PNPM use specifically

Comments

@aleclarson
Copy link
Collaborator

When linking to a local package [A] that another dependency [B] has a "peer dependency" on, the package [A] is not linked into dependency [B] as you might expect. In other words, even though my monorepo uses the local version of package [A], the dependency [B] uses the installed version.

@aleclarson aleclarson added bug Something isn't working pnpm Related to PNPM use specifically labels Dec 17, 2024
@aleclarson
Copy link
Collaborator Author

As a (bad) workaround, you can use the link: protocol:

// In the package.json where the peer is installed:
"foo": "link:./path/to/vendor/foo"

The vendor folder exists in the same folder your .indo.json file exists, so you'll have to consider that when writing the link: path.

@aleclarson aleclarson added the has workaround A workaround for this bug is known label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working has workaround A workaround for this bug is known pnpm Related to PNPM use specifically
Projects
None yet
Development

No branches or pull requests

1 participant