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

@typedly/data

v6.1.0

Published

A TypeScript type definitions package for @typescript-package/data.

Readme

@typedly/data

npm version GitHub issues GitHub license

GitHub issues GitHub forks GitHub stars GitHub license

GitHub Sponsors Patreon Sponsors

A TypeScript type definitions package for @typescript-package/data.

Features

  • Adapter: Optional data adapter to customize managing underlying data available under the @typedly/adaptable-data.
  • Configurable: Configurable data shape available under the @typedly/configurable-data.
  • Traits: Extended customization via traits, such as Configurable, Adaptable, Serializable, and Transformable under the @typedly/data-traits package.
  • Shape: The default shape for data of any T type with conditional async.

Table of contents

Related packages

Installation

Peer dependencies

npm install @typedly/constructor --save-peer

The package

npm install @typedly/data --save-peer

Api

import {
  // Configuration
  CacheableDataSettings,
  CacheableSettings,
  DataConfig,
  DataSettings,

// Inference.
  InferAsync,
  InferAsyncOf,
  InferValue,

  // Iterable.
  IterValue,
  IterableElement,

  // Data.
  DataConstructor,
  DataShape,

  // Return types
  AsyncReturn,
  // Input types
  DataConstructorInput,
  DataConstructorTuple,

  // Value.
  ValueConstructor,
  ValueShape,
} from '@typedly/data';

Configuration

CacheableDataSettings

The cacheable data settings type combines the data settings with the cacheable settings, allowing for optional or required asynchronous functions for fetching and updating the data value based on the read-only flag.

import { CacheableDataSettings } from '@typedly/data';

Source

CacheableSettings

The cacheable settings interface defines the structure for configuring cacheable data operations, including optional asynchronous functions for clearing, destroying, fetching, and updating the data value.

import { CacheableSettings } from '@typedly/data';

Source

DataConfig

The type for the data configuration, which can be either a full configuration object of C or just an async flag.

import { DataConfig } from '@typedly/data';

Source

DataSettings

The settings for a data type.

import { DataSettings } from '@typedly/data';

Source

Inference

InferAsyncOf

Infers the async flag from a tuple of arguments, returning true if any of the arguments has an async flag set to true.

import { InferAsync } from '@typedly/data';

Source

InferAsync

Infers the async flag from the settings DataSettings or shape DataShape.

import { InferAsync } from '@typedly/data';

Source

InferValue

Infers the value type from a data shape interface.

import { InferAsync } from '@typedly/data';

Source

Iterable

IterElement

The iterate element type.

import { IterElement } from '@typedly/data';

Source

IterValue

The iterated value type.

import { IterValue } from '@typedly/data';

Source

Data

AsyncReturn

The conditional return type for async methods.

import { AsyncReturn } from '@typedly/data';

Source

DataConstructorInput

The input type for data constructors, with arguments support.

import { DataConstructorInput } from '@typedly/data';

Source

DataConstructorTuple

The input type for data constructors, with arguments support.

import { DataConstructorTuple } from '@typedly/data';

Source

DataConstructor

The constructor interface for data types.

import { DataConstructor } from '@typedly/data';

Source

DataShape

The shape of a Data type.

import { DataShape } from '@typedly/data';

Source

Value

ValueConstructor

import { ValueConstructor } from '@typedly/data';

Source

ValueShape

The shape of a Value type.

import { ValueShape } from '@typedly/data';

Source

Contributing

Your contributions are valued! If you'd like to contribute, please feel free to submit a pull request. Help is always appreciated.

Support

If you find this package useful and would like to support its and general development, you can contribute through one of the following payment methods. Your support helps maintain the packages and continue adding new.

Support via:

or via Trust Wallet

Thanks for your support!

Code of Conduct

By participating in this project, you agree to follow Code of Conduct.

GIT

Commit

Versioning

Semantic Versioning 2.0.0

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards-compatible manner, and
  • PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

FAQ How should I deal with revisions in the 0.y.z initial development phase?

The simplest thing to do is start your initial development release at 0.1.0 and then increment the minor version for each subsequent release.

How do I know when to release 1.0.0?

If your software is being used in production, it should probably already be 1.0.0. If you have a stable API on which users have come to depend, you should be 1.0.0. If you’re worrying a lot about backwards compatibility, you should probably already be 1.0.0.

License

MIT © typedly (license)

Packages