I have to templates for creating my new projects:
- coworkflow https://github.com/mvc-works/coworkflow
- cumulo-workflow https://github.com/Cumulo/cumulo-workflow
For coworkflow, I have about 10+ repositories based on it, in old of newer versions, which contains:
shadow-cljs.ednfor ClojureScript compiler
package.jsonfor npm scripts, which handles assets building
main.cljsfor initializations of Respo and DOM
- business code
So every time there’s updates in a configure file, I have 10+ projects to update. As time past, it becomes really tedious and time-costing work to maintain them all. For each project:
=>> git log --oneline | grep up 37b5859 upgrade sepal and recollect; release 0.3.3 on npm 4ccdcbf update workflow; upgrade respo; fix :package ; release 0.3.1 on npm 3e5cda5 upgrade sepal; release 0.3.0 db30f1e update shortcut link; add Consolas in leaf; upgrade npm deps; release 0.2.19 on npm 3d90607 update icon; release 0.2.15 on npm 6842d74 update guide texts; release 0.2.14 on npm dfc6fae update README like stack-editor 12c2d3b upgrade shadow-cljs 2.0.3 to fix nodejs hmr 8e8bdd5 support editing expr in draft box e299661 upgrade deps ac31fee update respo; add comp-rename 0c74d8d upgrade respo 0.6.0-rc6 a6c0ee5 upgrade deps 673a512 upgrade deps 92a14c0 update push stack algorithm
Even through each project is a very simple page, updating the template is tedious.
For cumulo-workflow, contains more like
main.cljs with a
server.cljs, which means more code. I’m thinking about turning the code into side-effect functions, however it does no help to the build scripts…
What do you think can save us from such tedious works?