[BUG] Error: Invariant: renderHTML should not be called in minimal mode

[verdverm]

Describe the bug

I'm trying to make a post to the following NextJS API route and get this error back after the wrangler / opennext build. Not sure what's causing it

import { NextRequest, NextResponse } from 'next/server';
import { isValidHandle } from '@atproto/syntax'

import { client as atprotoOauthClient } from '@/lib/atproto/oauth/client'

type Session = { did: string }

export async function POST(req: NextRequest) {
  const data = await req.json()

  // Validate
  const handle = data.handle
  if (typeof handle !== 'string' || !isValidHandle(handle)) {
    return NextResponse.json({error: "invalid handle"})
  }

  // Initiate the OAuth flow
  try {
    const url = await atprotoOauthClient.authorize(handle, {
      scope: 'atproto transition:generic',
    })
    return NextResponse.json({ redirect: url.toString() })
  } catch (err) {
    return NextResponse.json({error: "oauth authorize failed", details: err, message: err.message})
  }
}

Steps to reproduce

Not sure yet, can get CF trace details

I can see about producing a minimal reproducer in the next couple of days

Expected behavior

I can post to oauth endpoint and not get errors

@opennextjs/cloudflare version

0.5.3

Wrangler version

3.109.2

next info output

Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.3.0: Thu Jan  2 20:23:36 PST 2025; root:xnu-11215.81.4~3/RELEASE_ARM64_T8112
  Available memory (MB): 24576
  Available CPU cores: 8
Binaries:
  Node: 21.7.1
  npm: 10.5.0
  Yarn: 1.22.21
  pnpm: 8.14.0
Relevant Packages:
  next: 15.1.7 // Latest available version is detected (15.1.7).
  eslint-config-next: 15.1.0
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: standalone

Additional context

running site is at https://verdverm.verdverm.workers.dev

[verdverm]

hmm, have a feeling it might be dotenv, I think I saw an error at some earlier point in previous versions of the code about fs.readFile not being implemented yet...

either way the error message coming out doesn't help me to RCA this. I did notice other endpoints which import the atprotoOauthClient (which imports dotenv) are also throwing 500 errors with the same error message

---

edit, dotenv does not seem to be the issue, removed it and still getting the same 500 & error message

edit2, I've done a bunch of edits to simplify things, still seeing the same error out of what I suspect is the ATProto package(s), I wonder if they are using some unsupported node:* package and the error is not bubbling up, or if it is the build process of these things causing the issue, or if the renderHtml is really about rendering the 500 page by next when it shouldn't?

[verdverm]

linking in #57

[verdverm]

refactored more code, per issue 57

You can not use process.env at top level

still seeing the same issue. Wondering if it is similar to NextAuth because we are doing OAuth with this package: https://github.com/bluesky-social/atproto/tree/main/packages/oauth/oauth-client-node

[gethassaan]

I am also facing the same issue and I am not even using 0Auth

[verdverm]

@vicb

Here is a minimal reproducer: https://github.com/verdverm/cf-repro

[vicb]

Thanks,
This issue is on my radar as it makes debugging errors cumbersome.
I'll probably start investigating early next week.

[verdverm]

thanks, keep me posted, I have one more thing I want to try (a hacky shim for one of the packages I'm using for ATProto)

It certainly seems like this renderHTML is not the real error, as you say, hard to debug. Will be great to see more relevance in the CF logs

[verdverm]

Some additional context, issues, and workarounds w.r.t. ATproto OAuth on Cloudflare Workers

bluesky-social/atproto#3292

[wesbos]

Was also hitting this and I finally narrowed it down to a not-found.tsx that tried to access headers:

import { headers } from 'next/headers';

export default async function NotFound() {
  const headersList = await headers();
  console.log(headersList);
  return (
    <div>
      <h2>Not Found</h2>
      <p>Could not find requested resource</p>
    </div>
  );
}

This code is pretty much straight from the next.js docs for creating a not found page. It's the getHeaders() call that breaks the entire site and throws the renderHTML error