unable to push deployment
I get this bug when trying to push my code to convex
✖ Error: Unable to push deployment config to https://giddy-hyena-745.convex.cloud
✖ Error fetching POST https://giddy-hyena-745.convex.cloud/api/push_config 400 Bad Request: Error: Hit an error while pushing:
Uncaught TypeError: Cannot read properties of undefined (reading 'json')
at <anonymous> (../../node_modules/convex/src/values/validators.ts:307:24)
at map [as map] (<anonymous>)
at get json [as json] (../../node_modules/convex/src/values/validators.ts:304:10)
5 Replies
Thanks for posting in <#1088161997662724167>.
Reminder: If you have a Convex Pro account, use the Convex Dashboard to file support tickets.
- Provide context: What are you trying to achieve, what is the end-user interaction, what are you seeing? (full error message, command output, etc.)
- Use search.convex.dev to search Docs, Stack, and Discord all at once.
- Additionally, you can post your questions in the Convex Community's <#1228095053885476985> channel to receive a response from AI.
- Avoid tagging staff unless specifically instructed.
Thank you!
it sounds like you have an invalid validator (
v.array, v.number, etc), either in args or returns or your schema.
it's unfortunate that the error message isn't telling you which validator is invalidYeah the common cases are a weird validator in your schema (I've seen stuff like
v.object({ field: "foo" }) instead of v.object({ field: v.literal("foo") }) as an example) or sometimes this happens if there are multiple versions of Convex floating around (like if you're using convex-helpers), in which case updating all the convex-related node modules usually helpsWe have another thread going for this too fyi: https://discord.com/channels/1019350475847499849/1351649078735540357
I just experienced this same error when I had a circular dependency in some validators. I.e. I had imports going in both directions between two files:
profile/validators.ts <---> submission/validators.ts.
These particular validator files are not used for my schema definition, so maybe that's why this particular error does not show up as our old friend "api instantiation is excessively deep ..."?