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,876,845,909 | 3,254 | Lehoczky | I think this can be closed now since https://github.com/vuejs/core/pull/3258 has been merged and released as part of v3.4 | 2024-01-04T10:18:44 | 2024-01-04T10:18:44 | {
"+1": 1
} | NONE |
vuejs | core | 1,876,850,365 | 3,254 | posva | Weird this didn't auto close once the change went into `main`. I guess it's because it wasn't in the commit message, only in the PR description | 2024-01-04T10:21:47 | 2024-01-04T10:21:47 | {} | MEMBER |
vuejs | core | 1,879,604,547 | 10,014 | LinusBorg | To a degree, that's expected.
We need to set the selected prop on each affected `<option>` when the parent *sets* the value during the re-render that was triggered by the change event of the select. To do that, we have to loo over all option elements, and for each element, look up the option's value in the list of ... | 2024-01-06T09:19:17 | 2024-01-06T09:19:17 | {} | MEMBER |
vuejs | core | 1,875,129,385 | 9,952 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 6cc91511fd215adcb7448a3f76b4564cc4abbbba |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-01-03T10:15:36 | 2024-01-03T10:15:36 | {} | NONE |
vuejs | core | 1,876,470,103 | 9,972 | baiwusanyu-c | workaround :
```
<script setup lang="ts">
const { isMulti } = defineProps<{ isMulti?: boolean }>();
const getter = () => {
return isMulti ? [] : '';
}
const model = defineModel({
get:getter,
})
</script>
```
The direct reason is that the compiler will first convert defineModel, and ... | 2024-01-04T06:30:08 | 2024-01-04T06:31:53 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,878,154,545 | 9,999 | baiwusanyu-c | Good idea, already modified | 2024-01-05T05:38:08 | 2024-01-05T05:38:08 | {} | MEMBER |
vuejs | core | 1,878,110,426 | 9,999 | baiwusanyu-c | case 1:
```
<template>
<transition name="page" mode="out-in" :duration="300">
<Suspense>
<component :is="Component" />
</Suspense>
</transition>
<button @click="toggle" id='cc'>Trigger error</button>
</template>
```
https://deploy-preview-9999--vue-sfc-playground.netlify.app/#eNqt... | 2024-01-05T04:34:18 | 2024-01-05T05:39:25 | {} | MEMBER |
vuejs | core | 1,878,577,565 | 10,007 | AhmadALi-glitch | I'm Sorry , I didn't understand the context of the OP
| 2024-01-05T12:17:20 | 2024-01-05T14:58:27 | {} | NONE |
vuejs | core | 1,876,029,093 | 9,982 | LinusBorg | This is expected behavior. Yes, it sometimes trips people up, but its documented behavior that we won't change until we talk about another major release.
https://vuejs.org/api/sfc-css-features.html#child-component-root-elements | 2024-01-03T22:02:35 | 2024-01-03T22:02:35 | {} | MEMBER |
vuejs | core | 1,876,600,526 | 7,828 | edison1105 | fixed via https://github.com/vuejs/core/pull/7290 | 2024-01-04T07:29:44 | 2024-01-04T07:29:44 | {} | MEMBER |
vuejs | core | 1,876,676,455 | 9,987 | briankchan | From the docs:
> This macro can be used to declare a two-way binding prop that can be consumed via `v-model` from the parent component.
I would expect this to mean that the model value in the child component stays in sync with the ref value in the parent.
> Under the hood, this macro declares a model prop and ... | 2024-01-04T08:08:05 | 2024-01-04T08:08:05 | {} | NONE |
vuejs | core | 1,878,051,230 | 10,002 | Doctor-wu | Could you provide a simple reproduction? | 2024-01-05T02:50:09 | 2024-01-05T02:50:09 | {} | MEMBER |
vuejs | core | 1,879,534,560 | 9,999 | edison1105 | I took a closer look, and caching the anchor may not work. If the anchor is uninstalled, there may still be problems with rendering.
😂😂😂 | 2024-01-06T04:22:35 | 2024-01-06T04:22:35 | {} | MEMBER |
vuejs | core | 1,879,597,449 | 9,987 | briankchan | Yeah, that's pretty much my conclusion as well--the defaults system that comes from props is not ideal for models because of these weird edge cases; it's much simpler to just implement custom defaults like this instead. If this is the case, then it may be worth updating the documentation accordingly. | 2024-01-06T08:49:58 | 2024-01-06T08:49:58 | {} | NONE |
vuejs | core | 1,879,635,017 | 10,016 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-06T10:47:17 | 2024-01-06T10:47:17 | {} | NONE |
vuejs | core | 1,879,653,756 | 10,014 | 4refael | @LinusBorg I agree, but I think this could be optimized to the extent that it becomes unnoticeable. I believe the slowness here is caused by a slow array search in the v-model implementation.
Here's an example where I've attempted to replicate the behavior of v-model, maintaining the original value type and updating... | 2024-01-06T11:41:44 | 2024-01-06T11:44:23 | {} | NONE |
vuejs | core | 1,879,662,215 | 10,019 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-06T12:19:11 | 2024-01-06T12:19:11 | {} | NONE |
vuejs | core | 1,879,740,485 | 10,023 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-06T16:07:43 | 2024-01-06T16:07:43 | {} | NONE |
vuejs | core | 1,876,249,328 | 9,943 | baiwusanyu-c | I think the possible reason is that there is no component named Comp2 registered in the scope of the Comp2 component (when it is a recursive component, you cannot register the component itself within the component), then we can register it as a global component to solve the problem
https://play.vuejs.org/#eNp9U8Fy... | 2024-01-04T03:09:46 | 2024-01-04T03:09:46 | {} | MEMBER |
vuejs | core | 1,876,529,125 | 9,556 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7406431551)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7393634823) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/740... | 2024-01-04T06:57:50 | 2024-01-04T06:57:50 | {} | CONTRIBUTOR |
vuejs | core | 1,878,138,703 | 9,999 | edison1105 | I think we only need to obtain an anchor once and cache it. No matter how the branch is switched internally, the anchor will not change.
Like this:
```diff
if (activeBranch) {
// if the fallback tree was mounted, it may have been moved
// as part of a parent suspense. get the latest anchor for insertion
- ... | 2024-01-05T05:17:51 | 2024-01-05T05:17:51 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,878,554,428 | 10,007 | LinusBorg | `v-html` is not a solution / relevant here. OP doesn't have a usage question, they reported a bug in our handling of Frament elements. | 2024-01-05T11:58:26 | 2024-01-05T14:58:21 | {} | MEMBER |
vuejs | core | 1,879,219,536 | 8,639 | kevmul | I think the one thing this PR is missing is some a test showing it fails before this change and passes after. Just to prevent this issue from happening again in the future. | 2024-01-05T20:26:11 | 2024-01-05T20:26:11 | {} | NONE |
vuejs | core | 1,879,518,297 | 9,990 | yyx990803 | This is then normal, because of static hoisting does cause a copy of the DOM tree to be cached. As long as the total memory usage does not increase over time this is not considered a memory leak.
Closing as duplicate of #5256 | 2024-01-06T03:19:25 | 2024-01-06T03:19:25 | {} | MEMBER |
vuejs | core | 1,875,128,002 | 9,952 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a801c36c74ca833dd65becb43131c5338234f050 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-01-03T10:14:33 | 2024-01-03T10:14:33 | {} | NONE |
vuejs | core | 1,829,465,700 | 9,693 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.5 kB |
### Usages
| Name | Size |... | 2023-11-28T09:52:32 | 2024-01-03T14:37:24 | {} | NONE |
vuejs | core | 1,876,787,600 | 9,990 | edison1105 | Neither the number of dom nodes nor the memory will continue to grow. 🤔
| 2024-01-04T09:38:52 | 2024-01-04T09:38:52 | {} | MEMBER |
vuejs | core | 1,877,094,869 | 9,997 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7410066029)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7393634823) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/741... | 2024-01-04T13:27:34 | 2024-01-04T13:27:34 | {} | CONTRIBUTOR |
vuejs | core | 1,875,329,077 | 9,978 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.4 kB (**-3 B**) | 34 kB (**-5 B**) | 30.7 kB |
| v... | 2024-01-03T12:54:05 | 2024-01-03T12:54:05 | {} | NONE |
vuejs | core | 1,877,191,881 | 9,999 | baiwusanyu-c | It works as expected in the playground, but the result is incorrect in e2e. I may need some guidance. | 2024-01-04T14:32:25 | 2024-01-04T14:32:25 | {} | MEMBER |
vuejs | core | 1,877,192,291 | 9,999 | baiwusanyu-c | ```
// #9996
test(
'trigger again when transition is not finished & correctly anchor',
async () => {
await page().evaluate(duration => {
const { createApp, shallowRef, h } = (window as any).Vue
const One = {
async setup() {
return () => h(... | 2024-01-04T14:32:42 | 2024-01-05T04:31:24 | {} | MEMBER |
vuejs | core | 1,875,359,228 | 9,674 | Leen27 | 👍🏻 | 2024-01-03T13:16:47 | 2024-01-03T13:16:47 | {} | NONE |
vuejs | core | 1,876,229,541 | 9,978 | yyx990803 | I would consider this a fix since previously the effect isn't removed if the watcher is created in a detached scope. | 2024-01-04T02:36:37 | 2024-01-04T02:36:37 | {} | MEMBER |
vuejs | core | 1,876,748,663 | 9,991 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-04T09:10:38 | 2024-01-04T09:10:38 | {} | NONE |
vuejs | core | 1,877,084,230 | 9,997 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-04T13:19:16 | 2024-01-04T13:19:16 | {} | NONE |
vuejs | core | 1,877,099,493 | 9,987 | LinusBorg | > I would expect this to mean that the model value in the child component stays in sync with the ref value in the parent.
Well it does, it you don't define a default value. Defining a default value for a prop means "use this value if the parent doesn't provide a value", which is technically indistinguishable from "p... | 2024-01-04T13:31:01 | 2024-01-04T13:31:18 | {} | MEMBER |
vuejs | core | 1,877,235,035 | 9,995 | mitar | > How does this realate to what we actually call "async components" defined with `defineAsyncComponent`?
Sorry, it seems to me I was using bad terminology here. So there is:
* Component with top-level await in its setup.
* Lazy loaded component (as defined with vue-router).
* Async component (which can help with ... | 2024-01-04T14:58:59 | 2024-01-04T14:58:59 | {} | NONE |
vuejs | core | 1,871,950,475 | 9,941 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.3 kB | 34 kB (**-7 B**) | 30.7 kB (**+22 B**) |
| vue.global.prod.js | 146 k... | 2023-12-29T10:58:20 | 2023-12-29T10:58:20 | {} | NONE |
vuejs | core | 1,772,565,516 | 7,306 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB (**+46 B**) | 34.1 kB (**+36 B**) | 30.7 kB (**-1 B**) |
... | 2023-10-20T11:27:23 | 2023-12-30T19:05:25 | {} | NONE |
vuejs | core | 1,872,564,677 | 9,948 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.4 kB (**-82 B**) | 34 kB (**-19 B**) | 30.7 kB (**-39 B**) |
... | 2023-12-30T16:56:56 | 2023-12-31T09:48:53 | {} | NONE |
vuejs | core | 1,873,319,705 | 9,965 | LinusBorg | Don't think we need a new issue.
Thanks for the new playground. The issue here is that `props` is not a `reactive()` object, it's a `shallowReactive()`.
This is indeed a change, caused by a fix for #9916 (PR: https://github.com/vuejs/core/pull/9928)
watching a shallow object should only traverse the first lev... | 2024-01-01T13:03:40 | 2024-01-01T13:06:17 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,874,226,799 | 9,971 | LinusBorg | When I set `lang="ts"`on the script tag, so it actually uses Typescript, it *does* give me the appropriate error in the stackblitz:
<img width="579" alt="Bildschirmfoto 2024-01-02 um 17 08 17" src="https://github.com/vuejs/core/assets/1444526/9be45c5b-7f7f-4d5f-9422-119fd7ad99d8">
I tested both with Vue 3.3 (as i... | 2024-01-02T16:10:12 | 2024-01-02T16:10:56 | {} | MEMBER |
vuejs | core | 1,871,953,404 | 9,942 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.3 kB | 34 kB | 30.6 kB |
| vue.global.prod.js | 146 kB | 53.2 kB | 47.6 kB |
### Usages
| Name | Size |... | 2023-12-29T11:02:40 | 2023-12-29T11:02:40 | {} | NONE |
vuejs | core | 1,872,515,545 | 9,572 | Alfred-Skyblue | Due to the consideration that users might have previously passed "deep" as a number in their usage, which was mistakenly treated as true in the previous implementation, if we now interpret "deep number" as referring to depth, the earlier practice of passing "deep" as a number would result in inconsistency. Of course, s... | 2023-12-30T12:06:54 | 2023-12-30T12:06:54 | {} | MEMBER |
vuejs | core | 1,873,095,131 | 9,960 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-01T01:40:36 | 2024-01-01T01:40:36 | {} | NONE |
vuejs | core | 1,874,783,095 | 8,425 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a294dee63cdc6c408b7a423516edfd094b03ce40 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2024-01-03T02:40:08 | 2024-01-03T02:41:09 | {} | NONE |
vuejs | core | 1,738,632,468 | 8,403 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB |
... | 2023-09-28T07:35:59 | 2024-01-03T02:44:25 | {} | NONE |
vuejs | core | 1,873,747,360 | 9,966 | edison1105 | https://github.com/vuejs/core/blob/8498fcb8d8328016a913181dda8756cfda33e1eb/packages/runtime-core/src/components/Suspense.ts#L479
Or we can change the initial value to `pendingId: suspenseId++`
| 2024-01-02T08:49:57 | 2024-01-03T03:24:58 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,687,318,847 | 7,901 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.6 kB (**+125 B**) | 34.1 kB (**+47 B**) | 30.7 kB (**+39 B**)... | 2023-08-22T02:26:18 | 2024-01-03T07:34:58 | {} | NONE |
vuejs | core | 1,795,340,384 | 9,556 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.3 kB | 34 kB | 30.6 kB |
| vue.global.prod.js | 146 kB | 53.2 kB | 47.6 kB |
### Usages
| Name | Size |... | 2023-11-06T16:22:22 | 2023-12-29T14:09:03 | {} | NONE |
vuejs | core | 1,872,482,995 | 9,928 | Alfred-Skyblue | I added a `depth` option in #9572 to control the depth of watch listeners. When the object being watched is a `shallowReactive`, it should only listen to changes at the first level.
| 2023-12-30T08:31:03 | 2023-12-30T08:31:03 | {} | MEMBER |
vuejs | core | 1,772,960,985 | 7,745 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB (**+5 B**) | 34 kB (**+6 B**) | 30.7 kB (**+28 B**) |
| vue.... | 2023-10-20T15:31:42 | 2023-12-30T23:21:49 | {} | NONE |
vuejs | core | 1,875,068,081 | 9,916 | yyx990803 | Reverted the shallow default behavior - see https://github.com/vuejs/core/issues/9965#issuecomment-1875067499 | 2024-01-03T09:27:48 | 2024-01-03T09:27:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,871,296,209 | 9,862 | pikax | I'll close this since there's no additional information has been provided, please create an error on element-plus repo, they can provide more information about if the issue is upstream or not. | 2023-12-28T15:54:40 | 2023-12-28T15:54:40 | {} | MEMBER |
vuejs | core | 1,871,711,125 | 9,875 | Masa-Shin | Updated the PR to fix enum value. | 2023-12-29T04:00:22 | 2023-12-29T04:00:22 | {} | CONTRIBUTOR |
vuejs | core | 1,721,466,458 | 8,657 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB (**+9 B**) | 34 kB (**+4 B**) | 30.7 kB (**+6 B**) |
| vue.... | 2023-09-15T15:28:48 | 2024-01-03T02:10:16 | {} | NONE |
vuejs | core | 1,874,772,041 | 9,973 | baiwusanyu-c | This is a downstream component library adaptation problem. Please ask the component library maintainer to confirm whether the version can be adapted and whether it is an upstream framework problem. | 2024-01-03T02:15:19 | 2024-01-03T02:15:19 | {} | MEMBER |
vuejs | core | 1,871,686,465 | 9,937 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.2 kB | 47.6 kB |
### Usages
| Name | Size |... | 2023-12-29T02:39:34 | 2023-12-30T01:18:36 | {} | NONE |
vuejs | core | 1,872,799,811 | 9,947 | gigabites19 | This is a cool pattern, thanks for sharing | 2023-12-31T07:47:14 | 2023-12-31T07:47:14 | {} | NONE |
vuejs | core | 1,873,101,975 | 9,961 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-01T01:55:26 | 2024-01-01T01:55:26 | {} | NONE |
vuejs | core | 1,738,688,395 | 7,266 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB (**+12 B**) | 34 kB (**+5 B**) | 30.7 kB (**+13 B**) |
... | 2023-09-28T08:16:39 | 2024-01-03T03:35:05 | {} | NONE |
vuejs | core | 1,807,508,985 | 7,151 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------ | ------------------ |
| runtime-dom.global.prod.js | 89.5 kB (**+28 B**) | 34 kB (**+11 B**) | 30.7 kB (**+7 B**) |
| vue.... | 2023-11-13T05:40:49 | 2024-01-03T03:37:12 | {} | NONE |
vuejs | core | 1,872,461,341 | 7,330 | yangmingshan | I think this PR may have hidden issues, especially for undetached effectScope. There are many other functions depends on currentInstance, like `callWithErrorHandling` `queuePostRenderEffect` etc.
`watchEffect` should be same as `watch`, maybe we can remove instance unmounted short circuit in `watchEffect`, since `wa... | 2023-12-30T05:57:18 | 2023-12-30T05:57:18 | {} | CONTRIBUTOR |
vuejs | core | 1,872,579,120 | 7,827 | skirtles-code | I believe this problem has been fixed by the overhaul of the reactivity system in 3.4. | 2023-12-30T18:25:46 | 2023-12-30T18:25:46 | {} | CONTRIBUTOR |
vuejs | core | 1,874,801,276 | 7,434 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.6 kB (**+110 B**) | 34.1 kB (**+49 B**) | 30.8 kB (**+52 B**)... | 2024-01-03T03:18:54 | 2024-01-03T03:18:54 | {} | NONE |
vuejs | core | 1,874,998,033 | 6,783 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ---------------------- | -------------------- | -------------------- |
| runtime-dom.global.prod.js | 91.3 kB (**+1.84 kB**) | 34.8 kB (**+810 B**) | 31.4 kB ... | 2024-01-03T08:25:14 | 2024-01-03T08:25:14 | {} | NONE |
vuejs | core | 1,875,126,631 | 9,975 | pikax | Using internal API/behaviours can cause these sort of issues, since they are not public they might not be tested directly and the tests are done by other places that rely on that behaviour.
My personal opinion and not talking as Vue team or any official manner:
I think there's an incorrect usage of the internal ... | 2024-01-03T10:13:26 | 2024-01-03T10:13:26 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,872,535,137 | 9,572 | Alfred-Skyblue | Agreed. It's a good plan. | 2023-12-30T14:10:39 | 2023-12-30T14:10:39 | {} | MEMBER |
vuejs | core | 1,874,763,992 | 9,451 | zhangenming | ```vue
// how about
<comp @event></comp>
// equivalent to
<comp @event="event"></comp>
``` | 2024-01-03T01:56:54 | 2024-01-03T01:56:54 | {
"+1": 5
} | CONTRIBUTOR |
vuejs | core | 1,874,792,204 | 7,891 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-03T02:58:33 | 2024-01-03T02:58:33 | {} | NONE |
vuejs | core | 1,873,313,482 | 9,965 | LinusBorg | I'm not sure if I understand the issue.
When you watch a ref without `deep: true`, then is should only be triggered when you re-assign the ref, not when you update a deeply nested reactive value. That's how it *should* work in my understanding, and that's what I'm seeing here.
The docs mention only one specific ... | 2024-01-01T12:45:34 | 2024-01-01T12:51:19 | {} | MEMBER |
vuejs | core | 1,873,726,775 | 9,949 | pikax | /ecosystem-ci run | 2024-01-02T08:24:15 | 2024-01-02T08:24:15 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,873,735,219 | 9,943 | arturs-buls | Yes, thanks for pointing that out. Updated Reproduction link and added sample in additional comments | 2024-01-02T08:35:21 | 2024-01-02T15:55:43 | {
"+1": 1
} | NONE |
vuejs | core | 1,874,350,293 | 9,971 | sleewoo | simply had to update editor's `vue-language-server` :)
thanks
| 2024-01-02T17:50:42 | 2024-01-02T17:50:42 | {} | NONE |
vuejs | core | 1,874,782,089 | 9,973 | baiwusanyu-c | We have already given feedback to the author of the component library for you. Please wait for them to fix it. If there are other problems, open the issue again. | 2024-01-03T02:37:54 | 2024-01-03T02:37:54 | {} | MEMBER |
vuejs | core | 1,874,906,676 | 9,966 | edison1105 | @RicardoErii
No additional test cases need to be added, but the relevant logic for `resetSuspenseId` needs to be added. To make sure there is no regression in the future. | 2024-01-03T06:33:08 | 2024-01-03T06:33:08 | {} | MEMBER |
vuejs | core | 1,872,527,913 | 9,931 | yyx990803 | I don't think this is related to static hoisting. This is actually caused by the devtools `_buffer` if you look at the retainers of the detached HTML elements, and it won't happen in production (or if you disable the devtools).
Even with the devtools `_buffer`, it is cleared after a short time and you won't see deta... | 2023-12-30T13:25:44 | 2023-12-30T13:25:44 | {} | MEMBER |
vuejs | core | 1,872,528,503 | 9,935 | yyx990803 | This is expected because inline styles are not considered part of the `<scoped style>`.
`<scoped style>` requires compile-time transforms. Inline styles can potentially contain dynamic values that come from anywhere, so there is no way for Vue to consistently make them work with scoped style. | 2023-12-30T13:29:32 | 2023-12-30T13:29:32 | {} | MEMBER |
vuejs | core | 1,872,565,329 | 9,948 | yangmingshan | /ecosystem-ci run | 2023-12-30T17:01:07 | 2023-12-30T17:01:07 | {
"-1": 1,
"laugh": 1
} | CONTRIBUTOR |
vuejs | core | 1,872,602,294 | 9,916 | jods4 | @yyx990803
👍 for respecting `{ deep: false }`, but RE: depth 1 for shallow reactives:
**This PR is an (unannounced) breaking change in a patch (not even minor!) release!! Before 3.4.2 a shallow reactive was deeply observed, after upgrade to 3.4.2 it is only observed shallowly, leading to observable changes in beh... | 2023-12-30T20:40:12 | 2023-12-31T01:57:33 | {} | CONTRIBUTOR |
vuejs | core | 1,872,671,992 | 9,953 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB (**+5 B**) | 34 kB (**+3 B**) | 30.7 kB (**+52 B**) |
| vue.... | 2023-12-31T05:04:12 | 2023-12-31T05:04:12 | {} | NONE |
vuejs | core | 1,872,921,970 | 9,933 | edison1105 | I will take a closer look later. | 2023-12-31T11:07:08 | 2023-12-31T11:07:08 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,873,316,365 | 9,965 | huang-julien | @LinusBorg Oops sorry, I've been too quick when analyzing the issue.
So i think the issue is probably when passing down an object Ref to a component which watch its own props
https://play.vuejs.org/#eNqFUk1LAzEQ/StjLluh7iLe6ragIqgHFRU8GA9ld7pNzSYhybaFZf+7k6z9Aq2HQOa9l+RN5rXsyph02SAbsdwVVhgPDn1jJlyJ2mjroQWLM+hgZ... | 2024-01-01T12:53:58 | 2024-01-01T12:53:58 | {} | CONTRIBUTOR |
vuejs | core | 1,873,726,321 | 9,948 | pikax | /ecosystem-ci run | 2024-01-02T08:23:40 | 2024-01-02T08:23:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,873,731,862 | 9,948 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7383634382)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7375028980) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/738... | 2024-01-02T08:30:57 | 2024-01-02T08:30:57 | {} | CONTRIBUTOR |
vuejs | core | 1,874,779,715 | 8,548 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.6 kB (**+115 B**) | 34.1 kB (**+29 B**) | 30.7 kB (**+16 B**)... | 2024-01-03T02:33:05 | 2024-01-03T02:33:05 | {} | NONE |
vuejs | core | 1,874,795,664 | 7,776 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 7be86427521a508b5cceff1db79bf1bedbbdf467 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2024-01-03T03:06:17 | 2024-01-03T03:06:17 | {} | NONE |
vuejs | core | 1,875,037,586 | 9,970 | yyx990803 | Looks like I unintentionally introduced this regression in https://github.com/vuejs/core/commit/f15d2f6cf69c0c39f8dfb5c33122790c68bf92e2
If this is in fact a Buffer, we should probably just revert the change to always do `JSON.parse(result.map.toString())`. | 2024-01-03T09:03:24 | 2024-01-03T09:03:38 | {} | MEMBER |
vuejs | core | 1,872,500,755 | 9,943 | LinusBorg | The reproduction seems to not include anything related to the description.
* no use of `<component>`
* no `getComponentName()`
* no recursive usage
So it's not helping to reproduce the issue.
Did you accidentally replace it with a wrong link?
| 2023-12-30T10:30:07 | 2023-12-30T10:30:07 | {} | MEMBER |
vuejs | core | 1,872,529,021 | 9,572 | yyx990803 | That's a good point. I think we can add a warning in a 3.4 patch that checks for `deep` with number values and warn users that it will be treated as depth in a future version. | 2023-12-30T13:33:05 | 2023-12-30T13:33:05 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,872,534,105 | 7,330 | yyx990803 | @yangmingshan PR welcome so we can take a better look and run ecosystem-ci if needed. | 2023-12-30T14:05:14 | 2023-12-30T14:05:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,873,322,347 | 9,966 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB (**+3 B**) | 34 kB (**+2 B**) | 30.8 kB (**+51 B**) |
| vue.... | 2024-01-01T13:10:24 | 2024-01-02T13:58:48 | {} | NONE |
vuejs | core | 1,874,783,083 | 8,425 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a294dee63cdc6c408b7a423516edfd094b03ce40 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-01-03T02:40:07 | 2024-01-03T02:41:08 | {} | NONE |
vuejs | core | 1,875,038,826 | 9,970 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-03T09:04:26 | 2024-01-03T09:04:26 | {} | NONE |
vuejs | core | 1,871,979,865 | 6,483 | plabiausse | Is it possible to have a follow up on this issue ? The fact that it impacts only the code pushed in production, and not the code in dev mode is especially hurting :'(.
For reference I've been bitten by it both for bindings `:var="new Test()"` and triggers `@click="test = new Test()"`
It is sometimes lighter and m... | 2023-12-29T11:39:41 | 2023-12-29T11:40:23 | {
"+1": 1
} | NONE |
vuejs | core | 1,773,044,401 | 7,360 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB (**-17 B**) |... | 2023-10-20T16:29:58 | 2023-12-31T01:38:15 | {} | NONE |
vuejs | core | 1,873,734,072 | 9,949 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7383638204)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7375028980) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/738... | 2024-01-02T08:33:54 | 2024-01-02T08:33:54 | {} | CONTRIBUTOR |
vuejs | core | 1,874,774,259 | 9,973 | zhou5631 | > This is a downstream component library adaptation problem. Please ask the component library maintainer to confirm whether the version can be adapted and whether it is an upstream framework problem.
ant-design-vue 19.1K
https://github.com/vueComponent/ant-design-vue/issues/7239
vue-vben-admin 20.9K
https://git... | 2024-01-03T02:19:43 | 2024-01-03T02:19:43 | {} | NONE |
vuejs | core | 1,874,784,928 | 9,966 | edison1105 | @RicardoErii
You don't need to add e2e tests. Some test cases in `Suspense.spec.ts` are likely problematic. The current test cases pass because `suspenseId` does not start from 0. I don't have permission to modify your PR directly, so I'm providing the solution here:
- Add `export const resetSuspenseId = () => sus... | 2024-01-03T02:44:05 | 2024-01-03T03:18:08 | {} | MEMBER |
vuejs | core | 1,874,804,968 | 9,931 | Joshua-Leee | In fact, you can try to package the basic hello world app, use nginx to access the index.html file in the dist generated by the package, and do what I said above, you will find that the svg ICONS are not released after separation, because I use the element-plus ui library, This library uses a lot of svg ICONS, and I'm ... | 2024-01-03T03:27:22 | 2024-01-03T03:27:22 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.