- React 18
- showstopper to upgrade to Chakra UI 2, really unfortunate as v1.x doesn’t receive patch releases anymore (fixes don’t even get merged in v1 branch)
Work is currently ongoing here: #5881 More help is very welcome
- provide a yarn option to create new project with
nmMode: hardlinks-global (or make it the default – see discussion in #5011 and linked articles))
- otherwise, every new project takes up ~0.8 GB more disk space than it would need to
- currently, only workaround is to create it first, then change .yarnrc, then delete node_modules folder, then
yarn install again
For anyone who wants this, please add to the discussion taking place in the PR linked above. My personal guess (have not talked to the rest of the team about this) is that a flag specifically for this setting is not going to be added to yarn create redwood-app. But if a single flag that can be used for “all” advanced configuration someone might want to do, that’s something that might get accepted. Similar to the flag we have on yarn rw dev to pass advanced config on to the underlaying webpack dev server (--forward I think we call it)
- shared i18n setup (same resource files consumable on both api/web-side, api automatically synced with user-setting in web, and api optionally responding in desired language, i.e. via Accept-Header)
Improving the i18n experience is definitely something we want to do. @simoncrypta, @noire.munich and I have a small working-group for this. But it’s been very quiet lately. Unfortunately other things have higher priority for the team right now. There is so much that can be done in this area. Especially around tooling! We’re more than happy for someone from the community to help work on anything i18n related 
- dedicated shared code directory (like we already have that for types)
Thanks for the +1. This is pretty high up on our TODO list already. And your comment validates our decision to put it there
- Performance, Performance, Performance:
- keep an eye bun as a future replacement for node runtime,
ideally enable it as an experimental feature for the hardcore living-on-the-edge folks soon?
Danny, one of the RW core team members, did some experiments a while ago GitHub - dac09/redwood-bun-try: Trying out Bun.sh with Redwood [Not working yet!] It says “not working” in the title, but he did get very far in the end. It was brought up for discussion again as bun recently got a bit of press spotlight. So we’re very much aware and excited about what’s going on Our main focus right now however is on getting Vite to work with Redwood. But we’re also going to invite the author of Bun to talk to us.
- Startup times on yarn dev & test (can’t do much about prisma & storybook i guess except contribute over there),
runtime performance of jest as well
We’re on it! We’re moving to Vite, which will help a lot. After that I’m guessing vitest isn’t far off
- (awesome to have:) pnpm compatibility (#2907 – compare also #5093)
We have a pretty tight relationship with the yarn guys, and now also Nx. So I think we’re staying with yarn for the foreseeable future. But I’m hoping that between all of us we can make something that’s fast enough. I actually watched a yarn conference talk at JSNation in Amsterdam last month and I’m confident in yarn’s speed going forward If you’re interested this talk is 30 minutes well spent! (It’s going to be available to the public tomorrow, right now it’s only open to conference attendees) https://portal.gitnation.org/contents/yarn-4-modern-package-management
- (nice to have:) Preact compatibility (seems like someone already worked on a CLI that would enable that #261) ?
@dom’s input on roadmap prio is always spot-on. His last comment in that issue still stands. That said, we’re all real suckers for community contributions. So if someone shows a lot of dedication over a longer period of time we like to support those individuals and try our best to come up with ways for them to get what they want. So if someone did show us a working implementation of preact inside redwood…
- Provide an immaculate create-redwood-project experience (unmet dependencies warning #2865, be more resilient to different local environments #4885)
I’m 100% on your side here. And not just yarn create redwood-app but also all our generators, setup commands etc. But there’s always the issue of diminishing returns the more you work on this stuff. And prioritizations overall. Should we spend time polishing our CLI tool output, or work on new features/bug fixes. Ideally it’s a bit of both. And again, community involvement goes a long way here
Otherwise, let me reiterate: RedwoodJS is awesome and gets awesome-er by the day! To everyone who built and is building this, give yourself a hug and a hooray at least daily 
Thank you!
- as I only have the time, not too much given my age. My perception of the relative importance of this idea makes me willing to propose to you to just keep your current interest warm enough to care about reading my (yet to be written) ramblings until you can assess whether this idea warrants the creation of a new company (open source, of course).