33 replies

Type instantiation is excessively deep and possibly infinite.

The last day or two ive had to disable typescript checking or tsignore as i have been getting this within the convex folder for the first time. Needing typecheck=disable to get around it. I had complained about it appearing in the app directory before as a annoyance. I recently added a lot of actions and some scheduled actions or mutations. I managed to get the same errors in the fullstack template by moving folders into the similar structure.

I was seeing this was not suggested.

convex
├── projects
│   └── activities.ts
└── projects.ts

convex
├── projects
│   └── activities.ts
└── projects.ts

convex
├── projects
│   └── activities.ts
└── projects.ts

convex
├── projects
│   └── activities.ts
└── projects.ts

support-communityType instantiation is excessively deep and possibly infinite.

But that's old and i followed the design of the convex ents example. Im doing things 2 deep.

convex
├── projects
│   └──- tasks
│   └ tasks.ts
└── projects.ts

convex
├── projects
│   └──- tasks
│   └ tasks.ts
└── projects.ts

convex
├── projects
│   └──- tasks
│   └ tasks.ts
└── projects.ts

convex
├── projects
│   └──- tasks
│   └ tasks.ts
└── projects.ts

When I was playing around with the fullstack-convex template in its own environment it was triggered when i moved tasks.ts and /tasks/ 1 level deeper
Its possible the saas-starter template does not have enough api or internal calls to triggers this. It seems to require there to be more then 1 on a page or multiple files with more than one call.

I also just noticed that --typecheck=disable is set on saas-starter so maybe that would avoid ever getting the error combined with the lack of api or internal calls.

Tonight i really don't really like typecheck=disable as i made schema changes to indexs and somehow got no warnings of issues till my business partner ran the same code without that flag and several functions were broken.

This fairly reproducible i'm curious if i should just change my file structure or try to spend time creating another fork example of it in a broken state if we want to go down the "this needs to get fixed" path.

I'm also curious if anyone else is naming their stuff like this in a big project.

Thanks

Type instantiation is excessively deep and possibly infinite.

Similar Threads

Similar Threads

Similar Threads