Skip to content
This repository has been archived by the owner on Mar 27, 2019. It is now read-only.

Follow the chain of paths for remote dependencies #638

Open
timaschew opened this issue Jun 13, 2015 · 4 comments
Open

Follow the chain of paths for remote dependencies #638

timaschew opened this issue Jun 13, 2015 · 4 comments

Comments

@timaschew
Copy link
Member

I think it's really annoying to touch all the locals if you want to upgrade a dependency which is used my almost all of your locals, here is an real world (open source) example:
DemocracyOS/democracyos#927

at our company we have the same issue

@jonathanong was it by design to prohibit defining remote dependencies at the root level and use them on local level?

I'm 👍 for changing this, actually like #337 but for remotes

@jonathanong
Copy link
Contributor

i don't remember. probably

@19h
Copy link

19h commented Jun 14, 2015

+1 for changing. Even if it was an artifact of design, the behavior fired back pretty hard.

@micky2be
Copy link
Contributor

For our projects, that are still using Component, we are not writing component.json files anymore.
We generate them.
Please take a look at https://github.com/Wizcorp/component-extractor
(PS: not tested with Component v1)

@timaschew
Copy link
Member Author

we're generating them as well, but we still have our Manifest files for each local.

we want to drop component now in our company, we have to many issues.
we're switching to webpack now, see #639

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants