component install --dev

[Mike Nichols]

I have 'local' dependencies which themselves have 'development' dependencies.

I note that when I call 'component install --dev' these are not installed, while the other dependencies _are_ properly installed. Is this by design or an oversight?

[vision media [ Tj Holowaychuk ]]

usually it's not necessary but I can see for an app it might be, usually those deps are just for assertion libs etc

On Mon, Dec 2, 2013 at 12:29 PM, Mike Nichols <nichols...@gmail.com> wrote:

I have 'local' dependencies which themselves have 'development' dependencies.

I note that when I call 'component install --dev' these are not installed, while the other dependencies _are_ properly installed. Is this by design or an oversight?

--
You received this message because you are subscribed to the Google Groups "component" group.
To unsubscribe from this group and stop receiving emails from it, send an email to componentjs...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[Mike Nichols]

Yes this is for an app that has many subcomponents getting aggregated.

I can manually do the install of dev dependencies of course but I guess I expected the flags to be forwarded to subcomponents.

--
You received this message because you are subscribed to a topic in the Google Groups "component" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/componentjs/TftPQ0rgIjs/unsubscribe.
To unsubscribe from this group and all its topics, send an email to componentjs...@googlegroups.com.

[vision media [ Tj Holowaychuk ]]

it's probably reasonable to just traverse for --dev, it'll lead to some extraneous stuff when you're just working on a single component but not a huge deal

[Mike Nichols]

Yeh it looks like the dev option is disregarded inside Package. I can patch that if it makes sense.

[John Syrinek]

Please do! I'm trying to write a build plugin to create a test suite (for MatthewMueller's component-test), but I can't figure out how to include development dependencies in the output to save my life. 

For example, with a setup like this:

/component.json

/traffic-recorder

   /component.json

   /test/feature.js

And a traffic-recorder/component.json containing "tests": ["test/feature.js"] Should output a /build/suite.js to use with `component test browser` when you run: `component build -d -n suite.js -u test-suite.js` Well it does, but the dependencies in /test/feature.js don't resolve.

[Mike Nichols]

Yeh i submitted a PR but they don't seem to get reviewed so I moved on to another tool.

[John Syrinek]

Aw, that's too bad. Well, I know they're cooking up a refactor that should make seriously-custom builds easier to implement. I'm going to try to use the new component-resolve and component-builder2.