I've added these in but nothing is rendered. If I remove them then everything renders as normal. Has anybody seen this?

E.g.

const App: FC<AppProps> = ({ Component, pageProps }: AppProps) => { return ( <NhostAuthProvider auth={auth}> <NhostApolloProvider auth={auth} gqlEndpoint={process.env.GRAPHQL_ENDPOINT}> <ChakraProvider> <Component {...pageProps} /> </ChakraProvider> </NhostApolloProvider> </NhostAuthProvider> ); }

this just renders a blank page, but if I remove the Nhost providers it works as normal.

Hi. I am evaluating this new product. I've just following the getting started guide and tried to create a "todos" app but now the process has been stuck on the "Creating your project..." step (Nhost console) for days now. Even when I pick my answers and move ahead, the process does not complete and stays at this step for hours.

Set ALLOWED_EMAIL_DOMAINS in the Nhost console to specify what email domain names are allowed to register accounts.

This PR adds a new example for Nhost with React-Query

Environment - Local/Nhost Dev Machine - Apple M1 Macbook Pro

Issue When trying to create a custom API, I installed the Twilio package and the nhost_api server crashed and logged the following

nhost_api | import net from 'net';

nhost_api | ^^^^^^

nhost_api |

nhost_api | SyntaxError: Cannot use import statement outside a module

nhost_api | at wrapSafe (internal/modules/cjs/loader.js:979:16)

nhost_api | at Module._compile (internal/modules/cjs/loader.js:1027:27)

nhost_api | at Module._extensions..js (internal/modules/cjs/loader.js:1092:10)

nhost_api | at Object.require.extensions.<computed> [as .ts] (/usr/src/app/node_modules/ts-node/src/index.ts:1286:43)

nhost_api | at Module.load (internal/modules/cjs/loader.js:928:32)

nhost_api | at Function.Module._load (internal/modules/cjs/loader.js:769:14)

nhost_api | at Module.require (internal/modules/cjs/loader.js:952:19)

nhost_api | at require (internal/modules/cjs/helpers.js:88:18)

nhost_api | at /usr/src/app/index.ts:17:26

nhost_api | at Array.forEach (<anonymous>)

Expectation I should be able to import an npm package without issue

Fixed two minor issues in the Nhost with React-Query example example:

• The register form was not passing the email and password to the auth.register function correctly.
• The login form is never shown due to the user === null check

assumption: every OSS app, is written for the people to use. for that a setup-instruction is a necassary part.

please publish a how-to, docker-compose etc. TIA

Hi @elitan , For hasura's backend, testing and monitoring are almost non-existent right now. Hasura basic console does not offer the features for us to run regression testing and monitor the traffic. Is it possible to include this feature in the near future? Thanks

A versioning of the last saved storage rule settings would be great to "fallback" to the last working version.

Probably someone screwed up his rules and has a struggle right now.. probably that someone is me ...:-|

It would be great to disable Anonymous registration from so that it cannot be controlled by an account admin. It seems that this could potentially be a security hole for some applications.

I am not sure if this belongs here or the backend plus.

On the Deployment screen it would be awesome to support gitmojis. This is a minor suggestion but would line up with github support

Dear @elitan ,

in the docs, i read about Custom APIs ( https://docs.nhost.io/custom-api ), which would really be an awesome feature. Prior, i worked a lot with NestJS ( https://nestjs.com/ ), which is (at least for me) the go-to backend framework when i need to develop an API.

For larger project, i always followed a monorepository approach (i.e., all of my applications (api, web application, mobile application, admin web application, ...) are stored within the same git repository. In this context, i used nrwl/nx to structure / maintain my monorepository. However, nrwl/nx has a predefined folder structure. For example, your apps are located within apps/!

In this context, the custom api would not work, because the api would be stored in apps/awesome-api or whatever ;) Could you please make the api path within the repository customizable? Somewhere in the Settings page or whatever?

All the best, Johannes

Dear @elitan ,

first of all, thanks for creating this awesome project. Really happy to take a look, read the docs and find my way around. Looks very promising.

I am currently evaluating nhost as a BaaS solution here at university for our next projects. I am not sure if this repository is the correct place to ask some general questions or request features - but i will try anyway. Please feel free to transfer this issue to any other repository, if it is more suitable.

In our institute, we support researchers from different domains in collecting, visualizing and analyzing (medical) health data. Based on our partners, we have a lot of "repeating projects" (i.e., deploy the same application over and over again for different scenarios, like tinnitus, diabetes, ...).

In order to easily manage these projects, i would like to have :

• some kind of export feature, that allows to quickly dump the entire project (i.e., the entire database schema with all relations, and so on)
• import this schema within a newly created project and have everything setup.

Can you point me into the right direction? Is this (already) possible? If so, how? Can we add such a "schema description" file to our git repository and keep track of changes?

All the best, Johannes

This also seems like the experience could be easier if the Sign in methods and Authentication settings where moved under the Authentication section at the top of the console.

From a usability standpoint having the Storage Rules under settings is confusing. It would be great to have it under the storage section.

When creating a user, it would be great to specify roles in the UI on this screen.