Matt Wollerman

Alternatively, what about a backend type extension that specifies where the `deployed.json` can be found? Similar to how terraform can use a s3 remote backend. This way, you can specify...

+1 As an example, I've deployed a few different chalice stages for the same project and this is what it ends up looking like in API gateway: 

Ah yea fair enough. I agree it makes more sense to be at the user customized cookbook level. That better follows open-closed principle. Thanks for the quick response!

I am also experiencing this. The only way I've been able to get past this is downgrading explicitly to ``` "@nhost/hasura-auth-js": "2.3.0", "@nhost/nhost-js": "3.0.5", // 3.0.6 bumps hasura-auth-js dep to...

@onehassan any update on this? It's preventing upgrading all nhost packages because of that dependency chain.

I ran into this after upgrading to expo 50 and switching to metro completely following these guides: * https://docs.expo.dev/router/migrate/from-expo-webpack/ * https://docs.expo.dev/distribution/publishing-websites/#vercel * https://github.com/expo/expo/issues/26706#issuecomment-1937044034 Server runs fine locally (most likely because...

@natew any update? Should we open an issue with metro instead?

Yea, this came about because of an integration that I'm dealing with. Specifically, the integration sends a JWT in the query parameters instead of the header, and, unfortunately, they are...