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

@construkt-kit/config

v0.1.2

Published

Shared tool configuration for all Construkt Kit frontend projects

Readme

@construkt-kit/config

Shared tool configuration for Construkt Kit frontend projects.

Sub-paths

| Import | Usage | | ---------------------------------- | ----------------------------------------------------------------------------- | | @construkt-kit/config/typescript | "extends": "@construkt-kit/config/typescript" in tsconfig.json | | @construkt-kit/config/oxlint | import baseConfig from "@construkt-kit/config/oxlint" in oxlint.config.ts | | @construkt-kit/config/oxfmt | export { default } from "@construkt-kit/config/oxfmt" in oxfmt.config.ts | | @construkt-kit/config/vite | createViteConfig(overrides?) factory | | @construkt-kit/config/playwright | createPlaywrightConfig(overrides?) factory | | @construkt-kit/config/kubb | createKubbConfig(options) factory for OpenAPI codegen |

Oxlint Config

The shared @construkt-kit/config/oxlint export now ships as a TypeScript config module. Consume it from an oxlint.config.ts file and merge local overrides there.

This requires the Node-based oxlint runtime with a Node version new enough to execute TypeScript config files.

Oxfmt Config

The shared @construkt-kit/config/oxfmt base enables Oxc import sorting via sortImports: true, so consuming packages inherit automatic import ordering without additional local config.

Vite Config

createViteConfig(overrides?) returns a merged Vite config using Vite's mergeConfig() (properly merges plugin arrays, not shallow).

Kubb Config (OpenAPI Codegen)

createKubbConfig(options?) generates a Kubb config that produces 3 output directories:

| Output dir | Content | Plugin | | ---------- | ------------------------------------- | ------------------ | | dtos/ | TypeScript types from OpenAPI schemas | pluginTs | | calls/ | API call functions | pluginClient | | hooks/ | React Query hooks (grouped by path) | pluginReactQuery |

Options (all optional):

| Option | Default | Description | | ------------------ | ------------------------ | ------------------------------ | | inputPath | ./src/api/openapi.json | Path to OpenAPI spec | | outputPath | ./src/api/gen | Output directory | | clientImportPath | @/api/client | Import path for the API client |

Key behaviors:

  • Query key versioning: All React Query keys are prefixed with "v5" for cache invalidation on breaking API changes
  • Path params as objects: pathParamsType: "object" — route params are passed as { id } not positional args
  • Inline params: paramsType: "inline" — params are inlined into hook signatures