You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 27, 2019. It is now read-only.
Repository navigation
This repository was archived by the owner on Mar 27, 2019. It is now read-only.
I presume you mean getting rid of --out for both install, as well as build? Why would you want to remove this, I find it useful, especially for managing components in a larger project. (in terms of directory structure)
I don't have the luxury of working with shallow directory structures at work, so being able to choose my destination (ex: to put it in app/webroot/components for a cakephp project) is much preferred to sticking it in the root, where it really doesn't belong.
I can probably work with that, is there any chance of a less generic name than "components" for the default output dir? node_modules was a good choice for npm, as it seems few would have ever chosen that name first. However, I could easily see wanting to use the name components for myself. Honestly, no decent names come to mind right away, even something like .components or _components would make it clear it's "machine-generated".
--out for both install and build is actually quite useful for writing integrations into existing apps and frameworks. However changing it so --out points to a directory that will then get a ./components directory is a change that wouldn't hurt the integration aspect and keeps the convention.
I'd actually like to see a --in option too which would solve a bunch of headaches that comes with writing flexible integrations.
Activity
dominicbarnes commentedon Mar 27, 2013
I presume you mean getting rid of
--outfor both install, as well as build? Why would you want to remove this, I find it useful, especially for managing components in a larger project. (in terms of directory structure)anthonyshort commentedon Mar 27, 2013
Consistency and predictability would be winning reasons.
dominicbarnes commentedon Mar 27, 2013
I don't have the luxury of working with shallow directory structures at work, so being able to choose my destination (ex: to put it in
app/webroot/componentsfor a cakephp project) is much preferred to sticking it in the root, where it really doesn't belong.yields commentedon Mar 27, 2013
I use
--outfrom time to time, plus like @dominicbarnes said, people might need this if they work with a framework that isn't as flexible as Express.tj commentedon Mar 27, 2013
ah sorry I should have specified for install only
dominicbarnes commentedon Mar 27, 2013
I can probably work with that, is there any chance of a less generic name than "components" for the default output dir? node_modules was a good choice for npm, as it seems few would have ever chosen that name first. However, I could easily see wanting to use the name components for myself. Honestly, no decent names come to mind right away, even something like
.componentsor_componentswould make it clear it's "machine-generated".tj commentedon Mar 27, 2013
I dont think we should go looking for problems, I've never seen anyone use ./components, I dont think that's a big deal
dominicbarnes commentedon Mar 27, 2013
Fair enough
edmellum commentedon May 21, 2013
--outfor both install and build is actually quite useful for writing integrations into existing apps and frameworks. However changing it so--outpoints to a directory that will then get a./componentsdirectory is a change that wouldn't hurt the integration aspect and keeps the convention.I'd actually like to see a
--inoption too which would solve a bunch of headaches that comes with writing flexible integrations.jonathanong commentedon Nov 6, 2013
6e1094a