Daniel Gruszczyk

Thanks for a great explanation @giltayar . I can confirm that with node `v18.16.0` and running it like `NODE_OPTIONS="--loader=ts-node/esm --loader=testdouble" npm run test` mocks are working. I will do a...

I can confirm that adding ava config to `package.json`: ``` "ava": { "extensions": { "ts": "module" }, "nodeArguments": [ "--loader=ts-node/esm", "--loader=testdouble" ] } ``` and running tests like `npm run...

by the way, for node 20 you have to switch `ts-node/esm` loader for `tsimp/import`: ``` export default { cache: false, failWithoutAssertions: false, extensions: { ts: 'module' }, nodeArguments: [ '--import=tsimp/import',...

+1. Any logging to the console should be an *option*! Can we please be able to switch that one off? For now I run `install` in a `child_process.fork` with `silent:...

A year and a half later and still experiencing this issue. Anything being done about this?

I second that. If I have `prop: SomeType` in my GQL schema, all I need is `prop?: SomeType` in TS. the inclusion of `Maybe` here actually annoys me as now...

Certainly doesn't look like it's maintained. However, TS is supported out-of-the-box with Serverless now.

Two weeks and nothing? Not even an acknowledgement?

Updating to `@stripe/stripe-react-native: 0.48.0` still has this issue. This is a serious problem now and stops me from distributing an internal build for testing.

> I further tested and when I provide a dummy implementation for setOrderTracking in the PlatformPayButton like this > > ``` > setOrderTracking={( > completion: ( > orderIdentifier: string, >...