[UMBRELLA ☂️] Asgardeo JavaScript SDK Suite – Framework & Platform Coverage
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- express, javascript, next.js, node.js, nuxtjs, react, typescript
- Domain
- developer-experience, frontend, web-dev
Research direction
Start by reviewing the linked issues for Vue (#349), Nuxt (#350), and @next/auth (#364), along with the checked-off SDK links to understand current coverage. No files, tests, or entry points are named here; completion is limited to tracking gaps and linking individual implementation issues, so this is not a standalone first contribution.
Written by the indexing model from the issue text.
Description
Overview
This is an umbrella tracking issue for the Asgardeo SDK Suite, covering framework- and platform-specific SDKs.
The goal is to provide consistent, first-class developer experiences across popular JavaScript runtimes, frameworks, and meta-frameworks.
This issue tracks the current coverage, gaps, and related sub-issues for individual SDKs.
SDK Coverage & Status
Core & Runtime SDKs
- JavaScript SDK (Core / Framework-agnostic)
- Browser SDK
- Node.js SDK
- Express.js SDK
Framework SDKs
- React SDK
↳ https://github.com/asgardeo/javascript/issues/58 - Next.js SDK
↳ https://github.com/asgardeo/javascript/issues/67 - Vue.js SDK
↳ https://github.com/asgardeo/javascript/issues/349 - Nuxt SDK
↳ https://github.com/asgardeo/javascript/issues/350
Integrations
- React Router SDK
- TanStack Router SDK
↳ https://github.com/asgardeo/javascript/issues/152 -
@next/authSDK
↳ https://github.com/asgardeo/javascript/issues/364
Goals
- Ensure feature parity and consistent DX across all SDKs
- Provide framework-native abstractions where applicable
- Align APIs, configuration patterns, and documentation across the SDK suite
- Enable scalable expansion as new frameworks gain adoption
Scope
This umbrella issue is intended for:
- Tracking SDK coverage and gaps
- Linking related feature / implementation issues
- Aligning roadmap discussions across the SDK suite
Individual SDKs should be discussed and implemented in their respective linked issues.
- Dominant language
- TypeScript
- Stars
- 18
- Forks
- 67
- Avg merge
- 4h 6m
- Merged PRs (30d)
- 13
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from asgardeo/javascript
-
Bug: SignInButton render prop usage in "react-tanstack-router" sample missing "onClick={signIn}" OpenType/Bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
asgardeo/javascript#572 ·
-
Type/Bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
asgardeo/javascript#571 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
asgardeo/javascript#485 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 52/100
asgardeo/javascript#527 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 56/100
asgardeo/javascript#522 · 2 comments ·
All issues in asgardeo/javascript
Similar issues
-
blocklist removal
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
MetaMask/eth-phishing-detect#296544 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
pastelsky/bundlephobia#1122 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
category/development priority/P2 scope/file-operations scope/testing type/enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Enatega Customer and Rider app: Add-ons price is not visible to customer after order is placed. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100