Missing asset log message for static assets in Propshaft 1.3+

[wlipa]

I have an app with a public/static directory which I manually version. It has things that don't change much like fonts and certain vendored js. In previous versions of propshaft, CSS urls could refer to these assets without an issue, but in the latest I get messages like this:

Unable to resolve '/static/fonts/Inter-v4.0/InterVariable.woff2' for missing asset 'static/fonts/Inter-v4.0/InterVariable.woff2' in main.css

The CSS declaration is:

@font-face {
  font-family: 'Inter';
  font-style: normal;
  font-weight: 100 900;
  src: url('/static/fonts/Inter-v4.0/InterVariable.woff2') format('woff2');
}

I tried adding public/static to the excluded directories, but no luck. How can I refer to particular static assets without triggering Propshaft digesting? I want to leave these URLs exactly as is.

[theodorton]

It's just a warning, it should still work as intended and leave the URL as is. Are you seeing a different output in your case?

[wlipa]

No, it is just a warning. Is there any way to avoid the new warning? I try to run without warnings.

[wlipa]

I can override the logger to deal with it, probably. But it'd be nice to have a config option to specify ignorable URL patterns.

[theodorton]

@wlipa I pushed a branch skip-resolve-warning-for-public-files - can you test with that and see if that gets rid of the warning?

[theodorton]

The convention would be to put fonts under app/assets/fonts/, which should solve the problem - are there any reasons for not doing that in your case?

[rafaelfranca]

Can you give us the result of bin/rails middleware? I think I put the Propashaft middleware before the static middleware by mistake

[rafaelfranca]

Accordingly with the tests in this commit this isn't the case rails/rails@6b11d3c.

But it could be the case in your app for some reason, so better to confirm

[wlipa]

$ bin/rails middleware
use Rack::Cors
use Honeybadger::Rack::UserInformer
use Honeybadger::Rack::UserFeedback
use Honeybadger::Rack::ErrorNotifier
use ActionDispatch::HostAuthorization
use Rack::Sendfile
use ActionDispatch::Static
use Propshaft::Server
use ActionDispatch::Executor
use ActionDispatch::ServerTiming
use Rack::Runtime
use Rack::MethodOverride
use ActionDispatch::RequestId
use RequestStore::Middleware
use ActionDispatch::RemoteIp
use Propshaft::QuietAssets
use Rails::Rack::Logger
use ActionDispatch::ShowExceptions
use ActionDispatch::DebugExceptions
use ActionDispatch::ActionableExceptions
use ActionDispatch::Reloader
use ActionDispatch::Callbacks
use ActiveRecord::Migration::CheckPending
use ActionDispatch::Cookies
use ActionDispatch::Session::CacheStore
use ActionDispatch::Flash
use ActionDispatch::ContentSecurityPolicy::Middleware
use ActionDispatch::PermissionsPolicy::Middleware
use Rack::Head
use Rack::ConditionalGet
use Rack::ETag
use Rack::TempfileReaper
use Warden::Manager
run Quxx::Application.routes

[wlipa]

I pushed a branch skip-resolve-warning-for-public-files - can you test with that and see if that gets rid of the warning?

Yes, it works!

[wlipa]

The convention would be to put fonts under app/assets/fonts/, which should solve the problem - are there any reasons for not doing that in your case?

I like to put externally maintained assets like fonts and js packages that come with a version number already and which I don't want the asset pipeline to modify in the public directory. Just seems simpler to avoid the asset pipeline entirely when it's not needed.

[theodorton]

Can you give us the result of bin/rails middleware? I think I put the Propashaft middleware before the static middleware by mistake

I had the same thought, but my understanding is that the assets are served correctly, just not resolved from the url processing of CSS files. It’s unrelated to the middleware changes.