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,560,609,227 | 12,542 | edison1105 | https://github.com/vuejs/core/blob/40193696b3564202173ac0367e4b3ae48c4ffb84/packages/compiler-sfc/src/compileScript.ts#L239-L248
if a variable is used in the template, we will return it in non-inline mode. However, if the template's lang is pug, `isUsedInTemplate` will be true without checking if it is really used in ... | 2024-12-24T03:54:26 | 2024-12-25T01:10:12 | {
"eyes": 1
} | MEMBER |
vuejs | core | 2,563,204,700 | 12,620 | edison1105 | It seems related to https://github.com/unjs/unimport. This issue only occurs when the `ref` is not imported, see [Playground](https://play.vuejs.org/#__PROD__eNp9Uc1OwzAMfhUrl4E0ViE4jQ4J0A5wAAQcc4lar2SkSZQ4Zajqu+Om2tgB7WZ/P/bnpBd33i+6hGIpylgF7QkiUvJglG1WUlCU4lbaotCtd4GgD7gZYBNcCzO2zaStnI0EtSIFK2D27PL8RtqymKaxlxvC1htFyB... | 2024-12-27T00:58:37 | 2024-12-27T00:59:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,567,431,654 | 12,634 | c-harding | Yup, that's definitely the offending code. I suspect this could be fixed with `Object.assign(Object.create(Iterator), {…})` | 2025-01-02T08:40:04 | 2025-01-02T08:40:04 | {} | NONE |
vuejs | core | 2,568,624,377 | 12,637 | youranreus | > I can't reproduce it on my local machine with
>
> ```
> "vue": "3.5.13",
> "typescript": "5.7.2",
> "vue-tsc": "2.2.0"
> ```
Hi, thanks for your comment. I`ve tried the version same as yours and still has the same error. Can you reproduce it in the vue playground that I provide above? | 2025-01-03T02:35:52 | 2025-01-03T03:53:28 | {} | NONE |
vuejs | core | 2,561,868,674 | 12,613 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/f85d4b08-9f30-4bc8-b1bf-365eb5aaf6ba)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12613
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-25T12:23:30 | 2024-12-25T12:23:30 | {} | NONE |
vuejs | core | 2,563,437,706 | 12,623 | ChinaChenMingQuan | What kind of development philosophy is this, and why is the parent component forcibly interfering with the styling of the child component without the use of :deep?
这是什么开发理念?为什么父组件不使用 :deep 就强行干预子组件的样式?
--deepl translator. | 2024-12-27T08:07:00 | 2024-12-27T08:07:00 | {} | NONE |
vuejs | core | 2,564,946,647 | 12,625 | edison1105 | > Does this case correspond to the content of the following note?
>
> > Note that default values for mutable reference types (like arrays or objects) should be wrapped in functions when using withDefaults to avoid accidental modification and external side effects. This ensures each component instance gets its own co... | 2024-12-30T01:53:28 | 2024-12-30T01:56:20 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,558,814,574 | 12,586 | edison1105 | Could you please provide more information? | 2024-12-23T03:04:45 | 2024-12-23T03:04:45 | {} | MEMBER |
vuejs | core | 2,544,424,975 | 12,559 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/21ea5ff1-d73d-40f7-9993-ac611460994c)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12559
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-16T02:44:51 | 2024-12-23T03:07:25 | {} | NONE |
vuejs | core | 2,558,994,206 | 12,575 | Gwynerva | I would argue about "minor" because in my opinion using standart `onErrorCaptured` on async components is not something very specific, and intent to catch async errors is rather common thing, not an edge case. In fact, I am surprised to be the first one to report it...
Either way, it's nice to know it's not a proble... | 2024-12-23T06:25:05 | 2024-12-23T06:43:27 | {} | NONE |
vuejs | core | 2,559,674,895 | 12,575 | edison1105 | @Gwynerva
[Playground with PR #12601](https://deploy-preview-12601--vue-sfc-playground.netlify.app/#__SSR__eNp9U01T2zAQ/SuLLg4zIaYtpxCYKQyd0kPLEKYnHxD2mghsSaMPJ4zH/70rKQke2uYm7b7dffvxevZV61nnkc3ZwpZGaAcWndeXhRStVsZBD3bFm0at77GGAWqjWsgoIjsfQZS8MUaZa66dN1h9xO2R16rVW9csD59QOyFKJa0DDGngYlRzchzdHypMEC4uoS8kpJBZxxtPNkBCAxj... | 2024-12-23T13:05:21 | 2024-12-23T13:05:21 | {} | MEMBER |
vuejs | core | 2,559,070,207 | 12,520 | edison1105 | > @Gwynerva [here it is](https://play.vuejs.org/#__SSR__eNp9Uk1v2zAM/SuELu4Azz5su3hqgG0osA7rB9rcqh5ch3bUypIgyWkAw/+9lBKnLdDmJFKPj3yU3sh+WVtsBmQV475x0gbwGAa7EFr21rgAf0xvoXWmh6woYxLLs59C83JHoFJKAvZW1QEpA+AruYHN19a4U8EkSA0/BEsIYYPaRxQruRjlxEs692h5gHmaHOqOeljBYB16RSG3i3Ot0QH3wRndLf4uL/6Tll3CS5LOytdZ0Kjae+Ip6cNBxNHRvCT5FPHy... | 2024-12-23T07:31:04 | 2024-12-24T08:04:07 | {
"heart": 2
} | MEMBER |
vuejs | core | 2,561,519,719 | 12,575 | edison1105 | @Gwynerva
This is the expected behavior. The SSR output content is three empty divs since SSR has no patch and Comp.vue renders nothing. for this scenarios, you should use `data-allow-mismatch = "children"` to ignore the mismatch warning.
see [Playground](https://deploy-preview-12601--vue-sfc-playground.netlify.ap... | 2024-12-25T01:02:40 | 2024-12-25T01:02:40 | {} | MEMBER |
vuejs | core | 2,561,868,637 | 12,613 | 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-25T12:23:24 | 2024-12-25T12:23:24 | {} | NONE |
vuejs | core | 2,564,936,507 | 12,624 | edison1105 | This might be using the implementation form vue2. The absence of `isComposing` might be to ensure compatibility across different browser environments(perhaps `isComposing` behaves inconsistently in various browsers/webviews).
Since there is no reproducible demo, we cannot investigate the reason. Could you please provi... | 2024-12-30T01:29:10 | 2024-12-30T01:29:10 | {} | MEMBER |
vuejs | core | 2,566,101,808 | 12,630 | edison1105 | Please follow the issue requirement and provide a minimal runnable reproduction
cannot reproduce see [Playground](https://play.vuejs.org/#eNqFUk1v2zAM/SusLk6AzEaxnTK3wFYY2HbYhm7ALr54Nh2rkyVBktMMhv/7KGl20q/0JvI9kY/kG9kHrdP9gGzLclsbrh1YdIO+LiXvtTIORmiw5RJvButUXwjsUTqYoDWqh4S+Ju8X7o3q9X8gzXzgS3u8VtI6KODquWIrz9yMYLuqUfe3... | 2024-12-31T03:28:08 | 2024-12-31T08:46:04 | {} | MEMBER |
vuejs | core | 2,568,766,040 | 12,643 | coderwhytop | The configDefaults that is not used is removed. | 2025-01-03T06:53:34 | 2025-01-03T06:53:34 | {} | CONTRIBUTOR |
vuejs | core | 2,558,822,112 | 12,586 | YanGer-kz | > Could you please provide more information?
When developing my own component, I wanted to use custom props as onClick, onFocus.
I noticed that they are not in runtime or I did not find them, I thought it would be better to add export for the type that will allow me to use for my components | 2024-12-23T03:13:03 | 2024-12-23T03:13:03 | {} | NONE |
vuejs | core | 2,559,058,475 | 12,575 | Gwynerva | @edison1105 Does not [seem](https://play.vuejs.org/#__SSR__eNp9U01v2zAM/SusLnaALO62ntK0wFp0WHfYiqbYyYeqNt2otSVBH04Kw/99lBynXrf1JpJPJB/J17EvWi9aj2zJVrYwQjuw6Lw+z6VotDIOOrAbXtdqe4sV9FAZ1UBCP5LTCUTJK2OUueTaeYPlW9wBeakavQ8tsmCE2gOiUNI6wJAGziY101kMv6mQIpydQ5dLGL4sWl578gESGsAQByOh4rUNjn6Wy1U28CNmZDhsdM0dkgWwWnurUdrBIrsULbQfR... | 2024-12-23T07:21:23 | 2024-12-23T07:26:24 | {} | NONE |
vuejs | core | 2,561,287,057 | 12,575 | Gwynerva | @edison1105 Sadly, still get hydration mismatches when rendering nodes deep inside `<Suspense>` (in Nuxt suspense is on root level and it can not be used again somewhere deep inside).
[Playground Example](https://deploy-preview-12601--vue-sfc-playground.netlify.app/#__SSR__eNqVVE1P20AQ/SuDLwlSiGnLKQSkgqhKDy0iqL34wGK... | 2024-12-24T16:51:26 | 2024-12-24T17:02:27 | {} | NONE |
vuejs | core | 2,561,923,220 | 12,570 | johnsoncodehk | /ecosystem-ci run | 2024-12-25T15:07:29 | 2024-12-25T15:07:29 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,562,041,878 | 12,570 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/12497834473)
| 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-26T00:40:35 | 2024-12-26T00:40:35 | {} | CONTRIBUTOR |
vuejs | core | 2,564,941,326 | 12,627 | 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:29 | 2024-12-30T01:41:29 | {} | NONE |
vuejs | core | 2,558,743,154 | 12,595 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/5fd8782f-83b5-48f4-97aa-48c5753d25cb)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12595
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-23T01:45:43 | 2024-12-30T01:41:37 | {} | NONE |
vuejs | core | 2,569,177,058 | 12,604 | chrisjansky | +1, I have the same exact issue | 2025-01-03T12:51:47 | 2025-01-03T12:51:47 | {} | NONE |
vuejs | core | 2,559,038,157 | 12,601 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/b393c9a2-9367-4fff-9c73-1ca62d545614)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12601
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-23T07:04:07 | 2024-12-23T14:02:18 | {} | NONE |
vuejs | core | 2,559,814,864 | 12,591 | huang-julien | In Nuxt side, we could either treeshake only the callback of `onServerPrefetch` in client side bundle or add `instance.sp = instance.sp || []`.
But i'm not really in favour of the second one tho.
Or maybe can we leave it to vue: we remove the treeshaking of `onServerPrefetch` and maybe can the vue compiler do the... | 2024-12-23T14:32:35 | 2024-12-23T14:32:44 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 2,568,783,930 | 12,643 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/e567e122-eafe-4bf2-828a-d3f0e34b1f9c)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12643
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-01-03T07:16:45 | 2025-01-03T07:16:45 | {} | NONE |
vuejs | core | 2,544,457,484 | 12,562 | 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-16T03:15:26 | 2024-12-23T03:11:02 | {} | NONE |
vuejs | core | 2,559,328,370 | 12,575 | Gwynerva | @edison1105 This does not work with bun, but I installed it in different folder and just copy/pasted the new files inside my project.
Now, it does not crash the whole page (which is super cool) but still tries to render template causing error and hydration mismatches.
 should be wrapped in functions when using withDefaults to avoid accidental modification and external side effects. This ensures each component instance gets its own copy of ... | 2024-12-29T14:15:48 | 2024-12-29T14:15:48 | {} | NONE |
vuejs | core | 2,566,114,047 | 12,088 | brc-dd | Technically, that same spec says this too:
> For historical reasons, certain elements have extra restrictions beyond even the restrictions given by their content model.
>
> A table element must not contain tr elements, even though these elements are technically allowed inside table elements according to the conten... | 2024-12-31T04:04:05 | 2024-12-31T04:20:19 | {
"-1": 1
} | MEMBER |
vuejs | core | 2,566,784,300 | 12,088 | tomtheisen | > Technically, that same spec says this too:
>
> > For historical reasons, certain elements have extra restrictions beyond even the restrictions given by their content model.
> > A table element must not contain tr elements, even though these elements are technically allowed inside table elements according to the c... | 2025-01-01T01:06:43 | 2025-01-01T01:15:10 | {
"+1": 8
} | NONE |
vuejs | core | 2,367,373,050 | 12,004 | edison1105 | duplicate of https://github.com/vuejs/core/issues/7276 | 2024-09-23T07:00:27 | 2024-09-23T07:00:27 | {} | MEMBER |
vuejs | core | 2,369,613,437 | 12,007 | skirtles-code | Avoiding `?.` is intended to reduce the file size, but it looks like this has increased it by 3 bytes. I was curious about why...
It looks like the `?.` version gets inlined into the `get dep` getter in `ObjectRefImpl`. Even though it expands to something fairly verbose, the inlining shaves off lots of bytes. Removi... | 2024-09-23T22:10:46 | 2024-09-23T22:10:46 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 2,367,472,014 | 12,007 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ----------------- | ----------------- | ------------------- |
| runtime-dom.global.prod.js | 101 kB (**+1 B**) | 38 kB (**-10 B**) | 34.2 kB (**-44 B**) |
| vue.global... | 2024-09-23T07:53:37 | 2024-09-24T03:01:11 | {} | NONE |
vuejs | core | 2,372,627,898 | 12,021 | jh-leong | /ecosystem-ci run | 2024-09-25T00:31:09 | 2024-09-25T00:31:09 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,372,747,934 | 11,956 | ftrsoft | @yyx990803 today I will test all versions of vue, determine which memory leaks starts and take a memory snapshot. Yesterday I checked 3.5.1 it is Ok | 2024-09-25T02:14:43 | 2024-09-25T02:14:43 | {} | NONE |
vuejs | core | 2,367,068,669 | 12,000 | edison1105 | ```js
import Vue from 'vue'
const compile = Vue.compile
// vite.config.js
// resolve: {
// alias: {
// vue: '@vue/compat',
// },
// },
```
| 2024-09-23T00:49:37 | 2024-09-23T00:49:37 | {} | MEMBER |
vuejs | core | 2,370,354,028 | 12,017 | linzhe141 | [minimal reproduction with playground](https://play.vuejs.org/#eNq9VE2P2kAM/SujXMJKNDm0JzaghnalfqgfolVPkVYhGJhl4okyk0CF8t/rmdnMBnZLu5c9gLD97Hm2nzkGaVVFbQPBJEhUUfNKMwW6qZjIcTPNAq2yYJYhLytZa/ZBlvCLw56ta1myMIp7hykRXnvckRWyrFjncWspwwyT2D1BBcnQUFYi10AWY8lngCoVvHUmOUwFiYCaTbgiJv1TWcAmO/hNHoOIbm8xL4FIJrHPcBXjYckkHjyXYTCmzgqJa... | 2024-09-24T06:59:02 | 2024-09-24T09:55:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,371,411,958 | 12,020 | edison1105 | It works in v3.5.6 | 2024-09-24T14:08:14 | 2024-09-24T14:08:14 | {} | MEMBER |
vuejs | core | 2,372,067,927 | 12,021 | samuelwei | +1 This fixes a bug since Vue 3.5.7
My CI tests suddenly failed with Vue 3.5.7+ because the pinia getters were no longer computed | 2024-09-24T18:56:31 | 2024-09-24T18:56:31 | {} | NONE |
vuejs | core | 2,372,575,531 | 12,022 | edison1105 | /ecosystem-ci run | 2024-09-24T23:39:40 | 2024-09-24T23:39:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,366,353,059 | 11,992 | edison1105 | /ecosystem-ci run | 2024-09-22T09:32:04 | 2024-09-22T09:32:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,367,414,074 | 7,276 | ritilyn1991 | same problem in 3.5.8 | 2024-09-23T07:23:33 | 2024-09-23T07:23:33 | {} | NONE |
vuejs | core | 2,367,798,130 | 12,008 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ----- | ------- |
| runtime-dom.global.prod.js | 101 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 160 kB | 58 kB | 51.5 kB |
### Usages
| Name | Size | Gzip |... | 2024-09-23T10:22:09 | 2024-09-23T10:22:09 | {} | NONE |
vuejs | core | 2,369,078,747 | 8,600 | rchl | I'll also paste my recent Vue language features issues since I forgot that I've created this before:
### Vue - Official extension or vue-tsc version
2.1.6
### VSCode version
1.93.1
### Vue version
3.5.8
### TypeScript version
5.6.2
### System Info
```shell
System:
OS: macOS 14.6.1
... | 2024-09-23T18:39:57 | 2024-09-23T18:39:57 | {} | NONE |
vuejs | core | 2,373,159,555 | 12,025 | edison1105 | Thanks for the PR.
I don't think this comment is necessary and the git commit message contains enough information. | 2024-09-25T06:38:41 | 2024-09-25T06:38:41 | {} | MEMBER |
vuejs | core | 2,365,475,926 | 11,983 | jh-leong | This behavior is expected. According to the docs: https://vuejs.org/api/reactivity-core.html#watch
> When using a getter source, the watcher only fires if the getter's return value has changed. If you want the callback to fire even on deep mutations, you need to explicitly force the watcher into deep mode with { dee... | 2024-09-22T05:25:31 | 2024-09-22T05:25:31 | {} | MEMBER |
vuejs | core | 2,367,168,258 | 11,998 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/10987108462)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10953451101) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-09-23T03:25:36 | 2024-09-23T03:25:36 | {} | CONTRIBUTOR |
vuejs | core | 2,367,377,290 | 11,998 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/10989164253)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10987953443) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-09-23T07:02:53 | 2024-09-23T07:02:53 | {} | CONTRIBUTOR |
vuejs | core | 2,367,397,877 | 12,006 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/ff5f7eb6-a2ce-40de-a847-034b4a604138)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12006
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-09-23T07:15:15 | 2024-09-23T07:15:15 | {} | NONE |
vuejs | core | 2,368,881,695 | 12,012 | KazariEX | Set `vueCompilerOptions.target` to `3.5`. | 2024-09-23T17:10:07 | 2024-09-23T17:10:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,370,231,452 | 12,010 | edison1105 | /ecosystem-ci run | 2024-09-24T05:35:45 | 2024-09-24T05:35:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,371,101,478 | 11,956 | agracia-foticos | Maybe this also is a memory leak???

| 2024-09-24T12:14:32 | 2024-09-24T13:18:10 | {} | NONE |
vuejs | core | 2,373,944,105 | 12,029 | Vanilagy | This here seems to be the code causing the divergence: (EDIT: It's not?)

I think it's destructuring `owner` from the `rawRef` here, which in my case (`new A()`) is obviously undefined. Thankfully in ... | 2024-09-25T12:26:35 | 2024-09-25T12:47:16 | {} | NONE |
vuejs | core | 2,366,348,046 | 11,992 | edison1105 | Thanks for this PR and I made small tweaks https://github.com/vuejs/core/pull/11992/commits/78f5696d637cf5a1294cc27313d326464779a757
LGTM. | 2024-09-22T09:31:10 | 2024-09-22T11:27:26 | {} | MEMBER |
vuejs | core | 2,367,080,008 | 11,992 | edison1105 | @KazariEX @skirtles-code
Maybe we can do compatibility like the following:
```ts
if('compileString' in nodeSaas){
// modern api
} else {
// legacy api
}
``` | 2024-09-23T01:09:08 | 2024-09-23T01:09:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,368,175,295 | 12,010 | edison1105 | /ecosystem-ci run | 2024-09-23T13:08:12 | 2024-09-23T13:08:12 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,370,454,756 | 12,010 | edison1105 | /ecosystem-ci run
| 2024-09-24T07:48:25 | 2024-09-24T07:48:25 | {
"+1": 1,
"hooray": 1
} | MEMBER |
vuejs | core | 2,371,914,755 | 12,022 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ----- | ------- |
| runtime-dom.global.prod.js | 101 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 160 kB | 58 kB | 51.5 kB |
### Usages
| Name | Size | Gzip |... | 2024-09-24T17:38:50 | 2024-09-24T17:38:50 | {} | NONE |
vuejs | core | 2,373,407,394 | 12,028 | jh-leong | Closing as a duplicate of #12020 | 2024-09-25T08:25:56 | 2024-09-25T08:25:56 | {} | MEMBER |
vuejs | core | 2,367,053,445 | 11,897 | yyx990803 | After thinking about this, we do already have other helpers like `useAttrs()` and `useTemplateRef()` that return a non-nullable type even when there is no active instance, and I think we should keep `useId()` consistent with that (i.e. always return a string). See a17709275 | 2024-09-23T00:40:07 | 2024-09-23T00:40:07 | {
"+1": 2,
"hooray": 2,
"rocket": 7
} | MEMBER |
vuejs | core | 2,370,125,838 | 11,956 | ftrsoft | I'm sorry, I don't know how to make a reproduction. I have a service in docker: nuxt 3.12.4 + vue 3.5.8. Memory usage is constantly growing. On vue 3.4.38, memory usage is stable

| 2024-09-24T04:27:46 | 2024-09-24T04:41:37 | {} | NONE |
vuejs | core | 2,371,597,878 | 12,021 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 101 kB (**+56 B**) | 38.1 kB (**+33 B**) | 34.2 kB (**-2 B**) |
| v... | 2024-09-24T15:14:06 | 2024-09-25T00:30:22 | {} | NONE |
vuejs | core | 2,372,635,039 | 12,021 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/11024072613)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10987953443) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-09-25T00:39:37 | 2024-09-25T00:39:37 | {} | CONTRIBUTOR |
vuejs | core | 2,365,456,274 | 11,983 | guda-art | > Please provide a minimal reproduction.
### deep: true will output trigger but false not
https://play.vuejs.org/#eNp9kstuwjAQRX9l5A1BQkFVu0pD1IdYtIu2aruruwhhCAHHtvwApCj/XscmEKSKrMZz79XMid2QRynjnUWSkFQXqpIGNBorM8qrWgploAGFq8k+N8UaWlgpUcPIBUaUF4JrA2KxgVnniRpu6wWqBG7aMeU+EVEOx+/nXAJEY5hlXTTe5cxiHJKTs+V3UAdzM8x3owXDmIky... | 2024-09-22T04:18:16 | 2024-09-22T04:18:16 | {} | NONE |
vuejs | core | 2,364,250,539 | 11,992 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/240e04b5-e678-4a42-b6f2-c8f41ef54dad)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11992
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-09-20T18:00:15 | 2024-09-23T02:59:58 | {} | NONE |
vuejs | core | 2,367,157,836 | 11,992 | edison1105 | /ecosystem-ci run | 2024-09-23T03:09:47 | 2024-09-23T03:09:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,370,239,282 | 12,010 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/11007678592)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10987953443) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-09-24T05:41:59 | 2024-09-24T05:41:59 | {} | CONTRIBUTOR |
vuejs | core | 2,372,675,097 | 12,024 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/d03800df-5240-4c2c-aa10-6e25106a8b0f)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12024
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-09-25T01:17:44 | 2024-09-25T03:24:29 | {} | NONE |
vuejs | core | 2,373,404,032 | 11,956 | ftrsoft | Test Vue 3.5.8. Memory leaks.
I found a place in my project that increases memory when change from one page (page1) to another (page2).
Algorigthm for snapshots:
1. Go to different pages on project for wam-up
2. Take snapshot 1
3. Make 5 times (page1 -> page2)
4. Take snapshot 2
5. Make 1 time (page1 -> page2)
... | 2024-09-25T08:24:20 | 2024-09-25T08:24:20 | {
"+1": 1
} | NONE |
vuejs | core | 2,365,484,159 | 11,992 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c04d12c83594f03ee1bfe0c518a2976cbd743812 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2024-09-22T06:01:14 | 2024-09-22T09:30:01 | {} | NONE |
vuejs | core | 2,366,735,907 | 11,992 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/10980718467)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10953451101) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-09-22T11:27:24 | 2024-09-22T11:27:24 | {} | CONTRIBUTOR |
vuejs | core | 2,367,485,549 | 11,956 | aurelsserban | @yyx990803 @edison1105 sorry for being late.
I can confirm that in my case vue v3.5.7 and v3.5.8 solved the memory leaks in our webapp.
Thank you. | 2024-09-23T08:00:59 | 2024-09-23T08:00:59 | {
"heart": 1
} | NONE |
vuejs | core | 2,367,798,689 | 12,008 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/76d7d4fb-7f92-4e79-8ee1-6c5a39556ad0)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12008
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-09-23T10:22:24 | 2024-09-23T10:22:24 | {} | NONE |
vuejs | core | 2,368,153,368 | 12,009 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ----- | ------- |
| runtime-dom.global.prod.js | 101 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 160 kB | 58 kB | 51.5 kB |
### Usages
| Name | Size | Gzip |... | 2024-09-23T12:59:15 | 2024-09-23T12:59:15 | {} | NONE |
vuejs | core | 2,315,142,333 | 11,702 | markrian | @alexanderturinske I spent a bit more time looking into this and believe I have a fix.
Roughly speaking, the problem is that the compiler and runtime have different expectations about how "native" events are annotated. The compiler constructs a string of modifiers that matches the source order. So, `@click.native.ca... | 2024-08-28T12:05:17 | 2024-09-23T13:36:37 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,369,961,538 | 12,014 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ----- | ------- |
| runtime-dom.global.prod.js | 101 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 160 kB | 58 kB | 51.5 kB |
### Usages
| Name | Size | Gzip |... | 2024-09-24T02:03:32 | 2024-09-24T03:12:07 | {} | NONE |
vuejs | core | 2,371,240,296 | 12,019 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/bb4b6074-5074-423f-b3b6-f49e17e0f08f)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12019
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
pnpm add https://pkg.... | 2024-09-24T13:13:32 | 2024-09-24T13:13:32 | {} | NONE |
vuejs | core | 2,371,241,255 | 11,956 | edison1105 | @agracia-foticos
Please create a new issue with a minimal reproduction. | 2024-09-24T13:13:55 | 2024-09-24T13:13:55 | {} | MEMBER |
vuejs | core | 2,373,301,739 | 11,956 | ftrsoft | I test different version, there are result:

Snapshot of Node heap with vue 3.5.6:

[Heap-20240925T143110.zip](https://github.com/user... | 2024-09-25T07:40:36 | 2024-09-25T07:40:36 | {} | NONE |
vuejs | core | 2,364,249,910 | 11,992 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ----- | ------- |
| runtime-dom.global.prod.js | 101 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 160 kB | 58 kB | 51.5 kB |
### Usages
| Name | Size | Gzip |... | 2024-09-20T18:00:10 | 2024-09-22T06:00:51 | {} | NONE |
vuejs | core | 2,366,857,085 | 11,998 | skirtles-code | I think #7167 is similar. I'm not sure why it was closed, it might have been a misunderstanding.
I'm not sure whether this a bug or not. Personally, I think it's an arbitrary choice between two different behaviours. It isn't immediately obvious to me which is better. To be clear, I think the question that we need to... | 2024-09-22T16:15:06 | 2024-09-22T16:15:06 | {} | CONTRIBUTOR |
vuejs | core | 2,367,162,219 | 11,992 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/10987020011)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10953451101) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-09-23T03:16:08 | 2024-09-23T03:16:08 | {} | CONTRIBUTOR |
vuejs | core | 2,371,268,080 | 11,956 | yyx990803 | @ftrsoft looks like this is on the server-side only.
I think you can use `node --inspect .output/server/index.mjs` to run the built Nuxt app locally, and then use Chrome (go to `chrome://inspect`) to take memory snapshots and compare two snapshots over time. You can also save the memory profiles and share with us he... | 2024-09-24T13:24:01 | 2024-09-24T13:24:01 | {} | MEMBER |
vuejs | core | 2,371,597,696 | 12,021 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/2d0550f8-10fc-4d4f-8837-079aee55c62e)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12021
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-09-24T15:14:01 | 2024-09-25T00:30:20 | {} | NONE |
vuejs | core | 2,366,458,711 | 11,998 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ---------------- | ------------------- |
| runtime-dom.global.prod.js | 101 kB (**+43 B**) | 38 kB (**+7 B**) | 34.2 kB (**-16 B**) |
| vue.global... | 2024-09-22T09:53:50 | 2024-09-23T05:59:12 | {} | NONE |
vuejs | core | 2,367,782,078 | 12,005 | yangliguo7 | @edison1105 ok. i'll see to it
by the way. Is this change too simple to require adding tests? | 2024-09-23T10:14:28 | 2024-09-23T10:14:28 | {} | CONTRIBUTOR |
vuejs | core | 2,369,095,508 | 8,600 | rchl | Note that those could be treated as two different issues (one for native elements and one for custom components) but it might be good to think about both at the same time. | 2024-09-23T18:47:20 | 2024-09-23T18:47:20 | {} | NONE |
vuejs | core | 2,369,961,669 | 12,014 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/22d385df-e198-48f4-8820-3cd52958897f)
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-dom@12014
```
</p></details>
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.p... | 2024-09-24T02:03:39 | 2024-09-24T05:16:45 | {} | NONE |
vuejs | core | 2,371,426,147 | 12,020 | JimmyPez | +1. I've also experienced the same. | 2024-09-24T14:13:34 | 2024-09-24T14:13:34 | {} | NONE |
vuejs | core | 2,367,092,194 | 12,001 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/4e46a878-9755-4c80-9ed1-cff8a00fa779)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12001
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-09-23T01:29:18 | 2024-09-25T06:33:09 | {} | NONE |
vuejs | core | 2,373,342,972 | 11,956 | edison1105 | @ftrsoft
Could you please test it with v3.5.8 and take snapshots?
Because we've already fixed several memory leaks before v3.5.8. | 2024-09-25T07:59:24 | 2024-09-25T07:59:24 | {} | MEMBER |
vuejs | core | 2,367,164,474 | 11,998 | edison1105 | /ecosystem-ci run | 2024-09-23T03:19:28 | 2024-09-23T03:19:28 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,370,364,999 | 11,956 | konstantin-karlovich-unbiased-co-uk | To be honest there is a memory leak in my project too, which I'm trying to localise
It appears since vue 3.5.5 and nuxt 3.13.2 | 2024-09-24T07:05:08 | 2024-09-24T07:05:08 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.