Conversation
|
Oh, this seems like a good thing. I'll come back to this when I'm done with Hello World Open :) |
|
Hi! Tried to reproduce the issue of "multiple bacons" today, but got stuck with NPM problems. Current status: created https://github.com/raimohanska/bjq-client-test which fails to install because npm insists on installing all teh devDependencies of bacon.jquery. Don't know why. Can't fix right now. Any help appreciated. This seems related to npm/npm#4660 Btw, Getting stuck with NPM problems seems to be a trend for me nowadays :( Update: removed |
|
NPM team has some doubts about usefulness of peerDependencies issues and instead recommend using npm dedupe to avoid multiple copies of a library. The behaviour of peerDependencies has been changed and they are not anymore installed automatically on |
|
I'm not sure if it's more relevant to this issue, or merits its own... But I would suggest exporting the As it stands, it's nearly impossible without modification to use both of, say, Generally speaking, automatically patching existing objects on require/import is a bad idea. These semantically include exported new variables, not extend existing ones. That should be the user's responsibility. |
hi!
peerDependencies help when multiple plugins want to play together. without peerDeps, it's likely each plugin would have it's own
Baconinstance, which is bad.cheers :)