Statically exporting a Next.js application via next export disables API routes and middleware.

[krismorf]

I receive the following error everytime I build my project using next build. I'm not using next export.

Statically exporting a Next.js application via `next export` disables API routes and middleware.
This command is meant for static-only hosts, and is not necessary to make your application static.
Pages in your application without server-side data dependencies will be automatically statically exported by `next build`, including pages powered by `getStaticProps`.

Is there anything else or a bad practice that would lead to this warning?

How can I see which pages were exported instead of built? There is no out directory.

// next.config.js

const nextConfig = {
  i18n,
  reactStrictMode: true,
  images: {
    dangerouslyAllowSVG: true,
    contentSecurityPolicy: "default-src 'self'; script-src 'none'; sandbox;",
  },
  async redirects() {
    return [
      ...
    ]
  },
}

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Wed Nov 23 01:01:46 UTC 2022
    Binaries:
      Node: 18.14.1
      npm: 9.3.1
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.1.6
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

[icyJoseph]

It's fixed in next@canary, expect it to be fixed in 13.1.7, looks like there was some "oopsie" between 13.1.5 and 13.1.6.

[icyJoseph]

Introduced: #45192
Fixed by: c45481b
First reported at: #41745 (comment)