<commit_before>static npm registry
-------------------

This module follows the `skimdb` from npm and creates a flat file copy of the
registry on your local machine. This can then be served up behind `nginx` to
give you a local, read-only copy of the npm registry.


usage
-----

    registry-static -d my.registry.com -o /var/www/registry

This is the most common use, this will start following the registry
and make copies of the modules and their tarballs into `/var/www/registry`.
When it does, it will replace the `tarball` key in the `package.json`
with the url provided with `-d` (so the downloads resolve locally).

This module also uses the sequence file, so you can kill it and it should
restart from where it left off.

_WARNING: This may take quite a while to complete and a large amount of disk space (more than 117GB at last check)_

directory structure
-------------------

When it pulls the `package.json` for a module, it will create a directory structure similar to this:

    ./davargs
    ├── -
    │   ├── davargs-0.0.1.tgz
    │   └── davargs-0.0.2.tgz
    ├── 0.0.1
    │   └── index.json
    ├── 0.0.2<commit_msg>readme: more updates<commit_after>static npm registry mirror
--------------------------

This module follows the `skimdb` from npm and creates a flat file copy of the
registry on your local machine. This can then be served up behind `nginx` to
give you a local, read-only mirror of the npm registry. It's not a private registry
nor does it attempt to be one. It's designed to allow you to use the registry
in-network to speed up your local development.

usage
-----

    registry-static -d my.registry.com -o /var/www/registry

This is the most common use, this will start following the registry
and make copies of the modules and their tarballs into `/var/www/registry`.
When it does, it will replace the `tarball` key in the `package.json`
with the url provided with `-d` (so the downloads resolve locally).

This module also uses the sequence file, so you can kill it and it should
restart from where it left off.

_WARNING: This may take quite a while to complete and a large amount of disk space (more than 117GB at last check)_

directory structure
-------------------

When it pulls the `package.json` for a module, it will create a directory structure similar to this:

    ./davargs
    ├── -
    │   ├── davargs-0.0.1.tgz
    │   └── davargs-0.0.2.tgz
    ├── 0.0.1
    │   └── index.json
    ├── 0.0.2
{'fraction_non_alphanumeric': 0.10984075132707227, 'fraction_numerical': 0.012249897917517355, 'mean_word_length': 2.8102643856920686, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 4, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '693753', 'n_tokens_mistral': 731, 'n_tokens_neox': 703, 'n_words': 372}