Rethinking scripts post take-off-training-wheels about create-cycle-app

[jvanbruegge]

I did this here: https://github.com/cyclejs-community/create-cycle-app-flavors/blob/master/packages/cycle-scripts-one-fits-all/scripts/eject.js
eject does not leave any traces

[geovanisouza92]

Yeah, this is something that I thought while working at the first flavor. As I took create-react-app as reference, and it only have a single bloated react-scripts, this is something that I leave to be addressed later.

Each flavor is completely independent, and could evolve freely, so, while maintaining the same contract with other flavors, each script could do what is more suitable for each case.

So, writing configuration files and using npm scripts more extensively, which is something the user that uses take-off-training-wheels probably will do, is not only OK, but desirable in some cases. The idea is that take-off-training-wheels give all the power (and responsibility) to the user.

[nickbalestra]

Totally agree.
On a side note, I see we don't have any labels for issues, perhaps we want to add just a couple of labels for basic things, like nice to have, bug, discussion, ... ?
EDIT: Ok, I see now that we have labels but it seems that only collaborators cat tag issues with them

[geovanisouza92]

Yeah, I just added the default labels, but I'm thinking if makes sense to create more, like @staltz did on cyclejs monorepo... That is a bigger project, with lot contributions caming from everywere, so, I think that was a must.

[nickbalestra]

Nice job with labels, me likes it 💯 !
#19 and #15 address this issue in regards to how we handle .babelrc config files.

TODO: make sure webpack based flavors also properly generates:

• webpack.config.js
• webpack.production.config.js