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,527,337,533 | 12,194 | fuyoo | 同样的问题 | 2024-12-09T09:09:02 | 2024-12-09T09:09:02 | {} | NONE |
vuejs | core | 2,527,691,179 | 12,508 | madogiwa0124 | @KazariEX @edison1105
Thank you for your comment!
I now understand that the design is effective only when directly deconstructing defineProps.
I got it!😄 | 2024-12-09T11:44:14 | 2024-12-09T11:44:14 | {} | NONE |
vuejs | core | 2,528,714,683 | 12,461 | adamdehaven | @edison1105 is there anything else myself or @Justineo can provide here to help this PR along?
I have a workaround in my project in a draft PR; however, it's definitely "messy" requiring me to manually inject `initial` all over the place in my userland code. | 2024-12-09T16:54:52 | 2024-12-09T16:54:52 | {} | NONE |
vuejs | core | 2,511,305,647 | 12,494 | yangxiuxiu1115 | hydrate方法只会在ssr模式下才会调用
[playground](https://play.vuejs.org/#__PROD____SSR__eNp9VF1r01AY/ivH3DSF2iJ6VetgakEFnWwDb3KxkJy22U5OwslJt1IClX2UjU1vHIpuUkFhDnS7mKM66/5Mk3ZX/gXfk6Rpu9UlIZzzvM95v99Tl6ZtO1t1sZSXCo7GDJsjB3PXnlKoYdoW46iu45JB8bRTo9oDCzCKKc+gCB0BTJUtzarLGcRwyUMlZplIkUCzIt1VqHg1izocmU4Z3RMcOfUIE2KhFxYj+o1UepTEVWcpUR3T... | 2024-12-02T11:41:19 | 2024-12-02T11:41:19 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,511,477,638 | 12,495 | FreeLiC | I think it should be modified like this, but I don't know if it is correct?
| 2024-12-02T12:59:41 | 2024-12-02T12:59:41 | {} | NONE |
vuejs | core | 2,522,280,348 | 12,502 | edison1105 | I think this is an issue with happy-dom because this is no such warning in the browser.
see [Playground](https://play.vuejs.org/#eNp9UstOwzAQ/JVoz1VzgFMVKgGqBBwAAeLkS5osiYtjW/a6BFX5d/xo0iBBb7Mzs+PZKAe41nq5dwgrKGxluKbMIjm9ZrLIE+GhHwg7LUpCP2VZQeVWJBiGFsv6OITRTDiKGa+vGAQPGgbruwiKnNrTSj7tBD6ljeFbVX//G15nKdfOX3gvhUMfNOv064... | 2024-12-06T07:01:31 | 2024-12-06T07:01:31 | {} | MEMBER |
vuejs | core | 2,525,382,236 | 12,507 | Justineo | Creating an appropriate benchmark is quite complex. I attempted a slightly more complex one. During testing, 100 strings of lengths ranging from 3 to 100 are randomly generated, and they may or may not include characters that need escaping. As a comparison, I also added an implementation that uses regular expressions e... | 2024-12-08T02:12:43 | 2024-12-08T02:12:43 | {} | MEMBER |
vuejs | core | 2,527,368,602 | 12,514 | 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-09T09:22:12 | 2024-12-09T09:22:12 | {} | NONE |
vuejs | core | 2,505,904,658 | 12,349 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/12067980777)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/12044045075) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci... | 2024-11-28T11:33:10 | 2024-11-28T11:33:10 | {} | CONTRIBUTOR |
vuejs | core | 2,507,142,658 | 12,461 | skirtles-code | TLDR: I think the latest proposal looks good.
---
I wasn't initially clear about the difference between `initial` and `v-bind('"initial"')`, so I put together a Playground to help demonstrate:
- [Playground](https://play.vuejs.org/#eNqVks1OwzAQhF/FWg4FqSQHOJWABKgScAAEHH1xk23r4tiWf0Jp1XdnndDQClSJm3e/GWvGyRqurc2... | 2024-11-29T06:01:40 | 2024-11-29T06:01:40 | {
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 2,510,363,287 | 6,034 | edison1105 | Closing as it's related to vue-router | 2024-12-02T01:10:16 | 2024-12-02T01:10:16 | {} | MEMBER |
vuejs | core | 2,515,237,738 | 12,494 | Muspcn | 
> 可以监听组件内部的onMounted事件
我是需要这样的需求，因为不确定组件的数量/降低加载时间，需要通过异步加载组件，从而调用组件的方法进行编辑数据，现在清楚组件异步加载状态，只能通过延时执行调用open方法，这种的生产中怕遇到问题，不知道有没有其他的办法 | 2024-12-03T17:57:03 | 2024-12-03T17:57:03 | {} | NONE |
vuejs | core | 2,518,902,555 | 12,491 | edison1105 | > Use Map rather than Object, this is about 30% faster.
I got different performance data, see https://measurethat.net/Benchmarks/Show/32894/1/test-map-vs-object | 2024-12-05T01:40:39 | 2024-12-05T01:40:39 | {} | MEMBER |
vuejs | core | 2,529,974,258 | 12,498 | edison1105 | Not sure if this will be fix since https://github.com/vuejs/core/issues/6142#issuecomment-1311364361 | 2024-12-10T01:24:08 | 2024-12-10T01:24:08 | {} | MEMBER |
vuejs | core | 2,505,909,704 | 12,349 | johnsoncodehk | /ecosystem-ci run | 2024-11-28T11:35:48 | 2024-11-28T11:35:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,505,978,920 | 12,349 | johnsoncodehk | PR is now based on alien-signals 0.4.4, due to the implementation of some new fast paths (e.g. https://github.com/stackblitz/alien-signals/pull/7), which gets more performance improvements compared to 0.3.2.
Benchmark result (baseline is https://github.com/vuejs/core/pull/12349/commits/f15e9d72c0ebffc2ba3015e1086ba7... | 2024-11-28T12:13:33 | 2024-11-28T12:13:33 | {
"+1": 5,
"heart": 2,
"hooray": 1,
"rocket": 16
} | MEMBER |
vuejs | core | 2,465,979,603 | 12,349 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/acc85245-c853-497f-ad9c-fbd2c5e24a63)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12349
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-11-09T01:45:49 | 2024-11-28T13:14:52 | {} | NONE |
vuejs | core | 2,510,361,020 | 6,035 | edison1105 | The behavior you encountered is a known limitation of how Vue handles reactive arrays and proxies.
As a workaround, you can manually convert the proxied objects back to raw objects before performing operations like .indexOf. | 2024-12-02T01:07:07 | 2024-12-02T01:07:07 | {} | MEMBER |
vuejs | core | 2,518,883,980 | 12,491 | edison1105 | /ecosystem-ci run | 2024-12-05T01:22:09 | 2024-12-05T01:22:09 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,293,986,749 | 11,569 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/471a00c7-5bbe-488b-97f0-30be84fe741f)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@11569
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-08-16T18:43:12 | 2024-12-05T21:58:41 | {} | NONE |
vuejs | core | 2,526,176,650 | 12,508 | KazariEX | The original intention of the design of "Reactive Props Destructure" was to replace `withDefaults`, it only takes effect when directly deconstructing the return value of `defineProps`. | 2024-12-08T15:15:06 | 2024-12-08T15:15:06 | {} | MEMBER |
vuejs | core | 2,526,696,934 | 12,507 | edison1105 | LGTM.
Here is the bench result on Node v22.7.0, and indeed, the performance has improved with this PR.
```
✓ src/__benchmarks__/escapeHtml.bench.js (3) 1815ms
✓ escapeHtml (3) 1813ms
name hz min max mean p75 p99 p995 p999 rme samples
· PR #12507 5,661.77 ... | 2024-12-09T02:53:09 | 2024-12-09T02:53:09 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,518,978,304 | 12,220 | jacksongross | I am seeing the same, even without generics. The workaround I found so far is to define the emits with the regular type-based syntax as [per the docs](https://vuejs.org/guide/typescript/composition-api.html#typing-component-emits), so in your case would be:
```ts
defineEmits<{
(e: 'update:modelValue': items: U... | 2024-12-05T02:54:54 | 2024-12-05T02:54:54 | {} | NONE |
vuejs | core | 2,526,591,626 | 12,459 | edison1105 | @lazytong-tech
Thank you for providing the reproduction, it indeed replicates the issue you described. However, the code cannot be downloaded, and I would like to debug it locally to see what the input parameters are. | 2024-12-09T01:28:37 | 2024-12-09T01:28:37 | {} | MEMBER |
vuejs | core | 2,526,698,168 | 12,507 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/184627a5-ca5e-4ce4-bba9-6a78a8be8390)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12507
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-09T02:54:24 | 2024-12-09T02:54:24 | {} | NONE |
vuejs | core | 2,505,616,108 | 12,483 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | -------------------- | -------------------- |
| runtime-dom.global.prod.js | 101 kB (**+729 B**) | 38.1 kB (**+119 B**) | 34.3 kB (**+80 B*... | 2024-11-28T09:14:06 | 2024-11-28T10:47:11 | {} | NONE |
vuejs | core | 2,522,638,386 | 12,502 | rMonell | @edison1105 Yes because this warning only appear when running the tests.
This makes it difficult to determine the source, but on the happy-dom side, this attribute seems to be managed, with references and unit tests (https://github.com/capricorn86/happy-dom/blob/d3566f4b2d4b82b3188d7476f492894534f1cfcb/packages/hap... | 2024-12-06T09:29:57 | 2024-12-06T09:33:55 | {} | NONE |
vuejs | core | 2,525,387,101 | 12,507 | ShuiRuTian | @Justineo Thanks a lot, however it seems you named the function mistakenly, oops
In https://jsben.ch/uPxu5, `escapeHtmlHybrid` contains the changes in this PR and `escapeHtmlLoop` is current implementation.
Then the result should be explained as "This PR is faster" | 2024-12-08T02:33:07 | 2024-12-08T02:37:32 | {
"+1": 1
} | NONE |
vuejs | core | 2,526,594,223 | 12,509 | edison1105 | /ecosystem-ci run vite-plugin-vue | 2024-12-09T01:29:40 | 2024-12-09T01:29:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,526,709,205 | 12,505 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/056ace30-0d20-4f9b-95d3-747db4cd8ec5)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12505
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-09T03:06:15 | 2024-12-09T03:26:14 | {} | NONE |
vuejs | core | 2,527,822,139 | 12,515 | edison1105 | duplicate of https://github.com/vuejs/core/issues/12306
there is no memory leak without clicking the checkbox. | 2024-12-09T12:41:32 | 2024-12-09T12:41:32 | {} | MEMBER |
vuejs | core | 2,509,582,299 | 12,491 | Justineo | `instanceof` cannot work across `<iframe>` boundaries. Using `Object.prototype.toString` is a common alternative to determine the type of an object. This covers more use cases. | 2024-12-01T05:33:56 | 2024-12-01T06:01:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,510,330,590 | 12,492 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/3fbe246d-0548-448c-b818-c26f8deb1060)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12492
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-02T00:24:05 | 2024-12-04T01:49:14 | {} | NONE |
vuejs | core | 2,518,890,823 | 12,491 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/12171407380)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/12153330926) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-12-05T01:28:57 | 2024-12-05T01:28:57 | {} | CONTRIBUTOR |
vuejs | core | 2,525,245,093 | 12,496 | wang-panfeng | Sorry for replying late. I've been too busy recently because of the 996 work schedule（TOT）. The reproduced demo is here.
https://github.com/wang-panfeng/vue3-migration-problem.git | 2024-12-07T16:58:15 | 2024-12-07T16:58:15 | {} | NONE |
vuejs | core | 2,526,650,258 | 12,496 | edison1105 | Each component can have its own `compatConfig`.
## Options API
```js
export default {
name: "Vue2Vmodel",
compatConfig: {
MODE: 2,
COMPONENT_V_MODEL: true,
}
};
```
## Composition API
```js
<script>
export default {
compatConfig: {
MODE: 3,
COMPONENT_V_MODEL: false,
},
};
... | 2024-12-09T02:08:19 | 2024-12-09T02:08:19 | {} | MEMBER |
vuejs | core | 2,529,018,355 | 12,220 | KazariEX | It is not necessary to use both `defineEmits` to specify the update event for `modelValue`, as it is automatically generated.
 | 2024-12-09T18:25:15 | 2024-12-09T18:25:15 | {} | MEMBER |
vuejs | core | 2,220,557,912 | 2,460 | ssaid-sg | Is there any news on this issue? | 2024-07-10T13:48:20 | 2024-07-10T13:48:20 | {} | NONE |
vuejs | core | 2,222,422,063 | 10,436 | yyx990803 | I agree with @skirtles-code here - this change essentially makes the `:global()` work like a combinator instead of a functional pseudo class.
The combinator-like behavior of `:deep` has been deprecated for a long time and is no longer recommended, so the behavior should not apply to `:global`. | 2024-07-11T09:11:26 | 2024-07-11T09:11:26 | {} | MEMBER |
vuejs | core | 2,224,820,318 | 11,338 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB (**+92 B**) | 34.2 kB (**+18 B**) | 30.9 kB (**+15 B**) |
... | 2024-07-12T06:07:23 | 2024-07-12T06:07:23 | {} | NONE |
vuejs | core | 2,228,680,232 | 11,272 | yyx990803 | This seems to only happen in the playground, maybe due to outdated Volar used?
I can't reproduce this locally in VSCode either. | 2024-07-15T14:46:03 | 2024-07-15T14:46:03 | {} | MEMBER |
vuejs | core | 2,229,929,746 | 9,014 | yyx990803 | After the reactivity refactor that allows computed re-evaluation during SSR in 3.5 this is no longer reproducible:
https://play.vuejs.org/#__SSR__eNqtU9tu2zAM/RVBL+mA1hkW7CXLskvRhw7YBeve6mIQLCZWJkuCRGcBgvz7dIkvgV1jGPZiU+QhdSgeHukHY7J9DXRJVwiVkQxhnStCVp9B1dE62/c+TFCghLc5LXO6Xs0b97Mw+DuY/K8wPYSlozdX816T/ugKKwwSB1gb7xG... | 2024-07-16T03:24:50 | 2024-07-16T03:24:50 | {} | MEMBER |
vuejs | core | 2,229,942,835 | 7,456 | yyx990803 | This is [documented behavior](https://github.com/vuejs/docs/pull/2273/files) now - it is intentional behavior for the current version range. Whether this should change will have to wait until a major version. | 2024-07-16T03:33:16 | 2024-07-16T03:33:16 | {} | MEMBER |
vuejs | core | 2,230,456,075 | 11,258 | yyx990803 | Thanks for the PR, but this is not the right fix. The root cause is slots from `useSlots` are not reactive, but whether we want to change that behavior still needs more discussion. | 2024-07-16T09:37:06 | 2024-07-16T09:37:06 | {} | MEMBER |
vuejs | core | 2,219,820,250 | 11,319 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9870340662)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9868431556) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/987... | 2024-07-10T08:02:20 | 2024-07-10T08:02:20 | {} | CONTRIBUTOR |
vuejs | core | 2,222,224,290 | 11,244 | yyx990803 | https://github.com/vuejs/core/issues/10236#issuecomment-2222223511 | 2024-07-11T07:24:56 | 2024-07-11T07:24:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,222,481,560 | 10,066 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9889004289)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9868431556) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/988... | 2024-07-11T09:38:31 | 2024-07-11T09:38:31 | {} | CONTRIBUTOR |
vuejs | core | 2,223,230,681 | 11,331 | ChristianMurphy | > I think this has nothing to do with MDX. It works with many runtimes, and they work. Vue is choosing to warn. Duckduckgo’ing your warning seems to indicate that Vue dislikes certain h calls (https://stackoverflow.com/questions/69875273/non-function-value-encountered-for-default-slot-in-vue-3-composition-api-comp). Bu... | 2024-07-11T15:21:39 | 2024-07-11T15:21:39 | {
"+1": 1
} | NONE |
vuejs | core | 2,223,574,787 | 11,281 | MeesterDev | I guess I can understand the reasoning that it should be on top in the scoped style also, though it appears to be based on principe rather than logic. Considering the `@import` is actually replaced with the file content, the requirement isn't there anymore.
We'll copy-paste our imported css a bunch of time if you de... | 2024-07-11T18:10:32 | 2024-07-11T18:14:31 | {} | NONE |
vuejs | core | 2,225,289,163 | 11,340 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34.2 kB | 30.9 kB |
| vue.global.prod.js | 146 kB | 53.6 kB | 47.8 kB |
### Usages
| Name | Size |... | 2024-07-12T10:30:16 | 2024-07-12T14:38:43 | {} | NONE |
vuejs | core | 2,227,613,184 | 11,360 | jh-leong | Could someone please run the ecosystem-cI? Thanks! | 2024-07-15T02:35:41 | 2024-07-15T02:35:41 | {} | MEMBER |
vuejs | core | 2,220,474,635 | 11,296 | JasonGotGithub | @LinusBorg @linzhe141 Out of curiosity, what would be the process to solve this bug? | 2024-07-10T13:11:09 | 2024-07-10T13:11:09 | {} | NONE |
vuejs | core | 2,223,196,353 | 11,331 | henrikruscon | I did just that initially and they claim the issue is with Vue and not related to MDX, asking me to post the issue here instead.
https://github.com/mdx-js/mdx/issues/2512 | 2024-07-11T15:10:35 | 2024-07-11T15:13:56 | {} | NONE |
vuejs | core | 2,224,108,478 | 11,329 | skirtles-code | I believe the problem here is that you aren't waiting for the router to resolve the route before beginning hydration. As the route isn't resolved yet it's trying to render a placeholder comment instead of the intended route component.
So change:
```js
createSSRApp(App).use(router).mount('#app');
```
to:
`... | 2024-07-11T23:22:12 | 2024-07-11T23:22:12 | {} | CONTRIBUTOR |
vuejs | core | 2,225,880,732 | 9,885 | jcbond92 | Actually, after some additional investigation, this doesn't seem to work when multiple instances of a component are used in a specific view. I'll reopen the #11335 with some fixes to get the tests passing. | 2024-07-12T15:58:20 | 2024-07-12T15:58:20 | {} | NONE |
vuejs | core | 2,227,135,669 | 11,350 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.6 kB (**+24 B**) | 34.2 kB (**+12 B**) | 30.9 kB (**+43 B**) |
... | 2024-07-13T23:21:30 | 2024-07-13T23:21:30 | {} | NONE |
vuejs | core | 2,227,620,268 | 11,359 | jh-leong | Invalid reproduction, could you please provide an actual reproduction? | 2024-07-15T02:48:16 | 2024-07-15T02:48:16 | {} | MEMBER |
vuejs | core | 2,228,703,150 | 11,360 | jh-leong | > A similar issue was fixed for `ComputedRef<T>` in #8748.
>
> I think the fix should be consistent to make `MaybeRef<T>` also include `ComputedRef<T>` and remove `ComputedRef<T>` from `unref`'s argument union.
According to the test case below, `MaybeRef` seems to be writable (ref this [comment](https://github.co... | 2024-07-15T14:56:04 | 2024-07-15T14:56:04 | {} | MEMBER |
vuejs | core | 2,229,859,498 | 11,360 | yyx990803 | In this case changing `MaybeRef` seems to technically be a type-level breaking change, and we should only do it in 3.5.
For now the immediate fix for #11356 should be just adding `ShallowRef` to the `unref` argument union. | 2024-07-16T02:00:38 | 2024-07-16T02:00:38 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,229,947,566 | 8,284 | yyx990803 | Both cases are no longer reproducible in latest 3.4 and also in 3.5 alpha. | 2024-07-16T03:40:11 | 2024-07-16T03:40:11 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,230,175,666 | 8,503 | yyx990803 | Merging this as this is indeed a correctness fix and passes Ecosystem CI | 2024-07-16T07:06:44 | 2024-07-16T07:06:44 | {} | MEMBER |
vuejs | core | 2,221,975,874 | 11,296 | jh-leong | The `ref` is set to `null` when the component unmounts. Transition `leave` hooks are triggered when the element is removed.
In your example, when you click the `about` button, the process is as follows:
1. Unmount the Home component (`pageRef` is set to null)
2. Remove the Home component
3. Trigger transition `... | 2024-07-11T04:00:44 | 2024-07-11T04:00:44 | {} | MEMBER |
vuejs | core | 2,223,504,140 | 11,281 | yyx990803 | `@import` can only be placed at the root of CSS files, that's how CSS works.
https://developer.mozilla.org/en-US/docs/Web/CSS/@import
> An `@import` rule must be defined at the top of the stylesheet... or it will be ignored | 2024-07-11T17:31:33 | 2024-07-11T17:33:12 | {} | MEMBER |
vuejs | core | 2,223,513,426 | 11,270 | yyx990803 | This is not a bug. It's expected behavior. You need to unmount the rendered component tree to release memory. | 2024-07-11T17:37:48 | 2024-07-11T17:37:48 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,224,124,467 | 11,329 | rschristian | Interesting, I don't happen to see any reference to this in the docs anywhere.
Will give it a shot shortly then, I wonder if my issues with other plugins are also due to this not-quite-so-sync `.use()` impl.
Edit: That seems to solve the StackBlitz issue, though slightly more complex (not by much, still incredibl... | 2024-07-11T23:43:06 | 2024-07-12T00:00:59 | {} | NONE |
vuejs | core | 2,224,883,867 | 11,337 | edison1105 | should be `$inputRef.value.$el.tagName` | 2024-07-12T06:31:23 | 2024-07-12T06:31:23 | {} | MEMBER |
vuejs | core | 2,227,785,313 | 11,360 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9934713185)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9933951906) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/993... | 2024-07-15T06:32:42 | 2024-07-15T06:32:42 | {} | CONTRIBUTOR |
vuejs | core | 2,228,645,369 | 11,360 | yyx990803 | A similar issue was fixed for `ComputedRef<T>` in #8748
I think the fix should be consistent to make `MaybeRef<T>` also include `ComputedRef<T>` (and remove `ComputedRef<T>` from `unref`'s argument union) | 2024-07-15T14:30:08 | 2024-07-15T14:30:29 | {} | MEMBER |
vuejs | core | 2,227,611,687 | 11,360 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.6 kB | 34.2 kB | 30.9 kB |
| vue.global.prod.js | 146 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-07-15T02:33:11 | 2024-07-16T02:27:52 | {} | NONE |
vuejs | core | 2,223,684,157 | 9,885 | jcbond92 | Working on getting a pull request up to fix this, and interestingly if put a small timeout around the [initial setting of the value in `vModel.ts`](https://github.com/vuejs/core/blob/main/packages/runtime-dom/src/directives/vModel.ts#L82-L84) I see the duplication issue resolved.
```
mounted(el, { value }) {
s... | 2024-07-11T19:03:10 | 2024-07-11T19:03:10 | {} | NONE |
vuejs | core | 2,225,113,520 | 11,336 | edison1105 | maybe duplicate of https://github.com/vuejs/core/issues/7256
It works fine without vuetify, [see](https://play.vuejs.org/#__PROD__eNqNVE1v2zAM/SuELk2AOE7WYofOCdAVHbAdtmEtsIsums0k6hTJkGQnQJD/Pkr+aNylHydL5KPwHvnoA7spy2ldIbtmmcutLD049FUJSuj1gjPvOFtyLbelsR5uDX01av9b+s3NvTIeVtZs4WKahlR46OLTAD0fAOYRwXUPOYDFFRxbUFvOdW60IyI... | 2024-07-12T08:47:08 | 2024-07-12T09:40:51 | {} | MEMBER |
vuejs | core | 2,229,910,934 | 11,360 | jh-leong | > In this case changing `MaybeRef` seems to technically be a type-level breaking change, and we should only do it in 3.5.
>
> For now the immediate fix for #11356 should be just adding `ShallowRef` to the `unref` argument union.
Updated.
Based on you feedback, would it be reasonable to submit a PR to the `mino... | 2024-07-16T03:02:27 | 2024-07-16T03:19:02 | {} | MEMBER |
vuejs | core | 2,229,947,964 | 11,366 | dddssw | If three is a bug , maybe I can try to fix it | 2024-07-16T03:40:47 | 2024-07-16T03:40:47 | {} | NONE |
vuejs | core | 2,230,168,460 | 8,503 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9952159884)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9933951906) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/995... | 2024-07-16T07:02:19 | 2024-07-16T07:02:19 | {} | CONTRIBUTOR |
vuejs | core | 2,222,279,805 | 11,296 | JasonGotGithub | Hi @jh-leong, thanks for your comment.
Is this different from Vue 2? In Vue 2 refs are available in the `leave` hooks, which would then be the "opposite" from how it is now. I assume since the destroy sequence is no longer present in Vue 3, that's where the different is?
The reason for making this issue, is that... | 2024-07-11T07:57:33 | 2024-07-11T07:57:33 | {} | NONE |
vuejs | core | 2,223,511,278 | 11,253 | yyx990803 | `VUE_HMR_RUNTIME` only exists in dev mode. Make sure to only report memory leaks that happen in production mode, and make sure to provide actual reproductions.
There's nothing we can do without reproductions. | 2024-07-11T17:36:22 | 2024-07-11T17:36:22 | {} | MEMBER |
vuejs | core | 2,224,137,832 | 9,885 | jcbond92 | Ok, so I think I've settled on a better solution than making a change in [the mentioned pull request](https://github.com/vuejs/core/pull/11335). I think this can be handled on a case-by-case basis by library authors.
The solution, I came up with was to wait for `nextTick` when registering the component in the custom... | 2024-07-12T00:00:58 | 2024-07-12T00:00:58 | {} | NONE |
vuejs | core | 2,197,295,279 | 11,248 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.6 kB | 34.2 kB | 30.9 kB |
| vue.global.prod.js | 146 kB | 53.7 kB | 47.8 kB |
### Usages
| Name | Size |... | 2024-06-28T16:44:03 | 2024-07-13T17:17:07 | {} | NONE |
vuejs | core | 2,227,396,886 | 11,354 | LinusBorg | For the third watcher, the **getter** doesn't trigger because it only reads `objectRef.value`, and that didn't change - it's still returning the same object. Yes, you changed a property of that object, but that property is not being accessed in the **getter**, so it's not a dependency being tracked, and will not trigge... | 2024-07-14T16:03:39 | 2024-07-14T16:04:38 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,227,596,909 | 11,358 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34.2 kB | 30.9 kB |
| vue.global.prod.js | 146 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-07-15T02:08:54 | 2024-07-15T08:32:26 | {} | NONE |
vuejs | core | 2,229,819,149 | 5,836 | edison1105 | @renatodeleao
As you can see, `TransitionGroup` will not re-render after `items` change, so the transition is not working.
```vue
<TransitionGroup name="list" tag="ul" id="teleport-target"/>
<template v-for="item in items" :key="item">
<teleport to="#teleport-target">
<Item :key="item">{{ item... | 2024-07-16T01:38:48 | 2024-07-16T01:38:48 | {} | MEMBER |
vuejs | core | 2,222,648,543 | 11,325 | magicandskill | > @magicandskill
>
>
>
> When props are changed, the reason for the execution of the render function is because during template parsing, reading props will store the render function as a dep.
>
> As @linzhe141 said
>
> The template parsing here does not store changes to props as dependencies
>
>
>
> <img widt... | 2024-07-11T11:07:53 | 2024-07-11T12:16:08 | {} | NONE |
vuejs | core | 2,225,176,076 | 11,336 | yyx990803 | It's related to #10870, I've found the fix. Writing tests now. | 2024-07-12T09:22:06 | 2024-07-12T09:22:06 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,225,649,525 | 11,342 | LinusBorg | That's because our default value for the model prop is a nonreactive object.
https://play.vuejs.org/#eNrlVU1v2zAM/SuaL07QwFnRnTInWJd2WAesG9JhO9TF4NhM6kaRDEnOBwL/95Gy4zhfbbDThh5sWOIj9Ug+yivnMk29WQZOx/F1pJLUMA0mSxkPxbgbOEYHTi8QyTSVyrAVUzBiORspOWUuurmV6epTX+KXAGFKs9eu7dEZ7vsKPYDRPry+ucYHIpJCGzbVY9al0xvuZ+Bcsl9S8fiN2wyE... | 2024-07-12T13:59:55 | 2024-07-12T13:59:55 | {} | MEMBER |
vuejs | core | 2,224,138,575 | 11,335 | jcbond92 | ~~Found a better solution that can be implemented by library authors instead of making the change here in Vue core.~~
~~https://github.com/vuejs/core/issues/9885#issuecomment-2224137832~~
Edit: the solution I thought would fix this that we could implement in our components didn't actually work in all scenarios. U... | 2024-07-12T00:01:26 | 2024-07-12T16:00:04 | {} | NONE |
vuejs | core | 2,226,821,629 | 11,349 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.6 kB | 34.2 kB | 30.9 kB |
| vue.global.prod.js | 146 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-07-13T08:30:36 | 2024-07-13T08:30:36 | {} | NONE |
vuejs | core | 2,228,793,380 | 5,836 | renatodeleao | > Hello, could teleport support `TransitionGroup`? Now I'm doing this, but the animation didn't work
>
> ```
> <div class="pinned">
> <TransitionGroup id="id" name="animation-class">
> <TransitionGroup/>
> </div>
> <div>
> <Teleport :disabled="!shouldPin" v-if="shouldShow"></Teleport>
> </div>
> ```
... | 2024-07-15T15:35:03 | 2024-07-15T15:58:36 | {} | NONE |
vuejs | core | 2,220,063,409 | 11,323 | linzhe141 | > What about v-if? v-if 怎么样？
The key of v-if is set internally. If the user manually sets the key, it will not take effect.
| 2024-07-10T09:56:11 | 2024-07-10T09:56:11 | {} | MEMBER |
vuejs | core | 2,220,068,256 | 11,323 | so1ve | Thanks for the explanation, perhaps we'd add a warning or improve the document | 2024-07-10T09:58:37 | 2024-07-10T09:58:37 | {} | MEMBER |
vuejs | core | 2,220,404,550 | 11,325 | linzhe141 | > > > const props = defineProps(['text','count'])
> > > const text = props.text
> > > const count = props.count
> >
> >
> > When the App component changes the text and count, the render function of the Hellowold component will be re-executed, but the setup function of Helloworld will not be re-executed, so the t... | 2024-07-10T12:37:11 | 2024-07-10T12:37:11 | {} | MEMBER |
vuejs | core | 2,222,223,511 | 10,236 | yyx990803 | This is no longer reproducible in 3.5 alpha.
The fix in #11244 is not exactly equivalent to the 3.5 behavior and from my testing introduces potential memory leaks when the computed references out of component reactive sources. Considering we are planning to release 3.5 soonish, I will consider this fixed in 3.5 and... | 2024-07-11T07:24:29 | 2024-07-11T07:24:48 | {
"heart": 1,
"rocket": 1
} | MEMBER |
vuejs | core | 2,225,286,981 | 11,341 | yyx990803 | This is not an issue caused by Vue and this is definitely not the right fix. | 2024-07-12T10:28:47 | 2024-07-12T10:28:47 | {
"confused": 1
} | MEMBER |
vuejs | core | 1,812,796,952 | 9,609 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.6 kB (**+74 B**) | 34.2 kB (**+18 B**) | 30.9 kB (**+52 B**) |
... | 2023-11-15T15:54:59 | 2024-07-13T06:52:42 | {} | NONE |
vuejs | core | 2,230,076,674 | 11,366 | edison1105 | @dddssw PR welcome. | 2024-07-16T05:49:54 | 2024-07-16T05:49:54 | {} | MEMBER |
vuejs | core | 2,219,808,270 | 11,319 | edison1105 | /ecosystem-ci run | 2024-07-10T07:55:43 | 2024-07-10T07:55:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,221,965,938 | 10,880 | yangliguo7 | @zch233
不需要指定T类型，你可以看下这个函数类型定义。
https://github.com/vuejs/core/blob/main/packages/runtime-core/src/apiDefineComponent.ts#L123-L154
<img width="1128" alt="image" src="https://github.com/vuejs/core/assets/46318880/887cc47b-7cb1-4593-a39b-77648120b213">
| 2024-07-11T03:50:26 | 2024-07-11T03:50:26 | {} | CONTRIBUTOR |
vuejs | core | 2,223,757,764 | 9,885 | jcbond92 | Seems to be some sort of collision with the update process in `apiCustomElement.ts` as I'm looking a bit more, and I think we can fix the issue there. | 2024-07-11T19:45:55 | 2024-07-11T19:46:09 | {} | NONE |
vuejs | core | 2,226,820,398 | 6,168 | yyx990803 | As of 3.4.31 both cases are working the same. Closing as fixed. | 2024-07-13T08:25:46 | 2024-07-13T08:25:46 | {} | MEMBER |
vuejs | core | 2,227,599,056 | 11,357 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.6 kB | 34.2 kB | 30.9 kB |
| vue.global.prod.js | 146 kB | 53.7 kB | 47.8 kB |
### Usages
| Name | Size |... | 2024-07-15T02:12:44 | 2024-07-15T02:12:44 | {} | NONE |
vuejs | core | 2,042,486,493 | 5,154 | shining-mind | The `v-memo=[]` can be used as workaround, the Vue will call unmount for the components in the cached subtree.
UPD: a more obvious [example of the bug](https://play.vuejs.org/#eNqNU11v0zAU/SvGL0mlLtk0nkZaAaUSIAaIgXixhEJy02ZzfCPbSStV/e9c22loxVrxYtn36xwfH+/4m7ZN+g74Hc9MoevWMgO2a+dC1U2L2rId01CxPas0Niyi0mhMLbBph3iSuoObF... | 2024-04-08T11:18:20 | 2024-07-15T12:34:33 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.