Thanks for the solution, @phcurado!
I wanted to add some clarification for anyone who might encounter a similar issue in the future.
You can’t use Phoenix routing-related functionality (like the ~p sigil) in Hologram templates, as Hologram has a separate routing system due to fundamental architectural differences.
Instead of:
<link phx-track-static rel="stylesheet" href={~p"/assets/css/app.css"} />
The recommended approach in Hologram is:
<link rel="stylesheet" href={asset_path("assets/css/app.css")} />
Why asset_path/1? This helper function automatically appends a digest to the asset path for proper asset fingerprinting, which is essential for cache busting in production environments.
While importing verified routes as @phcurado suggested will technically make the compilation error go away, using asset_path/1 is the idiomatic way to handle static assets in Hologram templates.
