_error is treated as a serverless function even though the edge runtime is specified (in Pages)

[dario-piotrowicz]

Verify canary release

• I verified that the issue exists in the latest Next.js canary release

Provide environment information

Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
    Binaries:
      Node: 16.16.0
      npm: 8.11.0
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant packages:
      next: 13.3.1-canary.9
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0

Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

Link to the code that reproduces this issue

https://github.com/dario-piotrowicz/nextjs-_error-edge-demo

To Reproduce

Run npm run build and view the .next/server/middleware-manifest.json file

Describe the Bug

the _error is not present in the middleware manifest thus it is being treated as a serverless function instead of an edge route, basically ignoring the user provided config

Expected Behavior

_error should be present as a field of the functions object inside the middleware manifest thus it will be deployed as an edge route as requested by the user provided config

Additional Information

• Seems like this only happens with the Pages routing, App routing seems to be fine

• By looking at the Vercel cli source code (specifically here) it looks to me like the way of discerning if a function is a serverless one or an edge one is to check their presence in the middleware manifest, so I based the details above on this assumption

• Regardless on the middleware manifest I noticed the issue when running vercel build since, as you can see from the following screenshot generates a node serverless function instead of an edge one:
  

[matiasironyard]

Any progress on this issue? We are facing a similar issue. Here is our error code:

"use client";

import { useEffect } from "react";

export const runtime = "edge";

export default function Error({
  error,
  reset,
}: {
  error: Error;
  reset: () => void;
}) {
  useEffect(() => {
    // Log the error to an error reporting service
    // eslint-disable-next-line no-console
    console.error(error);
  }, [error]);

  return (
    <div>
      <h2>Something went wrong!</h2>
      <button
        type="button"
        onClick={
          // Attempt to recover by trying to re-render the segment
          () => reset()
        }
      >
        Try again
      </button>
    </div>
  );
}

Build error:

13:41:08.376	⚡️ Completed yarn vercel build.
13:41:11.547
13:41:11.548	⚡️ ERROR: Failed to produce a Cloudflare Pages build from the project.
13:41:11.548	⚡️
13:41:11.548	⚡️ The following routes were not configured to run with the Edge Runtime:
13:41:11.548	⚡️ - /_error
13:41:11.548	⚡️
13:41:11.548	⚡️ Please make sure that all your non-static routes export the following edge runtime route segment config:
13:41:11.549	⚡️ export const runtime = 'edge';
13:41:11.549	⚡️
13:41:11.549	⚡️ You can read more about the Edge Runtime on the Next.js documentation:
13:41:11.549	⚡️ https://nextjs.org/docs/app/building-your-application/rendering/edge-and-nodejs-runtimes

[simpson]

Any updates?

[simpson]

Any chance you will review this?

[sylee999]

I have the same issue, but my app is using app routing.

When I used previous nextjs version 13.4.19, it worked well.
As I updated the newest one, I had the same error.
It seems like this bug was happened from 13.5.X.

So, you'd better use previous version like 13.4.19 while they are fixing it.

I just hope this problem be fixed soon.