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

markdown-to-medium

v1.4.4

Published

Publish markdown to medium

Downloads

61

Readme

markdown-to-medium stability

npm version downloads js-standard-style

Publish markdown to Medium. Extracted from @jxnblk's script (thank him if you see him).

markdown to medium example gif

Getting Started

  1. Get a third party integration token on medium
  2. Install markdown-to-medium
  3. Copy the token to the clipboard
  4. Create an article with the token passed through --token
  5. The token is now stored locally for future use, rinse repeat

Usage

Usage: markdown-to-medium <path to markdown>

Options:
  -h, --help        Output usage information
  -v, --version     Output version number
  -t, --token       Pass in the user token, stored after first use
  -i, --id          Pass in the user id
  -u, --canonicalUrl  Add a cross-reference to the original url for post
  -l, --license     Pass in the license
  --title           Pass in the title
  --tags            Pass in tags
  --publication     Publish to a Medium publication

Examples:
  $ markdown-to-medium ./foobar.md
  # Publish markdown to medium

  $ markdown-to-medium ./foobar.md  --tags="tag1,tag2" --title="Hello world"
  # Publish markdown to medium

Docs: https://github.com/yoshuawuyts/markdown-to-medium
Bugs: https://github.com/yoshuawuyts/markdown-to-medium/issues

License

You can specify a license for your draft. It must be one of these options: all-rights-reserved, cc-40-by, cc-40-by-nd, cc-40-by-sa, cc-40-by-nc, cc-40-by-nc-nd, cc-40-by-nc-sa, cc-40-zero, public-domain.

Metadata

To get the correct title and date to show up without using options, you can use YAML frontmatter in your markdown:

---
title: 'How to light a tire fire'
created: '6-20-2016'
publication: 'Intention and Integrity'
canonicalUrl: 'https://example.com/how-to-light-a-tire-fire'
tags: ['fire', 'tires']
license: 'public-domain'
---

Now put some of the best words here.
You can do it, you're witty and smart and charming and

Note that created is not passed through to Medium.

If there is no YAML frontmatter, you can also specify the title using a first level markdown header, such as # Title, on the first line of the file.

Installation

$ npm install --global markdown-to-medium

See Also

License

MIT