v1 Roadmap

[dai-shi]

Here are tasks that I would like to finish before v1.

Previous Versions

-v0.14.0

• Server bundling Support server bundling with vite #21
• New API as middleware Expose as middleware #23
• RSC-only SSR (or opt-in SSR) ssr middleware #66
• Improve HTTP errors (404 instead of 500, especially with router) feat: support 404 for rsc #76
• Support interacting with server (req and res) feat: server context #86
• CSS Modules on server fix: partially for css modules #98 Support CSS Modules #105
• Server bundling issues not compatible with prisma #79

v0.15.0

• fix waku/router unexpected cached result #85 Ssr doesn't work if use getContext in entries.ts 's defineRouter/getComponent #104
• Revisit entries.ts API (requires to revisit waku/router) how to get current pathname in server component? #84
• Revisit mutate() api and maybe serve() api Redesign serve() and mutate() apis, and maybe getEntry too #119

v0.16.0

• waku/router [slug] support feat(router): slug support #133
• SWR build error in SWR 2.2.0 #96

v0.17.0

• Reconsider SSR (give up RSC-only SSR and go with full SSR) breaking: switch to full SSR from RSC-only SSR #147
• Node 20 fix: support node 20 #159
• Refactor rscPrefix config to rscPath rename rscPrefix to rscPath #160

v0.18.0

• Support running on the edge
• Vite 5 feat: use vite5 #207

v0.18.1

• css support feat: css support #240
• deploy support fix: vercel output #263 feat: output cloudflare #267 feat: output deno #271

v0.19.0

• Utilize hoistable elements breaking: no index html #289
• Renew waku/router API re-design waku/router #246
• Environment variables environment variables improvement #292
• Improve Vercel deployment
• Config file waku.config.ts support in cli.ts feat: waku/config #368
• Improve CLI and templates

v0.19.1

• fix issues with deployment
  fix: improve building for deployment #395
  fix: add already created index.html in the list #398
• fix style HMR
  fix: hmr plugin with async component (with ssr, dev only) #411
  DEV: loading indicator to mitigate FOUC #414

v0.19.2

• Dev improvement
  fix: FOUC #427
  CSS modules broken in DEV after #427 #439
  Cannot import commonjs module from server component #110
• More support for deployments
  feat: netlify deploy #422
  feat: output AWS Lambda handler #419
• router improvement
  router: do not refetch on popstate #424

v0.19.3

• ssr build / bundling wrong export from packages.json #448
• Support hot reload for server components #113
• Better Netlify support auto detect netlify build #465

v0.19.4

• feat: preserve module structure on server #493
• Support customizing 404 support custom 404 (static html only) #497
• build / image import broken #498
• useLocation not work Error: Missing Router #417
• feat: private dir #514
• Can not build with swr #418

v0.20.0

• support middleware and custom routes #513
• Enable SSR by default (no --with-ssr option)
• getContext from waku/server
• Conditional SSR
  feat: conditional ssr (minimal API only) #534
  Experimental support for disabling SSR for waku/router #569
• File-based router
  feat: fs-router #572
  fix: fs-router for non-Node envs #575
• Managed mode (no main.tsx and entries.tsx)
  feat: managed mode #580
• new waku/router apis
  feat(router): unstable_redirect #593
  feat(router): useRouter #613

v0.20.1

• Support omitting file extensions in import statements
  feat: support omitting file extensions in import statements #629
• Support .js and .jsx extensions
  feat: support js/jsx extensions (minimal api only) #633
  feat(router): support js/jsx extensions #636
• Support trailing slash with static sites (SSG)
  fix/router: handle trailing slash #637
• Bug fixes
  [BUG] Context Provider invalid value #631
  Fix broken 04_cssmodules example #651
  Suspense doesn't work in layout with css modules (DEV-only) #639
  ssr build / use client / broken global CSS import from package #452

v0.20.2

• Improvements
  SSG: support wildcards in static paths #666
  SSG: high volume performance #668
  feat(waku/router): prefetch on view (<Link />) #672
  fix: private dir hmr #675
  feat: expose internals #694
  SSG: partial builds #689
  fix(client): enable to render previous element in slot (experimental) #696
• Bug fixes
  fix(router): push state on redirect #673
  fix: non js assets path should add config.basePath to be relative to root path #697
  fix(waku/router): regex in file replacement to correctly handle all matches (fs-router) #678
  Avoid exposing configs that are not configurable #682
  fix: use both typescript and ecmascript prasers #687

v0.21.0

• Transform files on the server (DEV)
  feat: eliminate worker thread for react-server #762
  fix: avoid patching global webpack require #707
