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
The user's lockfile should always be included in every cache key, unless we start doing static analysis of tasks to find out which packages they use like a big boy build system (Let's not do that 😓)
We can add an unsafe option to the CacheConfig type to turn off this behaviour on a per-script basis, maybe unsafe_excludeLockfile
Note that the lockfile path can be configured in yarn. Doesn't look like that's the case with npm/pnpm.
The text was updated successfully, but these errors were encountered:
The user's lockfile should always be included in every cache key, unless we start doing static analysis of tasks to find out which packages they use like a big boy build system (Let's not do that 😓)
We can add an unsafe option to the
CacheConfig
type to turn off this behaviour on a per-script basis, maybeunsafe_excludeLockfile
Note that the lockfile path can be configured in yarn. Doesn't look like that's the case with npm/pnpm.
The text was updated successfully, but these errors were encountered: