Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cache problems #2161

Open
Tracked by #2166
COD3BREAK3R opened this issue May 6, 2024 · 5 comments
Open
Tracked by #2166

Cache problems #2161

COD3BREAK3R opened this issue May 6, 2024 · 5 comments

Comments

@COD3BREAK3R
Copy link

Currently the extension has serious problems with the cache, many times even if changes are made to js files and the refresh button is pressed, these are not reflected

@captainbrosset
Copy link
Collaborator

Thanks for reaching out. I'm surprised because, in theory, the extension itself shouldn't play a role in caching.
Caching problems in web dev can either be due to your changes not having been deployed to your web server, or to app caching strategy problems. The extension in itself, doesn't have anything to do with those things.

Are you using the embedded browser preview, in VS Code? Or an external browser?
If the former, then perhaps the refresh button only does a "light" refresh, and your newly changed files are not being retrieved from the server. You can avoid this by versioning your files in development so that every time there's a change, their URLs are different.

You can also disable the cache from the Network tool in DevTools:

image

Let me know if this helps.

@COD3BREAK3R
Copy link
Author

COD3BREAK3R commented May 7, 2024

Thanks for reaching out. I'm surprised because, in theory, the extension itself shouldn't play a role in caching. Caching problems in web dev can either be due to your changes not having been deployed to your web server, or to app caching strategy problems. The extension in itself, doesn't have anything to do with those things.

Are you using the embedded browser preview, in VS Code? Or an external browser? If the former, then perhaps the refresh button only does a "light" refresh, and your newly changed files are not being retrieved from the server. You can avoid this by versioning your files in development so that every time there's a change, their URLs are different.

You can also disable the cache from the Network tool in DevTools:
Let me know if this helps.

The error occurs with Edge in headless mode and with linked JavaScript files. If it's a script within the HTML document, there is no problem. This issue is sometimes resolved by closing the instance and opening another one. Only linked .js files present the problem. There is no problem with the js files when using the external Edge browser.

However, I have encountered an issue when using the "Launch Edge and attach Dev Tools" mode from the Debug options in VSCode. In this case, when opening the inspector of Edge Dev Tools for the second time after closing it, it does not load.

@COD3BREAK3R
Copy link
Author

And when the issue with the JavaScript files occurs, it is not resolved by disabling the cache from the DevTools inspector.

@captainbrosset
Copy link
Collaborator

Thanks for the additional details.

@vidorteg does the extension implement some kind of caching that couple explain what @COD3BREAK3R is seeing here?

@naagadhepthi-11 naagadhepthi-11 mentioned this issue May 8, 2024
@rpatidar
Copy link

I was having same issues, until i figured out this was coming from the extensions. the problems were addressed but still it was showing them up

  1. It was looking into the dist directory don't know why
  2. it was showing problems for some files which were created but deleted as well.

I removed the extensions and all problems gone.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants