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

@gravityci/cli

v0.0.4

Published

> Run Gravity for a given set `filePath` patterns

Downloads

1,283

Readme

@gravityci/cli

Run Gravity for a given set filePath patterns

Usage

Minimal usage

gravityci 'dist/**/*'

Multiple paths

gravityci 'dist/**/*' 'dist2/**/*' 'dist3/**/*' ...

Arguments

| argument | type | description | | ------------ | ---------------- | --------------------------------------------------------------------------------------------- | | <patterns> | array of strings | Required. File path patterns of the compiled files the user wants to check its bundlesize |

Running it in your Local Machine

Before running CLI

Before running Gravity's cli in your local machine make sure:

  1. All your dependencies have been installed.
  2. package/cli has been compiled (pnpm run build) if you want to execute production version (pnpm run cli)
  3. All the necessary environment variables have been set in packages/cli/.env file:
    • GRAVITY_TOKEN: This is the token which will grant a user to interact with Gravity Server. If a user does not have a valid Gravity Token, the server won't let the user interact with it (upload a bundle, add a bundle analysis request to the queue, etc.)
    • GRAVITY_HOST: The host where the server is running. In localhost should be http://localhost or the host of the tunnel you could be using (see package/server for more details).
    • GRAVITY_PORT: The port where the server is running. In localhost usually is 3000 but can be any other port free of use you want to run your server locally. Just make sure the value matches the port used by @gravityci/server.
  4. @gravityci/server is running and listening to the $GRAVITY_HOST and $GRAVITY_PORT you set up in step 3.

Troubleshooting

gravity's cli

<patterns> argument is evaluated from process.cwd(), this means, the pattern is applied from the current working directory where the script is executed. The filePath pattern can use ../../ to navigate to parent directories.

Absolute paths are NOT supported for the moment.

Other common issues

For more general issues common across packages, don't forget to visit general Troubleshooting document

Contributing

See README.md#contributing

About Gravity

@gravity Gravity checks file sizes in your Pull Requests.

License

ISC