Tuesday 6 June 2017

Having private node modules without a registry

I'm working on a project where some of my react components could be used in further projects of mine. I don't necessarily want them to make public, but that is fine. All I need to do is specifying it as dependency in my package.json.

But to be honest, I am lazy and don't want to set the whole URL of my repository for each module I create. So I was wondering if there is a tool that could help me out, managing my private repositories, without the necessity to manage my own module registry. And also that helps, keeping my install/add/remove commands short

I did research, but only found things about keeping require/import paths short.

I thought of creating my own npm/Yarn/pnpm wrapper that helps organizing things, but was wondering if there is already something out there.



via lumio

No comments:

Post a Comment