Handling plugin dependencies


#1

What is the recommended way of handling plugin depencencies? So far, I’ve put run-time dependencies in my plugin. This creates some problems when these dependencies get upgraded in a consumer project - I have to release another version just to avoid forks. Would it be better to have them as development dependencies and let a client install them explicitly?


#2

i most certainly would do so now. if listed as peer dependencies one still gets the information which version the plugin expects