Johan Eliasson

It should be fixed in the latest release. You can see how it's done in our tests: - Local file: https://github.com/nhost/nhost/blob/main/packages/hasura-storage-js/tests/upload.test.ts#L11-L16 - Remote file: https://github.com/nhost/nhost/blob/main/packages/hasura-storage-js/tests/upload.test.ts#L22-L32

Here's a live example with Nhost and React Query: https://matterday-nhost.netlify.app/matters/1c664a23-f0cd-4849-b030-47e901129b81 Repo: https://github.com/nhost/matterday.netlify.com Interesting parts: - https://github.com/nhost/matterday.netlify.com/blob/main/pages/matters/%5Bid%5D.tsx#L12-L25 - https://github.com/nhost/matterday.netlify.com/blob/main/graphql.config.yaml#L6-L19 - https://github.com/nhost/matterday.netlify.com/blob/main/pages/_app.js#L58-L62 I'll write a post about it in the future.

Would you mind submitting a PR? https://github.com/nhost/nhost/edit/main/docs/docs/platform/quickstarts/nextjs.mdx

Hey @gedw99. Do you mean a Nhost Golang client/SDK as we have for JavaScript/TypeScript to make it easy to interact with graphql, auth, storage, and functions?

Totally. A Nhost Go SDK would be awesome. Let us know here if you want to start building such SDK.

Update potential docs that currently uses `localhost:1337` to `localhost`. Either after merging or in this PR. https://github.com/nhost/nhost/pull/783#pullrequestreview-1027664862

> subdomain: 'localhost:1234' is somehow semantically incorrect. We can live with it, but I think we should introduce a `port` param at a later stage, that would default to `1337`...

> `examples/react-apollo/cypress/videos/1-unauthenticated/authentication-guards.cy.ts.mp4` etc should not be pushed Should be fixed here: https://github.com/nhost/nhost/pull/786/commits/9feea987e68a3be00c8bc860d1e16fff7193bc59

We're using AWS Lambda for our serverless functions and AWS lambda currently only support version 12 and 14: https://docs.aws.amazon.com/lambda/latest/dg/lambda-nodejs.html Version 16 is expected to go live later this month: https://github.com/aws/aws-lambda-base-images/issues/14#issuecomment-1108679026...

AWS Lambda now has support for Node 16: https://aws.amazon.com/about-aws/whats-new/2022/05/aws-lambda-adds-support-node-js-16/ We plan to support this new versions soon.