about few weeks ago, I juggle around reworking my workflow for slightly complex javascript assets(which needs to import multiple library from npm), which basically:
- create dedicated javascript project directory for specific bss project;
- create multiple module files to be consumed by main file;
- open bss js assets file in vscode;
- run
"bun build main.mjs --format iife --watch --outfile C:/Users/myComputer/AppData/Local/Temp/ext-tmp/1000/main/main.js"
which I notice, when temporary file changes, it will imediately trigger livereload, however the bss it self shows that the save button is active (“presumably” indicating the bss main file is yet to be saved),
what I’m asking is:
- are bss at this point is saved, but the
savebutton bugged? - are bss main file is not saved, but
livereloadis triggered anyway?
my take is, if the livereload is triggered, wouldn’t it seems more natural to make bss autosave the main file on the externally edited file changes event;
if it’s already implemented, then the save button need to be clear enough(to be disabled) to not to be ambiguous as of now;
also I sometimes noticed bugs, when:
- opening multiple file with external editor;
- changes multiple file but does not save them imediately;
- saves multiple file at once(vscode, using save all changed file);
will results in one file being chaged, the other revert to previous changes;
thx…