local deployments are non strict but deployments with fly are strict
../../../src/admin/UsersPage.tsx(261,22): error TS18046: 'error' is of type 'unknown'.
../../../src/admin/UsersPage.tsx(275,20): error TS18046: 'error' is of type 'unknown'.
../../../src/auth/hooks.ts(142,40): error TS7006: Parameter 'tx' implicitly has an 'any' type.
../../../src/chat/ChatPage.tsx(295,65): error TS7053: Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{ 'Study Assistant': { reminder: string; initialMessage: { content: string; role: string; provider: string; }; }; 'Essay Helper': { reminder: string; initialMessage: { content: string; role: string; provider: string; }; }; ... 5 more ...; 'Meeting Planner': { ...; }; }'.
No index signature with a parameter of type 'string' was found on type '{ 'Study Assistant': { reminder: string; initialMessage: { content: string; role: string; provider: string; }; }; 'Essay Helper': { reminder: string; initialMessage: { content: string; role: string; provider: string; }; }; ... 5 more ...; 'Meeting Planner': { ...; }; }'....
wasp deploy
im getting this error when running wasp deploy wasp deploy fly launch petall ams
$ flyctl version
flyctl v0.3.137 linux/amd64 Commit: 7a200d0547f773b3892a907959878b278d04f107 BuildDate: 2025-06-02T21:28:41Z
$ flyctl auth whoami
njerumurimi@gmail.com...
FLY deploy WASP 13.2 Issue
Hello today i tried to deploy app using
wasp deploy fly launch appname ams
Firstly i for prompted thati need to specify organization so i used ...
@tanstack/react-query version
I am building on open-saas template built with Wasp version 0.16.0. The version is now 0.16.3. Wasp requires @tanstack/react-query "^4.29.0". It doesn't matter how many time "npm install" is invoked after adding "^4.29.0" to the package.json. I found out that the version "4.29.0" no longer exist in npm, and that "4.29.5" is the latest in the series. Now, the issue is every time npm install is invoked version 4.39.1 is always on the tree. I need you assistance in resolving this.
Persistent Schema again.
I'm experiencing a persistent migration state issue where Wasp is trying to apply an old schema that doesn't match my current schema.prisma file.
The Problem:
- My schema.prisma has a simple BudgetItem model
- But wasp db migrate-dev keeps trying to create phantom tables (Budget, BudgetCategory, Guest, Vendor) that don't exist in my schema...
Prisma Postgres + Wasp?
I want to use Prisma Postgres, their hosted Postgres service, but it's wanting me to run some commands to enable Accelerate. Is this okay to do with Wasp? I recall the docs saying to only run Prisma commands through the Wasp CLI, so I wanted to double check.
What's the best way to do import aliases?
I'm not sure how best to create import aliases with Wasp (if it's possible). I attempted a few ways, including adding it to all three tsconfig files and vite config, but none have worked. I'm using
*.wasp.ts for the app config if that's relevant. I know there's an issue open regarding aliases, so is it impossible for now? Thanks in advance!custom onaftersignup
How can I add a custom hook to run after creating a user using OAuth (Google)? I want to copy the email address from Google to the username field.
scrollReadRandom error on mobile scroll for landing page
I'm getting a type error as attached for my landing page when users are scrolling through my landing page. It seems users aren't able to scroll easily through the page. I can't find scrollReadRandom anywhere in my codebase...A bit flummoxed on how to deal with the issue. I can't recreate it Any suggestions? I'm using the OpenSaaS template.
signup Network Error
I'm trying to sign-up locally with the Dummy Provider. After entering an email and password, the page says
Network Error in red. The terminal logs don't show anything. The browser console logs show login.ts:7 POST http://localhost:3001/auth/email/login net::ERR_CONNECTION_REFUSED. Did I miss a step in the docs?
I'm using WSL and on Wasp version 0.16.4...Build Error: QueryClient Type Conflict - Need Help with Production Deployment
Hey everyone! 👋
I'm running into a build error when trying to deploy my WASP project to production and could really use some help.
Issue: When I run
wasp build, I'm getting this TypeScript error:...Adding sign up extra fields
[ Wasp ] src/auth/SignupPage.tsx(26,13): error TS2353: Object literal may only specify known properties, and 'recaptchaToken' does
not exist in type 'AdditionalSignupFields'.
[ Wasp ] src/auth/signup.ts(17,3): error TS2322: Type '(data: SignupData) => Promise<string>' is not assignable to type 'FieldGetter<string | null | undefined>'.
[ Wasp ] Types of parameters 'data' and 'data' are incompatible.
[ Wasp ] Type '{ [key: string]: unknown; }' is missing the following properties from type 'SignupData': email, password ...
wasp 0.16.5 Problem
after the last issue with @tanstack/react-query , i updated my wasp version from 0.16.3 to 0.16.5.
i run wasp clean , and deleted all package-lock.json and node_modules , deleted database container and volume and started fresh :
```wasp start db
wasp db migrate-dev...
Started getting this randomly after a wasp clean
e: https://docs.sentry.io/api/auth/
[ Client!] error when starting dev server:
[ Client!] Error: Failed to resolve entry for package "@tanstack/react-query". The package may have incorrect main/module/exports specified in its package.json.
[ Client!] at packageEntryFailure (file:///Users/jacobferrari/wasupupdate/my-saas/app/.wasp/out/web-app/node_modules/vite/dist/node/chunks/dep-DBxKXgDP.js:16198:15)
[ Client!] at resolvePackageEntry (file:///Users/jacobferrari/wasupupdate/my-saas/app/.wasp/out/web-app/node_modules/vite/dist/node/chunks/dep-DBxKXgDP.js:16195:3)...
React.StrictMode Causes Duplicate API Requests in Production
React.StrictMode Causes Duplicate API Requests in Production
Problem
All API requests are executed twice in production, causing:
- Duplicate database records...
Unit testing
Hello,
Are there any recommended ways for integrating unit testing in a Wasp project? I do have e2e tests via Playwright following the OpenSaaS template approach, but they're slow and expensive to maintain.
I'd like to add a layer of unit tests but I don't know if there is any recommended way to do it with Wasp...