cody
cody5w ago

I don't think so – it was working fine

I don't think so – it was working fine as of about 5 hours ago. I don't run a vpn or any custom connectivity stuff The fact that it appears to be failing silently makes debugging difficult
5 Replies
erquhart
erquhart5w ago
What prints out when you run npx convex dev
jamwt
jamwt5w ago
@cody sorry to hear that. we have a tool to help debug this can you run npx convex network-test ? and let us know the output?
cody
codyOP5w ago
It briefly shows Bundling component schemas and implementations... then that disappears and nothing else is shown. Each time I save within the convex folder it repeats that same thing. @jamwt all of the network tests say OK I think I may have figured out what the issue is. I have a convex action that is importing something from the root project folder and that module imports logic from a few tsx files. After commenting out the react components in those files I'm seeing the expected Convex functions ready! feedback in the terminal. In hindsight, it's not surprising that this caused an issue. I was attempting to share some logic between the front and back end, but looks like I'll need to rethink it
jamwt
jamwt5w ago
ah... yes, we should have thought of that circular import type stuff really throws everything for a loop makes sense sharing logic is pretty common, but normally the logic is pretty clearly in clean .ts files that act as libs or whatever. I suppose it's possible that somehow bundling .tsx for the convex backend causes something very odd to happen...
cody
codyOP5w ago
Honestly, I would be completely okay with it blowing up if I try to import any tsx logic – or any feedback at all that something isn't adding up Also just want to throw in that I absolutely love using convex. This is the only non-deployment-related issue I've ran into so far – and it was my own fault

Did you find this page helpful?