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

@staxomni/markdownlint-config

v0.0.0

Published

A shareable markdownlint configuration for projects.

Downloads

2

Readme

Shareable Markdownlint Config

📄 About

Shareable configuration package for markdownlint — a popular linter for Markdown files.

This package provides a consistent and standardized configuration for Markdown linters across projects. By using this package, you can ensure that your Markdown files adhere to the same set of rules and guidelines, improving their readability and maintainability.

→ Purpose

  • Make it easy for developers to create Markdown files that meet a minimum standard of quality
  • Provide a consistent and standardized configuration for Markdown linters across projects
  • Save time and effort by avoiding the need to manually configure markdownlint for each project
  • Improve the readability and maintainability of Markdown files

💿 Installation

To use this configuration, you'll need to install @staxomni/markdownlint-config as a development dependency in your mono-repository.

# Install as dev-dependency in the root of the mono-repository
$ pnpm add -wD \
 markdownlint \
 markdownlint-cli \
 @staxomni/markdownlint-config

This package should be installed in the root of your mono-repository, where you will create a file .markdownlint.json. Within your monorepo, you should have a structure with directories for your apps and packages, such as:

.
├── .markdownlint.json (root)
├── package.json (root)
├── apps
│   └── my-first-app
│       ├── package.json
│       └── ... (other app files)
└── packages
    └── my-first-package
        ├── package.json
        └── ... (other package files)

→ Configure

  1. Create .markdownlint.json file in root of mono-repository and add lines:

    {
      "extends": "./node_modules/@staxomni/markdownlint-config/base.json"
    }
  2. Add scripts to your package.json:

    pnpm pkg set scripts.lint:md="markdownlint --fix **/*.md --ignore '**/node_modules/**' --ignore '**/CHANGELOG.md'"