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

@natsuneko-laboratory/lazy

v1.0.4

Published

A tiny lazy initialization utility for TypeScript.

Readme

lazy

A tiny lazy initialization utility for TypeScript.
Values are created only when they are first accessed and are cached afterwards.
Both synchronous and asynchronous lazy values share the same failure semantics:

  • successful initialization is cached
  • failed initialization is not cached
  • accessing the value again after a failure retries initialization

Installation

npm install @natsuneko-laboratory/lazy

Usage

Lazy<T>

import { Lazy } from "@natsuneko-laboratory/lazy";

const value = new Lazy(() => {
  console.log("initialized");
  return expensiveOperation();
});

// The factory has not been called yet.
console.log(value.isValueCreated); // false

const first = value.value;
// "initialized"

console.log(value.isValueCreated); // true

const second = value.value;

// The factory is only called once.
console.log(first === second); // true

AsyncLazy<T>

AsyncLazy<T> provides the same behavior for asynchronous initialization.

import { AsyncLazy } from "@natsuneko-laboratory/lazy";

const value = new AsyncLazy(async () => {
  const response = await fetch("https://example.com/data");
  return response.json();
});

const result = await value.value;

Concurrent accesses share the same initialization promise:

const first = value.value;
const second = value.value;

console.log(first === second); // true

await Promise.all([first, second]);

The factory is still executed only once.

Failure behavior

Initialization failures are not cached.

Synchronous

let attempts = 0;

const value = new Lazy(() => {
  attempts++;

  if (attempts === 1) {
    throw new Error("Failed");
  }

  return "success";
});

try {
  value.value;
} catch {
  // Initialization failed.
}

console.log(value.isValueCreated); // false

console.log(value.value); // "success"
console.log(attempts); // 2

Asynchronous

let attempts = 0;

const value = new AsyncLazy(async () => {
  attempts++;

  if (attempts === 1) {
    throw new Error("Failed");
  }

  return "success";
});

try {
  await value.value;
} catch {
  // Initialization failed.
}

console.log(value.isValueCreated); // false

console.log(await value.value); // "success"
console.log(attempts); // 2

For AsyncLazy, concurrent accesses during initialization share the same promise. If that promise rejects, the cached promise is cleared and the next access starts a new initialization attempt.

API

Lazy<T>

new Lazy<T>(factory: () => T)

Creates a lazily initialized value.

value

get value(): T

Returns the initialized value.

On the first access, factory is called. If initialization succeeds, its result is cached and returned for all subsequent accesses.

If factory throws, the error is propagated and initialization remains incomplete. The next access retries the factory.

isValueCreated

get isValueCreated(): boolean

Returns whether a successfully initialized value is currently cached.


AsyncLazy<T>

new AsyncLazy<T>(factory: () => Promise<T>)

Creates a lazily initialized asynchronous value.

value

get value(): Promise<T>

Returns the initialization promise.

The first access starts initialization. Concurrent accesses return the same promise.

If initialization succeeds, the promise remains cached. If initialization fails, the cached promise is cleared so that the next access retries initialization.

isValueCreated

get isValueCreated(): boolean

Returns whether an initialization is currently cached.

For AsyncLazy, this becomes true as soon as initialization starts. If initialization rejects, it becomes false again.

License

MIT by @6jz.