Agree 100% - I have nearly 100 such projects collected through the years.
Notice in this screenshot:
1 - page count is 5 (20 on a page X 5 pages = between 80 and 100)
2 - They are sorted by latest update, the first 20 are all updated within the last 2 mo, so active.
3 - This doesn't count my company's repo group, which is another 25.
My top used pattern:
DNB / docker-npm-builder: all my apps, packages, etc, are all configured, built, and deployed by a single package - one improvement or feature added to DNB means 100 projects are immediately improved.
It configures 13 utilities across every project, using tools like jsdoc, Dockerfile, ncu, esbuild, tsconfig, npm, eslint, gitlab pipeline, etc
Imagine having 100 projects, and no matter which one you go to, they are all outfitted with exactly the same tools, same configurations, and they all are built exactly the same way, independent of the dev's local OS and config.
Other "lessor" patterns are like my file-util package. Every single file operation all working exactly the same way.
Ever used import fs... and then had to remember which function group is different from the other function group?
Callback vs promise, sync vs async, error handling, etc - all of mine are async, promises, and use throw.
I don't spend any time having to look them up, remind myself which one is it that does async/promise, etc.
I make them all the same, then I build utilities on top, like a JsonFile class that you access like an object read() and save(); finding all files in a directory, including sub-directories; recursively deleting; copying; and seeing if two files are really the same file (hardlink) on disk.
Obviously many more projects than those.
My first page on
@gitlab (with some redaction):