I want to use modern browser-based front ends. and make a webapp mostly server side with a sprinkles of JS code for interactivity. I found an Elm plugin for it, so I'll investigate that further.Īnd remember, nobody force you to use moderns frontend frameworks to build an app, you can continue to use. However, I use Elm and have no plans to switch. I think this space would be easier if I was using React, since there tons of tooling available for it. Also Parcel is an alternative to WebPack with zero configuration.Ī lot of tools and frameworks are starting to do this so you don't need to configure anything, except if you want to, but if you're used to let the IDE handle the build for you then you can let a CLI do it as well and avoid configs.Īnd remember, nobody force you to use moderns frontend frameworks to build an app, you can continue to use. There're always ways to avoid that, Angular CLI AFAIK is similar to this idea of not requiring to configure anything, Vue CLI and Nuxt.js (a clon of Next.js for Vue projects) has the same. I used to think that setup a Webpack config for React project was terrible but I use Next.js or Create React App (without eject to avoid config), for the second you can even use CodeSandbox which is an online editor for CRA, Vue.js, Svelte and Preact and you don't need to configure anything, you create a project and start coding, it will the build for you and you can connect it to GitHub. Does anyone else have awareness or even care that front-end builds are a pain compared to what else is out there? So what am I missing? Is there a tool I can use to make build setups easier? It could be a VS Code extension or different build program (i.e. And I still haven't figured out some things related to building multiple (Elm) apps which share common code. Yet I have to deal with the intricacies of webpack and a handful of loaders and plugins to accomplish this. Especially because my needs are simple: compile to js / css, bundle and minify, link in an index page. It still feels like a waste of time and brain cells to futz with. either because I learn new things or webpack version upgrades or template stops being maintained. I've had to do this for most new projects. I find a starter project that is close to what I want, then spend some time tweaking it to suit my needs. I have created a bunch of front-end apps using webpack to build. For a while, I got by on VS plugins which would minify or bundle automatically on save.įast forward to today. I got it to work, but I was incredulous that it was worth the effort and abandoned it. I went from builds not even being a thought in my head to having to code the entire build process myself. The first "modern" front-end project I did, I setup a build script with gulp to bundle and minify JS/CSS. (CI tools also used the project files to build and run tests.) Edit: removed extraneous details. When I was a junior dev I was not even aware of the build configuration/processes, because it just worked so I didn't have to know. This has negatives, but generally works well. It was setup and maintained mostly automatically for you under the covers through the GUI solution explorer, which doubled as a file manager. When doing server-side web apps with Visual Studio (WebForms, MVC), I never had to setup any build process. NET in particular), the build process was not a thing I had to worry about. You see, with managed languages on the server (and. However, one thing irritates me about them: the build process. Instead web apps were entirely server rendered, maybe with some JS sprinkles for mouse-overs (before CSS :hover existed) and other minor effects.Īs the balance has shifted toward browser-based front-ends, I have transitioned too and been happy for it. Back when I started, Javascript was too limited to build a full app. I've been developing web apps for many years.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |