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

@latellu/atlas-cli

v0.1.5

Published

Generate TypeScript types from an Atlas CMS workspace schema

Readme

@latellu/atlas-cli

Generate TypeScript types from an Atlas CMS workspace schema.

Full documentation: https://docs.atlas.latellu.com

The CLI calls GET /api/v1/public/schema on your Atlas backend (the workspace is derived from the API key) and writes an atlas.types.ts file with:

  • one interface per content type (PascalCase name from the slug),
  • select fields as string-literal unions,
  • a Locale union from the workspace's configured locales,
  • an AtlasContentTypes registry mapping each slug to its interface.

Usage

npx @latellu/atlas-cli generate --api-key=atlas_live_xxx --output=./src/types

Options

| Flag | Env | Default | Description | | --- | --- | --- | --- | | --api-key | ATLAS_API_KEY | — (required) | Workspace API key | | --url | ATLAS_API_URL | https://api.atlas.latellu.com | Atlas backend base URL (override only for self-hosted) | | --output | ATLAS_OUTPUT | ./src/atlas.types.ts | Output file, or directory (writes atlas.types.ts inside) |

Example output

// Generated by @latellu/atlas-cli — DO NOT EDIT BY HAND.
// Workspace: museum-kyoto

export type Locale = "en" | "ja";

/** Article (content type: "article") */
export interface Article {
  title: string; // localizable
  category?: "News" | "Event";
  published_at?: string;
  featured?: boolean;
  cover_image?: string;
  author?: string;
}

/** Maps each content-type slug to its entry interface. */
export interface AtlasContentTypes {
  "article": Article;
}

Localizable fields are typed as their base value in this release; a per-locale representation is planned alongside @latellu/atlas-sdk.

image, relation, and content_type_reference fields (cover_image and author above) are typed as plain string — the referenced media ID or entry ID/slug, not a resolved object. Resolve them yourself with atlas.media.get(id) or atlas.entries(type).get(slug) from @latellu/atlas-sdk. See content types for the full list of field types Atlas supports.