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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@everymundo/em-registry-cli

v0.15.2

Published

CLI for the EM Registry

Downloads

42

Readme

NPM version

registry

CLI for the EM Registry

Instalation

npm i -g @everymundo/em-registry-cli

Credentials

Just like the awscli you can have different profiles/accounts in your $HOME/.everymundo/registry.json file

Configure the default account

registry configure

? What's the accountId [] ABCD
? What's the userId  [] user1
? What's the userApiKey [...] [hidden]

This will create a file like this $HOME/.everymundo/registry.json

{
    "accounts": {
        "default": {
            "accountId": "ABCD",
            "userId": "user1",
            "userApiKey": "ejgfj9svjirshut894u40ounw4onug395p4uu4om9v"
        }
    }
}

Configure another account

registry configure -a test
# or
registry configure --account test

? What's the accountId [] abc
? What's the userId  [] u100
? What's the userApiKey [...] [hidden]

Modules

Initialize an existing module

In the case of having an existing project without an em-module.json file in the project your see the following message when running the registry

registry init

? What's the moduleId (m100)

{
  "moduleId": "m200"
}

Publish a module

At the moment we are only publishing a zipfile with the content of your transpile (preferred) module with the registry

An temporary requirement is an index.html file that loads your module. This requirement will be removed soon and we'll generate such file.

The flow could be something like this:

npm run build

cd dist # or cd build, or whatever is the output of your build

zip -r ../build.zip *

registry publish ./build.zip

The output of the publish command, when successfull, should be a preview URL of the module. Something like this:

Preview URL: https://em-registry-uploads--849481900493--us-east-1.s3.amazonaws.com/prod/ANDREZ/m201/000000340618804092/index.html

Commands

| Commands | Description | | --------------------------- | ---------------------------------------------------------- | | push <zipfile> | Pushes your Everymundo Module | | init | Initializes a module with its id | | configure | Configures credentials | | create | Creates a module on our servers | | list-modules [options] | List available modules for you | | package [options] | Creates a package file using the pre-defined command | | promote [options] | Puts a specific deployment in a queue for QA to promote it | | whoami | Prints the current Partner and userId | | help [command] | Display help for command |