ory / ory/elements

Please provide elements packages for other frameworks

Open
#581 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Needs Triage
Dominant language
TypeScript
Stars
187
Forks
80
PR merge metrics
No merged PRs in 30d

Description

Preflight checklist
Ory Network Project

No response

Describe your problem

Please provide elements for other frameworks.

We are using Nuxt 4 and Vue in production at work and have been using a flaky client-side only implementation of the ory fetch SDK for some time now.

We would really appreciate first-party support for frameworks other than Next.js and React

Describe your ideal solution

Equivelent versions of
/packages/nextjs and packages/elements-react
e.g /packages/nuxt and packages/elements-vue

Workarounds or alternatives

We're using the vanilla ory-fetch client in our Nuxt 4 projects with ssr: false.

Version

25.4

Additional Context

No response

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.

Research direction

Compare the existing /packages/nextjs and /packages/elements-react packages with the reported Nuxt 4 workaround using the vanilla ory-fetch client. Start by understanding how those packages support their frameworks and SSR, then define the equivalent Nuxt and Vue package scope. Done means first-party framework packages are available for the requested production use case.

Written by the indexing model from the issue text.

Assessment

Tech stack
next.js, nuxtjs, react, typescript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.