If when installing a package we found that there is one or more peerDependencies not available inside staticDependencies throw an error.
From #24 :
Installing peerDependencies automatically would be unexpected for people who are used to NPM/Yarn behavior.
From my understanding, it seems like staticDependencies could play well with peerDependencies. For example:
package A specifies peer dependency X
my project installs & requires package A using live-plugin-manager
live-plugin-manager will not install X
(new behavior) if my project does not pass X via staticDependencies, live-plugin-manager will error or warn
(just my 2 cents)
If when installing a package we found that there is one or more
peerDependencies
not available insidestaticDependencies
throw an error.From #24 :