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

@ahl389/markdoctor

v2.0.4

Published

A markdown parser and converter that will turn markdown files into properly formatted Google Docs files and upload them to your Google Drive.

Downloads

51

Readme

Markdoctor

A markdown parser and converter that will turn markdown files into properly formatted Google Docs files and upload them to your Google Drive.

Usage

INSTALLATION
$ npm install -g @ahl389/markdoctor

VERSION CHECKING
$ markdoctor (-v|--version|version)
@ahl389/markdoctor/0.0.1 darwin-x64 node-v14.17.2

USAGE
$ markdoctor run path/to/file.md
$ markdoctor login

Format

When writing your article for use with markdoctor, you can generally write markdown exactly as you're used to. However, because some markdown needs to be preserved in the final Google doc, in order to be imported into Wagtail, you must keep in mind the following two rules:

Inline code

For inline code, in typical markdown or when writing directly in Google docs, you would use a backtick before and after the code, like this:

In the code above, `const var = 1`, is an example of a variable declaration.

For this formatting to be preserved from your markdown file into Google Docs, you must escape your backticks:

In the code above, \`const var = 1\`, is an example of a variable declaration.

Fenced code blocks

In order to preserve your fenced code blocks when your markdown file is converted to Google Docs, be sure to prefix and suffix them with ~~~, as shown below:

~~~ ```javascript hl_lines="1" const myvar = 1; ``` ~~~

Links

oclif Version Downloads/week License