chore: stabilize `@asgardeo/react` & `@asgardeo/nextjs`

Open
#81 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
nextjs, react, typescript
Domain
developer-experience, tooling

Research direction

Start by inventorying the public APIs and behaviors exposed by the @asgardeo/react and @asgardeo/nextjs packages; the issue names no files or tests. Compare current APIs with the package documentation and define completion as documented stable APIs, clear experimental or internal boundaries, and semantic-versioning guidance for future changes.

Written by the indexing model from the issue text.

Description

Is your feature request related to a problem? Please describe.
The @asgardeo/react and @asgardeo/nextjs packages currently have APIs and behaviors that may change unexpectedly between versions. This makes it difficult for consumers to confidently adopt them in production environments, especially when version bumps introduce breaking changes or undocumented side effects.

Describe the solution you would prefer
Finalize and stabilize the public APIs for both @asgardeo/react and @asgardeo/nextjs, ensuring that future changes follow semantic versioning and include appropriate documentation. Mark internal or experimental APIs clearly to prevent unintentional usage by consumers.

Additional context
Stabilizing these packages is essential ahead of broader adoption, especially for enterprise clients and OSS maintainers. It will also help reduce developer friction, improve long-term maintainability, and align the SDKs with expectations set by other Asgardeo tooling.

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.