I think this space would be easier if I was using React, since there tons of tooling available for it. However, I use Elm and have no plans to switch. Thanks for the link to Parcel. I found an Elm plugin for it, so I'll investigate that further.
And remember, nobody force you to use moderns frontend frameworks to build an app, you can continue to use .NET, Django, Rails, etc. and make a webapp mostly server side with a sprinkles of JS code for interactivity.
I want to use modern browser-based front ends. (Especially in the .NET space, I have a bitter taste in my mouth from the server-side UI techs.) Having to tinker with the build process has just been the cost of doing business so far. Because this area of dev is so young, mature tooling did not have time to be created yet. But I figured we might have reached the point now where some standardized build processes have been identified and more automated tooling has begun to spring up. So I asked. :)
Yeah, the community is starting to create more and more tools for non-config builds more based on a convention over configuration philosophy but with the possibility to config a lot if you want, which is awesome if you know what you're doing and want to.
If you're doing many projects (I think that because of your post) using these tools and avoiding config is the best in my opinion, just let you limit by the tool and try to avoid special requirements (if you don't need to of course), because the great about this super configurable tools like Webpack is that in a big long term project you only need to configure it one time, but for a freelance dev or agency where develop many projects is just a waste of time, there is where tools like Parcel or the many frameworks CLIs shine.
I think this space would be easier if I was using React, since there tons of tooling available for it. However, I use Elm and have no plans to switch. Thanks for the link to Parcel. I found an Elm plugin for it, so I'll investigate that further.
I want to use modern browser-based front ends. (Especially in the .NET space, I have a bitter taste in my mouth from the server-side UI techs.) Having to tinker with the build process has just been the cost of doing business so far. Because this area of dev is so young, mature tooling did not have time to be created yet. But I figured we might have reached the point now where some standardized build processes have been identified and more automated tooling has begun to spring up. So I asked. :)
Thanks again.
Yeah, the community is starting to create more and more tools for non-config builds more based on a convention over configuration philosophy but with the possibility to config a lot if you want, which is awesome if you know what you're doing and want to.
If you're doing many projects (I think that because of your post) using these tools and avoiding config is the best in my opinion, just let you limit by the tool and try to avoid special requirements (if you don't need to of course), because the great about this super configurable tools like Webpack is that in a big long term project you only need to configure it one time, but for a freelance dev or agency where develop many projects is just a waste of time, there is where tools like Parcel or the many frameworks CLIs shine.
BTW, I'm sure Elm has a CLI to avoid any config 🤔
Elm has command line tools to build/debug/install-packages, but it does not handle bundling or minifying assets.
P.S. Based on your Create React App recommendation, I googled and found Create Elm App. I will have to give that a try too. :-)
Create Elm App is awesome. Worked really well for me.
I think Jest and Create React App really raised the bar on tooling and no config.