@nhost/nextjs

2.1.10

Patch Changes

@nhost/react@3.4.1

2.1.9

Patch Changes

Updated dependencies [768ca17]
- @nhost/react@3.4.0

2.1.8

Patch Changes

Updated dependencies [311374e]
- @nhost/react@3.3.2

2.1.7

Patch Changes

@nhost/react@3.3.1

2.1.6

Patch Changes

Updated dependencies [49a80c2]
- @nhost/react@3.3.0

2.1.5

Patch Changes

@nhost/react@3.2.3

2.1.4

Patch Changes

@nhost/react@3.2.2

2.1.3

Patch Changes

@nhost/react@3.2.1

2.1.2

Patch Changes

Updated dependencies [017f1a6]
- @nhost/react@3.2.0

2.1.1

Patch Changes

@nhost/react@3.1.1

2.1.0

Minor Changes

b19ffed: chore: update peerDependency to support nextjs 14

Patch Changes

e5bab6a: chore: update dependencies
Updated dependencies [1a61c65]
Updated dependencies [e5bab6a]
- @nhost/react@3.1.0

2.0.2

Patch Changes

8d91f71: chore: update deps and enable pnpm audit
Updated dependencies [8d91f71]
- @nhost/react@3.0.2

2.0.1

Patch Changes

@nhost/react@3.0.1

2.0.0

Major Changes

bc9eff6e4: chore: remove support for using backendUrl when instantiating the Nhost client

Patch Changes

Updated dependencies [bc9eff6e4]
- @nhost/react@3.0.0

1.13.40

Patch Changes

@nhost/react@2.1.1

1.13.39

Patch Changes

Updated dependencies [00c363f80]
Updated dependencies [66c3193bc]
- @nhost/react@2.1.0

1.13.38

Patch Changes

Updated dependencies [4fe4a1696]
- @nhost/react@2.0.32

1.13.37

Patch Changes

@nhost/react@2.0.31

1.13.36

Patch Changes

@nhost/react@2.0.30

1.13.35

Patch Changes

@nhost/react@2.0.29

1.13.34

Patch Changes

@nhost/react@2.0.28

1.13.33

Patch Changes

@nhost/react@2.0.27

1.13.32

Patch Changes

@nhost/react@2.0.26

1.13.31

Patch Changes

Updated dependencies [b3b64a3b7]
- @nhost/react@2.0.25

1.13.30

Patch Changes

@nhost/react@2.0.24

1.13.29

Patch Changes

@nhost/react@2.0.23

1.13.28

Patch Changes

@nhost/react@2.0.22

1.13.27

Patch Changes

@nhost/react@2.0.21

1.13.26

Patch Changes

@nhost/react@2.0.20

1.13.25

Patch Changes

7fea29a8: fix: update types config and fix the exposed React components
Updated dependencies [203bc97f]
Updated dependencies [7fea29a8]
- @nhost/react@2.0.19

1.13.24

Patch Changes

@nhost/react@2.0.18

1.13.23

Patch Changes

da03bf39: chore(build): change build target to ES2019
Updated dependencies [da03bf39]
- @nhost/react@2.0.17

1.13.22

Patch Changes

90c60311: chore(deps): add types to package.json
Updated dependencies [90c60311]
- @nhost/react@2.0.16

1.13.21

Patch Changes

@nhost/react@2.0.15

1.13.20

Patch Changes

Updated dependencies [43b1b144]
- @nhost/react@2.0.14

1.13.19

Patch Changes

@nhost/react@2.0.13

1.13.18

Patch Changes

@nhost/react@2.0.12

1.13.17

Patch Changes

@nhost/react@2.0.11

1.13.16

Patch Changes

ce1ee40d: fix(nextjs): allow subdomain, region and service URLs
- @nhost/react@2.0.10

1.13.15

Patch Changes

f375eacc: fix(nextjs): accept service URLs
Updated dependencies [f375eacc]
- @nhost/react@2.0.9

1.13.14

Patch Changes

@nhost/react@2.0.8

1.13.13

Patch Changes

850a049c: chore(deps): update docker/build-push-action action to v4
Updated dependencies [850a049c]
- @nhost/react@2.0.7

1.13.12

Patch Changes

4bf40995: chore(deps): bump typescript to 4.9.5
8bb097c9: chore(deps): bump vitest
35d52aab: chore(deps): replace cross-fetch with isomorphic-unfetch
Updated dependencies [4bf40995]
Updated dependencies [8bb097c9]
- @nhost/react@2.0.6

1.13.11

Patch Changes

@nhost/react@2.0.5

1.13.10

Patch Changes

01318860: fix(nhost-js): use correct URL for functions requests
Updated dependencies [01318860]
- @nhost/react@2.0.4

1.13.9

Patch Changes

445d8ef4: chore(deps): bump @nhost/react to 2.0.3
Updated dependencies [445d8ef4]
- @nhost/react@2.0.3

1.13.8

Patch Changes

@nhost/react@2.0.2

1.13.7

Patch Changes

@nhost/react@2.0.1

1.13.6

Patch Changes

Updated dependencies [19b11d40]
Updated dependencies [19b11d40]
- @nhost/react@2.0.0

1.13.5

Patch Changes

bf1e4071: chore(deps): bump react to v18
5013213b: chore(deps): update dependency @nhost/docgen to 0.1.6
Updated dependencies [5013213b]
Updated dependencies [bf1e4071]
- @nhost/react@1.13.5

1.13.4

Patch Changes

@nhost/react@1.13.4

1.13.3

Patch Changes

@nhost/react@1.13.3

1.13.2

Patch Changes

200e9f77: chore(deps): update dependency @types/react-dom to v18.0.10
Updated dependencies [200e9f77]
- @nhost/react@1.13.2

1.13.1

Patch Changes

d42c27ae: Add explicit return types to React hooks
927be4a2: Store the session in a cookie so there is no need for an SSR page to ask for a new access token
Updated dependencies [c2706c7d]
Updated dependencies [d42c27ae]
- @nhost/react@1.13.1

1.13.0

Patch Changes

@nhost/react@1.13.0

1.12.1

Patch Changes

Updated dependencies [1be6d324]
Updated dependencies [2e8f73df]
Updated dependencies [85683547]
- @nhost/react@1.12.1

1.12.0

Minor Changes

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

Patch Changes

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

1.11.0

Minor Changes

57db5b83: Refactor: remove dependency to @nhost/core

Patch Changes

Updated dependencies [57db5b83]
- @nhost/nhost-js@1.7.0
- @nhost/react@0.17.0

1.10.0

Minor Changes

7f251111: Use NhostProvider instead of NhostReactProvider and NhostNextProvider

NhostReactProvider and NhostNextProvider are now deprecated

Patch Changes

Updated dependencies [7f251111]
- @nhost/react@0.16.0

1.9.3

Patch Changes

Updated dependencies [132a4f4b]
- @nhost/react@0.15.2

1.9.2

Patch Changes

82124329: chore(deps): update dependency next to v12.3.4

1.9.1

Patch Changes

2e6923dc: Refactoring: use xstate's interpreter.getSnapshot() instead of interpreter.state
Updated dependencies [66b4f3d0]
Updated dependencies [2e6923dc]
Updated dependencies [ef117c28]
Updated dependencies [aebb8225]
- @nhost/core@0.9.4
- @nhost/nhost-js@1.6.2
- @nhost/react@0.15.1

1.9.0

Patch Changes

Updated dependencies [4601d84e]
Updated dependencies [843087cb]
- @nhost/react@0.15.0

1.8.3

Patch Changes

53bdc294: Allow NextJs 13 as peer dependency
Updated dependencies [f2aaff05]
- @nhost/core@0.9.3
- @nhost/react@0.14.3
- @nhost/nhost-js@1.6.1

1.8.2

Patch Changes

Updated dependencies [996e8016]
Updated dependencies [996e8016]
Updated dependencies [869e7253]
Updated dependencies [996e8016]
Updated dependencies [b5395be2]
- @nhost/core@0.9.2
- @nhost/nhost-js@1.6.0
- @nhost/react@0.14.2

1.8.1

Patch Changes

Updated dependencies [6b9d163e]
- @nhost/core@0.9.1
- @nhost/react@0.14.1
- @nhost/nhost-js@1.5.2

1.8.0

Patch Changes

ba785da1: Bump dependencies versions
Updated dependencies [13c41fe6] [ba785da1] [3ced63ab] [6da44bf8]
- @nhost/core@0.9.0
- @nhost/nhost-js@1.5.1
- @nhost/react@0.14.0

1.7.7

Patch Changes

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.

1.7.6

Patch Changes

Updated dependencies [739a3c45]
Updated dependencies [739a3c45]
Updated dependencies [8e4d790b]
- @nhost/react@0.13.0
- @nhost/nhost-js@1.5.0
- @nhost/core@0.8.0

1.7.5

Patch Changes

Updated dependencies [9eb78e06]
- @nhost/core@0.7.7
- @nhost/react@0.12.5
- @nhost/nhost-js@1.4.12

1.7.4

Patch Changes

@nhost/nhost-js@1.4.11
@nhost/react@0.12.4

1.7.3

Patch Changes

@nhost/nhost-js@1.4.10
@nhost/react@0.12.3

1.7.2

Patch Changes

Updated dependencies [eb46f7d8]
- @nhost/nhost-js@1.4.9
- @nhost/react@0.12.2

1.7.1

Patch Changes

@nhost/nhost-js@1.4.8
@nhost/react@0.12.1

1.7.0

Patch Changes

10beea72: Fix React Native build: Export package.json for all npm packages.
Updated dependencies [747aa969]
Updated dependencies [10beea72]
Updated dependencies [84ba29dd]
- @nhost/core@0.7.6
- @nhost/nhost-js@1.4.7
- @nhost/react@0.12.0

1.6.2

Patch Changes

197d1d5c: - Using same cookie package (js-cookie) for both @nhost/nextjs and @nhost/core packages.
- Adding expires to avoid the cookie turning into a session cookie that some browsers aggressively destroy.
Updated dependencies [197d1d5c]
- @nhost/core@0.7.5
- @nhost/react@0.11.2
- @nhost/nhost-js@1.4.6

1.6.1

Patch Changes

Updated dependencies [6eaa5c79]
- @nhost/core@0.7.4
- @nhost/react@0.11.1
- @nhost/nhost-js@1.4.5

1.6.0

Patch Changes

Updated dependencies [4f928756]
- @nhost/react@0.11.0
- @nhost/nhost-js@1.4.4

1.5.0

Patch Changes

Updated dependencies [f9854b15]
Updated dependencies [f9854b15]
- @nhost/react@0.10.0
- @nhost/core@0.7.3
- @nhost/nhost-js@1.4.3

1.4.2

Patch Changes

dbc10e62: fixed exports field to support imports in a server-side environment
Updated dependencies [dbc10e62]
- @nhost/core@0.7.2
- @nhost/nhost-js@1.4.2
- @nhost/react@0.9.2

1.4.1

Patch Changes

Updated dependencies [b8f4b75b]
- @nhost/nhost-js@1.4.1
- @nhost/react@0.9.1

1.4.0

Patch Changes

Updated dependencies [6f0a3005]
Updated dependencies [6f0a3005]
- @nhost/nhost-js@1.4.0
- @nhost/react@0.9.0
- @nhost/core@0.7.1

1.3.0

Minor Changes

c1613394: Deanonymisation Once signed in anonymously, users can deanonymise using nhost.auth.deanonymize. Deanonymisation works the same way as email+password sign-up or passwordless sign-in. The related methods, hooks in React and composables in Vue can therefore be used for deanonymising users, such as nhost.auth.signUp, useSignUpEmailPassword, and useSignInEmailPasswordless.

Patch Changes

Updated dependencies [c1613394]
- @nhost/core@0.7.0
- @nhost/nhost-js@1.3.0
- @nhost/react@0.8.0

1.2.13

Patch Changes

08a37aae: correct rewriting options when clientUrl is not available The client URL is set to window.location.origin, so it can rewrite redirection urls that are passed on to authenticaion methods. However, clientUrl is set to '' when running on the server side. This fix then avoid raising an error when trying to rewrite redirectTo on non-browser environment, and forces useProviderLink to be rendered on the client side.
Updated dependencies [08a37aae]
- @nhost/core@0.6.5
- @nhost/react@0.7.13
- @nhost/nhost-js@1.2.4

1.2.12

Patch Changes

ebad0936: reverted ESM related changes
Updated dependencies [ebad0936]
- @nhost/core@0.6.4
- @nhost/nhost-js@1.2.3
- @nhost/react@0.7.12

1.2.11

Patch Changes

1b37b9f6: fix: ESM import path fixes
Updated dependencies [1b37b9f6]
- @nhost/core@0.6.3
- @nhost/nhost-js@1.2.2
- @nhost/react@0.7.11

1.2.10

Patch Changes

78341491: fix: Next.js and React issues with ESM packages chore: Updated output bundle names
Updated dependencies [78341491]
- @nhost/core@0.6.2
- @nhost/nhost-js@1.2.1
- @nhost/react@0.7.10

1.2.9

Patch Changes

bc11c9e5: chore: Changed copy script to support Windows fix: Fixed warnings about unknown globals occurring while building the packages
2b2f8e91: fix: ESM related issues in Node environments chore: Improved the way different formats are exposed via exports field in package.js
Updated dependencies [bc11c9e5]
Updated dependencies [2b2f8e91]
Updated dependencies [858014e4]
- @nhost/core@0.6.1
- @nhost/nhost-js@1.2.0
- @nhost/react@0.7.9

1.2.8

Patch Changes

Updated dependencies [7c8f0926]
Updated dependencies [7c8f0926]
Updated dependencies [7c8f0926]
Updated dependencies [7c8f0926]
- @nhost/core@0.6.0
- @nhost/nhost-js@1.1.14
- @nhost/react@0.7.8

1.2.7

Patch Changes

Updated dependencies [6c423394]
- @nhost/core@0.5.6
- @nhost/react@0.7.7
- @nhost/nhost-js@1.1.13

1.2.6

Patch Changes

Updated dependencies [0b58894e]
Updated dependencies [c7a407f1]
- @nhost/core@0.5.5
- @nhost/react@0.7.6
- @nhost/nhost-js@1.1.12

1.2.5

Patch Changes

9d32314: Return an error when trying sign to in/up/out from hooks while in the wrong authentication status The actions of the authentication hooks were not resolving the promise when executed from the wrong authentication status. They now return an error.
Updated dependencies [9d32314]
Updated dependencies [9d32314]
Updated dependencies [236ce72]
Updated dependencies [e094e68]
Updated dependencies [236ce72]
- @nhost/react@0.7.5
- @nhost/core@0.5.4
- @nhost/nhost-js@1.1.11

1.2.4

Patch Changes

Updated dependencies [2887ce0]
- @nhost/react@0.7.4

1.2.3

Patch Changes

