Benjamin Pasero

Yeah I would suggest we go into filing new issues for remaining regressions. Please ping me on these issues or mention them here. Thanks!

@RedCMD btw I would like to thank you for willing to bisect this down to the offending commit and for collecting all the related issues. Sorry it took us that...

I actually went ahead and reported https://github.com/microsoft/vscode/issues/240567 for the `editor.tabSize` issue. That one does not seem like it does have a straight forward fix, at least from my pov.

Pushed a workaround that would support specific spaces/tabs settings for `go`, `makefile`, `shellscript` and `yaml`, basically the languages we ship out of the box, by contributing these settings from core....

@deepak1556 any idea why `show: false` gives us white background flicker while `show: true` does not?

@deepak1556 so this is a different window than the one VS Code gets to be rendered in and with `show: false` it becomes initially briefly visible, while with `show: true`...

You can explicitly pass the `backend` to use as `options`: https://github.com/parcel-bundler/watcher?tab=readme-ov-file#options I am not aware that the watcher would fallback, I am not even sure what the fallback would be...

I am quite certain that parcel watcher would use `fsevents` on macOS and `ReadDirectoryChangesW` on Windows. This module does not depend on the NPM module that you refer to at...

Ok, now I am curious as well. I was not aware that `fsevents` would not be available on macOS (unless maybe very old macOS versions). And looking at the sources...

I can confirm that this change helps not showing the access dialog 👏 . //cc @devongovett