Nuxt Hanko

Hanko integration for Nuxt

✨ Easy integration for Hanko
🧱 Type safety and auto-registration for Hanko web components
💪 Server utilities for full-stack auth

Installation

Install and add @nuxtjs/hanko to your nuxt.config.

npx nuxi@latest module add hanko

export default defineNuxtConfig({
  modules: ['@nuxtjs/hanko'],
  hanko: {
    // You can also configure this by setting NUXT_PUBLIC_HANKO_API_URL at runtime
    apiURL: '<YOUR_API_URL>',
    // You can also customise these if required
    // cookieName: 'hanko'
    // redirects: {
    //   login: '/login',
    //   success: '/',
    //   home: '/',
    //   followRedirect: true
    // },
    // registerComponents: true,
    // augmentContext: true,
  },
})

To use, you can use the Hanko components anywhere in your app: <hanko-auth>, <hanko-events> and <hanko-profile>. These are web components that will be rendered on the client-side only. Props are typed.

You can turn auto-registration of components off (if you wish to use Hanko just on the server side or programmatically) with registerComponents: false.

Check out the Hanko documentation to learn more.

<template>
  <hanko-auth />
</template>

Middleware

By default two new route middleware are available in your Nuxt app: hanko-logged-in and hanko-logged-out.

hanko-logged-in will prevent access to a page unless you are logged in. (It will redirect you to redirects.login instead, and then redirect back to this page once you login. You can disable this behaviour by setting redirects.followRedirect to false.)
hanko-logged-out will prevent access to a page unless you are logged out. (It will redirect you to redirects.success when you log in, and otherwise to redirects.home.)

You can also create your own middleware for full control.

Auto-imports

useHanko is exposed in the Vue part of your app to allow you direct access to the Hanko API. You can access the current user and much more. Note: It will return null on the server.

Server utilities

By default you can access a verified JWT context on event.context.hanko. (It will be undefined if the user is not logged in.) If you want to handle this yourself you can set augmentContext: false.

verifyHankoEvent is exposed in the Nitro part of your app to expose the underlying utility used to create event.context.hanko if you want to handle things manually.