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

@yukiakai/promise-scope

v1.0.1

Published

A Promise with built-in lifecycle control (timeout, abort, cleanup)

Readme

@yukiakai/promise-scope

A Promise with built-in lifecycle control (timeout, abort, cleanup)

Features

  • Built-in timeout
  • AbortSignal support
  • Automatic cleanup via DisposableStack
  • Scoped lifecycle (no leaks)
  • Promise-compatible (await, .then)
  • Strict mode (no silent failures)
  • Safe async executor handling (no unhandled rejections)

Installation

npm install @yukiakai/promise-scope

Usage

import { ScopedPromise } from "@yukiakai/promise-scope"

await new ScopedPromise((resolve, reject, { signal, stack }) => {
  const timer = setInterval(() => console.log("tick"), 1000)
  stack.defer(() => clearInterval(timer))

  fetch(url, { signal })
    .then(r => r.json())
    .then(resolve, reject)
}, { timeout: 5000 })

Abort Example

const controller = new AbortController()

await new ScopedPromise((resolve, reject, { signal }) => {
  fetch(url, { signal }).then(resolve, reject)
}, { signal: controller.signal })

controller.abort()

Cleanup Example

await new ScopedPromise((resolve, reject, { stack }) => {
  const resource = createResource()

  stack.defer(() => resource.dispose())

  doWork(resource).then(resolve, reject)
})

API

new ScopedPromise(executor, options)

executor

(resolve, reject, ctx) => void | Promise<void>

ctx

  • signal: AbortSignal
  • stack: ScopedStack (DisposableStack without dispose())

options

  • timeout?: number
  • signal?: AbortSignal

Errors

  • AbortedError — when aborted (including timeout)
  • TimeoutError — available as cause of AbortedError
  • AlreadySettledError — thrown if resolve/reject is called more than once

Strict Behavior

ScopedPromise is strict by design:

  • Calling resolve or reject more than once will throw an uncaught AlreadySettledError
  • Calling abort more than once will throw an error
  • Unlike native Promise, repeated calls are not silently ignored

This helps detect logic bugs early instead of hiding them.


Async Executor Behavior

Unlike native Promise, async executors are handled safely:

new ScopedPromise(async () => {
  throw new Error("boom") // handled, no unhandledRejection
})

Errors thrown inside async executors are automatically forwarded to reject.


Notes

  • Uses @yukiakai/disposable-stack for deterministic and strict cleanup semantics
  • Cleanup is always executed after resolve/reject
  • Timeout triggers abort internally
  • External AbortSignal is supported
  • stack.dispose() is intentionally not exposed — lifecycle is managed internally
  • Side effects inside resolve(...) arguments are evaluated before calling resolve (JavaScript behavior)

Requirements

  • Node.js 18+ recommended
  • Modern environments with AbortController support

License

MIT — Yuki Akai