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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@logto/node

v3.1.6

Published

[![Version](https://img.shields.io/npm/v/@logto/node)](https://www.npmjs.com/package/@logto/node) [![Build Status](https://github.com/logto-io/js/actions/workflows/main.yml/badge.svg)](https://github.com/logto-io/js/actions/workflows/main.yml) [![Codecov]

Readme

Logto Node.js SDK

Version Build Status Codecov

The Logto Node.js SDK written in TypeScript.

Table of Contents

Installation

Using npm

npm install @logto/node

Using yarn

yarn add @logto/node

Using pnpm

pnpm add @logto/node

What is this and how does it work?

As the name suggests, Logto Node.js SDK is the foundation of all Logto SDKs that run in Node.js (Express, Next.js, etc.). @logto/node extends @logto/client and provides a Node.js specific implementation of the client adapters:

  • Implements requester by using package node-fetch.
  • Implements generateCodeChallenge, generateCodeVerifier, generateState methods by using crypto.

Usually, you are not expected to use it directly in your application, but instead choosing a framework specific SDK that built on top of it. We have already released a set of official SDKs to accelerate your integration. Check this out and get started!

How to create your own SDK from scratch?

If Logto does not support your traditional web framework and you want to create your own SDK from scratch, we recommend checking out the SDK specification first. You can also refer to our Express SDK and Next.js SDK to learn more about the implementation details.

Prerequisites

  • Basic understanding of Node.js and TypeScript
  • Familiarity with your target web framework
  • Understanding of OAuth 2.0 and OpenID Connect concepts

Step 1: Setup the project

Prepare your project by installing @logto/node as the dependency.

Step 2: Implement store adapter

The store adapter is used to store the Logto session information. In most cases, we recommend using cookie-based storage to store the session information.

// storage.ts
import { CookieStorage } from '@logto/node';

export const storage = new CookieStorage({
  encryptionKey: '<your-encryption-key>',
  cookieKey: `<logto_app_xxx>`,
  isSecure: false, // Set to true if you are using HTTPS
  getCookie: (name) => {
    // Example usage, get cookie from the request, depends on your framework
    return request.cookies[name] ?? '';
  },
  setCookie: (name, value, options) => {
    // Example usage, set cookie to the response, depends on your framework
    response.setHeader('Set-Cookie', serialize(name, value, options));
  },
});

This will wrap the session data, encrypt it with the encryption key, and store it in the cookie directly.

But the cookie size is limited, so you may need to use external storage like Redis or memory cache to store the session information. Especially when you are using organization features, the session information will be quite large.

// storage.ts
import { CookieStorage } from '@logto/node';

class RedisSessionWrapper implements SessionWrapper {
  constructor(private readonly redis: Redis) {}

  async wrap(data: unknown, _key: string): Promise<string> {
    const sessionId = randomUUID();
    await this.redis.set(`logto_session_${sessionId}`, JSON.stringify(data));
    return sessionId;
  }

  async unwrap(value: string, _key: string): Promise<SessionData> {
    if (!value) {
      return {};
    }

    const data = await this.redis.get(`logto_session_${value}`);
    return JSON.parse(data);
  }
}

export const storage = new CookieStorage({
  cookieKey: `<logto_app_xxx>`,
  sessionWrapper: new RedisSessionWrapper(redis),
  isSecure: false, // Set to true if you are using HTTPS
  getCookie: (name) => {
    // Example usage, get cookie from the request, depends on your framework
    return request.cookies[name] ?? '';
  },
  setCookie: (name, value, options) => {
    // Example usage, set cookie to the response, depends on your framework
    response.setHeader('Set-Cookie', serialize(name, value, options));
  },
});

Step 3: Implement navigation adapter and create the client

Continue to prepare the navigation adapter and create the client. You need to implement the "redirect" function to redirect the user to the Logto sign-in page.

// client.ts
import { NodeClient } from '@logto/node';
import { config } from './config';
import { storage } from './storage';

export const client = new NodeClient({
  ...config,
  storage,
  navigate: (url) => {
    // Example usage, navigate to the url, depends on your framework
    response.redirect(url);
  },
});

Step 4: Use the client to sign in

You can now trigger the sign-in flow by calling the signIn method.

// app.ts
import { client } from './client';

await client.signIn({
  redirectUri: 'http://localhost:3000/callback',
});

Step 5: Handle the sign-in callback

You need to handle the sign-in callback by calling the signInCallback method.

// app.ts
import { client } from './client';

// You'll need to pass the full url to the callback handler,
// it depends on your framework to get the url.
await client.handleSignInCallback(`${request.url}`);

// After handling the callback, the user is signed in,
// information stored in the storage adapter we created earlier,
// you can now redirect the user to the home page.
response.redirect('/');

Step 6: Implement sign out and other methods

You can now implement the sign out and other methods by referring to our example implementation in other frameworks.

Step 7: Retrieve user information and protect resources

You can call the getContext method to retrieve the user information and protect your resources based on the context.

// app.ts
import { client } from './client';

const { isAuthenticated, claims } = await client.getContext();

if (!isAuthenticated) {
  // The user is not signed in, redirect to the sign-in page.
  // protect the resource from being accessed by unauthenticated users.
  response.redirect('/sign-in');
}

// The user is signed in, you can now do something with the user information.
console.log(claims);

Awesome unofficial SDKs

We have a list of awesome implementations of Logto SDK:

We are grateful for the amazing Logto community!

Resources

Website Docs Discord