Proxy / Middleware

The NextGlobeGen proxy can be enabled in proxy.ts file. The proxy handles locale negotiation and adds alternate links of the page to the response headers.

src/proxy.ts

export { proxy } from "next-globe-gen/proxy";

export const config = {
  // Matcher ignoring next internals and static assets
  matcher: ["/((?!_next|.*\\.).*)"],
};

Backward Compatibility

For backward compatibility with Next.js 15 and earlier, the middleware export is also available:

export { middleware } from "next-globe-gen/middleware";

Parameters

proxy(request: NextRequest, opts?: { skipAlternateLinkHeader?: boolean });

Param	Type	Required	Description
request	NextRequest	Yes	The request that is passed to Next.js middleware function
opts.skipAlternateLinkHeader	boolean	-	If the alternate link header should be skipped or not (default: false)
opts.localeNegotiation	"force" | "skip" | "default"	-	Modify if the locale negotiation should be skipped or ran forcefully
opts.localeCookieName	string	-	Custom locale cookie name (default: "NEXTGLOBEGEN_LOCALE")
opts.localeCookieOpts	Partial<ResponseCookie>	-	Custom locale cookie options

Returns

proxy returns a NextResponse instance, which can be further modified.

With other proxy logic

If you need to use custom proxy logic, call the proxy yourself with the given request instance and modify the returned response.

src/proxy.ts

import nextGlobeGenProxy from "next-globe-gen/proxy";

export function proxy(request: NextRequest) {
  const response = nextGlobeGenProxy(request);
  /**
   * Other custom logic that possibly modify the response
   */
  return response;
}

export const config = {
  // Matcher ignoring next internals and static assets
  matcher: ["/((?!_next|.*\\.).*)"],
};