</>PackageGraphPackageGraph

non-error

npmv0.1.0TypeScript

An error subclass for wrapping non-error values

Safe to adopt

Yes — non-error scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 326 days ago.

  • ?Adoption: grade ?, Not reported by this registry.

    No download data reported for this package yet.

  • BMaintenance: grade B, Good.

    Last published 326 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 14 KB installed.

  • BSupply chain: grade B, Good.

    This package has a single maintainer (bus factor of 1).

  • ALicense: grade A, Excellent.

    MIT — permissive, with no copyleft found in the dependency tree.

Grades are computed deterministically from registry metadata collected by PackageGraph — downloads, dependents, publish dates, the resolved dependency tree, maintainer count, and declared licenses. No third-party scores are used.

Install cost

What you actually take on by adding non-error to a project.

0
Direct dependencies

Runtime packages this one declares itself.

0
Total installed

Distinct packages in the full runtime tree, deduplicated the way a package manager would.

14 KB
Install size

Unpacked size of this package plus its entire runtime tree.

—
Tree depth

Longest resolved dependency chain below this package.

Compatibility

Node.js
node >=20
Module format
ESM only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the non-error README.

jsFull README ↗
import NonError from 'non-error';

const error = new NonError('Something went wrong');

console.log(error.message);
//=> 'Non-error value: Something went wrong'

console.log(error.value);
//=> 'Something went wrong'

console.log(error.isNonError);
//=> true

// Works with any value type
Example truncated — see the full README.

non-error vs the alternatives

Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.

PackageWeekly downloadsDependentsLicenseLast release
non-errorthis page01MIT10 months ago
camelcase95.7M2MIT15 hours ago
decamelize62.6M4MIT15 hours ago
strnum01MIT15 hours ago
serialize-error02MIT14 hours ago
make-error01ISC17 hours ago

Dependencies

Declared by non-error v0.1.0. Runtime dependencies are installed with the package; dev dependencies are not.

Dev (3)

ava ^6.4.1tsd ^0.33.0xo ^1.2.2

Used by

Popular packages that depend on non-error.

serialize-errornpm

Serialize/deserialize an error into a plain object

↓ 0/wk◈ 2 dependents⚖ MITTS

Relationship graph

Dependencies (left) and dependents (right) of non-error.

serialize-errornon-error
non-error dependencies dependents

Frequently installed together

type-festnpm

A collection of essential TypeScript types

↓ 337.8M/wk◈ 6 dependents⚖ (MIT OR CC0-1.0)TS
expect-typenpm

[![CI](https://github.com/mmkal/expect-type/actions/workflows/ci.yml/badge.svg)](https://github.com/mmkal/expect-type/actions/workflows/ci.yml) ![npm](https://img.shields.io/npm/dt/expect-type) [![X Follow](https://img.shields.io/twitter/follow/mmkal)](ht

↓ 78.4M/wk◈ 8 dependents⚖ Apache-2.0TS

Release history

1 release in the last two years.

Recent versions of non-error
VersionPublishedSizeLicense
0.1.0latest10 months ago14 KBMIT

Overview

non-error is an npm package that an error subclass for wrapping non-error values. It has 1 known dependents in the graph. The latest version is 0.1.0, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need an error subclass for wrapping non-error values and value a focused solution.

When not to use it

Consider an alternative if you need to or if a more actively-maintained option better fits your npm stack.

Pros

  • Ships TypeScript type definitions.
  • Clear open-source license (MIT).
  • Lean dependency tree (3 direct dependencies).

Cons

  • No significant drawbacks detected from available metadata.

Auto-generated from collected registry metadata. No external claims are inferred.

Maintainers

sindresorhus

Keywords

converterrormakenon-errornonerrorstringthrowtovaluewrap

Funding

Frequently asked questions

Should I use non-error?

Yes — non-error scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 326 days ago.

How do I install non-error?

Run `npm install non-error` to add non-error to your npm project.

What license is non-error released under?

non-error is distributed under the MIT license.

How popular is non-error?

npm does not publish download counts. Within PackageGraph's crawl, 1 known packages depend on non-error.

Is non-error still maintained?

The most recent release of non-error (v0.1.0) was published 10 months ago.

Does non-error run install scripts?

No. non-error does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.