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

@sammons/typed-mind

v1.1.1

Published

Core language parser and validator for TypedMind DSL - a declarative language for building software architectures

Readme

@sammons/typed-mind

Core language parser and validator for TypedMind DSL - a declarative language for building software architectures.

Installation

npm install @sammons/typed-mind

Usage

import { TypedMindParser, TypedMindValidator } from '@sammons/typed-mind';

// Parse TypedMind source code
const parser = new TypedMindParser();
const program = parser.parse(source);

// Validate the parsed program
const validator = new TypedMindValidator();
const validationResult = validator.validate(program);

if (validationResult.isValid) {
  console.log('Program is valid!');
} else {
  console.log('Validation errors:', validationResult.errors);
}

What is TypedMind?

TypedMind is a Domain Specific Language (DSL) for declaratively describing software architectures, including:

  • Data Transfer Objects (DTOs) - Pure data structures for configuration, serialization, and parameters (no functions allowed)
  • Service classes - Business logic with methods and dependencies
  • ClassFile entities - Fusion entities that combine class and file definitions - perfect for services and controllers
  • UI components - User interface elements and their relationships
  • Asset management - Static assets and routing configuration
  • Cross-cutting concerns - Validation, security, and other system-wide concerns

Features

  • Declarative syntax - Focus on what your system does, not how it's implemented
  • Strong validation - Catch architectural issues before they become problems
  • Dependency tracking - Understand relationships between components
  • Import system - Modular architecture with file-based organization
  • Type safety - Comprehensive validation of all language constructs

Example

program "User Management System"

dto UserDto {
  id: string
  email: string
  name: string
  createdAt: date
}

service UserService {
  method createUser(email: string, name: string): UserDto
  method getUserById(id: string): UserDto
  depends on DatabaseService
}

ui UserListComponent {
  displays UserDto[]
  triggers UserService.createUser
}

Grammar

The complete TypedMind grammar is documented in grammar.md and available in EBNF format in grammar.ebnf.

Contributing a checker rule or extractor warning

Every diagnostic message follows docs/diagnostic-style-guide.md's three-clause rule (what, where, what to do), backtick-quotes every named entity, and avoids internal implementation vocabulary. A standing lint (pnpm run check:diagnostic-jargon) enforces the no-jargon half of that rule in CI. docs/diagnostic-code-audit.md grades every registered code's current message against the guide (100% of the registry, checked for completeness via pnpm run check:diagnostic-code-audit) — grade a new code there when adding one.

Generic declarations

DTO, alias, Function, Class and ClassFile heads accept names-only parameters, including qualified names: Owner.Pair<T, U> %, Owner.Alias<T> = T, and Owner.Child<T> <: Owner.Base<T>. Constraints, defaults and const/in/out modifiers use repeated quoted longform properties:

dto Owner.Pair {
  typeParameter: "out T extends Constraint = Default"
  typeParameter: "U = Map<T, Other>"
  extends: "Owner.Base<T>"
}

Class longform accepts a quoted extends and repeated quoted implements properties; DTO inheritance uses repeated extends. Formatting promotes to longform whenever shortform cannot retain parameters or inheritance roles. Inline constrained/defaulted declaration heads are unsupported. Local parameters are declaration metadata, never separate global entities.

The shared parameter parser retains raw source for inspection and canonicalizes whitespace/comments outside literals for emission. Physical newlines inside literal values are unsupported and produce an explicit parse diagnostic. emitWithDiagnostics also reports invalid programmatically constructed generic metadata. The string-only emit API keeps its existing behavior; callers using it must validate unsupported metadata before emission.

Requirements

  • Node.js >= 22.0.0

Related Packages

License

MIT