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

Jump to bottom

README update - avoid isses related to browser cache during development #94

Closed
wants to merge 1 commit into from
Closed

README update - avoid isses related to browser cache during development #94

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
10 changes: 10 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,6 +36,16 @@ On the other hand, if you're already bundling JavaScript and CSS through a Node-

But for greenfield apps using the default import-map approach, Propshaft can also work well, if you're able to deal with vanilla CSS.

## Avoid issues related to browser cache

Propshaft digests your file based on the content and your browser will by default cache the digested file.
There are cases where if a CSS file references
to another file via `@import url('/other-file.css)`
or `url(/image-that-may-change.png)` browser may not pick up that the
referenced file has changed.

That's why we recommend to turn of caching in your browser during
development (for example in Chrome you can `Disable the cache (while DevTools is open)`)

## Will Propshaft replace Sprockets as the Rails default?

Expand Down