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

erquhart•12/11/24, 4:15 PM

What prints out when you run

npx convex dev

npx convex dev

jamwt•12/11/24, 4:25 PM

@cody sorry to hear that. we have a tool to help debug this

jamwt•12/11/24, 4:25 PM

can you run ?

jamwt•12/11/24, 4:25 PM

and let us know the output?

Eerquhart What prints out when you run `npx convex dev`

codyOP•12/11/24, 5:11 PM

It briefly shows 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 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•12/11/24, 5:14 PM

ah... yes, we should have thought of that

jamwt•12/11/24, 5:14 PM

circular import type stuff really throws everything for a loop

jamwt•12/11/24, 5:14 PM

makes sense

jamwt•12/11/24, 5:15 PM

sharing logic is pretty common, but normally the logic is pretty clearly in clean

.ts

.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...

codyOP•12/11/24, 5:31 PM

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

codyOP•12/11/24, 5:46 PM

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