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,111,766,743 | 5,820 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | fcca990647720b47330ec551275afa4da82dc893 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-28T05:33:45 | 2022-04-28T05:35:57 | {} | NONE |
vuejs | core | 1,113,118,690 | 5,764 | DrJume | When using `<script lang="ts">` everything is ok, because the TS Syntax is stripped away.
| 2022-04-29T09:44:11 | 2022-04-29T09:44:11 | {} | CONTRIBUTOR |
vuejs | core | 1,110,610,187 | 5,814 | TheOneZhen | scss | 2022-04-27T06:49:41 | 2022-04-27T06:49:41 | {} | NONE |
vuejs | core | 1,110,705,916 | 5,813 | w582745483 | > Because the `v-if`, when being false, leaves a placeholder in the vdom so it can later, when its true, be replaced with the actual content.
>
> A similar thing happens when you have a v-for loop that has zero items - it still creates a `Fragment` vnode.
why the named slot did not leave vnode? | 2022-04-27T08:27:34 | 2022-04-27T08:27:34 | {} | NONE |
vuejs | core | 1,111,766,738 | 5,820 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | fcca990647720b47330ec551275afa4da82dc893 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-28T05:33:44 | 2022-04-28T05:34:48 | {} | NONE |
vuejs | core | 1,112,062,069 | 5,824 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 3af421cef09d4124012d57a3677cf474ab461c5d |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-28T10:52:45 | 2022-04-28T12:13:17 | {} | NONE |
vuejs | core | 1,110,571,213 | 4,778 | productdevbook | some problem | 2022-04-27T05:50:56 | 2022-04-27T05:50:56 | {} | CONTRIBUTOR |
vuejs | core | 1,110,640,761 | 5,813 | LinusBorg | Because the `v-if`, when being false, leaves a placeholder in the vdom so it can later, when its true, be replaced with the actual content.
A similar thing happens when you have a v-for loop that has zero items - it still creates a `Fragment` vnode. | 2022-04-27T07:25:34 | 2022-04-27T07:25:34 | {} | MEMBER |
vuejs | core | 1,110,925,838 | 5,813 | LinusBorg | `<template v-if="..."> != <template v-slot:default v-if="....">`
the former is just a way of using v-if, unrelated to slots. so you basically just passed `<div v-if>` to the default slot again.
The latter is how you can to define a default slot alongside other named slots.
You can learn more in this secti... | 2022-04-27T12:12:28 | 2022-04-27T12:21:20 | {} | MEMBER |
vuejs | core | 1,111,887,058 | 5,818 | JulianRomana | Actually I wanted to say that the `myNestedObject` wasn't reactive, `myNestedProperty` is indeed.
I was able to reproduce what happened on my App [here](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgcmVhY3RpdmUgfSBmcm9tICd2dWUnXG5pbXBvcnQgQ29tcCBmcm9tICcuL0NvbXAudnVlJ1xuXG5jb25zdCBtc2c... | 2022-04-28T08:17:49 | 2022-04-28T08:25:03 | {} | NONE |
vuejs | core | 1,111,951,885 | 5,823 | yxw007 | 
It's working fine. I think it's your environment. Suggestion: Delete node_modules and package-lock.json and try NPM install again. If you still can't provide your node version, please refer to vite project i... | 2022-04-28T09:09:21 | 2022-04-28T09:09:21 | {} | NONE |
vuejs | core | 1,112,062,066 | 5,824 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 3af421cef09d4124012d57a3677cf474ab461c5d |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-28T10:52:45 | 2022-04-28T12:14:44 | {} | NONE |
vuejs | core | 1,113,108,358 | 5,764 | DrJume | I am using `<script lang="tsx">` because of a nice use case, where I am defining inline JSX Functional Components, which I can then use in the same `.vue` SFC and also export them for use in slots of the component. | 2022-04-29T09:30:55 | 2022-04-29T09:30:55 | {} | CONTRIBUTOR |
vuejs | core | 1,110,597,271 | 5,813 | liulinboyi | You can use `useSlots` like this:
### [example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBuYW1lPVwiQXBwXCI+XG5pbXBvcnQgQ2hpbGQgZnJvbSAnLi9DaGlsZC52dWUnXG48L3NjcmlwdD5cblxuPHRlbXBsYXRlPlxuICA8Q2hpbGQ+XG4gICAgPGgxPkFwcDwvaDE+XG4gICAgPGgyIHYtaWY9XCJmYWxzZVwiPkFwcCBoMjwvaDI+XG4gIDwvQ2hpbGQ+XG48L3RlbXBsYXRl... | 2022-04-27T06:32:33 | 2022-04-27T06:36:40 | {} | MEMBER |
vuejs | core | 1,110,633,571 | 5,813 | LinusBorg | You can use the "named slot" pattern with the default slot as well:
```html
<Child>
<template v-slot:default v-if="someCondition">
</template>
</Child>
``` | 2022-04-27T07:17:03 | 2022-04-27T07:17:13 | {} | MEMBER |
vuejs | core | 1,110,937,063 | 5,815 | LinusBorg | Please open an issue with their repo, or provide a demo that doesn't require `vue.draggable`. We don't debug 3rd party libraries | 2022-04-27T12:23:56 | 2022-04-27T12:23:56 | {} | MEMBER |
vuejs | core | 1,110,998,353 | 5,813 | w582745483 | As described in the vue documentation:
When a component accepts both a default slot and named slots, all top-level non-<template> nodes are implicitly treated as content for the default slot.
I think v-if in div with no name slot should be treated as default slot tag,not as placeholder in vdom,because it is rendere... | 2022-04-27T13:23:39 | 2022-04-27T13:26:12 | {} | NONE |
vuejs | core | 1,111,115,606 | 5,813 | LinusBorg | The behaviour is correct as I described. if you need assistance in better understanding what that means, feel free to reach out to the community on chat.vuejs.org
I don't have the capacity to continue this. The issue is closed and resolved. | 2022-04-27T15:05:11 | 2022-04-27T15:05:11 | {} | MEMBER |
vuejs | core | 1,111,666,728 | 5,819 | hchlq | Personally, I think the forAliasRE can be changed
```js
// origin
const forAliasRE = /([\s\S]*?)\s+(?:in|of)\s+([\s\S]*)/
// suggestion
const forAliasRE = /([\s\S]*?)\s+(?:in|of)\s+([^\s]+)/
```
| 2022-04-28T02:17:43 | 2022-04-28T02:17:43 | {} | CONTRIBUTOR |
vuejs | core | 1,111,773,058 | 5,821 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c31788b208b6317dddece7539d1172d7ac06edcd |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-28T05:47:54 | 2022-04-29T03:08:40 | {} | NONE |
vuejs | core | 1,113,115,489 | 5,764 | DrJume | Here I am using a type assertion, because Vue does not currently support infered slot types, so I need to set them manually, as the current slot type is `any`. | 2022-04-29T09:40:01 | 2022-04-29T09:40:01 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,113,152,353 | 5,764 | liulinboyi | ## [Passing Slots](https://vuejs.org/guide/extras/render-function.html#passing-slots)
### [Example](https://stackblitz.com/edit/vue-issue-repro-5764-whtmcj?file=src%2FApp.vue&terminal=dev)
### App.vue
```typescript
<!-- <script lang="ts" setup> WORKS -->
<script lang="tsx">
import PersonComponent from './compo... | 2022-04-29T10:28:24 | 2022-04-29T10:28:24 | {} | MEMBER |
vuejs | core | 1,110,091,336 | 5,810 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | dc5ad36a2b0a49aa93cf16252257071c92bc90e9 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-26T17:58:01 | 2022-04-27T01:34:38 | {} | NONE |
vuejs | core | 1,110,091,335 | 5,810 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | dc5ad36a2b0a49aa93cf16252257071c92bc90e9 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-26T17:58:01 | 2022-04-27T01:39:30 | {} | NONE |
vuejs | core | 1,110,617,522 | 5,813 | w582745483 | I just use like this
<Parent>
<slot></slot>
</Parent>
in the Parent Component log next line content
const slotDefault = useSlots().default;
console.log('slotDefault', slotDefault);
App is right here Parent Component
| 2022-04-27T06:59:08 | 2022-04-27T06:59:08 | {} | NONE |
vuejs | core | 1,110,631,798 | 5,813 | liulinboyi | >
> in the Dialog Component log slot.default is not null,but just like your example ,use named slot can work,I want to know why?
### this is name slot:
[example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBuYW1lPVwiQXBwXCI+XG5pbXBvcnQgQ2hpbGQgZnJvbSAnLi9DaGlsZC52dWUnXG48L3NjcmlwdD5cblxuPHRlbXB... | 2022-04-27T07:14:49 | 2022-04-27T07:14:49 | {} | MEMBER |
vuejs | core | 1,110,646,016 | 5,813 | liulinboyi | > I just want to know why use default slot the console in my Dialog component is not null 
### the code
```
<template v-if="false">App</template>
```
### is also a vnode.
)
const app = createApp(App)
app.mount('#app')
```
I added inline CSS for shadow root but styles are... | 2022-04-27T21:33:03 | 2022-04-27T21:33:03 | {} | NONE |
vuejs | core | 1,112,833,304 | 5,829 | Justineo | 这是符合预期的。你在模板中自增会相当于在渲染时修改响应式数据，于是重新触发渲染，造成无限递归。 | 2022-04-29T03:00:15 | 2022-04-29T03:00:15 | {} | MEMBER |
vuejs | core | 1,111,773,061 | 5,821 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c31788b208b6317dddece7539d1172d7ac06edcd |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-28T05:47:54 | 2022-04-29T03:06:48 | {} | NONE |
vuejs | core | 1,112,872,675 | 5,823 | sadashivm | Hello @yxw007
Here is the node version detail,
**node version - v16.14.2
npm - 8.7.0**
I aslo tried removing the node_modules folder and package-lock.json file. Still I'm getting the same issue | 2022-04-29T04:45:27 | 2022-04-29T04:45:27 | {} | NONE |
vuejs | core | 1,112,903,500 | 5,830 | liulinboyi | ### This will be fine.
### [Example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBsYW5nPVwidHNcIj5cblxuPC9zY3JpcHQ+XG5cbjxzY3JpcHQgc2V0dXAgbGFuZz1cInRzXCI+XG5pbnRlcmZhY2UgUHJvcHMge1xuICAvLyB6b29tP1xuICBhPzogc3RyaW5nO1xufVxuY29uc3QgcHJvcHMgPSB3aXRoRGVmYXVsdHMoZGVmaW5lUHJvcHM8UHJvcHM+KCksIHtcbiAgYTogXCJhXCIsXG59KTt... | 2022-04-29T06:00:53 | 2022-04-29T06:00:53 | {} | MEMBER |
vuejs | core | 1,110,040,769 | 2,116 | slavicd | Well, this is disappointing. I lost a few hours because, contrary to what the docs say, and contrary to all the logic, array.push() is "reactive" in the sense that my views are changed, yet I can't watch it as I always could. This is broken behaviour. | 2022-04-26T17:03:56 | 2022-04-26T17:03:56 | {
"+1": 1
} | NONE |
vuejs | core | 1,110,821,816 | 5,813 | w582745483 | I don't think you understand me
`1:<template #default>
<div v-if="false"/>
</template>
`
`2:<template #name>
<div v-if="false"/>
</template>
`
Both of the above：the first one slot.default is not null,the second slot.name is null
I just want to know why the vnode work on defaut slot,but not work ... | 2022-04-27T10:11:41 | 2022-04-27T10:11:41 | {} | NONE |
vuejs | core | 1,112,208,233 | 5,825 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a41c011eca39966cf5ba9ad8b9c71f6cd75af639 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-04-28T13:31:38 | 2022-04-28T13:32:21 | {} | NONE |
vuejs | core | 1,111,773,060 | 5,821 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c31788b208b6317dddece7539d1172d7ac06edcd |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-28T05:47:54 | 2022-04-29T03:11:40 | {} | NONE |
vuejs | core | 1,113,128,437 | 5,766 | DrJume | I have updated my issue/feature proposal for better clarity.
Is there anything else I can help you with, so that this issue can be triaged? 🙂 | 2022-04-29T09:56:39 | 2022-04-29T09:56:39 | {} | CONTRIBUTOR |
vuejs | core | 1,149,828,748 | 6,058 | donatas-luciunas | Dear Evan,
Let's begin with the fact that this issue is not about me, it is about improvement idea.
The recurring problem I notice is that you and @LinusBorg put too little effort to grasp the idea (good indicators are your mistakes for example "return value of IndexedDB.get can never be a reactive dependency") a... | 2022-06-08T12:06:47 | 2022-06-08T12:18:49 | {} | NONE |
vuejs | core | 1,150,568,426 | 5,657 | ff77645 | This problem always occurs in pages that use keep-alive. | 2022-06-09T01:15:57 | 2022-06-09T01:15:57 | {} | NONE |
vuejs | core | 1,151,317,811 | 6,084 | Justineo | It’s expected as Vue doesn’t support fully controlled native inputs. There’s already an RFC about this [here](https://github.com/vuejs/rfcs/pull/188). | 2022-06-09T15:57:10 | 2022-06-09T15:57:10 | {} | MEMBER |
vuejs | core | 1,152,562,613 | 6,071 | liulinboyi | Please provide a minimal reproduction, thanks! | 2022-06-10T17:03:01 | 2022-06-10T17:03:01 | {} | MEMBER |
vuejs | core | 1,152,925,868 | 6,086 | LinusBorg | I agree that this specific scenario is an easy pitfall to introduce a bug.
However it's documented behavior that we could only change in a major release, as far as I can see right now. Though I'd be interested in suggestions
For now, what we can do is to better document this pitfall in the docs about `<component... | 2022-06-11T13:10:52 | 2022-06-11T13:10:52 | {} | MEMBER |
vuejs | core | 1,153,557,863 | 3,562 | Rainer-Yu | > @whylost wrap your state class instance in a shallowRef: https://vuejs.org/guide/extras/reactivity-in-depth.html#integration-with-external-state-systems
thanks | 2022-06-13T07:13:28 | 2022-06-13T07:13:28 | {} | NONE |
vuejs | core | 1,149,415,893 | 6,067 | yyx990803 | This is not a concern for Vue core. Check out https://vueuse.org/core/userefhistory/ for something relevant. | 2022-06-08T03:29:08 | 2022-06-08T03:29:08 | {} | MEMBER |
vuejs | core | 1,149,608,441 | 6,058 | yyx990803 | > ...where parameter `value` is a unique function for every caller. Do you agree this could work?
No, because async dependency collection creates race conditions where each re-run of the async effect could produce different set of dependencies to be tracked. This is much more complicated than it may seem.
> As I ... | 2022-06-08T08:18:25 | 2022-06-08T08:20:46 | {} | MEMBER |
vuejs | core | 1,150,542,313 | 4,339 | hezhongfeng | Need this feature. | 2022-06-09T00:25:33 | 2022-06-09T00:25:33 | {} | NONE |
vuejs | core | 1,151,364,032 | 6,026 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 77f5d447f3baf6dbc781e022435ca50e5d476d5c |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-06-09T16:45:55 | 2022-06-09T16:45:55 | {} | NONE |
vuejs | core | 1,152,684,359 | 5,184 | kenrowland | FYI, I was able to clear this error by ensuring that my Vue components all at least have an empty emits member:
```
export default {
...
emits: [],
...
}
``` | 2022-06-10T19:54:43 | 2022-06-10T19:55:05 | {} | NONE |
vuejs | core | 1,151,099,213 | 4,294 | EgorPopovPP | @lzr900515
😉
https://github.com/vuejs/core/issues/4294#issuecomment-1128852150 | 2022-06-09T13:09:18 | 2022-06-09T13:09:18 | {
"+1": 9
} | NONE |
vuejs | core | 1,151,175,979 | 6,080 | bbcvc | This look like 'Transition Modes' problem. | 2022-06-09T14:14:44 | 2022-06-09T14:14:44 | {} | NONE |
vuejs | core | 1,152,065,022 | 6,086 | lidlanca | ### options 1
`defineEmit` on the "immediate" component (`Comp`). so vue does not attach a native event listener.
### options 2
guard native event in the consumer level, (in case you don't have control over Comp)
```js
function onChange(event) {
if(event instanceof Event ) return
title.value = e.target... | 2022-06-10T07:35:55 | 2022-06-10T07:35:55 | {} | CONTRIBUTOR |
vuejs | core | 1,152,246,198 | 2,855 | ThaDaVos | > I just came across this when doing watch with webpack. Maybe it helps somebody or is related to this.
>
> I get the error when I have my `<template>` like this:
>
> ```
> <template>
> <div>
> <Teleport to="body">
> <transition name="fade">
> <div>...</div>
> </transition>
> ... | 2022-06-10T11:07:20 | 2022-06-10T11:07:20 | {} | NONE |
vuejs | core | 1,152,852,632 | 6,086 | Linkontoask | Thank you for your replies. @lidlanca @KaelWD
I'm here to talk about an application scenario
``` jsx
<component :is="hit" @change="onChange" />
const hit = Comp1 || Comp2 || Comp3
```
It may be that `Comp2` does not need to respond to this event, but it happens that there are elements in `Comp2` that do ... | 2022-06-11T04:25:42 | 2022-06-11T04:26:25 | {} | NONE |
vuejs | core | 1,152,861,541 | 5,184 | soylomass | A maybe useful tip for anyone who is experiencing this error or the "**insertBefore**" one, I just solved one by using the "Break at catched exceptions" options in Chrome's DevTool.
Vue happens to catch and hide some template exceptions, so they won't show on console.
In this particular case, my template (at some... | 2022-06-11T05:40:18 | 2022-06-11T05:53:49 | {} | NONE |
vuejs | core | 1,152,922,874 | 5,184 | posva | Read and follow the links at https://github.com/vuejs/core/issues/5184#issuecomment-1002947715
A proper repro is required | 2022-06-11T12:53:23 | 2022-06-11T12:53:23 | {} | MEMBER |
vuejs | core | 1,152,923,903 | 5,415 | twelve17 | @LinusBorg @lidlanca - I came across this issue by way of https://github.com/vuejs/apollo/issues/1350 . Looks like something in the fix in https://github.com/vuejs/core/pull/5417 has still affected how the data is getting updated in vue apollo. I have an example app in a codesandbox in this issue: https://github.com/... | 2022-06-11T12:59:29 | 2022-06-11T12:59:29 | {} | NONE |
vuejs | core | 1,153,409,395 | 6,094 | yyx990803 | Thanks, but we do not accept stylistic changes without objective improvements. | 2022-06-13T03:01:33 | 2022-06-13T03:01:33 | {} | MEMBER |
vuejs | core | 1,155,036,437 | 4,294 | tewshi | I just observed this does not work, it only takes away the error, and the props don't get passed down using `withDefaults` | 2022-06-14T11:04:15 | 2022-06-14T11:04:15 | {
"eyes": 2
} | NONE |
vuejs | core | 1,155,161,484 | 6,111 | leopiccionia | It can be solved in userland with a computed property and a deep-merging function (e.g. [defu](https://www.npmjs.com/package/defu)). | 2022-06-14T13:07:01 | 2022-06-14T13:07:01 | {} | CONTRIBUTOR |
vuejs | core | 1,151,071,728 | 6,082 | liulinboyi | 希望提供一个最小的复现。 | 2022-06-09T12:42:14 | 2022-06-09T12:42:14 | {} | MEMBER |
vuejs | core | 1,152,817,511 | 6,071 | Justineo | This a far beyond minimal. See https://github.com/vuejs/core/blob/main/.github/bug-repro-guidelines.md#a-repro-should-be-minimal. Remove all unnecessary components and dependencies please. | 2022-06-11T00:38:41 | 2022-06-11T00:38:41 | {} | MEMBER |
vuejs | core | 1,152,923,175 | 6,098 | LinusBorg | Either:
https://vuejs.org/guide/components/events.html#declaring-emitted-events
Or:
https://vuejs.org/api/options-misc.html#inheritattrs
| 2022-06-11T12:55:13 | 2022-06-11T12:55:13 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,152,953,493 | 6,092 | zer0fire | Demo url: [Vue SFC Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgaXNTZWxlY3QgPSByZWYodHJ1ZSlcbmZ1bmN0aW9uIHRvZ2dsZSgpe1xuICBpc1NlbGVjdC52YWx1ZSA9ICFpc1NlbGVjdC52YWx1ZVxufVxuPC9zY3JpcHQ+XG5cbjx0ZW1wbGF0ZT5cbiAgPGgxIEBjbGljaz1cInRvZ2dsZVwiIDpjbGFzcz... | 2022-06-11T15:44:51 | 2022-06-11T15:44:51 | {} | NONE |
vuejs | core | 1,153,406,594 | 6,086 | yyx990803 | In Vue 2, custom vs. native event listeners are separated via the `.native` modifier.
In Vue 3:
1. Listeners will capture both custom and native listeners if no `emits` or `defineEmits` are explicitly declared
2. A listener will only capture custom events if it's declared as custom only via `emits`
Given that... | 2022-06-13T02:54:20 | 2022-06-13T02:54:20 | {} | MEMBER |
vuejs | core | 1,155,256,514 | 5,873 | ByePastHub | You need to bind v-model to the input, and the input value can be retained after switching | 2022-06-14T14:19:03 | 2022-06-14T14:19:03 | {} | NONE |
vuejs | core | 1,149,611,392 | 5,242 | Xing-He | @mythshuazi Element使用的组件有些存在是否选用teleport的参数，这个可以试试，我的处理比较粗暴些，因为一般使用了teleport的组件都是些input select啥的，SEO的时候其实也不需要获取这些节点数据，因此就采用了页面加载完成后再渲染出来，直接`v-if="mounted"` | 2022-06-08T08:21:30 | 2022-06-08T08:21:30 | {} | NONE |
vuejs | core | 1,151,855,375 | 6,082 | ArmedBone | > 这个链接要求访问者登录 Gitee 账号，请看一下能否在我们的 [SFC Playground](https://sfc.vuejs.org/) 上复现吧。
这个网页无法在chrome49的浏览器打开
| 2022-06-10T02:33:29 | 2022-06-10T02:33:29 | {} | NONE |
vuejs | core | 1,153,404,006 | 3,562 | yyx990803 | @whylost wrap your state class instance in a shallowRef: https://vuejs.org/guide/extras/reactivity-in-depth.html#integration-with-external-state-systems | 2022-06-13T02:47:54 | 2022-06-13T02:47:54 | {} | MEMBER |
vuejs | core | 1,153,534,089 | 6,072 | stewarthaines | Thanks! | 2022-06-13T06:43:48 | 2022-06-13T06:43:48 | {} | CONTRIBUTOR |
vuejs | core | 1,154,735,113 | 3,652 | willjayyyy | you can try to add attribute `incluce` to `<keep-alive></keep-alive>` to resolve | 2022-06-14T05:34:57 | 2022-06-14T05:35:44 | {} | NONE |
vuejs | core | 1,151,253,830 | 5,242 | mythshuazi | > @mythshuazi Element使用的组件有些存在是否选用teleport的参数，这个可以试试，我的处理比较粗暴些，因为一般使用了teleport的组件都是些input select啥的，SEO的时候其实也不需要获取这些节点数据，因此就采用了页面加载完成后再渲染出来，直接`v-if="mounted"`
@Xing-He 我的处理方法和你差不多，但是这个repo [vue3-ts-vite-ssr-starter](https://github.com/vok123/vue3-ts-vite-ssr-starter)搭的ssr 没有 mismatch的问题，我一直没看找到原因，一起看看？ | 2022-06-09T15:13:47 | 2022-06-09T15:13:47 | {} | NONE |
vuejs | core | 1,151,967,626 | 6,085 | liulinboyi | This is expected behavior.
[Docs](https://staging-cn.vuejs.org/guide/essentials/class-and-style.html#binding-html-classes) | 2022-06-10T05:42:17 | 2022-06-10T05:42:17 | {} | MEMBER |
vuejs | core | 1,152,566,897 | 5,993 | liulinboyi | 希望提供一个最小的复现。 | 2022-06-10T17:06:44 | 2022-06-10T17:06:44 | {} | MEMBER |
vuejs | core | 1,153,850,391 | 5,996 | livthomas | @qmhc I'm using the following script as a workaround:
```js
import {readFileSync, writeFileSync} from 'fs';
import path from 'path';
const filePath = path.resolve('./node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js');
const content = readFileSync(filePath, 'utf8');
const modifiedContent = conte... | 2022-06-13T12:24:56 | 2022-06-13T12:24:56 | {
"+1": 1
} | NONE |
vuejs | core | 1,154,863,547 | 5,847 | ig1na | Even when using withDefaults setting the prop to undefined, the type becomes `Ref<boolean>` but should be `Ref<boolean | undefined>`
Is there any workaround to use watchers on props without using toRefs ? | 2022-06-14T08:15:17 | 2022-06-14T08:40:15 | {} | NONE |
vuejs | core | 1,155,034,472 | 6,111 | xi2And33 | 
that is what i want ,i want to merge real value and default value , even if real value lack of some property | 2022-06-14T11:02:13 | 2022-06-14T11:02:13 | {} | NONE |
vuejs | core | 1,155,063,370 | 6,082 | ArmedBone | > Vue 3 不支持 Chrome 49.
vue2.x和react都没有出现过这个bug；vue3打了@vitejs/plugin-legacy可以兼容到chrome49; 谢谢偶像~^^ | 2022-06-14T11:33:01 | 2022-06-14T11:33:01 | {} | NONE |
vuejs | core | 1,151,219,938 | 6,081 | benjaminrobinet | @bbcvc Isn't the minimal reproduction enough to guess ?
I guess the problem is I'm using a ref as element key. But I don't know why it's not working when wrapping the <Transition/> component. | 2022-06-09T14:49:41 | 2022-06-09T14:49:41 | {} | NONE |
vuejs | core | 1,151,845,172 | 6,082 | ArmedBone | > 既然所有事件都可以复现的话就把无关的东西都删了，提供一个最小复现吧，谢谢。
https://gitee.com/come-out-and-fight-alone/my-vue3-study.git 随便绑定一个点击事件 在xp系统上延迟4秒注册 | 2022-06-10T02:18:28 | 2022-06-10T02:18:28 | {} | NONE |
vuejs | core | 1,153,365,591 | 3,562 | Rainer-Yu | Will there be an API for forceUpdate()?
I imported a class `instance` (using getter/setter and Proxy but can't use vue's reactive system to wrap it) in vue3 component and need to trigger update manually | 2022-06-13T01:34:36 | 2022-06-13T01:34:36 | {} | NONE |
vuejs | core | 1,154,640,416 | 6,103 | inkn | > Can't look at the repro right now, but I suspect you are missing `resolveComponent()`:
>
> ```js
> h(resolveComponent('component-name'))
> ```
thanks for youer reply ,i use resolveComponent in example，but it stiil not work, Why does this happen?
the example site:
https://stackblitz.com/edit/vitejs-vite-46el... | 2022-06-14T02:29:31 | 2022-06-14T02:29:31 | {} | NONE |
vuejs | core | 1,154,734,132 | 5,993 | willjayyyy | 尝试在keepalive中加入include解决问题 | 2022-06-14T05:33:31 | 2022-06-14T05:33:31 | {} | NONE |
vuejs | core | 1,150,921,710 | 5,657 | ff77645 | > > This problem always occurs in pages that use keep-alive.
>
> Could you provide a minimal repro?
No,doesn't always appear, and only appears in production environment. | 2022-06-09T09:58:03 | 2022-06-09T09:58:03 | {
"+1": 10
} | NONE |
vuejs | core | 1,151,763,045 | 6,082 | ArmedBone | > 希望提供一个最小的复现。
xp系统上所有的点击事件都会被延迟4秒注册。只有xp才会有这个状况
| 2022-06-10T00:53:49 | 2022-06-10T00:53:49 | {} | NONE |
vuejs | core | 1,152,821,418 | 6,071 | LoveofRedMoon | > Is all the code you provided necessary to reproduce the problem? Will the problem disappear if you remove any part of it?
Thanks, I will fix this manually myself. This issue is already closed. | 2022-06-11T00:55:44 | 2022-06-11T00:55:44 | {} | NONE |
vuejs | core | 1,153,637,733 | 6,086 | lidlanca | > I'm not quite sure how Vue can change its behavior to avoid this without causing breaking changes.
we can introduce modifiers to vue 3 (prefix).
The modifier can configure the type of binding ( native / emit ).
additionally we can also introduce case sensitive modifier, that can solve
https://github.... | 2022-06-13T08:36:50 | 2022-06-13T08:36:50 | {} | CONTRIBUTOR |
vuejs | core | 1,155,060,793 | 6,082 | ArmedBone | > Vue 3 不支持 Chrome 49.
我这边目前排查这个bug可能和浏览器无关。因为网页时运行在.net内的，我这边的.net开发人员不知道设置了什么，现在没有再出现这个延迟事件注册的现象。 | 2022-06-14T11:30:21 | 2022-06-14T11:30:21 | {} | NONE |
vuejs | core | 1,149,522,260 | 6,072 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 4b0b7b3594041f595cc1364d776edb8b7d4a398f |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-06-08T06:38:01 | 2022-06-08T06:38:01 | {} | NONE |
vuejs | core | 1,151,826,450 | 6,082 | Justineo | 既然所有事件都可以复现的话就把无关的东西都删了，提供一个最小复现吧，谢谢。 | 2022-06-10T01:53:28 | 2022-06-10T01:53:28 | {} | MEMBER |
vuejs | core | 1,152,397,836 | 6,086 | KaelWD | https://vuejs.org/guide/components/attrs.html#disabling-attribute-inheritance | 2022-06-10T14:04:07 | 2022-06-10T14:04:07 | {} | CONTRIBUTOR |
vuejs | core | 1,152,821,022 | 6,071 | LoveofRedMoon | > Is all the code you provided necessary to reproduce the problem? Will the problem disappear if you remove any part of it?
This is a production project and I have removed most of the business code. | 2022-06-11T00:53:50 | 2022-06-11T00:53:50 | {} | NONE |
vuejs | core | 1,152,926,165 | 5,415 | LinusBorg | Please open a new issue here with that reproduction (provided it's minimal, can't check it out tight now on mobile) and all additional information you can provide. | 2022-06-11T13:13:01 | 2022-06-11T13:13:01 | {} | MEMBER |
vuejs | core | 1,153,408,589 | 6,074 | yyx990803 | This is unnecessary. esbuild is more than fast enough even with sourcemaps. | 2022-06-13T02:59:32 | 2022-06-13T02:59:32 | {} | MEMBER |
vuejs | core | 1,155,204,594 | 6,112 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 9b2fe700a786d3b2543a93be8913cb782f2d2d67 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-06-14T13:42:22 | 2022-06-14T13:42:22 | {} | NONE |
vuejs | core | 1,149,689,758 | 4,339 | dreambo8563 | we really need the feature, more and more apps with multi tabs pop up | 2022-06-08T09:35:39 | 2022-06-08T09:35:50 | {} | NONE |
vuejs | core | 1,152,398,398 | 6,086 | Linkontoask | The first sense is that the custom event is only applied to the current component and not triggered by the grandchild component due to the failure to declare `defineEmit`
```
<Comp @change="onChange" />
```
The change event should only be triggered by `Comp` `emit('change')`
This doesn't match the first intu... | 2022-06-10T14:04:41 | 2022-06-10T14:06:26 | {} | NONE |
vuejs | core | 1,152,760,672 | 6,086 | lidlanca | I jumped to the workarounds to save you some time,
you can check the docs to better understand what is expected from vue when you bind events to a component with a defined emit and without,
and what is the difference between native event, and vue emitted "events".
if you are trying to push a new feature or cha... | 2022-06-10T21:49:41 | 2022-06-10T21:49:41 | {} | CONTRIBUTOR |
vuejs | core | 1,153,918,812 | 3,214 | lucaswerkmeister | > https://v3.vuejs.org/guide/migration/events-api.html#overview
That link broke; here’s a working one: https://v3-migration.vuejs.org/breaking-changes/events-api.html | 2022-06-13T13:31:02 | 2022-06-13T13:31:02 | {} | CONTRIBUTOR |
vuejs | core | 1,149,514,524 | 6,058 | donatas-luciunas | @yyx990803
> This is a fundamental limitation of how Vue's reactivity system works, unless JavaScript provides a mechanism to capture function execution context across async ticks.
I agree that it is not possible with the API I described, but you could change the API
```
const getDependency = (key) => ...
c... | 2022-06-08T06:27:29 | 2022-06-08T06:27:29 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.