Grunt, Gulp, Webpack, Other? #15
Replies: 5 comments 6 replies
-
Really depends on what you're building. Grunt and Gulp will work fine, but are a bit dated and may start to see issues with support for plugins. Webpack can be a crazy complicated beast, with a stack more features than probably needed for a 'normal' website. My last build I used Parcel.js. Virtually no config, just stays out of the way and does what it needs to do. Would recommend. |
Beta Was this translation helpful? Give feedback.
-
Why not plain Npm scripts and a couple of packages for what you need? Unless you have more complicated tasks than minifying, bundling and copying tasks, I believe it's the better (simpler) option. |
Beta Was this translation helpful? Give feedback.
-
Webpack can also be “no config”. So if it comes down to Webpack or Parcel I’d recommend building it in a way that either works. I’d love to help your team explore that as an option. It’s 5am so I might be dreaming :) Another thought to consider is who this is made for and will be using it. If you want high adoption you may not want to force anyone into this at all. And with the inevitable release of Bootstrap 5 it might be good to consider it as your FED framework; which you could mimic whatever their build process is so you’re not adding anything unique to this project that doesn’t come from bootstrap 5. |
Beta Was this translation helpful? Give feedback.
-
I think something that could easily be swapped in / out, maybe parcel and webpack? |
Beta Was this translation helpful? Give feedback.
-
A good place to learn more and compare the tools, is this project https://tooling.report by some of the chrome people... |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Frontend q, which is the go to option these days?
Beta Was this translation helpful? Give feedback.
All reactions