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

Handle / resolve workspaces that reference one another #130

Open
voxpelli opened this issue Apr 4, 2024 · 1 comment
Open

Handle / resolve workspaces that reference one another #130

voxpelli opened this issue Apr 4, 2024 · 1 comment

Comments

@voxpelli
Copy link
Owner

voxpelli commented Apr 4, 2024

Eg. knip references a shared eslint-config from its packages: https://github.com/webpro/knip/blob/a69b2b859f28cb4e97254c7147f2799308f7e6cc/packages/knip/package.json#L90

And eg pnpm itself also does

@voxpelli
Copy link
Owner Author

voxpelli commented Apr 4, 2024

Kind of done with [email protected] as it now follows symlinks.

Still doesn't take interdependency in consideration when suggesting engine ranges though, so if X relies on Y and Y has a tighter suggested engine range than X, then X will not get that engine range suggested until the engine range of Y has been fixed.

This is especially a blocker for voxpelli/node-installed-check#89

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

No branches or pull requests

1 participant