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

@dvukovic/style-guide

v0.40.1

Published

My own style guide

Readme

@dvukovic/style-guide

Personal style guide with ESLint, Prettier, Stylelint, CSpell, Knip, jscpd and Lighthouse CI configurations.

Quick Start

npx -y @dvukovic/style-guide@latest init

This interactive CLI will:

  • Let you select which tools to configure (ESLint, Prettier, Stylelint, CSpell, Knip, jscpd)
  • Ask about your project setup (TypeScript, React/Next.js, testing frameworks)
  • Install required dependencies
  • Generate configuration files

Manual Installation

yarn add -D @dvukovic/style-guide eslint prettier stylelint cspell knip jscpd

ESLint

Create eslint.config.js:

import { customDefineConfig, core, typescript } from "@dvukovic/style-guide/eslint"

export default customDefineConfig({
    configs: [core(), typescript()],
    ignores: ["dist", "build"],
})

Available Configs

  • core() - Essential rules for all JavaScript/TypeScript projects
  • typescript() - TypeScript parser and rules
  • typescriptStrict() - Additional strict TypeScript rules
  • react() - React framework rules
  • next() - Next.js framework
  • node() - Node.js specific rules
  • jest() - Jest testing framework
  • vitest() - Vitest testing framework
  • playwright() - Playwright e2e testing
  • mobx() - MobX state management
  • storybook() - Storybook
  • tanstackQuery() - TanStack Query
  • turbo() - Turborepo
  • packageJson() - package.json linting
  • packageJsonWorkspace() - package.json linting for monorepos
  • nextIntl() - Locale aware navigation, carrying the barrel import patterns
  • noBarrels() - Aggregate and current directory barrel imports

Spreadable values for rules whose options ESLint replaces instead of merging:

  • RESTRICTED_SYNTAX - Enum and wildcard re-export selectors
  • NO_BARREL_PATTERNS - Barrel import patterns

Customizing Configs

Each factory function accepts a config parameter to extend or override settings:

import { customDefineConfig, core, typescript } from "@dvukovic/style-guide/eslint"

export default customDefineConfig({
    configs: [
        core(),
        typescript({
            rules: {
                "@typescript-eslint/no-unused-vars": "warn",
            },
        }),
    ],
    ignores: ["dist"],
})

Project Structure

@dvukovic/style-guide/eslint/project-structure wires eslint-plugin-project-structure. File composition is shared, the folder structure is assembled from the shared tree plus the folders this project adds:

import { folderStructure, projectStructure } from "@dvukovic/style-guide/eslint/project-structure"

export default customDefineConfig({
    configs: [
        projectStructure({
            folderStructure: folderStructure({
                ignorePatterns: ["src/__generated__/**"],
                src: [{ name: "content", children: [{ ruleId: "functionFolder" }] }],
            }),
        }),
        core(),
    ],
})

folderStructure() takes extra children per container: root, src, shared, constants, modules and ui. It also exports FOLDER_RULES, FILE_RULES, FILE_COMPOSITION, FUNCTION_SUFFIXES and COMPONENT_SUFFIXES for projects that assemble their own.

In a monorepo, pass projectRoot (for example projectRoot: "apps/web") to projectStructure(). The plugin resolves paths from the folder that holds its node_modules, so without it every path starts with apps/ and nothing is checked.

Component folders accept X.hooks.ts, X.variants.ts and X.stories.tsx next to the component; stories are left out of the one-component-per-file rule.

Prettier

Create prettier.config.ts:

import type { Config } from "prettier"

import { core } from "@dvukovic/style-guide/prettier"

const config: Config = {
    ...core,
}

export default config

Stylelint

Create stylelint.config.js:

import { core } from "@dvukovic/style-guide/stylelint"

/** @type {import("stylelint").Config} */
const config = {
    ...core,
}

export default config

Mantine

postcss-preset-mantine breakpoint variables are not valid media query syntax until postcss expands them, so the mantine config turns that rule off:

import { core, mantine } from "@dvukovic/style-guide/stylelint"

/** @type {import("stylelint").Config} */
const config = {
    ...core,
    rules: {
        ...core.rules,
        ...mantine.rules,
    },
}

export default config

CSpell

Create cspell.config.js:

import { core } from "@dvukovic/style-guide/cspell"

/** @type {import("cspell").FileSettings} */
const config = {
    ...core,
    ignorePaths: [...core.ignorePaths],
    ignoreWords: [],
}

export default config

Knip

Create knip.config.ts:

import type { KnipConfig } from "knip"

import { core } from "@dvukovic/style-guide/knip"

const config: KnipConfig = {
    ...core,
    ignore: [],
    ignoreDependencies: [...core.ignoreDependencies],
}

export default config

jscpd

jscpd reads JSON only, so init writes .jscpd.json from the shared config. The same values are available as core from @dvukovic/style-guide/jscpd.

Lighthouse CI

Create lighthouserc.cjs:

const { core } = require("@dvukovic/style-guide/lighthouse")

module.exports = core()

URLs come from SEO_LH_URLS, and SEO_LH_INP=1 adds the interaction assertion. Both can be passed as core({ inp, urls }) instead.

CLI

style-guide init         # Generate configuration files
style-guide check-dashes # Find em and en dashes in messages and content

check-dashes scans src/i18n/messages and src/content, and exits 1 on a hit.

Scripts

Add to your package.json:

{
    "scripts": {
        "lint": "yarn lint:eslint && yarn lint:prettier && yarn lint:stylelint && yarn lint:cspell && yarn lint:knip && yarn lint:jscpd",
        "lint:eslint": "eslint . --cache --concurrency=auto",
        "lint:prettier": "prettier --check --cache .",
        "lint:stylelint": "stylelint ./**/*.css --cache",
        "lint:cspell": "cspell --no-progress --no-summary --unique '**'",
        "lint:knip": "knip",
        "lint:jscpd": "jscpd",
        "lint:fix": "yarn lint:eslint --fix && yarn lint:prettier --write && yarn lint:stylelint --fix"
    }
}

License

MIT