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

renderme

v0.1.0

Published

Render README files from github

Downloads

32

Readme

Renderme

Build Status

Renderme is simple module with one clear goal: Render README files. It tries to render the files locally using the marked module in the same way as Github would have rendered the files. Some details:

  • Sanitizes the outputted HTML using Google's caja parser.
  • Highlights code snippets using pygments
  • Falls back to the Github API for rendering when repository information has been provided and we're unable to detect the content as Markdown.

But there are some small but intentional differences when we are rendering the README files locally. We add line number information to all the code snippets so it's more readable and people can actually jump to snippets which are on the README files. These code snippets are prefixed with a different CSS class then the snippets that Github uses, we use renderme as a prefix for the code so you choose how you want to style them your self.

Installation

This module is released in the npm registry.

npm install --save renderme

Usage

This module exposes a single function as primary interface. So you can simply require the renderme module and that would be all you need.

'use strict';

var renderme = require('renderme');

The renderme variable now contains a function. This function accepts the following arguments.

  • data An object contains:
    • readme: The actual contents of a README file
    • readmeFilename: An optional filename of the README which is used for markdown detection.
  • options An optional object which allows you to configure:
    • github A pre-parsed object which contains a user and repo property with the relevant Github repository information
    • githulk A pre-configured githulk instance which will be used all fallback when the given README file isn't a valid markdown file.
    • trimmed The amount of chars we should assume that the supplied README data is trimmed and we need to fallback to GitHub for rendering instead.
  • fn The completion callback, which follows the error first callback pattern.

As you might have noticed the data structure follows the same internal structure as the packages in The npm Registry. Which makes it really easy to render README files of modules which is also it's primary use case.

Given all this knowledge, rendering a README would be as simple as:

renderme({
  readme: require('fs').readFileSync(__dirname +'/README.md', 'utf-8'),
  readmeFilename: 'README.md'
}, function rendered(err, html) {
  console.log(err, html);
});

Debugging

This module make use of the debug module for logging debug information. To display this information in your terminal you need to set the DEBUG env varible to renderme*:

DEBUG=renderme* node <entryfile.js>

License

MIT