v0.26.12026-10-23
⚠️ Breaking Changes
- Wasp now requires Node.js >=24.22.1 (previously >=24.14.1), which includes fixes for the October 2026 Node.js security vulnerabilities. (#5113)
v0.26.1-rc.1预发布2026-10-23
v0.26.02026-10-16
⚠️ Breaking Changes
Remember to check out the migration guide for step-by-step documentation on how to upgrade.
- Wasp now type-checks application code during compilation. (#4942)
- Email fields in Wasp's auth forms now use type="text" to support internationalized addresses. (#4695)
- SDK changes require updating tsconfig.src.json and copying the generated types directory in custom Dockerfiles. (#4049, #4067)
- Renamed the wasp deploy fly flags --vm-size, --initial-cluster-size, and --volume-size to --db-vm-size, --db-initial-cluster-size, and --db-volume-size, respectively. (#4642)
- wasp deploy fly now requires Fly CLI version 0.4.82 or newer. (#4642)
- wasp deploy railway now requires Railway CLI 5.28.0 or newer. (#4712)
- Moved internal server-only import paths under the wasp/server/... prefix. These paths are not part of the documented public API, but if your app imported any of them, update the import path or switch to documented public imports like wasp/server/auth. (#4557)
- Wasp now manages your app's URLs in development, so setting WASPSERVERURL, WASPWEBCLIENTURL, or REACTAPPAPIURL yourself is now an error. Use the new --client-url and --server-url options instead (see below). (#4692)
- Wasp now manages your app's ports in development, so setting them yourself (e.g. server.port in vite.config.ts) is now an error. (#4591)
- In deployed Wasp server apps, the PORT environment variable is now compulsory. (#4591)
- Removed the wasp info command, in favor of the new wasp show family of commands. (#4622)
- The Wasp server's liveness check moved from GET / to GET /up. The root path is free for custom apis, while /up is now reserved by Wasp. Point health checks that probed / at /up. (#4856)
🎉 New Features
- wasp start and wasp build start now accept --client-port <port> and --server-port <port> arguments to choose the ports your app runs on. (#4585)
- wasp start will also intelligently choose ports, so that you can run multiple apps in your system simultaneously. (#4586)
- wasp start and wasp build start now accept --client-url <url> and --server-url <url> to make your app reachable at a URL other than localhost, such as a LAN hostname or an HTTPS tunnel. (#4915)
- You can now run dev databases for multiple Wasp projects in parallel: wasp start db looks for a first port instead of failing when the default one is taken, and wasp start automatically finds the port the database ended up on. (#4571)
- wasp start db now accepts a --db-port <port> argument to choose the port your dev database runs on (by @Nihal-Ahamed-MS). (#4424)
- Wasp now pins newly created Fly.io and Railway databases to PostgreSQL 18. Added --db-volume-mount-path to wasp deploy railway launch and wasp deploy railway setup for custom database images that store data elsewhere. (#4647)
- Added the --db-vm-memory, --db-vm-cpus, and --db-vm-cpu-kind options to wasp deploy fly launch and wasp deploy fly create-db. (#4642)
- Now Wasp fails more gracefully when multiple commands are running in the same project. (#4504)
- Added a wasp show spec [--json] command that prints an overview of your app as Wasp sees it: routes, pages, queries, actions, APIs, CRUDs, and jobs. (#4451)
- Added the wasp show build [--json] command to print information about the last build. (#4625)
- You can now customize your tsconfig.src.json more freely: options like strict, target, and lib are no longer locked, include and exclude allow extra entries, etc. Wasp still requires the options it needs to compile and bundle your project. (#4772)
- Custom apis can now use the PATCH and HEAD HTTP methods. (#4852, #4860, #4867)
- wasp uninstall now accepts --force to skip the confirmation prompt. (#5003)
🐞 Bug fixes
- Fixed TypeScript incremental compilation failing to pick up updated types. (#4885)
- Wasp's compiler now properly escapes user input in the code it generates. (#4855)
- Fixed a bug that created Railway databases without a persistent volume when using --db-image. Existing databases are unchanged. (#4647)
- Fixed Wasp commands failing with "resource exhausted (Too many open files)" in projects with many files under src/. (#1919)
- Fixed wasp start and wasp db commands hanging in some edge cases. (#4930)
- Failed OAuth logins now tell users when they cancelled the login or it expired, instead of showing an unknown error. (#4941)
- If an optimistic update’s getQuerySpecifier throws, useAction now rejects with that error instead of an unrelated TypeError. (#5024)
🔧 Small improvements
- wasp start now finds the managed dev database by asking Docker where the project's database container is running, instead of assuming localhost:5432. This means Wasp will no longer accidentally connect to an unrelated database that happens to be listening on port 5432. (#4567)
- Newly created projects no longer open the browser automatically on wasp start. (#4553)
- Upgraded internal morgan to 1.12, which fixes CVE-2026-5078, CVE-2026-15603 and CVE-2026-87859. Wasp's usage was unaffected by the vulnerabilities. (#4573, #5032)
- The <region> argument of wasp deploy fly is now case-insensitive, so e.g. MIA is accepted instead of being rejected as an invalid region. (#4588)
- Fixed the throttle on resending the email verification email, which checked when the last password reset email was sent instead of the last verification email. (#4651)
- Verifying an email now returns an "invalid credentials" error instead of crashing the server when the account behind the verification link no longer exists. (#4652)
- Resetting a password now logs the account out everywhere, s
v0.26.0-rc.1预发布2026-10-15
v0.25.02026-07-27
⚠️ Breaking Changes
Remember to check out the migration guide for step-by-step documentation on how to upgrade.
- Upgraded Vite to v8 and Vitest to v4.1. (#4423)
- Upgraded Wasp's TypeScript support to TypeScript v6. (#4401)
- Upgraded React Router from v7 to v8. The upgrade is backwards compatible. (#4433)
- Removed internal wasp/... paths that were not part of the documented public API. If your app imported any of these private paths, switch to documented public imports like wasp/client/operations, wasp/server/operations, wasp/server/auth, and wasp/serialization. (#4351)
- Removed the Wasp Language Server functionality, since it's not needed anymore in the Wasp Spec. (#4335)
🎉 New Features
- We now have a Linux ARM64 build of Wasp available! That means that Wasp can now run on e.g. the Raspberry Pi or Docker on Apple Silicon. npm install -g @wasp.sh/wasp-cli will automatically install the correct version for your system. (#4435)
- A route's prerender option now also accepts an array of paths, so you can prerender specific instances of a dynamic route (e.g. prerender: ["/blog/intro", "/blog/changelog"] for a /blog/:slug route). (#4318)
- Added Resend as an email sender provider, usable via provider: "Resend" and the RESENDAPIKEY environment variable. (#4381)
- Added a wasp doctor command that runs common sanity checks on your setup to check that Wasp can work correctly, and prints a report. (#4283)
🐞 Bug fixes
- Fixed a race condition where useAuth() could return stale user data after an action that modifies the User entity (by @okxint). (#4343)
🔧 Small improvements
- The wasp compile command is now listed in wasp's usage output and bash completion, making it easier to discover. (#4456)
- wasp deps no longer shows internal Wasp packages in its output (by @okxint). (#4342)
- tsconfig.wasp.json's include now accepts extra globs in addition to the required Wasp entries, so you can keep helpers and libraries used by your .wasp.ts files in the same TS project. (#4398)
- Improved some prerendering internals for a faster first paint and more accurate lazy-loading of pages. (#4428)
- If you're writing a Wasp Spec library, you can now throw your own WaspSpecUserError from @wasp.sh/spec to report configuration problems the same way Wasp does. (#4448)
- The Wasp Spec package now exports the config object types for its constructors from @wasp.sh/spec, so libraries built on top of the Spec can reuse the type of a constructor's optional config argument. (#4447)
- The Wasp Spec package is now published to npm, for easier consumption by libraries outside of Wasp projects. Most users don't need to install it directly, since the Wasp CLI will manage it for you. (#4461)
- Listing the same entity more than once in a query or action's entities now fails with a clear error. (#4455)
v0.25.0-rc.1预发布2026-07-27
v0.24.02026-06-11
⚠️ Breaking Changes
Remember to check out the migration guide for step-by-step documentation on how to upgrade.
- The Wasp TS config (main.wasp.ts) is now called the Wasp Spec, and it should import from @wasp.sh/spec instead of wasp-config. (#4153)
- Wasp now requires vitest to be listed in your project's devDependencies. (#4182)
- Removed wasp new:ai and the ai-generated starter template. (#4280)
🎉 New Features
- The api export from wasp/client/api is now a Ky instance instead of Axios for improved performance and smaller final size. (#3998)
- Wasp TS spec now properly sets the NODE_ENV environment variable depending on which command you use to run Wasp. (#4087)
- Added a type-safe NavLink component, mirroring react-router's NavLink API (with isActive, isPending, isTransitioning render-prop helpers). (#4104)
- Wasp TS spec now supports real JS imports, letting you import values in main.wasp.ts and pass them directly instead of using import objects like { import, from }. (#4143)
🐞 Bug fixes
- Fixed a race condition in development mode that could potentially load the app's JS bundle before the Vite runtime, causing the app to fail the load with a "Can't detect preamble" error. (#4258)
- Fixed wasp deploy railway launch sometimes producing a crashed server with an empty DATABASE_URL. Wasp now waits for the database service to finish deploying before setting up the other services. (#4291)
- Fixed a bug where wasp deploy railway launch wouldn't correctly build the Wasp app client if the / route was not prerendered. (#4293)
🔧 Small improvements
- Wasp now also validates tsconfig.wasp.json and the root tsconfig.json in TS spec projects, and tsconfig validation errors now mention which tsconfig.*.json file caused them. (#3911)
- The npm package now shows a clear error when installed on an unsupported Node.js version. (#4268)
📖 Documentation
- We now have a SEO & GEO optimization guide. (#4264)
v0.24.0-rc.3预发布2026-06-11
v0.24.0-rc.2预发布2026-06-11
v0.23.02026-04-15
⚠️ Breaking Changes
Remember to check out the migration guide for step-by-step documentation on how to upgrade.
- Wasp now requires Node.js version >=v24.14.1 (previously >=v22.22.2). (#4010)
- Upgraded the pinned TypeScript version from 5.8.2 to 5.9.3 (required by @tsconfig/node24). (#4010)
- The HTML file for the final built web app has changed from index.html to 200.html. This is in preparation for prerendering support. (#3981)
🎉 New Features
- Routes can now be prerendered at build time by setting prerender: true. Prerendered routes are served as static HTML for faster load times and better SEO. (#3982)
🐞 Bug fixes
- Updated wasp deploy railway to work with the Railpack builder. (#3981)
🔧 Small improvements
- Updated our wasp deploy tool to support the new 200.html SPA fallback. (#3981)
- New Wasp projects now include an .npmrc with min-release-age=7 for supply chain protection. (#4016)
📖 Documentation
- Updated deployment guides for Fly.io, Railway, Netlify, and Cloudflare to work with the new 200.html SPA fallback. (#3981)
- Added guide for deploying to Render. (#4055)