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

@mettlecast/eslint-plugin-domain-module

v0.2.54

Published

ESLint plugin enforcing TIB Domain Module framework usage patterns. Prevents accidental AWS SDK, HTTP server, and cross-domain violations.

Readme

@mettlecast/eslint-plugin-domain-module

ESLint plugin enforcing TIB Domain Module framework usage patterns. Prevents accidental AWS SDK, HTTP server, and cross-domain violations.

Install

npm install --save-dev @mettlecast/eslint-plugin-domain-module

Configure in eslint.config.js:

import domainModulePlugin from '@mettlecast/eslint-plugin-domain-module';

export default [
  {
    files: ['src/domain/**/*.ts'],
    ...domainModulePlugin.configs.recommended,
  },
];

Rules

| Rule | Flags | Severity | |---|---|---| | no-raw-aws-sdk | Direct imports of @aws-sdk/* packages in domain handler files | error | | no-raw-http-server | Framework imports (express, koa, fastify, aws-lambda) in domain handlers | error | | require-define-primitive | Handler files without a top-level define*() call (missing domain primitive declaration) | warn | | no-cross-domain-internal-import | Importing internal modules (not exported types) from another domain directory | error |

Recommended Config

The recommended preset enables all four rules at their default severity levels:

domainModulePlugin.configs.recommended
// Results in:
// - no-raw-aws-sdk: error
// - no-raw-http-server: error
// - require-define-primitive: warn
// - no-cross-domain-internal-import: error

Examples

Violations caught:

// ❌ no-raw-aws-sdk
import { DynamoDBClient } from '@aws-sdk/client-dynamodb';

// ❌ no-raw-http-server
import express from 'express';

// ❌ require-define-primitive
export async function chargePayment(event, ctx) { /* ... */ }

// ❌ no-cross-domain-internal-import
import { internalFn } from '../payments/internal.js'; // not in payments/index.ts

Correct usage:

// ✓ Use DomainContext.db instead
const { db } = ctx;

// ✓ Use defineApi() to declare handlers
export const chargeHandler = defineApi({
  path: '/charge',
  // ...
});

// ✓ Only import exported types from other domains
import type { PaymentEvent } from '@myorg/payments-contracts';

See Also

  • @mettlecast/domain-runtime — handler definitions
  • @mettlecast/domain-cli — validation and linting