Proxy Middleware

When usingNextPress is enabled during configuration, a proxy middleware file is generated that routes WordPress asset requests through your Next.js application. This allows the storefront to serve WordPress-managed CSS, JavaScript, and REST API responses alongside the Next.js frontend.

Condition: usingNextPress = true

Source: <nextpress>/proxy.ts (generated into your src/ directory)

The proxy middleware handles two types of requests:

Requests matching NextPress proxy patterns are forwarded to the WordPress backend through the @axistaylor/nextpress proxyByWCR function. These routes include:

These requests are also wrapped with withMiddlewareTokenManager to attach session credentials to proxied requests.

All other routes (non-asset, non-API) go through a setUriHeader function that adds an x-uri header to the request. This header tells the layout which WordPress page assets (scripts and stylesheets) to fetch and render.

The middleware applies to two groups of routes:

export const config = {
  matcher: [
    // NextPress proxy routes
    '/atx/:instance/proxiee',
    '/atx/:instance/wp',
    '/atx/:instance/wc',
    '/atx/:instance/wp-internal-assets/:path*',
    '/atx/:instance/wp-assets/:path*',
    '/atx/:instance/wp-json/:path*',
    // All page routes (excludes _next, api, static files)
    '/((?!_next|api|favicon.ico|sw.js|\\.well-known|.*\\.).*)',
  ],
};

The proxy template depends on these internal modules:

When NextPress is enabled, the GraphQL client also generates additional helper functions for fetching WordPress content:

• fetchAssetsByUri(uri) - Fetches enqueued scripts and stylesheets for a given page URI
• fetchPageWithSession(uri) - Fetches WordPress page content with session cookies
• fetchCartPage() / fetchCheckoutPage() - Convenience wrappers for cart and checkout pages
• fetchOrder(orderId, key) - Fetches order details