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

fetchq-documentation

v0.0.2

Published

Fetchq Gitbook Documentation Project

Downloads

3

Readme

Fetchq Gitbook Documentation Project

This documentation project uses Gitbook Toolchain, please have a read before you start contributing so you get a hang of it.

There are 2 basic twists from a normal Gitbook project:

  • src is used as the contents source folder
  • docs is used as the build folder

We achieve that by customizing the gitbook serve/build command in the package.json. Basically you need to use yarn/npm start and yarn/npm build to run the gitbook properly.

Start the book locally

yarn install
yarn start

the project will resolve dependencies and boot on port 4000.

http://localhost:4000 »

Build the book for publication

yarn build

How to contribute

  1. fork
  2. make a nice change / fix / contribution
  3. commit and open a PR

We appreciate your help!