Paul Grau

I've been thinking about this for a while. I have been using the Webpack approach for 2 months now in a project, so I have a good idea of what...

Yes, I think that's a good idea. How should be move forward? We could start collecting information on what the other frameworks do (with pros and cons) and define our...

I also saw that blog post. It's a very similar problem indeed. They have one `create-react-app` command to setup the project, and some helper tools in `react-scripts`, but without any...

The first two should be pretty easy to do with just Webpack (multiple entry points and chunk splitting), although I'm not sure how you can target two architectures (browser and...

Seconding this. Especially for library modules (e.g. component libraries) it seems unnecessary to bundle everything into one file. I wonder what the use case for the current implementation of `bundle:...

Hi @evanw, is there anything we can do to help with this? Another use case is building design systems with Vanilla Extract. Currently, all my CSS is bundled into one...

@hyrious Thanks for your reply. I don't want to apply vanilla-extract to third-party libraries. I want my library to build all its ".css.ts" files to corresponding js and css, but...

I'd be happy to collaborate more actively. How about establishing another communication channel like a Telegram or Discord group chat or something like that? Feel free to DM me!

Great to hear. My two main issues have also been: 1. **Generalizing to other kinds of trees** - Instead of `path` and `name`, many trees just have `id`, `children` and...

> > I can totally imagine a package like `react-aspen-select`, that exports hooks like `useTreeSelect(tree: Tree)`. Or imagine `react-aspen-search` with `useTreeSearch(tree: Tree, matchFn: ((node: TreeNode) => number)))`. And everything just...