npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@wormss/fixtake

v1.0.1

Published

iterator::take closes the original generator, this removes the ability but adds back a manual way to do it

Readme

@wormss/fixtake

A utility to prevent Iterator.prototype.take() (and other consumers) from automatically closing your generators.

The Problem

In modern JavaScript, using the new Iterator helpers like .take(n) or using a break inside a for...of loop will automatically call .return() on the underlying generator. This makes it impossible to partially consume a generator and then continue using it elsewhere.

function* numbers() {
  yield 1; yield 2; yield 3;
}

const gen = numbers();
const taken = Array.from(gen.take(2)); // [1, 2]
// gen is now CLOSED because .take() called .return()
console.log(gen.next()); // { value: undefined, done: true }

The Solution

fixTake "fixes" the generator by hiding its .return() method from consumers while exposing it as .close() for when you actually want to terminate it manually.

import { fixTake } from '@wormss/fixtake';

function* numbers() {
  yield 1; yield 2; yield 3; yield 4;
}

const gen = fixTake(numbers());

const firstTwo = Array.from(gen.take(2)); // [1, 2]
// gen is STILL OPEN!
console.log(gen.next().value); // 3

const lastOne = Array.from(gen.take(1)); // [4]
// gen is still open (but exhausted)

Installation

npm install @wormss/fixtake

Usage

Basic Example

import { fixTake } from '@wormss/fixtake';

function* source() {
  yield 'a';
  yield 'b';
  yield 'c';
}

const gen = fixTake(source());

// This would normally close 'gen'
for (const item of gen.take(1)) {
  console.log(item); // 'a'
}

// But with fixTake, we can keep going!
console.log(gen.next().value); // 'b'

Manual Closing

If you need to trigger finally blocks or terminate the generator early, use the added .close() method:

const gen = fixTake(someGenerator());
// ... do work ...
gen.close(); // Equivalent to the original .return()

API

fixTake(generator)

  • Arguments: A standard Generator object.
  • Returns: A CloseableGenerator which is the same generator but with .return set to undefined and the original .return moved to .close.

License

ISC