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

Add a means of disabling cache in development mode, cache docs #761

Open
jywarren opened this issue Feb 12, 2019 · 8 comments
Open

Add a means of disabling cache in development mode, cache docs #761

jywarren opened this issue Feb 12, 2019 · 8 comments

Comments

@jywarren
Copy link
Member

I've continued having some issues with the cache, but it's hard to tell if I am seeing correct behaviors. I'd like to propose a few things, first that of the title - a way to disable the cache if it's running locally in development, to speed up local development.

(could relate to #544, #605)

Next (we can break out a new issue for this), I'd like to add more documentation about the cache, such as:

  1. where cache is stored and how to clear it from the javascript console in a browser window
  2. what sw.js is and what it does exactly
  3. documentation of this type of caching overall (MDN?) and it's purpose
  4. relation to Empty Cache and Hard Reload in Chrome; does this reload the cache?
  5. if the cache means we should be able to access Image Sequencer while not connected to the internet (this doesn't seem to work for me)
  6. the exact steps for updating the cache version (i see v3 cited in the gh-pages footer, but it never changes)
  7. what updating the cache version does

Thanks everyone, i think the cache is a little bit mysterious and we could do better on documenting its usage!

@jywarren
Copy link
Member Author

@publiclab/is-reviewers what do you think of this? Any input on the cache in general? Thank you!!!

@Mridul97
Copy link

@jywarren It's a great idea. Clearing cache everytime to see changes during development slows the process.

@tech4GT
Copy link
Member

tech4GT commented Feb 12, 2019

@Mridul97 @jywarren you can disable it in your devtools.

@jywarren
Copy link
Member Author

jywarren commented Feb 13, 2019 via email

@tech4GT
Copy link
Member

tech4GT commented Feb 16, 2019

@jywarren
Copy link
Member Author

jywarren commented Mar 2, 2019

OK, awesome:

image

I still wonder if there is a way to do it in the code too, and leave it that way for development?

@VladimirMikulic
Copy link

VladimirMikulic commented Jan 12, 2020

@tech4GT it doesn't work anymore. Probably there is a bug with the service worker that handles it.

Screenshot_20200112_115053

Screenshot_20200112_115138

@VladimirMikulic
Copy link

The cache from a few days ago was as big as 712 megabytes from the image-sequencer in development mode! Unfortunately, I forgot to take a screenshot of it before I cleared it.
Not to mention high CPU usage, DevTools RAM usage exceeded 2GB of RAM!

This project has some huge issues in the development mode.

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

4 participants