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

@companyio/tooling

v0.1.0

Published

Shared TypeScript, Vitest, and Vite configuration for CompanyIO packages and apps

Readme

@companyio/tooling package

Shared development / build / test configuration for the CompanyIO monorepo.

This package is not a business domain package. It does not own Accounting, Contacts, Fuel, Prisma, auth, or UI.

What belongs here

  • TypeScript base / library / backend / frontend configs
  • Shared Vitest defaults (Node vs browser)
  • Shared Vite defaults for frontend apps
  • Guidance for the root pnpm catalog of tooling versions

What does NOT belong here

  • Domain schemas → @companyio/schemas
  • Domain logic → accounting, contacts, fuel, hr, …
  • Prisma / database → apps/api
  • Fastify / React as forced transitive runtime deps
  • Product UI redesign

TypeScript

{
  "extends": "@companyio/tooling/typescript/backend.json",
  "compilerOptions": {
    "outDir": "./dist",
    "rootDir": "./src"
  },
  "include": ["src"],
  "exclude": ["node_modules", "dist", "src/**/*.test.ts"]
}

Presets:

| Export | Use for | | --------------------------------------------- | -------------------------------------------- | | @companyio/tooling/typescript/base.json | Lowest shared compiler options | | @companyio/tooling/typescript/library.json | Publishable packages (strict + declarations) | | @companyio/tooling/typescript/backend.json | Node packages (types: ["node"]) | | @companyio/tooling/typescript/frontend.json | React libraries/apps (jsx: react-jsx) |

Vitest

import { defineConfig } from 'vitest/config';
import { nodeVitestConfig } from '@companyio/tooling/vitest';

export default defineConfig({
  ...nodeVitestConfig,
  test: {
    ...nodeVitestConfig.test,
    // package overrides
  },
});
  • Node packages: nodeVitestConfig from @companyio/tooling/vitest
  • Browser packages: browserVitestConfig from @companyio/tooling/vitest

Vite

import { defineConfig } from 'vite';
import { reactAppViteConfig } from '@companyio/tooling/vite';

export default defineConfig({
  ...reactAppViteConfig,
  plugins: [/* app-owned plugins */],
});

Vite stays optional: backend packages must not depend on it.

Dependency catalog

Versions for TypeScript, Vitest, Vite, @types/node, ESLint, and Prettier live in the root pnpm-workspace.yaml catalog: block.

Package package.json entries should use:

"typescript": "catalog:",
"vitest": "catalog:"

Update the catalog once, then run pnpm install.

Updating shared tooling

  1. Change the version in root pnpm-workspace.yaml → catalog.
  2. Adjust shared configs under packages/tooling/ if needed.
  3. pnpm install
  4. Run package typecheck / tests / builds.

Packages still list typescript / vitest / vite as direct catalog: devDependencies when they run those tools. @companyio/tooling owns configuration, not the CLI binaries for every consumer.

Install

{
  "devDependencies": {
    "@companyio/tooling": "workspace:*",
    "typescript": "catalog:",
    "vitest": "catalog:"
  }
}