I've been using "vanilla" Elm (with elm-ui) for the last 12 months without any external build tools - mainly because I'm not really a web dev and don't know much about these, or indeed much about html, css, js etc. I've found the standard elm-watch tool does a fantastic job of hot reloading, so wondering why not just stick with this. I guess Vite brings extra things to the table which I'll see in future episodes...
If you don’t have any need to work with existing NPM packages or other build steps like TailwindCSS, there’s no need to upgrade! I originally made this Vite plugin for use with Elm Land, where folks had more varied and advanced needs. If you’re already using elm-watch, I’d stick with that!
do I have to config something to open VSC from the browser, when there is an error message? ... (some minutes later) VSC was not in path. Works great 👍
I've been using "vanilla" Elm (with elm-ui) for the last 12 months without any external build tools - mainly because I'm not really a web dev and don't know much about these, or indeed much about html, css, js etc. I've found the standard elm-watch tool does a fantastic job of hot reloading, so wondering why not just stick with this. I guess Vite brings extra things to the table which I'll see in future episodes...
If you don’t have any need to work with existing NPM packages or other build steps like TailwindCSS, there’s no need to upgrade!
I originally made this Vite plugin for use with Elm Land, where folks had more varied and advanced needs. If you’re already using elm-watch, I’d stick with that!
you would love to have all your ports in typescript so even the outside world is typesafe
do I have to config something to open VSC from the browser, when there is an error message?
... (some minutes later)
VSC was not in path. Works great 👍