From 7a6a3dd3e0996b0e2323e29a2a08eea0d9c71de8 Mon Sep 17 00:00:00 2001 From: Jonathan Rochkind Date: Fri, 1 Nov 2024 09:21:26 -0400 Subject: [PATCH] Helpfully mention assets:clobber in UPGRADING.md --- UPGRADING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/UPGRADING.md b/UPGRADING.md index c479333..bc2fbaa 100644 --- a/UPGRADING.md +++ b/UPGRADING.md @@ -261,6 +261,6 @@ raw Rails.application.assets.load_path.find('logo.svg').content Propshaft uses a dynamic assets resolver in development mode. However, when you run `assets:precompile` locally Propshaft will then switch to a static assets resolver. Therefore, changes to assets will not be observed anymore and you will have to precompile the assets each time changes are made. This is different to Sprockets. -If you wish to have dynamic assets resolver enabled again, you need to clean your target folder (usually `public/assets`) and propshaft will start serving dynamic content from source. +If you wish to have dynamic assets resolver enabled again, you need to clean your target folder (usually `public/assets`) and propshaft will start serving dynamic content from source. One way to do this is to run `rails assets:clobber`. Another way to watch changes in your CSS & JS assets is by running `bin/dev` command instead of `rails server` that not only runs the server but also keeps looking for any changes in the assets and once it detects any changes, it compiles them while the server is running. This is possible because of the `Procfile.dev`.