i know, i just don’t find it helpful to make the distinction between optional and not-optional peer dependencies, so I don’t. To me this is a typical example of some dev bubble introducing a concept that I didn’t need. If it’s a peer dependency, your/my package doesn’t need it, to work. Why add optional on top? Peers were supposed to define common dependencies with other packages. A depends on X, B depends on X, A is a peer to B. To my package, it’s absolutely irrelevant, if it’s peer is optional or not.
↧