blade-auth

library3.29.10jsnpmunverified

The `blade-auth` package provides essential utility functions and helpers designed for integrating authentication services seamlessly into applications built with the Blade framework. As of version 3.29.10, it offers streamlined mechanisms for common authentication patterns, including user registration, sign-in, sign-out, and active session management. The package maintains a relatively frequent release cadence, with recent updates focusing on refining internal 'trigger' syntax, improving documentation accuracy, and enhancing developer experience through features like dependency override support in the build API and improved error handling. Its primary differentiation lies in its deep integration within the Blade ecosystem, aiming to abstract away common authentication complexities and provide a consistent experience aligned with the Blade architectural philosophy. It targets modern JavaScript environments, likely favoring ESM.

auth-security web-framework

npm install blade-auth

github ↗package ↗

INSTALL

IMPORT

SIG · BLADE-AUTH

blade-auth

auth-securityjavascriptv3.29.10

Install

—

Import

—

Disk

—

Pass rate

0/ 6

Env Coverage0 / 6

glibc

18–22

musl

18–22

Install & Compatibility

Where this runs

tested against v? · npm install

Install × environment matrix

Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux

musl

node 18–226 runs

build_error

glibc

node 18–226 runs

build_error

Code

Verified usage

Verified import paths — ran on the pinned version, not inferred.

initAuth

✓ import { initAuth } from 'blade-auth';

✗ const initAuth = require('blade-auth').initAuth;

Most Blade packages are ESM-first. Use named imports for core utilities.

signIn

✓ import { signIn } from 'blade-auth';

✗ import signIn from 'blade-auth/signIn';

Authentication actions like `signIn` are typically named exports from the main package entry point.

getAuthSession

✓ import { getAuthSession } from 'blade-auth';

✗ const { getAuthSession } = require('blade-auth');

For retrieving the current authentication state or session, `getAuthSession` is a common named export.

This quickstart demonstrates the initialization of `blade-auth`, a user signup and sign-in flow, retrieving the current session, and finally signing out.

import { initAuth, signIn, signUp, signOut, getAuthSession } from 'blade-auth'; interface AuthConfig { apiBaseUrl: string; jwtSecret: string; } interface UserCredentials { email: string; password: string; } async function runAuthFlow() { // Initialize auth with configuration const config: AuthConfig = { apiBaseUrl: process.env.BLADE_API_URL ?? 'https://api.example.com/v1', jwtSecret: process.env.BLADE_JWT_SECRET ?? 'super-secret-key-please-change' }; // In a real app, this would be configured once, likely on app start initAuth(config); const user: UserCredentials = { email: 'test@example.com', password: 'password123' }; try { console.log('Attempting to sign up...'); const signUpResult = await signUp(user.email, user.password); console.log('Sign up successful:', signUpResult); console.log('Attempting to sign in...'); const signInResult = await signIn(user.email, user.password); console.log('Sign in successful:', signInResult); console.log('Getting current auth session...'); const session = await getAuthSession(); console.log('Current session:', session); if (session?.isAuthenticated) { console.log('User is authenticated. Token:', session.token); } console.log('Attempting to sign out...'); await signOut(); console.log('Sign out successful.'); const postSignOutSession = await getAuthSession(); console.log('Session after sign out:', postSignOutSession); } catch (error) { console.error('Authentication error:', error); } } runAuthFlow();

Debug

Known issues

breakingVersion 3.29.0 introduced a 'simplified trigger syntax' which updated auth logic and likely renders previous trigger configurations incompatible. Applications upgrading from earlier 3.x versions will need to adapt their trigger definitions.

fix

Review the official Blade documentation for the updated trigger syntax introduced in 3.29.0 and refactor existing trigger configurations accordingly. Pay close attention to how triggers are declared and loaded.

affects: >=3.29.0

gotchaWhen defining or referencing triggers, ensure they are consistently kebab-cased. Version 3.29.8 explicitly documented this convention, suggesting it's important for correct functionality.

fix

Standardize all trigger names and references to use kebab-case (e.g., `my-auth-trigger` instead of `myAuthTrigger`).

affects: >=3.29.8

gotchaThis library is primarily built for the Blade ecosystem. Attempting to use `blade-auth` outside of a properly configured Blade application context might lead to unexpected behavior or require significant manual setup not covered by its utilities.

fix

Ensure your project is a Blade application and `blade-auth` is integrated as intended by the framework's documentation. Avoid standalone usage without understanding its dependencies on the Blade runtime.

affects: >=3.0.0

Errors

Common errors & fixes

Error: Invalid trigger syntax provided.

Attempting to use pre-3.29.0 trigger syntax after upgrading to version 3.29.0 or later.

fix

Update your trigger definitions to comply with the simplified trigger syntax introduced in `blade-auth` v3.29.0. Consult the latest Blade documentation for examples.

TypeError: Cannot read properties of undefined (reading 'isAuthenticated')

The `getAuthSession()` function returned `null` or `undefined` because the user is not logged in or the authentication service is not initialized correctly.

fix

Always check if the session object returned by `getAuthSession()` is defined and its properties (like `isAuthenticated`) exist before accessing them. Ensure `initAuth` is called before any other auth operations.

AuthError: Invalid credentials.

The username or password provided to `signIn` or `signUp` did not match records on the authentication server.

fix

Double-check the provided credentials. If this error persists, investigate the server-side authentication logs or ensure the `apiBaseUrl` provided to `initAuth` points to the correct authentication endpoint.

Upgrade

Version history

3.29.10latest on npm

Audit

Dependencies

No dependency data recorded yet.

Agent activity

31 hits · last 30 days

node

OpenAI (training)

Resources

githubhttps://github.com/ronin-co/blade ↗

packagehttps://www.npmjs.com/package/blade-auth ↗