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 | 2,078,521,856 | 5,540 | zzw105 | I cannot obtain exposed in `$`, but I obtained exposed in ` _instance `
```javascript
myComponent.value._instance.exposed.xxx()
```
vue2 and vue3 can be obtained through `_instance` | 2024-04-26T02:27:58 | 2024-04-26T02:27:58 | {} | NONE |
vuejs | core | 2,078,793,487 | 10,806 | quiteeasy | The issue goes deeper than the `onActivated` lifecycle hook not being triggered in async context. The `onActivated` is not called on all descendant components mounted after a v-if change. I've prepared a [demo](https://play.vuejs.org/#eNqVU01vnDAQ/SuWL7uRttB0e0rZlbZVDm2ltmp7tFQhGIhTsC3bkJUQ/z0zeGHJF0pueN7M482bmY4fjInaB... | 2024-04-26T07:27:27 | 2024-04-26T07:30:17 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 2,073,995,228 | 10,774 | jevin98 | > vue object is used Proxy wrapped,xx.hasOwnProperty can emit proxy interception
Do you understand what my problem is? | 2024-04-24T04:19:12 | 2024-04-24T04:19:12 | {} | NONE |
vuejs | core | 2,074,365,037 | 10,774 | Disservin | > > Proxy
> > Thanks, However, in 3.4.24, there is no answer to the question why the function of the object on the prototype of slots disappeared.
A quick google search would answer this. https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/hasOwn#problematic_cases_for_hasownprope... | 2024-04-24T08:19:38 | 2024-04-24T08:19:38 | {} | CONTRIBUTOR |
vuejs | core | 2,076,262,640 | 10,790 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | -------------------- | -------------------- |
| runtime-dom.global.prod.js | 91 kB (**+311 B**) | 34.6 kB (**+103 B**) | 31.2 kB (**+104 B... | 2024-04-25T02:58:21 | 2024-04-25T02:58:21 | {} | NONE |
vuejs | core | 2,060,536,111 | 3,399 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8717685257)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8716544786) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/871... | 2024-04-17T07:10:11 | 2024-04-25T07:32:17 | {} | CONTRIBUTOR |
vuejs | core | 2,076,681,288 | 10,794 | edison1105 | related to https://github.com/vuejs/core/commit/6df53d85a207986128159d88565e6e7045db2add
| 2024-04-25T08:46:58 | 2024-04-25T08:46:58 | {} | MEMBER |
vuejs | core | 2,077,347,557 | 10,799 | LarsEQtiming | Similar example as whats in the reproduction link:
```vue
<template>Example</template>
<script setup lang="ts">
import { type Ref, ref } from 'vue';
interface DefAsInterface {
field: Ref<string>;
}
const initalizedAsEmpty = ref<DefAsInterface | undefined>();
initalizedAsEmpty.value = {
field: ref(... | 2024-04-25T14:30:05 | 2024-04-25T14:30:05 | {} | NONE |
vuejs | core | 2,078,735,623 | 10,784 | quiteeasy | As an alternative option, we could expose other values to the template, similar to how we expose values using the `ref()` function when using string refs in templates. However, we need to decide on a consistent approach. Should we stick to using string refs and leverage the existing `ref()` mechanism, or should we forb... | 2024-04-26T06:47:08 | 2024-04-26T06:47:08 | {} | CONTRIBUTOR |
vuejs | core | 2,074,007,743 | 10,774 | jacekkarczmarczyk | > ## What is expected?
>
> slots.hasOwnProperty No error reported


There's no error | 2024-04-24T04:32:32 | 2024-04-24T04:32:32 | {} | CONTRIBUTOR |
vuejs | core | 2,074,080,635 | 10,771 | rex-ll | +1 | 2024-04-24T05:41:45 | 2024-04-24T05:41:45 | {
"confused": 1,
"eyes": 1
} | NONE |
vuejs | core | 2,074,394,215 | 6,819 | skirtles-code | There's an RFC discussion at <https://github.com/vuejs/rfcs/discussions/587> that proposes a slightly different way of approaching this. I'm not sure which I prefer.
---
Just to clarify, a single event can have multiple listeners. In the Playground below, the emitted event triggers 3 handlers. `mergeProps` ensure... | 2024-04-24T08:33:08 | 2024-04-24T08:33:08 | {} | CONTRIBUTOR |
vuejs | core | 2,076,271,738 | 6,882 | alexzhang1030 | 
没看到有报错了现在 | 2024-04-25T03:11:25 | 2024-04-25T03:11:25 | {} | MEMBER |
vuejs | core | 2,077,083,806 | 10,796 | Disservin | https://github.com/vuejs/core/issues/10768 | 2024-04-25T12:38:20 | 2024-04-25T12:38:20 | {} | CONTRIBUTOR |
vuejs | core | 2,078,812,996 | 10,806 | DragonnZhang | > The issue goes deeper than the `onActivated` lifecycle hook not being triggered in async context. The `onActivated` is not called on all descendant components mounted after a v-if change. I've prepared a [demo](https://play.vuejs.org/#eNqVU01vnDAQ/SuWL7uRttB0e0rZlbZVDm2ltmp7tFQhGIhTsC3bkJUQ/z0zeGHJF0pueN7M482bmY4fjIn... | 2024-04-26T07:40:33 | 2024-04-26T07:40:33 | {} | NONE |
vuejs | core | 2,079,042,338 | 10,809 | ferferga | Tested in my app and with the same playground code I added to #4091 and it works flawlessly, thank you very much! | 2024-04-26T09:54:32 | 2024-04-26T09:54:32 | {} | CONTRIBUTOR |
vuejs | core | 2,074,350,426 | 10,771 | edison1105 | @Disservin Thanks.
I've reproduced the problem

related commit https://github.com/vuejs/core/commit/e51ca61ca060b2772e967d169548fc2f58fce6d1 | 2024-04-24T08:14:05 | 2024-04-24T08:14:05 | {} | MEMBER |
vuejs | core | 2,074,383,289 | 10,774 | jevin98 | > `hasOwnProperty`
Sorry, hasOwnProperty can still be used normally in this place in 3.4.23. So I'm not sure if there is a problem after upgrading to 3.4.24. | 2024-04-24T08:27:43 | 2024-04-24T08:27:43 | {} | NONE |
vuejs | core | 1,822,805,709 | 3,399 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/6958117394)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/6953069069) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/695... | 2023-11-22T13:47:31 | 2024-04-25T07:32:33 | {} | CONTRIBUTOR |
vuejs | core | 2,077,616,158 | 10,790 | yyx990803 | I don't think we should do this, for the reasons @edison1105 has provided. Thanks for the PR though! | 2024-04-25T15:48:09 | 2024-04-25T15:48:09 | {} | MEMBER |
vuejs | core | 2,078,673,105 | 10,806 | skirtles-code | Seems similar to #7276, though not exactly the same. It might be the same underlying cause.
That other issue has a PR at #7286, but that seems to be only handling cases involving `defineAsyncComponent`, so it doesn't fix the issue reported here. | 2024-04-26T05:43:50 | 2024-04-26T05:43:50 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 2,073,919,875 | 4,339 | cons2act | unplanned? | 2024-04-24T03:01:54 | 2024-04-24T03:01:54 | {} | NONE |
vuejs | core | 2,074,368,448 | 10,772 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8813280527)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8811254125) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/881... | 2024-04-24T08:20:23 | 2024-04-24T08:20:23 | {} | CONTRIBUTOR |
vuejs | core | 2,074,465,175 | 9,270 | andreww2012 | Even more minimal reproduction not involving `<router-view>` with a similar error thrown (which is still occurring inside `unmountComponent`) when the teleport target does not exist: https://stackblitz.com/edit/vitejs-vite-s1bxpv
1. Open the console. Observe a pretty normal warning saying "Failed to locate Teleport ... | 2024-04-24T09:07:58 | 2024-04-24T09:07:58 | {
"+1": 1
} | NONE |
vuejs | core | 2,074,483,390 | 10,771 | LebronLei | 这是 3.4.24这个版本的bug,导致只在生产环境出问题。修改使用的vue到历史版本,重新构建项目可以避免这问题。 | 2024-04-24T09:16:05 | 2024-04-24T09:16:05 | {
"+1": 2
} | NONE |
vuejs | core | 2,075,176,656 | 10,786 | skirtles-code | I believe this Playground shows a reproduction of the error:
- [Playground](https://play.vuejs.org/#__SSR__eNp9kU9rAjEQxb/KkMsqWEXa07IKtXhooX9oe8zF7o4am82EZGIty373JrtoLRRPSd77TeYN04hba8f7gCIXhS+dsgweOdi5NKq25BgaILPANTl8pGAYWlg7qiGLRZk00mhk+FCmghk0bRL+4IPBEGZzaKSBEwWevzXmkJWkyeXgsMoglrZDaYpJnyL2jw/G2uoVY3wBFNsp7K/SJz... | 2024-04-24T15:08:27 | 2024-04-24T15:08:27 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 2,076,215,940 | 10,501 | yyx990803 | Good catch. I made some small adjustments to make the head logic dev-only. | 2024-04-25T02:29:26 | 2024-04-25T02:29:26 | {
"rocket": 1
} | MEMBER |
vuejs | core | 2,077,610,932 | 10,794 | yyx990803 | Why are you relying on this check? Lodash's `isPlainObject` basically checks for objects that are created via object literals or with `null` prototypes, I can't really think of a reason why you'd want to check that on `attrs`. | 2024-04-25T15:45:23 | 2024-04-25T15:45:46 | {} | MEMBER |
vuejs | core | 2,078,707,445 | 10,807 | Alfred-Skyblue | ```ts
const b = ref(2)
function render() {
return h(Child, {
propA: { hh: 123, d: 'getB()' },
propB: b.value
})
}
render()
setTimeout(() => {
b.value = 3
}, 1000)
```
After the template is compiled into a render function, calling the render function creates virtual nodes. Since b.valu... | 2024-04-26T06:21:18 | 2024-04-26T06:21:18 | {} | MEMBER |
vuejs | core | 2,079,036,294 | 10,806 | DragonnZhang | I found an easier method to trigger `onActivated`. Instead of using `v-show`, just wrap the component with another `<KeepAlive>`, like [this](https://play.vuejs.org/#eNqVVFGPlEAM/ivjvOxesoDn+nSym6zmHtREjfpIYggUdk6YITMDuwnhv9sywCKnRN9ov7Z8/Tpty09V5Tc18AcemkSLyjIDtq6OkRRlpbRl71RZ3bNMq5Jt/KC3KGHzJpJh4FIwGA0LZVXEFtBiLPwIUJ... | 2024-04-26T09:50:45 | 2024-04-26T09:50:45 | {
"+1": 1
} | NONE |
vuejs | core | 2,074,348,247 | 10,772 | haoqunjiang | /ecosystem-ci run | 2024-04-24T08:12:59 | 2024-04-24T08:12:59 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,074,689,761 | 10,655 | quiteeasy | PR to add a warning for this case #10784 | 2024-04-24T11:07:12 | 2024-04-24T11:07:12 | {
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 2,074,689,879 | 10,784 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-04-24T11:07:16 | 2024-04-24T11:07:16 | {} | NONE |
vuejs | core | 2,074,698,010 | 10,774 | jevin98 | > Ah I think Evan might have just “fixed“ this [064e82f](https://github.com/vuejs/core/commit/064e82f5855f30fe0b77fe9b5e4dd22700fd634d) but still use hasOwn
Yes. If I had used hasOwn from the beginning there would be no problem. | 2024-04-24T11:12:26 | 2024-04-24T11:13:19 | {} | NONE |
vuejs | core | 2,076,348,568 | 10,790 | alexzhang1030 | > I think we shouldn't change the original behavior of stepDown or stepUp.
>
> - This is not in line with HTML specifications.
>
> - It's possible that users have already used stepUp to avoid triggering the input event. If we change the original behavior of stepUp, it might be a breaking change.
Agree with that 👍 | 2024-04-25T04:46:08 | 2024-04-25T04:46:08 | {} | MEMBER |
vuejs | core | 2,076,798,114 | 10,796 | baiwusanyu-c | I think this is a problem with your network. In some cases, cdn or dns resolution failure will cause this situation.

| 2024-04-25T09:50:44 | 2024-04-25T09:50:44 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,076,946,930 | 10,793 | SeppiHDamgaard | UPDATE: It the Console Ninja extension in VS Code that produced the error, whenever I wrote a console.log. | 2024-04-25T11:17:49 | 2024-04-25T11:17:49 | {} | NONE |
vuejs | core | 2,029,272,278 | 10,631 | q479902964 | I have another question. It's strange, I can solve this problem by making a shallow copy when passing the object parameter, but I don't know the reason and i don't think this is a reasonable solution.

| 2024-04-01T06:58:26 | 2024-04-01T06:58:26 | {} | NONE |
vuejs | core | 2,029,439,807 | 10,632 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8506070329)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8504038368) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-04-01T09:00:43 | 2024-04-01T09:00:43 | {} | CONTRIBUTOR |
vuejs | core | 2,029,765,319 | 5,362 | haoqunjiang | Thanks for the PR! Sorry that we didn't notice this one earlier.
Now we've merged https://github.com/vuejs/core/pull/10373 and this issue has been fixed since v3.4.20. | 2024-04-01T13:32:14 | 2024-04-01T13:32:14 | {} | MEMBER |
vuejs | core | 2,029,891,295 | 8,641 | haoqunjiang | Thanks for the PR. The mentioned issue has been fixed by https://github.com/vuejs/core/pull/9309 and was shipped in 3.3.10.
So I'm closing this PR. | 2024-04-01T14:56:24 | 2024-04-01T14:56:24 | {} | MEMBER |
vuejs | core | 2,029,915,035 | 10,606 | haoqunjiang | Closing due to lack of response. | 2024-04-01T15:09:32 | 2024-04-01T15:09:32 | {} | MEMBER |
vuejs | core | 2,031,360,233 | 10,638 | edison1105 | /ecosystem-ci run | 2024-04-02T08:16:15 | 2024-04-02T08:16:15 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,033,405,597 | 10,578 | shaobeichen | > > ```
> > <input
> > :value="text"
> > @input="event => text = event.target.value">
> > ```
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > v-model 也是语法糖,那和上面代码一样,初始化text时,input是不会触发的,在设计响应式时其实就遵循了这一点,只有当值改变时,才会有相应操作。
> > 
>
> //构造函数
> constructor() {
> this.name = 'test'
> }
>
> public initH... | 2024-04-03T08:57:32 | 2024-04-03T08:57:32 | {} | NONE |
vuejs | core | 2,041,027,377 | 10,651 | cernymatej | Didn't realize it was a problem with only `aria-` attributes. Linking https://github.com/vuejs/language-tools/issues/4219 then... 👍 | 2024-04-06T09:17:22 | 2024-04-06T09:17:22 | {} | CONTRIBUTOR |
vuejs | core | 2,041,470,110 | 10,652 | edison1105 | /ecosystem-ci run
| 2024-04-07T13:20:38 | 2024-04-07T13:20:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,041,742,640 | 10,658 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-04-08T02:12:44 | 2024-04-08T02:12:44 | {} | NONE |
vuejs | core | 2,029,076,736 | 10,627 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-04-01T03:02:40 | 2024-04-01T03:02:40 | {} | NONE |
vuejs | core | 2,029,431,946 | 10,632 | edison1105 | /ecosystem-ci run | 2024-04-01T08:53:55 | 2024-04-01T08:53:55 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,032,078,984 | 10,620 | wcldyx | > 第一个问题的复现是把 mode 和 include 都去掉吗?
>
> ```
> <Transition>
> <KeepAlive>
> <A v-if="show" />
> </KeepAlive>
> </Transition>
> ```
>
> .
#5195 was submitted by me two years ago. At that time, my understanding was incorrec... | 2024-04-07T12:24:09 | 2024-04-07T13:22:12 | {} | MEMBER |
vuejs | core | 2,042,222,176 | 10,637 | haoqunjiang | /ecosystem-ci run | 2024-04-08T08:58:36 | 2024-04-08T08:58:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,027,358,598 | 10,556 | haoqunjiang | Let's track this issue at https://github.com/vitejs/vite-plugin-vue/issues/374 | 2024-03-29T15:04:04 | 2024-03-29T15:04:04 | {} | MEMBER |
vuejs | core | 2,028,592,271 | 10,619 | LinusBorg | We don't debug projects. We debug issues with Vue that can be demonstrated in minimal reproductions.
I quickly ran your project, and all the errors I see popping up are errors from your own code.
I will convert this into a discussion topic so the community might be able to give you some help. | 2024-03-31T07:59:00 | 2024-03-31T07:59:00 | {} | MEMBER |
vuejs | core | 2,031,460,671 | 10,578 | zhengyanbin-yy | > ```
> <input
> :value="text"
> @input="event => text = event.target.value">
> ```
>
> v-model 也是语法糖,那和上面代码一样,初始化text时,input是不会触发的,在设计响应式时其实就遵循了这一点,只有当值改变时,才会有相应操作。
>
>  so I made up another (much simpler in my opinion) playground to better reproduce it, until I found this opened issue.
[Here's the link](https://play.vuejs.org/#__PROD__e... | 2024-04-04T17:10:41 | 2024-04-04T17:11:29 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 2,039,149,795 | 5,148 | edison1105 | @ferferga
I'll take a closer look at it later. | 2024-04-05T07:34:55 | 2024-04-05T07:34:55 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,041,532,641 | 10,655 | LinusBorg | The production behaviour is correct as the template ref gets a new array reassigned - and const variables are not re-assignable.
However we should look into how to warn about this in dev mode | 2024-04-07T17:07:11 | 2024-04-07T17:07:11 | {} | MEMBER |
vuejs | core | 2,028,018,171 | 10,615 | wangyewei | looks like same as #10503 | 2024-03-30T11:20:57 | 2024-03-30T11:20:57 | {} | CONTRIBUTOR |
vuejs | core | 2,029,269,696 | 10,620 | edison1105 | 第一个问题的复现是把 mode 和 include 都去掉吗?
```vue
<Transition>
<KeepAlive>
<A v-if="show" />
</KeepAlive>
</Transition>
```

把 mode 和 include 都去掉后,不停切换并不存在内存泄漏 | 2024-04-01T06:55:50 | 2024-04-01T08:59:58 | {} | MEMBER |
vuejs | core | 2,031,358,531 | 8,701 | hickiy | @shengxinjing 这个特性被合并了吗,我目前在实现基于缓存部分功能,对于共享一个组件的多个实例,无法精确控制,目前正在寻找方案 | 2024-04-02T08:15:15 | 2024-04-02T08:15:15 | {} | NONE |
vuejs | core | 2,033,636,991 | 10,630 | edison1105 | https://vuejs.org/api/sfc-script-setup.html#type-only-props-emit-declarations
> The latest version of Vue supports referencing imported and a limited set of complex types in the type parameter position. However, because the type to runtime conversion is still AST-based, some complex types that require actual type anal... | 2024-04-03T06:10:54 | 2024-04-03T06:10:54 | {} | MEMBER |
vuejs | core | 2,034,016,444 | 10,634 | edison1105 | @so1ve I don't have that permission. 😄 | 2024-04-03T09:19:45 | 2024-04-03T09:19:45 | {
"eyes": 1
} | MEMBER |
vuejs | core | 2,026,097,303 | 10,609 | baffalop | Update: I was mistaken about versions. My `^3.3.4` actually resolved to 3.4. When I pin both `vue` and `@vue/compat` to `~3.3.4` the issue goes away. This fits with https://github.com/vuejs/core/issues/10148 which reports the error as only present on 3.4, not 3.3. | 2024-03-28T20:54:34 | 2024-03-28T20:55:17 | {} | NONE |
vuejs | core | 2,029,754,420 | 5,435 | haoqunjiang | Thanks for the PR.
But we've migrated to Vitest. So I'm closing this one. | 2024-04-01T13:23:53 | 2024-04-01T13:23:53 | {} | MEMBER |
vuejs | core | 2,029,429,331 | 10,632 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 90.6 kB (**+2 B**) | 34.4 kB (**-2 B**) | 31.1 kB (**+42 B**) |
| vue.... | 2024-04-01T08:52:27 | 2024-04-03T01:16:42 | {} | NONE |
vuejs | core | 2,033,568,951 | 10,630 | halo-apps | > Please provide an actually **runnable** reproduction. I can't see the error from the provided link.
This problem must import any third Package which contains interface declaration, thus I can't supply a runable demo. Please Copy code to local to reproduction this. | 2024-04-03T05:35:54 | 2024-04-03T06:28:15 | {} | NONE |
vuejs | core | 2,040,885,967 | 5,148 | edison1105 | @ferferga
>You can reproduce this by checking how the data-v-* attributes are missing on Suspense's inner div.
I've made a [PR](https://github.com/vuejs/core/pull/10652) to fix this.
> Another interesting finding: [SFC link](https://play.vuejs.org/#__PROD__eNp9kj1PwzAQhv+KuYWlaQeYqoIEqAMMgGhGL1FyJC6ObfmcEKnKf8f... | 2024-04-06T02:13:13 | 2024-04-06T02:42:47 | {} | MEMBER |
vuejs | core | 2,041,472,166 | 10,652 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8589090597)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8565217622) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/858... | 2024-04-07T13:28:08 | 2024-04-07T13:28:08 | {} | CONTRIBUTOR |
vuejs | core | 2,041,919,608 | 10,630 | haoqunjiang | As there's no runnable reproduction, I'm closing this issue. There're already several other issues on complex types support, you can keep an eye on them:
https://github.com/vuejs/core/issues/10514
https://github.com/vuejs/core/issues/9877
https://github.com/vuejs/core/issues/8468 | 2024-04-08T05:55:44 | 2024-04-08T05:55:44 | {} | MEMBER |
vuejs | core | 2,028,618,663 | 10,588 | bambooGHT | > Hello!
>
> It seems to be the expected behavior of your codes, this part of the code `.list-leave-active { position: absolute; }`
>
> Causes the element to be positioned absolutely during transition, which means the element won't follow the usual flow of the document anymore. In this case, because u didn't spec... | 2024-03-31T09:42:37 | 2024-03-31T09:43:44 | {} | NONE |
vuejs | core | 2,031,358,650 | 10,638 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.6 kB (**+25 B**) | 34.4 kB (**+8 B**) | 31.1 kB (**+52 B**) |
... | 2024-04-02T08:15:20 | 2024-04-02T08:34:52 | {} | NONE |
vuejs | core | 2,034,056,134 | 10,517 | edison1105 | @chengazhen
please provide a minimal reproduction | 2024-04-03T09:36:54 | 2024-04-03T09:36:54 | {} | MEMBER |
vuejs | core | 2,036,566,698 | 10,643 | LinusBorg | This is a TS limitation - it allows for additional properties in certain situations.
TS types don't strictly enforce that *only* the defined properties are present on objects. It only enforces that *required* properties are present and that the types of defined properties do match. The fact that it does reject addi... | 2024-04-04T08:46:50 | 2024-04-04T10:32:16 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,042,237,965 | 10,637 | vue-bot | 📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8597347162)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8594783393) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-c... | 2024-04-08T09:05:38 | 2024-04-08T11:00:34 | {} | CONTRIBUTOR |
vuejs | core | 2,020,664,278 | 10,599 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-03-26T14:57:39 | 2024-03-29T11:48:01 | {} | NONE |
vuejs | core | 2,028,767,007 | 10,295 | kermanx | This issue is stoping the following workaround (related to https://github.com/vuejs/core/issues/5002) from working, because children's `created` is called before the parent's:
```ts
export function directiveProvide<T = unknown>(dir: DirectiveBinding<any>, key: InjectionKey<T> | string, value?: T) {
const instanc... | 2024-03-31T14:20:31 | 2024-03-31T14:20:31 | {} | CONTRIBUTOR |
vuejs | core | 2,029,729,634 | 9,225 | haoqunjiang | As said, please open an RFC discussion at https://github.com/vuejs/rfcs/discussions first. | 2024-04-01T13:05:34 | 2024-04-01T13:05:34 | {} | MEMBER |
vuejs | core | 2,029,781,576 | 7,612 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-04-01T13:43:55 | 2024-04-01T13:44:34 | {} | NONE |
vuejs | core | 2,034,010,632 | 10,634 | so1ve | Could you please transfer this issue to vuejs/language-tools? | 2024-04-03T09:16:52 | 2024-04-03T09:16:52 | {} | MEMBER |
vuejs | core | 2,041,305,658 | 10,654 | Justineo | Please provide a runnable reproduction. | 2024-04-07T04:25:52 | 2024-04-07T04:25:52 | {} | MEMBER |
vuejs | core | 1,813,956,020 | 9,603 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2023-11-16T08:00:49 | 2024-04-01T07:57:50 | {} | NONE |
vuejs | core | 2,033,550,561 | 10,578 | shaobeichen | > > > > ```
> > > > <input
> > > > :value="text"
> > > > @input="event => text = event.target.value">
> > > > ```
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > v-model 也是语法糖,那和上面代码一样,初始化text时,input是不会触发的,在设计响应... | 2024-04-03T05:20:46 | 2024-04-03T05:20:46 | {} | NONE |
vuejs | core | 2,036,312,067 | 10,510 | lmc3s3f0r | > I met this problem too after I upgraded the vue version of my project to v3.4.21( 3.4.15 still report the errors after tested ). Until I found this issue and downgraded to 3.4.14 and the recursive error report stoped.
FYI, it's just been fixed in vue3-openlayers 6.4.1 ;) | 2024-04-04T06:41:56 | 2024-04-04T06:41:56 | {} | NONE |
vuejs | core | 2,036,614,380 | 10,327 | index23 | @jpsc In which environment did you run this test? Did you consider to put test in pipeline? | 2024-04-04T09:09:37 | 2024-04-04T09:10:50 | {} | NONE |
vuejs | core | 2,026,495,051 | 10,607 | Shyam-Chen | ```ts
// Wrapper.vue
defineProps<{
show?: boolean;
}>();
``` | 2024-03-29T02:27:02 | 2024-03-29T02:27:02 | {} | CONTRIBUTOR |
vuejs | core | 2,028,565,438 | 10,619 | freddysae0 | Exactly the same issue😔 | 2024-03-31T05:45:07 | 2024-03-31T05:45:07 | {
"+1": 1,
"confused": 1,
"heart": 1
} | NONE |
vuejs | core | 2,028,956,059 | 10,625 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-04-01T00:02:59 | 2024-04-01T00:02:59 | {} | NONE |
vuejs | core | 2,033,954,713 | 10,642 | tgy3300 | > The dom instance can't be fetched until after the mounted.
主题已更新,改成这样也不行 | 2024-04-03T08:51:58 | 2024-04-03T08:51:58 | {} | NONE |
vuejs | core | 2,034,028,167 | 10,517 | chengazhen | i hava a same issue, but i see it is fixed in https://github.com/vuejs/core/issues/10098. why it it appear in this version ? | 2024-04-03T09:25:04 | 2024-04-03T09:25:04 | {} | NONE |
vuejs | core | 2,037,703,647 | 5,637 | ferferga | @sodatea I think this issue can be closed now? Isn't this what ``suspensible`` already does? See https://github.com/vuejs/core/pull/6736
There's no mention about it in the docs though, maybe I'll open a PR there. | 2024-04-04T16:47:39 | 2024-04-04T16:47:39 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.