wasp-lang/wasp v0.19.0 on GitHub

Remember to check out the migration guide for step-by-step documentation on how to upgrade.

Wasp now requires your project's package.json to contain "workspaces": [".wasp/build/*", ".wasp/out/*"]. (#3159)
The type of config.allowedCORSOrigins (from wasp/server) was changed from string | string[] to (string | RegExp)[].

Wasp now uses npm workspaces to manage our generated code. This makes our dependency system more reliable, improves install performance and reduces the size of each project on disk. (#3159)
You can now specify which PostgreSQL image to use in wasp start db with the --db-image argument. (#3182)
You can now specify a custom volume mount path for the development database with the --db-volume-mount-path option in wasp start db. (#3362)
You can now specify which PostgreSQL image to use in wasp deploy railway with the --db-image argument. (#3184)
You can now specify which PostgreSQL image to use in wasp deploy fly with the --db-image argument. (#3187)
It's now simpler to extend our default CORS rules. (#3339)

Fixed a type error in the generated server app when process.env.NODE_ENV is also declared by another dependency in the project. (#3189)
Fixed an incompatibility between wasp deploy fly and Fly CLI v0.3.214. (#3372)
Raised the internal requirement of Tailwind CSS from ^3.2.7 to ^3.4.17 to ensure compatibility with ESM config files. (#3380)
Fixed an error with routing when serving the client from a subpath in a domain. (#3322)
Fixed an error with CORS when serving the client from a subpath in a domain. (#3339)

Creating a new OpenSaaS project is now much faster (around 20x faster in our testing!). (#3196)
In development mode, Wasp displays a helpful message when navigating to the backend port, pointing you to your app's main URL. (#3213)

Updated Tailwind CSS installation command in docs from exact version 3.2.7 to 3 (latest v3) to ensure compatibility with Wasp 0.18.0+ ESM config files. (#3377)
Added note for SMTP ports being blocked by some hosting providers (by @Vickram-T-G). (#3109)
Added documentation on how to setup the Chrome DevTools workspace mapping with Wasp (by @0xTaneja). (#3103)

Wasp's kitchen-sink application has been moved to the public examples (examples/) directory in our repo. (#3085)