How to resolve local plugin or rule using old rc config file format?

[pawelgur]

Eslint v8.50, Windows, using eslintrc.js config format

I am following custom rule tutorial to create custom rule (which requires a plugin from what I understand), but I'm not able import my local plugin.

Tried following:

• provide object as per tutorial - object not supported, string required
• try providing path to my plugin - getting Plugins array cannot includes file paths error
• create eslint-plugin-example dir with index.js in root of the project (next to eslintrc.js) and provide "eslint-plugin-example" in plugins config - config not found

The only way I managed to make it work is to do npm i ./eslint-plugin-example --save-dev which created symlink in node_modules which looks way too complicated for such simple thing as including local rule/plugin.

Is there any other way to achieve it? (without migrating to flat config)

[mdjermanovic]

The only way I managed to make it work is to do npm i ./eslint-plugin-example --save-dev which created symlink in node_modules which looks way too complicated for such simple thing as including local rule/plugin.

We're doing the same in the eslint project:

eslint/package.json

Line 125 in 0f5df50

"eslint-plugin-internal-rules": "file:tools/internal-rules",

It indeed seems too complicated, but it's probably the best way to include local rules when using the eslintrc config format. The new flat config format is designed to make including local rules much easier.