Hi, I need the connection string to be able to connect to the postgres db in Nhost v2.

Update: NHost team now provides postgres DB Connection string 🚀

Hello nHost team, thanks for the great product!

But may I know if it's possible to reuse any existing authentication provider for the JWT authentication in hasura? For example, can I also support Firebase for authentication in addition to nHost auth?

https://hasura.io/docs/latest/graphql/core/auth/authentication/jwt/#introduction

Currently, the system doesn't allow me to set the HASURA_GRAPHQL_JWT_SECRET ENV, which is how hasura adds a JWT authentication.

I have a function that I am using as a Hasura action. Everything works as expected locally, using the CLI, however when the project deploys in the cloud the functions do not get built.

I am I doing something wrong? Or is there somewhere I can see detailed deployment logs?

Version: Nhost CLI v0.6.12 for darwin-amd64

Functions located in functions directory:

Deploy occurs after committing to repo, but no functions were built:

No functions listed:

Server returns generic error, if I change the function name to gibberish I get the same error message returned:

It works when running locally:

I'm trying to use NhostNextProvider on NextJS application. But once I used the provider, SSG is not working at all. If I remove it, then everything is fine. How can I solve this?

I've started getting this error while compiling suddenly when updated the Nhost dependencies

The version for Nhost libraries are - "@nhost/nhost-js": "^1.2.1", "@nhost/react": "^0.7.10", "@nhost/react-apollo": "^4.2.11",

./node_modules/@nhost/react-apollo/dist/index.esm.mjs Can't import the named export 'ApolloProvider' from non EcmaScript module (only default export is available)

Tried with downgrading and install the dependencies but the issue is not resolved and now the my portal is broken. "@nhost/nhost-js": "^1.1.14", "@nhost/react": "^0.7.8", "@nhost/react-apollo": "^4.2.9",

Describe the bug This bug is on the local development with nhost cli - then on http://localhost:3030/ I see error (screenshot below). This error is on the another pages. GraphQL, Auth and storage dont work too.

To Reproduce Steps to reproduce the behavior:

1. nhost up
2. Open http://localhost:3030/
3. On main screen see error "awsName"

Expected behavior A clear and concise description of what you expected to happen.

Screenshots

Desktop:

• OS: Windows + WSL2
• Browser Chrome
• Version Nhost CLI v0.8.12 for linux-amd64

problems:

• @nhost/hasura-storage-js depends on @nhost/hasura-auth-js for its types
• not new: when A depends on B depends on C, A needs to define both B and C as a dependency. Annoying.

Hi folks 👋

We've started seeing cancelled fetch requests in production.

They only happen for our customers in Thailand. Instance is in europe.

Situation

• Local machine based in the EU
• Works: no requests fail.
• Use VPN to pretend to be in other EU destinations. Always works.

Unexpected

• Visit URL from Thailand
• Use VPN to pretend to be outside of the EU. Always fails.
• requests get cancelled. No Errors

I've rolled back commits. Doesn't look like it's our application code that changed. So, I'm naturally thinking: nhost infra?

Looks like it could be one of two things. Either:

1. User data is inside the EU instance. So nhost is cancelling and failing silently.
2. The round-trip is taking too long, so the server is giving-up early

Any suggestions?

I remember it worked fine when I tried it couple months ago, but now when I'm running const { session, error} = await nhostTestStore.nhost.auth.signUp({...}) the resulting session is null - but the user is created fine

While deploying my NuxtJS application on Vercel, the hasura-auth-js is breaking for some reason. This wasn't happening until a month ago. And I didn't even change anything on my end. I'm also not getting this error locally. Everything is working fine locally.

I've tried changing multiple versions of @nhost/nhost-js. But none of them could solve this issue. Even tried falling back on v0.3.12. Even that didn't work.

Something is happening in @nhost/hasura-auth-js. Something that wasn't happening a month before.

