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

@venizia/dev-configs

v0.2.0

Published

Shareable development configurations for TypeScript projects: ESLint v9 flat config (with unicorn plugin), Prettier formatting, and TypeScript compiler options with critical decorator support (experimentalDecorators, emitDecoratorMetadata, useDefineForCla

Readme

@venizia/dev-configs

The ESLint, Prettier and TypeScript settings every IGNIS package is built with. Install it as a dev dependency in an application that wants the same rules.

Install

bun add -d @venizia/dev-configs eslint prettier typescript

eslint (9 or 10), prettier (3) and typescript (5 or 6) are optional peers. Install only the tools you use.

Use it

Each tool takes one file.

// eslint.config.mjs
import { eslintConfigs } from '@venizia/dev-configs';

export default [{ ignores: ['dist/'] }, ...eslintConfigs];
// .prettierrc.mjs
import { prettierConfigs } from '@venizia/dev-configs';

export default prettierConfigs;
// tsconfig.json
{
  "extends": "@venizia/dev-configs/tsconfig.common.json",
  "compilerOptions": {
    "outDir": "dist",
    "rootDir": "src",
    "experimentalDecorators": true,
    "emitDecoratorMetadata": true
  },
  "include": ["src"]
}

Declare the decorator flag in your own tsconfig

The base config sets experimentalDecorators. But Bun can miss a flag inherited through extends when it runs your source. Parameter decorators are then dropped with no error, and an @inject value is undefined at run time.

Declare experimentalDecorators: true in your application's own tsconfig.json, as in the example earlier. Every IGNIS example does.

| Flag | Base value | Why | | :--- | :--- | :--- | | experimentalDecorators | true | @inject, @controller, @repository and the other decorators need it | | emitDecoratorMetadata | true | Optional. IGNIS reads design:paramtypes once, to validate a @repository constructor, and skips the check when the metadata is absent | | useDefineForClassFields | false | Class fields are assigned, not defined, so a subclass field initializer does not shadow a value the base constructor set |

Entry points

| Entry point | What it gives | | :--- | :--- | | @venizia/dev-configs | eslintConfigs (flat config array), prettierConfigs, BunCompiler | | @venizia/dev-configs/tsconfig.base.json | Target and lib ES2024, module Node16, strict mode with noImplicitAny, strictPropertyInitialization and useUnknownInCatchVariables off, noEmitOnError, tests excluded | | @venizia/dev-configs/tsconfig.common.json | Extends the base and switches module and moduleResolution to nodenext |

What each config sets

eslintConfigs is @minimaltech/eslint-node (ESLint recommended, typescript-eslint, Prettier as a lint rule, naming conventions, eslint-plugin-n) plus three IGNIS rules:

| Rule | Setting | | :--- | :--- | | @typescript-eslint/no-explicit-any | off | | curly | ['error', 'all'] | | unicorn/switch-case-braces | ['error', 'always'] |

prettierConfigs:

| Setting | Value | | :--- | :--- | | printWidth | 100 | | tabWidth | 2 | | singleQuote | true | | semi | true | | trailingComma | 'all' | | bracketSpacing | true | | arrowParens | 'avoid' |

BunCompiler.compile() builds one Bun executable: minified, with a linked source map. The compile target comes from BUN_TARGET and defaults to bun-linux-x64.

import { BunCompiler } from '@venizia/dev-configs';

await BunCompiler.compile({ entrypoint: './src/index.ts', outfile: './dist/app' });

Where it sits

The root of the chain, with no IGNIS dependency: dev-configs -> inversion -> {filter, helpers} -> {boot, kernel} -> connectors -> {core-worker, core-server} -> atlas.

Links

MIT licensed - see LICENSE.md.