Ensure "Developer: Reload Window" actually picks up new css file contents #237603
+1
−1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
setupCSSImportMapsstep seems quite slow)