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
Like dprint, the tool turborepo supports installing both globally and per-project through npm. When the globally-installed executable is run in a directory which has a local install, it automatically defers to the local version.
It seems to me that this sort of behavior would also be useful for dprint. You have the convenience of a global install, but developers on a team will automatically stay in sync and it's easy to switch between projects with different dprint versions. Is this a pattern that dprint could also support?
The text was updated successfully, but these errors were encountered:
Like dprint, the tool turborepo supports installing both globally and per-project through npm. When the globally-installed executable is run in a directory which has a local install, it automatically defers to the local version.
https://turbo.build/repo/docs/installing#install-per-repository
It seems to me that this sort of behavior would also be useful for dprint. You have the convenience of a global install, but developers on a team will automatically stay in sync and it's easy to switch between projects with different dprint versions. Is this a pattern that dprint could also support?
The text was updated successfully, but these errors were encountered: