• @nhost/nhost-js@3.2.0

• @nhost/nhost-js@3.1.2

• @nhost/nhost-js@3.1.0

• @nhost/nhost-js@3.0.10

• @nhost/nhost-js@3.0.3

• @nhost/nhost-js@3.0.2

• @nhost/nhost-js@3.0.0

• @nhost/nhost-js@2.2.18

• @nhost/nhost-js@2.2.17

• @nhost/nhost-js@2.2.10

• @nhost/nhost-js@2.2.9

• @nhost/nhost-js@2.2.6

• @nhost/nhost-js@2.2.5

• @nhost/nhost-js@2.2.3

• @nhost/nhost-js@2.2.2

• @nhost/nhost-js@2.2.1

• @nhost/nhost-js@2.2.0

• @nhost/nhost-js@2.2.0

• @nhost/nhost-js@2.1.0

• @nhost/nhost-js@2.0.9

• @nhost/nhost-js@2.0.8

• @nhost/nhost-js@2.0.7

• @nhost/nhost-js@2.0.6

• @nhost/nhost-js@2.0.5

• @nhost/nhost-js@2.0.4

• @nhost/nhost-js@2.0.3

• @nhost/nhost-js@2.0.2

19b11d40: Remove deprecated signatures in React hooks

It is now not possible to send the input values of the following hooks when creating them:

• useChangeEmail
• useChangePassword
• useResetPassword
• useSendVerificationEmail
• useSignInEmailPassword
• useSignInEmailPasswordless
• useSignUpEmailPassword

For instance, it is not possible to do the following:

const [email, setEmail] = useState('')
const { changeEmail } = useChangeEmail(email)

const handleSubmit = async (e: React.SyntheticEvent<HTMLFormElement>) => {
    e.preventDefault()
    await changeEmail()
}

return <form onSubmit={ handleSubmit }>
            <input value={email} onChange={onChange={(event) => setEmail(event.target.value)}}  />
       </form>

Instead, write:

const [email, setEmail] = useState('')
const { changeEmail } = useChangeEmail()

const handleSubmit = async (e: React.SyntheticEvent<HTMLFormElement>) => {
    e.preventDefault()
    await changeEmail(email)
}

return <form onSubmit={ handleSubmit }>
            <input value={email} onChange={onChange={(event) => setEmail(event.target.value)}}  />
       </form>

19b11d40: Remove deprecated hooks

• useNhostAuth: use useNhostClient instead
• useAuthLoading: use useAuthenticationStatus instead
• useAvatarUrl: use useUserAvatarUrl instead.
• useDefaultRole: use useUserDefaultRole instead.
• useDisplayName: use useUserDisplayName instead.
• useEmail: use useUserEmail instead.
• useIsAnonymous: use useUserIsAnonymous instead.
• useNhostBackendUrl: use useNhostClient instead, then the urls in the respective nhost.<auth,storage,graphql,functions> clients

• @nhost/nhost-js@2.0.0

• @nhost/nhost-js@1.13.4

• @nhost/nhost-js@1.13.1

c2706c7d: Export commonly used types

BackendUrl, ErrorPayload, NhostSession, Subdomain, and User are now exported in all our SDKs

d42c27ae: Add explicit return types to React hooks

• @nhost/nhost-js@1.12.1

65687bee: Remove @nhost/nhost-js from peerDepencencies

The contents of the @nhost/nhost-js package are now exported by @nhost/react.

• @nhost/nhost-js@1.12.0

• @nhost/hasura-auth-js@1.7.0
• @nhost/hasura-storage-js@0.8.0
• @nhost/nhost-js@1.7.0

7f251111: Use NhostProvider instead of NhostReactProvider and NhostNextProvider

NhostReactProvider and NhostNextProvider are now deprecated

• @nhost/core@0.9.4
• @nhost/hasura-storage-js@0.7.4
• @nhost/nhost-js@1.6.2

• @nhost/core@0.9.3
• @nhost/hasura-storage-js@0.7.3
• @nhost/nhost-js@1.6.1

• @nhost/core@0.9.2
• @nhost/hasura-storage-js@0.7.2
• @nhost/nhost-js@1.6.0

• @nhost/core@0.9.1
• @nhost/hasura-storage-js@0.7.1
• @nhost/nhost-js@1.5.2

• @nhost/core@0.9.0
• @nhost/hasura-storage-js@1.0.0
• @nhost/nhost-js@1.5.1

739a3c45: Sign up with an email and a security key.

Use the hook useSignUpEmailSecurityKey to sign up a user with security key and an email using the WebAuthn API.

const { signUpEmailSecurityKey, needsEmailVerification, isLoading, isSuccess, isError, error } =
  useSignUpEmailSecurityKey()

console.log({ needsEmailVerification, isLoading, isSuccess, isError, error })

const handleFormSubmit = async (e) => {
  e.preventDefault()
  await signUpEmailSecurityKey('joe@example.com')
}

• @nhost/nhost-js@1.5.0
• @nhost/core@0.8.0
• @nhost/hasura-storage-js@1.0.0

• @nhost/core@0.7.7
• @nhost/hasura-storage-js@0.6.1
• @nhost/nhost-js@1.4.12

• @nhost/hasura-storage-js@0.6.0
• @nhost/nhost-js@1.4.10

• @nhost/nhost-js@1.4.9

84ba29dd: Introduce useSignInSmsPasswordless

const { signInSmsPasswordless, sendOtp, needsOtp, isLoading, isSuccess, isError, error } =
  useSignInSmsPasswordless()

1. The signInSmsPasswordless action will send a one-time password to the given phone number.
2. The client is then awaiting the OTP. needsOtp equals true
3. After the code is received by SMS, the client sends the code with sendOtp. On success, the client is authenticated, and isSuccess equals true.

Any error is monitored through isError and error. While the signInSmsPasswordless and sendOtp actions are running, isLoading equals true

• @nhost/core@0.7.6
• @nhost/hasura-storage-js@0.5.3
• @nhost/nhost-js@1.4.7

• @nhost/core@0.7.5
• @nhost/hasura-storage-js@0.5.2
• @nhost/nhost-js@1.4.6

• @nhost/core@0.7.4
• @nhost/hasura-storage-js@0.5.1
• @nhost/nhost-js@1.4.5

4f928756: Extend file upload parameters

• bucketId is available everywhere as an option
• It is possible to pass files as a parameter on a multiple upload, making the add action optional.
• The add and upload actions of multiple file upload accepts both a File, an array of File items, and a FileList

• @nhost/hasura-storage-js@0.5.0
• @nhost/nhost-js@1.4.4

• @nhost/hasura-storage-js@0.4.0
• @nhost/core@0.7.3
• @nhost/nhost-js@1.4.3

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

• @nhost/nhost-js@1.4.1

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

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

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

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

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

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

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

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

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

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

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

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

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

• @nhost/nhost-js@1.1.8

b56162a: prefer clientStorage/clientStorageType to clientStorageGetter/clientStorageSetter

1fb51a7: Rename user data hooks to make them all start with userUser... The hooks that help to access user data were not consistently named. The following hooks have been therefore renamed:

• useAvatarUrl -> useUserAvatarUrl
• useDefaultRole -> useUserDefaultRole
• useDisplayName -> useUserDisplayName
• useEmail -> useUserEmail
• useIsAnonymous -> useUserIsAnonymous

Their former names are still available for backwards compatibility, but are flagged as deprecated.

54e1873: Fix: add authentication headers to GraphQL operations when authenticated

Updated dependencies [185f39e]

• @nhost/nhost-js@1.1.7

• @nhost/nhost-js@1.1.5

• @nhost/nhost-js@1.1.3

• @nhost/nhost-js@1.1.0

• @nhost/nhost-js@1.0.10

7135aee: Add user and accessToken to authentication hooks

Hooks that can complete a successful authentication now have two additional user and accessToken exported states:

• useSignInEmailPassword
• useSignInAnonymous
• useSignUpEmailPassword

587eaff: Return a promise with the current context to hooks actions It is now possible to get the result of an action. Hook handlers return the action context in a promise.

const { signInEmailPasswordless, isError } = useSignInEmailPasswordless()
const MyComponent = () => {
    return <div>
                <button onClick={async () => {
                    const { isSuccess, isError, error } = await signInEmailPasswordless('johan@ikea.se')
                    if (isError) {
                        console.log(error)
                    }}}/>
                {isError && <div>an error occurred</div>}
            <div>
}

7cf875f: Deprecate the use of values sent as hook parameters

Although handlers parameters of authentication hooks can be given when creating the hook, it is recommended to use them when executing the handler. For instance, instead of:

const { signInEmailPasswordless } = useSignInEmailPasswordless('nuno@fcporto.pt')
signInEmailPasswordless()

It is recommended to use the following syntax:

const { signInEmailPasswordless } = useSignInEmailPasswordless()
signInEmailPasswordless('nuno@fcporto.pt')

No breaking change has been introduced. For instance, useSignUpEmailPassword('szilard@brussels.be','1234', options) will appear as deprecated but will work, while useSignUpEmailPassword(options) will work too.

• @nhost/nhost-js@1.0.9

correct dependencies

See this related issues:

• nhost
• pnpm

Updated dependencies

• @nhost/nhost-js@1.0.3

39df4d5: Deprecate useAuthLoading and introduce useAuthenticationStatus When using both useAuthLoading and useAuthenticated together, the hooks rerender independently from each other. As a result, when a user loads the page while he previously authenticated, the hooks values were chronologically:

The intermediate (false, false) is incorrect and is causing issues when using an authentication gate.

It is therefore recommended to stop using useAuthLoading, and to use useAuthenticationStatus instead, in order to keep the loading state and the authentication in sync within the same hook.

Usage:

const { isLoading, isAuthenticated } = useAuthenticationStatus()

Fixes this issue

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/nhost-js@1.0.0

• @nhost/client@0.2.1

207ae38: New React client

This release brings a full rewrite of the React client, to make it tree shakable and fully reactive. See the documentation for further information.

• useAccessToken
• useAnonymousSignIn
• useAuthenticated
• useChangeEmail
• useChangePassword
• useEmail
• useEmailPasswordlessSignIn
• useEmailPasswordSignIn
• useEmailPasswordSignUp
• useIsAnonymous
• useAuthLoading
• useNhost
• useNhostBackendUrl
• useNhostInterpreter
• useResetPassword
• useSignOut
• useUserData
• useUserLocale
• the useNhostAuth has not been included. Use useAuthenticated together with useAuthLoading and useUserData instead

Closes #189, #127, #186, and #195

• @nhost/client@0.2.0