Unable to load plugins
See original GitHub issueUsing jsdoc-parse@1.2.7
My jsdoc.conf.js:
{
  "plugins": ["node_modules/jsdoc-babel"],
  "babel": {
    "extensions": ["js", "es6", "jsx"],
    "presets": ["es2015", "stage-1", "react"],
    "plugins": ["transform-flow-strip-types", "babel-plugin-transform-decorators-legacy"]
  }
}
When running
jsdoc-parse -f src/index.js --conf jsdoc.conf.json
got error message
JSDOC_ERROR: ERROR: Unable to find the plugin "node_modules/jsdoc-babel"
jsdoc@3.4.0 works ok.
The same error with other jsdoc plugins (tested jsdoc-strip-async-await), so I beleive it’s plugin-unrelated.
Issue Analytics
- State:
 - Created 7 years ago
 - Comments:5 (3 by maintainers)
 
Top Results From Across the Web
Chrome error couldn't load plugin - Error Solutions
“Chrome error couldn't load plugin” may occur due to a bad Google Chrome cache, which may interfere with plugins. Clearing the cache may...
Read more >How to Fix the "Couldn't load plugin" Error on Chrome?
Sometimes this "Couldn't load plugin" error can appear because of the corrupted system files, and to fix this issue, you need to run...
Read more >How To Fix Chrome “Couldn't Load Plugin” Error [2022]
Fix #1: Update the Google Chrome browser. ... An outdated Chrome browser can cause a lot of issues including the “Couldn't load plugin”...
Read more >Failed to load plugin from - how to solve related issues - Opster
Managing permission issues during and after plugin installation is the most common problem. · In the case of DEB or RPM package installation,...
Read more >Couldn't load the plugin on Chrome: 2 quick ways to fix this error
Go to the Enhanced Mitigation Toolkit directory and run the EMT application. · When the EMT app opens, click the Configure apps button....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Thanks, it has fixed my issue.
i’ve traced this to a regression in jsdoc3, introduced by this commit… jsdoc2md does not use jsdoc3@3.4.0, it uses a fork which tracks the
masterbranch of jsdoc3.This is fixed and released in v3.5.6 of jsdoc-75lb… please reinstall jsdoc2md and try again.