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

remove component-install(1) --out #299

Closed

Description

@tj

not really useful

Activity

  1. dominicbarnes commented on Mar 27, 2013

    @dominicbarnes
    Contributor

    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)

  2. anthonyshort commented on Mar 27, 2013

    @anthonyshort
    Contributor

    Consistency and predictability would be winning reasons.

  3. dominicbarnes commented on Mar 27, 2013

    @dominicbarnes
    Contributor

    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.

  4. yields commented on Mar 27, 2013

    @yields
    Contributor

    I use --out from time to time, plus like @dominicbarnes said, people might need this if they work with a framework that isn't as flexible as Express.

  5. tj commented on Mar 27, 2013

    @tj
    ContributorAuthor

    ah sorry I should have specified for install only

  6. dominicbarnes commented on Mar 27, 2013

    @dominicbarnes
    Contributor

    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".

  7. tj commented on Mar 27, 2013

    @tj
    ContributorAuthor

    I dont think we should go looking for problems, I've never seen anyone use ./components, I dont think that's a big deal

  8. dominicbarnes commented on Mar 27, 2013

    @dominicbarnes
    Contributor

    Fair enough

  9. edmellum commented on May 21, 2013

    @edmellum

    --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.

  10. jonathanong commented on Nov 6, 2013

    @jonathanong
    Contributor
  11. removed this from the 1.0.0 milestone on Mar 29, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions