ESLint CLI gives no information about exceptions thrown on plugin load

What version of ESLint are you using? 2.13.1 (with eslint-plugin-react 6.0.0)

What parser (default, Babel-ESLint, etc.) are you using? Default (this shouldn’t matter)

Please show your full configuration:

{
    "plugins": ["react"]
}

What did you do? Please include the actual source code causing the issue.

$ eslint --debug someFile.js

What did you expect to happen? Plugin loads successfully, or if it fails to load, the exception thrown should show up in eslint --debug.

What actually happened? Please include the actual, raw output from ESLint.

eslint:cli Running on files +0ms
eslint:ignored-paths Looking for ignore file in /path/to/root +88ms
eslint:ignored-paths Could not find ignore file in cwd +3ms
eslint:glob-util Creating list of files to process. +0ms
eslint:cli-engine Processing /path/to/js/file +23ms
eslint:cli-engine Linting /path/to/js/file +2ms
eslint:config Constructing config for /path/to/js/file +1ms
eslint:config Using .eslintrc and package.json files +0ms
eslint:config Loading /.eslintrc +3ms
eslint:config-file Loading config file: /.eslintrc +1ms
eslint:plugins Failed to load plugin eslint-plugin-react. Proceeding without it. +212ms

With no indication of why the plugin failed to load. In this case, it wasn’t due to the plugin not being available, but rather the require() failed due to something wrong with the plugin’s main file.

[platinumazure]

TSC Summary: This issue is accepted, but I wanted to see if this merited being included on the core roadmap project.

TSC Question: Should this issue be added to the core roadmap project?

[platinumazure]

In addition, I’m wondering if we want to try to detect if the plugin existed (but threw an exception on require) vs the plugin didn’t exist, and modify the pretty message template accordingly.