re: Build tool maintenance? VIEW POST


I ended up using shell scripts to manage native commands. Like using scss -w for scss and same for typescript, PHPCS checks etc, Instead of using build tools like gulp or webpack or parcel.

But on some simple projects, I just use npm exec to execute scripts.


This works if you are the only one working on the project.
I can image you would need to create a detailed readme explaining every command and which libs to install when you are working in a team.

But of course, one could also say the same about a webpack/npm setup, even if it only has one command.


Not really... These are personal shell scripts which acts as wrapper for tooling. I mainly freelance with PHP or node in backend, and Typescript and Sass for frontend.

So for example new-project.sh will interactively ask my project parameters and then

  1. create a predefined project structure, Also copy my general eslintrc and phpcs
  2. execute composer init and yarn init.
  3. copy a docker-compose file for my runtime stack.

I do have predefined template for webpack, and wordpress, basic slim-starter, express, meteor, vue-laravel, etc.

As for the details of readme, It is just 'npm run build' 'npm run build-prod' 'npm run clean' etc. All commands are listed in npm script block.

Code of Conduct Report abuse