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

@agrovista/eslint-config

v1.34.0

Published

An Agrovista ESLint plugin which provides lint rules for TypeScript codebases.

Readme

@agrovista/eslint-config

An Agrovista ESLint plugin which provides lint rules for TypeScript codebases.


Setup

1) Install this package (and peer dependencies)

npm install -D @agrovista/eslint-config

The peerDependencies in this repository's package.json should be automatically installed if your npm version is up to date. If you are not using NPM, consult your package manager's documentation or install into your repository as devDependencies:

npm install -D @typescript-eslint/eslint-plugin @typescript-eslint/parser

2) Configure ESLint

Within your ESLint config file:

Note: Simply extending '@agrovista' is supported, however, it is much clearer to be explicit with a scoped eslint-config.

extends: [
+  "@agrovista/eslint-config"
]

For React codebases, instead extend:

extends: [
+  "@agrovista/eslint-config/react"
]

3) Configure the ESLint TypeScript parser

This config requires knowledge of your TypeScript config.

In your ESLint config, set parserOptions.project to the path of your tsconfig.json.

For example:

{
  extends: [
    "@agrovista/eslint-config"
  ],
+ parserOptions: {
+   project: "./tsconfig.json"
+ }
}

4) Run ESLint

Open a terminal to the root of your project, and run the following command, changing the path to your code location, for example:

npx eslint . --ext .ts
npx eslint 'resources/js/**/*.{ts,tsx}'
# etc

ESLint will lint all found files, and output results to your terminal.

Examples of package.json lint scripts are below, which can then be ran inside a CI pipeline against pull-requests:

{
  "scripts": {
    "lint": "tsc --noEmit && eslint 'resources/js/**/*.{ts,tsx}' && eslint 'tests/cypress/**/*.cy.ts'"
    // or
    "lint": "eslint . --ext .ts",
  },
}

These package.json scripts can be ran with:

npm run lint

5) Lint within your editor

You can also get results in realtime inside most IDEs via a plugin, in addition to automatically fixing fixable issues on-save.

For vscode, it's recommended to use: dbaeumer.vscode-eslint in combination with the below settings, which can be placed within a repository .vscode/settings.json file, for all maintainers to use.

{
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "explicit"
  },
  "eslint.validate": ["javascript", "typescript"]
}

FAQ

I get this error when running ESLint: "The file must be included in at least one of the projects provided"

If the file should not be linted:

A file can be excluded from linting by either method:

If the file should be linted:

This means you are attempting to lint a file that tsconfig.json doesn't include.

The simplest solution is to include it in the "include" array.

A slightly more complex common fix is to create a tsconfig.eslint.json file, which extends your tsconfig.json file and includes all files you are linting.

{
  "extends": "./tsconfig.json",
  "include": ["src/**/*.ts", "src/**/*.js", "test/**/*.ts"]
}

Update your ESLint config file:

parserOptions: {
-  project: "./tsconfig.json"
+  project: "./tsconfig.eslint.json"
}