oso
oso copied to clipboard
fix: catch and log the dynamic import error
My previous hunch was correct, something about vercel and dynamic imports either doesn't work or works in a different way than expected.
The latest updates on your projects. Learn more about Vercel for GitHub.
| Project | Deployment | Preview | Comments | Updated (UTC) |
|---|---|---|---|---|
| kariba-network | Preview | Comment | Nov 28, 2025 7:47am | |
| oso-www | Preview | Comment | Nov 28, 2025 7:47am |
I am starting to think it might be way easier for us to just go for a python backend and make the sql route communicate with that.
Yes I am also thinking this as well. but not necessarily python backend. Just do everything async via an async queue. I'll write up a bit of a proposal here. It would effectively be a python backend.