Heroku Issue: ActionView::Template::Error (The asset "tailwind.css" is not present in the asset pipeline.") #153

Dnncha · 2022-02-27T00:09:37Z

Hi

Thanks for your work.

I'm running a very simple Rails 7.0.2.2 which I've just set up.

Everything is working swimmingly locally, but when I deploy to heroku I'm getting the following error when I try to view a page:

ActionView::Template::Error (The asset "tailwind.css" is not present in the asset pipeline.)

I have checked to ensure that sassc-rails is disabled in the Gemfile.

I have also tried adding

config.assets.css_compressor = nil

to production.rb, but the error remains.

Any ideas where I am going wrong?

Thanks

joao99c · 2022-03-03T15:12:49Z

I fixed this problem running:
gem install bundler
bundle update --bundler
bundle lock --add-platform x86_64-linux

Commit and push to heroku.
Hope it helps!
JC

peteoliveira · 2022-03-05T18:32:37Z

I am seeing the same issue when running tests on github. My configuration is using importmap
config.assets.css_compressor = nil did not work and x86_64-linux is already present in Gemfile.lock

Recordings GET /new returns http success
Failure/Error: <%= stylesheet_link_tag "tailwind", "inter-font", "data-turbo-track": "reload" %>
ActionView::Template::Error:
The asset "tailwind.css" is not present in the asset pipeline.
./app/views/layouts/application.html.erb:12:in _app_views_layouts_application_html_erb__1997779[47](https://github.com/nuance-internal/sphere-enterprise/runs/5434230804?check_suite_focus=true#step:6:47)84[49](https://github.com/nuance-internal/sphere-enterprise/runs/5434230804?check_suite_focus=true#step:6:49)135196_69[50](https://github.com/nuance-internal/sphere-enterprise/runs/5434230804?check_suite_focus=true#step:6:50)0' ./spec/requests/recordings_spec.rb:6:in block (3 levels) in '
--- Caused by: ---
Sprockets::Rails::Helper::AssetNotFound:
The asset "tailwind.css" is not present in the asset pipeline.
./app/views/layouts/application.html.erb:12:in `_app_views_layouts_application_html_erb__1997779478449135196_69500'

dmarcoux · 2022-03-05T20:59:26Z

@peteoliveira: If you have this issue while running tests in your continuous integration, you need to precompile assets with:

bundle exec rake assets:precompile

I had the same issue and this fixed it.

peteoliveira · 2022-03-05T23:26:24Z

@dmarcoux That worked, thanks!

ur5us · 2022-03-15T06:40:07Z

@dmarcoux Shouldn’t CI be handled by the Rake tasks?

Rake::Task["assets:precompile"].enhance(["tailwindcss:build"])

if Rake::Task.task_defined?("test:prepare")
  Rake::Task["test:prepare"].enhance(["tailwindcss:build"])
elsif Rake::Task.task_defined?("db:test:prepare")
  Rake::Task["db:test:prepare"].enhance(["tailwindcss:build"])
end

Having said that, I’m having the same issue in CircleCI. I call bin/rails db:test:prepare explicitly before running RSpec but that tailwindcss:build task is never executed. Am I misunderstanding those *test:prepare enhancements?

dmarcoux · 2022-03-15T08:23:19Z

I didn't know about those enhance calls. I prepare my test database with bundle exec rake db:reset. I'll give bundle exec rake db:test:prepare a try. It should build Tailwind CSS assets before preparing the test database. This sounds exactly like what we need.

Edit: After giving the rake task db:test:prepare a try, it's not calling the rake task tailwindcss:build. I don't know why, because this should happen.

ur5us · 2022-03-15T08:44:14Z

@dmarcoux

Edit: After giving the rake task db:test:prepare a try, it's not calling the rake task tailwindcss:build. I don't know why, because this should happen.

Yeah, this is exactly what I’m seeing also as mentioned:

I call bin/rails db:test:prepare explicitly before running RSpec but that tailwindcss:build task is never executed.

Maybe @flavorjones or @dhh can shine some light?

elgrillo83 · 2022-03-24T13:17:21Z

Similar things are happening to me after updating the tailwindcss-rails gem from 2.0.5 to 2.0.8:

# Excerpt from my `Gemfile.lock`:

rails (7.0.2.3)

- tailwindcss-rails (2.0.5-arm64-darwin)
+ tailwindcss-rails (2.0.8-arm64-darwin)

RUBY VERSION
   ruby 3.0.3p157

BUNDLED WITH
   2.2.32

The tests run by GitHub CI were then failing with:

ActionView::Template::Error: couldn't find file 'tailwind.css'

After re-reading https://github.com/rails/tailwindcss-rails#building-for-testing, I was able to fix that by adapting the run script:

# Excerpt from my `.github/workflows/ci.yml`:

- run: bin/rake test
+ run: bin/rake test:all

Not running rake db:test:prepare though, just rake db:setup.

Timmitry · 2022-06-28T09:23:22Z

I also suddenly had this problem after upgrading tailwindcss-rails from 2.0.5 to 2.0.10.

The problem is present both locally (after removing old assets with bin/rails assets:clobber) and on the continuous integration.

I solved it by adding the following to my system test configuration:

# spec/support/system_test_configuration.rb
# Could alternatively be added to `rails_helper.rb` or `spec_helper.rb`
RSpec.configure do |config|
  ...

  config.before(:suite) do
    if config.files_to_run.any? { |path| path.start_with?(Rails.root.join("spec/system").to_s) }
      Rails.application.load_tasks
      Rake::Task["tailwindcss:build"].invoke
    end
  end
end

Works like a charm. Still seems like a breaking change in a patch version, though 😉

~~It is not perfect, as it will always compile tailwind before a test run, even if no system tests are involved (e.g. when running bin/rspec spec/models).~~ Edit: Updated the code snippet - it now only compiles if any system tests are run.

ionmx · 2022-07-21T04:23:29Z

@dmarcoux Great! it works like a charm... I'm using the Ruby On Rails CI provided by GitHub Actions, I added the assets precompile before running the tests.

...
# Precompile assets
- name: Assets Precompile
  run: bundle exec rake assets:precompile
# Add or replace test runners here
- name: Run tests
  run: bin/rake
...

gabrielboeker · 2022-08-18T14:18:48Z

none of the suggested solutions work for me which is really frustrating since my productive env is broken right now... staging works fine though.

Edit: Turns out in my gitignore i had /app/assets/builds/* which caused this issue... commenting out the line did the trick. weird.

seanbjornsson · 2022-08-24T15:38:45Z

~~tailwindcss:build was not sufficient for me to fix this issue. I have to run precompile:assets to resolve this.~~
Edit: I spoke too soon. This resolves the issue locally but not on Gitlab CI

What ended up working:

# config/application.rb
config.assets.css_compressor = nil

hendricius · 2022-08-24T15:44:15Z

none of the suggested solutions work for me which is really frustrating since my productive env is broken right now... staging works fine though.

Edit: Turns out in my gitignore i had /app/assets/builds/* which caused this issue... commenting out the line did the trick. weird.

/app/assets/builds/*

@gabrielboeker Wouldn't that mean that you have to commit your assets all the time?

noahd1 · 2022-08-30T20:36:23Z

For me, it was helpful to see which tasks tailwindcss-rails hooks into. You can see that here:

https://github.com/rails/tailwindcss-rails/blob/main/lib/tasks/build.rake#L15-L21

If you're using RSpec, you need to figure out a way to build tailwind's CSS or you'll receive this error.

@Timmitry 's solution worked for me in this case. I also put the whole block in a unless ENV["CI"] because CI precompiles assets, which in turn, as per the task definition, builds tailwind as well. Otherwise, tailwind would be built more than once (not the end of the world but simple to avoid).

flavorjones · 2022-09-03T18:11:21Z

If someone on this thread would be willing to submit a documentation PR to update the README, I would be very grateful!

Zuhaib042 · 2023-02-16T15:03:36Z

none of the suggested solutions work for me which is really frustrating since my productive env is broken right now... staging works fine though.

Edit: Turns out in my gitignore i had /app/assets/builds/* which caused this issue... commenting out the line did the trick. weird.
Thank you so much man, I was in deep trouble and spent hours fixing this tailwind asset pipeline issue while deploying rails app on render.
I actually noticed that .gitignore has this /app/assets/builds/* and then when I found out your solution then I went away with it and solved it.

olivierlacan · 2023-04-21T01:01:11Z

For the goofballs like me who don't notice a compilation error and only notice the failure to precompile tailwind.css I strongly recommend checking our CI output for a CssSyntaxError caused by (for example) usage of a non-existent CSS class with @apply.

Since this happened in my Setup test database stage and (annoyingly) didn't result in a 1 exit code (which would be best IMO, but may not be straightforward to achieve), I assumed wrongly that something had indeed failed to precompile tailwind.css despite my correct usage of db:test:prepare in my setup.

Nope, turned out I derped and Tailwind errored when trying to compile my typo, but then it failed to compile — as you'd expect.

Output from bin/rails db:create db:schema:load test:prepare step in GitHub Actions:

Run bin/rails db:create db:schema:load test:prepare
Database 'maison_test' already exists
["/home/runner/work/maison/maison/vendor/bundle/ruby/3.2.0/gems/tailwindcss-rails-2.0.21-x86_64-linux/exe/x86_64-linux/tailwindcss", "-i", "/home/runner/work/maison/maison/app/assets/stylesheets/application.tailwind.css", "-o", "/home/runner/work/maison/maison/app/assets/builds/tailwind.css", "-c", "/home/runner/work/maison/maison/config/tailwind.config.js", "--minify"]

Rebuilding...
CssSyntaxError: tailwindcss: /home/runner/work/maison/maison/app/assets/stylesheets/application.tailwind.css:86:5: The `grid-flow-cols` class does not exist. If `grid-flow-cols` is a custom class, make sure it is defined within a `@layer` directive.
    at Input.error (/snapshot/tailwindcss/node_modules/postcss/lib/input.js:148:16)
    at AtRule.error (/snapshot/tailwindcss/node_modules/postcss/lib/node.js:60:32)
    at processApply (/snapshot/tailwindcss/lib/lib/expandApplyAtRules.js:376:29)
    at /snapshot/tailwindcss/lib/lib/expandApplyAtRules.js:524:9
    at /snapshot/tailwindcss/lib/processTailwindFeatures.js:55:50
    at Object.Once (/snapshot/tailwindcss/lib/cli/build/plugin.js:251:19)
    at LazyResult.runOnRoot (/snapshot/tailwindcss/node_modules/postcss/lib/lazy-result.js:337:23)
    at LazyResult.runAsync (/snapshot/tailwindcss/node_modules/postcss/lib/lazy-result.js:393:26)
    at async build (/snapshot/tailwindcss/lib/cli/build/index.js:42:9) {
  reason: 'The `grid-flow-cols` class does not exist. If `grid-flow-cols` is a custom class, make sure it is defined within a `@layer` directive.',
  file: '/home/runner/work/maison/maison/app/assets/stylesheets/application.tailwind.css',
  source: '@tailwind base;\n' +
    '\n' +
    '@layer base {\n' +
    '  body {\n' +
    '    @apply text-slate-300;\n' +
    '  }\n' +
    '\n' +
    '  header h1 {\n' +
    '    @apply text-2xl font-bold tracking-wide;\n' +
    '  }\n' +
    '\n' +
    '  header nav ul li {\n' +
    '    @apply font-extrabold tracking-wide;\n' +
    '  }\n' +
    '\n' +
    '  h1, h2, h3, h4, h5 {\n' +
    '    @apply text-slate-600 font-bold;\n' +
    '  }\n' +
    '\n' +
    '  h1 {\n' +
    '    @apply text-2xl my-5;\n' +
    '  }\n' +
    '  h2 {\n' +
      '    text-sm\n' +
      '    px-8\n' +
      '    py-6\n' +
      '    space-y-3\n' +
      '    shrink;\n' +
      '}\n',
    url: 'file:///home/runner/work/maison/maison/app/assets/stylesheets/application.tailwind.css',
    file: '/home/runner/work/maison/maison/app/assets/stylesheets/application.tailwind.css'
  },
  plugin: 'tailwindcss'
}

…comment-1219552343 will work

fwuensche · 2023-07-21T08:54:52Z

I can confirm that two of the previously suggested solutions work for me.

Run all tests at once with bundle exec rails test:all
Source: cherrypush/cherrypush.com@8088175

Explicitly precompile assets before running your tests
Source: cherrypush/cherrypush.com@3967c6e

I'm sticking to the second solution, this way I can keep unit tests separated from system tests.

You can also check the builds on the two last commits of this pull request: cherrypush/cherrypush.com#80

Hope that helps ❤️

kalashnikovisme · 2023-12-07T00:39:40Z

Running assets:precompile in CI for this purpose looks like an overhead.

Enhancing prepare commands with tailwindcss:build is the good idea and it's already implemented here

if Rake::Task.task_defined?("test:prepare")
  Rake::Task["test:prepare"].enhance(["tailwindcss:build"])
elsif Rake::Task.task_defined?("spec:prepare")
  Rake::Task["spec:prepare"].enhance(["tailwindcss:build"])
elsif Rake::Task.task_defined?("db:test:prepare")
  Rake::Task["db:test:prepare"].enhance(["tailwindcss:build"])
end

So, you can just add bin/rake spec:prepare for RSpec tests, for example 🙂

pas256 · 2024-05-02T06:04:53Z

What does rake spec:prepare do? It isn't listed when I run rake -T but somehow it still works and fixed my tests in CI (GitHub Actions). Thanks @kalashnikovisme

kalashnikovisme · 2024-05-02T18:26:43Z

@pas256 yeah, as I wrote above, this should have been fixed in the latest versions of the gem.

Happy that everything is ok now 🙂

fernandokosh · 2024-06-18T14:07:16Z

I only makethis working after run:

rake tailwindcss:build

andrew · 2024-10-02T08:24:52Z

My fix for this error was to make sure that the app/assets/builds directory is in git:

git add app/assets/builds.keep -f

sebastialonso · 2024-12-03T01:22:40Z

I'm experiencing this issue in production, even though I've already run or have these:

rake assets:precompile already runs tailwindcss:build
apps/assets/builds already contains a .keep and also a tailwind.css

Always getting

Sprockets::Rails::Helper::AssetNotFound (The asset "tailwind.css" is not present in the asset pipeline.

Here's a bare bones repo to reproduce: https://github.com/sebastialonso/tailwindcss-rails-dokku

Anybody managed to solve this?

aksafan · 2024-12-30T23:36:39Z

~~tailwindcss:build was not sufficient for me to fix this issue. I have to run precompile:assets to resolve this.~~ Edit: I spoke too soon. This resolves the issue locally but not on Gitlab CI

What ended up working:
# config/application.rb
config.assets.css_compressor = nil

The only thing that worked for me is adding Rails.application.config.assets.css_compressor = nil to initializers/assets.rb and I've tried everything from this thread and even more from the Internet.

Thanks for the help @seanbjornsson!

aksafan · 2024-12-30T23:38:31Z

none of the suggested solutions work for me which is really frustrating since my productive env is broken right now... staging works fine though.
Edit: Turns out in my gitignore i had /app/assets/builds/* which caused this issue... commenting out the line did the trick. weird.

/app/assets/builds/*

@gabrielboeker Wouldn't that mean that you have to commit your assets all the time?

Oh, I thought I got some kind of glitch or smth, cause I've just baked a sourdough bread by your recipe @hendricius and now I see you here answering about the Ruby. What a great coincidence!

jeffdill2 · 2025-03-06T22:08:04Z

For those who have mentioned removing /app/assets/builds/* from their .gitignore file, I'd recommend doing this instead of removing that line entirely:

/app/assets/builds/*
!/app/assets/builds/.keep

This will ignore ignore anything in the /builds directory except for the .keep file.

bilalhussain-dev · 2025-05-19T15:57:21Z

@peteoliveira: If you have this issue while running tests in your continuous integration, you need to precompile assets with:

bundle exec rake assets:precompile
I had the same issue and this fixed it.

Love it! Problem solved!

violeta-p mentioned this issue May 14, 2022

Implement dashboard layout Nikola-Nino/denta_life#13

Merged

flavorjones closed this as completed Sep 3, 2022

This was referenced Sep 4, 2022

Tailwind precomplieエラーの件 Kei5665/tokyo_senkyo_matching#45

Closed

Tailwindとsassc-railsの非互換問題を解決。 Kei5665/tokyo_senkyo_matching#46

Merged

kenchen1126 mentioned this issue Oct 1, 2022

step18_tailwind css SSUCHIYEH/ruby_training#13

Merged

momer added a commit to kwux/kwux-frontend that referenced this issue Jan 16, 2023

Allow serving of some public assets; rails/tailwindcss-rails#153

2eba6d0

maimux2x mentioned this issue Apr 16, 2023

モックを利用したログインのテストを書いた maimux2x/subsc.mine#96

Merged

tyrant referenced this issue in tyrant/blog May 21, 2023

Maaaaybe https://github.com/rails/tailwindcss-rails/issues/153\#issue…

8b7ab91

…comment-1219552343 will work

shasherazi mentioned this issue Jul 7, 2023

Create budget app shasherazi/budget-app#7

Merged

siroemk mentioned this issue Sep 14, 2023

CIが通るように修正した siroemk/cotomemory#117

Merged

YukiWatanabe824 mentioned this issue Nov 8, 2023

Tailwind CSSのビルドファイルエラー対応 YukiWatanabe824/MAAKS#263

Closed

Heroku Issue: ActionView::Template::Error (The asset "tailwind.css" is not present in the asset pipeline.") #153

Heroku Issue: ActionView::Template::Error (The asset "tailwind.css" is not present in the asset pipeline.") #153

Comments

Dnncha commented Feb 27, 2022

joao99c commented Mar 3, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

peteoliveira commented Mar 5, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

dmarcoux commented Mar 5, 2022

Uh oh!

peteoliveira commented Mar 5, 2022

Uh oh!

ur5us commented Mar 15, 2022

Uh oh!

dmarcoux commented Mar 15, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ur5us commented Mar 15, 2022

Uh oh!

elgrillo83 commented Mar 24, 2022

Uh oh!

Timmitry commented Jun 28, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ionmx commented Jul 21, 2022

Uh oh!

gabrielboeker commented Aug 18, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

seanbjornsson commented Aug 24, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

hendricius commented Aug 24, 2022 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

noahd1 commented Aug 30, 2022

Uh oh!

flavorjones commented Sep 3, 2022

Uh oh!

Zuhaib042 commented Feb 16, 2023

Uh oh!

olivierlacan commented Apr 21, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

fwuensche commented Jul 21, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kalashnikovisme commented Dec 7, 2023

Uh oh!

pas256 commented May 2, 2024

Uh oh!

kalashnikovisme commented May 2, 2024

Uh oh!

fernandokosh commented Jun 18, 2024

Uh oh!

andrew commented Oct 2, 2024

Uh oh!

sebastialonso commented Dec 3, 2024 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

aksafan commented Dec 30, 2024

Uh oh!

aksafan commented Dec 30, 2024

Uh oh!

jeffdill2 commented Mar 6, 2025

Uh oh!

bilalhussain-dev commented May 19, 2025

Uh oh!

joao99c commented Mar 3, 2022 •

edited

Loading

peteoliveira commented Mar 5, 2022 •

edited

Loading

dmarcoux commented Mar 15, 2022 •

edited

Loading

Timmitry commented Jun 28, 2022 •

edited

Loading

gabrielboeker commented Aug 18, 2022 •

edited

Loading

seanbjornsson commented Aug 24, 2022 •

edited

Loading

hendricius commented Aug 24, 2022 •

edited

Loading

olivierlacan commented Apr 21, 2023 •

edited

Loading

fwuensche commented Jul 21, 2023 •

edited

Loading

sebastialonso commented Dec 3, 2024 •

edited

Loading