These are chat archives for brunch/brunch

5th
Aug 2016
Colin Bate
@colinbate
Aug 05 2016 03:20
@adrianmc I think the appeal of CRA was that you didn't have to worry about any of that. It was all basically decided for you. If you start having a bunch of options you might as well be using Brunch straight up. Perhaps a better option would be to create a well known set of curated Brunch skeletons for various setups.
Specifically for React
Adrian Li
@adrianmcli
Aug 05 2016 03:30
@colinbate that's a good point. Any ideas for where I should take the CLI tool now then? I still think it has potential for beginners if we can make certain things easier than Brunch.
Colin Bate
@colinbate
Aug 05 2016 03:36
Well you could poke the project name into the package.json file :) and if you want to go down the route of customization then you may want to create an interactive experience which prompts the user for choices if they care
Do you want to use a CSS preprocessor? (If yes prompt with some options, if no, use css-brunch)
I guess you could take the task of plugin discovery and make that easier
And you either have to have a skeleton for each combination or build up the template somewhat dynamically.
Food for thought
Adrian Li
@adrianmcli
Aug 05 2016 03:44
so basically a Yeoman generator
yeah I was about to do the project name > package.json thing. It's one of those minor things that is so small that I procrastinated on haha.
If I were to do it, I'd probably make it a a dynamic thing. It's so simple in Brunch anyway.
Artem Denysov
@denar90
Aug 05 2016 08:57
guys, if someone has a deal with service workers
https://github.com/denar90/sw-precache-brunch
Think it might be usefull.
Colin Bate
@colinbate
Aug 05 2016 16:30
@adrianmc :) Basically. It has been so long since I've used Yeoman that I forgot it did that.
Adrian Li
@adrianmcli
Aug 05 2016 23:42
@colinbate that's not exactly a bad idea. although we really have to think about the most common use cases