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.

Sign up for GitHub

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

docs: document bug in safari that caches css and prevents hmr #261

Merged
merged 1 commit into from
Sep 20, 2022
Merged

docs: document bug in safari that caches css and prevents hmr #261

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Description of workaround for Safari
  • Loading branch information
@powersurge360
powersurge360 committed Sep 20, 2022
commit 3001145b7652480a7df4d0aaec136ad7449abf54
4 changes: 4 additions & 0 deletions docs/src/guide/troubleshooting.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -157,6 +157,10 @@ This is probably the case if you are seeing errors such as `#<Errno::EMFILE: Too

Follow [this article][ulimit] for information on how to increase the limit of file descriptors in your OS.

### CSS does not seem to reflect changes in dev

Stylesheets are sent with [etags](https://en.wikipedia.org/wiki/HTTP_ETag) which allow a browser to cache the stylesheet until it changes. In development, a `Cache-Control: no-cache` header is also sent but unfortunately Safari does not respect the header and caches it anyways. The simplest way to work around the issue is to import the CSS directly into your javascript entry points. When the CSS is requested in this way it is requested with a query string that seems to break the cache.

## Fixed Issues

### Build not working in CI or Heroku
Expand Down