• @nhost/react@3.10.0

• @nhost/react@3.9.0

• @nhost/react@3.8.0

• @nhost/react@3.7.0

• @nhost/react@3.6.0

• @nhost/react@3.5.0

• @nhost/react@3.4.0

• @nhost/react@3.3.2

• @nhost/react@3.3.0

• @nhost/react@3.2.0

• @nhost/react@3.1.0

• @nhost/react@3.0.2

• @nhost/react@3.0.0

• @nhost/react@2.1.0

• @nhost/react@2.0.32

• @nhost/react@2.0.25

• @nhost/react@2.0.19

• @nhost/react@2.0.17

• @nhost/react@2.0.16

• @nhost/react@2.0.14

• @nhost/react@2.0.10

• @nhost/react@2.0.9

• @nhost/react@2.0.7

• @nhost/react@2.0.6

• @nhost/react@2.0.4

• @nhost/react@2.0.3

• @nhost/react@2.0.0

• @nhost/react@1.13.5

• @nhost/react@1.13.2

• @nhost/react@1.13.1

• @nhost/react@1.12.1

65687bee: Remove @nhost/react from peerDepencencies

The contents of the @nhost/react package are now exported by @nhost/nextjs. As a result, It is not required to install @nhost/react alongside @nhost/nextjs.

Before:

yarn add @nhost/react @nhost/nextjs graphql

After:

yarn add @nhost/nextjs graphql

Closes #1335

b21222b3: chore(deps): update dependency @types/node to v16

54df0df4: Use initial session sent from the server

When running a SSR page, the session was correctly created from the refresh token on the server side and was sent to the client side, but was not used correctly on the client side. As a result, the client was refreshing the access token when loading the page, rather than using the access token sent by the server. The client now uses the session sent from the server.

Updated dependencies [b21222b3]

Updated dependencies [54df0df4]

Updated dependencies [54df0df4]

Updated dependencies [65687bee]

• @nhost/react@1.12.0

• @nhost/nhost-js@1.7.0
• @nhost/react@0.17.0

7f251111: Use NhostProvider instead of NhostReactProvider and NhostNextProvider

NhostReactProvider and NhostNextProvider are now deprecated

• @nhost/react@0.16.0

• @nhost/react@0.15.2

• @nhost/core@0.9.4
• @nhost/nhost-js@1.6.2
• @nhost/react@0.15.1

• @nhost/react@0.15.0

• @nhost/core@0.9.3
• @nhost/react@0.14.3
• @nhost/nhost-js@1.6.1

• @nhost/core@0.9.2
• @nhost/nhost-js@1.6.0
• @nhost/react@0.14.2

• @nhost/core@0.9.1
• @nhost/react@0.14.1
• @nhost/nhost-js@1.5.2

• @nhost/core@0.9.0
• @nhost/nhost-js@1.5.1
• @nhost/react@0.14.0

1e31a956: read nextjs context cookies in createServerSideClient

8eafa198: Fix createServerSideClient

The refresh token was not fetched from the cookie when using createServerSideClient since this PR. It is now fixed.

• @nhost/react@0.13.0
• @nhost/nhost-js@1.5.0
• @nhost/core@0.8.0

• @nhost/core@0.7.7
• @nhost/react@0.12.5
• @nhost/nhost-js@1.4.12

• @nhost/nhost-js@1.4.9
• @nhost/react@0.12.2

• @nhost/core@0.7.6
• @nhost/nhost-js@1.4.7
• @nhost/react@0.12.0

• Adding expires to avoid the cookie turning into a session cookie that some browsers aggressively destroy.

• @nhost/core@0.7.5
• @nhost/react@0.11.2
• @nhost/nhost-js@1.4.6

• @nhost/core@0.7.4
• @nhost/react@0.11.1
• @nhost/nhost-js@1.4.5

• @nhost/react@0.11.0
• @nhost/nhost-js@1.4.4

• @nhost/react@0.10.0
• @nhost/core@0.7.3
• @nhost/nhost-js@1.4.3

