elements

Hanko elements

Provides web components that will bring a modern login and registration experience to your users. It integrates the Hanko API, a backend that provides the underlying functionalities.

Features

• Registration and login flows with and without passwords
• Passkey authentication
• Passcodes, a convenient way to recover passwords and verify email addresses
• Email, Password and Passkey management
• Customizable UI

Installation

# npm
npm install @teamhanko/hanko-elements

# yarn
yarn add @teamhanko/hanko-elements

# pnpm
pnpm install @teamhanko/hanko-elements

Usage

Script

To use the web components, you need to register them using the register() function provided by the hanko-elements package.

Module Usage:

import { register } from "@teamhanko/hanko-elements";

CDN Usage (with a script tag):

<script type="module">
  import { register } from "https://cdn.jsdelivr.net/npm/@teamhanko/hanko-elements/dist/elements.js";
</script>

After importing the register() function, call it with the URL of the Hanko API as an argument to register the Hanko elements with the browser's CustomElementRegistry.

const { hanko } = await register("https://hanko.yourdomain.com");

You can also pass certain options:

const defaultOptions = {
  shadow: true,                  // Set to false if you do not want the web component to be attached to the shadow DOM.
  injectStyles: true,            // Set to false if you do not want to inject any default styles.
  enablePasskeys: true,          // Set to false if you do not want to display passkey-related content.
  translations: null,            // Additional translations can be added here. English is used when the option is not
                                 // present or set to `null`, whereas setting an empty object `{}` prevents the elements
                                 // from displaying any translations.
  translationsLocation: "/i18n", // The URL or path where the translation files are located.
  fallbackLanguage: "en",        // The fallback language to be used if a translation is not available.
};

const { hanko } = await register("https://hanko.yourdomain.com", defaultOptions);

<hanko-auth>

A web component that handles user login and user registration.

Markup

<hanko-auth lang="en"></hanko-auth>

Attributes

• lang Used to specify the language of the content within the element. See Translations.
• experimental A space-separated list of experimental features to be enabled. See experimental features.

<hanko-profile>

A web component that allows to manage emails, passwords and passkeys.

Markup

<hanko-profile lang="en"></hanko-profile>

Attributes

• lang Used to specify the language of the content within the element. See Translations.

<hanko-events>

A web component that allows to bind event handler to certain events, without displaying UI elements. Events can be subscribed to with the <hanko-auth> and <hanko-profile> components in the same manner. Also, you can bind event handler via the frontend-sdk (see next section).

Markup

<hanko-events id="events"></hanko-events>
<script>
  document.getElementById("events").addEventListener("onAuthFlowCompleted", console.log)
  // more events are available (see "frontend-sdk" docs)...
</script>

Frontend-SDK Examples

The following examples will cover some common use-cases for the hanko-frontend-sdk instance returned by the register() function, but please take a look into the frontend-sdk docs for details.

Note that you can create a hanko-frontend-sdk instance without having to register the web components as follows:

import { Hanko } from "@teamhanko/hanko-elements";

const hanko = new Hanko("https://hanko.yourdomain.com")

Events

It is possible to bind callbacks to different custom events in use of the SDKs event listener functions. The callback function will be called when the event happens and an object will be passed in, containing event details.

• "hanko-auth-flow-completed": Will be triggered after a session has been created and the user has completed possible additional steps (e.g. passkey registration or password recovery) via the <hanko-auth> element.

hanko.onAuthFlowCompleted((authFlowCompletedDetail) => {
  // Login, registration or recovery has been completed successfully. You can now take control and redirect the
  // user to protected pages.
  console.info(`User successfully completed the registration or authorization process (user-id: "${authFlowCompletedDetail.userID}")`);
})

• "hanko-session-created": Will be triggered before the "hanko-auth-flow-completed" happens, as soon as the user is technically logged in. It will also be triggered when the user logs in via another browser window. The event can be used to obtain the JWT. Please note, that the JWT is only available, when the Hanko-API configuration allows to obtain the JWT. When using Hanko-Cloud the JWT is always present, for self-hosted Hanko-APIs you can restrict the cookie to be readable by the backend only, as long as your backend runs under the same domain as your frontend. To do so, make sure the config parameter "session.enable_auth_token_header" is turned off via the Hanko-API configuration. If you want the JWT to be contained in the event details, you need to turn on "session.enable_auth_token_header" when using a cross-domain setup. When it's a same-domain setup you need to turn off "session.cookie.http_only" to make the JWT accessible to the frontend.

hanko.onSessionCreated((sessionDetail) => {
  // A new JWT has been issued.
  console.info(`Session created or updated (user-id: "${sessionDetail.userID}", jwt: ${sessionDetail.jwt})`);
})

• "hanko-session-resumed": Will be triggered after the page has been loaded and there is a valid session, so it can be utilized like the "hanko-auth-flow-completed" event, to restore the state of your page, where the user is logged in. Note, that a "hanko-session-not-present" event will be triggered instead of the "hanko-session-resumed" event, after the page has been loaded, when the user does not have a valid session.

hanko.onSessionResumed((sessionDetail) => {
  // The user is logged in, protected content can be shown.
  console.info(`User is already logged in (user-id: "${sessionDetail.userID}", jwt: ${sessionDetail.jwt})`);
})

• "hanko-session-expired": Will be triggered when the session has expired, or when the session has been removed in another browser window, because the user has logged out, or deleted the account.

hanko.onSessionExpired(() => {
  // You can redirect the user to a login page or show the `<hanko-auth>` element, or to prompt the user to log in again.
  console.info("Session expired");
})

• "hanko-user-logged-out": Will be triggered, when the user actively logs out. In other browser windows, a "hanko-session-expired" event will be triggered at the same time.

hanko.onUserLoggedOut(() => {
  // You can redirect the user to a login page or show the `<hanko-auth>` element.
  console.info("User logged out");
})

• "hanko-user-deleted": Will be triggered when the user has deleted the account. In other browser windows, a "hanko-session-expired" event will be triggered at the same time.

hanko.onUserDeleted(() => {
  // You can redirect the user to a login page or show the `<hanko-auth>` element.
  console.info("User has been deleted");
})

To learn what else you can do, check out the custom-events README.

User Client

The SDK contains several client classes to make the communication with the Hanko-API easier. Here some examples of things you might want to do:

• Getting the current user:

const user = await hanko.user.getCurrent();
console.info(`id: ${user.id}, email: ${user.email}`)

• Log out a user:

await hanko.user.logout();

To learn how error handling works and what else you can do with SDK, take a look into the frontend-sdk docs.

UI Customization

CSS Variables

CSS variables can be used to style the hanko-auth and hanko-profile elements to your needs. A list of all CSS variables including default values can be found below:

hanko-auth, hanko-profile {
  /* Color Scheme */
  --color: #171717;
  --color-shade-1: #8f9095;
  --color-shade-2: #e5e6ef;

  --brand-color: #506cf0;
  --brand-color-shade-1: #6b84fb;
  --brand-contrast-color: white;

  --background-color: white;
  --error-color: #e82020;
  --link-color: #506cf0;

  /* Font Styles */
  --font-weight: 400;
  --font-size: 14px;
  --font-family: sans-serif;

  /* Border Styles */
  --border-radius: 4px;
  --border-style: solid;
  --border-width: 1px;

  /* Item Styles */
  --item-height: 34px;
  --item-margin: .5rem 0;

  /* Container Styles */
  --container-padding: 0;
  --container-max-width: 600px;

  /* Headline Styles */
  --headline1-font-size: 24px;
  --headline1-font-weight: 600;
  --headline1-margin: 0 0 .5rem;

  --headline2-font-size: 14px;
  --headline2-font-weight: 600;
  --headline2-margin: 1rem 0 .25rem;

  /* Divider Styles */
  --divider-padding: 0 42px;
  --divider-visibility: visible;

  /* Link Styles */
  --link-text-decoration: none;
  --link-text-decoration-hover: underline;

  /* Input Styles */
  --input-min-width: 12em;

  /* Button Styles */
  --button-min-width: max-content;
}

CSS Shadow Parts

In addition to the CSS variables, there is the possibility of using the ::part selector to equip various elements with your own styles.

Please note that shadow parts only work when the web components are attached to the shadow DOM:

register("https://hanko.yourdomain.com", { shadow: true })

The following parts are available:

• container - the UI container
• headline - the headline of each page
• paragraph - the paragraph elements
• button - every button element
• primary-button - the primary button
• secondary-button - the secondary button on the email login page
• input - every input field
• text-input - every input field not used for passcodes
• passcode-input - the passcode input fields
• link - the links in the footer section
• error - the error message container
• error-text - the error message
• divider - the horizontal divider on the login page
• divider-text - the divider text
• divider-line - the line before and after the divider-text
• form-item - the container of a form item, e.g. an input field or a button

CSS classes (not recommended)

There is also the possibility to provide your own CSS rules when the web component has not been attached to the shadow DOM:

register("https://hanko.yourdomain.com", { shadow: false })

Please take a look at the CSS example file to see which CSS rules can be used. If you only want to change specific properties you can override the predefined ones. For example if you like to change the background color, include the following CSS rule:

.hanko_container {
  background-color: blue !important;
}

Also, you can prevent injecting any styles:

register("https://hanko.yourdomain.com", { shadow: false, injectStyles: false })

so you don't need to override properties but provide the entirety of CSS rules:

.hanko_container {
  background-color: blue;
}

/* more css rules... */

If this is your preferred approach, start with the CSS example file, change everything according to your needs and include the CSS in your page.

Keep in mind we made CSS classes available and added light DOM support only because a Safari bug is breaking the autocompletion of input elements while the web component is attached to the shadow DOM. You would normally prefer to attach the component to the shadow DOM and make use of CSS parts for UI customization when the CSS variables are not sufficient.

Translations

Default Behavior

The hanko-elements package includes English translations by default and the lang attribute can be omitted.

Script:

register("https://hanko.yourdomain.com");

Markup:

<hanko-auth></hanko-auth>

Installing Additional Translations

Translations are currently available for the following languages:

• "de" - German
• "en" - English
• "fr" - French

You can import them individually:

// Replace the paths below with
// "https://cdn.jsdelivr.net/npm/@teamhanko/hanko-elements/dist/i18n/{en|de|all|...}.js"
// if you're using CDN.

import { de } from "@teamhanko/hanko-elements/i18n/de";
import { en } from "@teamhanko/hanko-elements/i18n/en";
import { fr } from "@teamhanko/hanko-elements/i18n/fr";

Or import all translations at once:

import { all } from "@teamhanko/hanko-elements/i18n/all";

After importing, provide the translations through the register() function:

register("https://hanko.yourdomain.com", { translations: { de, en, fr } });

// or

register("https://hanko.yourdomain.com", { translations: all });

You can now set the lang attribute of the element to the desired language:

<hanko-auth lang="de"></hanko-auth>

Modifying Translations

You can modify existing translations as follows:

import { en } from "@teamhanko/hanko-elements/i18n/en";

en.errors.somethingWentWrong = "Aww, snap!";

register("https://hanko.yourdomain.com", { translations: { en } });

Adding New Translations

If you need to create a new translation, pass an object that implements (or partially implements) the Translation interface.

Script:

import { all } from "@teamhanko/hanko-elements/i18n/all";
import { Translation } from "@teamhanko/hanko-elements"; // if you're using typescript

const myLang: Translation = { ... }

register("https://hanko.yourdomain.com", { translations: { ...all, myLang } });

Markup:

<hanko-auth lang="myLang"></hanko-auth>

Using External Files

For languages provided via the element's lang attribute, or via the fallback language option, that are not included in the object passed to the translations option, the component will fetch a JSON file from the location specified by the translationsLocation option. For example, if "en" is missing due to an empty object being passed, as shown in the example below, the component will fetch a file named "/i18n/en.json".

Script:

register("https://hanko.yourdomain.com", {
  translations: {},             // An empty object, so even the default "en" translation won't be available.
  translationsLocation: "/i18n" // A public folder containing language files, e.g., "en.json".
});

Markup:

<!-- Will fetch "/i18n/en.json" -->
<hanko-auth lang="en"></hanko-auth>

Fallback Language

The fallbackLanguage option is used to specify a fallback language for the web components when translations are missing or incomplete for a particular language. By setting the fallbackLanguage option to a valid language string like "en" or "de", the missing translation strings will be automatically retrieved from the specified fallback language. When the translation for the specified fallbackLanguage is not available in the translations option, the web components will attempt to fetch it from an external file.

Script:

import { en } from "@teamhanko/hanko-elements/i18n/en";
import { Translation } from "@teamhanko/hanko-elements";

const symbols: Partial<Translation> = {
  labels: { continue: "➔" }
};

register("https://hanko.yourdomain.com", {
  fallbackLanguage: "en",
  translations: { en, symbols }
});

Markup:

<!-- Will appear in English, but the "continue" button label will be "➔"  -->
<hanko-auth lang="symbols"></hanko-auth>

Experimental Features

Conditional Mediation / Autofill assisted Requests

<hanko-auth [...] experimental="conditionalMediation"/>

If the browser supports autofill assisted requests, it will hide the "Sign in with passkey" button on the login page and instead present the available passkeys via the email input's autocompletion menu. Enabling this feature will currently cause the following issues:

• On iOS 16/Safari you may encounter an issue that WebAuthn credential registration is not working the first time you press the button or only after reloading the page.

• Microsoft Edge v. 108 sometimes crashes or is not able to display the credential name properly.

Demo

Take a look at our live demo.

Frontend framework integrations

To learn more about how to integrate the Hanko elements into frontend frameworks, see our guides in the official documentation and our example applications.

Exports

The @teamhanko/hanko-elements package exports the functions and interfaces listed below and additionally every declaration provided by the frontend-sdk.

Functions

• register - A function to register the web components with the browser's custom element registry.

Interfaces

• RegisterOptions - represents the options of the register() function.
• RegisterResult - represents the return value of the register() function.
• Translation - represents a translation that can be provided through the RegisterOptions.
• HankoAuthElementProps - represents the <hanko-auth> element properties.
• HankoProfileElementProps - represents the <hanko-profile> element properties.
• HankoEventsElementProps - represents the <hanko-events> element properties.

Browser support

• Safari
• Firefox
• Opera
• Chromium-based browsers (Chrome, Edge, Brave,...)

Bugs

• Customizable UI: In Chrome the ::part selector is not working in combination with some pseudo classes. E.g. :disabled is currently broken. See: chromium-issue-#1131396, chromium-issue-#953648

Found a bug? Please report on our GitHub page.

License

The elements project is licensed under the MIT License.