Ensure "Developer: Reload Window" actually picks up new css file contents

[tmm1]

I made an edit to a css file, and then used Reload Window from the command palette. The css change was not present, and when I looked at the Sources list in the developer tools, the old file contents were still present.

Adding a random query param to force disk loads fixed the issue, so I created this PR with that change.

(Is there a better dev workflow for testing css changes? The setupCSSImportMaps step seems quite slow)

[tmm1]

Is there a better dev workflow for testing css changes?

An approach used by others is to watch the css files for changes and update the nocache parameters: https://github.com/dperrymorrow/electron-css-reload?tab=readme-ov-file#how-does-it-work

[deepak1556]

Hi, thanks for the PR. Yeah this is a known issue and is not restricted to css files, we have tracked the root cause in #234357. The tl:dr; is that cache validation headers are not respected for custom protocols in the runtime today. I am not aware of better workarounds than disabling the in-memory cache.

If we want to land a workaround till the runtime issue is fixed then I suggest we add the no-cache header to the protocol layer (/protocolMainService.ts) when running out of sources.

[tmm1]

Interesting, thank you for the additional context!