Skip to documentation

reference

Migration — @stackline/dev-null

Project migration notes for @stackline/dev-null 1.0.5. Review behavior, requirements and limitations.

Versioned project notes for @stackline/dev-null 1.0.5. Original attribution is retained in the linked repository.

Migration

Direct scoped import

Install the maintained package:

npm install @stackline/dev-null

Then update the package specifier:

const devNull = require('@stackline/dev-null');
import devNull from '@stackline/dev-null';

No source changes

Use an npm alias when application or dependency source must keep the historical package name:

npm install dev-null@npm:@stackline/dev-null

Existing code remains unchanged:

const devNull = require('dev-null');
source.pipe(devNull());

The alias belongs in dependencies or devDependencies, matching the old package's role in the consumer. Commit the resulting lockfile.

Behavioral boundary

No option rename or stream wrapper is required. All options are forwarded to Node's Writable constructor. Code writing objects must continue to request objectMode: true; silently enabling it would change validation and backpressure units.

See COMPATIBILITY_CONTRACT.md for the complete contract.

Package reference