We're currently using Make to orchestrate various tasks. Look at our makefile, I don't think its doing anything particularly complex that, for example, we couldn't do with scripts in package.json. Could we remove Make?
Pros:
Cons:
- Task changing is slightly cleaner in Make compared to
package.json scripts. However, I wonder if removing the chaining makes this more explicit? For example, in CI we perform make riffraff-bundle which implicitly runs webpack and cdk synth. Does performing each task separately reduce complexity?
Alternatively, if we're happy with the DX of using Make, to solve the divergence issue, Make could call package.json scripts. That is, rather than the makefile having a task that runs webpack, could it instead run pnpm run build? And the container file will do the same?
We're currently using Make to orchestrate various tasks. Look at our makefile, I don't think its doing anything particularly complex that, for example, we couldn't do with
scriptsinpackage.json. Could we removeMake?Pros:
Cons:
package.jsonscripts. However, I wonder if removing the chaining makes this more explicit? For example, in CI we performmake riffraff-bundlewhich implicitly runswebpackandcdk synth. Does performing each task separately reduce complexity?Alternatively, if we're happy with the DX of using Make, to solve the divergence issue, Make could call
package.jsonscripts. That is, rather than the makefile having a task that runswebpack, could it instead runpnpm run build? And the container file will do the same?