Repository: next.js
Issue: @vercel/og: WebAssembly module for webpack Error
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

##### Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
##### Binaries:
      Node: 19.2.0
      npm: N/A
      Yarn: N/A
      pnpm: N/A
##### Relevant packages:
      next: 13.0.7-canary.5
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

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

_No response_

### Link to the code that reproduces this issue

https://github.com/alchui/og-wasm-bug

### To Reproduce

As instructed from https://vercel.com/docs/concepts/functions/edge-functions/og-image-generation:

Installed Dependency:
```
npm i @vercel/og
```
Ran OG Example:
```
import { ImageResponse } from '@vercel/og';

export const config = {
  runtime: 'experimental-edge',
};

export default function () {
  return new ImageResponse(
    (
      <div
        style={{
          fontSize: 128,
          background: 'white',
          width: '100%',
          height: '100%',
          display: 'flex',
          textAlign: 'center',
          alignItems: 'center',
          justifyContent: 'center',
        }}
      >
        Hello world!
      </div>
    ),
    {
      width: 1200,
      height: 600,
    },
  );
}
```
Entered Dev Production Mode:
```
npm run dev
```

### Describe the Bug

Produced Bug:
```ps
> dev     
> next dev

event - compiled client and server successfully in 7.7s (148 modules)
warn  - You are using an experimental edge runtime, the API might change.
wait  - compiling /_error (client and server)...
wait  - compiling / (client and server)...
error - ./node_modules/@vercel/og/vendor/resvg.simd.wasm?module
Module parse failed: Unexpected character '' (1:0)
The module seem to be a WebAssembly module, but module is not flagged as WebAssembly module for webpack.
BREAKING CHANGE: Since webpack 5 WebAssembly is not enabled by default and flagged as experimental feature.
You need to enable one of the WebAssembly experiments via 'experiments.asyncWebAssembly: true' (based on async modules) or 'experiments.syncWebAssembly: true' (like webpack 4, deprecated).
For files that transpile to WebAssembly, make sure to set the module type in the 'module.rules' section of the config (e. g. 'type: "webassembly/async"').
(Source code omitted for this binary file)
[Error: Objects are not valid as a React child (found: [object Response]). If you meant to render a collection of children, use an array instead.] 
```
Attempted Debugging Solution:

- according to the error `You need to enable one of the WebAssembly experiments via 'experiments.asyncWebAssembly: true' (based on async modules) or 'experiments.syncWebAssembly: true' (like webpack 4, deprecated)`
- added following config to `next.config.ts`
```
	webpack: function (config, options) {
		config.experiments = { asyncWebAssembly: true, syncWebAssembly: true };
		return config;
	},
```
Entered Dev Production Mode:
```
npm run dev
```
Produced Another Error:
```
> dev
> next dev

ready - started server on 0.0.0.0:3000, url: http://localhost:3000
event - compiled client and server successfully in 3.4s (148 modules)
warn  - You are using an experimental edge runtime, the API might change.
wait  - compiling /_error (client and server)...
wait  - compiling / (client and server)...
error - ./node_modules/@vercel/og/vendor/resvg.simd.wasm?module
Module parse failed: Unexpected section: 0xc
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
Error: Unexpected section: 0xc
```

### Expected Behavior

Expected to produce a similar result as https://og-examples.vercel.sh/api/static
![Expected Result](https://og-examples.vercel.sh/api/static)

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_