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,483,169,986 | 12,412 | edison1105 | I think this usage is not quite right. Vue adds many private properties to custom elements. You can't continue to use the element that has been removed from the DOM tree. because the private properties still on the element will cause some edge cases. You should add a new custom element instead. | 2024-11-18T14:16:22 | 2024-11-18T14:16:22 | {
"-1": 1
} | MEMBER |
vuejs | core | 2,482,080,101 | 12,413 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 100 kB (**+222 B**) | 38 kB (**+79 B**) | 34.3 kB (**+90 B**) |
... | 2024-11-18T06:40:14 | 2024-11-19T03:20:26 | {} | NONE |
vuejs | core | 2,477,849,228 | 12,190 | yyx990803 | Sorry, didn't realize this PR was pointing at #12181 when I merged it. Manually landed in 54812eaca | 2024-11-15T02:51:08 | 2024-11-15T02:51:08 | {} | MEMBER |
vuejs | core | 2,481,833,451 | 12,396 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/1b62b45d-3191-4256-9dbf-8a0856d054d0)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12396
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-18T02:53:29 | 2024-11-18T03:01:45 | {} | NONE |
vuejs | core | 2,482,419,641 | 12,427 | edison1105 | ~~It works fine with v3.5.13, see [Playground](https://play.vuejs.org/#eNqNU02P0zAQ/SuDL06lkFIVLqWtFlAl4LCgXSQOGKE0naRZHDvyR7ZSlP/O2GH7IaGylyh+7/n5zYzds3dtm3Ue2YItbWHq1oFF59u1UHXTauOgB4NlSp+8cHWHKTh9F4DH3BX7TVli4QgzdVWhIWKA0ugGOHlyoYQqtLIOGlvBKhgl/CNKqeG7NnL3gk9OklKbJmrGc5IevEWzoPOxyWu5gB88v8mzQjc8Bb692cbfnzDAMHl7soniW... | 2024-11-18T09:35:57 | 2024-11-18T12:55:47 | {
"+1": 1,
"eyes": 1,
"heart": 1,
"laugh": 1
} | MEMBER |
vuejs | core | 2,483,501,018 | 5,914 | dgautsch | @yyx990803 Is this change ready to be merged? We have a number of async mounted calls in our options API and would love to have these changes in place. It's a large codebase with a lot of legacy components that can't be readily converted to composition API. Thanks so much. | 2024-11-18T16:15:37 | 2024-11-18T16:15:37 | {} | NONE |
vuejs | core | 2,484,643,271 | 12,413 | lejunyang | Oh, I forgot to run e2e tests in my local, my bad. I can see it's from `_parseSlots`, child custom element is removed and unmounted... let me see how to handle this | 2024-11-19T03:42:02 | 2024-11-19T03:42:02 | {} | CONTRIBUTOR |
vuejs | core | 2,485,014,803 | 7,672 | edison1105 | The origin issue can no longer be reproduced in the playground with the latest version.
@Csszabi98
Please create a new issue with a minimal reproduction if it still not working in your application. | 2024-11-19T08:26:02 | 2024-11-19T08:26:02 | {} | MEMBER |
vuejs | core | 2,485,099,912 | 7,578 | edison1105 | a workaround: convert boolean value to string, see [Playground](https://play.vuejs.org/#eNp9kTFPwzAQhf/KyUtaUSUDTCWtBKgDDICADTNEyTVxSWzLdkKkKP+dc6wEBujme/dO77vzwG60jrsW2ZalNjdCO7DoWr3nUjRaGQdDNcLRqAYiskVccpkraR3cqUbDDgYuIYys1qEAMFQaCSTs9lCtokJ00QbenWnxIoo+1tfeNm64HLlMkxBLgVQ4bHSdOaQKIPURCT3TZNHZhjlLAEdRxierJHFPoZzlZBY1... | 2024-11-19T09:05:33 | 2024-11-19T09:05:33 | {} | MEMBER |
vuejs | core | 2,487,833,187 | 12,442 | edison1105 | The `isRenderableAttrValue` should be applied here to filter values, aligning with SSR behavior.
https://github.com/vuejs/core/blob/c4312f9c715c131a09e552ba46e9beb4b36d55e6/packages/runtime-dom/src/helpers/useCssVars.ts#L97
| 2024-11-20T08:09:44 | 2024-11-20T08:09:44 | {} | MEMBER |
vuejs | core | 2,415,562,935 | 12,182 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/16f48b00-c114-4dc9-b571-2fa56237dd1c)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12182
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-10-16T01:52:30 | 2024-11-15T02:37:37 | {} | NONE |
vuejs | core | 2,477,845,730 | 12,343 | yyx990803 | This widens the type constraint for the interface, but I think it's worth it.
If the user writes something like
```ts
interface Emits {
bar: 1 // !!!!
}
```
Now it will be allowed, but the `emit` function will expect `...args` to be of type `1`, which will never be satisfied, so that serves as a safeguard ag... | 2024-11-15T02:46:52 | 2024-11-15T02:46:52 | {} | MEMBER |
vuejs | core | 2,478,193,758 | 3,341 | bgoscinski | closing as this seems to have been implemented in https://github.com/vuejs/core/pull/9927 | 2024-11-15T08:11:16 | 2024-11-15T08:11:16 | {} | NONE |
vuejs | core | 2,481,769,727 | 12,422 | 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-11-18T01:56:38 | 2024-11-18T01:56:38 | {} | NONE |
vuejs | core | 2,481,782,272 | 12,423 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/dc385a1b-38d8-48f3-9d26-29eed18e6aee)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12423
```
</p></details>
<details><summary><b>@vue/compiler-ssr</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-18T02:09:19 | 2024-11-18T02:31:00 | {} | NONE |
vuejs | core | 2,482,377,989 | 12,428 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 100 kB (**+48 B**) | 38 kB (**+29 B**) | 34.2 kB (**+37 B**) |
| v... | 2024-11-18T09:17:58 | 2024-11-18T09:17:58 | {} | NONE |
vuejs | core | 2,484,879,589 | 8,006 | edison1105 | Closed via https://github.com/vuejs/core/pull/11350 | 2024-11-19T07:22:24 | 2024-11-19T07:22:24 | {} | MEMBER |
vuejs | core | 2,423,096,777 | 12,217 | 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-10-18T19:22:10 | 2024-11-19T15:17:27 | {} | NONE |
vuejs | core | 2,478,010,175 | 12,402 | edison1105 | very similar to #12306, I believe this is a Chrome bug.
| 2024-11-15T05:47:17 | 2024-11-15T05:47:17 | {} | MEMBER |
vuejs | core | 2,478,105,682 | 12,405 | edison1105 | @zh-lx
I think `:global(.foo) .bar` should compile to `.foo .bar[data-v-xxx]` instead of `.foo .bar`. If you want to get `.foo .bar`, write `:global(.foo .bar)`. this is the expected behavior of #12404.
https://github.com/vuejs/core/issues/10403#issuecomment-2222424619 | 2024-11-15T07:10:07 | 2024-11-15T07:15:31 | {} | MEMBER |
vuejs | core | 2,480,385,543 | 12,410 | noootwo | This issue seems to occur because the `div` generated by `v-for` is identified and wrapped inside a `STABLE_FRAGMENT`, and at this point, the `dynamicChildren` array in this vnode has a length of 0. However, when the ref `count` changes, the newly generated `vnode` contains child nodes in `dynamicChildren`. This causes... | 2024-11-16T04:07:48 | 2024-11-16T04:07:48 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,480,665,197 | 12,416 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/643f40b9-f4df-4861-a14f-6b321714931e)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12416
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-16T16:58:49 | 2024-11-16T16:58:49 | {} | NONE |
vuejs | core | 2,481,769,800 | 12,422 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/bd68c559-3d3f-4b15-933f-a86c249cf090)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12422
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-18T01:56:45 | 2024-11-18T01:56:45 | {} | NONE |
vuejs | core | 2,481,769,511 | 12,421 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/c4ac574c-6879-4590-972d-ed4ab2e25de8)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12421
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-18T01:56:21 | 2024-11-18T02:33:17 | {} | NONE |
vuejs | core | 2,482,027,268 | 12,420 | edison1105 | <s>
This PR has some performance impact on ref. The baseline is the main branch.
```text
✓ packages/reactivity/__benchmarks__/ref.bench.ts (4) 11856ms
✓ ref (4) 11854ms
name hz min max mean p75 p99 p995 p999 rme samples
· create ref 11,642,2... | 2024-11-18T06:01:26 | 2024-11-20T08:37:49 | {} | MEMBER |
vuejs | core | 2,488,144,131 | 12,444 | Kanade-Lu | ```vue
:draggable="false"
```
will work as expected | 2024-11-20T10:07:00 | 2024-11-20T10:07:26 | {} | NONE |
vuejs | core | 2,485,007,993 | 7,402 | edison1105 | The issue can no longer be reproduced using the latest version of Vue. | 2024-11-19T08:22:30 | 2024-11-19T08:22:30 | {} | MEMBER |
vuejs | core | 2,477,802,765 | 12,399 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 99.9 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.3 kB |
### Usages
| Name | Size ... | 2024-11-15T02:03:33 | 2024-11-15T14:18:54 | {} | NONE |
vuejs | core | 2,481,811,807 | 12,394 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 99.8 kB (**-239 B**) | 37.9 kB (**-59 B**) | 34.2 kB (**-48 B**)... | 2024-11-18T02:37:18 | 2024-11-18T02:37:18 | {} | NONE |
vuejs | core | 2,478,518,759 | 12,406 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 100 kB (**+15 B**) | 38 kB (**+14 B**) | 34.2 kB (**-2 B**) |
| v... | 2024-11-15T10:35:18 | 2024-11-18T05:57:38 | {} | NONE |
vuejs | core | 2,482,282,327 | 12,413 | lejunyang | @edison1105 Thanks for your suggestions! It's a good fix for current issues.
However I found another issue regarding moving element. If we move a child element directly into other element(not waiting two nextTick), its parent context is not updated
I will check more on this and update issue and commit this night | 2024-11-18T08:39:05 | 2024-11-18T08:39:26 | {} | CONTRIBUTOR |
vuejs | core | 2,482,514,184 | 12,427 | ilyary | ```
@vue/reactivity/dist/reactivity.cjs.js:1487
ref2.dep.trigger({
^
TypeError: Cannot read properties of undefined (reading 'trigger')
```
this error is printed in Node.js , when executing this piece of code in shell
Browser is silent | 2024-11-18T10:07:30 | 2024-11-18T10:07:48 | {} | NONE |
vuejs | core | 2,482,533,475 | 12,427 | ilyary | it's not only TS.
the basic cause is how `Proxy` treats properties e.g. [Proxy index gets converted to string](https://stackoverflow.com/questions/39880064/proxy-index-gets-converted-to-string) | 2024-11-18T10:12:29 | 2024-11-18T10:12:29 | {} | NONE |
vuejs | core | 2,484,946,745 | 7,909 | edison1105 | Closing as it's not a bug. | 2024-11-19T07:50:22 | 2024-11-19T07:50:22 | {} | MEMBER |
vuejs | core | 2,485,718,073 | 12,420 | skirtles-code | @edison1105 Would you be able to try that performance benchmark again?
I tried running it locally, but it seems to get stuck running `bench-compare`. It starts off OK, then it just gets stuck at 100% CPU and never completes.
I don't think my changes should impact those benchmarks. The benchmark you mentioned seem... | 2024-11-19T13:29:20 | 2024-11-19T13:29:20 | {} | CONTRIBUTOR |
vuejs | core | 2,487,077,074 | 12,439 | th1m0 | I was able to reproduce this issue in just the `App.vue` with the following code:
```vue
<template>
<p class="block" :style="{ color: '#000' }">
test
</p>
</template>
<script setup lang="ts">
import { ref } from 'vue'
const backGroundColor = ref(null)
</script>
<style scoped>
.block {
bac... | 2024-11-20T00:53:53 | 2024-11-20T00:53:53 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,487,892,553 | 12,420 | edison1105 | @skirtles-code
I tested it again. This time, I repeated step 6 above three times, and the results showed that performance was not affected. Below are the results from the third execution.
The [above test results](https://github.com/vuejs/core/pull/12420#issuecomment-2482027268) were obtained from the first time ... | 2024-11-20T08:36:48 | 2024-11-20T08:36:48 | {} | MEMBER |
vuejs | core | 2,573,328,726 | 4,098 | kleinfreund | https://github.com/vuejs/core/pull/9675 fixes the incorrect type definitions which seems to be the more immediately relevant fix. I'm running into this issue when assigning `submit` event listeners to `form` elements and using `event: SubmitEvent` in the listener's signature. | 2025-01-06T15:19:19 | 2025-01-06T15:19:19 | {} | CONTRIBUTOR |
vuejs | core | 2,579,776,361 | 12,669 | zaalbarxx | Here is the React example which does exacly the same, unmounting the actual node from the DOM, but still allowing to change the DOM in the middle of transition.
https://stackblitz.com/edit/vitejs-vite-y49udcv1?file=src%2FApp.tsx,package.json&terminal=dev
You say that it might work that way on purpose, but I don't s... | 2025-01-09T10:36:26 | 2025-01-09T10:36:26 | {
"+1": 1
} | NONE |
vuejs | core | 2,579,965,714 | 12,675 | pikax | I see, read the docs again, that's the expected usage, thanks. | 2025-01-09T11:52:20 | 2025-01-09T11:52:20 | {} | MEMBER |
vuejs | core | 2,579,985,359 | 12,669 | zaalbarxx | My proposition is to create a flag which would explicitly allow mutation of the DOM, this way it would be backward compatible with existing behavior (I guess it could potentially break some animations). Same thing was proposed in Svelte issue. Could be something like `trackChangesDuringTransition` with default of `fals... | 2025-01-09T12:01:49 | 2025-01-09T12:01:49 | {} | NONE |
vuejs | core | 2,581,613,284 | 12,677 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vapor-repl* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | e1c5980ed4b70bc99023f5b38aacfe1bcc65f903 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vapor-repl/d... | 2025-01-10T02:24:12 | 2025-01-10T06:50:21 | {} | NONE |
vuejs | core | 2,581,932,723 | 12,678 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vapor-repl* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d948c5bb8c64430a8c33d028c75c79e5460c331f |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vapor-repl/d... | 2025-01-10T07:08:19 | 2025-01-10T09:28:59 | {} | NONE |
vuejs | core | 2,582,762,355 | 12,682 | mertcb | I opened related issue at https://github.com/vitejs/vite-plugin-vue/issues/500 but nobody has replied it | 2025-01-10T13:53:47 | 2025-01-10T13:53:47 | {} | NONE |
vuejs | core | 2,585,322,297 | 12,691 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-11T16:19:04 | 2025-01-11T16:19:04 | {} | NONE |
vuejs | core | 2,573,060,623 | 12,650 | edison1105 | Removing the comment is a workaround. | 2025-01-06T12:58:07 | 2025-01-06T12:58:07 | {} | MEMBER |
vuejs | core | 2,574,425,154 | 12,643 | HUYIJUNCODING | > The configDefaults that is not used is removed.
你的这个english语法很高级 | 2025-01-07T05:32:16 | 2025-01-07T05:32:16 | {} | NONE |
vuejs | core | 2,575,743,214 | 5,860 | davidkhess | @orimay wow, I forgot about this issue. And I didn't get notified when it got a nice-to-have label.
I did some preliminary digging around in the core parser code and it definitely has the source line numbers available during compilation. Conceivably, I just need to convert that to source map format and store it with... | 2025-01-07T16:33:45 | 2025-01-07T16:33:45 | {
"heart": 1
} | NONE |
vuejs | core | 2,579,107,643 | 12,672 | wuzhibo0902 | > Kapture.2025-01-09.at.10.40.09.mp4
> Please make sure to operate in Chrome incognito mode or disable vue-devtools. After manually clicking collect garbage, the DOM nodes will be reclaimed, which is not a memory leak.
I found that the js heap size did not increase, perhaps Chrome's counting of the number of dom n... | 2025-01-09T03:24:27 | 2025-01-09T03:24:27 | {} | NONE |
vuejs | core | 2,579,468,815 | 12,676 | jh-leong | /ecosystem-ci run | 2025-01-09T08:48:11 | 2025-01-09T08:48:11 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,579,269,948 | 12,675 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/75dbc2b5-c75b-41f0-a64b-40b89f5105ae)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12675
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-01-09T06:28:05 | 2025-01-09T09:14:46 | {} | NONE |
vuejs | core | 2,579,977,528 | 12,675 | teleskop150750 | @pikax I understand that perfectly well. But there is no typing for this, for `h`, `v-bind` and `jsx`
| 2025-01-09T11:57:57 | 2025-01-09T12:10:41 | {} | NONE |
vuejs | core | 2,585,383,359 | 12,693 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/777bed6d-b40b-4aca-b631-a80dec9a5d7f)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12693
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-01-11T19:26:48 | 2025-01-11T19:37:33 | {} | NONE |
vuejs | core | 2,585,846,296 | 12,570 | johnsoncodehk | /ecosystem-ci run | 2025-01-12T17:40:16 | 2025-01-12T17:40:16 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,575,240,681 | 12,620 | edison1105 | @noootwo
> I do some research, I set a breakpoint during unimport initialization, but it never reached the breakpoint before the program crashed.
This is the exact reason for the problem. `unimport` should automatically import ref before the Vue code compilation, but it does not. Maybe it's `enforce` should be `pr... | 2025-01-07T12:58:51 | 2025-01-07T12:59:43 | {} | MEMBER |
vuejs | core | 2,579,269,698 | 12,675 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-09T06:27:50 | 2025-01-09T06:27:50 | {} | NONE |
vuejs | core | 2,579,957,335 | 12,675 | teleskop150750 | @pikax
Due to the poor naming there is confusion about how certain modifiers should be used.
This solves the problem with types [comment](https://github.com/vuejs/babel-plugin-jsx/issues/714#issuecomment-2177063570) | 2025-01-09T11:48:18 | 2025-01-09T11:48:43 | {} | NONE |
vuejs | core | 2,580,034,898 | 12,670 | edison1105 | To make `'onUpdate:props': (newProps: Record<string, any>) =>` work, the following changes are necessary:
```js
// MyButton.vue
const emit = defineEmits<{
// changes to `update:props`
'onUpdate:props': [props: Record<string, any>];
}>();
``` | 2025-01-09T12:27:40 | 2025-01-09T12:27:40 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,582,632,362 | 12,570 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed. **[Why did it fail? →](https://app.netlify.com/sites/vue-sfc-playground/deploys/6781158f6eac2d00082d1217?deploy_diagnostics=true)**
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ... | 2025-01-10T12:46:00 | 2025-01-10T12:46:00 | {} | NONE |
vuejs | core | 2,564,941,409 | 12,628 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/cc49fa47-30e2-4ce3-b605-795646af85fa)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12628
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-30T01:41:40 | 2025-01-11T16:16:22 | {} | NONE |
vuejs | core | 2,585,321,558 | 12,685 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-11T16:16:33 | 2025-01-11T16:16:33 | {} | NONE |
vuejs | core | 2,585,322,312 | 12,690 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-11T16:19:07 | 2025-01-11T16:19:07 | {} | NONE |
vuejs | core | 2,586,013,061 | 12,694 | edison1105 | Thanks for your contribution, but this change has slowed down the code. see https://jsbench.me/ntm5uccvi4/1 | 2025-01-13T01:07:55 | 2025-01-13T01:07:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,572,219,377 | 12,649 | edison1105 | Could you please add a test case for this PR? | 2025-01-06T03:42:32 | 2025-01-06T03:42:32 | {} | MEMBER |
vuejs | core | 2,574,015,325 | 12,652 | markrian | I have attempted a fix with https://github.com/vuejs/core/pull/12654. | 2025-01-06T22:10:35 | 2025-01-06T22:10:51 | {} | CONTRIBUTOR |
vuejs | core | 2,579,390,721 | 12,676 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-09T08:04:28 | 2025-01-09T08:04:28 | {} | NONE |
vuejs | core | 2,581,500,048 | 12,630 | edison1105 | @seperez-ncl
the reproduction link shows page not found when opened
| 2025-01-10T00:27:17 | 2025-01-10T00:27:17 | {} | MEMBER |
vuejs | core | 2,585,322,209 | 12,687 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-11T16:18:47 | 2025-01-11T16:18:47 | {} | NONE |
vuejs | core | 2,573,020,870 | 12,650 | linzhe141 | It is similar to this https://github.com/vuejs/core/issues/10747 | 2025-01-06T12:32:49 | 2025-01-06T12:32:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,574,329,638 | 12,656 | edison1105 | Please follow the issue requirement and provide a minimal runnable reproduction.
try the latest versions of `vue`,`@vue/compat`,`vuex` | 2025-01-07T03:37:31 | 2025-01-07T03:37:31 | {} | MEMBER |
vuejs | core | 2,575,099,484 | 5,860 | orimay | This would've been really useful! I can't count the times I was struggling from finding the exact line that has causes an error in template! Absolute must have! Just came here to create the same issue. Hope this change lands soon!
@davidkhess, since it's marked as nice-to-have, will you contribute? | 2025-01-07T11:54:21 | 2025-01-07T11:54:21 | {
"+1": 1
} | NONE |
vuejs | core | 2,576,494,715 | 12,575 | edison1105 | @Gwynerva
> Now to business. It seems the approach of "component replacement in parent when error in child" fails not only with SSR, but even on client side with deep Suspense. I don't know if this is expected, but Vue shows strange error.
[Example](https://deploy-preview-12601--vue-sfc-playground.netlify.app/#eNp9V... | 2025-01-08T00:49:29 | 2025-01-08T00:49:29 | {
"+1": 2,
"eyes": 1
} | MEMBER |
vuejs | core | 2,586,003,107 | 12,695 | edison1105 | @axlrommel
Thanks for your contribution. Is there more information about SonarGit? We can't see the dashboard content or the actual effects right now. | 2025-01-13T00:50:41 | 2025-01-13T00:50:41 | {} | MEMBER |
vuejs | core | 2,571,765,123 | 5,472 | geferon | Would be nice to have these methods expose for other libraries to use... | 2025-01-05T22:03:51 | 2025-01-05T22:03:51 | {} | NONE |
vuejs | core | 2,573,485,828 | 12,630 | canciodev | Hello @edison1105 ,
Thank you for looking into this. I understand that you were unable to reproduce the issue using the defineCustomElement function. However, in our case, we are extending the VueElement class directly in order to inject global styles into the web component something that should, in theory, work sim... | 2025-01-06T16:40:43 | 2025-01-06T16:40:43 | {} | NONE |
vuejs | core | 2,578,971,205 | 12,670 | edison1105 | Could you please provide a minimal reproduction via [stackblitz](https://stackblitz.com/github/nuxt/starter/tree/v3?file=README.md) ? | 2025-01-09T00:49:30 | 2025-01-09T00:49:30 | {} | MEMBER |
vuejs | core | 2,579,378,251 | 12,669 | zaalbarxx | @edison1105
Ok, I created some example more in line with the behavior I'd expect. It is here:
https://codepen.io/zaalbarxx/pen/KKbNwOG
I'm still not quite sure how the statement above
> <Transition> for applying animations when an element or component is entering and leaving the DOM.
actually exclude the beha... | 2025-01-09T07:56:26 | 2025-01-09T07:59:45 | {} | NONE |
vuejs | core | 2,582,628,183 | 12,570 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed. **[Why did it fail? →](https://app.netlify.com/sites/vue-sfc-playground/deploys/67811506e55cdc000821fc30?deploy_diagnostics=true)**
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ... | 2025-01-10T12:43:36 | 2025-01-10T12:43:36 | {} | NONE |
vuejs | core | 2,585,322,358 | 12,692 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-11T16:19:19 | 2025-01-11T16:19:19 | {} | NONE |
vuejs | core | 2,585,386,083 | 12,681 | ferferga | Interestingly enough, the callback runs on the `watch` exported by `@vue/reactivity`. See the checks of the linked PR. | 2025-01-11T19:37:29 | 2025-01-11T19:37:29 | {} | CONTRIBUTOR |
vuejs | core | 2,585,987,499 | 12,696 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-13T00:24:51 | 2025-01-13T00:24:51 | {} | NONE |
vuejs | core | 2,571,672,812 | 12,403 | dariasavinova | this behavior is likely caused by type handling in the Monaco Editor, which is used in the playground
here're some screenshots of how types look in hints in the playground of the [Editor repo](https://github.com/imguolao/monaco-vue)
<img width="361" alt="monaco editor example" src="https://github.com/user-attachments... | 2025-01-05T16:01:59 | 2025-01-05T16:26:14 | {} | NONE |
vuejs | core | 2,577,133,800 | 12,664 | edison1105 | Please provide a reproducible repository.
| 2025-01-08T08:59:31 | 2025-01-08T08:59:31 | {} | MEMBER |
vuejs | core | 2,579,069,865 | 12,672 | edison1105 | ERROR: type should be string, got "\r\nhttps://github.com/user-attachments/assets/185f7848-11e5-45fb-bc5d-2c5908fcf4f2\r\n\r\nPlease make sure to operate in Chrome incognito mode or disable vue-devtools.\r\nAfter manually clicking collect garbage, the DOM nodes will be reclaimed, which is not a memory leak." | 2025-01-09T02:45:20 | 2025-01-09T02:45:20 | {} | MEMBER |
vuejs | core | 2,579,423,130 | 12,675 | jh-leong | /ecosystem-ci run | 2025-01-09T08:23:30 | 2025-01-09T08:23:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,564,941,390 | 12,627 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/cb530859-2071-4107-a699-6fdb20fd872b)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12627
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-30T01:41:37 | 2025-01-11T16:16:38 | {} | NONE |
vuejs | core | 2,585,322,351 | 12,691 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/b81bd416-715f-4464-962a-47e1b70140c4)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12691
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-01-11T16:19:18 | 2025-01-11T16:19:18 | {} | NONE |
vuejs | core | 2,585,764,617 | 12,681 | ferferga | @edison1105 @skirtles-code Is there any reason/something I'm missing of why the watcher's callback doesn't run inside the effect scope of the component by default?
Wouldn't wrapping all the calls to the callback like this:
```
scope.run(() => cb)
```
Be a good solution?
And yes, a warning is printed in DE... | 2025-01-12T14:51:50 | 2025-01-12T14:58:01 | {} | CONTRIBUTOR |
vuejs | core | 2,579,590,023 | 12,669 | edison1105 | >I mean, is there an actual reason why Vue would not want this to behave like this ? I don't see any drawback of such thing and it would add a little bit of flexibility regarding transitions/animations without relying on JS and intermediate variables to apply between the transition.
This design might be intended to:... | 2025-01-09T09:36:59 | 2025-01-09T09:36:59 | {} | MEMBER |
vuejs | core | 2,579,981,593 | 12,675 | pikax | @teleskop150750 apologies, what I meant is: "after reading the docs again, capture is only supported by appending *Capture to the ending of the event name, so this PR will fix the issue that is linked" | 2025-01-09T12:00:00 | 2025-01-09T12:00:00 | {} | MEMBER |
vuejs | core | 2,582,622,366 | 12,570 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed. **[Why did it fail? →](https://app.netlify.com/sites/vue-sfc-playground/deploys/678114c9689d8d0008b51d75?deploy_diagnostics=true)**
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ... | 2025-01-10T12:40:31 | 2025-01-10T12:40:31 | {} | NONE |
vuejs | core | 2,585,322,302 | 12,689 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2025-01-11T16:19:04 | 2025-01-11T16:19:04 | {} | NONE |
vuejs | core | 2,577,181,060 | 12,664 | hlxvi | > Please provide a reproducible repository.
<script setup lang="ts">
import { defineModel } from 'vue'
interface JoinInfo{
uid:number,
type_id:number
}
let joinInfos = defineModel<JoinInfo[]>()
joinInfos.value = [ {
"uid":1,
"type_id":1,
},
{
"uid":2,
"type_id":2,
},
{
... | 2025-01-08T09:21:23 | 2025-01-08T09:21:23 | {} | NONE |
vuejs | core | 2,585,992,729 | 12,681 | edison1105 | > Is there any reason/something I'm missing of why the watcher's callback doesn't run inside the effect scope of the component by default?
There is no need to track dependencies inside watch callback calls, so the watcher's callback doesn't run inside an effect scope. `onScopeDispose` should be placed inside the set... | 2025-01-13T00:32:51 | 2025-01-13T00:32:51 | {} | MEMBER |
vuejs | core | 2,578,960,977 | 12,669 | edison1105 | This is by design. For `Transition` triggered by `v-if`, there will be no patch when the element leaves.
> `<Transition>` for applying animations when an element or component is entering and leaving the DOM.
The elements inside `Transition` enter and leave when `showNext` changes.
[codepen.io/zaalbarxx/pen/PwY... | 2025-01-09T00:41:50 | 2025-01-10T00:46:15 | {} | MEMBER |
vuejs | core | 2,585,345,467 | 12,681 | xfontr | I don't have a specific solution for this but yes hopefully a debugging hint.
The immediate watcher is triggered even before the component is created. After that, the component is created. Once that happens, the non-immedate watcher is triggered. I assume that the fact this happens later affects the onScopeDispose a... | 2025-01-11T17:13:03 | 2025-01-11T17:39:59 | {
"heart": 1
} | NONE |
vuejs | core | 2,586,395,849 | 12,680 | markbrockhoff | > Having said all that, though... From a dev's POV I would agree that it would make more sense if the comment was simply ignored.
Exactly, if there were two actual element inside the root of the template I'd totally agree and expect the issue. However having Vue respect a comment as part of the Fragment feels unintu... | 2025-01-13T07:34:45 | 2025-01-13T07:34:45 | {} | NONE |
vuejs | core | 2,577,961,861 | 12,630 | canciodev | I was able to reproduce the issue, and it turns out it specifically occurs when the component used to register the custom element is compiled with the customElement property during the build process.
https://codesandbox.io/p/live/442d0220-8af3-45b5-b2ed-2ab21cf088d8
![Screenshot 2025-01-08 at 10 07 52 AM](https://git... | 2025-01-08T15:29:47 | 2025-01-08T15:29:47 | {
"+1": 1
} | NONE |
vuejs | core | 2,579,391,071 | 12,676 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/3b2530ed-8f18-498b-9e1c-1a2f7eace53b)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12676
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-01-09T08:04:41 | 2025-01-09T08:04:41 | {} | NONE |
vuejs | core | 2,544,425,091 | 12,560 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/c3a2ccaf-743b-4b2e-bad3-4fba3920b314)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12560
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-16T02:44:59 | 2025-01-11T16:17:36 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.