Importing next/image into app router middleware logs "attempted import error" only on Linux

[Syphini]

Verify canary release

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

Provide environment information

Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP Debian 5.10.179-1 (2023-05-12)
    Binaries:
      Node: 16.20.0
      npm: 9.8.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant Packages:
      next: 13.4.20-canary.2
      eslint-config-next: 13.4.19
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A

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

App Router, Image optimization (next/image, next/legacy/image), Middleware / Edge (API routes, runtime), Operating System (Windows, MacOS, Linux)

Link to the code that reproduces this issue or a replay of the bug

https://github.com/Syphini/nextjs-middleware-import-bug-repro

To Reproduce

1. Create a new NextJS app using npx create-next-app@latest (the reproduction template was perfect)
2. Create a middleware.js file with the following code:

import Image from "next/image";

export async function middleware(request) {

}

3. Run the project with npm run dev
4. Open the hosted page in a browser and see the following error

Attempted import error: 'preload' is not exported from 'react-dom' (imported as 'preload').

Import trace for requested module:
./node_modules/next/dist/esm/client/image-component.js
./node_modules/next/dist/esm/shared/lib/image-external.js
./node_modules/next/image.js

Describe the Bug

An unexpected import error is logged to console

Attempted import error: 'preload' is not exported from 'react-dom' (imported as 'preload').

Import trace for requested module:
./node_modules/next/dist/esm/client/image-component.js
./node_modules/next/dist/esm/shared/lib/image-external.js
./node_modules/next/image.js

In my case, I was incidently importing next/image through a third-party package that deeply nested it within
The bug doesn't appear to have much affect other than logging to console, but it's a bit of a spam on middleware reload

Expected Behavior

Can verify on Windows OS that this error is not logged to the console, and no other issues observed.
It appears to just log this error on Linux (at least on the Debian/Ubuntu versions I have tried)

Which browser are you using? (if relevant)

No response

How are you deploying your application? (if relevant)

No response

[github-actions]

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.