Usually, in a project there are node scripts throught package.json. It's common to have a project to propose a pipe such as:
npm run check && npm run dev
Such as in AstroJS projects.
This is fine, but manual invocation of commands does lead to sloppy development. And not a good experience, too.
There are two task runners for suited for this repo:
make part of the POSIX standart. It's usually implement throught gnumake for almost every Linux distro. We can assure the existance of make using Docker / Podman or Nix, even.
Then there's just, that's a new contender in the task running scene. It has good features, such as automatic --help for reading task targets, and aims to "deal with make's idiocyncracies"
Sure, there's pure shell scripts, and node scripts, too, but manual handling of targets dependencies is no bueno. I would recommend it.
I would prefer make, for this project is not that complex, and we would not declare another dependency, for make is part of almost every UNIX/Linux box, whether or not you use it.
Usually, in a project there are node scripts throught
package.json. It's common to have a project to propose a pipe such as:npm run check && npm run devSuch as in AstroJS projects.
This is fine, but manual invocation of commands does lead to sloppy development. And not a good experience, too.
There are two task runners for suited for this repo:
makepart of thePOSIXstandart. It's usually implement throughtgnumakefor almost every Linux distro. We can assure the existance ofmakeusing Docker / Podman or Nix, even.Then there's
just, that's a new contender in the task running scene. It has good features, such as automatic--helpfor reading task targets, and aims to "deal withmake's idiocyncracies"Sure, there's pure shell scripts, and node scripts, too, but manual handling of targets dependencies is no bueno. I would recommend it.
I would prefer
make, for this project is not that complex, and we would not declare another dependency, formakeis part of almost every UNIX/Linux box, whether or not you use it.