veloware

@joaoarieira were you ever able to get around this issue, I'm also having the same problem, thanks

I hit this problem when I forgot to create a `tsconfig.json` if that helps anyone. I wasn't using serverless-offline so that was irrelevant for me.

also using 2018-05-29, also having this issue

+1 I am storing date/time as a unix timestamp so I can use TTL (TimeToLive) but its too big for Int :/

I too am running into similar cumbersome issues. I love Chakra so far, but small complexities like this cropping up are making me thing twice about using the library unfortunately....

@alon-green there is a 2nd arg you can pass to `useFetch` as a callback, its the first arg of that callback, e.g. - ``` useFetch(url, (globalOptions) => ({ ... interceptors:...

in the case above though, the `globalOptions` is not passed to the callback, it's provided by the callback. Those will be the options that were set at the `` level

https://github.com/alixaxel/chrome-aws-lambda/issues/282

Same problem here, I tried converting the callback to an async function, but now the tests just fail with it telling me to wrap in `act` ``` fetchMock.mockIf('url', async (req)...

also experiencing this, did you ever get around it?