</>PackageGraphPackageGraph

warn-once

npmv0.1.1TypeScript

Show a warning once

Not recommended for new projects

No — warn-once should not be adopted for new projects. Last published 1495 days ago.

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

    No download data reported for this package yet.

  • FMaintenance: grade F, Failing.

    Last published 1495 days ago.

  • AWeight: grade A, Excellent.

    Zero runtime dependencies, about 2.4 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 warn-once 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.

2.4 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
No constraint declared
Module format
CommonJS only
TypeScript
Types included
Install scripts
None

Quick start

A usage example from the warn-once README.

const warnOnce = require('warn-once');

// ...

warnOnce(someCondition, 'This is a warning message');

Used by

Popular packages that depend on warn-once.

Relationship graph

Dependencies (left) and dependents (right) of warn-once.

react-native-scre…warn-once
warn-once dependencies dependents

Frequently installed together

Release history

No releases in the last two years, typically about 454 days apart.

Recent versions of warn-once
VersionPublishedSizeLicense
0.1.1latest4 years ago2.4 KBMIT
0.1.05 years ago1.3 KBMIT
0.0.15 years ago652 BMIT

Overview

warn-once is an npm package that show a warning once. It has 1 known dependents in the graph. The latest version is 0.1.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need show a warning once 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).
  • Zero runtime dependencies — minimal footprint.

Cons

  • No significant drawbacks detected from available metadata.

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

Maintainers

Frequently asked questions

Should I use warn-once?

No — warn-once should not be adopted for new projects. Last published 1495 days ago.

How do I install warn-once?

Run `npm install warn-once` to add warn-once to your npm project.

What license is warn-once released under?

warn-once is distributed under the MIT license.

How popular is warn-once?

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

Is warn-once still maintained?

The most recent release of warn-once (v0.1.1) was published 4 years ago.

Does warn-once run install scripts?

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