Can an MIT-licensed project include GPL-released dependencies?

Question

Licenses for software and other works

We are writing a framework for node.js, one of the components is managing application microservices, there are thoughts not to fence our bicycles, but to use the pm2 api.
But pm2 is released under the GPL license, and we plan to release our framework under MIT (we also consider the latest version of BSD as an option)
Could there be legal problems from such a decision? Or is it better to immediately abandon it and write your own bike?

Answer 1

Comparison of licenses
As far as I understand, including a link in the pm2 documentation with an example of how to use it will not violate the license, while this package will not be included in your software as a dependency. Judging by the examples, it still needs to be installed globally, while your framework (purely in theory) will become a plug-in part of the application.
If pm2 is just a part of your application, you will have to distribute it under the terms of the GPL.
For process start systems, see supervisord

Answer 2

> considering the latest version of BSD as an option
What is "the latest version of BSD"? Well, that is, I understand that it should be 4.4BSD :-). But you, of course, one of the BSD licenses . So they do not have any "versions", and even the names are conditional, because they were written for purely internal use.
And although you didn't ask, I can't help but notice that your attraction to sloppy licenses is incomprehensible to me.
> Can there be legal problems from such a decision?
No, there are definitely no legal problems and conflicts of conditions here. Both so-called. "MIT licenses" - Expat and X11, are compatible with all versions of the GNU GPL, that is, under their terms, parts can be linked into one program arbitrarily deep.
Another thing is that there may be conflicts with your interests, but I don’t know anything about them.