process-warning
npmv5.1.0TypeScriptA small utility for creating warnings and emitting them.
Safe to adopt
Yes — process-warning scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 41 days ago. 3 releases in the last 2 years.
- ?Adoption: grade ?, Not reported by this registry.
No download data reported for this package yet.
- AMaintenance: grade A, Excellent.
Last published 41 days ago. 3 releases in the last 2 years.
- AWeight: grade A, Excellent.
Zero runtime dependencies, about 35 KB installed.
- ASupply chain: grade A, Excellent.
No install scripts, 10 maintainers, and a contained dependency surface.
- 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 process-warning to a project.
Runtime packages this one declares itself.
Distinct packages in the full runtime tree, deduplicated the way a package manager would.
Unpacked size of this package plus its entire runtime tree.
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 process-warning README.
const {
createWarning,
createDeprecation
} = require('process-warning')
const warning = createWarning({
name: 'ExampleWarning',
code: 'EXP_WRN_001',
message: 'Hello %s',
unlimited: true
})
const emitted = warning('world')process-warning vs the alternatives
Packages solving a similar problem in the npm ecosystem, compared on the signals that drive an adoption decision.
| Package | Weekly downloads | Dependents | License | Last release |
|---|---|---|---|---|
| process-warningthis page | 0 | 2 | MIT | 1 month ago |
| @fastify/error | 0 | 2 | MIT | 1 day ago |
| type-fest | 337.8M | 6 | (MIT OR CC0-1.0) | 1 day ago |
| http-errors | 149.4M | 7 | MIT | 1 day ago |
| @rolldown/pluginutils | 132.4M | 1 | MIT | 1 day ago |
| once | 109.6M | 1 | ISC | 1 day ago |
Dependencies
Declared by process-warning v5.1.0. Runtime dependencies are installed with the package; dev dependencies are not.
Dev (6)
Used by
Popular packages that depend on process-warning.
Relationship graph
Dependencies (left) and dependents (right) of process-warning.
Frequently installed together
An HTTP/1.1 client, written from scratch for Node.js
An AST-based pattern checker for JavaScript.
Build and manage the AJV instances for the fastify framework
TypeScript definitions for node
Create HTTP error objects
Manipulate the HTTP Vary header
Really Fast Deep Clone
Fake HTTP injection library
Stringify your JSON at max speed
Build and manage the fast-json-stringify instances for the fastify framework
Crazy fast http radix based router
Asynchronous bootstrapping of Node applications
Release history
3 releases in the last two years, typically about 142 days apart.
| Version | Published | Size | License |
|---|---|---|---|
| 5.1.0latest | 1 month ago | 35 KB | MIT |
| 5.0.0 | 1 year ago | 24 KB | MIT |
| 4.0.1 | 1 year ago | 22 KB | MIT |
| 4.0.0 | 2 years ago | 22 KB | MIT |
| 3.0.0 | 2 years ago | 21 KB | MIT |
| 2.3.2 | 2 years ago | 20 KB | MIT |
| 2.3.1 | 2 years ago | 22 KB | MIT |
| 2.3.0 | 2 years ago | 20 KB | MIT |
| 2.2.0 | 3 years ago | 14 KB | MIT |
| 2.1.0 | 3 years ago | 12 KB | MIT |
| 2.0.0 | 4 years ago | 11 KB | MIT |
| 1.0.0 | 4 years ago | 12 KB | MIT |
Overview
process-warning is an npm package that a small utility for creating warnings and emitting them. It has 2 known dependents in the graph. The latest version is 5.1.0, released under the MIT license.
Who should use it
Teams working in the npm ecosystem who need a small utility for creating warnings and emitting them 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).
Cons
- No significant drawbacks detected from available metadata.
Auto-generated from collected registry metadata. No external claims are inferred.
Maintainers
Funding
Frequently asked questions
Should I use process-warning?
Yes — process-warning scores well across adoption, maintenance, weight, supply chain, and licensing. No download data reported for this package yet. Last published 41 days ago. 3 releases in the last 2 years.
How do I install process-warning?
Run `npm install process-warning` to add process-warning to your npm project.
What license is process-warning released under?
process-warning is distributed under the MIT license.
How popular is process-warning?
npm does not publish download counts. Within PackageGraph's crawl, 2 known packages depend on process-warning.
Is process-warning still maintained?
The most recent release of process-warning (v5.1.0) was published 1 month ago.
Does process-warning run install scripts?
No. process-warning does not define preinstall, install, or postinstall scripts, so installing it does not execute publisher-supplied code.