• Support importing server files directly from client files
  refactor waku/client (technically breaking) #708
  feat: use server action from client modules #714
• Support server actions in server components
  feat: server actions in server components #729
  fix: edge case when rsa depends on another rsa #785
• Router improvements
  breaking(router): string query #799
  feat: expose hash from useRouter #746
• Cloudflare Pages support
  feat: cloudflare pages adapter, alternate implementation #795
• Support customizing html attrs & head with SSR
  breaking: render full <html> instead of inside <body> #825
• DEV improvements
  fix(dev-server): initial modules recursive resolution and module loading in ssr #833

v0.21.1

• Minor improvements
  downgrade swc/core #848
  fix(build): do not remove index.html when buildConfig is empty #851
  [fix] File upload #850
  experimental: expose hono context #852

v0.21.2

• Improve build system (mostly internally, plugin system)
  feat(build): introduce buildData in platformObject #860
  feat: deploy plugins #866
• Bug fixes
  fix(dev): import local node_modules with SSR #864
  fix: cloudflare routing 404 #870

v0.21.3

• Improve build system (mostly internally, plugin system)
  fix(deploy): move isNodeCompatible to deploy plugins #876
  refactor(deploy): vercel serve and constants #877
  refactor(deploy): netlify serve #878
  refactor(deploy): cloudflare serve #879
  refactor(deploy): deno serve #880
  refactor(deploy): partykit serve #881
  refactor(deploy): aws-lambda serve #882
• Improve router
  feat: infer types for waku router #854
  feat: entries gen for fs router projects #886
  404 and broken link handling #895
  feat(router): props inferred for page components #917
• Misc
  prefer getHonoContext to hono/context-storage #914
  feat(create-waku): install dependencies automatically when creating a new waku project #808

v0.21.4

• Internal re-architecture (customizable entries with router)
  experimental GET support #947
  redesign rscPath encoding #951
  new defineEntries (and context middleware) #961
• Router improvement
  feat: allow optionally controlled root #952
  new defineRouter #949
  feat: regenerate fs-router types #966

v0.21.5

• Bug fixes
  fix(rsc-transform): fix server function error in SSR #979
  fix(plugin/fs-router-typegen): use swc.parseSync instead of parseFileSync #980

v0.21.6

• Internal re-architecture (continued)
  fix: new_defineRouter #991
  feat: new create pages to use new defineRouter #963
• Cloudflare support improvement
  Switch from Cloudflare Pages to Workers with Static Assets #989

v0.21.7

• Internal re-architecture (continued)
  refactor: use new_createPages in examples #997
• Router improvement
  feat: pageprops type improvements with docs for use #1001
• Cloud plugin improvement
  feat: honoEnhancer for Vercel, Deno and Netlify #941
• Bug fixes
  fix: improve resolveClient for DEV #998
  fix(dev): fix hot-reload with e2e test #1021

v0.21.8

• Internal re-architecture (continued)
  refactor: fs-router to use new_createPages & fix staticPaths #1003
• DEV improvement
  fix: improve client HMR #1029
  fix(hmr): file add and delete runtime error with fs-router #1042
• React 19
  react 19 stable #1044

v0.21.9

• Support progressive enhancement for forms
  feat: progressive enhancement for form actions #1070
• Internal re-architecture (continued)
  refactor unstable_defineRouter with new_defineEntries #1043
• Bug fixes
  fix(dev): hot-reload #1061
  fix(cloudflare): update default generated wrangler.toml #1059
  fix(create-pages): nested layouts missing #1063
  fix(dev): waku package not found #1064
  fix(dev): avoid configFile: false in vite config #1036
  fix(use-router): router.push bug #1067
  fix(router): improve function returning components with skip #1072

v0.21.10

• Bug fixes
  fix(build): avoid externalizing waku/middleware/context #1076
  fix(create-pages): layouts missing with more nesting #1077
  fix(create-pages): dynamic wildcard pages runtime errored #1080
  fix(handler): return promise of stream with allReady #1083

v0.21.11

• Internal re-architecture (continued)
  feat: migrate to vite v6 #1012
  breaking(minimal): handleBuild API for build #1093
• Bug fixes
  chore(e2e): add website to smoke tests & fix dev server error #1095
• Minor improvements
  fix(html): overriding default head #1088

v0.21.12

• Internal re-architecture (continued)
  feat(define-router): handleApi #1099
  feat(create-pages): api handling #1108
• Compiler support
  feat(config): granular vite configs and React Compiler support #1102