Maybe @plmercereau can take a look at this.

ERROR in ./node_modules_dev/@nhost/hasura-auth-js/dist/index.cjs.js 1:8801
  Module parse failed: Unexpected token (1:8801)
  You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
  > var A=Object.defineProperty;var O=Object.getOwnPropertyDescriptor;var U=Object.getOwnPropertyNames,p=Object.getOwnPropertySymbols;var y=Object.prototype.hasOwnProperty,I=Object.prototype.propertyIsEnumerable;var P=(i,e,n)=>e in i?A(i,e,{enumerable:!0,configurable:!0,writable:!0,value:n}):i[e]=n,d=(i,e)=>{for(var n in e||(e={}))y.call(e,n)&&P(i,n,e[n]);if(p)for(var n of p(e))I.call(e,n)&&P(i,n,e[n]);return i};var N=i=>A(i,"__esModule",{value:!0});var T=(i,e)=>{var n={};for(var t in i)y.call(i,t)&&e.indexOf(t)<0&&(n[t]=i[t]);if(i!=null&&p)for(var t of p(i))e.indexOf(t)<0&&I.call(i,t)&&(n[t]=i[t]);return n};var x=(i,e)=>{for(var n in e)A(i,n,{get:e[n],enumerable:!0})},k=(i,e,n,t)=>{if(e&&typeof e=="object"||typeof e=="function")for(let r of U(e))!y.call(i,r)&&(n||r!=="default")&&A(i,r,{get:()=>e[r],enumerable:!(t=O(e,r))||t.enumerable});return i};var D=(i=>(e,n)=>i&&i.get(e)||(n=k(N({}),e,1),i&&i.set(e,n),n))(typeof WeakMap!="undefined"?new WeakMap:0);var L={};x(L,{HasuraAuthClient:()=>C});var m=require("xstate"),o=require("@nhost/core");var E=require("@nhost/core"),g=()=>typeof window<"u",c=i=>!i||!i.accessToken.value||!i.refreshToken.value?null:{accessToken:i.accessToken.value,accessTokenExpiresIn:(i.accessToken.expiresAt.getTime()-Date.now())/1e3,refreshToken:i.refreshToken.value,user:i.user},l=(i,e)=>{e.forEach(n=>{typeof i[n]!="function"&&console.error(`clientStorage.${n} is not a function`)})},w=(i,e)=>{if(e){if(i==="react-native"||i==="custom")return l(e,["getItem"]),n=>{var t;return(t=e.getItem)==null?void 0:t.call(e,n)};if(i==="capacitor")return l(e,["get"]),n=>{var t;return(t=e.get)==null?void 0:t.call(e,{key:n})};if(i==="expo-secure-storage")return l(e,["getItemAsync"]),n=>{var t;return(t=e.getItemAsync)==null?void 0:t.call(e,n)}}return E.defaultClientStorageGetter},R=(i,e)=>{if(e){if(i==="react-native"||i==="custom")return l(e,["setItem","removeItem"]),(n,t)=>{var r,s;t?(r=e.setItem)==null||r.call(e,n,t):(s=e.removeItem)==null||s.call(e,n)};if(i==="capacitor")return l(e,["set","remove"]),(n,t)=>{var r,s;t?(r=e.set)==null||r.call(e,{key:n,value:t}):(s=e.remove)==null||s.call(e,{key:n})};if(i==="expo-secure-storage")return l(e,["setItemAsync","deleteItemAsync"]),async(n,t)=>{var r,s;t?await((r=e.setItemAsync)==null?void 0:r.call(e,n,t)):(s=e.deleteItemAsync)==null||s.call(e,n)}}return E.defaultClientStorageSetter};var S={message:"User is already signed in",status:100},b={message:"User is not authenticated",status:101},G={message:"User is not anonymous",status:101},M={message:"Email needs verification",status:102},C=class{constructor({url:e,autoRefreshToken:n=!0,autoLogin:t=!0,clientStorage:r,clientStorageType:s="web",clientStorageGetter:u,clientStorageSetter:a,refreshIntervalTime:f,start:h=!0,Client:_=o.AuthClient}){this._client=new _({backendUrl:e,autoRefreshToken:n,autoSignIn:t,start:h,clientStorageGetter:u||w(s,r),clientStorageSetter:a||R(s,r),refreshIntervalTime:f})}async signUp(e){let n=await this.waitUntilReady(),{email:t,password:r,options:s}=e;return this.isAuthenticated()?{session:null,error:S}:new Promise(u=>{n.send({type:"SIGNUP_EMAIL_PASSWORD",email:t,password:r,options:s}),n.onTransition(a=>{if(a.matches({authentication:{signedOut:"needsEmailVerification"}}))return u({session:null,error:null});if(a.matches({authentication:{signedOut:"failed"}}))return u({session:null,error:a.context.errors.registration||null});if(a.matches({authentication:"signedIn"}))return u({session:c(a.context),error:null})})})}async signIn(e){let n=await this.waitUntilReady();if(this.isAuthenticated())return{session:null,mfa:null,error:S};if("provider"in e){let{provider:t,options:r}=e,s=(0,o.encodeQueryParameters)(`${this._client.backendUrl}/signin/provider/${t}`,(0,o.rewriteRedirectTo)(this._client.clientUrl,r));return g()&&(window.location.href=s),{providerUrl:s,provider:t,session:null,mfa:null,error:null}}return"email"in e&&"password"in e?new Promise(t=>{n.send(d({type:"SIGNIN_PASSWORD"},e)),n.onTransition(r=>{r.matches({authentication:"signedIn"})?t({session:c(r.context),mfa:null,error:null}):r.matches({authentication:{si
message.txt
5 KB

Screenshot from Vercel deployment:

• Plug a graphql-request client to nhost.graphql
• Add new getters nhost.graphql.httpUrl and nhost.graphql.wsUrl, and deprecate nhost.graphql.getUrl()
• Update the documentation

Package is bumped to major as this introduces a breaking change - let me know if you want to bump it to major instead.

Closes #1177 and #1229

It is a feature request : When a new user is asked to verify the email after signing up in local mode via mobile not with laptop , redirects to the localhost error.

Sol'n I would like to have : As user authentication is being tested locally , he should be able to verify email via mobile and would be redirected to a page acknowledgement about the verification.

Discussed in https://github.com/nhost/nhost/discussions/1464

I would like to enforce allowed roles on the backend side instead of the client like mentioned in the doc with: await nhost.auth.signUp({ email: '[email protected]', password: 'secret-password' options: { allowedRoles: ['user'] } })

This poses a security vulnerability as it could be modified client side to give other allowed roles (like admin for example?)

Is there a good way to do this ?

I was thinking of using event triggers but it would occur after the user insert and is not really advisable Another way to do it is either with postgre constraints or actions ?

The potential requirement here is: I want to securely assign a subset of allowed roles to certain user profiles. e.g. a regular user will not be able to have the role appAdmin

Thanks a lot in advance !!

It is now possible to pass on image transformation parameters in nhost.storage.getPublicUrl(). Available parameters:

• height
• width
• blur
• quality

For instance:

const url = nhost.storage.getPublicUrl({
  fileId: 'cd8eaca3-30a9-460e-b4d7-b4b7afc759c1',
  width: 800,
  blur: 20
})

missing part: test on the quality parameter, that doesn't seem to work correctly in hasura-storage

Hello 🙂 I'm having trouble connecting my nhost project to a github repository. The NHost app is already installed on github and several repositories are already linked to other NHost workspaces on different accounts. As shown on the screenshots, I can only "Connect to Github", then "Configure the app". 3 repositories are supposed to be accessible, but none is available when back on my dashboard.

Thanks for the help 🙂