Closed wryk closed 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.
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.
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.
component_components
:trollface:
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
+1 to disliking node_modules
i think just letting people supply a components dir would be fine (and easy) later on
yeah just wanna do it with a .componentrc
file or something. setting --out
in every command would be super annoying.
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)
components
is a good name butcomponent
is a really too generic name. what about prefix/change it ?npm doesn't use
modules
butnode_modules
(as exemple)