Deno Standard Library

High-quality APIs for Deno and the web. Use fearlessly.

Note

Newer versions of the Standard Library are now hosted on JSR. Older versions up till 0.224.0 are still available at deno.land/std.

Packages

The following list contains links to the Standard Library's packages and documentation:

Package	Status	Latest version
archive	Unstable
assert	Settled
async	Settled
bytes	Settled
cli	Unstable
collections	Settled
crypto	Settled
csv	Settled
data_structures	Unstable
datetime	Unstable
dotenv	Unstable
encoding	Settled
expect	Unstable
fmt	Settled
front_matter	Settled
fs	Settled
html	Unstable
http	Unstable
ini	Unstable
io	Unstable
json	Settled
jsonc	Settled
log	Unstable
media_types	Settled
msgpack	Unstable
net	Unstable
path	Settled
regexp	Unstable
semver	Unstable
streams	Settled
testing	Settled
text	Unstable
toml	Settled
ulid	Unstable
url	Unstable
uuid	Settled
webgpu	Unstable
yaml	Settled

Note: Settled status means a package is unlikely to have breaking changes, but has not yet achieved v1 status.

Stabilization

The Standard Library is now in the process of stabilizing its packages. Below is the current schedule:

• @std/bytes is being stabilized on June 7, 2024 (#4746).
• @std/collections is being stabilized on June 20, 2024 (#4773).
• @std/media-types is being stabilized on June 21, 2024 (#4780).

Each package must go through the following steps to achieve stabilization:

1. Publish version 1.0.0-rc.1 once meeting the following requirements:
   1. Approved by at least 2 maintainers. There must be consensus that the design, documentation and implementation of the package are good and that it is unlikely to undergo breaking changes in the future.
   2. 100% documented, passing deno doc --lint checks and adhering to the documentation guidelines.
   3. Maximum possible test coverage
   4. No open issues or pull requests that might lead to breaking changes. For example, issues that suggest new non-breaking features are fine to exist at stabilization.
2. Allow 1 month for the community and the core team to review the package and handle any feedback. There must be consensus that the design, documentation and implementation of the package are good and that it is unlikely to undergo breaking changes in the future.
3. If there are no remaining issues, publish version 1.0.0. If there are remaining issues, extend the waiting period to allow further time for a resolution. Then, repeat this step.

Architecture

Check out the architecture guide here.

Design

Minimal Exports

Files are structured to minimize the number of dependencies they incur and the amount of effort required to manage them, both for the maintainer and the user. In most cases, only a single function or class, alongside its related types, are exported. In other cases, functions that incur negligible dependency overhead will be grouped together in the same file.

Contributing

Check out the contributing guidelines here.

Releases

New versions of packages are published every 1 or 2 weeks. Package versions

=1.0.0 follow Semantic Versioning, and package versions <1.0.0 follow this proposal.

Badge

<a href="https://jsr.io/@std">
  <img
    width="135"
    height="20"
    src="https://raw.githubusercontent.com/denoland/deno_std/main/badge.svg"
    alt="Built with the Deno Standard Library"
  />
</a>

[![Built with the Deno Standard Library](https://raw.githubusercontent.com/denoland/deno_std/main/badge.svg)](https://jsr.io/@std)

Frequently Asked Questions

Check out the frequently asked questions page here.