search

componentjs / component

frontend package manager and build tool for modular web applications
https://github.com/componentjs/guide
MIT License
4.55k stars 306 forks source link

Follow the chain of paths for remote dependencies #638

Open timaschew opened 9 years ago

timaschew commented 9 years ago

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: https://github.com/DemocracyOS/app/issues/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 :+1: for changing this, actually like https://github.com/componentjs/component/pull/337 but for remotes

jonathanong commented 9 years ago

i don't remember. probably

19h commented 9 years ago

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

micky2be commented 9 years ago

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 commented 9 years ago

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 https://github.com/componentjs/component/issues/639