Closed stevemao closed 9 years ago
Overrides are only respected on the project level. So, your own bower.json. Inherited overrides is not something we should support, as it could have unintended side-effects, in addition to being completely confusing! If the set up of a project is so tangled, just writing some script tags seems easier.
Let me know if I'm missing something!
Well, in module A it doesn't have a main
entry. In fact, it's not registered on bower. My module B is a wrapper of module A. I have many modules that depends on B and I don't want to write the same overrides
for module A in all these modules.
This looks like a duplicate of #183 (and actually like 5 others). While not something we want to integrate as a rule, someone posted a way to combine bower.json
in that thread as part of a Gulp script that may help you.
:sob: I totally understand. Although my logic would be: if I work on module C I might not even know module A exists and module B should override module A's config for anyone who depends on module B. npm
does it very well and I think bower
is way behind :disappointed:
Why is this issue closed? #183 links to this issue https://github.com/taptapship/wiredep/issues/185 which is also closed.
Is there a solution for inheriting overrides in bower.json?
Assume module A is used by module B and in module B's
bower.json
it hasmodule B is used by module C and module C doesn't override module A in its own
bower.json
When I use wiredep I'm assuming module A's config should be overridden by module B's
bower.json
. If module Coverrides
module A then it should take precedence.Currently only module C's
overrides
is honoured :sob:Thought?