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

standardmark

v0.1.0

Published

Markdown Style Guide, Linter & Formatter to produce clean and standardised documents.

Downloads

11

Readme

standardmark

Markdown Style Guide, Linter and Formatter inspired by the strict ruleset of
JavaScript Standard Style and expanding on the GitHub Markdown Styleguide
following the GitHub Flavoured Markdown spec. It core is a modified version of
markdownlint. To see an example of the standardmark target-spec,
you can have a look at [this README in plain-text].
NOTE: the standardmark-spec is still a work in progress and subject to change.

Table of Content

Goals

  • It should be able to use autoformatting to help the Author to style-rules that
    are less practicle to write.

  • It should be easy to integrate it into a workflow. eg.

    • linting and formatting program documentation prepublish.
    • help in creating templates for issues or PRs and the like.
    • providing easy to read text to show on a terminal without the help of
      additional tools like coloring. eg. Abouts, credits or loginmessages.
  • It should help in creating an ordered document by:

    • creating a Table of Content
    • create reference links from inline links and move them to a more appropriate
      position for plain text reading. eg. move them before the next header.
    • help in indenting and formatting tables.
  • it should try to guarantee that documents are usefull to accessability tools.

  • it should be able to use formatting option specified in a config file and
    inside the document (using config comments and/or a frontmatter) to make it as
    easy as possible to configure linting and formatting for different cases. eg:

    • disable requireing a title for posts that have a seperate tilte field
    • to disable/configure the creation of a ToC.
  • it should be smart enough guess basic purpous of a document and automatically
    adjust some of the formatting. eg.

    • only creating a ToC if the file has exeeded a certain length.
    • adjusting allowed line length when it is sensible.
  • it should not only point out issues but also provide rationale.

  • it should assist by suggesting ways to improve a document. eg.

    • by pointing out overly long paragraphs that could be split.
    • by interpreting keywords in context and provide feedback based on it. eg.
      registering a reference like "see the link" or "discribed below" and ask
      for a reference link to be added.

need input

some rules