npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ovh-ux/manager-registry

v3.0.0

Published

Provide OVHcloud Manager registry

Readme

Manager Registry

Registry for OVHcloud Manager.

Downloads Dependencies Dev Dependencies

Installation

yarn global add @ovh-ux/manager-registry

or

yarn add @ovh-ux/manager-registry

Usage

CLI

manager-registry --help
Usage: manager-registry [options] [command]

Options:
  -V, --version          output the version number
  -h, --help             output usage information

Commands:
  dev <fragmentsPath>    Dev server for local fragments
  static <registryPath>  Static registry commands
  help [cmd]             display help for [cmd]

Common Options

  • -V, --version: Display version number
  • -h, --help: Display help

Dev

Help to serve a registry from dev fragments environment

manager-registry dev --help
Usage: manager-registry-dev [options] <fragmentsPath>

Options:
  -V, --version                          output the version number
  -p, --port <port>                      server port (default: 8888)
  -e, --regexp <pattern>                 filter fragment pattern (default: [])
  --fallbackRegistry <fallbackRegistry>  Fallback server registry url
  -h, --help                             output usage information

Options

  • -p, --port <port>: Server port (default: 8888)
  • -e, --regexp <pattern>: Allows to filter fragments served (multiple allowed)
  • --fallbackRegistry <fallbackRegistry>: Fallback server registry url

Examples

$ manager-registry dev ./packages/manager/fragments
Serve: ./packages/manager/fragments - localhost:8888

$ manager-registry dev ./packages/manager/fragments -p 1234
Serve: ./packages/manager/fragments - localhost:1234

To serve fragments from dev environmment, and fallback missing fragments to another registry:

$ manager-registry dev ./packages/manager/fragments --fallbackRegistry http://localhost:1234
Serve: ./packages/manager/fragments - localhost:8888
Fallback registry: http://localhost:1234

To serve only the navbar fragment:

$ manager-registry dev ./packages/manager/fragments -e navbar
Serve: ./packages/manager/fragments - localhost:8888

To serve only fragments with name following *bar and !sidebar patterns (e.g. navbar, userbar):

$ manager-registry dev ./packages/manager/fragments -e '*bar' -e '!sidebar'
Serve: ./packages/manager/fragments - localhost:8888

Static

Help to manage a static registry

manager-registry static --help
Usage: manager-registry-static [options] [command]

Options:
  -V, --version                                   output the version number
  -h, --help                                      output usage information

Commands:
  generate-manifests <registryPath>               Generate manifest for static registry
  serve <registryPath>                            Serve a static registry
  add <registryPath> <fragmentPath>               Add a fragment in static registry
  sync <sourceRegistryPath> <targetRegistryPath>  Sync two registry folders
  help [cmd]                                      display help for [cmd]
Generate Manifests

Will generate and write manifest for registry and fragments.

$ manager-registry static generate-manifests --help
Usage: manager-registry-static-generate-manifests [options] <registryPath>

Options:
  -V, --version                          output the version number
  --fallbackRegistry <fallbackRegistry>  Fallback server registry url
  -h, --help                             output usage information

Options

  • --fallbackRegistry <fallbackRegistry>: Fallback server registry url

Examples

$ manager-registry static generate-manifests ./path/to/static/registry
Manifests are generated for static registry in ./path/to/static/registry

To generate manifests with static fragments and fallback registry informations:

$ manager-registry static generate-manifests ./path/to/static/registry --fallbackRegistry http://localhost:1234
Manifests are generated for static registry in ./path/to/static/registry with fallback informations from http://localhost:1234
Serve

Will serve a static registry

$ manager-registry static serve --help
Usage: manager-registry-static-serve [options] <registryPath>

Options:
  -V, --version      output the version number
  -p, --port <port>  server port (default: 8888)
  -h, --help         output usage information

Examples

$ manager-registry static serve ./path/to/static/registry -p 1234
Serve: ./path/to/static/registry - localhost:1234
Add fragment

Add a fragment dist to a static registry

$ manager-registry static add --help
Usage: manager-registry-static-add [options] <registryPath> <fragmentPath>

Options:
  -V, --version  output the version number
  -h, --help     output usage information

Examples

Add a fragment dist (containing a manifest.json) in a static registry:

$ manager-registry static add ./path/to/static/registry ./path/to/fragment/dist
Fragment "[email protected]" added in registry ./path/to/static/registry

Trying to add an existant fragment version in a static registry:

$ manager-registry static add ./path/to/static/registry ./path/to/fragment/dist
Fragment "[email protected]" already exists in ./path/to/static/registry
Sync registry

Sync two registry directories (will add missing fragment from source to target directory)

$ manager-registry static sync --help
Usage: manager-registry-static-sync [options] <sourceRegistryPath> <targetRegistryPath>

Options:
  -V, --version  output the version number
  -h, --help     output usage information

Example

Sync a static registry with an another existing static registry

$ manager-registry static sync ./path/to/static/registry ./path/to/another/static/registry
Fragment "[email protected]" added in registry ./path/to/another/static/registry

Related

Contributing

Always feel free to help out! Whether it's filing bugs and feature requests or working on some of the open issues, our contributing guide will help get you started.

License

BSD-3-Clause © OVH SAS