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

@clevertech.biz/browse

v0.1.2

Published

Command line utility to open links found in package.json

Downloads

31

Readme

Browse

Command line utility to open links found in package.json

Usage

Put in your package.json file a bunch of links with any tree strcuture you prefer. The leaves must be URLs.

{
  "browse": {
    "website": "https://example.com/",
    "sentry": "https://sentry.example.com/example/project-name/",
    "development": {
      "server": {
        "api": "https://api-dev.example.com/",
        "frontend": "https://dev-dev.example.com/"
      },
      "sumologic": {
        "api": "https://www.sumologic.com/whatever",
        "cms": "https://www.sumologic.com/whatever",
        "frontend": "https://www.sumologic.com/whatever"
      }
    }
  }
}

Now you have a few options:

Using npx

Just run this in the directory where your package.json file is:

npx github:clevertech/browse [path]

Installing locally

Install by using either:

npm install @clevertech.biz/browse -D
yarn install @clevertech.biz/browse -D

Add a local script in your package.json:

{
  "scripts": {
    "browse": "browse"
  }
}

Then run:

npm/yarn run browse [path]

Installing globally

npm/yarn install @clevertech.biz/browse -g

Then just run

browse [path]

Autocomplete

browse works in two different ways. If you don't provide any command line argument it will print all available links and an autocomplete interface.

If you provide the path, it will open the link right away.