Build error after 10.0.1 migration

NathanSoyhuce commented 2 months ago

Reporting a bug?

I get an error on build after migrating to version 10.0.1 Seems similar to https://github.com/intlify/vue-i18n/issues/1946 but not using Nuxt

Expected behavior

No error on build

Reproduction

Build the project

System Info

System:
    OS: macOS 14.6.1
    CPU: (8) arm64 Apple M1
    Memory: 70.89 MB / 8.00 GB
    Shell: 5.9 - /bin/zsh
Binaries:
    Node: 22.6.0 - /opt/homebrew/bin/node
    Yarn: 1.22.22 - /opt/homebrew/bin/yarn
    npm: 10.8.2 - /opt/homebrew/bin/npm
    pnpm: 9.10.0 - ~/Library/pnpm/pnpm
    Watchman: 2024.08.12.00 - /opt/homebrew/bin/watchman
Browsers:
    Chrome: 128.0.6613.138
    Safari: 17.6
npmPackages:
    @vitejs/plugin-vue: ^5.1.4 => 5.1.4 
    @vue/test-utils: ^2.4.6 => 2.4.6 
    @vue/typescript-plugin: ^2.0.29 => 2.1.6 
    vite: ^5.4.6 => 5.4.6 
    vite-plugin-checker: ^0.8.0 => 0.8.0 
    vite-tsconfig-paths: ^5.0.1 => 5.0.1 
    vitest: ^2.1.1 => 2.1.1 
    vue: ^3.4.38 => 3.5.6 
    vue-i18n: ^10.0.1 => 10.0.1 
    vue-router: ^4.4.5 => 4.4.5 
    vue-tsc: ^2.1.6 => 2.1.6

Screenshot

Capture d’écran 2024-09-18 à 14 44 22

Additional context

I'm using pnpm

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 Discussions

github-actions[bot] commented 2 months ago

Thank you for your feadback! Would you be able to provide a reproduction 🙏

More info

### Why do I need to provide a reproduction? Reproductions make it possible for us to triage and fix issues quickly with a relatively small team. It helps us discover the source of the problem, and also can reveal assumptions you or we might be making. ### What will happen? If you've provided a reproduction, we'll remove the label and try to reproduce the issue. If we can, we'll mark it as a bug and prioritise it based on its severity and how many people we think it might affect. If `Status: Need More Info` labeled issues don't receive any substantial activity (e.g., new comments featuring a reproduction link), we'll close them. That's not because we don't care! At any point, feel free to comment with a reproduction and we'll reopen it. ### How can I create a reproduction? We have a couple of templates for starting with a minimal reproduction: 👉 [Reproduction mininal starter](https://stackblitz.com/edit/vitejs-vite-gfrx6w) 👉 [Reproduction starter with unpluguin-vue-i18n](https://stackblitz.com/edit/vitejs-vite-jnecup) A public GitHub repository is also perfect. 👌 Please ensure that the reproduction is as **minimal** as possible. You might also find these other articles interesting and/or helpful: - [The Importance of Reproductions](https://antfu.me/posts/why-reproductions-are-required) - [How to Generate a Minimal, Complete, and Verifiable Example](https://stackoverflow.com/help/mcve)

NathanBnm commented 2 months ago

In the end I didn't reproduce the bug today, although I don't really understand what caused it.

kazupon commented 1 month ago

Closing due to inactivity. Please open a new issue with a reference to this one if you can follow up with more minimal reproduction.

Thanks

intlify / vue-i18n