ronanyeah / elm-phoenix-example

minimum elm + phoenix setup, with webpack

💻 ronanmccabe.app

elm-phoenix-example's Issues

Test

Webpack may be overkill.

https://maximilianhoffmann.com/posts/how-to-compile-elm-files-on-save

Hot reloading

Please note that this is absolutely not an issue, more an enhancement request, so feel free to close it.

I'm completely new to Elm and I have tried to understand how to have hot module reloading as an addition of this repository.

BTW this repo was by far the best for me to understand how all the bits and pieces go together, so thanks for that 👍. I've spent some time adapting this to a Phoenix 1.3 project and it worked like a charm.

I think it would be nice to add a hot reload option and explain the commit that adds it, as there are so many contradictory sources around that it's a nightmare (on Elm street) to pick what's good, so having this here would be really great.

I tried with webpack-combine-loaders by having a elm-hot loader and elm-webpack loader combined, but I ended up having my full page reloaded anyway.

Elm tests: where do they go with this setup?

A good addition to this boilerplate would be a very basic MainTest.elm file to test whatever is being achieved in Main.elm, but also very much acting as a guideline on how to get things going regarding testing.

README out of date

Looks like the README has not been updated for the Phoenix 1.3 update

Ctrl+C on the mix task leaves the process running

Before running mix npm watch:

ps aux | grep webpack
(Nothing).

After running mix npm watch 3 times and Ctrl+C:

ps aux | grep webpack
doodloo    411  0.0  0.0   4612   756 ?        S    15:21   0:00 /bin/sh -c webpack --watch
doodloo    412 29.4  0.8 1272796 142768 ?      Sl   15:21   0:07 node webpack --watch
doodloo    543  0.0  0.0   4612   860 ?        S    15:22   0:00 /bin/sh -c webpack --watch
doodloo    544 33.9  0.8 1271180 141352 ?      Sl   15:22   0:06 node webpack --watch
doodloo    859  0.0  0.0   4612   760 ?        S    15:22   0:00 /bin/sh -c webpack --watch
doodloo    860 41.7  0.8 1273840 142612 ?      Rl   15:22   0:05 node webpack --watch

I noticed this, because each process compilation triggers all the others. Needless to say, my 6 CPUs are completely busy as this efficiently creates an infinite loop.