Skip to content

chore: stabilize @asgardeo/react & @asgardeo/nextjs #81

@brionmario

Description

@brionmario

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions