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

@injitools/core

v0.2.1

Published

Core of the Inji framework: declarative router, DTO/Zod validation, OpenAPI generation and error handling. No database dependency.

Readme

@injitools/core

Core of the Inji framework: a declarative router with DTO/Zod validation, OpenAPI 3.1 generation, middleware wiring and an error hierarchy. No database dependency.

Part of the Inji monorepo.

Install

npm install @injitools/core

Requires experimentalDecorators + emitDecoratorMetadata in your tsconfig.json.

Usage

import {Router, Get, Response, InjiRouter} from "@injitools/core";

@Router("hello")
class HelloApi {
  @Get()
  @Response(200, String)
  index() { return "Hello"; }
}

const router = new InjiRouter([HelloApi]);
app.use(router.toExpressRouter()); // Express router
router.toOpenApi();                // OpenAPI 3.1 spec

Entry points

  • @injitools/core — router, RequestDto/ResponseDto and validation decorators, error middleware, buildOpenApiDocument (router → OpenAPI 3.1 doc), and createApiClient/createFetchClient (an inter-server client between backends).
  • @injitools/core/codegenemitSchema (router → generated schema.gen.ts TS interfaces for frontends). A separate subpath (uses node:fs) so runtime servers don't pull in the generator. Needs only ORM metadata — run it offline via TypeORM's buildMetadatas(), no DB connection.
  • @injitools/core/runtimeenv, Config, loadEnv, environment helpers.
  • @injitools/core/lifecyclemakeProcess, graceful shutdown.

See the monorepo README for the full picture.

License

MIT