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

roggy

v0.1.3

Published

Fetch any markdown documentation as raw markdown strings

Downloads

5

Readme

roggy

Install

yarn add roggy
# or
npm install roggy

Programmatic Usage

Require the function call it with any of the following:

  • A remote branch name like master
  • A version number, like 3.0.0
  • A version number that starts with a v, like v1.0.0
  • A commit SHA, like 74603dec82800abe2f313d8edace189836d93432
  • A local directory, like ~/my/path/to/something-great

Also you need provide owner and repository. Example:

import { roggy } from 'roggy'

const docs = await roggy('master', {
  owner: 'electron',
  repository: 'electron',
})
docs.forEach((doc) => {
  // docs is an array of objects, one for each markdwon file in /docs
})

Each object in the array looks like this:

{
  slug: 'chromium-rce-vulnerability',
  filename: 'chromium-rce-vulnerability.md',
  markdown_content: '---\ntitle: Chromium RCE Vulnerability Fix\nauthor: zeke\ndate: ' +
}

When fetchhing docs from a local directory, be sure to use a full path:

import * as path from 'path'
const docsPath = path.join(__dirname, 'docs')

roggy(docsPath, { owner: '', repository: '' }).then((docs) => {
  // ...
})

License

MIT