4 ms·
There isn’t even a need for a shell script. The author is already invoking three separate tools, each of which has a mechanism for invoking custom commands.
by thom 2y ago
There isn’t even a need for a shell script. The author is already invoking three separate tools, each of which has a mechanism for invoking custom commands.
- oblio 2y agoWhat if he wants to have a uniform environment across projects and some aren't JavaScript?
- scrame 2y agoDear God! There is something that isn't javascript? Do you know you can it use on the server and the browser!??!
- thom 2y agoThen he could just use Gulp, but I have no skin in this absurd game.
- oblio 2y agoGulp? That JS tool that was last cool in 2018? After it which it was replaced with Grunt, which stopped being cool in 2020? And that was replaced with Webpack, ESBuild, Rome, Bun... Why would anyone voluntarily subject themselves to that kind of insanity? :-)) Better to just use the hacksaw that is Make than all these Rube Goldberg contraptions :-)
- thom 2y agoI don’t personally care about the JS ecosystem. But OP is already using Gulp. He’s then calling Gulp from npm run. He’s then calling npm run from make. Adding make into the mix is solving nothing here. If you’re saying he should use make properly I agree!