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,724,282,940 | 13,036 | jh-leong | This behavior is expected.
In your case, the model prop in the parent component remains unchanged, so the child component does not update. You can force an update by modifying the value inside `nextTick`: [Playground](https://play.vuejs.org/#eNqNUk1vm0AQ/SujvRhLGA7tybWjfiiHVOqHWreXbg8IxmSTZVntB3WL+O+dXYxNEivKBcGbx5t5M... | 2025-03-14T10:36:44 | 2025-03-14T10:36:44 | {} | MEMBER |
vuejs | core | 2,727,744,596 | 13,047 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.3 kB |
| vue.global.prod.js | 158 kB | 58 kB | 51.6 kB |
### Usages
| Name | Size | G... | 2025-03-17T00:21:41 | 2025-03-17T00:21:41 | {} | NONE |
vuejs | core | 2,728,056,276 | 13,051 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.3 kB |
| vue.global.prod.js | 158 kB | 58 kB | 51.6 kB |
### Usages
| Name | Size | G... | 2025-03-17T03:50:25 | 2025-03-17T03:50:25 | {} | NONE |
vuejs | core | 2,728,866,025 | 13,053 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vapor-repl* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | efaa5b156779da4f2358bc04ba2c2f599b24fb1a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vapor-repl/d... | 2025-03-17T10:00:10 | 2025-03-17T10:01:26 | {} | NONE |
vuejs | core | 2,730,045,757 | 11,517 | maddanio | Exactly our problem too... | 2025-03-17T15:56:40 | 2025-03-17T15:56:40 | {} | NONE |
vuejs | core | 2,730,088,629 | 13,057 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/6d794f23-3e1b-4670-a7e6-e8f722e79ec8)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13057
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-17T16:09:51 | 2025-03-18T04:33:53 | {} | NONE |
vuejs | core | 2,708,914,593 | 12,935 | johnsoncodehk | /ecosystem-ci run | 2025-03-09T15:26:10 | 2025-03-09T15:26:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,709,793,625 | 13,010 | Justineo | > Yes, but this will be a breaking change.
Does any specific piece of code rely on the presence of `true-value` and `false-value` as DOM attributes right now? | 2025-03-10T08:34:05 | 2025-03-10T08:34:05 | {} | MEMBER |
vuejs | core | 2,720,597,379 | 13,032 | edison1105 | duplicate of https://github.com/vuejs/core/issues/12261 | 2025-03-13T09:38:53 | 2025-03-13T09:38:53 | {} | MEMBER |
vuejs | core | 2,720,786,617 | 13,031 | grindpride | > Please try updating `vue-tsc` to `v3.0.0-alpha.0`.
Yep, that works well, thx
https://stackblitz.com/edit/vitejs-vite-bpg4gyf6?file=package.json,src%2FApp.vue | 2025-03-13T10:41:13 | 2025-03-13T10:41:13 | {} | NONE |
vuejs | core | 2,727,202,638 | 13,044 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/8640fbfe-78a3-4106-87a9-6c86e370837e)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13044
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-16T05:23:12 | 2025-03-16T05:23:12 | {} | NONE |
vuejs | core | 2,723,883,245 | 13,035 | Coreight98 | > vue only exports the Component's type definition, there is no associated class or method implementation, if you set verbatimModuleSyntax: false, it does cause the problem you mentioned. I think this might be as expected though?
>
> I haven't found a role for **VUE_PROD_DEVTOOLS** in this, it seems to fail to package... | 2025-03-14T07:45:07 | 2025-03-14T07:57:06 | {} | NONE |
vuejs | core | 2,727,744,871 | 13,046 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/5ccc8382-094d-47ed-90c2-ce00d1d13fc9)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13046
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-17T00:21:59 | 2025-03-17T03:29:21 | {} | NONE |
vuejs | core | 2,709,227,540 | 13,015 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ----------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 100 kB (**-5 B**) | 38.1 kB (**-19 B**) | 34.3 kB (**+17 B**) |
| vue.... | 2025-03-10T01:39:01 | 2025-03-10T01:39:01 | {} | NONE |
vuejs | core | 2,718,093,773 | 12,935 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/13813756494)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/13804039700) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci... | 2025-03-12T14:30:37 | 2025-03-12T14:30:37 | {} | CONTRIBUTOR |
vuejs | core | 2,720,595,572 | 13,032 | yangxiuxiu1115 | https://github.com/vuejs/core/issues/12261#issuecomment-2440005882
https://github.com/vuejs/core/issues/12261 | 2025-03-13T09:38:12 | 2025-03-13T09:38:12 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,723,054,613 | 12,948 | mrleblanc101 | Yass, thanks 🙌 | 2025-03-14T01:01:15 | 2025-03-14T01:01:15 | {} | NONE |
vuejs | core | 2,726,576,674 | 13,041 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vapor-repl* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 1e71009effffe76cdb9286b61c646bcca138cbb2 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vapor-repl/d... | 2025-03-15T14:05:09 | 2025-03-15T14:10:15 | {} | NONE |
vuejs | core | 2,727,777,265 | 13,045 | edison1105 | LGTM | 2025-03-17T00:59:49 | 2025-03-17T00:59:49 | {} | MEMBER |
vuejs | core | 2,677,262,635 | 12,931 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/1e13a482-cfb8-41d1-9b90-55dd1613a314)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12931
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-02-24T01:27:45 | 2025-03-10T01:39:09 | {} | NONE |
vuejs | core | 2,709,832,588 | 13,010 | sebbayer | I'm only concerned about passing the validator, but I also think that standards are important. Maybe that's in my DNA as a German ;)
Backwards compatibility with data-attributes being the standard sounds like a good solution. | 2025-03-10T08:49:41 | 2025-03-10T08:49:41 | {} | NONE |
vuejs | core | 2,718,122,569 | 12,935 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/13813756494)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/13804039700) |
|-------|--------|----------------|
| pinia | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1381375649... | 2025-03-12T14:39:28 | 2025-03-12T14:39:28 | {} | CONTRIBUTOR |
vuejs | core | 2,719,236,419 | 12,935 | johnsoncodehk | /ecosystem-ci run | 2025-03-12T22:06:13 | 2025-03-12T22:06:13 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,693,198,283 | 12,984 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/6021a520-540d-4820-98a0-135fdf8c9504)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12984
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-03T03:33:41 | 2025-03-17T01:04:37 | {} | NONE |
vuejs | core | 2,601,152,219 | 12,747 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/9fdc985d-a8a3-4f69-a13f-32a5ab1249ad)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12747
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-01-20T01:38:20 | 2025-03-17T03:20:57 | {} | NONE |
vuejs | core | 2,702,634,464 | 5,705 | Ecco | Thanks for the very insightful feedback @brentfulgham ! Since WebKit is leading the way (yay!), I tried to come up with a patch for Vue 😄 | 2025-03-06T02:37:54 | 2025-03-06T02:37:54 | {
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 2,709,227,227 | 13,014 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.3 kB |
| vue.global.prod.js | 158 kB | 58 kB | 51.6 kB |
### Usages
| Name | Size | G... | 2025-03-10T01:38:43 | 2025-03-10T01:38:43 | {} | NONE |
vuejs | core | 2,709,325,980 | 13,008 | edison1105 | this one is related to vite-plugin-vue. | 2025-03-10T03:16:37 | 2025-03-10T03:16:37 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,721,369,505 | 13,030 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/13836321088)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/13804039700) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci... | 2025-03-13T14:00:27 | 2025-03-13T14:00:27 | {} | CONTRIBUTOR |
vuejs | core | 2,722,414,064 | 12,948 | mrleblanc101 | This is a major pain for debugging, I hope this gets merged soon | 2025-03-13T19:03:35 | 2025-03-13T19:03:35 | {} | NONE |
vuejs | core | 2,726,576,951 | 13,041 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/fae213f9-a92e-4dcf-b8e5-2f213d7357ee)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13041
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-15T14:05:41 | 2025-03-15T14:08:35 | {} | NONE |
vuejs | core | 2,730,615,183 | 11,969 | xak2000 | I see an already opened [PR](12005) with a fix.
Although, I have some comments regarding type name and it's exported state, it still does its job.
Is there anything else I can do to make this PR (imrpoved or not) to be merged? It is already in a `ready to merge` state, so I wonder why it is stalled for so long. 🤷♂ | 2025-03-17T19:31:07 | 2025-03-17T19:31:07 | {} | NONE |
vuejs | core | 2,702,870,515 | 13,001 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 100 kB (**+19 B**) | 38.1 kB (**+10 B**) | 34.3 kB (**+21 B**) |
| v... | 2025-03-06T05:43:41 | 2025-03-06T05:43:41 | {} | NONE |
vuejs | core | 2,705,863,676 | 12,999 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/13716874180)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/13714085897) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci... | 2025-03-07T08:45:36 | 2025-03-07T08:45:36 | {} | CONTRIBUTOR |
vuejs | core | 2,712,722,138 | 13,022 | jh-leong | This behavior is expected: https://vuejs.org/guide/components/props.html#boolean-casting | 2025-03-11T05:45:29 | 2025-03-11T05:45:29 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,727,781,588 | 13,049 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.3 kB |
| vue.global.prod.js | 158 kB | 58 kB | 51.6 kB |
### Usages
| Name | Size | G... | 2025-03-17T01:04:59 | 2025-03-17T01:04:59 | {} | NONE |
vuejs | core | 2,729,721,766 | 13,055 | padcom | the workaround is to add the `.camel` modifier, e.g. `.test-prop.camel="someReactiveValue"`. | 2025-03-17T14:26:44 | 2025-03-17T14:26:44 | {} | CONTRIBUTOR |
vuejs | core | 2,268,741,700 | 11,514 | edison1105 | a workaround `<transition-group :tag="'div'">` | 2024-08-05T10:31:08 | 2024-08-06T00:02:40 | {
"rocket": 1
} | MEMBER |
vuejs | core | 2,270,245,335 | 11,442 | jh-leong | Hi @mefcorvi, thanks for your feedback.
The behavior in the examples you mentioned is expected, see [TypeScript Playground](https://www.typescriptlang.org/play/?#code/JYWwDg9gTgLgBAbzgWQIYE8BGBTAStgMwBo4pC4BfOAqCEOAcgDcBXbBgbgFgAoXgYwgA7AM7xUALhQYc+AgB4hLEDigA+OAF44ARm49Bo+Ji2lCAClQBKDnAD0duJilzFy1SSUrs63pgB0TKgANmy... | 2024-08-06T02:23:31 | 2024-08-06T02:23:31 | {} | MEMBER |
vuejs | core | 2,270,702,152 | 11,467 | yyx990803 | `msg` is declared in the scope so the output is expected.
In normal JavaScript the code is invalid and results in an error (accessing an in-scope const before initialization), Vue should not change that. | 2024-08-06T08:35:37 | 2024-08-06T08:35:58 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,271,583,432 | 8,826 | yyx990803 | closed via #8830 (to be released in 3.5) | 2024-08-06T15:34:17 | 2024-08-06T15:34:26 | {} | MEMBER |
vuejs | core | 2,271,817,365 | 6,532 | MartinX3 | Bump!
It seems to be impossible to use `exactOptionalPropertyTypes` with `withDefaults` for only the optional props. | 2024-08-06T17:43:26 | 2024-08-06T17:43:26 | {
"+1": 1
} | NONE |
vuejs | core | 2,271,881,541 | 8,132 | yyx990803 | Superseded by 37ccb9b9a | 2024-08-06T18:20:16 | 2024-08-06T18:20:16 | {} | MEMBER |
vuejs | core | 2,272,471,469 | 11,536 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/10276735664)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10242865140) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-08-07T01:55:34 | 2024-08-07T01:55:34 | {} | CONTRIBUTOR |
vuejs | core | 2,272,522,713 | 11,491 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 90.1 kB | 34.6 kB (**+1 B**) | 31.1 kB (**+14 B**) |
| vue.global.prod.js | 147 kB ... | 2024-08-07T02:59:08 | 2024-08-07T02:59:08 | {} | NONE |
vuejs | core | 2,273,378,465 | 11,548 | jh-leong | Thank you for reporting this issue.
FYI: this issue has existed prior to the changes merged in v3.4.35. However, I agree that it requires further investigation and testing. | 2024-08-07T12:40:21 | 2024-08-07T12:40:21 | {} | MEMBER |
vuejs | core | 2,273,527,145 | 11,548 | cnzgray | Sorry, you’re right; this issue has existed in previous versions. | 2024-08-07T13:50:11 | 2024-08-07T13:50:11 | {} | NONE |
vuejs | core | 2,269,205,619 | 9,380 | Zheng-Changfu | > Could be solved by #5912
Can you provide a revised case？ | 2024-08-05T14:23:40 | 2024-08-05T14:23:40 | {} | NONE |
vuejs | core | 2,270,790,074 | 11,491 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 7eb3b6a27ee771b4dd0e62ed09892684d033ae98 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-08-06T09:14:27 | 2024-08-06T10:25:03 | {} | NONE |
vuejs | core | 2,271,578,669 | 11,442 | mefcorvi | To be honest, I didn't expect that it was possible to put one `ref` inside another `ref`. I was sure that in such cases there would be unwrapping, i.e., `b2.value = ref(1)` would be equivalent to `b2.value = 1`, since `ref(ref(1)).value === 1`. Now I see that this is a valid case, and it is actually possible to have on... | 2024-08-06T15:31:56 | 2024-08-06T15:31:56 | {} | CONTRIBUTOR |
vuejs | core | 2,271,590,624 | 6,530 | yyx990803 | closed via bb4a02a70c30e739a3c705b3d96d09258d7d7ded (to be released in 3.5) | 2024-08-06T15:37:44 | 2024-08-06T15:37:44 | {} | MEMBER |
vuejs | core | 2,272,013,482 | 11,531 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 688370abd245bfc00f854147b76535075e4d8f59 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-08-06T19:39:31 | 2024-08-06T19:39:31 | {} | NONE |
vuejs | core | 2,272,015,286 | 11,531 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.1 kB | 34.6 kB | 31.1 kB |
| vue.global.prod.js | 147 kB | 54 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-08-06T19:40:43 | 2024-08-06T19:40:43 | {} | NONE |
vuejs | core | 2,272,531,502 | 11,532 | Alfred-Skyblue | The issue is that `b.value = ref(2)` leads to `b._value = ref(2)`. When we trigger the setter, we do not unref `b._value`, so this results in `b.value` still returning a `ref(2)`. This has been fixed in #11537.
```ts
const a = ref(1)
const b = ref(a);
// b === a
console.log(b.value.toFixed()); // 1
const c = re... | 2024-08-07T03:10:04 | 2024-08-07T03:10:04 | {} | MEMBER |
vuejs | core | 2,272,540,782 | 11,530 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | --------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 98 kB (**+7.84 kB**) | 37.2 kB (**+2.62 kB**) | 3... | 2024-08-07T03:22:01 | 2024-08-07T03:22:48 | {} | NONE |
vuejs | core | 2,272,933,949 | 11,541 | liuseen-l | I opened a PR to solve this problem, which contains some of my own opinions. @edison1105 Do you have time to take a look? thank you🫰 | 2024-08-07T08:38:29 | 2024-08-07T08:38:29 | {} | CONTRIBUTOR |
vuejs | core | 2,272,967,806 | 5,925 | yyx990803 | The root cause is that `<chess-board>` expects `position` to be set as an attribute, but it also exposes `position` as a property.
In other words, this works:
```js
const el = document.createElement('chess-board')
el.setAttribute('position', 'start')
document.getElementById('app').appendChild(el)
```
but t... | 2024-08-07T08:56:08 | 2024-08-07T08:57:34 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,273,572,783 | 11,543 | yyx990803 | For #11526 the to-be-emitted value is different from parent state, so it should indeed emit. It also worked in versions < 3.4.31 so we should keep it working. | 2024-08-07T14:10:00 | 2024-08-07T14:10:00 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,272,558,201 | 11,539 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ---------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 98.4 kB (**+8.18 kB**) | 37.3 kB (**+2.72 kB**) ... | 2024-08-07T03:45:37 | 2024-08-07T14:23:44 | {} | NONE |
vuejs | core | 2,268,821,078 | 11,508 | skirtles-code | I think this is behaving correctly.
Variables using `const` and `let` are still in scope prior to being declared, but an error will be thrown if you try to use them before an initial value is set.
The same thing happens if you don't use an inline function:
* [Playground](https://play.vuejs.org/#eNp9klFPgzAUhf/... | 2024-08-05T11:14:11 | 2024-08-05T11:16:24 | {} | CONTRIBUTOR |
vuejs | core | 2,270,669,918 | 11,521 | Disservin | However, there's a drawback that the Component which exposes the `item` slot still see's a slot being passed, which I wouldn't expect since the `v-if` condition is false.
[Vue Playground](https://play.vuejs.org/#eNqtUk1P4zAQ/Suz3kNYiU2FunvptqDdFQc4AAKOllCUTorBsSN/hEpR/jtjO0mLBD0gbuN5b8Yz817H/jZN3npkC7a0pRGNA4vON6dc... | 2024-08-06T08:19:26 | 2024-08-06T08:20:04 | {} | CONTRIBUTOR |
vuejs | core | 1,772,430,942 | 8,830 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ---------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 97.7 kB (**+7.51 kB**) | 37.1 kB (**+2.54 kB**) ... | 2023-10-20T09:55:50 | 2024-08-06T15:32:59 | {} | NONE |
vuejs | core | 2,271,880,763 | 8,127 | yyx990803 | closed via https://github.com/vuejs/core/commit/37ccb9b9a0e4381f9465e0fc6459609003030da4 (to be released in 3.5) | 2024-08-06T18:19:51 | 2024-08-06T18:19:51 | {} | MEMBER |
vuejs | core | 2,271,225,485 | 11,527 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 90.2 kB (**+15 B**) | 34.6 kB (**+2 B**) | 31.1 kB (**-6 B**) |
| v... | 2024-08-06T12:55:24 | 2024-08-07T04:04:22 | {} | NONE |
vuejs | core | 2,272,883,513 | 4,635 | yyx990803 | Closed via 6758c3cd0
Note the design is a bit different from proposed - instead of passing in an already created app, custom elements now always have an associated app and can be configured via the `configureApp` extra option. This is because `defineCustomElement` and `defineSSRCustomElement` need to auto-determine ... | 2024-08-07T08:12:32 | 2024-08-07T08:12:32 | {
"heart": 5,
"hooray": 5
} | MEMBER |
vuejs | core | 2,273,441,598 | 11,550 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 98.3 kB | 37.3 kB | 33.5 kB |
| vue.global.prod.js | 156 kB | 57 kB | 50.7 kB |
### Usages
| Name | Size |... | 2024-08-07T13:11:47 | 2024-08-07T13:11:47 | {} | NONE |
vuejs | core | 2,272,891,751 | 11,543 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ---------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 90.2 kB (**-8.09 kB**) | 34.6 kB (**-2.71 kB**) ... | 2024-08-07T08:16:42 | 2024-08-07T13:47:15 | {} | NONE |
vuejs | core | 2,269,970,119 | 9,739 | mefcorvi | @yyx990803 I wonder, isn't it possible to just use `ctor.name` in `getType` when it is available? I believe the most expensive part of the code is `ctor.toString().match(/^\s*(function|class) (\w+)/)`. If we can avoid this, we can eliminate the need for caching. I'm also not sure about cases when `getType` is called fo... | 2024-08-05T21:42:28 | 2024-08-05T21:42:28 | {} | CONTRIBUTOR |
vuejs | core | 2,270,204,025 | 7,271 | Alfred-Skyblue | The issue has been resolved by PR #11472 | 2024-08-06T01:43:15 | 2024-08-06T01:43:15 | {} | MEMBER |
vuejs | core | 2,270,255,633 | 11,518 | jh-leong | Closing as a duplicate of #11373. Refer to Evan's [comment](https://github.com/vuejs/core/issues/11373#issuecomment-2232294372):
> As said, this is mostly a design flaw and there's no real fix for it. I am thinking of providing a dedicate useTemplateRef function in 3.5. | 2024-08-06T02:33:27 | 2024-08-06T02:33:27 | {} | MEMBER |
vuejs | core | 2,270,631,297 | 8,038 | yyx990803 | Thanks for the PR - relying on `compilerOptions.isCustomElement` is not going to work for projects that use the build step to pre-compile templates. However, we can simply check for the presence of `-` in the tag name for custom elements. See https://github.com/vuejs/core/commit/7d473b7721b423050dba62823b16f3d39e640567... | 2024-08-06T08:00:14 | 2024-08-06T08:00:14 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,272,423,996 | 11,527 | edison1105 | Could you please add a test case? | 2024-08-07T00:59:47 | 2024-08-07T00:59:47 | {} | MEMBER |
vuejs | core | 2,272,485,492 | 11,536 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/10276852312)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10242865140) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-08-07T02:12:35 | 2024-08-07T02:12:35 | {} | CONTRIBUTOR |
vuejs | core | 2,272,832,114 | 11,541 | liuseen-l | This way you can achieve your [needs：](https://play.vuejs.org/#eNqFVduO2zYQ/ZWBgMY2sLJ3k7YPiu20m+ahBZoGbVGgiPJAiyOba5oUSMoXuP73Di+y5d3NRgZkaa5nZg5Hx+znphlvW8yKbGorIxoHFl3bgGRqOSszZ8tsXiqxabRxcASDNZygNnoDA3IbnFX3Wktk6r51TqtkMJ5cSX2ewdtSlarSyjpYBOn7lRYVwsyHni6iPfwHqpVyPvT3EblMJxEcQaEXh5tGMof0BjBd3c1j/BTpHyZbLOB4vE5wOk0nZ... | 2024-08-07T07:44:16 | 2024-08-07T07:45:53 | {} | CONTRIBUTOR |
vuejs | core | 2,270,503,039 | 11,520 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ---------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 97.6 kB (**+7.46 kB**) | 37.1 kB (**+2.52 kB**) ... | 2024-08-06T06:43:05 | 2024-08-06T06:43:05 | {} | NONE |
vuejs | core | 2,272,477,119 | 11,536 | jh-leong | /ecosystem-ci run | 2024-08-07T02:01:57 | 2024-08-07T02:01:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,272,539,086 | 11,536 | yyx990803 | It's better to align the types with existing runtime behavior, since changing runtime behavior is actually breaking. | 2024-08-07T03:19:43 | 2024-08-07T03:19:43 | {} | MEMBER |
vuejs | core | 2,272,826,068 | 11,541 | liuseen-l | This seems to be as expected, because when the selected state is clicked again, the value of modelValue does not change, so the set method is not triggered. | 2024-08-07T07:40:47 | 2024-08-07T07:40:47 | {} | CONTRIBUTOR |
vuejs | core | 2,270,793,838 | 11,496 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | f8ef7337fc4f6e96663f97bb25ea946d3513bb52 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-08-06T09:16:06 | 2024-08-06T16:31:31 | {} | NONE |
vuejs | core | 2,273,031,436 | 11,544 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ---------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 90.2 kB (**-8.09 kB**) | 34.6 kB (**-2.71 kB**) ... | 2024-08-07T09:28:49 | 2024-08-07T13:41:17 | {} | NONE |
vuejs | core | 2,269,929,122 | 11,442 | mefcorvi | @jh-leong @yyx990803
It appears this PR has changed the type inference for `ref` when used with `MaybeRef`:
```
import { ref, MaybeRef } from 'vue'
const a: MaybeRef<number> = 1;
const b = ref(a); // Ref<number, MaybeRef<number>>
```
Shouldn't it be `Ref<number, number>` instead?
Consider this example ... | 2024-08-05T21:13:20 | 2024-08-05T21:13:20 | {} | CONTRIBUTOR |
vuejs | core | 2,272,583,494 | 10,537 | yyx990803 | Superseded by 63689ed
@skirtles-code that seems to be a separate topic from this PR - the current behavior of Vue custom elements always reflect declared props as attribute if it has a value, so this PR (and by extension 63689ed) just aligns default values with that behavior. | 2024-08-07T04:14:32 | 2024-08-07T04:14:32 | {} | MEMBER |
vuejs | core | 2,179,948,003 | 11,178 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 98.3 kB | 37.3 kB | 33.5 kB |
| vue.global.prod.js | 156 kB | 57 kB | 50.7 kB |
### Usages
| Name | Size |... | 2024-06-20T06:53:03 | 2024-08-07T11:56:27 | {} | NONE |
vuejs | core | 2,273,582,735 | 11,547 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ----------------- | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 90.2 kB | 34.6 kB (**+3 B**) | 31.2 kB (**+4 B**) |
| vue.glo... | 2024-08-07T14:14:36 | 2024-08-07T14:14:36 | {} | NONE |
vuejs | core | 2,269,009,633 | 6,610 | yyx990803 | superseded by #11517 | 2024-08-05T12:54:58 | 2024-08-05T12:54:58 | {} | MEMBER |
vuejs | core | 2,270,659,033 | 11,521 | Disservin | Workaround just specify the v-if on the slot directly.
```html
<template #item v-if="slots?.default">
<slot />
</template>
``` | 2024-08-06T08:13:45 | 2024-08-06T08:13:45 | {} | CONTRIBUTOR |
vuejs | core | 2,270,796,425 | 11,496 | kakkokari-gtyih | https://github.com/vuejs/core/pull/11496#issuecomment-2270793838 seems nothing to do with the content of the PR | 2024-08-06T09:17:20 | 2024-08-06T09:17:20 | {} | CONTRIBUTOR |
vuejs | core | 2,270,805,067 | 11,521 | jh-leong | > However, there's a drawback that the Component which exposes the `item` slot still see's a slot being passed, which I wouldn't expect since the `v-if` condition is false.
>
> [Vue Playground](https://play.vuejs.org/#eNqtUk1P4zAQ/Suz3kNYiU2FunvptqDdFQc4AAKOllCUTorBsSN/hEpR/jtjO0mLBD0gbuN5b8Yz817H/jZN3npkC7a0pRGNA4v... | 2024-08-06T09:21:26 | 2024-08-06T09:21:26 | {} | MEMBER |
vuejs | core | 2,270,859,883 | 11,523 | edison1105 | This is expected behavior, see https://vuejs.org/guide/components/props.html#boolean-casting | 2024-08-06T09:47:34 | 2024-08-06T09:47:34 | {} | MEMBER |
vuejs | core | 2,269,039,116 | 11,516 | autofix-ci[bot] | Hi! I'm <a href="https://autofix.ci"><img alt="autofix logo" src="https://autofix.ci/logo/logo.svg" width="16"><strong>autofix.ci</strong></a>, a bot that automatically fixes trivial issues such as code formatting in pull requests.
I would like to apply some automated changes to this pull request, but it looks like I ... | 2024-08-05T13:08:39 | 2024-08-05T13:08:39 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,270,787,402 | 11,491 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | e9942d0bd17cb9c4d97ff5c5ae8505daefe71978 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-08-06T09:13:11 | 2024-08-06T09:13:11 | {} | NONE |
vuejs | core | 2,270,922,260 | 8,112 | yyx990803 | This is fixed by 79602f9ec
However note that the `getSSRProps` in the linked reproduction is incorrect - it should be:
```diff
app.directive('inner-html', {
getSSRProps(binding) {
return {
- domProps: {
- innerHTML: 'sanitizeCustom(directiveMeta.value)',
- },
+ innerHTML... | 2024-08-06T10:18:25 | 2024-08-06T10:20:03 | {} | MEMBER |
vuejs | core | 2,271,586,499 | 4,662 | yyx990803 | closed via #11517 | 2024-08-06T15:35:45 | 2024-08-06T15:35:45 | {
"hooray": 19
} | MEMBER |
vuejs | core | 2,272,586,243 | 6,131 | yyx990803 | I think in this case we have to consider `defineCustomElement` to have a different browser support baseline from other features. | 2024-08-07T04:18:23 | 2024-08-07T04:18:23 | {} | MEMBER |
vuejs | core | 2,273,613,100 | 9,883 | yyx990803 | Thanks for the PR, but I think a runtime-based approach like #7525 is more ergonomic. | 2024-08-07T14:28:02 | 2024-08-07T14:28:02 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,270,201,924 | 11,518 | edison1105 | [a workaround](https://play.vuejs.org/#__PROD__eNp9Uk1r20AQ/SvDUogMRqZuT0Y2tGkOLbQJbo57iJBG6qarWbEfqsHov3d2FckuDTlJ+96beW929iw+9X0+BBQ7UbjKqt6DQx/6gyTV9cZ6OIPFZg2GvptAHmsYobGmgxuuupEkqTLkuMp0eGuoVl4Zgn0syrwNuLpIUL9/IRicoe0FkrSYZNkK9gc4SwKISqMx16bNnrjHDt6d+ZMPpQ44PnHhf5rtpNleacZk0ASqUsDQ16XHIxuzZJV8VJP9M8RUPHEQw08A5+VvB... | 2024-08-06T01:40:41 | 2024-08-06T01:40:41 | {} | MEMBER |
vuejs | core | 2,270,465,092 | 6,277 | edison1105 | fixed since v3.4.21 via https://github.com/vuejs/core/pull/10416 | 2024-08-06T06:13:55 | 2024-08-06T06:13:55 | {} | MEMBER |
vuejs | core | 2,271,125,215 | 11,525 | skirtles-code | I've tried to reduce this reproduction down to a Playground:
- [Playground](https://play.vuejs.org/#eNp9UcFKxDAQ/ZUhpxaW7kFPZV1YZQ+KqLjejIfSzm6zpklIJmuh9N9NUq0ispDAzHtvhjczA9sYU5w8spKtXG2FIXBI3qy5Wi65Wi0nMKQhmWPsjbYEDe4rLwkGrgCaiqoSshyu1pAlBKAViu6FQlfC69siYmPO1fi3L2FnZEUYMoBhAGqFK+bagvSOrFCHLC8sBmGNGykzzhbhwfRzGFPXu... | 2024-08-06T12:03:02 | 2024-08-06T12:03:02 | {} | CONTRIBUTOR |
vuejs | core | 2,272,396,849 | 11,533 | Procrustes5 | I found this PR. I think it's probably due to the impact of moving functionality to onMounted in this change.
Can I participate in solving this problem?
https://github.com/vuejs/core/pull/8523 | 2024-08-07T00:28:44 | 2024-08-07T00:28:44 | {} | CONTRIBUTOR |
vuejs | core | 2,272,705,635 | 11,540 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.2 kB | 34.6 kB | 31.2 kB |
| vue.global.prod.js | 147 kB | 54.1 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-08-07T06:21:32 | 2024-08-07T06:21:32 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.