perf: remove oxc-parser manual wasm fallback logic

[BobbieGoede]

Experimenting

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxtjs/i18n@3413

commit: da583c0

[BobbieGoede]

@danielroe @Boshen

Based on https://stackblitz.com/edit/oxc-parser I was hoping to remove our manual wasm fallback for oxc-parser (same for nuxt), it looks like this only works when explicitly adding @oxc-parser/binding-wasm32-wasi as a (prod) dependency (matching the usage example).

However, having this as prod dep will cause issues when installing in unsupported environments (as was the case in this PR).

Here some stackblitz reproductions using the preview release of this PR (nuxt-i18n + @oxc-parser/binding-wasm32-wasi as optional dep)

• Playground - breaks/hangs on Nuxt splash/loading screen
• Playground + with binding dep - works as expected

I suppose in the case for nuxt-i18n we could add the binding to the stackblitz playground/issue starters, but it would be great to have this working without adding the dependency or at least conditionally if the environment supports it.

[Boshen]

We are currently working with stackblitz to get oxc-parser work automatically without @oxc-parser/binding-wasm32-wasi. @hi-ogawa will let you know when it works.

[hi-ogawa]

Hi folks! With the latest oxc-parser 0.62.0, it fallbacks to wasm package automatically on stackblitz. Here is a quick example https://stackblitz.com/edit/stackblitz-starters-mv7ri8rj?file=index.js

As you can see in the example, currently this adds a few seconds of download time during import (not during npm i) with a bit too noisy log, which is not ideal, but I started with this to see how it affects downstream project in general. If this is too bothersome, we can explore more direct way of package replacement by coordinating with Stackblitz team. Please let me know if you have any feedback. Thanks!