silverdr
Phoenix different handling of some CSS files
Current Phoenix ships with a nicely working assets handling config, employing esbuild and tailwind. This is all extra cool now that we no longer need webpack and whatnot. I can add my custom, modularised CSS/JS into separate files, import them into wherever I need, etc. and things fly out of the box. Super cool. I have a probably slightly less common need though. I want some CSS files to remain unbundled into the main app.css and just automatically copy them over from assets/css/ to priv/static/assets/ on change/build. What would be the Phoenix idiomatic way to do it?
First Post!
LostKobrakai
Phoenix normalized on just having files needing a build system be in assets. Non compiled stuff just lives in priv/static/ directly. But also watchers (in config/dev.exs) as well as the mix assets.* aliases (in mix.exs) can be extended to your likeing if you still wish to plain copy files around.
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
- #advent-of-code
- #elixirconf-us
- #distillery
- #processes
- #forms
- #api
- #metaprogramming
- #security
- #performance









