You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you use a monorepo, there could be shared tools installed in the repo root and then each package has its own unique dependencies. It would be nice to have them be in path.
Suggested solution:
when creating the PATH variable, walk up the path and add any subdirectories named node_modules/.bin.
The text was updated successfully, but these errors were encountered:
That could introduce ambiguity between bar's modules and monorepo's modules. We could define to use the more local ones preferentially, but I would think that if you have a script inside of bar, the dependencies of that script should also be contained within bar's modules. Is this not desirable in your case?
Problem description:
When you use a monorepo, there could be shared tools installed in the repo root and then each package has its own unique dependencies. It would be nice to have them be in path.
Suggested solution:
when creating the PATH variable, walk up the path and add any subdirectories named
node_modules/.bin
.The text was updated successfully, but these errors were encountered: