gilest
Hi all
Relatively new to Elixir, but was curious to see how Phoenix might run with a basic importmap configuration.
Introducing, phoenix_importmap.
Benefits:
In dev - minimal file-based tooling, removal of esbuild transpilation step, parity with prod
In prod - more granular caching of js files since they are many rather than a few bundles
Curious to know if folks are interested in this approach, anyway.
Usual disclaimer - this is an early stage library. I’ve not yet used it in prod ![]()
Trending in RFCs
There was some time when I started thinking about giving a boost to Lambdapad, the initiative from @garretsmith in Erlang that I loved wa...
New
Hey everyone — I’m putting together a practical, code-first book on building production-ready business applications with Phoenix LiveView...
New
You set up environments, each with its own tools, its own data and its own limits, and programs get evaluated in them. The same program r...
New
Other Trending Topics
Hey, I’m Jesse and I’m the main contributor behind Dexter, a full-featured, lightning-fast Elixir LSP optimized for large codebases. It s...
New
I am happy to introduce the very α version of the new programming language compiled to BEAM.
Welcome Cure.
It has literally three kille...
New
Hi there! We created Gust: A task orchestrator inspired by Airflow.
For those who have never heard about Aiflow, it’s a Python-based wor...
New
Hi everyone!
The first release candidate for the Expert language server project is now available!
We’ve published a press release detai...
New
Beam Bots (or just BB for short) is a framework for building fault-tolerant robotics applications in Elixir using familiar OTP patterns. ...
New
Xamal is a deployment tool for Elixir apps that deploys native releases to bare metal servers over SSH. It’s a port of GitHub - basecamp/...
New
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixirconf-us
- #ai
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #elixirconf-eu
- #metaprogramming
- #hex










Showing Posts 1 to 4- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
jakeprem
This is really interesting thanks for making it!
I’ll have to take a closer look next time I venture outside the LiveView bubble.
derek-zhou
Neat. I am using a more bare bone nobuild setup. I made sym links of phoenix js into my static dir:
Then I directly import those phoenix js in my app.js:
If I need to use more than a couple of npm modules, I will consider using the importmap package.
jakeprem
Do these get copied correctly when you build releases too?
derek-zhou
I don’t copy assets from
assets/topriv/any more. My original js and css lives directly underpriv/static/and the phoenix js are symlink’ed topriv/static/js/and remain that way in the release. The symlinks are flatten in deploy.