• @nhost/core@0.7.2
• @nhost/nhost-js@1.4.2
• @nhost/react@0.9.2

• @nhost/nhost-js@1.4.1
• @nhost/react@0.9.1

• @nhost/nhost-js@1.4.0
• @nhost/react@0.9.0
• @nhost/core@0.7.1

• @nhost/core@0.7.0
• @nhost/nhost-js@1.3.0
• @nhost/react@0.8.0

• @nhost/core@0.6.5
• @nhost/react@0.7.13
• @nhost/nhost-js@1.2.4

• @nhost/core@0.6.4
• @nhost/nhost-js@1.2.3
• @nhost/react@0.7.12

• @nhost/core@0.6.3
• @nhost/nhost-js@1.2.2
• @nhost/react@0.7.11

• @nhost/core@0.6.2
• @nhost/nhost-js@1.2.1
• @nhost/react@0.7.10

• @nhost/core@0.6.1
• @nhost/nhost-js@1.2.0
• @nhost/react@0.7.9

• @nhost/core@0.6.0
• @nhost/nhost-js@1.1.14
• @nhost/react@0.7.8

• @nhost/core@0.5.6
• @nhost/react@0.7.7
• @nhost/nhost-js@1.1.13

• @nhost/core@0.5.5
• @nhost/react@0.7.6
• @nhost/nhost-js@1.1.12

• @nhost/react@0.7.5
• @nhost/core@0.5.4
• @nhost/nhost-js@1.1.11

• @nhost/react@0.7.4

