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

@g2i/local

v2.1.3

Published

This project provides a local, offline-first development environment for the G2i platform.

Downloads

9

Readme

g2i-local

This project provides a local, offline-first development environment for the G2i platform.

Prerequisites

You need to be authenticated with our organization on GitHub Package Registry. Here's a guide from @DevanB on how to do that.

CLI

Usage: g2i-local [options] [command]

Options:
  -h, --help       display help for command

Commands:
  start [options]  Start a local G2i environment. This will pull down the latest staging database if you don't already have a clone.
                   If you'd like to start one anew, use the --wipe flag.
  stop             Stop your local G2i environment.
  destroy          Delete your local G2i environment.
  help [command]   display help for command

Getting Started

To get started with zero setup, run npx -p @g2i/local g2i-local start.

:warning: On the first run, this project imports our staging database which can take a really long time. It only does this on the first run, or whenever you decide to recreate your clone.

Recreating your clone

Use the g2i-local destroy command to delete your local clone, and run g2i-local start again to bring it up from scratch.

Contributing

To setup a local development environment against which you can test changes to the... local development environment, follow these steps.

  1. Clone this repo. (git clone)
  2. Navigate into its folder. (cd local)
  3. Update the code.