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
vite_ruby uses the mtime as a reference to detect different versions of the app: https://github.com/ElMassimo/vite_ruby/blob/main/vite_ruby/lib/vite_ruby/commands.rb#L148 That being said, a single Vite build can generate files with more than one mtime. For example, vite-plugin-rails uses rollup-plugin-gzip at the end of the build which will write many files with different mtimes.
This causes files to delete unexpectedly when running bin/vite clean. It's possible this bug is hard to reproduce with a small project as all written files may end up having the same mtime.
Reproduction 馃悶
Vite Ruby Info
Run bin/rake vite:build on a big project with no currently built assets.
Run bin/rake vite:clean[1,0]
Result: files will be deleted while there is only a single version of the built assets.
The text was updated successfully, but these errors were encountered:
Description 馃摉
vite_ruby
uses themtime
as a reference to detect different versions of the app: https://github.com/ElMassimo/vite_ruby/blob/main/vite_ruby/lib/vite_ruby/commands.rb#L148 That being said, a single Vite build can generate files with more than onemtime
. For example,vite-plugin-rails
usesrollup-plugin-gzip
at the end of the build which will write many files with differentmtime
s.This causes files to delete unexpectedly when running
bin/vite clean
. It's possible this bug is hard to reproduce with a small project as all written files may end up having the samemtime
.Reproduction 馃悶
Vite Ruby Info
bin/rake vite:build
on a big project with no currently built assets.bin/rake vite:clean[1,0]
Result: files will be deleted while there is only a single version of the built assets.
The text was updated successfully, but these errors were encountered: