core
core copied to clipboard
vuejs
fix: `<Suspense>` + `<Transition>` means mounted() runs too early
close #5844
fix: <Suspense> + <Transition> means mounted() runs too early
when will this be release ? This issue causes bugs on nuxt 3 which make it difficult to use in production for the moment
Oh, this would solve soooooo many issues we're having with Nuxt 3 right now, please please give this the love it deserves! 🙏
@stikoo agreed... For me this issue makes nuxt 3 pretty much pointless. It made me lose so much time trying to figure out the least ugly workarounds 🤯
No disrespect to Vue maintainers, but I just find amazing that it's been a year since this PR was posted and there are no signs of merging yet. This bug heavily impacts the biggest and most used Vue framework, Nuxt 3, and makes it a huge pain to deal with what would be an otherwise excellent DX (and UX for that matter).
This single issue is preventing me from trying to migrate our next projects to the Nuxt 3 ecosystem, it's a pretty huge deal breaker 😢
For anyone else waiting, this composable can work as an interim solution: https://github.com/nuxt/nuxt/issues/13471#issuecomment-1449898517
For anyone else waiting, this composable can work as an interim solution: nuxt/nuxt#13471 (comment)
The workaround is Cool! PlayGround
https://github.com/nuxt/nuxt/issues/13471#issuecomment-1449898517
We rely on this in our workflow, this seems to happen only when JS transitions are used and with mode "out-in" if I'm not wrong. Commenting to follow updates.
Would be nice if this bug could be squeezed. Stuck in Nuxt3 workarounds for now.
I can't believe it's been 1 year + 2 months since this PR was created and it's still not merged? This is a pretty major bug and the kind of bug that can break applications without realising it. Is this normal? It would be great if we can get this merged in and sorted once and for all. Thanks.
1 year and 3 months and counting, what's is stopping this from being merged?
Out of curiosity, is this shelved or pending merging? From a creative development standpoint, it makes migrating to Vue 3 hard so it would great to get an update on it. Also, to assess if a search to an alternative solution (or framework) needs to happen in the case where the current behavior is the intended behavior
- This is a p4 issue, meaning we'll prioritize it when reviewing and merging the next batch of PRs.
- But this PR, in its current status, isn't ready for merge (or even for review) because it lacks tests. Besides, the branch is far behind the current main branch. The code must be rebased first.
- If you are really bothered by the bug, there's a workaround in the comments: https://github.com/nuxt/nuxt/issues/13471#issuecomment-1449898517 Please give it a try.
@sodatea Thanks for updating us 💖 I can vouch for the aforementioned workarounds, I'm currently using them successfully. But it will be great to see a proper solution.
@sodatea Dear Vue team members.
I would like to inquire if there is a plan for merging PRs? While I have been in the process of upgrading to Vue 3, I have encountered several issues, and some of these issues could be resolved through specific PRs. However, these PRs have remained in a state of suspension for some time now. Consequently, I have had to resort to alternative methods to address my problems, but I believe this is not an ideal approach. Moreover, these temporary solutions may potentially lead to issues in my application once these PRs are eventually fixed.
@sodatea Dear Vue team members.
I would like to inquire if there is a plan for merging PRs? While I have been in the process of upgrading to Vue 3, I have encountered several issues, and some of these issues could be resolved through specific PRs. However, these PRs have remained in a state of suspension for some time now. Consequently, I have had to resort to alternative methods to address my problems, but I believe this is not an ideal approach. Moreover, these temporary solutions may potentially lead to issues in my application once these PRs are eventually fixed.
I have pack of answers there: https://github.com/vuejs/core/discussions/7050 https://github.com/vuejs/core/discussions/8560
@daniluk4000 I hope it can be processed as soon as possible, many issues have been bothering me for a long time.
@daniluk4000 I hope it can be processed as soon as possible, many issues have been bothering me for a long time.
Lol I didn't see you literally commented the last one, sorry.
I hope it can be processed as soon as possible
So do I.
