I was exploring the new esbuild system in Phoenix. The documentation suggests that the two ways to import third-party libraries are by putting them in a vendor folder or by using
npm install. However, the app generated by
phx.new doesn’t appear to do either of those when importing the phoenix & phoenix liveview js. (Although it does use the first method to import the topbar library.)
Based on the output js file, it looks like esbuild is finding the js libraries in the
deps directory, but I haven’t been able to find any config or code telling esbuild to look there.
How does this work?
We also set an environment variable in the esbuild config pointing to Elixir deps folder, and esbuild also looks for files in there. I am on my phone but I can give a full reference tomorrow.
So esbuild treats deps like a node_modules folder, finds the phoenix folder, reads the package.json inside, sees:
And picks one of them?
We have an SPA served from a different port/server, and on ‘start’ the app tries to open a socket on the SPA port. This thread looks like the right place to start to track this down. We have been trying to go back versions to get to a place where this socket behavior does not happen, with no luck. We removed the env: statement in the config.exs and that did not fix the socket connect behavior.
Any suggestions on where to look? I figure We cannot be the only SPA / phoenix API & Dashboard implementation. Do we just go back and never upgrade deps ever? or is this really and esbuild related issue? TIA.