componentjs / component

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

change deps install folder name to a less generic name ? #544

Closed wryk closed 10 years ago

wryk commented 10 years ago

components is a good name but component is a really too generic name. what about prefix/change it ?

npm doesn't use modules but node_modules (as exemple)

dominicbarnes commented 10 years ago

Yeah, I feel the same way since I've always wanted to use components to hold my own local components, (ones that don't belong in separate repos) but I have to come up with other weird names instead.

jonathanong commented 10 years ago

if we add the "source" i.e. github.com to each component, we could probably just store it globally somewhere instead. no more components/ folder, and installs would only happen in the background.

dominicbarnes commented 10 years ago

I don't think we need to change to something like that necessarilly, even just renaming to use component_dependencies or something less generic would be more than enough for me.

cristiandouce commented 10 years ago

component_components :trollface:

tj commented 10 years ago

I wish node didn't use node_modules haha, it's super ugly, but irrelevant either way really, we can change it down the road if we need to but there's no reason to

ianstormtaylor commented 10 years ago

+1 to disliking node_modules

i think just letting people supply a components dir would be fine (and easy) later on

jonathanong commented 10 years ago

yeah just wanna do it with a .componentrc file or something. setting --out in every command would be super annoying.

ianstormtaylor commented 10 years ago

it should be first in the the JS api, then in --out then in .componentrc. but i dont think any build-level settings should ever be settable only in .componentrc (only user level settings)