Replace webpack with modd (2nd try) - #58
Conversation
Webpack is currently only used for automatically compiling the elm sources and reloading in the browser. The tools modd/devd do the same with much less boilerplate. No need to have the npm machinery. https://github.com/cortesi/modd https://github.com/cortesi/devd Current version v0.6 of devd doesn't support serving SPAs with non-hash-routes. See this related issue: cortesi/devd#38 Since we don't want to use hash-routes, we will not use this modd/devd setup as long as devd doesn't support them.
oliverbarnes
left a comment
oliverbarnes
left a comment
There was a problem hiding this comment.
Thomas, can you point to some reference where the community shows adoption of modd and devd? I couldn't find much just by googling. I worry new developers to the project will be used to webpack or another lib, and be turned off tooling that's not what most elm devs use. We have to weigh personal ease of use with general community adoption
|
You are right, the webpack configuration works right now and may be easier to kick off because most frontend devs will have installed node and npm anyway. So, let's postpone the question of the best build system to a later time. As a workaround for the poor formatting of compiler messages there is already a supplemental For future reference let me sketch my reflections on that topic so far: What I don't like about webpack is...
On the contrary, a production build process may profit from webpack's abilities. Alternatives (for development builds):
|
2 participants
Continuing from #33
Reopening this PR, as devd version 0.7 now supports SPA routes.
This way we can cut the whole bloated Node.js/npm machinery.