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

mdr

v0.2.0

Published

Read markdown files in the terminal in color

Downloads

13

Readme

mdr

NPM version

Markdown reader with color

Requirements

  • Node
  • npm (comes bundled with Node)

Installation

Install the mdr command globally

npm install -g mdr

Usage

mdr [file] [[-g github_repo | -b bitbucket_repo] [-B] | -h | -v] [-i] [-s]

The first parameter should be a file name or url. If not provided, this will default to README.md. github_repo and bitbucket_repo should be in the format user/rpo e.g. mrchimp/mdr.

Here are some things you can do:

mdr                            # Show README.md from current directory
mdr foo.md -i                  # Use dark-on-light style
mdr http://example.com/foo.md  # Show foo.md from a the web
mdr -g mrchimp/mdr             # Show README.md from Github repo
mdr foo.md -b bar/bar          # Show foo.md from Bitbucket repo
mdr -n mdr                     # Show readme from NPM package
mdr -g mrchimp/mdr -B dev      # Show README.md from the dev branch
                                 of a Github repo

mdr -h for more help.

Config

Config files are found and parsed by rc. For example put the following content in $HOME/.mdrrc or $HOME/.mdr/config.

{
    "invert": "true"
}

See rc docs for more in-depth instructions.

Notes

Italic and strikethrough aren't widely supported so I've made them coloured as well. They will show as italic and struck through where possible.

Coverage

✔ = Implemented
✘ = Not implemented

  • ✔ Paragraphs / Line Breaks
  • ✔ Headers
  • ✔ Blockquotes
  • ✔ Unordered Lists
  • ✔ Lists
  • ✔ Code Blocks
  • ✔ Code
  • ✔ Horizontal Rules
  • ✔ Links
  • ✔ Emphasis
  • ✔ Strong
  • ✔ Images (outputs [$ALT_TEXT - $TITLE - $URL])
  • ✘ HTML
  • ✘ Nested Blockquotes
  • ✘ Ordered Lists (can't implement due to limitation in Marked)
  • ✘ Nested Lists

Things I might get around to

  • Improve pad() implementation
  • Syntax highlighting for code blocks
  • Detect italic support?

Screenshot

MDR Screenshot