[nuxt-bridge] Unexpected token 'export' gives critical error with v6

[Tragio]

Describe the bug
Using Nuxt Bridge (Vue2), works perfectly in dev and it builds, but if I start my build server and try to access it, I have a critical error.

Reproducible test case
Minimal reproduction:
https://github.com/Tragio/fontawesome-v6-reproduction

Using:

"@fortawesome/fontawesome-svg-core": "^1.3.0",
"@fortawesome/free-solid-svg-icons": "^6.0.0",
"@fortawesome/vue-fontawesome": "^2.0.6",

Thank you for the beautiful work! 🙂

[Tragio]

After digging a little bit more, I found that is related to these issues FortAwesome/Font-Awesome#18514 and FortAwesome/Font-Awesome#16439

If I change all packages from .es.js to .mjs, they work perfectly.

If I use "type": "module" I have a critical error.
This file is being treated as an ES module because it has a '.js' file extension and '/Users/tragio/Downloads/fontawesome-reproduction/package.json' contains "type": "module". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.

@robmadole could you let us know if is there any ETA to change them?

PS: The workaround at the moment is to add to transpile. https://v3.nuxtjs.org/concepts/esm/#transpiling-libraries
For example:

  build: {
    transpile: [
      'vue-instantsearch',
      'instantsearch.js/es',
      '@fortawesome/fontawesome-svg-core',
      '@fortawesome/free-solid-svg-icons',
      '@fortawesome/free-brands-svg-icons',
    ],
  },