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

[Bug Report][3.3.7] breaks Vue 3.2.X Support #17755

Closed
mgaller opened this issue Jul 7, 2023 · 5 comments
Closed

[Bug Report][3.3.7] breaks Vue 3.2.X Support #17755

mgaller opened this issue Jul 7, 2023 · 5 comments
Assignees
Labels
P: low The issue is of low importance T: bug Functionality that does not work as intended/expected
Milestone

Comments

@mgaller
Copy link

mgaller commented Jul 7, 2023

Environment

Vuetify Version: 3.3.7
Last working version: 3.3.6
Vue Version: 3.2.47
Browsers: Firefox 115.0
OS: Windows 10

Steps to reproduce

This breaks by import of "toValue" which is only available in vue version 3.3 and higher
https://github.com/vuetifyjs/vuetify/blob/master/packages/vuetify/src/composables/filter.ts
https://vuejs.org/api/reactivity-utilities.html#tovalue

Expected Behavior

Should work

Actual Behavior

Dies with
ambiguous indirect export: toValue

Reproduction Link

https://play.vuetifyjs.com/#...

Other comments

If at least vue version 3.3 is required, this should at least be listed in the changes.

@KaelWD KaelWD added T: bug Functionality that does not work as intended/expected P: low The issue is of low importance labels Jul 7, 2023
@KaelWD KaelWD self-assigned this Jul 7, 2023
@KaelWD KaelWD added this to the v3.3.x milestone Jul 7, 2023
@github-actions github-actions bot removed the S: triage label Jul 7, 2023
@KaelWD KaelWD closed this as completed in 112508f Jul 7, 2023
@rjcalifornia
Copy link

@KaelWD How do I fix this on the project? It still gives me error even when I updated Vuetify

@KaelWD
Copy link
Member

KaelWD commented Jul 12, 2023

It wasn't released yet. Why are you guys updating vuetify but not vue anyway?

@rjcalifornia
Copy link

@KaelWD Yeah well, it was working on my computer however I use Vercel to deploy my projects. It was working well in Vercel until this week in which I pushed a small change to master. So.... That's how I got here.

@KaelWD
Copy link
Member

KaelWD commented Jul 12, 2023

That's why lockfiles exist, so every environment has the exact same packages.

@rjcalifornia
Copy link

That's why lockfiles exist, so every environment has the exact same packages.

Yeah, that's what I thought too yet this happened. Luckily, it was just a font color change nothing relevant.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P: low The issue is of low importance T: bug Functionality that does not work as intended/expected
Projects
None yet
Development

No branches or pull requests

3 participants