Re: [elm-discuss] Re: using a compile-to-js workflow with elm-webpack-starter

2016-11-11 Thread Martin DeMello
Thanks, that helped me get everything working! I think this would be useful to add to the docs somewhere (either in elm-webpack-starter or in the elm tutorial itself, since it does mention webpack elsewhere). martin On Tue, Nov 8, 2016 at 3:54 AM, Wouter In t Velt wrote: > I use elm-webpack-sta

Re: [elm-discuss] Re: using a compile-to-js workflow with elm-webpack-starter

2016-11-08 Thread Wouter In t Velt
I use elm-webpack-starter too, with ports. In webpack, the watcher automatically rebuilds whenever you change a file. Not only one of the elm files, but also when you change index.js or index.html. You can change your index.js, or create a new *.js file which you require into index.js, or add a

Re: [elm-discuss] Re: using a compile-to-js workflow with elm-webpack-starter

2016-11-07 Thread Peter Damoc
Using elm-webpack-starter means that the process is slightly different from the guide. In the guide, you build elm.js and edit some index.html which has a script tag where you start the Elm app add work with the ports. Using the elm-webpack-starter you have the src/static/index.js where the Elm ap

[elm-discuss] Re: using a compile-to-js workflow with elm-webpack-starter

2016-11-07 Thread Martin DeMello
No one? If the recommended solution is to move off webpack (plus pointers to a replacement) that's fine too; I would just like to get my dev environment set up once and for all and then go back to writing elm code. martin On Sat, Nov 5, 2016 at 5:31 PM, Martin DeMello wrote: > I have my project