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
Today there is no logic implemented to clean up old or unused cypress binaries from the cache. This could use up a large amount of space on a users computer unnecessarily . With the proposed addition of downloadable browser binaries this problem could get worse. The ask is to design and implement a system to remove binaries after a certian amount of time.
Why is it needed?
To reduce hard drive burden on a users computer over time.
Cases to consider, Does a user have multiple versions of cypress across several different repositories
What does the experience look like when the binary has been removed but npm has not re-installed.
Scope: we could scope this change to just the new browser binaries, but we should at least consider it for the cypress binary as well as we're building out a design that accounts for them.
The text was updated successfully, but these errors were encountered:
What would you like?
Today there is no logic implemented to clean up old or unused cypress binaries from the cache. This could use up a large amount of space on a users computer unnecessarily . With the proposed addition of downloadable browser binaries this problem could get worse. The ask is to design and implement a system to remove binaries after a certian amount of time.
Why is it needed?
To reduce hard drive burden on a users computer over time.
Cases to consider, Does a user have multiple versions of cypress across several different repositories
What does the experience look like when the binary has been removed but npm has not re-installed.
Scope: we could scope this change to just the new browser binaries, but we should at least consider it for the cypress binary as well as we're building out a design that accounts for them.
The text was updated successfully, but these errors were encountered: