<i18n-t> error after packaging

[Lucas-lululu]

Reporting a bug?

The development environment can be used but the formal environment is wrong

Expected behavior

Hope it works

Reproduction

vue <template #world> 123 en.js export default { hello: 'hello {world}' } vite.config

System Info

System:
    OS: macOS 12.5
    CPU: (8) x64 Intel(R) Core(TM) i5-8257U CPU @ 1.40GHz
    Memory: 30.12 MB / 8.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.5.0 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 7.19.1 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Browsers:
    Chrome: 104.0.5112.101
    Firefox: 100.0
    Safari: 15.6
  npmPackages:
    @intlify/unplugin-vue-i18n: ^0.5.0 => 0.5.0 
    @vitejs/plugin-vue: ^3.0.3 => 3.0.3 
    vite: ^3.0.7 => 3.0.8 
    vue: ^3.2.37 => 3.2.37 
    vue-i18n: 9 => 9.2.2

Screenshot

No response

Additional context

No response

Validations

• [X] Read the Contributing Guidelines
• [X] Read the Documentation
• [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• [X] Check that this is a concrete bug. For Q&A open a GitHub Discussion
• [X] The provided reproduction is a minimal reproducible example of the bug.

[Lucas-lululu]

When @intlify/unplugin-vue-i18n is not applicable, the official environment will not report an error, but the development environment will display a warning

[kazupon]

Thank you for your reporting!

Unfortunately, We couldn't check this issue without reproduction repo, and we could not resolve this issue if this issue is a bug.

Could you give us the minimum reproduction repo, please? 🙏

[Lucas-lululu]

This problem can only be reproduced by running the dist file after executing the build. You need to use @intlify/unplugin-vue-i18n, and then execute npm run build

[kazupon]

Close in-activity We need a solution to this issue, but we need the minimue reproduction code that can actually confirm the issue with anyone. we need a github repo or stackbliz where anyone can reproduce the issue. If you would be faced this issue agina, please you would open the new issue. thanks!