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

@wonse/eslint-ts

v5.0.0

Published

Shared ESLint config for TypeScript projects

Readme

@wonse/eslint-ts

Shared ESLint configuration for TypeScript projects using the new ESLint flat config.

Features

  • 🎯 Optimized for modern TypeScript development
  • 🔄 Uses the new ESLint flat config system
  • 🎨 Integrates with Prettier for consistent code formatting
  • 🔍 Strict type checking rules enabled
  • 📦 Extends JavaScript configuration with TypeScript-specific rules

Installation

# Using npm
npm install --save-dev @wonse/eslint-ts eslint typescript

# Using yarn
yarn add --dev @wonse/eslint-ts eslint typescript

# Using pnpm
pnpm add -D @wonse/eslint-ts eslint typescript

Usage

Create an eslint.config.js file in your project root:

import tsConfig from '@wonse/eslint-ts';

export default [
  ...tsConfig,
  // Your custom configurations (optional)
];

Configuration Details

The base configuration includes:

  • All JavaScript rules from @wonse/eslint-js
  • TypeScript parser configuration
  • Strict type-checking rules
  • TypeScript-specific best practices
  • Integration with your project's tsconfig.json

Extending the Configuration

You can extend or override the configuration in several ways:

  1. Adding New Rules:
import tsConfig from '@wonse/eslint-ts';

export default [
  ...tsConfig,
  {
    rules: {
      '@typescript-eslint/explicit-function-return-type': 'error',
      '@typescript-eslint/no-explicit-any': 'error',
    },
  },
];
  1. Targeting Specific Files:
import tsConfig from '@wonse/eslint-ts';

export default [
  ...tsConfig,
  {
    files: ['src/**/*.ts'],
    rules: {
      '@typescript-eslint/strict-boolean-expressions': 'error',
    },
  },
];
  1. Custom Parser Options:
import tsConfig from '@wonse/eslint-ts';

export default [
  ...tsConfig,
  {
    files: ['**/*.ts'],
    languageOptions: {
      parserOptions: {
        project: './tsconfig.build.json',
      },
    },
  },
];

Included Rules

This configuration includes carefully selected rules from:

TypeScript-Specific Rules

  • Strict type checking enabled
  • Prevents unsafe type assertions
  • Enforces explicit return types where beneficial
  • Ensures proper usage of generics
  • Prevents unnecessary type declarations

Type Assertions and Casting

  • Prefers type assertions over casting
  • Prevents unnecessary type assertions
  • Ensures type assertions are safe

Code Quality

  • Prevents unused variables and types
  • Enforces consistent type definitions
  • Ensures proper error handling
  • Prevents unreachable code

Best Practices

  • Enforces consistent type imports
  • Prevents unsafe type assumptions
  • Ensures proper null checks
  • Enforces proper Promise handling

Contributing

Contributions are welcome! Please feel free to submit a Pull Request.

License

MIT

Author

Wonse Shin (@shinwonse)