owner stringclasses 14
values | repo stringclasses 14
values | id int64 116k 4.61B | issue_number int32 1 181k | author stringlengths 1 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:16:18 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:22:56 | reactions unknown | author_association stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|
vuejs | core | 1,139,256,576 | 6,019 | LastHeaven | 
| 2022-05-27T04:03:15 | 2022-05-27T04:03:15 | {} | NONE |
vuejs | core | 1,139,724,809 | 6,007 | b-d-k | @zhmushan I checked the fix and approved the PR yesterday. Is there anything else that I can do? Also, is the fix going into a release anytime soon? | 2022-05-27T15:29:09 | 2022-05-27T15:29:09 | {} | NONE |
vuejs | core | 1,132,515,116 | 5,964 | yoyo837 | It seems that adding `key` can also be solved, but there is no `v-for` here. | 2022-05-20T06:16:51 | 2022-05-20T06:16:51 | {} | NONE |
vuejs | core | 1,133,640,235 | 5,976 | xiafrog | 
| 2022-05-21T14:05:31 | 2022-05-21T14:05:31 | {} | NONE |
vuejs | core | 1,133,931,837 | 5,984 | Marchcn-Ben | and I found that there are 1.5 times more doms generated in vue3 than vue2 in test project, and less performance | 2022-05-22T16:38:32 | 2022-05-22T16:38:32 | {} | NONE |
vuejs | core | 1,134,525,641 | 4,294 | AndreiSoroka | ### My draft solution
Component:
<img width="577" alt="image" src="https://user-images.githubusercontent.com/6079139/169802814-5a3fcb46-12b1-4265-b6b5-e540f2799665.png">
Types:
<img width="472" alt="image" src="https://user-images.githubusercontent.com/6079139/169803382-0dff5bce-6b72-419d-9173-cdcb72876a6a.png"... | 2022-05-23T11:00:06 | 2022-05-23T11:00:06 | {
"+1": 3,
"-1": 1
} | NONE |
vuejs | core | 1,137,332,432 | 5,957 | alex116 | > If you deliver a system with end of life components to your customer, you are knowingly exposing them to security risks.
If I build up to date software today and put it on an embedded device, and deliver it to a customer, then in 5 years it will be outdated. This is obvious. It's also completely besides the point ... | 2022-05-25T14:29:16 | 2022-05-25T14:29:16 | {} | NONE |
vuejs | core | 1,137,048,002 | 5,988 | 0x009922 | Thank you very much!
By the way, neither `/* @__PURE__ */` nor `/*#__PURE__*/` works - these marks don't make any sense. | 2022-05-25T10:04:41 | 2022-05-26T05:34:45 | {} | NONE |
vuejs | core | 1,138,197,544 | 6,007 | zhmushan | Notice that changes made to the value of the option tag react directly to the DOM, while the Input tag does not. I'll write a patch to fix it. | 2022-05-26T06:21:25 | 2022-05-26T06:21:25 | {} | CONTRIBUTOR |
vuejs | core | 1,136,593,998 | 5,990 | hiuny | @LinusBorg
~Thank you very much for the bug fix. I checked by installing the bug-fixed version ([3.2.36](https://github.com/vuejs/core/releases/tag/v3.2.36)). However, the `container._vnode = vnode` code seems to be missing. Please check if the build is not successful.~
Oh, I misunderstood. Sorry. When is the rele... | 2022-05-25T01:14:31 | 2022-05-27T06:14:29 | {} | NONE |
vuejs | core | 1,133,350,489 | 5,971 | cabal95 | @yyx990803 Yes, 3.2.35 does indeed fix the problem! Thanks for the quick response, really appreciate it! | 2022-05-20T20:42:15 | 2022-05-20T20:42:15 | {} | NONE |
vuejs | core | 1,133,916,615 | 5,957 | alex116 | @yyx990803 we want to have reproducible builds for our embedded system that builds node in docker and then uses that binary node to build the web interface. How can we be independent of this forced upgrade and continue to use node 12 in the future? I am trying to use package lock/shrinkwrap but this mishap just complet... | 2022-05-22T15:11:41 | 2022-05-22T15:11:41 | {} | NONE |
vuejs | core | 1,134,025,097 | 5,977 | yyx990803 | This is a usage question and not for the issue list. | 2022-05-22T23:59:53 | 2022-05-22T23:59:53 | {} | MEMBER |
vuejs | core | 1,132,210,824 | 4,294 | AndreiSoroka | Question: Is it possible to force webpack to import and then paste the type before compiling?
For example:
code
``` vue
<script lang="ts" setup>
import { SharedProps } from "./sharedProps.ts";
interface Props extends SharedProps {}
const props = defineProps<Props>(); // The type props.foo can be inferred ... | 2022-05-19T21:09:56 | 2022-05-19T21:09:56 | {} | NONE |
vuejs | core | 1,132,418,949 | 5,963 | netlify[bot] | ### <span aria-hidden="true">👷</span> Deploy request for *vue-next-template-explorer* pending review.
[Visit the deploys page to approve it](https://app.netlify.com/sites/vue-next-template-explorer/deploys)
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</spa... | 2022-05-20T03:25:06 | 2022-05-20T03:25:06 | {} | NONE |
vuejs | core | 1,132,514,270 | 5,964 | yoyo837 | > Moving the `:key` binding from `<template>` to `<slot>` resolves the issue:
>
> ```
> <van-loading>
> <template v-for="(_, slot) of $slots" v-slot:[slot]="scope">
> 👇
> <slot :name="slot" v-bind="scope" :key="slot" />
> </template>
> </van-loading>
> ```
> ... | 2022-05-20T06:15:26 | 2022-05-20T06:15:26 | {} | NONE |
vuejs | core | 1,133,038,651 | 5,958 | yyx990803 | fixed via cf554801 | 2022-05-20T15:28:57 | 2022-05-20T15:28:57 | {} | MEMBER |
vuejs | core | 1,133,123,505 | 3,796 | yyx990803 | #5416 introduced a regression because it changed the argument order of `DefineComponent`, which breaks component definitions generated via tsc/vue-tsc, and a number of other cases.
We need to find a way to do it while preserving the current argument order of `DefineComponent`. | 2022-05-20T16:57:56 | 2022-05-20T17:34:48 | {} | MEMBER |
vuejs | core | 1,135,519,068 | 5,990 | LinusBorg | ~~why would you use createSSRApp() on the client side when it's for the server-side?~~
Edit: I'm a dumb-dumb. | 2022-05-24T07:38:03 | 2022-05-24T07:38:57 | {} | MEMBER |
vuejs | core | 1,135,574,539 | 5,990 | LinusBorg | Sent a PR | 2022-05-24T08:35:19 | 2022-05-24T08:35:19 | {} | MEMBER |
vuejs | core | 1,136,482,861 | 5,957 | alex116 | @yyx990803 We have a buildroot system that we are using today with buildroot 2020 and it came with node 12. If I deliver this system to a customer in an embedded system and they have an issue, I want to reproduce this exact build that they have on their system without having to resort to newer software. If I use gcc-5 ... | 2022-05-24T22:16:30 | 2022-05-24T22:16:30 | {} | NONE |
vuejs | core | 1,136,688,265 | 4,344 | linuschinsay | > use webpack resolve vue to one package reference.
how do I do that? | 2022-05-25T03:34:56 | 2022-05-25T03:34:56 | {} | NONE |
vuejs | core | 1,132,418,942 | 5,963 | netlify[bot] | ### <span aria-hidden="true">👷</span> Deploy request for *vuejs-coverage* pending review.
[Visit the deploys page to approve it](https://app.netlify.com/sites/vuejs-coverage/deploys)
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | bafdd... | 2022-05-20T03:25:05 | 2022-05-20T03:25:05 | {} | NONE |
vuejs | core | 1,132,521,964 | 5,964 | tony19 | Your usage in that blitz doesn't make sense to me. To forward the default slot, just use `<slot/>`:
```html
<template>
<van-loading v-bind="$attrs">
<slot />
</van-loading>
</template>
```
[demo](https://stackblitz.com/edit/vue3-forwarding-slots-pkmvmx?file=src%2Fcomponents%2FComponentB.vue) | 2022-05-20T06:26:56 | 2022-05-20T06:26:56 | {} | CONTRIBUTOR |
vuejs | core | 1,132,032,800 | 5,960 | 07akioni | Simple workaround (may not work for all scenes): Add `@vue/shared` as dep & add this to your project.
```
// type-fix.d.ts
import type {} from '@vue/shared'
```
---
After some time of exploration, I found the problem is a bit complex. It's caused by a series of combinations of different packages (vue, vue-t... | 2022-05-19T18:15:32 | 2022-05-20T10:16:45 | {} | CONTRIBUTOR |
vuejs | core | 1,133,138,588 | 5,958 | yyx990803 | The optional chaining is unnecessary, but the intention **was** to fix the syntax in Node 12.
This can be merged as a refactor/chore but not a fix. | 2022-05-20T17:15:37 | 2022-05-20T17:16:12 | {} | MEMBER |
vuejs | core | 1,133,535,489 | 5,973 | zhmushan | related: https://github.com/vuejs/core/commit/59cf2958e7bae5f1e13953373fcdbb4ad988be6c | 2022-05-21T05:08:17 | 2022-05-21T05:08:17 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,135,983,851 | 5,960 | DrJume | I could not reproduce this issue with `vue@3.2.34` anymore, seems `Volar` uses the newer version of `vue@3.2.36` with the fixed regression. | 2022-05-24T14:12:56 | 2022-05-24T14:12:56 | {} | CONTRIBUTOR |
vuejs | core | 1,136,861,008 | 6,003 | zhmushan | Notice the editor's scrollbar is not adapted to dark mode, set color-scheme to solve this | 2022-05-25T07:10:30 | 2022-05-25T07:10:30 | {} | CONTRIBUTOR |
vuejs | core | 1,131,841,926 | 5,957 | liulinboyi | > > 我看了看，是因为这个[build: output es2020 (target node 14+) for cjs/server builds](https://github.com/vuejs/core/commit/cbeb9f2d7859edbaceee0c73d2b33c578a1ffb58)，从[v3.2.34-beta.1](https://github.com/vuejs/core/releases/tag/v3.2.34-beta.1)开始，编译产物就是`es2020`了，需要`node`版本`node 14+`。
>
> 但是 官方是 >=12 就可以噻
[Vite docs](https://... | 2022-05-19T15:02:44 | 2022-05-19T15:02:44 | {} | MEMBER |
vuejs | core | 1,131,922,708 | 5,960 | DrJume | I updated the reproduction to use .tsx and included a demo use case.
The error is in `GenericList.tsx`:
| 2022-05-19T16:17:26 | 2022-05-19T16:17:26 | {} | CONTRIBUTOR |
vuejs | core | 1,133,134,568 | 5,960 | yyx990803 | I believe this was caused by https://github.com/vuejs/core/commit/98b821d94a0a0fb4d7701809da6bec331a47e6e5 which altered the argument order of `DefineComponent`.
Should be fixed by 8071ef47 which reverts the change. (Update: out in 3.2.35) | 2022-05-20T17:12:20 | 2022-05-20T17:21:09 | {} | MEMBER |
vuejs | core | 1,134,026,989 | 5,984 | yyx990803 | 1. There is no version of Vue that supports the `:scope` syntax on slots.
2. The `slot-scope` syntax has been [deprecated since 2.6](https://v2.vuejs.org/v2/guide/components-slots.html#Deprecated-Syntax) and no longer supported in Vue 3. Please read [relevant sections on slots in Vue 3 docs](https://vuejs.org/guide/co... | 2022-05-23T00:07:04 | 2022-05-23T00:07:04 | {} | MEMBER |
vuejs | core | 1,134,029,594 | 5,983 | yyx990803 | This is a known issue and **expected behavior**.
In short, when you use the following syntax:
```js
class Foo {
constructor() {
this // <-- this is the raw object and not the reactive proxy
}
inc = () => {
this // <-- same as above
}
normal() {
this // <-- this is the reactive pro... | 2022-05-23T00:16:33 | 2022-05-23T00:18:44 | {} | MEMBER |
vuejs | core | 1,135,524,328 | 5,990 | hiuny | When using ssr, must use 'createSSRApp()' on the client side. This is also stated in the vue.js ssr guide document. https://vuejs.org/guide/scaling-up/ssr.html#client-hydration
<img width="300" src="https://user-images.githubusercontent.com/2697067/169976435-434ff6b2-bcce-4bf3-a77e-167757534a3c.png">
| 2022-05-24T07:43:53 | 2022-05-24T07:43:53 | {} | NONE |
vuejs | core | 1,137,709,138 | 6,005 | yyx990803 | This is not a valid reproduction. | 2022-05-25T18:45:42 | 2022-05-25T18:45:42 | {} | MEMBER |
vuejs | core | 1,137,719,233 | 6,006 | yyx990803 | There is no error in the reproduction link. Make sure to provide actual reproductions. | 2022-05-25T18:50:04 | 2022-05-25T18:50:04 | {} | MEMBER |
vuejs | core | 1,138,552,855 | 6,015 | liulinboyi | [Preview](https://deploy-preview-6015--vue-sfc-playground.netlify.app/#__SSR__eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2PlxuICAgIEEgPHdicj4gPGNvZGU+MDwvY29kZT4gPHdicj4gQiA8d2JyPiA8Y29kZT4xPC9jb2RlPiBDIDxjb2RlPjI8L2NvZGU+IDx3YnI+IEQgPHdicj4gPGNvZGU+RTwvY29kZT5cbiAgPC9kaXY+XG48L3RlbXBsYXRlPiIsImltcG9ydC1tYXAuanNvbiI6Intcbi... | 2022-05-26T13:02:58 | 2022-05-26T13:02:58 | {} | MEMBER |
vuejs | core | 1,406,366,726 | 5,525 | johanmolen | @liulinboyi
This is a simplified example:
https://stackblitz.com/edit/vitejs-vite-bqescg?file=src/App.vue
Works fine in dev but not once it is builded.
| 2023-01-27T11:24:35 | 2023-01-27T11:24:35 | {} | NONE |
vuejs | core | 1,409,231,351 | 7,606 | franck102 | The linked issue put me on the right track, calling useXxxStore from main.js before the Vue app is mounted is a valid workaround, watchEffect gets called with currentInstance = null and the effect works normally. | 2023-01-30T19:42:26 | 2023-01-30T19:42:26 | {} | NONE |
vuejs | core | 1,411,290,536 | 7,614 | edison1105 | as a workaround
```html
<Canvas :data='[...data]' />
``` | 2023-02-01T01:02:45 | 2023-02-01T01:02:45 | {} | MEMBER |
vuejs | core | 1,411,728,249 | 7,590 | yyx990803 | My concern with this is that it doesn't really address the the fundamental issue, since `currentInstance` isn't the only global singleton that the Vue runtime relies on. Some other examples include the reactivity tracking maps and built-in VNode type symbols like `Text` or `Fragment`. Only addressing `currentInstance` ... | 2023-02-01T09:24:21 | 2023-02-01T09:24:21 | {} | MEMBER |
vuejs | core | 1,412,228,145 | 7,530 | sxzz | Close this pr because it has been fixed by @yyx990803 https://github.com/vuejs/core/commit/957722c4185ea87aabc711f6f8997e528dd3ba1b
| 2023-02-01T15:14:33 | 2023-02-01T15:14:33 | {} | MEMBER |
vuejs | core | 1,406,260,136 | 7,584 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a15e88df78201f15f80cf374b15f01af92580304 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-27T09:44:20 | 2023-01-27T09:44:20 | {} | NONE |
vuejs | core | 1,411,737,947 | 5,998 | yyx990803 | Thanks for working on the fix - see https://github.com/vuejs/core/issues/5996#issuecomment-1411737604 | 2023-02-01T09:31:35 | 2023-02-01T09:31:35 | {} | MEMBER |
vuejs | core | 1,413,893,590 | 7,630 | sqal | When you declare an event in defineEmits, it will be removed from the $attrs because it is stored **internally** elsewhere.
Duplicate https://github.com/vuejs/core/issues/5319
There is no official API for getting declared events passed from the parent component, I don't know if this is something that is planned t... | 2023-02-02T15:07:04 | 2023-02-02T15:10:50 | {} | CONTRIBUTOR |
vuejs | core | 1,308,159,359 | 6,459 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | adfb68ad2fd0627885f0b621f5140f2fd4c05fa7 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-09T03:32:18 | 2023-01-26T17:11:27 | {} | NONE |
vuejs | core | 1,408,112,728 | 7,603 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ff377b765775b1106f8da44139dc7d0e7fa19b52 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-30T07:24:02 | 2023-01-30T07:24:02 | {} | NONE |
vuejs | core | 1,408,327,778 | 4,344 | tangjiahui-cn | > components
'isCE' happen because which has two differece vue verdion. you can try use 'external' to exclude another vue in components. | 2023-01-30T10:07:37 | 2023-01-30T10:07:37 | {} | NONE |
vuejs | core | 1,409,162,553 | 7,606 | franck102 | I cannot use a regular watch, as I mentioned the sample code above is an inlined version of VueUse:computedAsync.
Here is the original store:
```
import { defineStore } from "pinia"
import { epClient } from "@/common-services/epClient"
import { recomputedAsync } from "@/common-services/vue-recomputed-async"
i... | 2023-01-30T18:56:18 | 2023-01-30T18:56:18 | {} | NONE |
vuejs | core | 1,407,351,555 | 7,593 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 28be6730f423662187d332c6579d9bacad2cd44b |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-28T09:21:19 | 2023-01-31T11:11:11 | {} | NONE |
vuejs | core | 1,410,279,792 | 7,329 | MBoretto | Is there any quick fix for that? | 2023-01-31T12:42:54 | 2023-01-31T12:42:54 | {} | NONE |
vuejs | core | 1,410,825,680 | 7,612 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | aadd76cc8ae7053cb483f2fc576e38102705d206 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-31T17:57:31 | 2023-01-31T17:57:31 | {} | NONE |
vuejs | core | 1,411,175,070 | 7,329 | MichaelDeBoey | @MBoretto The fix would be helping me re-implement it in https://github.com/remorses/esbuild-plugins/pull/29 without that bug 🤷♂️
| 2023-01-31T22:46:22 | 2023-01-31T22:46:22 | {
"eyes": 2
} | NONE |
vuejs | core | 1,413,325,921 | 4,662 | HaloElite | As a simple workaround exclude the styles into a css-file and import it inside the `<style>` tag of the `main.ce.vue` file. | 2023-02-02T08:24:10 | 2023-02-02T08:24:45 | {} | NONE |
vuejs | core | 1,413,678,552 | 3,875 | cryi | Is there any point to keep this open @posva @yyx990803 ? | 2023-02-02T12:38:54 | 2023-02-02T12:38:54 | {} | NONE |
vuejs | core | 1,408,874,736 | 7,448 | weidehai | because vue didn't removeEventlistener explicit（in modern browser，removeEventlistener will be call automatic after dom remove），the question you mentioned that event listeners not going down,I guess the reason is browser control it clear action at specific conditions(not exactly at remove dom),and after reach a certai... | 2023-01-30T15:57:41 | 2023-01-30T15:57:41 | {
"confused": 1
} | NONE |
vuejs | core | 1,411,293,522 | 7,614 | yurivish | Hi @edison1105, thanks for the quick response! Your workaround is a good one for the specific example I gave in the issue, but has performance implications that prevent it from being a workaround in my actual use case, where the data is a large Uint8Array representing the ImageData of a canvas.
One alternative work... | 2023-02-01T01:05:25 | 2023-02-01T01:29:39 | {} | NONE |
vuejs | core | 1,411,674,277 | 4,344 | zongzi531 | > why this has been closed even if the error happen all the time ? we should have hard tests on that as it seems people have it a lot when using module federation or library components
>
> none of the solutions works unfortunately with latest vue version + vite 4
@flozero You can try this config set at vue@3.2.x ... | 2023-02-01T08:46:43 | 2023-02-01T08:46:43 | {} | NONE |
vuejs | core | 1,412,166,967 | 7,329 | p-m-p | I added https://github.com/remorses/esbuild-plugins/pull/32 on top of @MichaelDeBoey PR to fix those internal modules. It's quite hard to test in that repo but I think it solve the issue. | 2023-02-01T14:38:38 | 2023-02-01T14:38:38 | {} | NONE |
vuejs | core | 1,412,489,246 | 6,095 | Akryum | Seeing the 3rd one randomly too | 2023-02-01T17:59:39 | 2023-02-01T17:59:39 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,412,825,767 | 7,614 | yurivish | > @yurivish The Playground you linked is slightly misleading. Both the parent and child templates will unwrap refs, so it isn't immediately clear in each example whether the unwrapping is occurring in the parent or the child.
I was using the output of the handy JS inspector in the playground to see where the unwrapp... | 2023-02-01T22:28:03 | 2023-02-01T23:21:59 | {} | NONE |
vuejs | core | 1,413,099,841 | 7,116 | godxiaoji | > @godxiaoji Thank you very much for the PR - @sxzz came up with a better alternative in #7619 that retains the ability to jump to definition on props properties, but we really appreciate your contribution!
Is my pleasure. @yyx990803 I have a few pr, free also trouble to review #7133 #6827 #6773 #6765. | 2023-02-02T03:27:40 | 2023-02-02T03:27:40 | {} | CONTRIBUTOR |
vuejs | core | 1,413,244,705 | 7,606 | edison1105 | @posva
duplicate of https://github.com/vuejs/core/issues/7319
it works on the latest version. [see](https://sfc.vuejs.org/#eNp9VM2OmzAQfhWLSxJtAntOSdTVLlUvVauwVS9cCBkCu2Aj25Ctsnn3ztiYECJVHGzPzzff/DBn76lp/K4Fb+2FGuqmSjVsE85YeCg7llWpUpvEywrI3hPPKFBV8qbVTP9twOn24iPxWLeqxQEqFKpCnFBQHq73wHlX6R4qlgs56LYxHkwXwMIMAbaxFhJ+K5... | 2023-02-02T07:03:13 | 2023-02-02T07:03:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,413,922,515 | 7,630 | LinusBorg | Events that are not declared *are* part of `attrs`. *Declared* component events are not, because by default, all `attrs` are passed on to a component's root element, and you likely don't want your declared events to be added as a listener on some div.
the simplest way to deal with that is to just wrap the emit funct... | 2023-02-02T15:25:54 | 2023-02-02T15:25:54 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,406,800,400 | 7,578 | vaakian | seems it works only in `template` that the compiler will wrap booleans with [`toDisplayString`](https://github.com/vuejs/core/blob/a51f935b72c7467e234221b6e1559b18f1cb8ceb/packages/shared/src/toDisplayString.ts#L16).
Check JS on the right: [Vue SFC playrgound](https://sfc.vuejs.org/#eNo9TksOwiAQvQqZtYV9g028B5u2otIUm... | 2023-01-27T17:10:54 | 2023-01-27T17:13:55 | {} | CONTRIBUTOR |
vuejs | core | 1,407,064,247 | 7,590 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c52939698a2e0610dd06e752743b225dfefb8218 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-27T20:55:04 | 2023-01-27T20:55:04 | {} | NONE |
vuejs | core | 1,407,618,121 | 7,597 | edison1105 | your repro is not minimal and I believe this is not related to vue-core. | 2023-01-29T10:03:27 | 2023-01-29T10:03:27 | {} | MEMBER |
vuejs | core | 1,409,746,148 | 7,607 | zhangzhonghe | Duplicate of #7121 | 2023-01-31T04:41:23 | 2023-01-31T04:41:23 | {} | MEMBER |
vuejs | core | 1,409,827,250 | 7,606 | edison1105 | @posva
> Trasfered from pinia and updated the reproduction. This is similar to #7319 but not exactly the same. Use a regular `watch()` as a workaround.
I think the root cause is exactly the same and @LinusBorg 's [PR](https://github.com/vuejs/core/pull/7330) will fix this. [see](https://deploy-preview-7330--vue-... | 2023-01-31T06:15:28 | 2023-01-31T06:15:43 | {
"hooray": 1
} | MEMBER |
vuejs | core | 1,409,894,308 | 4,294 | Caffeine19 | I have a type called IProduct
```typescript
export interface IProduct {
id: number;
name: string;
brand: string;
price: number;
images: string;
category: string;
capacity: string;
mark: number;
}
```
this way, the compiler warning
```typescript
defineProps<IProduct>();
```
my soluti... | 2023-01-31T07:31:12 | 2023-01-31T07:40:11 | {} | NONE |
vuejs | core | 1,411,538,795 | 7,614 | skirtles-code | I've seen variations on this theme a few times on Vue Land. I added a note about it a few weeks ago in the docs repo, <https://github.com/vuejs/docs/issues/849#issuecomment-1382072571>, as it's something we might want to consider documenting.
While I can understand why people find it counterintuitive, I don't think ... | 2023-02-01T06:36:52 | 2023-02-01T06:36:52 | {
"+1": 1,
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 1,411,564,334 | 7,576 | LinusBorg | I assume this sort here is not stable since a change in 3.2.38 (https://github.com/vuejs/core/commit/78c199d6dbe8931520b75d8bfe0d49366a06922a):
https://github.com/vuejs/core/blob/957722c4185ea87aabc711f6f8997e528dd3ba1b/packages/runtime-core/src/scheduler.ts#L219 | 2023-02-01T07:08:35 | 2023-02-01T07:09:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,413,358,357 | 7,188 | Alexis2004 | Hello!
Can you please tell me if there is a chance that this fix will be released soon? | 2023-02-02T08:53:15 | 2023-02-02T08:53:15 | {} | NONE |
vuejs | core | 1,308,629,102 | 7,068 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c6f252a8d1a0a0e29dc24a016288b21a61ae30b3 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-09T11:45:31 | 2023-01-26T17:22:20 | {} | NONE |
vuejs | core | 1,405,739,913 | 5,220 | jaketig | > For your specific use case, you can just switch from declaring an event to a prop:
>
> ```js
> props: ['onClose'],
> // instead of:
> emits: ['close'],
> ```
>
> Event Listeners are passed as props with an `on` prefix, so these two declarations both represent an event. Meaning, if you have an `onClose` prop... | 2023-01-26T22:12:13 | 2023-01-26T22:12:13 | {
"+1": 1
} | NONE |
vuejs | core | 1,407,622,053 | 7,553 | sxzz | Supported in Vue Macros https://github.com/sxzz/unplugin-vue-macros/commit/2a6e990be6fc523c4b43f21a1773250ce8c88273 | 2023-01-29T10:19:04 | 2023-01-29T10:31:47 | {} | MEMBER |
vuejs | core | 1,408,181,506 | 7,048 | klausXR | So, are we supposed to copy-paste this code everywhere? I don't really like this solution | 2023-01-30T08:30:00 | 2023-01-30T08:30:00 | {} | NONE |
vuejs | core | 1,411,538,678 | 7,609 | edison1105 | duplicate of #7095 | 2023-02-01T06:36:42 | 2023-02-01T06:36:42 | {} | MEMBER |
vuejs | core | 1,411,646,543 | 7,217 | btea | Close this pr because it has been updated. https://github.com/vuejs/core/commit/957722c4185ea87aabc711f6f8997e528dd3ba1b | 2023-02-01T08:26:21 | 2023-02-01T08:26:21 | {} | CONTRIBUTOR |
vuejs | core | 1,407,540,960 | 1,503 | Nick87-xkk | my vue2.7/lib is umd , this webpack config dosn't work.
so I use props to reception vue2.7/app's this.$root.
| 2023-01-29T02:24:37 | 2023-01-29T02:24:37 | {} | NONE |
vuejs | core | 1,407,566,757 | 6,926 | earlAchromatic | @edison1105 There are some use cases where it would actually be nice to have css vars work with SSR. For instance, if I am prerendering and then want to lazily hydrate some components but still have the css vars initially bound so styles show up. Not sure how Astro is doing this but my guess is you can't use css vars u... | 2023-01-29T05:32:46 | 2023-01-29T05:32:46 | {} | NONE |
vuejs | core | 1,411,334,154 | 7,614 | edison1105 | @yurivish
Another [workaround](https://sfc.vuejs.org/#eNqlU8tu2zAQ/JWFDpGMyKSTtBfHDhIUPfRWFE0vYYAw0tpWIpEEubIRGP73Li0/FDfoJRdB3NcMd4br5M45sWwxGSeTUPjKEQSk1t0oUzXOeoI1hIWua7v6hbMcfPyQr+Zz9NvASlOx+D6bYUE5WHNvGtsawhI2MPO2gZSHp4dh37RZ6rDLCNkdI36qSBllCmsCQalJw7SHmxlcwX1l6Oryznv9ll0MBtf76pn1Bd47bsI/um6RO5kll+wLuA/9UtdxJNKP... | 2023-02-01T01:56:52 | 2023-02-01T01:57:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,411,561,787 | 7,614 | LinusBorg | I agree with @skirtles-code
When working with nonreactive data, it's better to then work with immutable data as @edison1105 suggested.
| 2023-02-01T07:06:23 | 2023-02-01T07:06:23 | {} | MEMBER |
vuejs | core | 1,412,467,137 | 7,620 | LinusBorg | > If a setter manipulates multiple fields, changes are not detected properly if not all dependent getters are used within the same slot template.
Your description is missing a further detail: *"if a setter manipulates multiple *nonreactive fields* ..."*
And that's expected. Vue observes that the setter has been c... | 2023-02-01T17:45:52 | 2023-02-01T17:46:24 | {} | MEMBER |
vuejs | core | 1,412,826,603 | 7,620 | MisterGoodcat | Thank you so much for taking the time to explain the details! With these I was able to observe the chain of events in the debugger, in particular your first and last bullet points. To confirm, what I was seeing was:
- When you set a (reactive) property, a render is triggered for all places reading that property, no ... | 2023-02-01T22:28:59 | 2023-02-01T22:28:59 | {} | NONE |
vuejs | core | 1,405,328,567 | 7,119 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | daae5dcb2b562430955698514df52aadb4429537 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-26T17:10:56 | 2023-01-26T17:10:56 | {} | NONE |
vuejs | core | 1,407,331,171 | 6,745 | locki13freja | `<template>
<div v-if="posts.length > 0">
<h3>Post list</h3>
<TransitionGroup name="post-list">
<PostItem
v-for="post in posts"
:post="post"
:key="post.id"
@remove="$emit('remove', post)"
/>
</TransitionGroup>
</div>
<h2 v-else style="color: red">Post list empty</h2>
</temp... | 2023-01-28T08:24:57 | 2023-01-28T08:25:31 | {} | NONE |
vuejs | core | 1,407,392,039 | 7,584 | liuseen-l | @LinusBorg
| 2023-01-28T12:48:38 | 2023-01-28T12:48:38 | {} | CONTRIBUTOR |
vuejs | core | 1,410,785,404 | 7,601 | roydukkey | > So I think this is a volar type checking problem.
@johnsoncodehk cc | 2023-01-31T17:29:19 | 2023-01-31T17:29:19 | {} | NONE |
vuejs | core | 1,411,735,765 | 7,617 | haoqunjiang | Oops, I meant to test on my own repo first… It's not fully ready. | 2023-02-01T09:29:59 | 2023-02-01T09:29:59 | {} | MEMBER |
vuejs | core | 1,413,978,936 | 7,630 | mrhammadasif | Yes, definitely the docs need to be updated then. All confusion was because of the docs
> If you think this should be added to the docs, feel free to start a discussion on the docs repo.
Yes, will do that
| 2023-02-02T16:01:54 | 2023-02-02T16:01:54 | {} | NONE |
vuejs | core | 1,349,196,576 | 7,340 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 289f71979e76b5ca8e1b6d2f36fd1626bbcaae6a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-13T17:30:13 | 2023-01-26T17:23:11 | {} | NONE |
vuejs | core | 1,406,713,977 | 7,589 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c8cca01da86370ec7ebd66f21e314111bcc9232c |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-27T16:13:18 | 2023-01-27T16:13:18 | {} | NONE |
vuejs | core | 1,407,787,840 | 4,344 | flozero | why this has been closed even if the error happen all the time ? we should have hard tests on that as it seems people have it a lot when using module federation or library components
none of the solutions works unfortunately with latest vue version + vite 4 | 2023-01-29T22:31:13 | 2023-01-29T22:31:50 | {} | NONE |
vuejs | core | 1,408,168,194 | 7,604 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 00fd435e9173c4b21af0416608890e5caadff40c |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-30T08:19:40 | 2023-01-31T17:18:05 | {} | NONE |
vuejs | core | 1,411,487,700 | 7,576 | wellrus | So...
Is it bug? | 2023-02-01T05:25:22 | 2023-02-01T05:25:22 | {} | NONE |
vuejs | core | 1,412,632,533 | 7,614 | skirtles-code | @yurivish The Playground you linked is slightly misleading. Both the parent and child templates will unwrap refs, so it isn't immediately clear in each example whether the unwrapping is occurring in the parent or the child.
The process of passing a prop doesn't directly unwrap anything.
Top-level refs are unwrapp... | 2023-02-01T19:48:44 | 2023-02-01T19:48:44 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,413,084,534 | 6,908 | yc-huang | I have a page which use vxetable(https://vxetable.cn/v3) to display a large table. Everything works fine in dev mode, but in production it will trigger this error (type is null when calling isAsyncWrapper) when scrolling between table columns, and this fix seems to work fine for my use case... | 2023-02-02T03:03:48 | 2023-02-02T03:04:39 | {} | NONE |
vuejs | core | 1,405,341,902 | 7,536 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 40f958b6b60058247545a10a02a36156638ec416 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-26T17:21:14 | 2023-01-26T17:21:14 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.