npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@zitadel/sdk-qwik

v0.7.0

Published

Qwik components for the Zitadel auth UI (client-side SPA).

Readme

@zitadel/sdk-qwik

Qwik components for the Zitadel auth UI, for client-side SPAs (Vite, etc.).

Installation

pnpm add @zitadel/sdk-qwik@latest

Requirements

Peer dependencies: @qwik.dev/core ^2.0.0-beta.45.

TypeScript ≥ 5.0, the floor shared by every SDK; see the compatibility notes.

Usage

import { component$ } from '@qwik.dev/core';
import { ZitadelLogin, configureZitadel } from '@zitadel/sdk-qwik';

export default component$(() => {
  const project = configureZitadel({
    projectId: import.meta.env.VITE_ZITADEL_PROJECT_ID,
    proxyPath: '/__nextgen',
  });

  return <ZitadelLogin project={project} purpose="login" postSignInUrl="/" />;
});

<ZitadelLogout project={project} postSignOutUrl="/login" /> works the same way.

ZitadelLogin also takes resumeFlowId, an existing flow to resume instead of starting a new one; unset, null or "" falls back to the flow query parameter.

The signed-in session card is <ZitadelSession project={project} /> (exported as ZitadelSession).

The SDK binds project (and the discrete projectId / proxyPath) to the element as DOM properties, the same as the other framework SDKs.

Widget props and events

ZitadelLogin, ZitadelLogout and ZitadelSession take the props below, spelled the same in every SPA SDK. An unset prop keeps the widget's own default.

| Prop | Type | Default | Widgets | Description | | --- | --- | --- | --- | --- | | project | ZitadelProject | unset | Login, Logout, Session | The handle from configureZitadel(...). Wins over projectId and proxyPath. | | projectId | string | unset | Login, Logout, Session | Project id, read when no project handle is passed. | | proxyPath | string | "/__nextgen" | Login, Logout, Session | Same-origin path the widget calls. | | purpose | CreateFlowBodyPurpose | "login" | Login | Flow purpose. | | flowName | string | unset | Login | Runs the flow definition with this name; unset runs the project's default flow for the purpose. | | postSignInUrl | string | unset | Login | Where to navigate after a completed sign-in. When the page's next query parameter names a path on the same origin, as the server SDKs' middleware sets it for a signed-out visit to a protected route, the widget returns there instead. | | forcePostSignInUrl | boolean | false | Login | Navigates to postSignInUrl even when the page's next query parameter names a path, for a page that uses next for something of its own. | | postSignOutUrl | string | unset | Logout, Session | Where to navigate after sign-out. | | resumeFlowId | string or null | unset | Login | An existing flow's id to resume instead of starting a new flow; unset, null or "" falls back to the flow query parameter, and an id that no longer resolves starts a new flow. | | variant | "widget" or "page" | "widget" | Login, Session | widget is content-sized and paints no page chrome; page claims the viewport, paints the surface background and loads the brand font, and on Login focuses the first field. | | theme | "light", "dark" or "auto" | unset | Login, Logout, Session | Colour mode. Unset follows the tenant's branding theme on Login, then the variant default (dark for page, auto for widget); Logout defaults to auto. auto follows prefers-color-scheme. | | suppressHeader | boolean | false | Login, Session | Visually hides the widget's own heading block while keeping it in the accessibility tree, for pages that already carry the heading. | | suppressPasswordToggle | boolean | false | Login | Hides the show/hide button on password fields. | | heading | string | "Signed in as" | Session | Heading text override. | | logoutLabel | string | "Sign out" | Session | Logout action label override. | | locales | Record<string, Partial<Record<string, string>>> | unset | Login | Copy overrides merged over the builtin dictionaries, keyed by primary language subtag, for example { en: { "identifier.title": "Welcome back" } }. | | lang | string | browser language | Login | BCP-47 language override. |

Each widget event reaches the callback in the last column, which receives the event's detail payload.

| Widget event | Fires when | Detail | Widgets | Callback | | --- | --- | --- | --- | --- | | zitadel-flow-step | Login shows a step, the first one included. | { step } | Login | onFlowStep$ | | zitadel-flow-input | The visitor edits a field. | { name, value } | Login | onFlowInput$ | | zitadel-flow-complete | The flow reaches a terminal step. | { behavior, redirect_uri?, handoff_token?, handoff_token_expires_at? } | Login | onFlowComplete$ | | zitadel-flow-redirect | The widget hands the browser to an identity provider; nobody is signed in yet. | { redirect_url, step } | Login | onFlowRedirect$ | | zitadel-flow-error | The flow reports an error. | { message } | Login | onFlowError$ | | zitadel-signout | The user signs out. | { display, identifier } | Logout, Session | onSignout$ |

<ZitadelLogin project={project} theme="light" onFlowComplete$={(detail) => track(detail)} />

When your callback for zitadel-flow-complete, zitadel-flow-redirect or zitadel-signout returns a promise, the widget waits for it to settle (up to two seconds) before it navigates.

Standard HTML attributes

ZitadelLogin, ZitadelLogout and ZitadelSession also take the standard HTML attributes (class, style, id, title, slot, hidden, role, tabIndex, data-* and aria-*) and pass them to the widget element, so you can position, style and label the widget without an extra wrapper element. Nothing else reaches the element: any other prop is ignored.

<ZitadelLogin project={project} class="login" data-testid="login" aria-label="Sign in" />

Server rendering

If your app renders on the server, pass projectId and proxyPath to the ZitadelLogin wrapper as strings (it writes them as the project-id and proxy-path attributes; use those hyphenated names only on a raw <zitadel-login> element), because a widget that starts before its configuration arrives shows an error instead of the flow. ZitadelLogout and ZitadelSession do the same, and the other string and boolean options (purpose, flowName, postSignInUrl, forcePostSignInUrl, resumeFlowId, postSignOutUrl, variant, theme, heading, logoutLabel, lang, suppressHeader, suppressPasswordToggle) are written as attributes too. A project handle contributes its projectId, proxyPath, url and publishableKey as attributes; the rest of the handle, and locales, are set as element properties after hydration, so a widget that needs locales still gets them only on the client. The on…$ callbacks are attached once the page is interactive, so the wrappers hold the widget's terminal events (zitadel-flow-complete, zitadel-flow-redirect, zitadel-flow-error and zitadel-signout, at most eight per widget) until then and replay them to the callbacks in order; a resumed flow that is already finished still reaches onFlowComplete$. Step and input events are never held, so field values are not retained, and a raw <zitadel-login> you render yourself is not buffered at all.

Proxying to the backend (deployment)

The widgets call ${proxyPath}/… same-origin (default /__nextgen). In production the same-origin path must come from your hosting platform — until the CLI can scaffold those configs, production SPA deployment is not yet supported; see ADR 036 and zitadel/nextgen#560. The CLI dev proxy covers local development.

For local development you can also skip the proxy and point proxyPath straight at the backend (cross-origin), e.g. proxyPath: "http://localhost:8080" (the zitadel start local runtime default port).

Testing

To test an app that uses this SDK end to end, against a real local Zitadel server, use @zitadel/testing (guide).