v0.25.0

⚠️ 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 RESEND_API_KEY 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)