@swc/plugin-formatjs: Plugin invokation fails with pointer out of bounds

[tom-streller-tutti]

Describe the bug
Using the official plugin @swc/plugin-formatjs fails with an internal WASM error:

FATAL: An unexpected Turbopack error occurred. Please report the content of /var/folders/8x/wrjv5tmx047cc7vdnhjp0br40000gp/T/next-panic-7076f4752db8755edbe4441acd744935.log, along with a description of what you were doing when the error occurred, to https://github.com/vercel/next.js/issues/new
Failed to compile.

./node_modules/next/dist/pages/_app.js
Error: failed to process failed to invoke plugin: failed to invoke plugin on 'Some("/Users/tomstr/Projects/JavaScript/next-swc-formatjs/node_modules/next/dist/pages/_app.js")'

Caused by:
    0: failed to invoke `/Users/tomstr/Projects/JavaScript/next-swc-formatjs/node_modules/@swc/plugin-formatjs/swc_plugin_formatjs.wasm` as js transform plugin at /Users/tomstr/Projects/JavaScript/next-swc-formatjs/node_modules/@swc/plugin-formatjs/swc_plugin_formatjs.wasm
    1: wasm plugin bytecheck failed "check bytes error: check failed for tuple struct member 0: check failed for struct member pkg_version: pointer out of bounds: base 0x4ba14081398 offset -53202 not in range 0x4ba14081200..0x4ba140813b4"

URL to minimal reproduction

You can reproduce it using my example repo. Just check it out and run

yarn install
yarn build

Expected behavior
Expecting the plugin to run without an error in invokation.

Additional context

Using @swc/core version 1.10.6. I tried other versions. For the main project I'm working on I need to set @swc/core as a direct dependency.

[kdy1]

See https://plugins.swc.rs/versions/range/116.
Formatjs is not in the list and it means it's not supported.

[kdy1]

You can wait for vercel/next.js#74580 to be merged

[tom-streller-tutti]

You can wait for vercel/next.js#74580 to be merged

Thank you.

Apologies for my prior message, it was rude. I did not understand the compatibility matrix the site shows - it is very useful once I understood it.

It appears we have to wait for Next.js to move, then.

Thank you.