> > Can you comment on why you did not use the elm-webpack-loader? > I'm trying to understand if we are moving towards a better approach or if > there are other considerations. >
It honestly did not occur to me that I might do that! If I have the choice between using Webpack and not using Webpack, I gravitate towards not using Webpack. It hasn't exactly been the most delightful piece of software I've ever used. ;) The main advantage to using the loader would be to show a way to integrate > Elm with the rest of the web tech especially SCSS and to provide a > development/deployment build environment. I suppose, but that wasn't my goal here. I understand your point, but I'd rather keep it decoupled from JS build tools...everybody's existing setup is going to be a bit different, and I would rather not give people the impression that they need anything special to build this application. :) -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
