Gzemnid
Gzemnid copied to clipboard
nodejs
An npm beholder that deceives you
When invoked with no args, gzemnid will now print a usage message.
Some status updates: 1) The latest dataset is uploaded to https://gzemnid.nodejs.org/datasets/out.2019-06-04/ 2) npm, Inc removed both `byField` view from the replicate host and shut down skimdb host completely, so `gzemnid...
That would allow to switch back to `replicate.npmjs.com`, which should include scoped packages. Also that would allow to build real-time updates without re-downloading the whole dataset. See https://github.com/npm/registry-follower-tutorial
depsdb is consuming 2 GiB uncompressed and 350 MiB compressed. It should be compressed automatically, like `slim.code.*`
Currently, the [server stub](https://github.com/nodejs/Gzemnid/blob/master/src/commands/server.js) does not support oAuth. Once a proper server would be set up, oAuth support would be a must-have to expose this as an API / web...
`extract` should be split into small files, alowing to introduce various extraction mechanisms without touching any of the existing source files (except the config).
There should be an option to store _just_ partials and to fetch new packages on the fly. That would make full rebuilds problematic, but would significantly reduce the required storage...
This is a proposal, not a bug report. As such it's a bit unfocused, mostly brainstorming. - Filter the `package.json`s from `meta/` - Filter the `.tgz`s from `current/`, optionally based...
Two ways: 1. Huge package.json file for everything, indexed on the package id, 2. Search-ready lz4 file, like `slim.code.*` files.
This needs to work with a separate npm mirroring tool, which just downloads the packages. That means that it should check the packages in the local mirror, and use those...