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

@grafana/eslint-plugin-plugins

v0.6.3

Published

An ESlint plugin with Grafana plugin specific rules

Readme

eslint-plugin-plugins

eslint-plugin-plugins contains an ESLint rule that checks whether imports from any of the Grafana packages (@grafana/ui, @grafana/data and @grafana/runtime) from within a Grafana plugin source code exist in all the Grafana runtimes that the plugin is supposed to support (as specified in the grafanaDependency in plugin.json).

How to install

npm install @grafana/eslint-plugin-plugins --save-dev

Configure

To determine the plugin's minimum supported Grafana version, the linter checks the grafanaDependency property in the plugin's plugin.json. By default, it looks for plugin.json in the <projectRoot>/src folder. If the file is located elsewhere or if you're using a monorepo with multiple plugins that have different grafanaDependency values, you can specify minGrafanaVersion directly in the ESLint configuration.

Flat config

const grafanaPlugins = require('@grafana/eslint-plugin-plugins');

module.exports = [
  // ...other configs
  {
    files: ['src/**/*.{ts,tsx}'],
    plugins: { '@grafana/plugins': grafanaPlugins },
    rules: {
      '@grafana/plugins/import-is-compatible': [
        'warn',
        // optionally pass the minimum supported version
        // { minGrafanaVersion: '10.3.0' },
      ],
    },
  },
];

Legacy config

Add the following to your Grafana plugin's .eslintrc:

{
  ...
  "plugins": ["@grafana/eslint-plugin-plugins"],
  "rules": {
    "@grafana/plugins/import-is-compatible": [
      "warn"
      // optionally pass the minimum supported version
      // { minGrafanaVersion: '10.3.0' },
    ]
  }
}

Lint

npm run lint

If your IDE has an ESlint integration that displays errors and warning in the source code, you may need to restart the ESlint server. In VSCode you can run the task ESLint: Restart ESlint Server.

How it works

When the ESlint plugin is loaded the first time, it will check the grafanaDependency property in the Grafana plugin's plugin.json file to find the min supported Grafana version. If for example the grafanaDependency is set to >=10.0.2, @grafana/[email protected], @grafana/[email protected] and @grafana/[email protected] will be downloaded to a temp directory on the host machine. It will then check that imports from any of these packages within the plugin source code has a corresponding export in version 10.0.2 of these packages. If not, a problem is reported. It currently ignores member that don't exist at runtime such as types, interfaces and enums.

The import-is-compatible rule only checks backwards compatibility. If a member has been removed in an upcoming release of the Grafana packages, it will not be detected.

Contributing

Refer to the contributing guidelines.

Rules

| Name          | Description | | :------------------- | :------------------------------------------------------------------------------------------------------------------- | | import-is-compatible | A rule that checks if the imported member is available in all Grafana runtime environments that the plugin supports. |