Fix #10893 Making sure scripts from extensions are not cached #10895
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.
Description
This way intex.js is appended by a random param making sure that script will not be cached.
I just noticed that removeExtensions seems not be triggered when removing the installed extension. can you double check is the case?
Please check if the PR fulfills these requirements
What kind of change does this PR introduce? (check one with "x", remove the others)
Issue
What is the current behavior?
Fix #10893
What is the new behavior?
index.js of the extensions will not be cached
Breaking change
Does this PR introduce a breaking change? (check one with "x", remove the other)
Other useful information
to test this locally when targeting dev env