Can't use ipx in serverMiddleware with @nuxt/bridge

When adding /server/middleware/ipx.js to nuxt.config.js (as indicated at https://image.nuxtjs.org/providers/ipx/#advanced-custom-servermiddleware) while using @nuxt/bridge…

import { createIPX, createIPXMiddleware } from 'ipx'
const ipx = createIPX({
  dir: '',
  domains: [],
  alias: {},
  sharp: {},
})
export default createIPXMiddleware(ipx)

it results in an error:

 WARN  [worker] Named export 'stat' not found. The requested module 'fs-extra' is a CommonJS module, which may not support all module.exports as named exports.
CommonJS modules can always be imported via the default export, for example using:

import pkg from 'fs-extra';
const { stat, readFile } = pkg;


  import { stat, readFile } from 'fs-extra';
  ^^^^
  SyntaxError: Named export 'stat' not found. The requested module 'fs-extra' is a CommonJS module, which may not support all module.exports as named exports.
  CommonJS modules can always be imported via the default export, for example using:

  import pkg from 'fs-extra';
  const { stat, readFile } = pkg;

  at ModuleJob._instantiate (internal/modules/esm/module_job.js:121:21)
  at async ModuleJob.run (internal/modules/esm/module_job.js:166:5)
  at async Loader.import (internal/modules/esm/loader.js:178:24)
  at async Object.loadESM (internal/process/esm_loader.js:68:5)

[ms-fadaei]

@pi0, Can we use this pattern?

- import { readFile, stat, Stats } from 'fs-extra'
+ import fsExtra, { Stats } from 'fs-extra'
+ const { stat, readFile } = fsExtra;

[nathanchase]

This is still unfortunately the only thing that is holding me back from using @nuxt/bridge. Is /server/middleware no longer viable in Nuxt 3 or Bridge?