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

@auto-engineer/server-checks

v0.22.0

Published

Server validation commands for TypeScript type checking, ESLint linting, and Vitest test execution.

Readme

@auto-engineer/server-checks

Server validation commands for TypeScript type checking, ESLint linting, and Vitest test execution.


Purpose

Without @auto-engineer/server-checks, you would have to manually run TypeScript, ESLint, and Vitest separately, parse their outputs, and integrate results into your pipeline.

This package provides command handlers for validating server code quality. Each command follows the CQRS pattern, accepting a command and emitting passed or failed events for integration with event-driven workflows.


Installation

pnpm add @auto-engineer/server-checks

Quick Start

Register the handlers and run validation checks:

1. Register the handlers

import { COMMANDS } from '@auto-engineer/server-checks';
import { createMessageBus } from '@auto-engineer/message-bus';

const bus = createMessageBus();
COMMANDS.forEach(cmd => bus.registerCommand(cmd));

2. Send a command

const result = await bus.dispatch({
  type: 'CheckTypes',
  data: {
    targetDirectory: './server',
  },
  requestId: 'req-123',
});

console.log(result);
// → { type: 'TypeCheckPassed', data: { targetDirectory: './server', checkedFiles: 42 } }

The command runs tsc --noEmit and returns structured results.


How-to Guides

Run via CLI

auto check:types --target-directory=./server
auto check:lint --target-directory=./server
auto check:tests --target-directory=./server

Run with Auto-Fix

auto check:lint --target-directory=./server --fix

Run at Project Scope

auto check:types --target-directory=./server --scope=project

Run Programmatically

import { checkTypesCommandHandler } from '@auto-engineer/server-checks';

const result = await checkTypesCommandHandler.handle({
  type: 'CheckTypes',
  data: {
    targetDirectory: './server',
    scope: 'slice',
  },
  requestId: 'req-123',
});

Handle Errors

if (result.type === 'TypeCheckFailed') {
  console.error('Type errors:', result.data.errors);
  console.error('Failed files:', result.data.failedFiles);
}

if (result.type === 'LintCheckFailed') {
  console.error('Lint errors:', result.data.errorCount);
}

if (result.type === 'TestsCheckFailed') {
  console.error('Failed tests:', result.data.failedTests);
}

Enable Debug Logging

DEBUG=auto:server-checks:* auto check:types --target-directory=./server

API Reference

Exports

import {
  COMMANDS,
  checkTypesCommandHandler,
  checkLintCommandHandler,
  checkTestsCommandHandler,
} from '@auto-engineer/server-checks';

import type {
  CheckTypesCommand,
  TypeCheckPassedEvent,
  TypeCheckFailedEvent,
  CheckLintCommand,
  LintCheckPassedEvent,
  LintCheckFailedEvent,
  CheckTestsCommand,
  TestsCheckPassedEvent,
  TestsCheckFailedEvent,
} from '@auto-engineer/server-checks';

Commands

| Command | CLI Alias | Description | |---------|-----------|-------------| | CheckTypes | check:types | Run TypeScript type checking | | CheckLint | check:lint | Run ESLint validation | | CheckTests | check:tests | Run Vitest tests |

CheckTypesCommand

type CheckTypesCommand = Command<'CheckTypes', {
  targetDirectory: string;
  scope?: 'slice' | 'project';
}>;

CheckLintCommand

type CheckLintCommand = Command<'CheckLint', {
  targetDirectory: string;
  scope?: 'slice' | 'project';
  fix?: boolean;
}>;

CheckTestsCommand

type CheckTestsCommand = Command<'CheckTests', {
  targetDirectory: string;
  scope?: 'slice' | 'project';
}>;

Scope Options

| Value | Description | |-------|-------------| | slice | Check only files within target directory (default) | | project | Check all files in the project |


Architecture

src/
├── index.ts
└── commands/
    ├── check-types.ts
    ├── check-lint.ts
    └── check-tests.ts

The following diagram shows the check flow:

flowchart TB
    A[Command] --> B[Find Project Root]
    B --> C[Discover Files]
    C --> D[Run Tool]
    D --> E{Success?}
    E -->|Yes| F[PassedEvent]
    E -->|No| G[FailedEvent]

Flow: Command finds project root, discovers files based on scope, runs tool, emits result event.

Dependencies

| Package | Usage | |---------|-------| | @auto-engineer/message-bus | Command/event infrastructure | | execa | Process execution for tsc, eslint, vitest | | fast-glob | File discovery | | debug | Debug logging |