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

freshdoc

v0.1.0

Published

``` javascript @freshdoc ./main.mjs:5-5 //main.mjs:5-5 program.name("freshDocs") ```

Downloads

3

Readme

//main.mjs:5-5
program.name("freshDocs")

The Way That It Works

FreshDoc works by parsing your markdown files and finding all of the code blocks that have a freshDoc reference. We then allow you to keep these in sync using the sync command.

If your files get out of sync and you need to review them first. For example, if you have moved a code block, you can use the changes command to see what has changed.

Example FreshDoc reference

``` javascript @freshdoc ./Readme.md:11-11
//Readme.md:11-11
Example FreshDoc reference
```

A reference is composed of the following:

  • The language of the code block. Only javascript is currently supported.
  • the annotation @freshdoc so our engine can find the code block.
  • The file that the code block is in.
  • The line number of the code block always specified as n-m. You can show one line of code using n-n as in the example.

Commands

Changes

//main.mjs:14-19
program
  .command('changes')
  .description('Get all changes')
  .action(() => {
    getAllChanges()
  })

More details on the 'changes' command can be found here

Sync

Syncing changes to blocks

//main.mjs:7-12
program
  .command('sync' )
  .description('Sync all blocks')
  .action(() => {
    syncAllBlocks()
  })

More details on the 'sync' command can be found here