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

@living-architecture/riviere-extract-ts

v0.4.22

Published

TypeScript extractor for detecting architectural components from source code.

Readme

@living-architecture/riviere-extract-ts

TypeScript extractor for detecting architectural components from source code.

Overview

Extracts architectural components from TypeScript code using deterministic, config-driven detection rules. Uses ts-morph for AST parsing to identify components based on decorators, JSDoc tags, inheritance, interfaces, and naming patterns.

Current Status: Skeleton implementation. Predicate logic and output generation coming in subsequent tasks (see PRD phase-10-typescript-extraction).

Installation

npm install @living-architecture/riviere-extract-ts

Usage

import { extractComponents } from '@living-architecture/riviere-extract-ts'
import type { ExtractionConfig } from '@living-architecture/riviere-extract-config'

const config: ExtractionConfig = {
  modules: [
    {
      name: 'users',
      path: '.',
      glob: 'src/**/*.ts',
      api: {
        find: 'methods',
        where: { hasDecorator: { name: 'Get' } },
      },
      useCase: { notUsed: true },
      domainOp: { notUsed: true },
      event: { notUsed: true },
      eventHandler: { notUsed: true },
      ui: { notUsed: true },
    },
  ],
}

const sourceFiles = ['src/api/users.controller.ts']
const components = extractComponents(sourceFiles, config)

console.log(components)

Output Format

Draft components (before connection detection):

{
  "type": "api",
  "name": "getUserById",
  "location": {
    "file": "src/api/users.controller.ts",
    "line": 42
  },
  "domain": "users"
}

Development

# Tests (coverage enabled by default)
pnpm nx test riviere-extract-ts

# Build
pnpm nx build riviere-extract-ts

Related Packages

  • @living-architecture/riviere-extract-config - Config schema and validation
  • @living-architecture/riviere-extract-conventions - Decorators for marking components

License

Apache 2.0