• Bug fixes
  fix: hydration error with useId #1109

v0.21.13

• Improve error handling
  chore: react-server (dynamic ssr and rsc) error handling e2e tests #1112
  refactor: error handling #1122
• Support monorepo setup
  chore: create monorepo e2e spec #1079
• Bug fixes
  fix(dev): do not process mdx files in devCommonJsPlugin #1125
  fix: netlify relative fs path #1126

v0.21.14

• Bug fixes
  fix(dev): proper not found handling #1136
  fix(path-types): allow # and ? links for to prop #1137
  fix(build): fsRouterFiles were not included during static build #1139
  feat: Remove ErrorBoundary from Router #1131
  fix(dev): module resolution in monorepo setup #1143

v0.21.15

• Bug fixes
  fix: use case with preload #1150
  fix: react-compiler with the latest canary #1151

v0.21.16

• Bug fixes
  fix: React context loss in a monorepo setup #1162
  fix(typegen): skip parsing errors and remove formatting #1164

v0.21.17

• Bug fixes
  fix(types): PageProps was missing type hints for paths #1173
  fix: build data (critical issue with non-nodejs envs) #1179
  feat: separate build data into files #1181

v0.21.18

• Bug fixes & some updates
  refactor(tailwind): bump all projects to v4 with vite tailwind plugin #1189
  fix(router): static route handling #1194
  fix(core): add hash to rsf{n} #1203
  fix: prefix for exported functions #1205

v0.21.19

• Bug fixes & some updates
  chore: vite 6.1 #1214
  fix(minimal/dev): rscPath encoding in willBeHandled #1216
  Fix import of platform data file for cloudflare builds when using dynamic routes #1224
  fix(vercel): emit platform data #1226
  feat(create-waku): Add support for bun package manager #1229
• Router improvement
  feat(create-pages): support for exactPath #1215
  feat(fs-router): allow _components & _hooks in the pages folder #1222

v0.21.20

• Bug fixes & some updates
  feat(create-waku): --project-name option #1232
  fix(tailwind): swap @tailwindcss/vite for @tailwindcss/postcss #1234
  fix(create-waku): remove tsbuildinfo files from template #1236
• Router improvement
  feat(router): configuration of scroll behavior for Link and useRouter #1231

v0.21.21

• Bug fixes & some updates
  fix: keep server assets on server build #1258
  fix(dev-server): hot reload with css modules #1259
  fix(router): _components and _hooks should be ignored by path typegen #1246
  fix(create-pages): Ensure dynamic layouts receive path prop #1256
  fix(router): avoid default startTransition #1257

v0.21.22

• Bug fixes & some updates
  hack tailwindcss4 for stackblitz #1266
  fix(create-waku): Fix detection of bun using npm_config_user_agent env var #1268
• Router improvement
  feat(create-pages): Support HEAD and OPTIONS api handlers #1269

v0.21.23

• Bug fixes & some updates
  feat(router): fs-router support apiDir configurability #1295
  fix(handler): tee body for decode post action #1298
  fix(create-pages): pass request url for createApi handler with search #1300
  fix(router): decode path for storing elements and slug as prop #1304

v0.21.24

• Bug fixes & some updates
  fix(build): analyze client components loaded from server functions #1316

v0.22.0

• Support for API routes
  feat(router): create api #1260
• useRouter hook
  breaking: remove _UNSTABLE from useRouter #1129
• string-based waku.config.ts
  breaking: string only waku.config.ts #1281
• Drop Node 18
  drop node 18 #1331
• React 19.1
  update react 19.1 #1330
• Some improvements
  feat: bypass Link click handler if alt click or defaultPrevented #1249

v0.22.1

• Fix dependencies
  rollup 4.38.0 #1343
  fix: downgrade tailwindcss for now #1341

v0.22.2

• Improve create-waku
  fix(create-waku): fix cli and swap to clack + pico #1319
• Bug fixes & some updates
  Bump Node.js to v22 for Vercel deployments #1337
  feat(api): support default export for handling all api methods #1348
  fix: React component as server function argument #1354
  fix: loading two middleware in DEV #1361

v0.22.3

• Bug fixes & some updates
  rollup 4.39.0 #1353
  fix: 404 handling #1371

v0.22.4

• Bug fixes & some updates
  fix: update client module cache after n css module importee hmr #1378
  fix: temporary references with server components #1384

v0.23.0

• Pathless components in waku/router
  Layout Reset / Groups / Pathless Routes #977
  chore: remove flags for router features in prep of 0.23 #1401
• Async refetch & changeRoute (internal breaking change)
  feat: async refetch #1396
  feat(router): routing events #1391

