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

forked

v0.1.4

Published

fork from the command line

Downloads

18

Readme

What?

Saw a tweet:

But why?

If you have ever needed to debug a node module you're using in your project it's a no brainer. If you find a bug in someone's project you might want to fix it and made a fork of it so you can then open a pull request.

Getting Started

First, you need an access token from github so forked can log in. You can find instructions for that here

Make sure to give your token public repo privileges.

Add repo privileges

Then add it to your .bashrc file, or whatever you use to manage your env variables:

export FORKED_TOKEN='PUT_YOUR_ACCESS_TOKEN_HERE'

Then install the module:

$ npm i -g forked

Dive into some random node module:

$ cd node_modules/react

Run the command:

$ fork

If it worked, you should be able to see the fork on GitHub. If you find a bug please document it in the issues :)