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

dr-mike

v0.2.0

Published

Opinionated, composable ESLint, TypeScript, and Vitest configuration presets

Readme

dr-mike

Opinionated, composable ESLint, TypeScript, and Vitest configuration presets. One package, three subpath exports — opt in to the pieces you want.

Install

pnpm add -D dr-mike

That's it. dr-mike bundles every plugin and tool it needs — eslint, typescript, vitest, the rule plugins, the language services — at the exact versions it was tested with. You don't need to install anything else.

If you want to use a different version of eslint, typescript, or vitest, install your own copy and pnpm will hoist it; dr-mike's pinned copies just become the fallback.

ESLint

// eslint.config.js
import drMike from 'dr-mike/eslint'

export default drMike()

The default export is a synchronous factory. No await required.

Options

export default drMike({
  gitignore: true,        // bool | string. true = auto-detect ./.gitignore. string = absolute path. false = disable.
  internalPattern: [],    // string[] — perfectionist sort-imports "internal" group regex(es). Default: []
  turborepo: false,       // adds eslint-plugin-turbo
  vitest: false,          // adds @vitest/eslint-plugin rules to **/*.test.ts
  effect: false,          // adds @codeforbreakfast/eslint-effect rules
})

All optional features default to false. Flip them on as needed — every plugin is already installed.

Batteries-included preset

If you want everything turned on, skip the factory call:

// eslint.config.js
export { default } from 'dr-mike/eslint/full'

This is equivalent to drMike({ turborepo: true, vitest: true, effect: true }).

Svelte profile

// eslint.config.js
import drMike from 'dr-mike/eslint/svelte'
import svelteConfig from './svelte.config.js'

export default [
  ...drMike(),
  {
    files: ['**/*.svelte', '**/*.svelte.ts'],
    languageOptions: {
      parserOptions: { svelteConfig, tsconfigRootDir: import.meta.dirname },
    },
  },
]

The svelte profile relies on svelte being present in your project — which it always is for a Svelte codebase, so no extra install is needed.

Monorepos

dr-mike's preset allows root-level *.config.{ts,mts,cts} files (e.g. vitest.config.ts) to be linted without expanding your tsconfig include. The match is relative to typescript-eslint's tsconfigRootDir, which defaults to process.cwd().

For monorepos, this means:

  • Per-package ESLint configs (recommended): each package has its own eslint.config.js extending dr-mike, and lint runs per-package (e.g. via turbo). Config files in each package are picked up automatically. No extra setup.
  • Single root ESLint config linting the whole repo: the glob only matches root-level files; nested packages/*/vitest.config.ts won't be matched. Either run lint per-package, or add the nested config files to a tsconfig include.

Extending

export default [
  ...drMike({ turborepo: true }),
  {
    rules: {
      '@typescript-eslint/no-explicit-any': 'off',
    },
  },
]

TypeScript

Strictest-possible base preset, with environment-specific extensions. Uses TS 6 ${configDir} so outDir and include resolve relative to the consumer's tsconfig.

{
  "extends": "dr-mike/tsconfig/node"
}

Available presets:

| Subpath | Use for | |---|---| | dr-mike/tsconfig/base | The strictest base. Extend if you need a custom target/module. | | dr-mike/tsconfig/node | Node 22+, NodeNext modules, ES2023 lib. | | dr-mike/tsconfig/node-effect | Same as node plus @effect/language-service plugin. | | dr-mike/tsconfig/svelte | Svelte/SvelteKit, Bundler resolution, DOM lib. |

typescript ships with dr-mike at the version it's tested against. To use a different version, install your own — pnpm will hoist it. Note that typescript-eslint has a tight TS compatibility window; very old (pre-5.0) or future major versions may not parse cleanly.

Vitest

// vitest.config.js
import sharedConfig, { defineConfig, mergeConfig } from 'dr-mike/vitest'

export default mergeConfig(
  sharedConfig,
  defineConfig({
    test: { name: 'my-package' },
  }),
)

Defaults: src/**/*.test.ts, globals on, V8 coverage on, HTML/JSON/text reporters.

Versioning & releases

Uses Changesets. Contributors run pnpm changeset to describe their change; merging the auto-generated "Version Packages" PR cuts a release and publishes to npm.

License

MIT