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

tinymarkdown

v0.0.1

Published

a minimalistic library for inline markdown: 9 features – 10 lines of code – 0 dependencies

Downloads

3

Readme

TinyMarkdown

a minimalistic library for inline markdown: 9 features – 10 lines of code – 0 dependencies

sometimes you want some strings (like translation strings, user's profile description, etc.) to allow for some basic styling, but without allowing/requiring HTML. this library is a bunch of regexes that help you easily add support for inline markdown features.

usage

const TinyMarkdown = require('tinymarkdown');

const translations = {
    consent: 'i confirm that am **over 18 years old** and have read the [terms of service](/terms).',
}

const html = TinyMarkdown(translations.consent, {links: true});
// 'i confirm that am <strong>over 18 years old</strong> and have read the <a href="/terms">terms of service</a>.'

features

bold/strong

foo **bar** bazfoo <strong>bar</strong> baz

italics/emphasis

foo _bar_ bazfoo <em>bar</em> baz

code/monospace

foo `bar` bazfoo <code>bar</code> baz

strikethrough

foo ~~bar~~ bazfoo <del>bar</del> baz

highlight

foo ==bar== bazfoo <mark>bar</mark> baz

superscript

foo ^bar^ bazfoo <sup>bar</sup> baz

subscript

foo ~bar~ bazfoo <sub>bar</sub> baz

links

⚠️ this feature needs to be explicitly enabled with a {links: true} param

[foo](/bar)<a href="/bar">foo</a>

external links will automatically be set to open in a new tab:

[foo](https://example.com)<a href="https://example.com" target="_blank" rel="noopener">foo</a>

if you want to force that on local links as well, add a ! before the link:

[foo](!/bar)<a href="/bar" target="_blank" rel="noopener">foo</a>

images

⚠️ this feature needs to be explicitly enabled with a {images: true} param

![foo](/bar.svg)<img src="/bar.svg" alt="foo"/>

development

node tests.js     # run tests
node homepage.js  # regenerate homepage from readme

author & links