devnacho
Adding processed styles from stylesheet to HTML template
Hi there! ![]()
For SEO purposes, I’m trying to improve loading performance by not having render blocking stylesheets and loading critical styles inside <style> tags directly in the HTML.
Does anybody have any idea or recommendation on how to put my webpack-processed stylesheet inside <style> tags in the HTML layout.
Any help would be really appreciated!
Most Liked
hubertlepicki
You can read and output compiled app.css file (or other target if you have one). This should work in development and in prod, also with Erlang releases. In your layout or template do:
<style type="text/css">
<%= {:safe, File.read!(Path.join(:code.priv_dir(:ui), "static/css/app.css"))} %>
</style>
And it will output the compiled CSS in place, provided your compiled file ends up in priv/css/app.css and that your application name is :ui. Replace these with your own if needed ![]()
idi527
idi527
If you load the contents into a module attribute, it’s read from the filesystem only once during the compilation.
Oh, I misunderstood you. Ignore me.
I’d put it in a function instead of a module attribute though. This way you would be able to invoke it from other modules as well, not just within the module where you defined the module attribute.
defmodule Web.CSSView do
app_css = File.read!(Path.join(:code.priv_dir(:your_app_name), "static/css/app.css"))
def inline_css(:app) do
{:safe, unquote(app_css)}
end
end
and then in any template
<style type="text/css"><%= Web.CSSView.inline_css(:app) %></style>
Last Post!
devnacho
Thanks for the replies.
I ended up getting the file from priv/static and I used GitHub - melpon/memoize: A method caching macro for elixir using CAS on ETS. · GitHub to memoize the contents of the file and avoid opening the file with each rendering of the template.
Popular in Questions
Other popular topics
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #channels
- #elixirconf
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #phoenix_html
- #iex
- #blog-post
- #graphql
- #genstage
- #ai
- #websockets
- #supervisor
- #elixirconf-us
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #metaprogramming
- #security
- #hex









