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,771,390,128 | 13,127 | iiio2 | Oh I see. Ok @edison1105 . Thanks. | 2025-04-02T05:39:29 | 2025-04-02T05:39:29 | {} | CONTRIBUTOR |
vuejs | core | 2,775,095,026 | 11,517 | RozbehSharahi | This is not a real solution to the issue imho. I might be worng.
As far as I can see, this way it is not possible to use the same child-component within a shadow-root and within normal app scenario.
Imagine a button you want to use on the one-hand on some shadow-root component and one the other hand within an app... | 2025-04-03T09:37:39 | 2025-04-03T09:38:06 | {} | NONE |
vuejs | core | 2,780,148,727 | 13,163 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.4 kB |
| vue.global.prod.js | 158 kB | 58.3 kB | 51.9 kB |
### Usages
| Name | Size | G... | 2025-04-05T02:29:38 | 2025-04-05T02:29:38 | {} | NONE |
vuejs | core | 2,763,036,019 | 8,146 | Giwayume | I tried Vue versions from the very latest 3.5.13 all the way back to 3.2.0 to check if this is a regression (can't go lower from other dependencies) and it breaks the same. | 2025-03-29T02:37:08 | 2025-03-29T02:43:39 | {} | NONE |
vuejs | core | 2,764,329,419 | 13,118 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 101 kB | 38.3 kB | 34.6 kB |
| vue.global.prod.js | 159 kB | 58.4 kB | 52 kB |
### Usages
| Name | Size | G... | 2025-03-30T01:29:11 | 2025-03-30T01:29:11 | {} | NONE |
vuejs | core | 2,764,347,586 | 13,118 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/14151702043)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/14122305444) |
|-------|--------|----------------|
| vuetify | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/action... | 2025-03-30T02:27:39 | 2025-03-30T02:27:39 | {} | CONTRIBUTOR |
vuejs | core | 2,746,580,333 | 13,093 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/3eecf2a1-901f-4680-a861-3e401c1427be)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13093
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-24T00:23:21 | 2025-03-31T01:54:10 | {} | NONE |
vuejs | core | 2,765,010,554 | 13,122 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.3 kB |
| vue.global.prod.js | 158 kB | 58.2 kB | 51.8 kB |
### Usages
| Name | Size | G... | 2025-03-31T03:33:29 | 2025-03-31T03:33:29 | {} | NONE |
vuejs | core | 2,767,756,321 | 13,125 | edison1105 | LGTM | 2025-04-01T00:59:11 | 2025-04-01T00:59:11 | {} | MEMBER |
vuejs | core | 2,772,755,452 | 13,153 | jimei416 | #13152 | 2025-04-02T14:31:14 | 2025-04-02T14:31:14 | {} | NONE |
vuejs | core | 2,780,161,121 | 13,163 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/14277670340)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/14258348052) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci... | 2025-04-05T02:58:57 | 2025-04-05T02:58:57 | {} | CONTRIBUTOR |
vuejs | core | 2,763,127,860 | 13,116 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed. **[Why did it fail? →](https://app.netlify.com/sites/vue-next-template-explorer/deploys/67e78b870bd20a00086e6a07?deploy_diagnostics=true)**
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> ... | 2025-03-29T05:59:45 | 2025-03-29T05:59:45 | {} | NONE |
vuejs | core | 2,741,328,752 | 13,078 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 101 kB (**-118 B**) | 38.3 kB (**-10 B**) | 34.5 kB (**-49 B**) |
... | 2025-03-20T18:28:47 | 2025-03-31T05:30:30 | {} | NONE |
vuejs | core | 2,741,329,140 | 13,078 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/9106385c-daa3-4f02-943e-80d2f9ee0d9d)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13078
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-20T18:28:58 | 2025-03-31T05:39:53 | {} | NONE |
vuejs | core | 2,768,247,575 | 13,126 | drylint | > Thanks for the PR. Will this change improve performance? If so, please provide a benchmark. If not, it's not worth it.
It has almost no effect on performance, and all it does is reduce the length of the literal string (tens of characters) and, if anything, reduce the size of the package by a little.
| 2025-04-01T06:12:15 | 2025-04-01T06:12:15 | {} | NONE |
vuejs | core | 2,768,983,411 | 12,615 | Maxim-Mazurok | I'm seeing something related...
Upgrading from `3.3.11` to `3.5.0`.
I've had a Map, where keys were reactive (values from a reactive array), and I would pass reactive value into `.get(...)` and it would work.
Now I have to convert all keys `toRaw` and I have to do `.git(toRaw(...))` as well. Not sure what happened...
... | 2025-04-01T11:00:07 | 2025-04-02T06:51:36 | {} | NONE |
vuejs | core | 2,771,809,491 | 13,144 | pkg-pr-new[bot] |
[Open in StackBlitz](https://pkg.pr.new/template/84b16590-e426-4dbd-a5c4-19d293fec5d4)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13144
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-04-02T08:33:04 | 2025-04-02T08:49:15 | {} | NONE |
vuejs | core | 2,774,023,250 | 13,153 | edison1105 | A workaround is to use `v-if` instead of `v-show` | 2025-04-03T00:13:42 | 2025-04-03T00:13:42 | {} | MEMBER |
vuejs | core | 2,764,337,665 | 13,118 | edison1105 | /ecosystem-ci run vuetify | 2025-03-30T02:01:25 | 2025-03-30T02:01:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,764,344,265 | 13,118 | edison1105 | /ecosystem-ci run vuetify | 2025-03-30T02:15:45 | 2025-03-30T02:15:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,765,177,448 | 13,078 | johnsoncodehk | /ecosystem-ci run | 2025-03-31T05:19:45 | 2025-03-31T05:19:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,765,690,207 | 13,001 | edison1105 | @dili021
Try `npm i https://pkg.pr.new/vue@13001` or wait for the next patch release. (will soon) | 2025-03-31T09:35:38 | 2025-03-31T09:35:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,777,433,743 | 13,157 | jh-leong | The prop instability occurs because `@click="select(item.id)"` compiles to a new function on each render (`onClick: $event => ($setup.select(item.id))`). You can verify this in the Playground's JS output.
As a workaround, declare the emit option in `ListItem` to skip the event props check: [Playground](https://play.vu... | 2025-04-04T02:48:45 | 2025-04-04T02:48:45 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,764,329,737 | 13,118 | edison1105 | /ecosystem-ci run vuetify | 2025-03-30T01:30:20 | 2025-03-30T01:30:20 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,765,048,455 | 13,078 | johnsoncodehk | /ecosystem-ci run | 2025-03-31T04:09:32 | 2025-03-31T04:09:32 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,765,244,721 | 13,001 | edison1105 | /ecosystem-ci run | 2025-03-31T06:18:23 | 2025-03-31T06:18:23 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,765,850,607 | 12,935 | johnsoncodehk | /ecosystem-ci run | 2025-03-31T10:45:19 | 2025-03-31T10:45:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,769,309,932 | 13,127 | edison1105 | Thanks. But the main branch is already using Node 22 for Netlify deploy, so there's no need to modify it on the vapor branch | 2025-04-01T13:10:14 | 2025-04-01T13:10:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,771,807,433 | 13,144 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vapor-repl* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 53564e01b7870bcddcbd35ab439b97593d21c255 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vapor-repl/d... | 2025-04-02T08:32:17 | 2025-04-02T08:49:34 | {} | NONE |
vuejs | core | 2,780,354,664 | 13,126 | edison1105 | Thank you for your PR, but `toRawType` internally actually calls `toTypeString` and includes a `slice` operation, which is not as performant as directly calling `toTypeString`. | 2025-04-05T06:51:08 | 2025-04-05T06:51:08 | {} | MEMBER |
vuejs | core | 2,764,608,203 | 12,761 | danyadev | I think it's related to the issue when generics stop working when the second argument of defineComponent is present
On the first screenshot everything is fine with the generic (except that props don't work)
On the second screenshot I've added a list of props, but the generic just disappeared
<img height="400" alt="... | 2025-03-30T15:12:15 | 2025-03-30T16:16:57 | {} | CONTRIBUTOR |
vuejs | core | 2,767,930,242 | 13,126 | edison1105 | Thanks for the PR. Will this change improve performance?
If so, please provide a benchmark.
If not, it's not worth it. | 2025-04-01T02:58:55 | 2025-04-01T02:59:12 | {} | MEMBER |
vuejs | core | 2,777,669,365 | 13,158 | RobinWM | sdfsdf
edison ***@***.***> 于2025年4月4日周五 10:57写道：
> Note: selectedcontent is under experimentation
> https://developer.mozilla.org/en-US/docs/Web/HTML/Element/selectedcontent
>
> —
> Reply to this email directly, view it on GitHub
> <https://github.com/vuejs/core/issues/13158#issuecomment-2777441196... | 2025-04-04T06:27:58 | 2025-04-04T13:42:52 | {} | NONE |
vuejs | core | 2,780,158,539 | 13,163 | edison1105 | /ecosystem-ci run | 2025-04-05T02:52:46 | 2025-04-05T02:52:46 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,775,728,219 | 13,156 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.4 kB |
... | 2025-04-03T13:05:42 | 2025-04-07T00:18:01 | {} | NONE |
vuejs | core | 2,768,664,600 | 13,128 | pkg-pr-new[bot] |
[Open in StackBlitz](https://pkg.pr.new/template/bafc3091-e21c-4272-9d0b-338eeb948525)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13128
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-04-01T08:57:33 | 2025-04-01T08:57:33 | {} | NONE |
vuejs | core | 2,776,158,619 | 11,517 | patroza | > This is not a real solution to the issue imho. I might be worng.
>
> As far as I can see, this way it is not possible to use the same child-component within a shadow-root and within normal app scenario.
>
> Imagine a button you want to use on the one-hand on some shadow-root component and one the other hand wit... | 2025-04-03T15:21:56 | 2025-04-03T15:21:56 | {} | NONE |
vuejs | core | 2,559,685,388 | 12,575 | Gwynerva | @edison1105 Now it is working with async Comp and not working with sync Comp (try commenting and uncommenting `await ...` Promise line in `Comp.vue`). And this bug works even when SSR is turned off, also in both (async and sync) cases it warns in console 🤣
To be more precise, it actually "kind of" works, but instea... | 2024-12-23T13:10:13 | 2024-12-23T13:16:50 | {} | NONE |
vuejs | core | 2,560,486,648 | 12,591 | edison1105 | Vue compiler cannot find all `onServerPrefetch` calls during compilation. Apart from the scenario mentioned by @danielroe, users may also call an externally imported function, which internally calls `onServerPrefetch`. | 2024-12-24T00:52:23 | 2024-12-24T00:52:23 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,560,775,367 | 12,575 | edison1105 | > @edison1105 Why sync Comp.vue calling both setup and render? Isn't sync version is supposed to trigger parent `onErrorCaptured` which causes a component replacement just as it happens in async version? Or why async version is not calling both setup and render?
>
> I want to show only actual error, the error in `se... | 2024-12-24T07:32:24 | 2024-12-24T07:33:09 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,558,819,486 | 12,599 | dependabot[bot] | Looks like rollup is no longer updatable, so this is no longer needed. | 2024-12-23T03:10:00 | 2024-12-23T03:10:00 | {} | CONTRIBUTOR |
vuejs | core | 2,558,833,256 | 12,600 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/27249fcf-181a-4bb0-b2f4-54f698a11da9)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12600
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-23T03:25:43 | 2024-12-23T03:25:43 | {} | NONE |
vuejs | core | 2,561,874,435 | 12,612 | edison1105 | related https://github.com/vuejs/core/pull/11162 https://github.com/vuejs/core/issues/11125 | 2024-12-25T12:39:32 | 2024-12-25T12:39:32 | {} | MEMBER |
vuejs | core | 2,566,227,949 | 12,632 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/dd8ebfcf-bcaa-41c8-80ad-4bac80af76a7)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12632
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-31T08:13:38 | 2024-12-31T08:21:38 | {} | NONE |
vuejs | core | 2,558,826,589 | 12,586 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.... | 2024-12-23T03:18:01 | 2024-12-23T03:18:01 | {} | NONE |
vuejs | core | 2,559,634,753 | 12,575 | Gwynerva | @edison1105 Sadly, I can't use your PR on Vue SFC Playground. But I made a [StackBlitz demo](https://stackblitz.com/edit/github-gkqcng5e?file=src%2Fcomponents%2FComp.vue) with your PR and reproduced the same example as in first post.
Right now it does not even catching errors in sync Comp setup (with Promise line co... | 2024-12-23T12:39:30 | 2024-12-23T12:42:13 | {} | NONE |
vuejs | core | 2,559,926,069 | 12,591 | huang-julien | Yes, useAsyncData is a too specific case to be handled by vue-compiler. In the meantime, we can try the second option using an empty `instance.sp = instance.sp || []`
Or fully remove the treeshaking of onServerPrefetch and we try treeshaking the callback in Nuxt side ? | 2024-12-23T15:42:19 | 2024-12-23T15:48:40 | {} | CONTRIBUTOR |
vuejs | core | 2,560,520,083 | 12,575 | edison1105 | > @edison1105 Now it is working with async Comp and not working with sync Comp (try commenting and uncommenting `await ...` Promise line in `Comp.vue`). And this bug works even when SSR is turned off, also in both (async and sync) cases it warns in console 🤣
>
> To be more precise, it actually "kind of" works, but ... | 2024-12-24T01:41:28 | 2024-12-24T01:55:03 | {} | MEMBER |
vuejs | core | 2,561,831,679 | 12,612 | yangliguo7 | https://github.com/vuejs/core/blob/21f8d9dba9bb51f2a5c943193c12acd5c7cca9ec/packages/runtime-core/src/helpers/useModel.ts#L61-L64
when using useModel and the data unchanged, the data will not be triggered. This is inconsistent with emit
I'm not sure if we should emit when the data hasn't changed.
If there i... | 2024-12-25T10:46:09 | 2024-12-25T10:46:09 | {} | CONTRIBUTOR |
vuejs | core | 2,561,655,782 | 12,575 | Gwynerva | @edison1105 Does this mean there are no ways to do component replacement in parent when async child throws with Suspense + SSR? I tried to use nested `<Suspense>` inside Wrapper with `supensible` attribute but it changes nothing unfortunately.
> for this scenarios, you should use `data-allow-mismatch = "children"` t... | 2024-12-25T06:37:34 | 2024-12-25T12:50:06 | {} | NONE |
vuejs | core | 2,563,770,140 | 12,619 | catsmeatman | bug exist from Vue 3.5.0. In Vue 3.4.38 all ok. | 2024-12-27T14:48:48 | 2024-12-27T14:49:34 | {} | NONE |
vuejs | core | 2,564,941,348 | 12,628 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-30T01:41:32 | 2024-12-30T01:41:32 | {} | NONE |
vuejs | core | 2,566,193,514 | 7,997 | Mrlilili | > > Yes - although I'd write:
> > ```js
> > export function useQuery (variables) {
> > watch(() => toValue(variables), (value) => {})
> > }
> > ```
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > which would be more efficient as it doesn't create an intermedia... | 2024-12-31T07:12:49 | 2024-12-31T07:12:49 | {} | NONE |
vuejs | core | 2,567,629,485 | 12,570 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/12581146825)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/12567376952) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci... | 2025-01-02T11:26:41 | 2025-01-02T11:26:41 | {} | CONTRIBUTOR |
vuejs | core | 2,558,826,956 | 12,586 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/461e5e6c-06a7-4ae7-8414-53b37bee5ca7)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12586
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-23T03:18:25 | 2024-12-23T03:18:25 | {} | NONE |
vuejs | core | 2,559,039,113 | 12,584 | LoveVin | @edison1105 "Why should I change the way native custom tags are used, and it's unreasonable to ask users to add a ^ prefix when assigning attributes to custom tags within a Vue3 project. You mentioned that this is an issue with Vue3's handling method. Is this a bug in Vue3? Vue3 should not affect the definition and us... | 2024-12-23T07:04:59 | 2024-12-23T07:04:59 | {} | NONE |
vuejs | core | 2,561,883,205 | 12,575 | Gwynerva | Such a long road to such a painful failure, lol.
Well, I think my only option here is to redesing some core functionality.
Maybe require every SSR compatible child to have sync setup, which receives precalculated async data through props, and that async data is calculated in parent component, where I can catch asyn... | 2024-12-25T13:04:40 | 2024-12-25T13:12:25 | {} | NONE |
vuejs | core | 2,558,742,666 | 12,594 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/51d4530f-da6a-4870-ae51-1b375d523cec)
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-sfc@12594
```
</p></details>
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/... | 2024-12-23T01:45:26 | 2024-12-30T01:41:38 | {} | NONE |
vuejs | core | 2,568,609,473 | 12,637 | edison1105 | I can't reproduce it on my local machine with
```
"vue": "3.5.13",
"typescript": "5.7.2",
"vue-tsc": "2.2.0"
``` | 2025-01-03T02:06:54 | 2025-01-03T02:06:54 | {} | MEMBER |
vuejs | core | 2,568,783,716 | 12,643 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-03T07:16:29 | 2025-01-03T07:16:29 | {} | NONE |
vuejs | core | 2,568,813,753 | 12,636 | edison1105 | duplicate of #11617
a workaround
```diff
+ <div>
<Child
ref="childRef"
v-model="rwableImportedList"
:imported="onImported"
:anyProp="!childRef"
/>
+ </div>
```
will be fixed via #11619
see [Playground with PR#11619 ](https://deploy-preview-11619--vue-sfc-playground.netlify.app/#e... | 2025-01-03T07:54:06 | 2025-01-03T07:59:18 | {} | MEMBER |
vuejs | core | 2,544,457,871 | 12,561 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/0c8f7715-59c2-4d78-b51a-fd48ad60c68a)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12561
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-16T03:15:28 | 2024-12-23T03:07:42 | {} | NONE |
vuejs | core | 2,558,817,216 | 12,597 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-23T03:07:34 | 2024-12-23T03:10:52 | {} | NONE |
vuejs | core | 2,559,893,838 | 12,591 | danielroe | I'm happy to remove treeshaking of `onServerPrefetch`, more generally, and leave it up to the vue compiler - but it's not quite that straightforward. In this case, the call to `onServerPrefetch` is in an entire separate if/then fork (because data fetching on the server and in the hydration process in the browser run di... | 2024-12-23T15:21:33 | 2024-12-23T15:23:16 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,560,778,817 | 12,575 | Gwynerva | Ok, I see now. So I guess my solution here is to display div with the first error only and supress everything after.
So the only problem left are hydration mismatches in my project, but I guess they might be because of [this bug](https://github.com/vuejs/core/issues/12520#issuecomment-2559070207) we discovered as I he... | 2024-12-24T07:35:58 | 2024-12-24T07:37:33 | {} | NONE |
vuejs | core | 2,561,028,810 | 12,520 | Gwynerva | @Ghosterbeef turns out it's a `<p>` problem, not a Vue bug! | 2024-12-24T11:41:16 | 2024-12-24T11:42:12 | {
"heart": 1
} | NONE |
vuejs | core | 2,561,925,370 | 12,570 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/12494263813)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/12489583301) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-12-25T15:14:42 | 2024-12-25T15:14:42 | {} | CONTRIBUTOR |
vuejs | core | 2,564,955,468 | 12,619 | edison1105 | @catsmeatman
It seems not, see [Playground with v3.4.38](https://play.vuejs.org/#eNqVVVtvmzAU/iseL5AqhYb2YcqSSFvVh+1hq9Y+Ik0MThI6YyPbpJki/nuPba65NeUFfM7nz5/PjZ3ztSj8TQnO1JnJRGSFIhJUWSwiluUFF4rsiIAlqchS8Jy4CHVb1/06o2nt8AOz0lwdYEdSWGYM7kupeP5AIQemBlxfIhaxhDOpyCamJUzIXJ/nuRyZrcUdDRDhASLUiIih7ucsB14qzxuR+YLsIkZqDt+8cKfL4... | 2024-12-30T02:11:38 | 2024-12-30T06:16:44 | {} | MEMBER |
vuejs | core | 2,566,227,857 | 12,632 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 100 kB (**+19 B**) | 37.9 kB (**+9 B**) | 34.2 kB (**-10 B**) |
| vue.... | 2024-12-31T08:13:28 | 2024-12-31T08:13:28 | {} | NONE |
vuejs | core | 2,567,388,284 | 12,634 | Bayn-Web | See [this](https://github.com/vuejs/core/blob/5a6e98ca323ff0e50450580412694961dce5e312/packages/reactivity/src/collectionHandlers.ts#L58). Vue dropped rest of the function except `next`. | 2025-01-02T07:50:37 | 2025-01-02T07:50:37 | {} | NONE |
vuejs | core | 2,560,731,600 | 12,575 | Gwynerva | @edison1105 Why sync Comp.vue calling both setup and render? Isn't sync version is supposed to trigger parent `onErrorCaptured` which causes a component replacement just as it happens in async version? Or why async version is not calling both setup and render?
I want to show only actual error, the error in `setup`. ... | 2024-12-24T06:42:34 | 2024-12-24T07:22:17 | {} | NONE |
vuejs | core | 2,563,309,255 | 12,620 | kingyue737 | Thanks! I forgot Playground can be run in production mode. It is much easier to reproduce!
| 2024-12-27T04:44:30 | 2024-12-27T04:44:30 | {} | NONE |
vuejs | core | 2,566,066,720 | 12,629 | Doctor-wu | In the previous implementation, reactive data has an update boundary for each `createIf`, which is dropped in this PR (since we merge all reactive stuff into one createIf).
Considering this case
```vue
<h1 v-if="msg">{{ msg }}</h1>
<span v-else-if="foo">foo</span>
<span v-else-if="foo1">foo1</span>
<spa... | 2024-12-31T01:55:23 | 2024-12-31T01:55:23 | {
"eyes": 1
} | MEMBER |
vuejs | core | 2,559,265,579 | 12,575 | edison1105 | @Gwynerva
> @edison1105 Does not [seem](https://play.vuejs.org/#__SSR__eNp9U01v2zAM/SusLnaALO62ntK0wFp0WHfYiqbYyYeqNt2otSVBH04Kw/99lBynXrf1JpJPJB/J17EvWi9aj2zJVrYwQjuw6Lw+z6VotDIOOrAbXtdqe4sV9FAZ1UBCP5LTCUTJK2OUueTaeYPlW9wBeakavQ8tsmCE2gOiUNI6wJAGziY101kMv6mQIpydQ5dLGL4sWl578gESGsAQByOh4rUNjn6Wy1U28CNmZDhsdM0dkgW... | 2024-12-23T09:12:28 | 2024-12-23T09:27:33 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,561,089,728 | 12,584 | kleinfreund | > I think it's author's responsiblity to reflect property to attribute in custom elements if they want to use both property and attribute
While it's the custom element author's responsibility to handle how IDL and content attributes reflect each other in the CE, there can be no argument about whether it's legitimate ... | 2024-12-24T12:43:55 | 2024-12-24T12:43:55 | {} | CONTRIBUTOR |
vuejs | core | 2,561,649,565 | 12,607 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/12490150059)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/12489583301) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci... | 2024-12-25T06:23:18 | 2024-12-25T06:23:18 | {} | CONTRIBUTOR |
vuejs | core | 2,567,541,068 | 12,634 | edison1105 | duplicate of https://github.com/vuejs/core/issues/12615 | 2025-01-02T10:15:31 | 2025-01-02T10:15:31 | {} | MEMBER |
vuejs | core | 2,567,570,252 | 12,570 | johnsoncodehk | /ecosystem-ci run | 2025-01-02T10:39:04 | 2025-01-02T10:39:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,558,817,215 | 12,598 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-23T03:07:34 | 2024-12-23T03:07:34 | {} | NONE |
vuejs | core | 2,558,833,111 | 12,600 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-23T03:25:32 | 2024-12-23T03:25:32 | {} | NONE |
vuejs | core | 2,558,818,147 | 12,599 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/9f62cfd9-ecf3-4c52-ab15-4200f33329c3)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12599
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-23T03:08:31 | 2024-12-23T03:08:31 | {} | NONE |
vuejs | core | 2,526,570,681 | 12,511 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-09T01:02:16 | 2024-12-23T03:17:36 | {} | NONE |
vuejs | core | 2,560,797,201 | 12,575 | Gwynerva | I will investigate this and let you know. Thank you!
With your PR this issue can be considered solved I guess. | 2024-12-24T07:55:40 | 2024-12-24T07:55:58 | {
"+1": 1
} | NONE |
vuejs | core | 2,561,414,060 | 12,349 | nin-jin | Guys, you are doing it wrong. Your microbenchmarks are executed on unrealistic cases. As a result, you are sharpening your implementations for benchmarks, which **in real applications leads to performance degradation**. In particular, both the
this implementation and your previous one cannot cut off equivalent chang... | 2024-12-24T20:44:35 | 2024-12-24T21:32:36 | {
"+1": 2,
"eyes": 1,
"heart": 4,
"rocket": 1
} | NONE |
vuejs | core | 2,561,878,439 | 12,575 | edison1105 | > Does this mean there are no ways to do component replacement in parent when async child throws with Suspense + SSR?
I think so. | 2024-12-25T12:50:20 | 2024-12-25T12:50:20 | {} | MEMBER |
vuejs | core | 2,566,216,635 | 12,631 | edison1105 | a workaround: use `watch` instead. | 2024-12-31T07:55:09 | 2024-12-31T07:55:09 | {} | MEMBER |
vuejs | core | 2,559,041,436 | 12,575 | edison1105 | @Gwynerva
If possible, you can throw the exception in `onServePrefetch`, it will be correctly handed. | 2024-12-23T07:06:56 | 2024-12-23T07:06:56 | {} | MEMBER |
vuejs | core | 2,559,879,014 | 12,520 | Gwynerva | So for now this issue covers three problems:
1. Using `<component :is=".." v-html="..." />` in SSR [[link]](https://github.com/vuejs/core/issues/12520#issue-2729549865)
2. Using `h`-created VNodes directly as tags without wrapping them with `<component :is=".." />` in SSR [[link]](https://github.com/vuejs/core/issu... | 2024-12-23T15:11:58 | 2024-12-23T15:12:34 | {} | NONE |
vuejs | core | 2,560,815,297 | 12,456 | edison1105 | This is the expected behavior. It is not recommended to add `style` or `script` tags in the template. | 2024-12-24T08:13:11 | 2024-12-24T08:13:11 | {} | MEMBER |
vuejs | core | 2,560,864,691 | 12,584 | lejunyang | For custom elements, I think current modern frameworks share a common sense of assigning the data as property other than attribute, if that property exists on the element.
I can see React does this too for your [demo](https://codesandbox.io/p/sandbox/react-dev-forked-9ynfn2?file=%2Fsrc%2FApp.js%3A8%2C2)
We can also c... | 2024-12-24T09:01:26 | 2024-12-24T09:04:28 | {
"+1": 2,
"-1": 1
} | CONTRIBUTOR |
vuejs | core | 2,561,027,355 | 12,605 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/cb58ea84-7a91-4080-b14e-a86f892593f4)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12605
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-24T11:39:45 | 2024-12-24T13:37:34 | {} | NONE |
vuejs | core | 2,563,430,649 | 12,623 | edison1105 | this is the expected behavior. see https://vuejs.org/api/sfc-css-features.html#child-component-root-elements
| 2024-12-27T07:57:32 | 2024-12-27T07:57:32 | {
"-1": 1
} | MEMBER |
vuejs | core | 2,567,578,596 | 12,570 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/12581146825)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/12567376952) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci... | 2025-01-02T10:46:01 | 2025-01-02T10:46:01 | {} | CONTRIBUTOR |
vuejs | core | 2,558,812,548 | 12,596 | edison1105 | https://issues.chromium.org/issues/342247579
This bug appeared only after Chrome v125. Try using v124. Additionally, there are other memory leaks after v129. [This one](https://issues.chromium.org/issues/376777343) is also quite serious. We can't avoid it, and using an older version is the only solution. | 2024-12-23T03:02:26 | 2024-12-23T03:02:26 | {} | MEMBER |
vuejs | core | 2,558,817,916 | 12,599 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.... | 2024-12-23T03:08:17 | 2024-12-23T03:08:17 | {} | NONE |
vuejs | core | 2,558,742,502 | 12,584 | edison1105 | use the `^` prefix to set the property as an attribute.
```vue
<aa-bb ^name="111" age="22"></aa-bb>
```
see [Playground](https://play.vuejs.org/#eNqNU91q1UAQfpVxvfAc6PmvpcTTQi0FFauivVyEPcmcZNvNbshuTltKQRQp+giCUL30whsVER9Hq+1bOJuctKFKEXKR+ebbb+abnT1ga1nWnRXIAja2YS4zBxZdka1yHSphLWzurxfWmXRDYYraAe451JGFO1ub92vsgGuA0Gj... | 2024-12-23T01:45:21 | 2024-12-23T10:01:07 | {} | MEMBER |
vuejs | core | 2,559,037,771 | 12,601 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-23T07:03:48 | 2024-12-23T14:01:43 | {} | NONE |
vuejs | core | 2,559,864,302 | 12,591 | cernymatej | imho, it would be nice to tree-shake it on the Vue side | 2024-12-23T15:03:15 | 2024-12-23T15:03:15 | {} | CONTRIBUTOR |
vuejs | core | 2,560,794,873 | 12,575 | edison1105 | @Gwynerva
[This hydration mismatch](https://github.com/vuejs/core/issues/12520#issuecomment-2559070207) is not necessarily the same as yours. This bug is actually an edge case; if the tag is not p, there will be no issue.
if the tag is not a p, it will work as expected.[see](https://play.vuejs.org/#__SSR__eNp9Uk1v... | 2024-12-24T07:53:08 | 2024-12-24T07:53:08 | {} | MEMBER |
vuejs | core | 2,561,469,203 | 12,349 | johnsoncodehk | Hi @nin-jin 👋, I don't know how to use the website so can't test it, but this problem we think needs to be avoided by developers, #9497 is the PR for this.
In fact, alien-signals has an equalityComputed API under the unstable namespace that can return the results you expect and you can take a try.
But anyway, th... | 2024-12-24T22:04:27 | 2024-12-24T22:06:37 | {
"+1": 6,
"confused": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.