Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build error after 10.0.1 migration #1957

Closed
4 tasks done
NathanSoyhuce opened this issue Sep 18, 2024 · 3 comments
Closed
4 tasks done

Build error after 10.0.1 migration #1957

NathanSoyhuce opened this issue Sep 18, 2024 · 3 comments
Labels
Status: Need More Info Lacks enough info to make progress

Comments

@NathanSoyhuce
Copy link

Reporting a bug?

I get an error on build after migrating to version 10.0.1
Seems similar to #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’écran 2024-09-18 à 14 44 22

Additional context

I'm using pnpm

Validations

@NathanSoyhuce NathanSoyhuce added the Status: Review Needed Request for review comments label Sep 18, 2024
@kazupon kazupon added Status: Need More Info Lacks enough info to make progress and removed Status: Review Needed Request for review comments labels Sep 21, 2024
Copy link

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
👉 Reproduction starter with unpluguin-vue-i18n

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:

@NathanBnm
Copy link

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

@kazupon
Copy link
Member

kazupon commented Oct 6, 2024

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

@kazupon kazupon closed this as completed Oct 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Status: Need More Info Lacks enough info to make progress
Projects
None yet
Development

No branches or pull requests

3 participants