npmpackage.info

Gathering detailed insights and metrics for @ljharb/through

Other packages similar to @ljharb/through

@ljharb/resumer

0.1.3

a through stream that starts paused and resumes on the next tick

Gathering detailed insights and metrics for @ljharb/through

@ljharb/through - 2.3.14 | npmpackage.info

@ljharb/through

simple way to create a ReadableWritable stream that works

2.3.14

MIT

JavaScript

31.97 kB

4.1

Installations

npm install @ljharb/through

Developer Guide

BETA

Typescript

Yes

Module System

CommonJS

Min. Node Version

>= 0.4

Node Version

23.7.0

NPM Version

10.9.2 Pull Requests

Open

0

Total

1

Closed

0

Merged

1

Issues

Open

0

Total

1

Closed

1

Releases

Unable to fetch releases

Languages

JavaScript

JavaScript (100%)

Developer

ljharb

Download Statistics

Total Downloads

Last Day

Last Week

Last Month

Last Year

GitHub Statistics

MIT License

3 Stars

129 Commits

3 Watchers

1 Branches

1 Contributors

Updated on Feb 08, 2025

Maintainers

View All 1 Contributors

Package Meta Information

Latest Version

2.3.14

Package Id

@ljharb/through@2.3.14

Unpacked Size

31.97 kB

Size

10.61 kB

File Count

NPM Version

10.9.2

Node Version

23.7.0

Published on

Feb 08, 2025

Total Downloads

Cumulative downloads

Total Downloads

NaN

Last Day

NaN

Compared to previous day

Last Week

NaN

Compared to previous week

Last Month

NaN

Compared to previous month

Last Year

NaN

Compared to previous year

Weekly Downloads

Monthly Downloads

Yearly Downloads

Dependencies

call-bind

Dev Dependencies

@arethetypeswrong/cli @ljharb/eslint-config @ljharb/tsconfig @types/call-bind @types/node @types/tape auto-changelog encoding eslint from in-publish npmignore nyc safe-publish-latest stream-spec tape typescript

@ljharb/through

Note: This package is a fork of https://npmjs.com/through, and builds off of it.

Easy way to create a Stream that is both readable and writable.

Pass in optional write and end methods.
through takes care of pause/resume logic if you use this.queue(data) instead of this.emit('data', data).
Use this.pause() and this.resume() to manage flow.
Check this.paused to see current flow state. (write always returns !this.paused).

This function is the basis for most of the synchronous streams in event-stream.

1var through = require('@ljharb/through')
2
3through(function write(data) {
4    this.queue(data) //data *must* not be null
5  },
6  function end () { //optional
7    this.queue(null)
8  })

Or, can also be used without buffering on pause, use this.emit('data', data), and this.emit('end')

1var through = require('@ljharb/through')
2
3through(function write(data) {
4    this.emit('data', data)
5    //this.pause()
6  },
7  function end () { //optional
8    this.emit('end')
9  })

Extended Options

You will probably not need these 99% of the time.

autoDestroy=false

By default, through emits close when the writable and readable side of the stream has ended. If that is not desired, set autoDestroy=false.

1var through = require('@ljharb/through')
2
3//like this
4var ts = through(write, end, {autoDestroy: false})
5//or like this
6var ts = through(write, end)
7ts.autoDestroy = false

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

4.1

/10

Last Scanned on 2025-07-07

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