Two plugins not working after Rider update, possibly new ones? ESLint & JSHint
Hi everyone,
I just updated to Rider 2026.2.0.2 and when I started it afterwards, it greeted me with plugins that don't work because other plugins they depend on are deactivated. Both the plugins that don't work and those that are dependencies are from the JavaScript Frameworks and Tools category, in which I had disabled all plugins. My guess is that ESLint and JSHint, the two plugins with missing dependencies, are new and have been activated automatically. Is this the case? If so, greeting me with broken plugins seems undesirable to me.
In this specific case it would have been ideal if Rider had tracked that I deactivated the entire category and hence not activated new plugins in this category. In general, I'd like to be in control of new plugins, deciding myself if they should be activated. I've noticed undesired behaviour regarding AI plugins before and I guess that it's related. I'm partly guessing here though, so I'd like to learn more about what happens when new plugins are added to Rider with updates, and I'd also like to learn what might have caused JSHint and ESLint to appear in a broken state.
Thank you very much!
Please sign in to leave a comment.
ESLint and JSHint were split into separate bundled plugins in Rider 2026.2. They still depend on the JavaScript and TypeScript plugin. An early 2026.2 build could leave them enabled while that dependency was disabled, which produced the state you saw.
Update Rider to the latest available 2026.2 build. The later builds correct the dependency handling.
Until then, keep the JavaScript and TypeScript plugin enabled if you use ESLint or JSHint. If you want all JavaScript tooling disabled, disable ESLint and JSHint as well.
Thank you! I don't need either, so I just disabled them. Good to know that this was an issue that was already handled.