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 🙏

© 2025 – Pkg Stats / Ryan Hefner

wikilint

v2.32.0

Published

A Node.js linter for MediaWiki markup

Readme

npm version CodeQL CI Codacy Badge Istanbul coverage

WikiLint

This is a minimal version of WikiParser-Node. The Wikitext LSP and the WikiParser Language Server VS Code extension is written based on this package.

You can also directly lint Wikitext articles in the command line using this package:

npx wikilint --config zhwiki --include --lang zh-hans *.wiki

CLI Options

| Option | Argument | Description | Default | | :----- | :------- | :---------- | :------ | | -c, --config | <path or preset config> | Choose parser's configuration | default | | --cache | | Enable caching | false | | --cache-file | <path> | Specify cache file and enable caching | .wikilintcache | | --ext | <extension> | Specify file extensionCan be used multiple times | all files | | --fix | | Automatically fix problems | false | | -h, --help | | Print available options | | | -i, --include | | Parse for inclusion | false | | --ignore | <pattern> | Ignore files matching the glob patternCan be used multiple times | | | -l, --lang | <path or preset language> | Choose i18n language | English | | --lc, --lint-config | <path> | Specify lint config file | .wikilintrc.json.wikilintrc.js.wikilintrc.cjs.wikilintrc.mjs | | -q, --quiet | | Report errors only | errors and warnings | | -r, --recursive | | Recursively lint files | false | | -s, --strict | | Exit when there is an error or warningOverride -q or --quiet | Exit 1 only where there is an error | | -v, --version | | Print package version | |

Configuration

For MediaWiki sites with the CodeMirror extension installed, such as different language editions of Wikipedia and other Wikimedia Foundation-hosted sites, you can use the following command to obtain the parser configuration:

npx getParserConfig <site> <script path> [user] [force]
# For example:
npx getParserConfig jawiki https://ja.wikipedia.org/w [email protected]

The generated configuration file will be saved in the config directory. You can then use the site name as the --config option.

# For example:
npx wikilint --config jawiki *.wiki