Thomas O

Would love to see this integrated into the data table component.

I think what the OP: means is that the resulting zip file when installing all dependencies is> 55M. This means that it is not possible to run on AWS lambda....

@jpweytjens yes to work around this I made a fork yesterday and just commented out the dependency on SpeechRecognition and successfully deployed to lambda. So having the SpeechRecognition dependency as...

Hm getting the same error and upgrading od downgrading node does not seem to help. starting via `npx expo start` i am on latest version and node 16

For anyone having this issue. I cant connect to api.expo.dev from any ipv6 address jumping on vpn that exits via an ipv4 it seems to work. cc @Kudo or anyone...

Getting the same error this makes the resulting json unusable in later mapbox implementations etc.

Yes just starting a new project and getting the exact same error. Having working local mock functionality for generated code should be a mimimum. Might have to take the advice...

For people having the same issue here. Mocking of typescript functions does not seem to work. However they seem to run with amplify push. So the workaround is as mentions...