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

@mentra/types

v1.0.0-beta.2

Published

Shared TypeScript types for MentraOS client and cloud

Readme

@mentra/types

Shared TypeScript types for MentraOS client and cloud.

Purpose

Single source of truth for client-facing types used by both mobile app and cloud backend. Eliminates type drift and duplication.

What's Included

  • AppletInterface - Minimal app interface for home screen (8 fields)
  • HardwareRequirement - Hardware requirements for apps
  • Capabilities - Device hardware capabilities
  • AppletPermission - App permission types
  • Enums: HardwareType, HardwareRequirementLevel

Installation

Already linked via Bun workspace. Just import:

import { AppletInterface, HardwareType, Capabilities } from "@mentra/types";

Development

# Build (compile TypeScript)
bun run build

# Watch mode
bun run dev

# Type check only
bun run typecheck

# Test Bun compatibility
bun run src/index.ts  # Should output nothing (no errors)

Bun Compatibility

This package uses explicit exports to work with Bun's runtime TypeScript execution:

// ✅ Types/Interfaces - export type
export type { AppletInterface, Capabilities } from "./applet";

// ✅ Enums (runtime) - export
export { HardwareType } from "./enums";

// ❌ Never use this (breaks Bun)
export * from "./applet";

See cloud/issues/todo/sdk-type-exports/README.md for details.

Usage Examples

In Cloud Services

import { AppletInterface } from "@mentra/types";

export class ClientAppsService {
  static async getAppsForHomeScreen(
    userId: string,
  ): Promise<AppletInterface[]> {
    // Return minimal interface for client
  }
}

In Mobile Client

import { AppletInterface, HardwareType } from "@mentra/types";

function renderAppList(apps: AppletInterface[]) {
  // Render home screen
}

What NOT to Include

  • ❌ Internal database models (AppI, UserI)
  • ❌ Service logic or business rules
  • ❌ Validation schemas
  • ❌ Complex SDK types (webhooks, tool schemas)
  • ❌ Runtime dependencies

What to Include

  • ✅ Client-facing app types
  • ✅ Hardware capability types
  • ✅ Permission types
  • ✅ Shared enums
  • ✅ Minimal DTOs

Adding New Types

  1. Add type definition in appropriate file (applet.ts, hardware.ts, etc.)

  2. Add explicit export in src/index.ts:

    // For types/interfaces
    export type { MyNewType } from "./file";
    
    // For enums/values
    export { MyNewEnum } from "./file";
  3. Test Bun compatibility: bun run src/index.ts

  4. Build: bun run build

  5. Bump version in package.json (semver)

Versioning

  • Major: Breaking changes to existing types
  • Minor: New optional fields or new types
  • Patch: Documentation, internal changes

Files

  • src/enums.ts - Runtime enums (HardwareType, etc.)
  • src/hardware.ts - Hardware capability types
  • src/applet.ts - App/applet types for clients
  • src/index.ts - Main export (Bun-compatible)

Links