</>PackageGraphPackageGraph

on-finished

npmv2.4.1

Execute a callback when a request closes, finishes, or errors

Not recommended for new projects

No — on-finished should not be adopted for new projects. Last published 1660 days ago.

  • AAdoption: grade A, Excellent.

    96.7M downloads per week and 5 known dependents.

  • FMaintenance: grade F, Failing.

    Last published 1660 days ago.

  • AWeight: grade A, Excellent.

    Pulls in 1 transitive package, about 13 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 on-finished to a project.

1
Direct dependencies

Runtime packages this one declares itself.

1
Total installed

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

13 KB
Install size

Unpacked size of this package plus its entire runtime tree.

1
Tree depth

Longest resolved dependency chain below this package.

Licenses in the dependency tree

MIT

Every license you inherit by installing on-finished, not just its own. Check this before a legal review, not after.

Compatibility

Node.js
node >= 0.8
Module format
CommonJS only
TypeScript
No bundled types
Install scripts
None

Quick start

A usage example from the on-finished README.

jsFull README ↗
var onFinished = require('on-finished')

Dependencies

Declared by on-finished v2.4.1. Runtime dependencies are installed with the package; dev dependencies are not.

Runtime (1)

ee-first 1.1.1

Dev (9)

eslint 7.32.0eslint-config-standard 14.1.1eslint-plugin-import 2.25.4eslint-plugin-markdown 2.2.1eslint-plugin-node 11.1.0eslint-plugin-promise 5.2.0eslint-plugin-standard 4.1.0mocha 9.2.1nyc 15.1.0

Used by

Popular packages that depend on on-finished.

finalhandlernpm

Node.js final http responder

↓ 132.1M/wk◈ 3 dependents⚖ MIT
sendnpm

Better streaming static file server with Range and conditional-GET support

↓ 127.6M/wk◈ 3 dependents⚖ MIT
body-parsernpm

Node.js body parsing middleware

↓ 97.1M/wk◈ 5 dependents⚖ MIT
expressnpm

Fast, unopinionated, minimalist web framework

↓ 92.8M/wk◈ 17 dependents⚖ MIT
koanpm

Koa web app framework

↓ 6.8M/wk◈ 0 dependents⚖ MIT

Relationship graph

Dependencies (left) and dependents (right) of on-finished.

ee-firstfinalhandlersendbody-parserexpresskoaon-finished
on-finished dependencies dependents

Frequently installed together

http-errorsnpm

Create HTTP error objects

↓ 149.4M/wk◈ 7 dependents⚖ MIT
eslintnpm

An AST-based pattern checker for JavaScript.

↓ 138.4M/wk◈ 279 dependents⚖ MITTS
encodeurlnpm

Encode a URL to a percent-encoded form, excluding already-encoded sequences

↓ 133.6M/wk◈ 5 dependents⚖ MIT
debugnpm

Lightweight debugging utility for Node.js and the browser

↓ 0/wk◈ 46 dependents⚖ MIT
escape-htmlnpm

Escape string for use in HTML

↓ 0/wk◈ 7 dependents⚖ MIT
statusesnpm

HTTP status utility

↓ 0/wk◈ 6 dependents⚖ MIT
content-typenpm

Create and parse HTTP Content-Type header

↓ 191.4M/wk◈ 6 dependents⚖ MITTS
mime-typesnpm

The ultimate javascript content-type utility.

↓ 185.3M/wk◈ 9 dependents⚖ MIT
type-isnpm

Infer the content-type of a request.

↓ 130.9M/wk◈ 3 dependents⚖ MIT
freshnpm

HTTP response freshness testing

↓ 0/wk◈ 3 dependents⚖ MIT
parseurlnpm

parse a url with memoization

↓ 0/wk◈ 6 dependents⚖ MIT
varynpm

Manipulate the HTTP Vary header

↓ 100.2M/wk◈ 4 dependents⚖ MIT

Release history

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

Recent versions of on-finished
VersionPublishedSizeLicense
2.4.1latest4 years ago13 KBMIT
2.4.04 years ago13 KBMIT
2.3.011 years ago—MIT
2.2.111 years ago—MIT
2.2.011 years ago—MIT
2.1.112 years ago—MIT
2.1.012 years ago—MIT
2.0.012 years ago—MIT

Overview

on-finished is an npm package that execute a callback when a request closes, finishes, or errors. It is extremely widely used, with about 96.7M downloads per week and 5 known dependents in the graph. The latest version is 2.4.1, released under the MIT license.

Who should use it

Teams working in the npm ecosystem who need execute a callback when a request closes, finishes, or errors and value a battle-tested, widely-adopted solution.

When not to use it

Consider an alternative if you need to have first-class TypeScript types out of the box, or if a more actively-maintained option better fits your npm stack.

Pros

  • Large, well-established user base (96.7M weekly downloads).
  • Clear open-source license (MIT).

Cons

  • No bundled TypeScript types (may require a separate @types package).

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

Maintainers

dougwilson

Frequently asked questions

Should I use on-finished?

No — on-finished should not be adopted for new projects. Last published 1660 days ago.

How do I install on-finished?

Run `npm install on-finished` to add on-finished to your npm project.

How many dependencies does on-finished have?

on-finished declares 10 direct dependencies and pulls in 1 packages in total once its runtime tree is resolved totalling about 13 KB on disk.

What license is on-finished released under?

on-finished is distributed under the MIT license.

How popular is on-finished?

on-finished has approximately 96,718,568 downloads per week and 5 known dependent packages.

Is on-finished still maintained?

The most recent release of on-finished (v2.4.1) was published 4 years ago.

Does on-finished run install scripts?

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