Uncompile Development Asset Pipeline

Question

I was compiling my asset pipeline for my production environment and it did for all my environments. How can I uncompile my asset pipeline for my development environment?

I have checked my config/development environment and cannot find a fix.

Thanks in advance for any help...

Phil Bottomley · Accepted Answer · 2014-03-05T13:51:58.563

90

To remove precompiled assets use:

rake assets:clean

What this basically does is remove the public/assets directory. You may need to include the RAILS_ENV variable if you need to run it for a certain environment.

edited Mar 05 '14 at 13:51

answered Dec 20 '11 at 11:31

Phil Bottomley

2,387
1
17
20

11

This didn't work for me. I had to issue `RAILS_ENV=development bundle exec rake assets:clean`. – Tass Mar 11 '13 at 21:32
1

also, be sure to clear your browser cache. even after you've restarted your server, the pages served up may still include a cached copy of the compiled application.js file – Michael Apr 24 '13 at 02:03
3

Neither worked here, had to remove the entire `public/assets` folder. – Alvaro Lourenço May 03 '13 at 22:56
Did you put this line in your application.js '//= require_tree .' and this line in application.css '*= require_tree .' You need to to it. – Franzé Jr. Apr 01 '14 at 08:47
1

Or just remove your folder public/assets – Franzé Jr. Apr 01 '14 at 08:48
3

I'm not sure why they changed the syntax for Rails 4 to rake assets:clobber – Natus Drew Dec 23 '14 at 20:56

score 45 · Answer 2 · answered Dec 01 '14 at 16:29

45

Try using

rake assets:clobber

worked for me in rails 4

answered Dec 01 '14 at 16:29

mattecalcio

491
4
4

Care to explain why this works? Until then I cannot vote up your answer and frankly few people will, SO answers should help people understand the issue not just provide a line of code. – jasonleonhard Mar 02 '17 at 00:59
It deletes compiled assets. You can also manually remove them, this is just a shortcut. – mattecalcio Feb 11 '18 at 02:28

score 5 · Answer 3 · answered Jun 05 '17 at 17:55

5

For Rails 5:

$ RAILS_ENV=development bin/rake assets:clobber

answered Jun 05 '17 at 17:55

stujo

2,089
24
29

score 5 · Answer 4 · answered Dec 19 '11 at 04:38

When you run the compile task locally (on your development machine) the assets are compiled in the Rails production environment, but are written to the public folder.

This means that even when you run in development mode it'll use the compiled assets instead of sending requests to the pipeline. This is normal behavor - requests only go to the pipeline if the file does not exists in public/assets.

The compile task should generally only be used when deploying, and on the remote (production) machine.

If you have compiled locally, you can delete all the files in the public/assets folder and development will behave as before. If you checked these files into source control you'll need to remove them.

Once removed things should work fine. s One final tip: if this is an upgraded app check your config settings against those in the last section of the Rails asset pipeline guide.

At least this answer doesn't just provide a one line code answer, but attempts to explain. — jasonleonhard, Mar 02 '17 at 01:34

Uncompile Development Asset Pipeline

4 Answers4