Wait so how’s this better than node modules in a private registry plus a bot that keeps the modules updated if tests pass? I can see this breaking code very fast and I don’t think the headache is worth it just to avoid the publishing / upgrading step. You can automate all of it and if you need to develop your module to work with a microservice you can just add the module from your local copy of the repo and switch to the registry version when done. If you really have a problem with the tiny little extra steps this involves, you can always automate this as well by watching any changes in the module repo (locally) and executing the update everytime there’s a change. If you’re worried about the money you can always use your own registry proxy like verdaccio.
Just my two cents, but I don’t see the point of this. It seems like a fancy, non-standard, non-versioned, version-control-cluttering way of reinventing the wheel.
I might be missing the point. Please don’t take it personally, I’m only talking devops.