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
We skip re-optimizing assets when we see the file in the build cache. The asset name has the hash of the input contents and asset options so if we see the same name, the optimized version is always the same. However since we output assets to a different place in debug vs release builds, we end up re-optimizing assets when switching between the two builds
Implement Suggestion
Use a shared location for the asset optimization cache and copy assets from there into the final build
The text was updated successfully, but these errors were encountered:
Feature Request
We skip re-optimizing assets when we see the file in the build cache. The asset name has the hash of the input contents and asset options so if we see the same name, the optimized version is always the same. However since we output assets to a different place in debug vs release builds, we end up re-optimizing assets when switching between the two builds
Implement Suggestion
Use a shared location for the asset optimization cache and copy assets from there into the final build
The text was updated successfully, but these errors were encountered: