这是indexloc提供的服务,不要输入任何密码
Skip to content
Discussion options

You must be logged in to vote

So, by default, turbo stays out of the package install management lifecycle. That's deeply integrated with each package manager and is not something we can safely intercept. You've noted multiple types of behavior where attempting to cache the results of an install could lead to incorrect behavior. Caching of that lifecycle is best handled by the package managers themselves.

In a monorepo, riding on the install rails (prepare, postinstall) isn't an approach I would recommend; I'd typically just encourage ^build which will make sure that all things are built correctly. The first <package manager> install will set up all the workspace links correctly, and then you'd only call install again …

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by nathanhammond
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Help
Labels
None yet
2 participants