feat: support JIT like compilation

[kazupon]

Background

vue-i18n has had a message compiler since v9.
The message compiler compiles messages in I18n resources in formats such as json, yaml and js / ts into a javascript executable for AoT like. This allowed us to maximize performance in v9.

Issues and Limitations

However, the resulting problem is that it does not work in environments with CSP restrictions.

To make it work in such environments, it is possible to avoid this problem by compiling and bundling i18n resources in advance with bundlers such as unplugin-vue-i18n

• Optimization: https://vue-i18n.intlify.dev/guide/advanced/optimization.html#performance

And, it's difficult to deal with environments such as service workers.

• Service Worker fails in dev if runtimeOnly flag is set to false #1333

In addition, it is difficult to import i18n resources dynamically from a DB or other source via the backend API.

• Support fetching locales from api #957

related issues

nuxt i18n module v8 beta has currently some issues triggered by pre-compilation of the message compiler:

• i18n build crash on pre-render: e.g i18n crashes app with custom nitro pre-render config nuxt-modules/i18n#2086
• pre-compile step on middlewares: middlewares can crash precompile step nuxt-modules/i18n#2139
• deploy failed on edge side hosting: e.g. v8.0.0-beta11 Cloudflare Worker deployment fails nuxt-modules/i18n#2095
• required "type": "module": e.g. add "type": "module" to package.json cause build failed on AWS Amplify nuxt-modules/i18n#2142

[kazupon]

bench mark:

> node ./benchmark/index.mjs

compilation:

compile simple message x 312,721 ops/sec ±1.47% (96 runs sampled)
compile complex message x 49,949 ops/sec ±0.51% (95 runs sampled)

simple pattern on 1000 resources (AOT):

resolve time with core x 250,851 ops/sec ±0.69% (98 runs sampled)
resolve time on composition x 91,027 ops/sec ±0.68% (96 runs sampled)
resolve time on composition with compile cache x 222,005 ops/sec ±0.31% (100 runs sampled)

simple pattern on 1000 resources (JIT):

resolve time with core x 252,275 ops/sec ±0.19% (100 runs sampled)
resolve time on composition x 93,385 ops/sec ±0.64% (97 runs sampled)
resolve time on composition with compile cache x 221,485 ops/sec ±0.45% (100 runs sampled)

simple pattern on 1000 resources (JIT + AOT):

resolve time with core x 315,706 ops/sec ±0.36% (97 runs sampled)
resolve time on composition x 227,192 ops/sec ±0.57% (98 runs sampled)
resolve time on composition with compile cache x 228,938 ops/sec ±0.76% (96 runs sampled)

complex pattern on 1000 resources (AOT):

resolve time with core x 217,489 ops/sec ±0.90% (99 runs sampled)
resolve time on composition x 31,493 ops/sec ±0.72% (96 runs sampled)
resolve time on composition with compile cache x 192,985 ops/sec ±0.15% (98 runs sampled)

complex pattern on 1000 resources (JIT):

resolve time with core x 204,574 ops/sec ±0.26% (99 runs sampled)
resolve time on composition x 33,833 ops/sec ±0.82% (96 runs sampled)
resolve time on composition with compile cache x 180,907 ops/sec ±0.38% (100 runs sampled)

complex pattern on 1000 resources (JIT + AOT):

resolve time with core x 277,086 ops/sec ±0.20% (98 runs sampled)
resolve time on composition x 103,517 ops/sec ±0.82% (96 runs sampled)
resolve time on composition with compile cache x 104,429 ops/sec ±0.44% (100 runs sampled)