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.
What was the reasoning behind removing --out apart from "not really useful"? For some of us, it clearly is (see #389 and #299), and that includes myself.
My projects are limited to one version of a component, and I use multiple build phases to create a multi-injection single page app. I like storing the 3rd party components for those builds in one common folder.
For my projects, that keeps 3rd party deps nicely in one place, which is a bit more manageable. The removal of --out made this pattern impossible. If there really is a compelling reason to not have --out, can you please explain it to me?
I think component has reached a level of popularity where the removal or change of an API or command line argument, no matter how small, can have a major impact on how people use it. I hope we can work towards stability and consensus where possible. Although I will readily admit that as far as consensus goes, I missed out on #299 and that was totally my bad.
Right now, I add everything that got built in page 1 to the ignorelist of page 2, etc. The order in which I load pages is deterministic, so that works really well for me.
We use --out for building components in the Titanium/Alloy mobile framework as a plugin. We can do it a different way, but would rather keep it the way it is.
imo it sounds like the real issue is that component doesn't have a good bundling framework, not that you actually care about --out.
i'm +1 to removing options from the CLI for simplicity. however, you should be able to specify your --out directory using the JS API as component becomes more lib-ish. component(1) should be accommodating small web components, and complicated apps should be using the JS API.
Until the new version of component and component builder are out and useable (to me, nothing using generators is usable until Node 0.12 is out and ideally has the generators harmony flag on by default), reintroducing --out will do the trick for me. I would love to use an API instead if I could.
Please keep in mind that solutions for tomorrow are great discussion material, but many of us need solutions yesterday.
i'm going to put this in, but i want it to be a hidden feature. i.e. it won't display in component install -h and stuff. trying to make the help commands and simple and short as possible.
Activity
remove component-install(1) --out flag. Closes #389
timoxley commentedon Jan 6, 2014
Perhaps just rename the
componentsfolder at the end of your build?jonathanong commentedon Jan 6, 2014
how are you splitting up builds?
you can use something like https://github.com/yields/component-bundle, though i foresee a billion different ways and edge cases with custom builds and i'm not sure how it handles those.
ronkorving commentedon Jan 7, 2014
Right now, I add everything that got built in page 1 to the ignorelist of page 2, etc. The order in which I load pages is deterministic, so that works really well for me.
stephenmathieson commentedon Jan 11, 2014
Can you do something like this (like @timoxley suggested)?
btknorr commentedon Jan 11, 2014
+1
We use --out for building components in the Titanium/Alloy mobile framework as a plugin. We can do it a different way, but would rather keep it the way it is.
ronkorving commentedon Jan 14, 2014
@stephenmathieson Of course hacks are possible. But this used to work, and it wasn't hacky, was it?
jonathanong commentedon Feb 14, 2014
imo it sounds like the real issue is that component doesn't have a good bundling framework, not that you actually care about
--out.i'm +1 to removing options from the CLI for simplicity. however, you should be able to specify your
--outdirectory using the JS API as component becomes more lib-ish.component(1)should be accommodating small web components, and complicated apps should be using the JS API.ronkorving commentedon Feb 15, 2014
Until the new version of component and component builder are out and useable (to me, nothing using generators is usable until Node 0.12 is out and ideally has the generators harmony flag on by default), reintroducing
--outwill do the trick for me. I would love to use an API instead if I could.Please keep in mind that solutions for tomorrow are great discussion material, but many of us need solutions yesterday.
jonathanong commentedon Mar 31, 2014
i'm going to put this in, but i want it to be a hidden feature. i.e. it won't display in
component install -hand stuff. trying to make the help commands and simple and short as possible.jonathanong commentedon Apr 2, 2014
anyone know how to make an option in
commander.jswithout having it print inhelp?jonathanong commentedon Apr 5, 2014
this is going ot be annoying because you would basically have to do
--outin every CLI command. let's discuss this in #517