A few questions on project development about create-cycle-app HOT 4 CLOSED

from create-cycle-app.

@geovanisouza92 @SteveALee I think this issue: #27 could be somehow related. I like the idea too. Let's bring the conversation there

from create-cycle-app.

hehe you very welcome!

1. Yes it could (only for the core-flavors). How offten it will depends, we have no rules in this regard yet. For custom flavors this is will be done by the owner/maintainers.

2. It depends, if you don't need much changes from what the core-flavors offer you, then is just fine not to eject, especially cause this could result in 'free' updates coming down for you (^ point 1). You could decide to use it as a boilerplate starter if that is what you looking for, that's also super fine, and you could even create your own flavor and maintain that so that once you update it all your app relying on it could take advantage of that (again, ^ point 1 ).

3. We don't handle that within core flavor yet, and agree that adding some CSS support will be a good idea, can you open a separate issue for this point so that we can bring the discussion on how we might wan to implement this in a separate thread?

Having said that, I will say that in general core-flavor aim to be very simple, with the goal to allow to mix and match different stream libraries, and language/bundlers for the main purpose of easing people to getting started with cycle.js, everything more complex or specific should probably be better developed as a custom flavor.

Hope this answer your question

from create-cycle-app.

yes they helped thanks

I'll make a minor PR to readme

I agree the main use case should be easy bootstrap. But also imagining a more advanced workflow like this:

Use existing flavour -> [opt eject] -> modify config or flavour -> create custom flavour -> publish

And was trying to figure how that might work.

from create-cycle-app.