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

grunt-mdspell

v0.4.0

Published

A grunt task for mdspell - spell check your markdown files as part of your build

Downloads

4

Readme

grunt-mdspell

build status

Spell check your markdown files

This plugin runs a spell-checker against the markdown files within your project, reporting any errors that it finds. It's a useful addition to any project that has a lot of documentation, or markdown-based blogs. Here's an example of the output:

Running "mdspell:main" (mdspell) task
    overview.md
        7 | to enforce your team’s coding convntions. It is
    foo/bar.md
        3 | Monkey-patch (hook) functins for debugging and stuff.
        7 | This code should wrk just fine:
>> 3 spelling errors found in 2 files
Warning: Task "mdspell:main" failed. Use --force to continue.

Aborted due to warnings.

You can provide a .spelling file that contains global or file-specific words that should be ignored. Probably the easiest way to create this file is via the interactive mdspell tool which this grunt task is built on.

Getting Started

This plugin requires Grunt ~0.4.5

If you haven't used Grunt before, be sure to check out the Getting Started guide, as it explains how to create a Gruntfile as well as install and use Grunt plugins. Once you're familiar with that process, you may install this plugin with this command:

npm install grunt-mdspell --save-dev

Once the plugin has been installed, it may be enabled inside your Gruntfile with this line of JavaScript:

grunt.loadNpmTasks('grunt-mdspell');

The "mdspell" task

Overview

In your project's Gruntfile, add a section named mdspell to the data object passed into grunt.initConfig().

grunt.initConfig({
  mdspell: {
    options: {
      // Task-specific options go here.
    },
    your_target: {
      // Target-specific file lists and/or options go here.
    },
  },
});

Options

options.ignoreAcronyms

Type: Boolean Default value: false

Ignores acronyms when spell checking.

options.ignoreNumbers

Type: Boolean Default value: false

Ignores numbers such as 22nd, 31st - numbers without suffix, e.g. 345, are always ignored.

Usage Example

In this example, a number of markdown files are spell checked with both acronyms and numbers ignored.

grunt.initConfig({
  mdspell: {
    options: {
      ignoreAcronyms: true,
      ignoreNumbers: true
    },
    files: {
      src: ['**/*.md']
    },
  },
});

When spelling errors are found, they are reported as follows:

Running "mdspell:main" (mdspell) task
    test/fixtures/foo.md
        7 | to enforce your team’s coding convntions. It is
    test/fixtures/sub-folder/bar.md
        3 | Monkey-patch (hook) functins for debugging and stuff.
        7 | This code should wrk just fine:
>> 3 spelling errors found in 2 files
Warning: Task "mdspell:main" failed. Use --force to continue.

Aborted due to warnings.