New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Getting a failed to load plugin
error when running tester locally
#382
Comments
Thanks for your interest @sjarva! This tool can indeed be used for local eslint rule development. I used it myself when building new rules to Before debugging this further I just want to ensure you have linked the local project in your package manager - this is something ESLint requires when it is resolving the plugins. In practice this means that you'll have to run Here is how |
That did the trick! Thanks for the quick reply @AriPerkkio 馃 |
Perfect! Make sure to check the How and when to use section for local development instructions. Now that I'm looking at these instructions, I think this package linking should be added here. eslint-remote-tester/README.md Lines 140 to 145 in 38c0b03
This is a good chance for a documentation PR if you are interested. 馃憤 |
Yes, I was just looking at them and came to the same conclusion. I'll make a PR about this tomorrow 馃摑 |
First of all, thanks for developing this kind of tool, it's really essential in eslint plugin development 馃ぉ 馃檹
I'm trying to run this locally after modifying an existing rule for an existing plugin (
eslint-plugin-react
), but get the following error:I have a
eslint-remote-tester.config.js
with contents copied from React example config, but the rule name changed to the rule I want to test.Any ideas why I'm getting this error?
The text was updated successfully, but these errors were encountered: