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 🙏

© 2026 – Pkg Stats / Ryan Hefner

sfdoc

v1.0.2

Published

Package to generate documentation for Salesforce metadata and UML for Apex classes

Readme

ABOUT

SfDoc was created to simplify process of documentation creation. It is based on NodeJs.

Idea is to: 1. generate .md files for first run 2. generate ./docs directory

.md files should be populated manually after development of specific task is done
.md files guide: https://www.markdownguide.org/basic-syntax/

USAGE

Configuration: docsify cli is required (https://docsify.js.org/#/quickstart)

To initialize .md files:

sfdocs
--init
--sfdir 'C:XXXXXXX\sf_sample\force-app\main\default'

To generate docs:

sfdocs
--sfdir 'C:XXXXXXX\sf_sample\force-app\main\default'

Options:
--help Show help [boolean]
--version Show version number [boolean]
--init Creates initial documentaton files in salesforce project structure. Specify along with sfdir argument [boolean] --sfdir Directory contains sfdx project. Should point to single project [string] [required]
--docsdir Directory containing base docsify files [string] [default: "./docs/"]

To open generated documentation use docsify serve command:

docsify serve docs

CREDIT

Created by Sebastian Gozdur (Salesforce Developer)

Contact via Github or https://www.linkedin.com/in/sebastian-gozdur/