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

@alma-oss/eslint-config-typescript

v3.0.0-alpha.2

Published

Alma's ESLint config for TypeScript projects

Readme

@alma-oss/eslint-config-typescript

ESLint configuration for TypeScript projects

📦 Installation

npm install --save-dev eslint @alma-oss/eslint-config-typescript
# or
yarn add --dev eslint @alma-oss/eslint-config-typescript

🧩 Rulesets

  • @alma-oss/eslint-config-typescript

A generic ruleset that focuses on code correctness.

  • @alma-oss/eslint-config-typescript/optional

Additional ruleset that might provide useful tips and hints how to improve your code.

For new projects, it is recommended to enable this ruleset. For existing projects, it is only recommended for the brave.

  • @alma-oss/eslint-config-typescript/style

Ruleset that focuses on code style (indentation, spacing, naming, syntax preference etc.).

  • @alma-oss/eslint-config-typescript/react

Ruleset that provides additional customizations for the @alma-oss/eslint-config-react ruleset when working with TypeScript.

👨‍💻 Usage

A full configuration for a TypeScript on Node.js project:

// eslint.config.js
import typescript from '@alma-oss/eslint-config-typescript';
import optional from '@alma-oss/eslint-config-typescript/optional';
import style from '@alma-oss/eslint-config-typescript/style';

/** @type {Array<import("eslint").Linter.Config>} */
export default defineConfig({
  ...typescript,
  ...optional,
  ...style,

  parserOptions: {
    // The project field is required in order for some TS-syntax-specific rules to function at all
    // @see https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/parser#configuration
    project: './tsconfig.json',
  },
});

A full configuration for a TypeScript on React project:

Please note, that you need to have eslint-config-react installed as well

// eslint.config.mjs
import { defineConfig, globalIgnores } from 'eslint/config';
import typescript from '@alma-oss/eslint-config-typescript';
import react from '@alma-oss/eslint-config-typescript/react';
import optional from '@alma-oss/eslint-config-typescript/optional';
import style from '@alma-oss/eslint-config-typescript/style';

export default defineConfig([
  ...typescript,
  ...react,
  ...optional,
  ...style,

  {
    parserOptions: {
      // The project field is required in order for some TS-syntax-specific rules to function at all
      // @see https://github.com/typescript-eslint/typescript-eslint/tree/master/packages/parser#configuration
      project: './tsconfig.json',
    },
  },
]);

🔌 Integration

Visual Studio Code

The vscode-eslint plugin for integrating ESLint into VSCode does not automatically parse TypeScript files. To do so, you must inform ESLint to enable on TypeScript files by adding this configuration to your settings (File > Preferences > Settings):

  "eslint.validate": [
    "javascript",
    "javascriptreact",
    { "language": "typescript", "autoFix": true },
    { "language": "typescriptreact", "autoFix": true }
  ]

Notice we are adding javascriptreact and typescriptreact above. It won’t harm adding those, but you can always omit these languages if not using them.

🙌 Contributing

We’re always looking for contributors to help us fix bugs, build new features, or help us improve the project documentation. If you’re interested, definitely check out our Contributing Guide! 👀

📝 License

Licensed under the MIT.