Samir Alibabic
Samir Alibabic
WWasp
Created by Samir Alibabic on 1/8/2025 in #🙋questions
SendGrid setup
It’s in beta. You would need a printful account / store to make any sense of it. I’ll dm the link if you want to check.
28 replies
WWasp
Created by Samir Alibabic on 1/8/2025 in #🙋questions
SendGrid setup
Just verified with different configurations. No issues this time. I'm assuming some downtime or missconfiguration at the fly.io side as temorary cause of this.
28 replies
WWasp
Created by Samir Alibabic on 1/8/2025 in #🙋questions
SendGrid setup
Sure. I’ll revert to how it was and share the results
28 replies
WWasp
Created by Samir Alibabic on 1/8/2025 in #🙋questions
SendGrid setup
After pulling my hair our for over 2 days, I've finally found what the issue was. Not sure how exactly, but cold starts at fly.io were the problem! Now I have 1 machine running all the time and it works. I have this for both server and client .toml files:
auto_stop_machines="off"
auto_start_machines="true"
min_machines_running=1
auto_stop_machines="off"
auto_start_machines="true"
min_machines_running=1
😤 I guess Wasp apps don't scale well horizontally, but it's also not a requirement for me at this stage.
28 replies
WWasp
Created by Samir Alibabic on 1/8/2025 in #🙋questions
SendGrid setup
All? For SendGrid there is only API_KEY. Everything else is in main.wasp (from email, auth, etc.)
28 replies
WWasp
Created by Samir Alibabic on 1/8/2025 in #🙋questions
SendGrid setup
Yes
28 replies
WWasp
Created by Samir Alibabic on 1/8/2025 in #🙋questions
SendGrid setup
Already did. Nothing in the logs and works locally. The classic „works on my machine“ problem 🤣
28 replies
WWasp
Created by Samir Alibabic on 1/8/2025 in #🙋questions
SendGrid setup
Works in development. Only after deployment, the app does not send emails. I don’t even see them in SendGrid logs, meaning the request to trigger an email does not reach SendGrid. This is for signups and reset password emails. I also noticed that after deployment the date when machine was changed on fly.io does not update, only last deployed date, so I suspect it has something to do with stale docker containers. Will try to remove everything and redeploy fresh.
28 replies
WWasp
Created by Samir Alibabic on 1/7/2025 in #🙋questions
[Error] TypeError: Module name, '.prisma/client/index-browser' does not resolve to a valid URL.
Correct
20 replies
WWasp
Created by Samir Alibabic on 1/7/2025 in #🙋questions
[Error] TypeError: Module name, '.prisma/client/index-browser' does not resolve to a valid URL.
Resolved. I was importing @prisma/client in some hooks and utility functions that were shared, and replacing with shared types, did the trick. Just in case anyone asks :be:
20 replies
WWasp
Created by Samir Alibabic on 1/7/2025 in #🙋questions
[Error] TypeError: Module name, '.prisma/client/index-browser' does not resolve to a valid URL.
@kapa.ai If I have prisma/client in a hook thats being used in client, this could also be the issue? I have a few places where I import prisma/client and those utiliy functions are used in both, frontend and backend.
20 replies
WWasp
Created by Samir Alibabic on 1/7/2025 in #🙋questions
[Error] TypeError: Module name, '.prisma/client/index-browser' does not resolve to a valid URL.
@kapa.ai If I have prisma/client in a hook thats being used in client, this could also be the issue? I have a few places where I import prisma/client and those utiliy functions are used in both, frontend and backend.
20 replies
WWasp
Created by Samir Alibabic on 1/7/2025 in #🙋questions
[Error] TypeError: Module name, '.prisma/client/index-browser' does not resolve to a valid URL.
@kapa.ai I've made the changes and now use separate file for shared types but I still get: [Error] TypeError: Module name, '.prisma/client/index-browser' does not resolve to a valid URL. or in firefox: Uncaught TypeError: The specifier “.prisma/client/index-browser” was a bare specifier, but was not remapped to anything. Relative module specifiers must start with “./”, “../” or “/”. index-c6x-aDJm.js:1:15
20 replies