v0.23.1

• Bug fixes & some updates
  fix(aws-lambda): remove errored code #1412
  fix: Cannot update a component ("Root") while rendering a different component warning #1421
  fix: continue transition with server actions triggering rerender #1425
  fix(typegen): routes with leading numbers cause typescript error #1427

v0.23.2

• Bug fixes & some updates
  refactor(minimal): enhance features (BREAKING) #1430
  feat(Link): Support forwarding ref on Link component #1455
  fix: continue transition with waku/router Link #1458

v0.23.3

• Bug fixes & some updates
  fix: rename entry files (BREAKING) #1460
  Fix(create-pages): Fix path matching precedence for api routes with wildcard routes #1451
  fix(create-pages): keep path encoded consistently when passed as a page prop #1395
  BREAKING: update vite 7 #1490

v0.23.4

• Bug fixes & some updates
  fix: update url after route change #1459
  fix(create-pages): Fix API catch-all routes matching before standard API routes #1508
  fix monorepo with pnpm and yarn #1524

v0.23.5

• Bug fixes & some updates
  fix(ssr): hydration error with the root script tag #1514
  fix(define-router): unstable_disableSSR in createPages #1540
  feat(define-router): support unstable_redirect in server functions #1532

v0.23.6

• Hotfix for v0.23.5
  fix(define-router): experimental flag #1547

v0.23.7

• Bug fixes & some updates
  fix(dev-server): prefer default ws port #1550
  fix: workaround React.use SSR bug by wrapping extra component #1545
  fix: fouc in website #1568

v0.24.0

• vite-rsc / environment api
  feat: use @vitejs/plugin-rsc #1493
• Bug fixes & some updates
  feat: support catch all on router api #1573
  feat: allow read private folder during rsc #1576

v0.25.0

• Breaking: page defaults to static
  fix(fs-router): change default render for pages and slices to be static [BREAKING CHANGE] #1605
• Slice API in waku/router
  feat(router): unflag slice feature #1607

v0.26.0

• Drop page parts
  chore(router): remove deprecated page parts #1606
• Drop legacy CLI
  feat: remove --experimental-legacy-cli and legacy implementation #1597

v1-alpha

• 🤩

v1-beta

• More compatibilities with third-party libraries
  [Umbrella] Third-party library compatibility issues #423

v1-final

• 💪

Post-v1

• Migrate to Rolldown full bundled mode
• Waku PPR Waku PPR? #1172

[Aslemammad]

How about actions? I was thinking about developing a plugin for vite a while ago, Since I think it's something similar to telefunc while developing this tool with Rom Brillout.

[dai-shi]

Actions (what I call "React Server Functions") are already implemented. I wouldn't say it's complete though.

[Aslemammad]

Nice!

[tom-sherman]

Anecdotally there seems to be a fairly large gap between waku's server actions and Next.js' implementation - I suppose this is expected because server actions are completely experimental in React right now.

IMO it makes sense to mark them as such (as an opt-in config option) before releasing v1.

[dai-shi]

I don't think our RSF (react server function) isn't that experimental, meaning it's the same level as react server component. I suppose Next's server action does more experimental things.

That said, I would like to revisit our approach anyway, which will require some feedbacks from collaborators/contributors/users.

In any case, unless we have an official doc or RFC from React, we wouldn't be able to finalize our API, which means v1 probably won't land until then.

[tom-sherman]

The problem with shipping server actions now (or before they're stable in React) is that the semantics are not specified yet. For example Next.js server actions are queued, it's impossible to execute them concurrently - not the case in Waku. There is also the integration with transitions, not sure if this is implemented in Waku.

IMO need to wait for a React RFC but only for server actions, there is already an RFC for server components and they're designated at stable by the React team.

This is why I think waku server actions behind a flag is the right way forward.

[dai-shi]

Yeah, if we would release v1 before the callserver RFC, we should hide it behind a flag. For now, just noting it's not finalized would be enough. But in that sense, everything isn't finalized.

[childrentime]

@dai-shi How about SSG? And change docs website to static files.

[dai-shi]

docs website is already static files.
we generate static files on build (SSG is a vague word, as people expect to generate HTML files.)

[dai-shi]

IMO it makes sense to mark them as such (as an opt-in config option) before releasing v1.

Having been working on #124, I'm getting more skeptical about the stability. (What is currently working may not work in the future.)
My gut feeling is that we should wait releasing v1 before React 18.3.0 or 19 is out.

[zouhangwithsweet]

So waku will not use react-server-dom-vite in the future?