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

@double-great/double-check

v0.5.1

Published

Double check your writing uses inclusive language and correct spelling.

Downloads

500

Readme

@double-great/double-check

Double check your writing uses inclusive language and correct spelling.

[!Note]
A fork of https://github.com/get-alex/alex

Install

npm install @double-great/double-check -g

Use it

You can run double-check from your terminal and point it at a folder of markdown files or a specific set of markdown files (using glob pattern):

double-check pages/

If your markdown files use liquid, add the --liquid flag.

To check HTML files, use the --html flag.

double-check pages/ --html

If you have a mix of files, you must run separate commands to parse them properly:

double-check **/*.md && double-check **/*.html --html

The command will return errors for any rules your writing may have encountered. The rule might make sense or be totally wrong for your context. You can decide to:

  • Fix the error.
  • If a rule doesn't make sense for your writing, disable it.
  • For files you don't want to double check, ignore them.

If you'd like to warnings instead of error, use the --warn flag.

Configuration

You can configure double check by committing .doublecheckrc file to your repository. This file can take many formats, such as .doublecheckrc.json, .doublecheckrc.js, or .doublecheckrc.yml.

retext-simplify:
  ignore:
    - function
    - parameters
retext-spell:
  ignore:
    - double-check
    - CLI
# This plugin is now turned off
retext-passive: false
# This plug is now turned on
retext-quotes: true

Plugins

Default plugins

The following plugins are enabled by default, if the plugin as options that you'd like to change, you can add them to your configuration file:

Example of adding options for a specific plugin:

retext-sentence-spacing:
  preferred: double-space

Opt-in plugins

To enable the following plugins, update your configuration file to define the plugin's options or set the plugin to true. These plugins are opt-in because they are often more opinionated and need configuration:

Example of opt-in:

retext-quotes: true

Disable rules

You can disable a rule either for a single page or an entire repository.

For a single page

You can ignore a rule inline with an HTML comment:

<!--double-check ignore just-->
Just double check it.

You can disable a single rule for full blocks of text:

<!--double-check disable just-->
Just double check it.
<!--double-check enable just-->

A message for just this sentence will appear.

To ignore many rules for a page:

<!--double-check ignore however clear indicate-->
However, it was clear that you did not indicate you wanted the last donut.

For an entire repository

In .doublecheckrc, you can specify a list of rules to disable if you have no better alternative.

retext-simplify:
  ignore:
    - info
    - appropriate

Ignore specific files

If the are files that you do not want to double check, create a .doublecheckignore file in your repository's root that defines these file paths (kind of like .gitignore).