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

remark-preset-lint-node

v5.0.2

Published

remark preset to configure remark-lint with settings for nodejs/node

Downloads

17,191

Readme

remark-preset-lint-node

Build Status

remark preset to configure remark-lint with settings for nodejs/node

Install

npm install remark-preset-lint-node

Test

npm test

Add new language or grammar

Adding the language to the documentation style guide

  1. PR the nodejs/node repo adding the language/grammar to the documentation style guide.

Adding the language to the linter

  1. PR this repo adding the language/grammar.
  2. Bump this package version, publish it.
  3. In node-lint-md-cli-rollup, bump the remark-preset-lint-node dependency.
  4. In the nodejs/node repo, rebuild the Markdown linter (make lint-md-rollup).
  5. PR the nodejs/node repo with the updated linter.

Environment variables

NODE_RELEASED_VERSIONS

On runtime, the linter will check the environment if the NODE_RELEASED_VERSIONS variable is defined; if it's there, it will use the content of the variable as a comma-separated list of allowed version numbers. This list is supposed to be built from the changelog(s), and validates the version numbers for the nodejs-yaml-comments rule.

For better compatibility with the nodejs/node changelogs, there are a few exceptions:

  • Version numbers ^0.0.0 || ^0.1.0 are not validated using the provided list. They are validated using the vx.x.x pattern.
  • REPLACEME placeholder is always valid, regardless if it's in the list or not.