-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Install PM2 module from Github's non-master branch #2809
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
Labels
Comments
We should add something here to trim the name |
@ma-zal looks like a quick fix, feel free to open a PR on this |
ma-zal
added a commit
to ma-zal/pm2
that referenced
this issue
Apr 19, 2017
…as Github repository with non-master branch. Fixed the broken upgrade of modules specified by Github source (old version was not been removed, therefore two instances existed in memory after upgrade).
inerc
pushed a commit
to inerc/pm2
that referenced
this issue
Feb 11, 2020
…as Github repository with non-master branch. Fixed the broken upgrade of modules specified by Github source (old version was not been removed, therefore two instances existed in memory after upgrade). (Unitech#2840)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Installation of PM2 module from GitHub's non-master branch is failing.
Problem is, that PM2 is expecting, that final NPM module directory will be
module#branchname
, but real is without#branchname
of course. So the PM2 finally stores the wrong name tomodule_conf.json
->module-db
object.Example:
pm2 install ma-zal/pm2-slack#own-customization
The text was updated successfully, but these errors were encountered: