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

[Dnncha]

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]

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]

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

1. 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]

@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]

@dmarcoux That worked, thanks!

[ur5us]

@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]

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]

@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]

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]

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]

@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]

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]

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]

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]

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).