584976d: - publishable directory structure changes (ESM, CJS and UMD included in the output)
- build system improvements
- fixed some bundling concerns (#428)
Updated dependencies [584976d]
- @nhost/core@0.5.3
- @nhost/nhost-js@1.1.10
- @nhost/react@0.7.3

1.2.2

Patch Changes

@nhost/nhost-js@1.1.9
@nhost/react@0.7.2

1.2.1

Patch Changes

58fa2a2: Improve loading status The loading status indicates the authentication is not yet known to the client when it starts. Once the client is ready, the authentication status is either signed in, or signed out. When the user was trying to authenticate, the loading status was set to true until the result of the authentication was known. The client now only return loading: true on startup, and in no other cases.
58fa2a2: Look for a valid refresh token both the URL and local storage When auto-signin was activated, the client was not taking into account the refresh token in the URL if a token was already stored locally. The user was then not able to authenticate from a link when the refresh token stored locally was invalid or expired. When auto-signin is activated, the client now checks and tries tokens from both the URL and the local storage, starting with the URL.
Updated dependencies [58fa2a2]
Updated dependencies [58fa2a2]
- @nhost/react@0.7.1
- @nhost/nhost-js@1.1.8

1.2.0

Minor Changes

42edb74: Adapt to React 18

Patch Changes

b56162a: prefer clientStorage/clientStorageType to clientStorageGetter/clientStorageSetter
b56162a: Introduce 'custom' client storage type
b56162a: Introduce a new 'cookie' client storage type
54e1873: Fix: add authentication headers to GraphQL operations when authenticated
Updated dependencies [54e1873]
- @nhost/nhost-js@1.1.7
- @nhost/react@0.7.0

1.1.1

Patch Changes

7b23d33: Get the refresh token in the right place in the url Hasura-auth puts the refresh token in the url as refreshToken, but it is not stored using the same key in localStorage / the cookie. This fix makes the right correspondance between the two.
- @nhost/nhost-js@1.1.6
- @nhost/react@0.6.1

1.1.0

Minor Changes

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.

Patch Changes

49545c0: Remove filtering of useLayoutEffect from logs The suppressConsoleMessage method was meant to suppress incorrect useLayoutEffect messages raised on Nextjs server-side renderings. Its implementation had an impact on the normal functionning of logging (see #447). This filtering was necessary when using former versions of xstate and can now be removed.
b52b4fc: Bump xstate to latest version (4.31.0)
Updated dependencies [d49b837]
- @nhost/react@0.6.0
- @nhost/nhost-js@1.1.5

1.0.18

Patch Changes

@nhost/nhost-js@1.1.4
@nhost/react@0.5.7

1.0.17

Patch Changes

Updated dependencies [5ee395e]
- @nhost/react@0.5.6
- @nhost/nhost-js@1.1.3

1.0.16

Patch Changes

@nhost/nhost-js@1.1.2
@nhost/react@0.5.5

1.0.15

Patch Changes

@nhost/nhost-js@1.1.1
@nhost/react@0.5.4

1.0.14

Patch Changes

Updated dependencies [ccba0b5]
- @nhost/nhost-js@1.1.0
- @nhost/react@0.5.3

1.0.13

Patch Changes

4635a14: - fixed typings of getNhostSession function (thanks to zerosym)
- added missing TSdoc to getNhostSession function

1.0.12

Patch Changes

@nhost/nhost-js@1.0.11
@nhost/react@0.5.2

1.0.11

Patch Changes

Updated dependencies [2c97db6]
- @nhost/nhost-js@1.0.10
- @nhost/react@0.5.1

1.0.10

Patch Changes

Updated dependencies [587eaff]
- @nhost/react@0.5.0
- @nhost/nhost-js@1.0.9

1.0.9

Patch Changes

@nhost/nhost-js@1.0.8
@nhost/react@0.4.7

1.0.8

Patch Changes

@nhost/nhost-js@1.0.5
@nhost/react@0.4.4

1.0.5

Patch Changes

correct dependencies

See this related issues:
- nhost
- pnpm
Updated dependencies
- @nhost/nhost-js@1.0.3
- @nhost/react@0.4.2

1.0.3

Patch Changes

@nhost/nhost-js@1.0.2
@nhost/react@0.4.1

1.0.2

Patch Changes

Updated dependencies [39df4d5]
- @nhost/react@0.4.0

1.0.1

Patch Changes

@nhost/nhost-js@1.0.1
@nhost/react@0.3.1

1.0.0

Minor Changes

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()

Name	Type	Notes
`signInAnonymous`	() => void	Registers an anonymous user
`isLoading`	boolean	Returns `true` when the action is executing, `false` when it finished its execution.
`isSuccess`	boolean	Returns `true` if the sign-up suceeded. Returns `false` if the new email needs to be verified first, or if an error occurred.
`isError`	boolean	Returns `true` if an error occurred.
`error`	{status: number, error: string, message: string} \| undefined	Provides details about the error.

Usage

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)

Name	Type	Notes
`generateQrCode`	() => void	Generates the QR code that will be used by the MFA app e.g. Google Authenticator or Authy.
`isGenerating`	boolean	Returns `true` if the QR code is generating but not yet available
`isGenerated`	boolean	Returns `true` when the QR code has been successfully generated and is available
`qrCodeDataUrl`	string	Returns the QR code as a Data URL
`activateMfa`	(code?: string) => void	Activate MFA from the code given by the MFA authentication application
`isActivating`	boolean	Returns `true` when the activation code has been sent to the server, and we await server response
`isActivated`	boolean	Returns `true` when MFA has been successfully activated
`isError`	boolean	Returns `true` if an error occurred.
`error`	{status: number, error: string, message: string} \| undefined	Provides details about the error.

Usage

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.

Patch Changes

Updated dependencies [744fd69]
- @nhost/react@0.3.0
- @nhost/nhost-js@1.0.0

0.3.1

Patch Changes

9bd01e7: Export refresh function

0.3.0

Minor Changes

0d8afde: Use @nhost/react as a peer dependency @nhost/react was bundled where it shouldn't. As a result, @nhost/react-apollo did not have access to the Nhost React context, leading to errors

Patch Changes

0d8afde: Bump xstate version 4.30.5
0d8afde: Capture the Nextjs/xstate warning about useLayoutEffect When using Xstate on the server side, Nextjs raises a warning about the use of useLayoutEffect whereas xstate is actually using an isomorphic version of layout effects. Such warnings are now captured.
Updated dependencies [0d8afde]
- @nhost/react@0.2.1

0.2.0

Minor Changes

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

Patch Changes

Updated dependencies [207ae38]
- @nhost/client@0.2.0
- @nhost/react@0.2.0

Files

CHANGELOG.md

Latest commit

History

CHANGELOG.md

File metadata and controls

@nhost/nextjs

2.1.10

Patch Changes

2.1.9

Patch Changes

2.1.8

Patch Changes

2.1.7

Patch Changes

2.1.6

Patch Changes

2.1.5

Patch Changes

2.1.4

Patch Changes

2.1.3

Patch Changes

2.1.2

Patch Changes

2.1.1

Patch Changes

2.1.0

Minor Changes

Patch Changes

2.0.2

Patch Changes

2.0.1

Patch Changes

2.0.0

Major Changes

Patch Changes

1.13.40

Patch Changes

1.13.39

Patch Changes

1.13.38

Patch Changes

1.13.37

Patch Changes

1.13.36

Patch Changes

1.13.35

Patch Changes

1.13.34

Patch Changes

1.13.33

Patch Changes

1.13.32

Patch Changes

1.13.31

Patch Changes

1.13.30

Patch Changes

1.13.29

Patch Changes

1.13.28

Patch Changes

1.13.27

Patch Changes

1.13.26

Patch Changes

1.13.25

Patch Changes

1.13.24

Patch Changes

1.13.23

Patch Changes

1.13.22

Patch Changes

1.13.21

Patch Changes

1.13.20

Patch Changes

1.13.19