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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@envsa/cspell-config

v9.0.13

Published

CSpell configuration for @envsa/shared-config.

Readme

@envsa/cspell-config

NPM Package @envsa/cspell-config License: MIT

CSpell configuration for @envsa/shared-config.

Overview

It's a shared CSpell config, plus a command-line tool envsa-cspell to perform CSpell-related project initialization and linting. Note that automated fixes are handled via an ESLint integration provided in @envsa/eslint-config.

[!IMPORTANT]

You can use this package on its own, but it's recommended to use @envsa/shared-config instead for a single-dependency and single-package approach to linting and fixing your project.

This package is included as a dependency in @envsa/shared-config, which also automatically invokes the command line functionality in this package via its envsa command

Setup

To use just this CSpell config in isolation:

  1. Install the .npmrc in your project root. This is required for correct PNPM behavior:

    pnpm dlx @envsa/repo-config init
  2. Add the package:

    pnpm add -D @envsa/cspell-config
  3. Add the starter .cspell.json file to your project root, and add any customizations you'd like:

    pnpm exec envsa-cspell init

Usage

The CSpell binary should be picked up automatically by VS Code plugins.

You can call it directly, or use the script bundled with the config.

Integrate with your package.json scripts as you see fit, for example:

{
  "scripts": {
    "spellcheck": "envsa-cspell lint"
  }
}

Configuration

To create a cspell.config.js in your project root:

pnpm exec envsa-cspell init

(Note that this will delete the cspell property in your package.json!)

Or

To create a cspell property in package.json:

pnpm exec envsa-cspell init --location package

(Note that this will delete the cspell.config.js file in your project root!)

Disabling bundled dictionaries

In additional to CSpell's default dictionary configuration, this shared configuration enables a number of dictionaries that ship with CSpell for all file types:

It also includes a number of custom dictionaries distributed with this package, all of which are enabled by default:

  • envsa-acronyms Contains acronyms
  • envsa-files Contains file extensions and types
  • envsa-misc Contains words that are not acronyms or file extensions/types

In your project's root cspell.config.js, you can disable any combination of these dictionaries by adding them to the dictionaries array with a ! prefix.

For example, do disable the envsa-acronyms and envsa-misc dictionaries:

import { cspellConfig } from '@envsa/cspell-config';

export default cspellConfig({
  dictionaries: [
    '!envsa-acronyms',
    '!envsa-misc',
    // ...Additional !-prefixed dicitonary names
  ],
});

Adding project-scoped words

In your project's root cspell.config.js:

import { cspellConfig } from '@envsa/cspell-config';

export default cspellConfig({
  words: [
    'mountweazel',
    'steinlaus',
    'jungftak',
    'esquivalience',
    // ...Additional words
  ],
});

CLI

Command: envsa-cspell

Envsa's CSpell shared configuration tools. (Automated fixes are handled by ESLint.)

This section lists top-level commands for envsa-cspell.

Usage:

envsa-cspell <command>

| Command | Argument | Description | | -------------- | ----------- | ------------------------------------------------------------------------------------------------------------ | | init | | Initialize by copying starter config files to your project root or to your package.json file. | | lint | [files..] | Check for spelling mistakes. Matches files below the current working directory by default. | | print-config | | Print the resolved CSpell configuration. Package-scoped. Searches up to the root of a monorepo if necessary. |

| Option | Description | Type | | ------------------- | ------------------- | --------- | | --help-h | Show help | boolean | | --version-v | Show version number | boolean |

See the sections below for more information on each subcommand.

Subcommand: envsa-cspell init

Initialize by copying starter config files to your project root or to your package.json file.

Usage:

envsa-cspell init

| Option | Description | Type | Default | | ------------------- | ------------------- | -------------------- | -------- | | --location | TK | "file" "package" | "file" | | --help-h | Show help | boolean | | | --version-v | Show version number | boolean | |

Subcommand: envsa-cspell lint

Check for spelling mistakes. Matches files below the current working directory by default.

Usage:

envsa-cspell lint [files..]

| Positional Argument | Description | Type | Default | | ------------------- | ------------------------------ | ------- | -------- | | files | Files or glob pattern to lint. | array | "**/*" |

| Option | Description | Type | | ------------------- | ------------------- | --------- | | --help-h | Show help | boolean | | --version-v | Show version number | boolean |

Subcommand: envsa-cspell print-config

Print the resolved CSpell configuration. Package-scoped. Searches up to the root of a monorepo if necessary.

Usage:

envsa-cspell print-config

| Option | Description | Type | | ------------------- | ------------------- | --------- | | --help-h | Show help | boolean | | --version-v | Show version number | boolean |

Notes

This config includes a bunch of words I've happened to have needed to use. Your preferences will vary.

CSpell is configured to automatically ignore files and paths in .gitignore (via "useGitignore": true), and to ignore words inside of ``` code fences in markdown and mdx files.

As part of the lint command process, @envsa/cspell-config also runs a check to identify any words in your config file's "words" array that do not actually appear anywhere else in your project. This was inspired by Zamiell's cspell-check-unused-words project.

Credits

Eric Mika is the author of the original @kitschpatrol/shared-config project on which this is based.

License

MIT © Liam Rella