Best way to add package in the cache only(not in npm)

[LucsT]

Hello, me again.

In a future use, I would see a feature like:

Adding a package trough my cache and only on mine, not in npm open database.

ie a kind of private npm registry.

Probably can contribute to the feature, depending on my time, amount of work and Jdpaton wish for this software.
I'm not really an old JS dev, but i have very useful advice around me.

Jdpaton and all others, if you have opinions or advices, please share it.

Lucas

[jdpaton]

There could be a custom endpoint like /private/ behind HTTP basic auth that allows the upload of a custom .tgz created by the uploader using npm pack.

An issue is validating that it doesn't conflict with an existing package in the open database. Private packages could use a custom data directory instead and the server can have an option like --allow_private_package_overrride to allow them to served first instead of the public NPM package.

[LucsT]

For now the 'uploading' didn't matter for me. I have a full access and the host is dedicated to npm-lazy-mirror.

We (me and a friend) start a proof of concet

We avoiding the conflict risk you talk about, by select our package name with a particular string.
We avoid cache expiring to that kind of package. (see this PR :https://github.com/LucsT/npm-lazy-mirror/pull/1)

Now, need to dev a packaging tool for preparing Json, and tarball from a git or a directory.

It's more a hack than a feature for now. But need it soon and working.
Try to push a more constructive thing later.