Skip to content

Sample setups for build tools

Notifications You must be signed in to change notification settings

GrimLink/build-tools

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

11 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Dev Build tools

This repo contains sample setups for each Task runner en Bundlers.

While the setup focuses an generic setup. It does have some opinionated things I feel are the best way to go.

So if you have something that is wrong or could have been done better. Don't hesitate to shoot an PR/Issue with why and how.

Table of Contents

Whats in the 📦

Grunt setup with Webpack for JS bundeling.

I personlay moved to Gulp and/or Webpack. So I am not using Grunt that much any more.

Still this setup rocks! Since it builds the CSS just the way I want it. And JS via the power of webpack.

I was planing to also add an Uglify option so you don't need the Webpack. But I am not going to add this anymore.

Pretty much an port of Grunt but with more flexibility.

I kept the tasks clean and simple. Compared to many Gulp configs I have seen. That just lost logic 😨

I my current preferred build tool.

Just as Grunt it uses the power of Webpack for the JS. But I am planning to add an uglify option. Just because I want to see that option work as well.

Sample setup using parcel.

Usefull for quick setups. Since it is zero config.

Funny enough this not completely true. There are many config for other packages found in a parcel project. E.g. postcss.config.js, .babelrc and .sassrc.

But if you keep things simple you probably don't need this.

I personally do need these configs for my build tools. So parcel is not my choice when to pick a build tool.

Sample not made yet

Like parcel webpack can also run without any config.

But I am planing to add an config example here.

For now you can check the version in the Gulp sample.