Remove use of React Server Components

[lightwalker-eth]

Goals

Take some small steps towards transitioning ENSAdmin away from Next.js and into a pure client-side app.

Subtasks

Advice appreciated 👍

[notrab]

@lightwalker-eth here’s a plan for how we could simplify things and move toward static exports:

What you’re seeing in those URLs with &_rsc is caused by next/link prefetching, which triggers Next.js’ RSC behavior by default.

After checking the next/link docs, we have a couple of options:

Option 1: Create a Link Wrapper

We could create a small wrapper around NextLink that sets prefetch={false}.

That would prevent the _rsc query param from appearing, and once we migrate away from Next.js, we can replace this with the Link component from whichever client router we choose (likely TanStack Router).

Option 2: Move now to Static Export

Alternatively, we could enable output: "export" in next.config.js to generate fully static pages.

However, this currently isn’t possible because we rely on the dynamic route /name/:x.

To make that compatible, we could migrate /name/[name] to a query string pattern like /name?name=xyz.

Enabling static export would also disable:

• API routes, which we currently only use for the AI endpoint (we could consider removing or replacing this) ❓
• Server Actions, which we’re not using ☑️

Actions for Option 2;:

1. Migrate /name/[name] → /name?name=
2. Remove the AI API route (since it’s just one feature)
3. Enable output: "export" for static exports

That would simplify the setup and bring us closer to a clean static build.

[lightwalker-eth]

@notrab Hey thanks for your analysis and advice here.

I'm happy to proceed with the Option 2 that you recommended.

For the open question about what we do with the "AI endpoint", here's some suggestions:

• Background info: Matt is currently advancing work that will create a completely new app in the ENSNode suite: "ENSApi".
• Suggest we transfer the "AI endpoint" from ENSAdmin to ENSApi.
• The ENSApi app isn't shipped just yet. Therefore, to unblock advancing this goal, suggest to:
  • Comment out any code in ENSAdmin related to the "AI endpoint" (we shouldn't completely delete this code). This means ENSAdmin will temporarily lose this feature.
  • Create a separate follow-up issue in GitHub to track the goal for transferring this "AI endpoint" from ENSAdmin to ENSApi after it's created. Once this work is completed the AI feature should be restored again.