Tour of an open-source 4,000 LoC Elm SPA

[Richard Feldman]

I get asked if there are any sizeable open-source Elm SPA examples out there...so I made one!

Hope it's useful: https://dev.to/rtfeldman/tour-of-an-open-source-elm-spa

[Peter Damoc]

First, thank you so much for taking time from your already busy schedule to solve this for the community! 
I think it is an amazingly useful project as it short-circuits a lot of the potentially time-hungry decisions.  

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.

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.  

 

On Mon, May 8, 2017 at 10:59 AM, Richard Feldman <richard....@gmail.com> wrote:

I get asked if there are any sizeable open-source Elm SPA examples out there...so I made one!

Hope it's useful: https://dev.to/rtfeldman/tour-of-an-open-source-elm-spa

--
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 elm-discuss+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

There is NO FATE, we are the creators.
blog: http://damoc.ro/

[Peter Damoc]

another advantage to a build system (webpack) is that you could create a `docs` folder where to output the current build, mount that folder to be used by the project as its Github Pages root and link it from the README.md. 

[Robin Heggelund Hansen]

This is great Richard! I've already shown it to several people who've asked me how I structure my Elm apps :)

[Richard Feldman]

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. :)

[Erik Lott]

A great many folks are going to be thankful for this SPA example... You are a saint good sir.

[Marek Fajkus]

👏 It's clearly great contribution to educative materials around Elm. I've seen your tweet before and was really pleased you've found time to build it - give it your likes folks.

About web-pack - even though we're using it with elm in company project I never used it for any of my hobby project so far. Simply it makes sense to build from ground up not other way around. Also I think it's reasonable to stay focused so when the goal is to show Elm code then there's no need for unnecessary noise (webpack & env config). That's being said it still might make sense to create demo on "building webpack environment for Elm" which than can use rather simple Elm app and demo just setup of more complex environment (dev/test/prod) with SCSS for instance. That would be great too.

[Richard Feldman]

Agreed! That does sound like a useful (albeit separate) demo project. :D

On Mon, May 8, 2017 at 10:03 AM Marek Fajkus <mare...@gmail.com> wrote:

👏 It's clearly great contribution to educative materials around Elm. I've seen your tweet before and was really pleased you've found time to build it - give it your likes folks.

About web-pack - even though we're using it with elm in company project I never used it for any of my hobby project so far. Simply it makes sense to build from ground up not other way around. Also I think it's reasonable to stay focused so when the goal is to show Elm code then there's no need for unnecessary noise (webpack & env config). That's being said it still might make sense to create demo on "building webpack environment for Elm" which than can use rather simple Elm app and demo just setup of more complex environment (dev/test/prod) with SCSS for instance. That would be great too.

--
You received this message because you are subscribed to a topic in the Google Groups "Elm Discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elm-discuss/hqO3P6uJiew/unsubscribe.
To unsubscribe from this group and all its topics, send an email to elm-discuss...@googlegroups.com.

[Rex van der Spuy]

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. ;)

Ahmen, Bro!