Nuxt SDK

Open
#350 2 comments 0 reactions 1 assignee View on GitHub

@kavindadimuthu is already working on this.

Since Feb 9, 2026.

Assessment

This issue has not been assessed yet.

Description

@asgardeo/nuxt
Problem

Asgardeo currently provides official SDKs for popular frameworks such as React and Next.js, enabling developers to easily integrate authentication and identity features. However, there is no first-class SDK available for Nuxt (https://nuxt.com/), which is a widely adopted meta-framework in the Vue ecosystem.

Nuxt developers are currently required to:

  • Use low-level JavaScript SDKs directly, or
  • Build custom plugins, middleware, and wrappers to handle authentication flows

This increases integration complexity and leads to inconsistent implementations compared to supported meta-frameworks such as Next.js.

Proposed Solution

Introduce an official Asgardeo Nuxt SDK that mirrors the capabilities and developer experience of the existing Asgardeo Next.js SDK.

The Nuxt SDK should closely align with the Next.js SDK in terms of:

  • Supported Components and helpers
  • API surface and abstractions
  • Configuration and initialization patterns
  • Server-side and client-side authentication handling
  • Documentation structure and quick-start experience, similar to the Next.js guide
    (https://wso2.com/asgardeo/docs/quick-starts/nextjs/)

This would enable Nuxt developers to integrate Asgardeo in a framework-native way while supporting Nuxt-specific patterns such as plugins, composables, middleware, and SSR.

[!IMPORTANT]
We can get the SDK listed on the official Nuxt space

Alternatives

N/A

Please select the package issue is related to

@asgardeo/nuxt

Version

N/A

Reporter Checklist
  • I have searched the existing issues and this is not a duplicate.
  • I have provided all the necessary information.
  • I have verified the feature on the latest version of the package.
Dominant language
TypeScript
Stars
18
Forks
67
Avg merge
4h 6m
Merged PRs (30d)
13

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from asgardeo/javascript

All issues in asgardeo/javascript

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.