• build system improvements
• fixed some bundling concerns (#428)

• @nhost/core@0.5.3
• @nhost/nhost-js@1.1.10
• @nhost/react@0.7.3

• @nhost/react@0.7.1
• @nhost/nhost-js@1.1.8

• @nhost/nhost-js@1.1.7
• @nhost/react@0.7.0

• @nhost/nhost-js@1.1.6
• @nhost/react@0.6.1

b52b4fc: Introduce createServerSideNhostClient Until now, the Nhost client was not functionning correctly on the server side. The createServerSideNhostClient can be called inside the getServerSideProps function of a page. When called, it will try to get the refesh token in cookies, or from the request URL. If a refresh token is found, it uses it to get an up to date access token (JWT) and a user session This method returns a promise of an NhostClient and resolves only when the authentication status is known eventually.

getNhostSession now uses the above method under the hood to extract the user session and hydrate the NhostClient context on the client side.

616e320: Look for the refresh token both in the query parameters and in the hash Until now, after redirecting from an email, Hasura-auth puts refresh tokens in the hash part of the url. It is a problem when using SSR as the hash is not accessible to the server. This behaviour is likely to change. As a result, the client now parses both the hash and the query parameters of the url. See this issue to keep track of the progress on Hasura-auth.

• @nhost/react@0.6.0
• @nhost/nhost-js@1.1.5

• @nhost/react@0.5.6
• @nhost/nhost-js@1.1.3

• @nhost/nhost-js@1.1.0
• @nhost/react@0.5.3

• added missing TSdoc to getNhostSession function

• @nhost/nhost-js@1.0.10
• @nhost/react@0.5.1

• @nhost/react@0.5.0
• @nhost/nhost-js@1.0.9

correct dependencies

See this related issues:

• nhost
• pnpm

Updated dependencies

• @nhost/nhost-js@1.0.3
• @nhost/react@0.4.2

• @nhost/react@0.4.0

744fd69: Introducing useSendVerificationEmail

While useSignInEmailPassword automatically sends a verification email (when the backend is configured to do so), an user may sometime want to request for an verification email to be sent again. See the documentation for further information about how to use this hook.

744fd69: Rename hooks and their methods to make them more explicit

• useEmailPasswordlessSignIn

  • Hook renamed to useSignInEmailPasswordless
  • signIn renamed to signInEmailPasswordless

• useEmailPasswordSignIn

  • Hook renamed to useSignInEmailPassword
  • signIn renamed to signInEmailPassword
  • needsVerification renamed to needsEmailVerification

• useEmailPasswordSignUp

  • Hook renamed to useSignUpEmailPassword
  • signUp renamed to signUpEmailPassword
  • needsVerification renamed to needsEmailVerification

• useAnonymousSignIn

  • Hook renamed to useSignInAnonymous
  • renamed signIn to signInAnonymous

• useChangeEmail

  • needsVerification renamed to needsEmailVerification

744fd69: Introducing useSignInAnonymous

Anonymous Sign-In is a feature that allows users to get a temporary id without attaching yet any personal information such as an email or a passowrd.

Anonymous users can then run GraphQL operations, with a specific public role that is distinct from the default user role. The anonymous can then "deanonymize" their account at a later stage in attaching the missing registration information and an authentication method.

Note Anonymous Sign-In is not available out of the box yet in the Nhost cloud, but will be available in the near future.

Note 2 The deanonymisation process is not yet available. This is also part of our roadmap.

const { signInAnonymous, isLoading, isSuccess, isError, error } = useSignInAnonymous()

import { useSignInAnonymous } from '@nhost/react'

const Component = () => {
  const { signInAnonymous, isSuccess } = useSignInAnonymous(email, password)
  return (
    <div>
      <button onClick={signInAnonymous}>Anonymous sign-in</button>
      {isSuccess && <div>You are now signed in anonymously</div>}
    </div>
  )
}

744fd69: Add options to useProviderLink

Since Hasura Auth version 0.4, it is possible to pass on options when signing up or signin in through an OAuth provider. It is now possible to determine these options in the useProviderLink, so it generates the right URL when using the provider links.

See the React documentation for additional information.

744fd69: Time-based One-Time Password Multi-Factor Authentication

Note MFA is not available out of the box yet in the Nhost cloud, but will be available in the near future.

When enabled in the backend, users that signed up with an email and a password can opt-in for an additional authentication security measure. MFA can be activated in using the new useConfigMfa hook.

Two methods has been also added to useEmailPasswordSignIn: when MFA is active, authentication won't be a success straight after signin up with an email and a password. The new needsMfaOtp will then appear as true, and the authentication will succeed only when the user will have sent back the OTP code with sendMfaOtp(code:string).

const { generateQrCode, isGenerating, isGenerated, qrCodeDataUrl, activateMfa, isActivating, isActivated, isError, error } =
  useConfigMfa(code?: string)

import { useConfigMfa } from '@nhost/react'
import { useState } from 'react'

export const Mfa: React.FC = () => {
  const [code, setCode] = useState('')
  const { generateQrCode, activateMfa, isActivated, isGenerated, qrCodeDataUrl } =
    useConfigMfa(code)

  return (
    <div>
      {!isGenerated && (
        <button block appearance="primary" onClick={generateQrCode}>
          Generate
        </button>
      )}
      {isGenerated && !isActivated && (
        <div>
          <img alt="qrcode" src={qrCodeDataUrl} />
          <input value={code} onChange={onChange={(event) => setCode(event.target.value)}} placeholder="Enter activation code" />
          <button block appearance="primary" onClick={activateMfa}>
            Activate
          </button>
        </div>
      )}
      {isActivated && <div>MFA has been activated!!!</div>}
    </div>
  )
}

744fd69: Unify vanilla, react and next APIs so they can work together React and NextJS libraries now works together with @nhost/nhost-js. It also means the Nhost client needs to be initiated before passing it to the React provider. See the React and NextJS configuration documentation for additional information.

• @nhost/react@0.3.0
• @nhost/nhost-js@1.0.0

• @nhost/react@0.2.1

207ae38: New NextJS client

Introducting a new @nhost/nextjs package. It is designed to keep the refresh token between the browser and the Next.js server with a cookie. SSR routes should fetch the session in getServerSideProps into a nhostSession pageProps in using the getNhostSession method.

Every @nhost/react hook is compatible with this package.

See the documentation for further information.

Closes #110 and #180

• @nhost/client@0.2.0
• @nhost/react@0.2.0