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

@armadacore/eslint-plugin-essentials

v0.1.0

Published

ESLint plugin enforcing @armadacore/essentials patterns: handle Result errors, default optional parameters

Readme

@armadacore/eslint-plugin-essentials

npm version license node

ESLint plugin that enforces patterns from @armadacore/essentials:

  • result-must-handle-errIResult<T> values must have their error path handled.
  • optional-must-have-default — Optional function/method parameters and return types must not leak undefined/null.

Install

npm install -D @armadacore/eslint-plugin-essentials

Peer dependencies: eslint >=9, typescript >=5.

Usage (flat config)

// eslint.config.js
import essentials from '@armadacore/eslint-plugin-essentials';
import tseslint from 'typescript-eslint';

export default [
	...tseslint.configs.recommendedTypeChecked,
	...essentials.configs.recommended,
	{
		languageOptions: {
			parserOptions: {
				project: './tsconfig.json',
			},
		},
	},
];

Both rules require parserServices (i.e. a TypeScript program). Without parserOptions.project, the rules will silently no-op.

Rules

result-must-handle-err

Reports any IResult<T> value whose Err branch is never handled.

Accepted as handling: onErr, match, unwrapOr, unwrapOrElse, err, expectErr, orElse, ignoreErr.

Delegation also counts: return result, passing as argument, assignment to a container.

See docs/rules/result-must-handle-err.md.

optional-must-have-default

Reports function/method signatures that introduce undefined/null into the function body or its return value.

See docs/rules/optional-must-have-default.md.

Example

The example/ directory contains a real workspace using @armadacore/essentials with both valid and invalid code samples. Run:

npm install
npm run build
npm run example:lint

License

MIT