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,874,879,492
9,966
yangxiuxiu1115
NB, Thank you, then I won't add test cases
2024-01-03T05:50:42
2024-01-03T05:50:42
{}
CONTRIBUTOR
vuejs
core
1,871,713,213
9,875
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 89.3 kB | 34 kB | 30.6 kB | | vue.global.prod.js | 146 kB | 53.2 kB | 47.6 kB | ### Usages | Name | Size |...
2023-12-29T04:06:04
2023-12-29T04:06:04
{}
NONE
vuejs
core
1,872,483,009
9,946
yyx990803
This should be reported to histoire.
2023-12-30T08:31:07
2023-12-30T08:31:07
{ "+1": 1 }
MEMBER
vuejs
core
1,869,636,205
9,928
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | -------------------- | ------------------- | ------------------- | | runtime-dom.global.prod.js | 89.5 kB (**+107 B**) | 34 kB (**+53 B**) | 30.7 kB (**+64 B**)...
2023-12-26T16:05:14
2023-12-30T10:49:39
{}
NONE
vuejs
core
1,872,617,188
9,335
StepanMynarik
Tried the same thing as @andredewaard , I just used: `const modelValue = defineModel<Props['modelValue']>({ required: true })` instead of: `const modelValue = defineModel<Pick<Props, 'modelValue'>>('modelValue', { required: true })` This compiles, but the property type just includes all possible types of 'modelVa...
2023-12-30T22:20:54
2023-12-30T22:20:54
{}
NONE
vuejs
core
1,872,564,873
9,949
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------------------- | ------------------- | ------------------- | | runtime-dom.global.prod.js | 89.4 kB (**-47 B**) | 34 kB (**-12 B**) | 30.7 kB (**+11 B**) | ...
2023-12-30T16:58:05
2023-12-31T09:49:59
{}
NONE
vuejs
core
1,874,911,607
9,975
zhou5631
老师来发声了,赞赞赞
2024-01-03T06:40:44
2024-01-03T06:40:44
{}
NONE
vuejs
core
1,874,925,178
9,975
cc-hearts
Can you set `effect.dirty` to true before calling `update`? For example like this: [playground](https://play.vuejs.org/#eNqNVNtO20AQ/ZWRX2IUx1abPqUB0SIqtVIB0Yonvzj2OFmwZ1d7MVTI/97ZdWJcCFKlSMnO5cyZMzN5jr4olXYOo1W0NqUWyoJB69RZTqJVUlt4Bo11AqXGwuLdlawwYQtVqKEwcOfwNjwSkPRTOrJYJbCDHmotW5gx9GyEupCt2tvTzD985dnnnBq0QK6FU/iQU...
2024-01-03T06:56:21
2024-01-03T06:56:21
{}
NONE
vuejs
core
1,872,503,640
9,928
yyx990803
@Alfred-Skyblue I like the depth idea, but it is a feature so I refactored this PR to use your depth-based `traverse` so we can land the fix in a patch sooner.
2023-12-30T10:49:57
2023-12-30T10:49:57
{ "heart": 2 }
MEMBER
vuejs
core
1,872,568,215
9,247
felix-berlin
Hey, got the same error on an Vue + Astro project. I tried to solve the warning with `compilerOptions.isCustomElement`, but had no luck. [Link to my Astro Issue](https://github.com/withastro/astro/issues/9549).
2023-12-30T17:16:57
2023-12-30T17:16:57
{}
NONE
vuejs
core
1,872,833,726
9,933
logotip4ik
@edison1105 Can you reopen issue ? Still can see error if pass a list rendering (`v-for`) to slot, here's demo: https://play.vuejs.org/#__SSR__eNqNU01vm0AQ/SvTveRi4OCcXDdKW0VVe2ir1lIvXCiMzSbsh3YH7Arx3zsLxCaERDnBzntvvvZtKz5aGzc1io3Y+txJS+CRanuTaqmscQR/XGYtOtg7o+AqTsZzEF29v7AklV+cqe3OZdpLkkZfFM+xR/U2GYpyOT4QKltlhHwC2L...
2023-12-31T08:13:44
2023-12-31T08:13:44
{}
NONE
vuejs
core
1,873,138,762
9,962
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB | | vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB | ### Usages | Name | Size |...
2024-01-01T03:59:52
2024-01-01T03:59:52
{}
NONE
vuejs
core
1,873,138,862
9,963
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB | | vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB | ### Usages | Name | Size |...
2024-01-01T04:00:13
2024-01-01T04:00:13
{}
NONE
vuejs
core
1,875,123,664
9,948
yyx990803
I took a deeper look and this is already guarded by this line here https://github.com/vuejs/core/blob/main/packages/runtime-core/src/apiWatch.ts#L333 so it should be safe to remove.
2024-01-03T10:11:04
2024-01-03T10:11:04
{}
MEMBER
vuejs
core
1,871,301,780
9,912
pikax
@aibayanyu20 The link to minimal reproduction is an PR, please provide exactly what issue you're having, since there's no reproduction there.
2023-12-28T16:01:55
2023-12-28T16:01:55
{}
MEMBER
vuejs
core
1,872,481,679
9,947
ATQQ
I had the same problem,when I use `vue-command-palette@0.1.4` in Vue@latest (3.4.1) ```ts import { Command } from 'vue-command-palette' ``` ```vue <Command.Dialog> <!-- xxx --> </Command.Dialog> ``` A screenshot of my error is below ![image](https://github.com/vuejs/core/assets/42485491/1be99507-c1...
2023-12-30T08:22:17
2023-12-30T08:23:27
{}
NONE
vuejs
core
1,872,504,528
9,572
yyx990803
Now have some conflicts after #9928 Also, I think it might be more concise to simply allow passing a number to `deep`, since the presence of `depth` implies `deep: true`: ```js // infinite depth watch(src, () => {}, { deep: true }) // explicit depth watch(src, () => {}, { deep: 1 }) ```
2023-12-30T10:56:09
2023-12-30T10:56:09
{}
MEMBER
vuejs
core
1,872,672,842
9,916
Alfred-Skyblue
@jods4 You can still use `deep: true` to deeply watch `shallowReactive`, and it will trigger the following logic: https://github.com/vuejs/core/blob/8f85b6da442cec326c22418ead6486e914245656/packages/runtime-core/src/apiWatch.ts#L296-L299 [playground](https://play.vuejs.org/#eNp9Uk1PwzAM/StWLi2i6oS4VR3iQxzgAAg45hI...
2023-12-31T05:11:19
2023-12-31T05:11:19
{}
MEMBER
vuejs
core
1,872,903,963
9,916
yyx990803
@jods4 `deep: true` is still respected if explicitly passed on a shallow reactive source. That said, it does occur to me that we are double-traversing in this case. I've updated the code to avoid the double traverse when `deep: true` is passed, and also added a test case for `deep: true` + shallowReactive source in 24d...
2023-12-31T09:31:35
2023-12-31T09:31:35
{}
MEMBER
vuejs
core
1,874,791,107
8,341
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------------------- | ------------------- | ------------------- | | runtime-dom.global.prod.js | 89.5 kB (**+31 B**) | 34 kB (**+11 B**) | 30.7 kB (**+14 B**) | ...
2024-01-03T02:55:43
2024-01-03T02:55:43
{}
NONE
vuejs
core
1,875,067,499
9,965
yyx990803
This is indeed a bigger breaking change than expected, so I think it's best to revert the change. For #9916 - we can still use `deep: false` to only traverse the root level of shallow reactive arrays. And we can still have a full flexibility after we merge and release #9572 in a minor.
2024-01-03T09:27:22
2024-01-03T09:27:22
{}
MEMBER
vuejs
core
1,875,074,472
9,953
yyx990803
Did the same in 24d77c25c - thanks!
2024-01-03T09:32:29
2024-01-03T09:32:29
{}
MEMBER
vuejs
core
1,875,094,239
9,970
yyx990803
Thanks for the PR - for some reason it seems to be including commits that shouldn't belong (maybe because the PR was based off `main`). I've reverted SCSS source map handling to the old behavior in 71d3121b7.
2024-01-03T09:47:26
2024-01-03T09:47:26
{}
MEMBER
vuejs
core
1,871,729,489
7,506
qkreltms
Using "window.location.href" could resolve error
2023-12-29T04:59:52
2023-12-29T04:59:52
{}
NONE
vuejs
core
1,872,573,397
9,950
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------------------- | ------------------- | ------------------- | | runtime-dom.global.prod.js | 89.5 kB (**+36 B**) | 34 kB (**+11 B**) | 30.7 kB (**+10 B**) | ...
2023-12-30T17:50:12
2023-12-30T17:50:12
{}
NONE
vuejs
core
1,873,094,974
9,959
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB | | vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB | ### Usages | Name | Size |...
2024-01-01T01:40:09
2024-01-01T01:40:09
{}
NONE
vuejs
core
1,874,281,197
9,971
sleewoo
no, rather i'm missing something, stackblitz works well after upgrading to `v3.4` looking
2024-01-02T16:51:51
2024-01-02T16:51:51
{}
NONE
vuejs
core
1,874,937,007
9,975
tangjinzhou
> Can you set `effect.dirty` to true before calling `update`? > > For example like this: [playground](https://play.vuejs.org/#eNqNVNtO20AQ/ZWRX2IUx1abPqUB0SIqtVIB0Yonvzj2OFmwZ1d7MVTI/97ZdWJcCFKlSMnO5cyZMzN5jr4olXYOo1W0NqUWyoJB69RZTqJVUlt4Bo11AqXGwuLdlawwYQtVqKEwcOfwNjwSkPRTOrJYJbCDHmotW5gx9GyEupCt2tvTzD985dnnnBq0QK6...
2024-01-03T07:12:32
2024-01-03T07:13:21
{ "heart": 8 }
CONTRIBUTOR
vuejs
core
1,871,840,776
8,844
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 89.3 kB | 34 kB | 30.6 kB | | vue.global.prod.js | 146 kB | 53.2 kB | 47.6 kB | ### Usages | Name | Size |...
2023-12-29T08:36:33
2023-12-29T08:36:33
{}
NONE
vuejs
core
1,871,944,248
9,940
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 89.3 kB | 34 kB | 30.6 kB | | vue.global.prod.js | 146 kB | 53.2 kB | 47.6 kB | ### Usages | Name | Size |...
2023-12-29T10:49:30
2023-12-29T10:49:30
{}
NONE
vuejs
core
1,871,957,325
9,940
Alfred-Skyblue
Sorry, I didn't find that you have created this PR. I found in #9942 that adjusting the order of overloads can solve this problem, which can reduce unnecessary overloads. Of course, I don't know if my solution in #9942 is reasonable. If you think it is better to add an overload, I can turn close #9942.
2023-12-29T11:08:21
2023-12-29T11:08:21
{ "+1": 2 }
MEMBER
vuejs
core
1,872,403,722
9,940
yyx990803
I think #9942 is simpler than adding a dedicated overload.
2023-12-30T00:22:48
2023-12-30T00:22:48
{ "+1": 1 }
MEMBER
vuejs
core
1,874,164,059
9,966
yangxiuxiu1115
I am not very familiar with e2e testing, this is [playground](https://play.vuejs.org/#eNp9kslqwzAQhl9l0MUOGJvSW3ACbumhhS60Pepi7Emq1paEliyEvHtHcmOndLnN8s3wz3Jgldb5xiObs9I2RmgHFp3XSy5Fr5VxUNm9bK5Vr2FlVA9JXoyRi1CZjOQBXrzVKC1moOS98tJhm4HBFRy/igeey0ZJ66CtXQ2LAKRJsJMZl2Nhms5gsYQDlxDBfFN3HglPokFtjoSXxaCa9JLjsNdd7ZA8gPKkJnrkT5...
2024-01-02T15:21:39
2024-01-02T15:21:39
{}
CONTRIBUTOR
vuejs
core
1,874,795,657
7,776
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed. | Name | Link | |:-:|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 7be86427521a508b5cceff1db79bf1bedbbdf467 | |<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s...
2024-01-03T03:06:15
2024-01-03T03:06:15
{}
NONE
vuejs
core
1,874,800,411
7,502
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 89.5 kB | 34 kB | 30.7 kB | | vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB | ### Usages | Name | Size |...
2024-01-03T03:17:21
2024-01-03T03:17:21
{}
NONE
vuejs
core
1,874,900,960
7,716
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------------------- | ------------------ | ------------------- | | runtime-dom.global.prod.js | 89.5 kB (**+16 B**) | 34 kB (**+7 B**) | 30.7 kB (**+36 B**) | | v...
2024-01-03T06:24:56
2024-01-03T06:24:56
{}
NONE
vuejs
core
1,875,073,075
9,968
yyx990803
I don't think I agree. All directories under `packages` should be treated as a workspace package by `pnpm` to ensure correct dependencies. Manually listing them only creates room for error in the future (e.g. creating a new package without adding them to the workspace), and this would already require changes to [core-v...
2024-01-03T09:31:29
2024-01-03T09:31:29
{}
MEMBER
vuejs
core
2,003,941,357
6,435
mitar
But `v-html` does not work on custom components even in SPA mode, not just SSR, [see example here](https://play.vuejs.org/#eNqNUrFOwzAQ/RXLS5eSSMBUpZEAdSgDIGD00Ci9ti6ObdlOWqnKv3PnNGmrAmKyfe/53Ts/H/iDtUlTA5/wzJdO2sA8hNrmQsvKGhfYgTlYsZatnKnYCKmjAXoylT3Wk5QOpISw0KXRPrBNqBSbskW2lA0rVeH9VHCpNTjB8zmtWYpQvhA6S7vu2BcPASqrigB4Y...
2024-03-18T13:41:21
2024-03-18T13:41:21
{}
NONE
vuejs
core
2,006,997,062
4,662
matthiasPOE
anyone managed to solve this cleanly yet?
2024-03-19T12:00:41
2024-03-19T12:00:41
{ "+1": 1 }
NONE
vuejs
core
2,011,101,013
10,562
haoqunjiang
/ecosystem-ci run
2024-03-21T03:01:43
2024-03-21T03:01:43
{ "+1": 1 }
MEMBER
vuejs
core
2,014,664,678
10,570
zjtakato
> The context of the render's vue is different from the context of the createApp, so you can't get the components registered in the createApp.render的vue的上下文和createApp的上下文不同,所以无法获取createApp中注册的组件。 Thanks, but it's not a good design. I think it could be better.
2024-03-22T09:12:25
2024-03-22T09:15:11
{}
NONE
vuejs
core
2,017,081,558
10,574
edison1105
[a workaround](https://play.vuejs.org/#eNqFUt9LwzAQ/leOPCnMVZ1PpQoqCgpOcXszPtT2tmWmSUjSOhj7370k2xyiG5Qm9913ue9+LNm1Mf2uRZazwlVWGH/FFS6Mth5qnJSt9EuuAKAufXl0DMkAi761amMBOKGmEnM4722QhiJFDm9nPRi8J3AVDvrRV2TbZGR4bIwsPZJVTLRtQNSXnJXGcEYQQFGLLl7oKssPlFdP4XUTMhZZQtZuhxIrD91Jo2uU9ErUwVnSQxFrIlG18UIryLtStkjMU8o21AqLLHn+Z54R815Y5...
2024-03-25T02:04:54
2024-03-25T02:04:54
{}
MEMBER
vuejs
core
2,017,356,000
10,586
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31.1 kB | | vue.global.prod.js | 148 kB | 53.7 kB | 48 kB | ### Usages | Name | Size |...
2024-03-25T07:07:56
2024-03-25T07:07:56
{}
NONE
vuejs
core
2,003,140,979
10,510
lmc3s3f0r
> I'm encountering another error, even when using the plugin documentation pages. Every time I open [this page](https://vue3openlayers.netlify.app/componentsguide/layers/vectorlayer/) and navigate to the second map, the current Chrome tab crashes, and everything freezes. Hi. Is this related to the issue I reported o...
2024-03-18T08:00:11
2024-03-18T08:00:11
{}
NONE
vuejs
core
2,016,748,863
10,578
yangxiuxiu1115
有道理,或许可以新增一个`immediate`的option参数
2024-03-24T09:31:00
2024-03-24T09:31:00
{}
CONTRIBUTOR
vuejs
core
2,017,167,456
10,583
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31.1 kB | | vue.global.prod.js | 148 kB | 53.7 kB | 48 kB | ### Usages | Name | Size |...
2024-03-25T04:00:55
2024-03-25T04:00:55
{}
NONE
vuejs
core
2,022,452,106
10,578
shaobeichen
``` <input :value="text" @input="event => text = event.target.value"> ``` v-model 也是语法糖,那和上面代码一样,初始化text时,input是不会触发的,在设计响应式时其实就遵循了这一点,只有当值改变时,才会有相应操作。 ![image](https://github.com/vuejs/core/assets/18715564/30c0adca-1ed4-4acc-978d-01166b55c2be)
2024-03-27T10:45:40
2024-03-27T10:45:40
{}
NONE
vuejs
core
2,023,044,278
9,943
arturs-buls
@shaobeichen if registering component would be a requirement - why explicitly setting name in `Comp2` make it work (as in playground by yangxiuxiu1115? If self-reference in dynamic components would need to be registered - only workaround for this case would be the one provided by Bayn-Web
2024-03-27T15:21:30
2024-03-27T15:21:30
{}
NONE
vuejs
core
2,015,415,149
10,570
zjtakato
> ```diff > + const ElBtn = resolveComponent('el-button'); > function createNotify() { > const container = document.createElement('div'); > const vnode = h({ > render() { > - const ElBtn = resolveComponent('el-button'); > console.log(ElBtn); // is 'el-button' string, not vnode > retur...
2024-03-22T16:03:40
2024-03-22T16:05:02
{}
NONE
vuejs
core
2,017,167,311
10,582
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31.1 kB | | vue.global.prod.js | 148 kB | 53.7 kB | 48 kB | ### Usages | Name | Size |...
2024-03-25T04:00:42
2024-03-25T04:00:42
{}
NONE
vuejs
core
2,018,556,451
10,589
LinusBorg
refs are only unwrapped in templates (by the template compiler) in render functions, you need to do that yorself, by reading from `.value`
2024-03-25T17:43:03
2024-03-25T17:43:03
{}
MEMBER
vuejs
core
2,025,242,081
10,576
haoqunjiang
/ecosystem-ci run
2024-03-28T13:53:35
2024-03-28T13:53:35
{ "+1": 2 }
MEMBER
vuejs
core
2,003,146,700
10,510
mostafaznv
To be honest, I’m not entirely sure yet. I’m currently investigating the issue, but I haven’t identified the root cause so far. I thought it might be related to this issue, but if it’s not, please disregard my reply. Apologies in advance for any confusion.
2024-03-18T08:03:51
2024-03-18T08:03:51
{ "+1": 1 }
NONE
vuejs
core
2,006,999,895
10,547
logicao
> a workaround [add a key](https://deploy-preview-8213--vue-sfc-playground.netlify.app/#eNqNUstOwzAQ/JXFFzdS1Aq4hbS81AMcAAE3zCEk29bUtSPbKUVR/p21Q1sQCJEc4t2ZHc1O3LLzuh6uG2QZy11pZe3BoW/qidByVRvroQWLsxQW0MHMmhVwYnOhhS6Ndh6km1bSwziwBrNCOUz2oMWiImiQwHgCiwGv5Jqn7RLfs8MOnniA+XNysqVjr/SdDpF/1KVPQsMvz44XPoc8Sf9BO+Jk8icnWglvPuqz...
2024-03-19T12:02:08
2024-03-19T12:02:08
{}
NONE
vuejs
core
2,007,620,795
10,549
HowInteresting
来,骗,来偷袭我一个老同志,简直上了个大当
2024-03-19T16:23:50
2024-03-19T16:27:21
{}
NONE
vuejs
core
2,007,655,401
10,549
haoqunjiang
Fixed in `@vue/babel-plugin-jsx` v1.2.2 by pinning the `@babel/helper-module-import` dependency version. Please update your project dependencies. We'll further investigate this issue later to see why the new Babel release would cause such a bug.
2024-03-19T16:41:08
2024-03-19T16:41:08
{ "+1": 7 }
MEMBER
vuejs
core
2,022,088,994
10,597
tuskermanshu
> > It's incorrect, unfortunately. I apologize. If possible, could you also share the reason why Symbol cannot be used? I would like to learn more about it.
2024-03-27T07:03:42
2024-03-27T07:03:42
{}
NONE
vuejs
core
2,022,797,477
10,601
khamer
@LinusBorg given that `data` is reactive and the template depends on it, shouldn't changes to `data` trigger rerendering? The fact that I can change properties of a reactive object without triggering re-rendering still doesn't seem right to me, even if the computed() value doesn't need to be re-computed.
2024-03-27T13:39:20
2024-03-27T13:43:33
{}
NONE
vuejs
core
2,007,522,855
10,549
Ttou
是的,突然碰到 <img width="815" alt="image" src="https://github.com/vuejs/core/assets/4298437/b5e779bd-03ed-457c-b01a-a7bf5118f9af">
2024-03-19T15:39:42
2024-03-19T15:39:42
{}
NONE
vuejs
core
2,011,106,574
10,562
vue-bot
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8369040456) | suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8354053421) | |-------|--------|----------------| | language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a...
2024-03-21T03:09:11
2024-03-21T03:09:11
{}
CONTRIBUTOR
vuejs
core
2,011,345,180
6,811
metkm
I see some issues linked here but hey seem to look like they are solved but I this this issue still occurs. Or it might be because I have this problem using nuxt 3. Currently using `flush: 'post'` solved the issue
2024-03-21T07:04:56
2024-03-21T07:04:56
{}
NONE
vuejs
core
2,016,444,158
10,485
itsmnthn
I feel this is related https://github.com/vuejs/language-tools/issues/4469 getting vscode type errors from `typescript@5.4`
2024-03-23T10:37:45
2024-03-23T10:38:40
{}
NONE
vuejs
core
2,019,255,061
6,817
so1ve
vue-tsc internally runs the language server to get type checking
2024-03-26T02:06:31
2024-03-26T02:06:31
{ "+1": 1 }
MEMBER
vuejs
core
2,020,289,064
10,598
mitar
OK. But I think the other one is maybe a special case of this one, but not necessary. I think codepath for array handling is different than true-value/false-value handling?
2024-03-26T12:23:03
2024-03-26T12:23:03
{}
NONE
vuejs
core
2,021,799,273
10,595
xstxhjh
> We still need a way to reproduce the problem. You can provide a github repository with a minimal reproduction if it's not reproducible on the playground. Okay, I'll give it a try.
2024-03-27T02:20:21
2024-03-27T02:20:21
{}
NONE
vuejs
core
2,024,350,649
10,588
yangxiuxiu1115
[workground](https://play.vuejs.org/#eNqNVN9r2zAQ/lcOQ6kLieM07R68tKwbZWwP29j60IGhOPbFUSNLQpITZyH/+06S86NllL0kvrvPd9/36eRtdKdUsmoxyqKpKTVTFgzaVt3mgjVKagtb0DiHHcy1bOCcoOe5yEUphbHAGf3cOEB8p3WxSRwo3nIUtV1kk3Q3iJ8GTFTYXdzchv+L9+716SgMozEUWGwULyxSBDCt2ApKXhhzk0duwHAmu3Ee+SKVH3QhDLNMis9atgpE0WCPzCOwRU2B5Af8q4YWPWw1nEtNYax6eiD...
2024-03-28T03:55:37
2024-03-28T03:55:37
{}
CONTRIBUTOR
vuejs
core
1,802,116,508
9,573
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31 kB | | vue.global.prod.js | 148 kB | 53.7 kB | 47.9 kB | ### Usages | Name | Size |...
2023-11-08T15:25:30
2024-03-18T08:51:26
{}
NONE
vuejs
core
2,011,731,157
10,560
Saeid-Za
Thank you for your response. I understand your point and the design decision made [here](https://github.com/vuejs/rfcs/discussions/503#discussioncomment-7828483) but I as a developer want more granular control on whether I want my prop to be internally or externally controlled via the `defineModel` macro, providing...
2024-03-21T09:26:45
2024-03-21T09:48:16
{ "heart": 1 }
CONTRIBUTOR
vuejs
core
2,022,168,280
10,596
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31.1 kB | | vue.global.prod.js | 148 kB | 53.7 kB | 48 kB | ### Usages | Name | Size |...
2024-03-27T08:07:56
2024-03-27T08:07:56
{}
NONE
vuejs
core
2,023,709,909
7,966
nmeierpolys
Does anyone have a workaround or plans to merge one of the proposed fixes? I'm seeing the same thing and it feels like an issue that warrants some attention.
2024-03-27T18:50:22
2024-03-27T18:50:22
{}
NONE
vuejs
core
2,007,152,844
10,547
edison1105
related [commit](https://github.com/vuejs/core/commit/f17a82c769cfb60ee6785ef5d34d91191d153542) Maybe should reconsider https://github.com/vuejs/core/pull/8100
2024-03-19T13:16:37
2024-03-19T13:16:37
{ "+1": 2 }
MEMBER
vuejs
core
2,008,760,548
5,540
shery
> ``` > myRef.value.$.exposed.ExposedMethod() > ``` Worked for me
2024-03-20T06:50:51
2024-03-20T06:50:51
{}
NONE
vuejs
core
2,011,057,458
10,556
songpeng154
> 我用你给的例子试了一下,发现defineProps函数使用泛型时热更新仍然正常,但如果使用ant-design-vue组件中的接口作为类型确定,会导致热更新变得异常缓慢。使用TableProps时,就像这样` defineProps<TableProps >()`,热更新时间大概是30秒,如果再加入省略内置函数时,就像这样` defineProps<Omit<TableProps,'columns'>>()`,热更新时间有几个。具体原因不清楚 @vitejs/plugin-vue 这个插件的问题,把这个插件换成4.6.2版本就没这个问题了
2024-03-21T02:10:07
2024-03-21T02:10:07
{}
NONE
vuejs
core
2,016,387,157
10,571
LinusBorg
We can't help with this issue if we can't reproduce it. If you can't provide a reproduction, we will have to close this issue. What you should investigate is the actual error following these warnings: > cannot read properties of undefined (reading '0') This sounds like you try to render a list with an array, b...
2024-03-23T07:06:29
2024-03-23T07:06:55
{}
MEMBER
vuejs
core
2,017,181,737
10,574
axllent
Thanks for that @edison1105 - the `:value` approach hadn't even crossed my mind. I've reverted back to a working Vue version in the meantime as I assume this fix will (hopefully) make it in to a new release in the not-too-distant future :)
2024-03-25T04:19:37
2024-03-25T04:19:37
{}
NONE
vuejs
core
2,016,550,730
10,576
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------------------ | ------------------ | ------------------- | | runtime-dom.global.prod.js | 90.6 kB (**-6 B**) | 34.4 kB (**+1 B**) | 31 kB (**-30 B**) | | vue....
2024-03-23T17:12:14
2024-03-26T02:31:55
{}
NONE
vuejs
core
2,004,099,834
1,791
dimitri-grablow
hm, I don't have `ssrRender` on my component. Is it coming from Nuxt? We do not use Nuxt currently or otherwise I do not know how to access it
2024-03-18T14:39:25
2024-03-18T14:39:25
{}
NONE
vuejs
core
2,007,572,400
10,549
letsbug
类似于 pnpm,package.json 加上这一句: ```json "pnpm": { "overrides": { "@babel/helper-module-imports": "~7.22.15" } }, ``` @babel/helper-module-imports 这个包6小时前的新版本 7.22.15 到 7.24.1 引发的问题
2024-03-19T16:01:21
2024-03-19T16:01:21
{ "+1": 8, "heart": 2, "hooray": 2, "rocket": 2 }
NONE
vuejs
core
2,014,697,119
10,570
LinusBorg
```diff + const ElBtn = resolveComponent('el-button'); function createNotify() { const container = document.createElement('div'); const vnode = h({ render() { - const ElBtn = resolveComponent('el-button'); console.log(ElBtn); // is 'el-button' string, not vnode return h(ElBtn, { type:...
2024-03-22T09:32:03
2024-03-22T09:32:03
{}
MEMBER
vuejs
core
2,016,231,183
10,570
Justineo
Global registration is within current Vue application and it’s possible to make the same name refer to different components in different apps. You cannot expect a component name is resolved to the same component across all different Vue application so you can’t implement this in a standalone JS file without specifying ...
2024-03-23T00:37:32
2024-03-23T07:46:06
{ "+1": 18 }
MEMBER
vuejs
core
2,016,721,135
10,578
yangxiuxiu1115
看上去是符合预期的,set处理函数在值发生更新时触发。如果你希望初始化时生效,你应该再添加get函数,在get中处理修饰符
2024-03-24T07:29:43
2024-03-24T07:29:43
{}
CONTRIBUTOR
vuejs
core
2,020,401,484
10,595
LinusBorg
We still need a way to reproduce the problem. You can provide a github repository with a minimal reproduction if it's not reproducible on the playground.
2024-03-26T13:14:38
2024-03-26T13:14:38
{}
MEMBER
vuejs
core
2,020,518,956
10,597
mitar
To explain the use case here: I have some user supplied values (strings) I use for checkbox values, but I also want to include checkboxes for special system values (like "all", "none", etc.). So that there is no overlap/conflict between strings, I wanted to use Symbols for system values. I could find some other way esc...
2024-03-26T14:04:27
2024-03-26T14:04:27
{}
NONE
vuejs
core
2,022,137,420
10,042
edison1105
@719media there may be a chance to fix it in v3.5, probably be in early April.
2024-03-27T07:44:43
2024-03-27T07:44:43
{ "heart": 1 }
MEMBER
vuejs
core
2,005,678,314
10,537
mgibas
I’m pretty sure if you’ll set an attribute (setProp-> reflect attr) inside of the constructor, real browser will throw an exception :(
2024-03-19T03:17:00
2024-03-19T03:17:00
{}
NONE
vuejs
core
1,980,011,654
10,464
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------------------- | ------------------- | ------------------- | | runtime-dom.global.prod.js | 90.6 kB (**+37 B**) | 34.4 kB (**+14 B**) | 31 kB (**-2 B**) | ...
2024-03-06T03:29:18
2024-03-21T03:51:06
{}
NONE
vuejs
core
1,997,164,652
10,522
github-actions[bot]
## Size Report ### Bundles | File | Size | Gzip | Brotli | | -------------------------- | ------- | ------- | ------- | | runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31.1 kB | | vue.global.prod.js | 148 kB | 53.7 kB | 48 kB | ### Usages | Name | Size |...
2024-03-14T10:53:01
2024-03-21T03:51:11
{}
NONE
vuejs
core
2,016,217,202
10,570
Justineo
Everything you need to know to solve this issue is [right in the docs](https://vuejs.org/api/render-function.html#resolvecomponent).
2024-03-23T00:21:27
2024-03-23T00:21:27
{}
MEMBER
vuejs
core
2,020,289,924
10,598
mitar
Link to the other issue: https://github.com/vuejs/core/issues/10597
2024-03-26T12:23:21
2024-03-26T12:23:21
{}
NONE
vuejs
core
2,024,333,880
9,943
shaobeichen
> @shaobeichen if registering component would be a requirement - why explicitly setting name in `Comp2` make it work (as in playground by yangxiuxiu1115? > > If self-reference in dynamic components would need to be registered - only workaround for this case would be the one provided by Bayn-Web These are two ques...
2024-03-28T03:31:26
2024-03-28T03:31:26
{}
NONE
vuejs
core
2,006,577,346
10,547
edison1105
a workaround [add a key](https://deploy-preview-8213--vue-sfc-playground.netlify.app/#eNqNUstOwzAQ/JXFFzdS1Aq4hbS81AMcAAE3zCEk29bUtSPbKUVR/p21Q1sQCJEc4t2ZHc1O3LLzuh6uG2QZy11pZe3BoW/qidByVRvroQWLsxQW0MHMmhVwYnOhhS6Ndh6km1bSwziwBrNCOUz2oMWiImiQwHgCiwGv5Jqn7RLfs8MOnniA+XNysqVjr/SdDpF/1KVPQsMvz44XPoc8Sf9BO+Jk8icnWglvPuqzoB...
2024-03-19T09:52:53
2024-03-19T09:52:53
{}
MEMBER
vuejs
core
2,008,674,393
10,553
dragonish
Duplicate of #6771
2024-03-20T05:18:07
2024-03-20T05:18:07
{}
NONE
vuejs
core
2,008,698,416
10,553
lincenying
临时用`<a href="javascript:;" ^text="hex-fff 12px">test1</a>`解决
2024-03-20T05:49:00
2024-03-20T05:49:00
{}
NONE
vuejs
core
2,021,860,588
10,595
xstxhjh
I think my scenario is quite complex, with a large project volume and intricate logical structure. I tried and was unable to reproduce the issue, so I will temporarily close this question for now. I will reopen it once I am able to reproduce the problem.
2024-03-27T03:33:10
2024-03-27T03:33:10
{ "+1": 1 }
NONE
vuejs
core
2,022,048,738
10,597
tuskermanshu
<s> In the compilation process of Vue, Symbol cannot be used as a value. During the compiler's operation, event names, directives, etc., are converted into string form.However, Symbol cannot be converted into a string type. If the explanation is incorrect, please forgive me.<s/>
2024-03-27T06:23:58
2024-03-27T07:03:03
{}
NONE
vuejs
core
2,023,391,513
10,605
LinusBorg
We dont maintain nuxt ui. Please open an issue in their repo
2024-03-27T17:36:16
2024-03-27T17:36:16
{}
MEMBER
vuejs
core
2,023,781,375
10,601
LinusBorg
You're right, and not. Your setIntervall is changing properties of the non-reactive original `data` object. Those changes will not be picked up as reactive changes, as Vue cannot observe them. If you wrap it in `reactive()`, everything works as expected: https://play.vuejs.org/#eNp9ks1ugzAQhF9l5UsSCZGk7SkiqfqT...
2024-03-27T19:15:33
2024-03-27T19:15:47
{ "+1": 1 }
MEMBER
vuejs
core
2,024,807,454
10,517
MineDrum
Hmm, I have a similar issue, but it traces back to an error on unmount. Downgrading to 3.3.0 worked for me
2024-03-28T09:55:31
2024-03-28T09:55:31
{}
NONE
vuejs
core
2,022,080,674
10,597
LinusBorg
> If the explanation is incorrect, please forgive me. It's incorrect, unfortunately.
2024-03-27T06:55:44
2024-03-27T06:55:44
{}
MEMBER
vuejs
core
2,004,054,846
10,524
haoqunjiang
Hi Itamar, thanks for your enthusiasm in contributing to Vue. However, regarding to this PR, I'm afraid these comments would not increase the readability of this module. These function and parameter names are already quite self-explanatory. The TypeScript types have already made code-completion easy. These extra lin...
2024-03-18T14:22:32
2024-03-18T14:23:30
{ "+1": 1 }
MEMBER