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 | 1,869,342,074 | 9,914 | yyx990803 | I implemented some basic treeshaking safety checks in 897112abc which allows us to actually remove the condition in 73ae6adbb | 2023-12-26T07:54:23 | 2023-12-26T07:54:23 | {} | MEMBER |
vuejs | core | 1,848,597,661 | 9,774 | sadeghbarati | List of TypeScript errors in Vue (SFC) files I faced
- [@vue/compiler-sfc] Unresolvable type: TSConditionalType
- [@vue/compiler-sfc] Unresolvable type: TSTypeQuery
- [@vue/compiler-sfc] Failed to resolve extends base type.
If this previously worked in 3.2, you can instruct the compiler to ignore this extend by a... | 2023-12-09T17:50:46 | 2023-12-28T09:03:01 | {} | NONE |
vuejs | core | 1,867,408,196 | 9,893 | lixiaofa | > This works as designed
What I want to ask is, Scope slots passed parameters, whether parameters have reactivity
| 2023-12-22T08:46:05 | 2023-12-22T08:46:27 | {} | NONE |
vuejs | core | 1,868,114,165 | 9,903 | johnsoncodehk | The problem seems to be the inconsistency between the unref behavior of defineComponent setup return and UnwrapRef.
https://play.vuejs.org/#eNp9Uk1P3DAQ/SsjX0ikbWiFetmGRS3i0ErQisLNlyg7yQacsWVP2EVR/jtjR7t8CLhE9ryXN+/NeFQ/nSseBlRLVYbad44hIA8OTEXtqVYctFpp6npnPcMIt7T1lbvGZgE+ftJpjU1HeG6FREgMEzTe9nAkukeaNNWWAkMfWjiFy4o3h... | 2023-12-22T22:45:40 | 2023-12-22T22:45:40 | {} | MEMBER |
vuejs | core | 1,869,219,268 | 9,914 | yyx990803 | Currently the only case where this is needed in prod is for the hydration mismatch flag, so I've added it in https://github.com/vuejs/core/commit/b4ebe7ae8b904f28cdda33caf87bc05718d3a08a
Still prefer to keep it as a safeguard in case we miss the condition somewhere for now, although a more fundamental solution would... | 2023-12-26T03:08:38 | 2023-12-26T03:08:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,869,409,733 | 9,923 | yyx990803 | Confirmed this is a Volar issue and fixed by https://github.com/vuejs/language-tools/commit/68c556c28fc145664bd25a8ec7bc4fc1d1d04ede (pending release) | 2023-12-26T09:39:14 | 2023-12-26T09:39:14 | {
"rocket": 1
} | MEMBER |
vuejs | core | 1,869,477,725 | 9,162 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7329137591)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7319223848) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/732... | 2023-12-26T11:34:55 | 2023-12-26T11:34:55 | {} | CONTRIBUTOR |
vuejs | core | 1,869,480,107 | 9,162 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7329163793)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7319223848) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/732... | 2023-12-26T11:39:41 | 2023-12-26T11:39:41 | {} | CONTRIBUTOR |
vuejs | core | 1,869,867,870 | 9,922 | edison1105 | like [this](https://play.vuejs.org/#eNp9U0uP2jAQ/iuuLwlSFA57o7Bqu0Jqe+iidqW95BLiAQyObfkBrBD/vWObJOyLA8Se+ebzPL450e9al3sPdEKntjFcO2LBeX1fSd5qZRw5EQOrgjQGageILsiGnMnKqJZkGJj1wCew7mIvx+ESeNFdyUZJdLV2TWaBLM9+ghCKPCsj2JdsFCArLxvHlSRKg1wo7fUzl0wd8hE5VZKQRKEHB1Id4qEMEXlWL5V3k6Wo5S4rSBZ+ET17AZuNvg4c+O9qLsEgA1ONb0G6MlU3FxBuecb4... | 2023-12-27T01:43:35 | 2023-12-27T01:43:35 | {} | MEMBER |
vuejs | core | 1,864,689,351 | 9,882 | LinusBorg | This is documented behavior so 1) it's not a bug and 2) will not be changed in Vue 3.
> The Boolean absent props will be cast to false. You can change this by setting a default for it — i.e.: default: undefined to behave as a non-Boolean prop. | 2023-12-20T15:34:57 | 2023-12-20T15:34:57 | {} | MEMBER |
vuejs | core | 1,867,978,308 | 9,039 | LinusBorg | > What about a feature flag?
something like `inheritAttrs: 'avoid-props-override'` ? (not attached to the specific name).
It seems to me it can't be a global flag (at least not exclusively) as it would easily lead to weird bugs in 3rd party components relying on it.
So it would have to be a guard implemented... | 2023-12-22T18:41:05 | 2023-12-22T18:41:05 | {} | MEMBER |
vuejs | core | 1,867,978,720 | 9,039 | LinusBorg | > Duplicate of #6325 ?
Seems to be, yes. We might want to close that old one as this one here already has a good chunk of discussion now. | 2023-12-22T18:41:40 | 2023-12-22T18:41:40 | {} | MEMBER |
vuejs | core | 1,868,589,004 | 9,363 | xesxen | bump :) | 2023-12-24T20:30:24 | 2023-12-24T20:30:24 | {} | CONTRIBUTOR |
vuejs | core | 1,869,220,599 | 9,916 | yyx990803 | @edison1105 I think we need two changes:
1. Do not set `deep` to `true` if the user option explicitly has `deep: false`
2. If the source is reactive **and** is shallow, we should use a shallow traverse (i.e. only traverse the root level). | 2023-12-26T03:12:27 | 2023-12-26T03:12:27 | {
"heart": 2
} | MEMBER |
vuejs | core | 1,868,468,195 | 9,909 | codspeed-hq[bot] | ## [CodSpeed Performance Report](https://codspeed.io/vuejs/core/branches/RicardoErii:feat/setup-ref-type)
### Merging #9909 will **not alter performance**
<sub>Comparing <code>RicardoErii:feat/setup-ref-type</code> (fa5bf44) with <code>main</code> (a8d0b1b)</sub>
### Summary
`✅ 53` untouched benchmarks
| 2023-12-24T09:03:56 | 2023-12-26T03:52:55 | {} | NONE |
vuejs | core | 1,866,568,025 | 9,889 | codspeed-hq[bot] | ## [CodSpeed Performance Report](https://codspeed.io/vuejs/core/branches/Alfred-Skyblue:chore/vitest/type-deprecated)
### Merging #9889 will **not alter performance**
<sub>Comparing <code>Alfred-Skyblue:chore/vitest/type-deprecated</code> (a0db20c) with <code>main</code> (9fa8241)</sub>
### Summary
`✅ 53` untouch... | 2023-12-21T16:04:51 | 2023-12-21T16:04:51 | {} | NONE |
vuejs | core | 1,867,310,334 | 9,896 | Alfred-Skyblue | Due to the mutability of object properties, `required` is inferred as a `boolean` type, and it may be `false`. Therefore, you need to apply a constant assertion to `props` to ensure that `required` can be inferred as `true`.
```ts
const props = {
data: {
required: true,
type: Array as PropType<numb... | 2023-12-22T06:53:51 | 2023-12-22T06:53:51 | {} | MEMBER |
vuejs | core | 1,867,715,472 | 9,875 | yyx990803 | Hmm, I think it's better to correct the enum value to match the key and the docs (the missing `S` was a mistake) | 2023-12-22T13:54:46 | 2023-12-22T13:54:46 | {} | MEMBER |
vuejs | core | 1,869,259,295 | 9,920 | edison1105 | @johnsoncodehk done~ | 2023-12-26T05:09:44 | 2023-12-26T05:09:44 | {} | MEMBER |
vuejs | core | 1,864,713,946 | 9,882 | LinusBorg | You can define a default in `defineModel()` just like you can for the normal Boolean prop. I don't think it's desirable to switch the behavior for `defineModel<boolean>()` only, that will only cause more confusion. | 2023-12-20T15:46:24 | 2023-12-20T15:46:24 | {} | MEMBER |
vuejs | core | 1,864,741,287 | 4,428 | jcbond92 | I have a [PR up](https://github.com/vuejs/core/pull/9883) that addresses this issue (at least partially) for custom elements.
It allows you to specify a `v-model` type for different custom elements (like `checkbox`, `radio`, etc.). Library authors will need to mirror native input props (e.g. `value`, `checked`) and ... | 2023-12-20T16:02:28 | 2023-12-20T16:11:58 | {} | NONE |
vuejs | core | 1,864,756,824 | 9,884 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 87.1 kB | 33.1 kB | 29.9 kB |
| vue.global.prod.js | 133 kB | 50 kB | 44.8 kB |
### Usages
| Name | Size |... | 2023-12-20T16:12:22 | 2023-12-20T16:12:22 | {} | NONE |
vuejs | core | 1,864,449,891 | 9,871 | edison1105 | <s>a [workaround](http://localhost:5173/#__DEV__eNrFVV1v0zAU/StWXppKbSKYEFLIitgY0niACao95SVLbtoMx7ZsJ+1U9b9zbeer67qBJsRLFfsen3vv8bnuzvskRNDU4EVerDJZCk0U6FoQmrLVeeJplXiLhIUhgUroh4SVleBSk9vLNWS/7viWFJJXZBKEbsdwTT4MsGsmaj1g7PIRZkckFGTfgtpYwjLOlCZZm+Y2pTWQcwP1taxhihiH0LDV4+hkYmJx6LrB2nGhsXiaasAVIXFeNvaDkCspuSRv3SIeeooaQ4jt... | 2023-12-20T13:11:11 | 2023-12-22T07:01:24 | {} | MEMBER |
vuejs | core | 1,867,528,029 | 9,892 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 87.1 kB | 33.1 kB | 29.9 kB |
| vue.global.prod.js | 133 kB | 50 kB | 44.8 kB |
### Usages
| Name | Size |... | 2023-12-22T10:40:28 | 2023-12-22T10:40:28 | {} | NONE |
vuejs | core | 1,868,704,401 | 9,871 | edison1105 | Never mind! The problem should have been fixed by https://github.com/vuejs/core/commit/03aa0d4b9fa507e3396723f6eb7fd452cc62abf4.
But it's weird, the problem still happens on the [local playground](http://localhost:5173/#__DEV__eNq9VV1vmzAU/SsWLyFSBtL6ltFMa9dJ3cNWbVGfeKFwSemMjWyTpIry33evDYY2bTJtWt+w7/G5536yCz41TbRuIZ... | 2023-12-25T03:42:01 | 2023-12-25T03:42:01 | {} | MEMBER |
vuejs | core | 1,869,234,495 | 9,909 | yyx990803 | Looks like the previous complication was introduced in https://github.com/vuejs/core/pull/4100, which is also fixed by having the extra distribute type, so the distribute type itself can be simplified.
I also added tests in [fa5bf44](https://github.com/vuejs/core/pull/9909/commits/fa5bf44519e5349e8b51bdc65f91fdabd64... | 2023-12-26T03:57:20 | 2023-12-26T03:57:20 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,869,235,504 | 9,909 | yangxiuxiu1115 | It looks like it is, thanks | 2023-12-26T04:00:39 | 2023-12-26T04:00:39 | {} | CONTRIBUTOR |
vuejs | core | 1,869,236,847 | 9,919 | yyx990803 | We also have https://github.com/vuejs/core/pull/9894 which expands the asset url scenarios - anything that might be affected there? | 2023-12-26T04:04:23 | 2023-12-26T04:04:23 | {} | MEMBER |
vuejs | core | 1,869,495,043 | 9,916 | edison1105 | Is it possible to fix it based on this PR: https://github.com/vuejs/core/pull/9572/files. It does something similar.
/cc @Alfred-Skyblue | 2023-12-26T12:06:39 | 2023-12-26T12:07:17 | {
"eyes": 1
} | MEMBER |
vuejs | core | 1,865,417,962 | 9,877 | alexzhang1030 | Should it be supported in the future, or it be designed thus? | 2023-12-21T03:16:09 | 2023-12-21T03:16:09 | {
"+1": 1,
"eyes": 1,
"heart": 1,
"hooray": 1,
"rocket": 1
} | MEMBER |
vuejs | core | 1,867,437,102 | 9,897 | LinusBorg | We can't debug 3rd party libraries. Please open a new issue when you can reproduce the problem with Vue core alone. if you can't, I suggest opening an issue with the 3rd party library. | 2023-12-22T09:15:07 | 2023-12-22T09:15:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,867,777,637 | 9,890 | yyx990803 | Closed via 7aa3f250f | 2023-12-22T14:51:51 | 2023-12-22T14:51:51 | {} | MEMBER |
vuejs | core | 1,868,621,714 | 9,910 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 87.1 kB | 33.1 kB | 29.9 kB |
| vue.global.prod.js | 133 kB | 50 kB | 44.8 kB |
### Usages
| Name | Size |... | 2023-12-25T00:19:52 | 2023-12-25T00:19:52 | {} | NONE |
vuejs | core | 1,868,894,581 | 9,818 | Leopoldthecoder | Hi @baiwusanyu-c @HcySunYang , could you help review this PR? Thanks! | 2023-12-25T09:46:33 | 2023-12-25T09:46:33 | {} | CONTRIBUTOR |
vuejs | core | 1,847,167,743 | 9,502 | codspeed-hq[bot] | ## [CodSpeed Performance Report](https://codspeed.io/vuejs/core/branches/renovate/build)
### Merging #9502 will **not alter performance**
<sub>Comparing <code>renovate/build</code> (136371b) with <code>main</code> (a8d0b1b)</sub>
### Summary
`✅ 53` untouched benchmarks
| 2023-12-08T13:29:12 | 2023-12-25T10:33:31 | {} | NONE |
vuejs | core | 1,869,344,468 | 9,914 | brc-dd | Thanks! 🙏 | 2023-12-26T07:58:21 | 2023-12-26T07:58:21 | {} | MEMBER |
vuejs | core | 1,871,187,355 | 9,927 | LittleSound | I ran vitest bench, my modified apiWatch seems to be slower than the original apiWatch. However, I don't have experience in optimizing its performance. Are there any tips or documents that I can refer to?
#### Minor
##... | 2023-12-28T13:39:12 | 2023-12-28T13:39:31 | {} | MEMBER |
vuejs | core | 2,448,546,685 | 12,287 | KamilOcean | Hi, @Mefinst !
May be I get something wrong, but I think the problem is that you are trying to apply CSS classes outside of incapsulated shadowDOM to that shadowDOM element. But as I know it doesn't work by the nature of native elements' incapsulation concept.
There are special techniques for this case. I've chan... | 2024-10-30T22:10:40 | 2024-10-30T22:10:40 | {
"+1": 1
} | NONE |
vuejs | core | 2,449,139,397 | 12,298 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/26530eb0-d607-496f-be90-3bf67a34c9f9)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12298
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-10-31T06:49:24 | 2024-10-31T06:49:24 | {} | NONE |
vuejs | core | 2,451,403,334 | 12,302 | ludwig801 | > Closing as a duplicate of #2981. As a workaround, see: [#2981 (comment)](https://github.com/vuejs/core/issues/2981#issuecomment-1831724017)
I do not believe this is a duplicate, for the following reason: using `ref<Class>` works as intended, and Class is not unwrapped. Using `ref<Class[]>` does unwrap Class. In th... | 2024-11-01T07:00:09 | 2024-11-01T07:00:09 | {} | NONE |
vuejs | core | 2,453,012,334 | 12,313 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/dfe3d65a-da7c-48ae-8aef-92a0f07e066d)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12313
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-02T14:44:51 | 2024-11-02T14:44:51 | {} | NONE |
vuejs | core | 2,453,670,283 | 12,316 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 159 kB | 57.9 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-11-04T01:09:08 | 2024-11-04T01:09:08 | {} | NONE |
vuejs | core | 2,440,017,422 | 12,272 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/9d7da263-a462-4ea6-9525-87fd2aa68dd3)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12272
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-10-27T13:14:30 | 2024-10-30T09:05:43 | {} | NONE |
vuejs | core | 2,446,295,196 | 12,286 | jacobg | Thanks @edison1105 .
Your workaround does indeed seem fix that error.
It does seem though that the error wasn't caused by something about `markRaw` changing when updating from Vue 3.4 to 3.5, because I'm also getting a couple other errors when building non-typescript sfc's as follows:
```
src/components/Chart... | 2024-10-30T09:22:55 | 2024-10-30T09:22:55 | {} | NONE |
vuejs | core | 2,447,353,953 | 11,788 | artem-schander | is this fix already released? sorry if its a dumb question, i have no idea how to find it out myself | 2024-10-30T14:32:02 | 2024-10-30T14:32:02 | {} | NONE |
vuejs | core | 2,451,170,684 | 11,014 | edison1105 | The currently supported usage is to tell the compiler the global type explicitly.
```ts
vue({
script: {
globalTypeFiles: [
'./src/types/global.d.ts'
]
}
})
```
and
```ts
//src/types/global.d.ts
declare global {
type MyNumber = number
}
``` | 2024-11-01T02:21:47 | 2024-11-01T02:21:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,440,819,851 | 12,280 | edison1105 | It looks like this is a good feature, but the implementation is not quite right. I think it should handle `!foo` as `foo="false"` during compilation, rather than modifying the runtime code.
the following code
```vue
<Comp !stat/>
```
compiled to
```js
_createVNode($setup["Comp"], { "stat": false })
```
ins... | 2024-10-28T08:09:32 | 2024-10-29T01:06:00 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,444,186,626 | 12,291 | ferferga | I can't reproduce, I believe it's not GCed directly because the size is really small. See this modiification, where I add a huge array at setup function and switch to production:
https://play.vuejs.org/#__PROD__eNqVVG1v2jAQ/itePoWJhNdpXQZVacuHTtNWtbTSpEgoSy7g1nEi26FFiP++sx0DlVDLPkBs33N3z52f88abVFW4qsGLvNGnIIg5+UwuJr... | 2024-10-29T13:12:12 | 2024-10-29T13:12:12 | {} | CONTRIBUTOR |
vuejs | core | 2,447,042,224 | 12,293 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 100 kB (**-47 B**) | 38 kB (**+9 B**) | 34.2 kB (**+36 B**) |
| vue.... | 2024-10-30T12:50:32 | 2024-10-30T12:50:32 | {} | NONE |
vuejs | core | 2,448,919,139 | 12,288 | edison1105 | > I'm not sure if this is really the best way, because it required me to modify the transition.html file and add a new function in e2eUtils.ts. I couldn't think of an easier and less intrusive way to check for reflow reliably. _Maybe_ it's possible to do so with just classes, but I tried that multiple times with no suc... | 2024-10-31T02:56:23 | 2024-10-31T02:56:35 | {} | MEMBER |
vuejs | core | 2,449,365,257 | 6,752 | edison1105 | It is not the same as #6080 and #6238 is not fixed this one.
see [Playground with 6238](https://deploy-preview-6238--vue-sfc-playground.netlify.app/#__PROD__eNp9kk1vEzEQhv/K4EtB6u4iAZewjYCqIJD4EHD0xWxmE7de27Jnt4mi/HfG9iZppao3z8zzjsevZy8+el9PI4qFaGMXtCeISKNfSqsH7wLBHgL2cIA+uAEuGL04lb7vrjfarOZS3cxx6seQtJ2zkftt3D1cpS4ve2... | 2024-10-31T09:02:49 | 2024-10-31T09:02:49 | {} | MEMBER |
vuejs | core | 2,453,756,403 | 12,320 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 159 kB | 57.9 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-11-04T03:17:54 | 2024-11-04T03:17:54 | {} | NONE |
vuejs | core | 2,446,110,280 | 12,291 | ysswebdev | @edison1105 Thank you for your answer. Is there any other solution to this problem? I tested the situation of using the third-party element-plus and replaced the input tag with el-input alone, which produced the same result and would not be released. However, if the el-input tag is wrapped with the el-form tag, if ther... | 2024-10-30T08:03:37 | 2024-10-30T08:03:37 | {} | NONE |
vuejs | core | 2,449,138,155 | 12,298 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| v... | 2024-10-31T06:49:13 | 2024-10-31T06:49:13 | {} | NONE |
vuejs | core | 2,449,279,748 | 11,239 | edison1105 | duplicate of https://github.com/vuejs/core/issues/4662
It has been fixed via https://github.com/vuejs/core/pull/11517
see https://stackblitz.com/edit/vitejs-vite-pkmdzu?file=package.json | 2024-10-31T08:11:37 | 2024-10-31T08:12:21 | {} | MEMBER |
vuejs | core | 2,432,019,290 | 12,247 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/9166658a-4485-4651-ab38-d30138db2dd3)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12247
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-10-23T12:38:09 | 2024-10-31T10:16:48 | {} | NONE |
vuejs | core | 2,452,483,739 | 12,301 | KazariEX | @edison1105 How do you think we should handle this feature? https://github.com/vuejs/language-tools/pull/4971#issuecomment-2452434659 | 2024-11-01T19:41:55 | 2024-11-01T19:41:55 | {} | MEMBER |
vuejs | core | 2,453,667,623 | 12,317 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/c5cd032e-f348-497f-ba8a-6629c8445e18)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12317
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-04T01:04:52 | 2024-11-04T01:04:52 | {} | NONE |
vuejs | core | 2,443,419,248 | 4,704 | edison1105 | Thanks for your contribution. But this PR is outdated. The `VNodeKey` type has been replaced by `PropertyKey`. | 2024-10-29T07:20:41 | 2024-10-29T07:20:41 | {} | MEMBER |
vuejs | core | 2,443,988,639 | 12,286 | jacobg | The error doesn't come up when running `npm run dev`, only `npm run build`. Isn't that what a sandbox repro would do?
Should I create a github repo for it, or upload a zip file? | 2024-10-29T11:46:45 | 2024-10-29T11:46:45 | {} | NONE |
vuejs | core | 2,447,488,990 | 12,288 | Tadehz | I'm not sure if this is really the best way, because it required me to modify the transition.html file and add a new function in e2eUtils.ts. I couldn't think of an easier and less intrusive way to check for reflow reliably. _Maybe_ it's possible to do so with just classes, but I tried that multiple times with no succe... | 2024-10-30T15:13:55 | 2024-10-30T15:15:31 | {} | CONTRIBUTOR |
vuejs | core | 2,453,096,008 | 12,288 | Tadehz | > > I'm not sure if this is really the best way, because it required me to modify the transition.html file and add a new function in e2eUtils.ts. I couldn't think of an easier and less intrusive way to check for reflow reliably. _Maybe_ it's possible to do so with just classes, but I tried that multiple times with no s... | 2024-11-02T18:59:54 | 2024-11-02T19:02:23 | {} | CONTRIBUTOR |
vuejs | core | 2,453,744,231 | 10,815 | edison1105 | As @bsuooo said. | 2024-11-04T03:00:42 | 2024-11-04T03:00:42 | {} | MEMBER |
vuejs | core | 2,453,756,202 | 12,319 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/f1e03264-6c71-4f6c-abbd-264b68249a4c)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12319
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-04T03:17:37 | 2024-11-04T03:17:37 | {} | NONE |
vuejs | core | 2,453,899,634 | 10,365 | edison1105 | Using the provided reproduction steps, I encountered the following error.
But this error is not caused by Vue. The following code causes it:
```js
export class ShadowElement extends HTMLElement{
constructor(
temp... | 2024-11-04T06:17:58 | 2024-11-04T06:17:58 | {} | MEMBER |
vuejs | core | 2,444,181,632 | 12,291 | edison1105 | As you can see it hold by C++ persistent roots. It's a chrome bug. Duplicate of #11552 | 2024-10-29T13:10:00 | 2024-10-29T13:11:00 | {} | MEMBER |
vuejs | core | 2,451,498,500 | 12,302 | jh-leong | From what I understand, the limitation on unwrapping private fields is still present: [Playground](https://play.vuejs.org/#eNqNU1Fr2zAQ/isXvSSFzlka9hKcwDY6tj1sYxvsIQrDOGdbrSwJSXZSjP/7ToqdNaV0A2Oku+87fd/p1LG3xiRtg2zFUpdbYTw49I0BmalyzZl3nG24ErXR1kMHFgvoobC6hinRplxxlWvlPNSuhHXIz6YfUUoNv7SV+8n0KkA6rgBymTkHH7SGuAUwVrSZRygot... | 2024-11-01T08:24:12 | 2024-11-01T08:24:12 | {} | MEMBER |
vuejs | core | 2,451,603,024 | 12,306 | linzhe141 | When I repeated the above reproduce steps and take heap snapshot, I found that there were many detached HTML elements, and these HTML elements were referenced by vnode
The above operations are all in the prod environment
 | 2024-11-01T09:44:38 | 2024-11-01T09:44:38 | {} | MEMBER |
vuejs | core | 2,451,930,828 | 12,307 | DrWarpMan | So you have to manually specify it, it can't get inferred? | 2024-11-01T14:05:57 | 2024-11-01T14:05:57 | {} | NONE |
vuejs | core | 2,394,926,477 | 12,110 | KazariEX | ~~Solution in https://github.com/vuejs/core/issues/12012#issuecomment-2377956415~~ | 2024-10-05T04:54:23 | 2024-11-02T09:14:16 | {} | MEMBER |
vuejs | core | 2,443,125,741 | 12,288 | edison1105 | /ecosystem-ci run | 2024-10-29T03:29:12 | 2024-10-29T03:29:12 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,444,791,698 | 12,286 | jacobg | @edison1105
Here is a repo link that reproduces it:
https://github.com/jacobg/vue-project-ts
Note that HelloWorld.vue is a non-typescript sfc.
If you clone, and run:
```
npm i
npm run build
```
These errors should occur:
```
src/components/HelloWorld.vue:1:1 - error TS9006: Declaration emit for this... | 2024-10-29T16:34:25 | 2024-10-29T16:34:25 | {} | NONE |
vuejs | core | 2,447,042,173 | 12,293 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/8ae206cd-66c1-40cc-b875-52ad36be5e1f)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12293
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-10-30T12:50:31 | 2024-10-30T12:50:31 | {} | NONE |
vuejs | core | 2,319,589,156 | 6,238 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/bf7c768b-ba14-4b92-a1bc-6c755dec0bda)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@6238
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.p... | 2024-08-30T00:58:53 | 2024-10-31T08:58:59 | {} | NONE |
vuejs | core | 2,450,083,263 | 8,015 | MarkusJLechner | I just stumbled upon this issue, but unfortunately, there's no solution yet. This issue has been open for over a year; it's quite a specific problem and might not be resolved anytime soon.. | 2024-10-31T14:51:10 | 2024-10-31T14:51:10 | {} | NONE |
vuejs | core | 2,453,554,008 | 12,306 | chibx | > This seems to be a Chrome bug.
>
> 1. Create an HTML file with the following code.
> 2. Open the HTML file and take a heap snapshot.
> 3. Click the "show" button.
> 4. Click the "test" button.
> 5. Click the "remove" button.
> 6. Click "GC" and take another heap snapshot.
> 7. Compare the snapshots, there ar... | 2024-11-03T19:42:26 | 2024-11-03T19:42:26 | {
"+1": 1
} | NONE |
vuejs | core | 2,453,667,410 | 12,316 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/34e91675-5921-4799-8ae4-b31e0df46023)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12316
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-04T01:04:29 | 2024-11-04T01:04:29 | {} | NONE |
vuejs | core | 2,442,952,643 | 12,289 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/54968ef1-b2d0-4185-9462-8055a02d9665)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12289
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
pnpm add https://pkg.... | 2024-10-29T00:59:15 | 2024-10-29T00:59:15 | {} | NONE |
vuejs | core | 2,449,059,235 | 11,296 | edison1105 | This behavior is different from vue2.
see https://codesandbox.io/p/sandbox/vue-2-playground-forked-2jn5f7?workspaceId=28b40334-b6d1-4971-a748-f2552025b31c | 2024-10-31T05:58:04 | 2024-10-31T05:58:04 | {} | MEMBER |
vuejs | core | 2,449,292,904 | 11,078 | edison1105 | The issue can no longer be reproduced using the latest version of Vue.
see https://stackblitz.com/edit/nuxt-issues-27454-6qv6vm?file=package.json | 2024-10-31T08:20:12 | 2024-10-31T08:20:12 | {} | MEMBER |
vuejs | core | 2,449,333,662 | 9,559 | edison1105 | `render()` 每次都会生成一个新的组件，导致不会被缓存。 | 2024-10-31T08:45:03 | 2024-10-31T08:45:03 | {} | MEMBER |
vuejs | core | 2,451,871,326 | 10,935 | edison1105 | Considering that SVGElement can also apply animations, we cannot directly change the Element type to HTMLElement. | 2024-11-01T13:26:44 | 2024-11-01T13:26:44 | {} | MEMBER |
vuejs | core | 2,452,471,889 | 12,311 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38 kB | 34.2 kB |
| vue.global.prod.js | 159 kB | 57.9 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-11-01T19:32:33 | 2024-11-01T19:32:33 | {} | NONE |
vuejs | core | 2,452,472,080 | 12,311 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/46de07fb-b3f0-4afd-a755-bad7c3518069)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12311
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-11-01T19:32:40 | 2024-11-01T19:32:40 | {} | NONE |
vuejs | core | 2,452,963,489 | 12,012 | KazariEX | Please define a generic type used by union props as a workaround:
```vue
<script setup lang="ts" generic="T extends {
foo: string
} | {
foo?: number
bar: boolean
} | {
baz: boolean
}">
defineProps<T>();
</script>
``` | 2024-11-02T11:44:44 | 2024-11-02T11:44:44 | {} | MEMBER |
vuejs | core | 2,440,777,139 | 12,279 | edison1105 | ~~There is a bug of v7.0.0.
I've created [an issue](https://github.com/postcss/postcss-selector-parser/issues/297) in postcss-selector-parser's repository~~ | 2024-10-28T07:46:13 | 2024-10-29T01:03:13 | {} | MEMBER |
vuejs | core | 2,443,399,661 | 4,955 | edison1105 | Could you please resolve the conflicts? | 2024-10-29T07:14:41 | 2024-10-29T07:14:41 | {} | MEMBER |
vuejs | core | 2,445,717,752 | 12,294 | maxbogue | Sorry about that; I've fixed the link. | 2024-10-30T02:52:25 | 2024-10-30T02:52:25 | {} | NONE |
vuejs | core | 2,446,014,848 | 12,291 | edison1105 | 
As you mentioned, I deployed a project locally and indeed, the issue can be reproduced. However, this is indeed a bug in Chrome. | 2024-10-30T07:00:42 | 2024-10-30T07:00:42 | {} | MEMBER |
vuejs | core | 2,449,487,275 | 12,299 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 100 kB (**+24 B**) | 38 kB (**+8 B**) | 34.2 kB (**+19 B**) |
| v... | 2024-10-31T10:06:57 | 2024-10-31T12:44:05 | {} | NONE |
vuejs | core | 2,451,924,753 | 12,307 | edison1105 | should be
```ts
const FunctionalComponent = () => h(Comp<string>, {
modelValue: foo.value,
['onUpdate:modelValue']: (val) => foo.value = val,
});
``` | 2024-11-01T14:02:18 | 2024-11-01T14:02:18 | {} | MEMBER |
vuejs | core | 2,443,440,747 | 4,331 | edison1105 | Could you please resolve the conflicts? | 2024-10-29T07:24:45 | 2024-10-29T07:24:45 | {} | MEMBER |
vuejs | core | 2,443,988,141 | 12,291 | ysswebdev | The fact is that after packaging and deployment, after clicking the change button, the input DOM element has not been released after the component is switched.
| 2024-10-29T11:46:31 | 2024-10-29T11:46:31 | {} | NONE |
vuejs | core | 2,451,153,772 | 11,034 | edison1105 | this is valid.
```vue
v-memo="[ formData[questionId] ]"
```
Closing as this is the expected behavior. | 2024-11-01T02:04:09 | 2024-11-01T02:04:09 | {} | MEMBER |
vuejs | core | 2,451,494,572 | 11,014 | NonSpicyBurrito | While this is a work around for self declared global types, it's not ideal for global types introduced by dependencies. | 2024-11-01T08:20:52 | 2024-11-01T08:20:52 | {
"+1": 1
} | NONE |
vuejs | core | 2,453,753,458 | 12,315 | YiMo1 | @edison1105
抱歉，按照你的解决方案试了下，结果在动画结束时，`.itemTransition` 类依旧存在于子元素。这是否属于另外一个Bug？ | 2024-11-04T03:13:49 | 2024-11-04T03:13:49 | {} | NONE |
vuejs | core | 2,446,211,768 | 2,133 | edison1105 | The issue can no longer be reproduced using the latest version of Vue and Firefox 131.0.3(64-bit) on MacOS.
see https://jsfiddle.net/v4tsr2q6/ | 2024-10-30T08:48:26 | 2024-10-30T08:48:26 | {} | MEMBER |
vuejs | core | 2,447,070,811 | 12,293 | edison1105 | see https://github.com/vuejs/core/pull/12293#discussion_r1822537666 | 2024-10-30T13:00:34 | 2024-10-30T13:00:34 | {} | MEMBER |
vuejs | core | 2,442,948,386 | 12,288 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/db81e7c3-b9c4-4380-9079-d0ad5b0270d3)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@12288
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://pkg.... | 2024-10-29T00:54:26 | 2024-10-31T01:15:49 | {} | NONE |
vuejs | core | 2,444,276,971 | 12,288 | Tadehz | > Could you please add a test case for this to avoid regression?
Not entirely sure how to go about it, but I will try. | 2024-10-29T13:44:37 | 2024-10-29T13:44:37 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.