search

cyclejs-community / create-cycle-app

Create Cycle.js apps with no build configuration.
ISC License
237 stars 21 forks source link

Porting xstream-boilerplate to create-cycle-app flavor #32

Open nickbalestra opened 8 years ago

nickbalestra commented 8 years ago

As per discussion on https://github.com/cyclejs-community/xstream-boilerplate/issues/233

geovanisouza92 commented 8 years ago

I was thinking, as xstream-boilerplate is, as name suggests, xstream-focussed, this could raise the idea about limiting flavors by its supported stream-libs, otherwise, this will force flavors to support multiple stream libraries.

For the core flavors, this is a must, but for private/personal flavors that could be used by anyone, this could be annoying, considering that, if I prefer to use one library for my projects, this would be the preferred one for all projects.

Widdershin commented 8 years ago

I would also quite like to limit my flavor to xstream only.

nickbalestra commented 8 years ago

Yes, I totally agree. We should have a way to opt-out from streamlib selection, in the case that a flavor only want to support one (it makes a lot of sense indeed for custom flavors), added an ad-hoc issue for that: https://github.com/cyclejs-community/create-cycle-app/issues/33