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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@anoesj/eslint-config-vue-ts

v0.4.1

Published

Anoesj's ESLint config for Vue and Nuxt projects with TypeScript

Readme

@anoesj/eslint-config-vue-ts

This is an opiniated set of ESLint rules for Vue and Nuxt projects using TypeScript. It extends:

Installation

Install using your Node.js package manager of choice:

pnpm i -D @anoesj/eslint-config-vue-ts

You need to have NPM package eslint installed in order to start using ESLint with this configuration. Assuming your IDE of choice is VSCode, it's recommended to install VSCode plugin "ESLint" by Dirk Baeumer and set it up as follows in your VSCode workspace's settings.json:

{
  "editor.codeActionsOnSave": {
    "source.fixAll": "never", // optional
    "source.fixAll.eslint": "explicit"
  },
  "eslint.format.enable": true,
}

Usage

In your eslint.config.js file, write the following for a simple, default setup:

// @ts-check
import vueTsEslint from '@anoesj/eslint-config-vue-ts';

export default vueTsEslint();

When you want to add more rules of your own and you want type checking on your config file, use defineConfig from eslint/config:

// @ts-check
import vueTsEslint from '@anoesj/eslint-config-vue-ts';
import { defineConfig } from 'eslint/config';

export default defineConfig(
  ...vueTsEslint(),
  {
    files: ['src/components/**/*Icon*.vue'],
    rules: {
      // Disable max-len for icon components, as they usually contain long SVG paths
      '@stylistic/max-len': 'off',
    },
  },
);

If this causes any type errors, what may be happening is that another package is installing @types/eslint, which is a package that can be removed entirely. Using pnpm overrides in your pnpm-workspace.yaml or package.json, you can prevent the installation of the package:

pnpm-workspace.yaml

overrides:
  '@types/eslint': '-'

package.json

{
  "pnpm": {
    "overrides": {
      "@types/eslint": "-"
    }
  }
}

Configuration

You can pass an object to configure some options:

  • ignores: override the default list of files to ignore
  • files: override the default list of files to lint
  • rules: add or override the default rules

Example:

// @ts-check
import vueTsEslint, {
  defaultIgnores,
  defaultFiles,
} from '@anoesj/eslint-config-vue-ts';

export default vueTsEslint({
  ignores: [
    ...defaultIgnores,
    'cypress/**',
    '.nuxt-e2e-build/**',
  ],
  files: defaultFiles.filter((file) => !file.includes('js')),
  rules: {
    '@stylistic/max-len': 'off',
  },
});

Caveats

While ESLint provides its own defineConfig function, it does not provide type definitions for rules yet. This is a work in progress in the ESLint ecosystem:

  • https://github.com/eslint/eslint/issues/19721
  • https://github.com/eslint/eslint/pull/19843

Development

Maintenance

This is a project I mainly use for my own projects, but feel free to use it if you like it. I may not always be able to keep up with the latest changes in the ESLint ecosystem. Also, know that I may introduce breaking changes without notice, but I'll try to keep this README.md up-to-date.

If you have any suggestions or improvements, feel free to open an issue or a pull request. I may not respond immediately, but I'll try to get back to you as soon as possible.

Other

Building

This project is written in TypeScript and converted to .js & .d.ts files using tsdown.

Linting

I lint this project using itself, using experimental eslint.config.ts file loading.

Before Node v22.10.0, you could not load TS files natively in Node. It required jiti as a project dependency and configuring ESLint to use the unstable_ts_config flag, e.g. in your .vscode/settings.json:

{
  "eslint.options": {
    "flags": ["unstable_ts_config"],
  },
}

Since Node v22.18.0, you can use the native support for TS files in Node. This requires configuring ESLint to use the unstable_native_nodejs_ts_config flag instead, e.g. in your .vscode/settings.json:

{
  "eslint.options": {
    "flags": ["unstable_native_nodejs_ts_config"],
  },
}

Note that between Node v22.10.0 and v22.18.0, you could use the native support for TS files in Node, but it was under Node's --experimental-strip-types flag.

More

See https://eslint.org/docs/developer-guide/shareable-configs for more info on shareable ESLint configs.

Run pnpx @eslint/config-inspector@latest (or npx, bunx etc.) to inspect the rules in your project in order to debug your ESLint config.