-
-
Notifications
You must be signed in to change notification settings - Fork 14
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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugins not loaded #16
Comments
I just tested the export plugin with a pre-built binary, so that shouldn't be an issue. What OS are you using? This is the configuration file I have:
Then, the
|
I'm having a similar problem on Mac OS. My plugin-export directory doesn't contain the 'node_modules' directory. Is that something that's created at runtime? Or did I miss a node config step? |
In regards to plugin-export, it requires rtm-cli and rtm-api as peer dependencies. Therefore, I think in order for it to work as it is, it needs to be placed into the rtm-cli directory. Otherwise, those require statements will cause the package to fail and the plugin will not be loaded. I could be wrong but that's the only way I could get it to work. |
This doesn't make sense with how that package is set up because the packages are listed as peer dependencies rather than pure dependencies, so even if you npm install, you won't get those packages in this plugin directory. |
Ubuntu 20.10 : |
I'm running rtm 1.5.1 retrieved from a pre-built binary. I can't get plugins to load. I have been trying both rtm-cli-plugin-example and rtm-plugin-export. I tried manually setting the plugin directory path in the configuration file to no avail. Is this an issue with pre-built binaries or what?
The text was updated successfully, but these errors were encountered: