npmpackage.info

Gathering detailed insights and metrics for destroy

Other packages similar to destroy

@types/destroy

1.0.3

TypeScript definitions for destroy

nocache

4.0.0

Middleware to destroy caching

@types/server-destroy

1.0.4

TypeScript definitions for server-destroy

@tsparticles/updater-destroy

3.7.1

tsParticles particles destroy updater

Gathering detailed insights and metrics for destroy

destroy

destroy a stream if possible

1.2.0

MIT

JavaScript

585.00 B

6,773,822,046 3.4

Installations

npm install destroy

Score

98.9

Supply Chain

86.3

Quality

77.7

Maintenance

100

Vulnerability

100

License

Pull Requests

Open

1

Total

7

Closed

4

Merged

2

Issues

Open

0

Total

3

Closed

3

Releases

Unable to fetch releases

Developer

stream-utils

Developer Guide

BETA

Module System

Unable to determine the module system for this package.

Min. Node Version

>= 0.8

Typescript Support

No

Node Version

16.14.0

NPM Version

8.3.1 Statistics

56 Stars

130 Commits

9 Forks

6 Watching

2 Branches

6 Contributors

Updated on 24 Jul 2024

Bundle Size

1.39 kB

Minified

585.00 B

Minified + Gzipped

Bundlephobia

Languages

JavaScript (100%)

Total Downloads

Cumulative downloads

Total Downloads

6,773,822,046

Last day

-2.7%

6,851,788

Compared to previous day

Last week

3.1%

37,139,858

Compared to previous week

Last month

11.5%

152,397,555

Compared to previous month

Last year

4.8%

1,619,417,619

Compared to previous year

Daily Downloads

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dev Dependencies

eslint eslint-config-standard eslint-plugin-import eslint-plugin-node eslint-plugin-promise eslint-plugin-standard mocha nyc

Versions

destroy

Destroy a stream.

This module is meant to ensure a stream gets destroyed, handling different APIs and Node.js bugs.

API

1var destroy = require('destroy')

destroy(stream [, suppress])

Destroy the given stream, and optionally suppress any future error events.

In most cases, this is identical to a simple stream.destroy() call. The rules are as follows for a given stream:

If the stream is an instance of ReadStream, then call stream.destroy() and add a listener to the open event to call stream.close() if it is fired. This is for a Node.js bug that will leak a file descriptor if .destroy() is called before open.
If the stream is an instance of a zlib stream, then call stream.destroy() and close the underlying zlib handle if open, otherwise call stream.close(). This is for consistency across Node.js versions and a Node.js bug that will leak a native zlib handle.
If the stream is not an instance of Stream, then nothing happens.
If the stream has a .destroy() method, then call it.

The function returns the stream passed in as the argument.

Example

1var destroy = require('destroy')
2
3var fs = require('fs')
4var stream = fs.createReadStream('package.json')
5
6// ... and later
7destroy(stream)

No vulnerabilities found.

10

Binary-Artifacts

Determines if the project has generated executable (binary) artifacts in the source repository.

10

Dangerous-Workflow

Determines if the project's GitHub Action workflows avoid dangerous patterns.

10

Vulnerabilities

Determines if the project has open, known unfixed vulnerabilities.

10

License

Determines if the project has defined a license.

0

Maintained

Determines if the project is "actively maintained".

0

Code-Review

Determines if the project requires human code review before pull requests (aka merge requests) are merged.

0

Token-Permissions

Determines if the project's workflows follow the principle of least privilege.

0

Pinned-Dependencies

Determines if the project has declared and pinned the dependencies of its build process.

0

CII-Best-Practices

Determines if the project has an OpenSSF (formerly CII) Best Practices Badge.

0

Security-Policy

Determines if the project has published a security policy.

0

Fuzzing

Determines if the project uses fuzzing.

0

Branch-Protection

Determines if the default and release branches are protected with GitHub's branch protection settings.

0

SAST

Determines if the project uses static code analysis.

Score

3.4

/10

Last Scanned on 2024-11-18

The Open Source Security Foundation is a cross-industry collaboration to improve the security of open source software (OSS). The Scorecard provides security health metrics for open source projects.

Learn More