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,046,187,739 | 3,822 | skirtles-code | I believe the fix proposed here is the same as in #5781. That PR was closed after #4077 was merged instead.
I think this PR can be closed too. | 2024-04-09T23:18:44 | 2024-04-09T23:18:44 | {} | CONTRIBUTOR |
vuejs | core | 2,047,452,055 | 4,010 | kubajmarek | Bumping the question above, although after [refreshing the initial reproduction](https://play.vuejs.org/#eNp9Ustu2zAQ/BWClyiAKh/akysbfcCHFn3B7a3MQaGXMmOKFPhQHAj69yxJW/Eh8U2cnRnNkDvSz31fDQHoktYeul41HtZME1Lv5ECGd8LYFaMSR0RqoqTzjBIL4gRuQTgElgd4OiGMrseRJME01Qt0yXb3wXujySeuJD8g18IA1sGP5Lje5lO9yDSU1IuLOHh03MreEwc+9IjIrjfWkzF... | 2024-04-10T12:48:11 | 2024-04-10T13:08:54 | {
"heart": 1
} | NONE |
vuejs | core | 2,049,142,957 | 8,900 | rudolfbyker | Updated the original post for Vue 3.4 | 2024-04-11T07:59:39 | 2024-04-11T07:59:39 | {} | NONE |
vuejs | core | 2,049,716,272 | 10,678 | microwin7 | > Please provide a minimal reproduction. We can't debug your docker image
docker-compose.yaml:
```yaml
version: '3.9'
services:
wiki:
build: https://github.com/GravitLauncher-SUPPORT/LauncherWiki.git
restart: always
ports:
- 8091:80
``` | 2024-04-11T13:38:35 | 2024-04-11T13:38:35 | {} | NONE |
vuejs | core | 2,051,980,025 | 10,684 | DabeDotCom | > Overloading like this is simply not supported... use different names for the prop and the computed.
I'm disappointed, but not at all surprised... (And like the saying goes, I've been "granted the serenity" to accept that it's something I cannot change; the rest of this message is just for posterity. «grin»)
... | 2024-04-12T15:27:29 | 2024-04-12T15:33:06 | {} | NONE |
vuejs | core | 2,054,086,096 | 10,464 | yyx990803 | The idea is right, but the fix can be placed in the instrumented `hasOwnProperty` returned by the proxy trap to only perform the string coercion only for `hasOwnProperty`, instead of all tracking calls. See https://github.com/vuejs/core/commit/c3c5dc93fbccc196771458f0b43cd5b7ad1863f4
Also the test case here doesn't ... | 2024-04-14T14:48:39 | 2024-04-14T14:48:39 | {
"rocket": 1
} | MEMBER |
vuejs | core | 1,767,917,253 | 9,421 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.6 kB (**+44 B**) | 34.4 kB (**+9 B**) | 31.1 kB (**+21 B**) |
... | 2023-10-18T08:11:46 | 2024-04-14T15:12:24 | {} | NONE |
vuejs | core | 2,048,487,387 | 10,678 | microwin7 | I found a screenshot from the found mention of the exception on the old working version, which was not yet in the docker image | 2024-04-10T21:44:26 | 2024-04-10T21:44:26 | {} | NONE |
vuejs | core | 2,048,643,976 | 5,695 | skirtles-code | I was wondering whether this PR is still needed since the changes in #9497? That PR introduced the `oldValue` as an argument, with corresponding changes to the relevant types. The `...args: any[]` is now gone. | 2024-04-11T00:27:50 | 2024-04-11T00:27:50 | {} | CONTRIBUTOR |
vuejs | core | 2,048,676,611 | 5,760 | skirtles-code | This seems similar to #3969, which was merged in 3.2.46. I haven't studied this PR in detail, but I'm wondering whether the changes proposed here are still needed? | 2024-04-11T00:50:10 | 2024-04-11T00:50:10 | {} | CONTRIBUTOR |
vuejs | core | 2,049,723,279 | 10,678 | microwin7 | @LinusBorg | 2024-04-11T13:42:02 | 2024-04-11T13:42:02 | {} | NONE |
vuejs | core | 2,049,764,546 | 10,678 | LinusBorg | Giving us instructions on how to run your app in docker does not qualify as a "minimal runnable reproduction"
Please read the issue guidelines | 2024-04-11T14:01:35 | 2024-04-11T14:01:35 | {} | MEMBER |
vuejs | core | 2,050,710,913 | 6,577 | skirtles-code | This PR looks good to me, but it seems that #8558 made a very similar change, and that has been merged into `main`. Unless I'm missing something, I think this PR can now be closed. | 2024-04-11T23:26:25 | 2024-04-11T23:26:25 | {} | CONTRIBUTOR |
vuejs | core | 2,052,397,292 | 7,260 | skirtles-code | I believe something equivalent to this feature is now available in the latest Playground. It seems to have been introduced in various stages, but it looks like commit 9e529f8acbeee90832cda8e09f0a968736e65332 is the point where the feature was completed. | 2024-04-12T19:21:15 | 2024-04-12T19:21:15 | {} | CONTRIBUTOR |
vuejs | core | 2,054,032,180 | 10,652 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8679714689)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8657200885) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-04-14T12:23:57 | 2024-04-14T12:23:57 | {} | CONTRIBUTOR |
vuejs | core | 2,046,328,265 | 4,942 | skirtles-code | The original reproduction seems to be fixed from 3.2.45 onwards. | 2024-04-10T02:04:03 | 2024-04-10T02:04:03 | {} | CONTRIBUTOR |
vuejs | core | 2,048,771,925 | 8,576 | guaijie | > I made a component with these props (I've reduced it to the specific problem):
请问怎么去解析这种情况:
```ts
type Props = {
prop?: true | string
}
```
明确都排除了不能传 false 还是默认转换为false 吗?这个 defineProps 明显就是一个 bug ,为什么要担心破坏性更改。
有 bug 就修复啊,现今为止我身边的开发者没有不为这种默认行为感到不吃惊的 。为了等待你们的修复都转而使用 defineComponent。
`
https://stackoverflow.com/a/32697733/2302258
热更新出错是合理的,不过可能需要看一下为什么初次加载时没出错。 | 2024-04-11T13:54:08 | 2024-04-11T13:54:08 | {} | MEMBER |
vuejs | core | 2,050,863,328 | 6,319 | hubvue | @skirtles-code The version of vue that submitted the PR didn't yet support support for readonly arrays, I tested that the current version does, and there's not much use for this PR, so it looks like it's possible to turn this PR off. | 2024-04-12T02:40:20 | 2024-04-12T02:40:20 | {} | NONE |
vuejs | core | 2,051,164,850 | 10,681 | haoqunjiang | 不好意思,是我看错了。我再仔细研究一下。 | 2024-04-12T07:19:54 | 2024-04-12T07:19:54 | {} | MEMBER |
vuejs | core | 2,053,889,788 | 7,930 | skirtles-code | Related: #5105. | 2024-04-14T03:58:00 | 2024-04-14T03:58:00 | {} | CONTRIBUTOR |
vuejs | core | 2,055,044,263 | 9,044 | skirtles-code | I think this is a duplicate of #7800. | 2024-04-15T04:38:03 | 2024-04-15T04:38:03 | {} | CONTRIBUTOR |
vuejs | core | 2,042,676,438 | 9,587 | sldone | Any update on this? | 2024-04-08T12:51:12 | 2024-04-08T12:51:12 | {} | NONE |
vuejs | core | 2,047,367,364 | 10,675 | FreeLiC | v-for must need add key | 2024-04-10T12:03:59 | 2024-04-10T12:03:59 | {} | NONE |
vuejs | core | 2,049,130,902 | 10,676 | Shyam-Chen | > https://vuejs.org/guide/components/props.html#boolean-casting
```ts
const value = defineModel<boolean | string>({ required: true });
``` | 2024-04-11T07:51:43 | 2024-04-11T07:52:20 | {} | CONTRIBUTOR |
vuejs | core | 2,049,315,190 | 10,675 | FreeLiC | > In fact, they will be mounted in the same tick, I am curious what's the problem in the real-world use.
For example: In some business logic, I need to record the sequence of v-for loop update triggers in the component mounted life cycle into an array, and use subscripts to get the sequence to meet some business log... | 2024-04-11T09:42:23 | 2024-04-11T09:42:23 | {} | NONE |
vuejs | core | 2,052,534,795 | 7,301 | skirtles-code | This fixes the problem for the initial hydration, but it throws an error if the text is subsequently updated:
- [Example](https://deploy-preview-7301--vue-sfc-playground.netlify.app/#__DEV____SSR__eNpNjsFqwzAQRH9l0EUOmPheZNPSb+ip6iGxNlhUloS8chuM/70bXGiPs/tmeJt6yfm8VlJPyixj8ZmxENc82OjnnApjQ6Fbiwk7biXN0EJrG20cU1wYTN+M... | 2024-04-12T21:08:14 | 2024-04-12T21:08:14 | {} | CONTRIBUTOR |
vuejs | core | 2,048,737,678 | 10,674 | guaijie | > This is a known issue that has been discussed for several times. Changing the behavior will be a breaking change that we cannot make at the point in Vue 3.
本身就是错的,就一直错下去吗?一个新的东西,前期难免有破坏性更改。等这个 defineProps 用的越来越多就越难动。
我真的很吃惊,一个错的东西想到的不是解决而是担心会产生破坏性更改。 | 2024-04-11T01:15:34 | 2024-04-11T01:38:24 | {} | CONTRIBUTOR |
vuejs | core | 2,049,731,372 | 10,678 | microwin7 | 
the version is still 3.4.19, I was mistaken when I assumed that the versions were updated during assembly | 2024-04-11T13:45:54 | 2024-04-11T13:45:54 | {} | NONE |
vuejs | core | 2,052,789,287 | 7,556 | skirtles-code | I'm wondering whether this is still an issue since #9328 was merged? The fixes look very similar. | 2024-04-13T01:01:33 | 2024-04-13T01:01:33 | {} | CONTRIBUTOR |
vuejs | core | 2,053,890,871 | 7,938 | skirtles-code | Are these changes still needed now that #9573 has been merged? | 2024-04-14T04:03:33 | 2024-04-14T04:03:33 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,054,828,859 | 10,695 | yyx990803 | Instead of changing tokenizer logic, it's better to handle this at the parser level in `onCloseTag` where the location info is generated. See https://github.com/vuejs/core/commit/16174da21d6c8ac0aae027dd964fc35e221ded0a
Also `.trimEnd` is ES2019 and cannot be used in the codebase. | 2024-04-15T03:53:08 | 2024-04-15T03:53:08 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,046,197,077 | 3,435 | skirtles-code | I'm wondering whether this should now be closed?
The original `if (pos > -1) {` check was removed in:
- https://github.com/vuejs/core/commit/d810a1a56943aeba5160b42bc917187e99cdfb8e#diff-6142a09a188ff9ccb70f2ac08cb772e3ad9798386f3af4c95dd1567d9ab376ce
I believe that's essentially equivalent to solution 1. | 2024-04-09T23:31:17 | 2024-04-09T23:31:17 | {} | CONTRIBUTOR |
vuejs | core | 2,046,655,748 | 10,672 | troy351 | It seems `move` class not added properly | 2024-04-10T06:53:02 | 2024-04-10T06:53:02 | {} | NONE |
vuejs | core | 2,047,145,524 | 10,674 | Justineo | Duplicate of #9882
See also: https://github.com/vuejs/vue/issues/4792 https://github.com/vuejs/vue/issues/7646 | 2024-04-10T10:20:58 | 2024-04-10T10:20:58 | {} | MEMBER |
vuejs | core | 2,049,296,106 | 10,675 | Doctor-wu | In fact, they will be mounted in the same tick, I am curious what's the problem in the real-world use. | 2024-04-11T09:32:27 | 2024-04-11T09:32:27 | {} | MEMBER |
vuejs | core | 2,054,092,458 | 7,556 | niksy | Applying these changes to latest Vue (3.4.21) results in following error:
```
Uncaught (in promise) TypeError: Cannot redefine property: __vnode
```
It seems like dev tools select works on initial load, but when your refresh the page with dev tools open and Vue tab selected, it stops working. Solution is to clo... | 2024-04-14T15:09:27 | 2024-04-14T15:10:28 | {} | NONE |
vuejs | core | 2,209,342,332 | 11,293 | skirtles-code | I don't think the global reactive object is really a factor here. The same thing happens for local data:
- [Playground](https://play.vuejs.org/#eNp9U9uOmzAQ/ZWRVYmsFBG126eIpN2u8rDVKlv18lRXFTUmeBds5AtNhfj3jm0g9KLlBTNzZs6ZM7gnN22bdo6TLckM06K1YLh17Z5K0bRKW+hB83INJ25vndZc2jtpbC4ZXwNTTessL2CAUqsGEmyUUEklU4iBvK5h56tXyc39f... | 2024-07-04T16:49:23 | 2024-07-04T16:49:23 | {} | CONTRIBUTOR |
vuejs | core | 2,209,850,599 | 11,264 | edison1105 | @skirtles-code I think we should open a new issue to track the render function clashing names problem due to the related problem has been fixed via #8523 | 2024-07-05T01:38:18 | 2024-07-05T01:38:18 | {} | MEMBER |
vuejs | core | 2,210,373,522 | 11,296 | JasonGotGithub | Without an explanation is quite difficult to understand what your intention is of your message @linzhe141 Besides that, the problem of this issue still occurs in your link | 2024-07-05T07:47:59 | 2024-07-05T07:47:59 | {} | NONE |
vuejs | core | 2,210,491,728 | 11,296 | LinusBorg | I think they just provided a simplified reproduction that doesn't involve a router etc. Which is helpful. | 2024-07-05T09:03:59 | 2024-07-05T09:04:11 | {} | MEMBER |
vuejs | core | 2,210,506,773 | 11,293 | LinusBorg | > btw, the [vue/no-side-effects-in-computed-properties](https://eslint.vuejs.org/rules/no-side-effects-in-computed-properties.html#vue-no-side-effects-in-computed-properties) not work in above cases.
This might be a bug /improvement for this rule. It would be helpful if you could open an issue for the eslint plugin ... | 2024-07-05T09:12:48 | 2024-07-05T09:12:48 | {} | MEMBER |
vuejs | core | 2,217,934,571 | 11,309 | shuxinqin | thanks!! | 2024-07-09T14:50:29 | 2024-07-09T14:50:29 | {} | NONE |
vuejs | core | 2,219,340,841 | 11,319 | edison1105 | /ecosystem-ci run | 2024-07-10T02:08:19 | 2024-07-10T02:08:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,219,573,068 | 11,319 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9867025959)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9868431556) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/986... | 2024-07-10T05:10:15 | 2024-07-10T05:10:15 | {} | CONTRIBUTOR |
vuejs | core | 2,197,212,689 | 10,948 | Tjaitil | I came to the same alternative approach as you @lejunyang. But in my opinion that kind of defeats the purpose of using vue with web components with such a custom solution.
If this is something that won't implement then I think there is an argument that this should be reflected in the docs; https://vuejs.org/guide/ex... | 2024-06-28T15:47:40 | 2024-06-28T15:47:40 | {
"+1": 1
} | NONE |
vuejs | core | 2,205,858,366 | 11,253 | liangqi2510 | 代码不太方便,可以举个例子 {{row.userData.name}} -> {{row?.userData?.name}} | 2024-07-03T11:29:28 | 2024-07-03T11:29:28 | {} | NONE |
vuejs | core | 2,212,695,319 | 11,311 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34.2 kB | 30.8 kB |
| vue.global.prod.js | 146 kB | 53.6 kB | 47.7 kB |
### Usages
| Name | Size |... | 2024-07-08T00:53:55 | 2024-07-08T00:53:55 | {} | NONE |
vuejs | core | 2,219,342,272 | 11,325 | wangyewei | ERROR: type should be string, got " https://vuejs.org/guide/extras/reactivity-transform.html#reactive-props-destructure" | 2024-07-10T02:09:35 | 2024-07-10T02:09:35 | {} | CONTRIBUTOR |
vuejs | core | 2,195,966,127 | 11,240 | yyx990803 | closing as a duplicate of #11227 as the root cause is the same. | 2024-06-28T01:57:20 | 2024-06-28T01:57:20 | {} | MEMBER |
vuejs | core | 2,196,100,019 | 11,245 | yangxiuxiu1115 | https://cn.vuejs.org/api/sfc-script-setup.html#basic-syntax | 2024-06-28T04:11:29 | 2024-06-28T04:11:29 | {} | CONTRIBUTOR |
vuejs | core | 2,199,288,107 | 11,262 | linzhe141 |  | 2024-07-01T05:47:25 | 2024-07-01T05:47:25 | {} | MEMBER |
vuejs | core | 2,208,194,840 | 5,846 | karlsbeard | 想询问一下,如果用选项式的写法,这种是不支持的吗?是不是必须要用组合式写法呢?
<script lang="jsx">
render() {
return ()
}
</script> | 2024-07-04T06:17:42 | 2024-07-04T06:17:42 | {} | NONE |
vuejs | core | 2,211,813,743 | 11,299 | trcat | When the props type becomes more complex, such as when an enum type appears, there still has other type error | 2024-07-06T16:32:53 | 2024-07-06T16:32:53 | {} | NONE |
vuejs | core | 2,213,400,919 | 11,316 | bushuizaijian | > [Maybe in the parent component, use it like this](https://play.vuejs.org/#eNqFUk1v1DAQ/SsjX3YrheSwnKLsCqh6AGkBAbeaQ0hmd9167cgf6aIo/50Zh4YISntJ7PeeZ94bexBvuy7vI4pSVL5xqgvgMcRuJ406d9YFGMDhIaNP3QTVYwYPdWhOGVizt9EEbGGEg7NnWFGZ1Xxs//Pa0sqgCb/pvFhg3JPE0jTWeFJY62HLndaDNABa+VDefpdmvGJRVUzeyBVtAp47XQekHaSTJQzDVGIcGat+uMRVSxP9... | 2024-07-08T08:46:20 | 2024-07-08T08:46:20 | {} | NONE |
vuejs | core | 2,216,470,737 | 11,318 | JochemBruijninckx | > ```diff
> EventTarget.prototype.addEventListener = function (type, listener, options) {
> - console.log(`Added event listener: ${type}`, this);
> originalAddEventListener.call(this, type, listener, options);
> };
>
> EventTarget.prototype.removeEventListener = function (type, listener, options) {
> - cons... | 2024-07-09T04:14:22 | 2024-07-09T04:14:22 | {} | NONE |
vuejs | core | 2,199,601,437 | 11,253 | liangqi2510 | blockStack?和我的情况有点类似。https://github.com/liangqi2510/vue-block-study 不知道能不能帮到你。 | 2024-07-01T08:55:41 | 2024-07-01T08:55:41 | {} | NONE |
vuejs | core | 2,203,535,323 | 11,284 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | -------------------- |
| runtime-dom.global.prod.js | 89.4 kB (**+38 B**) | 34.2 kB (**+13 B**) | 30.9 kB (**+37 B**) ... | 2024-07-02T15:29:38 | 2024-07-02T15:29:38 | {} | NONE |
vuejs | core | 2,209,871,962 | 11,293 | linzhe141 | [However this does not retain full backwards compatibility.](https://blog.vuejs.org/posts/vue-3-4#more-efficient-reactivity-system)

| 2024-07-05T02:06:28 | 2024-07-05T02:10:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,211,116,846 | 11,273 | bcdanieldickison | > This problem does seem to be reproducible using the Playground in SSR mode:
Thanks! I didn't notice there was an option to enable dev-mode SSR rendering in the playground. I'll add a link to the description.
| 2024-07-05T16:04:36 | 2024-07-05T16:04:36 | {} | NONE |
vuejs | core | 2,198,418,997 | 4,314 | LAMMUpro | The native slot function can only be used under the shadow dom.... | 2024-06-30T03:22:43 | 2024-06-30T03:22:43 | {} | NONE |
vuejs | core | 2,198,921,459 | 11,246 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | -------------------- |
| runtime-dom.global.prod.js | 89.4 kB (**-3 B**) | 34.2 kB | 30.8 kB (**+25 B**) |
| v... | 2024-07-01T01:57:13 | 2024-07-01T01:59:42 | {} | NONE |
vuejs | core | 2,199,139,864 | 11,259 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34.2 kB | 30.8 kB |
| vue.global.prod.js | 146 kB | 53.6 kB | 47.7 kB |
### Usages
| Name | Size |... | 2024-07-01T03:14:19 | 2024-07-01T03:14:19 | {} | NONE |
vuejs | core | 2,208,972,239 | 11,293 | linzhe141 | If I unshift a responsive array, the following code will be triggered, and the dirty of the effect corresponding to componentUpdateFn will be changed to true, so it will be re-rendered and the view will be updated. So I think this should be a bug in Vue.
`: [playground](https://play.vuejs.org/#eNqVVMFu2zAM/RVCl3RAFmPrTp6TYRt66A5r0fVoYHBsOnVmS5okZ9mC/PtIKVacdi2yHGKJfBQfxUftxEetZ5seRSoyW5pGO7Doeg1tIVfzXDibi0Uum04r4+Cz6jTURnUwmSW84dDJ+1xGxA4M1rA/gNjLzlJJ66Bx2MGcARe7XALUSqXgTI9T3i0Lk8LbXO5f+fOyJNCh5LShSN0WDmkHkHFmXgBsXi8bWaV8MpHlTy5... | 2024-07-02T02:08:18 | 2024-07-02T02:08:18 | {} | MEMBER |
vuejs | core | 2,207,943,541 | 11,290 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | -------------------- |
| runtime-dom.global.prod.js | 89.4 kB (**+63 B**) | 34.2 kB (**+32 B**) | 30.9 kB (**+69 B**) ... | 2024-07-04T02:55:05 | 2024-07-04T02:55:05 | {} | NONE |
vuejs | core | 2,209,399,497 | 11,264 | skirtles-code | This seems to be reproducible in the Playground using 3.4.21 and PROD:
- [Playground (3.4.21)](https://play.vuejs.org/#__PROD__eNp9Uk1rGzEQ/SuDLnJgs8ZtT+7G0BZD20Na2tIcohA20sRWrJWEpN04mP3vGWnz4UPITTPz3ps3Dx3YF+/roUe2ZE2UQfsEEVPvV8LqzruQ4AAyYJvw/7lTWEFAqzDACLfBdcCJyj8LK6x0NiZIW+wQzjLJGReWwL22Ow7jEWawJESYI9kZV3rgFRzGCi... | 2024-07-04T17:45:43 | 2024-07-04T17:45:43 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,212,694,834 | 11,310 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34.2 kB | 30.8 kB |
| vue.global.prod.js | 146 kB | 53.6 kB | 47.7 kB |
### Usages
| Name | Size |... | 2024-07-08T00:53:15 | 2024-07-08T00:53:15 | {} | NONE |
vuejs | core | 2,217,609,776 | 11,278 | so1ve | /ecosystem-ci run | 2024-07-09T12:44:01 | 2024-07-09T12:44:01 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,219,348,405 | 11,319 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9867025959)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9833783701) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/986... | 2024-07-10T02:15:44 | 2024-07-10T02:15:44 | {} | CONTRIBUTOR |
vuejs | core | 2,199,164,778 | 11,254 | linzhe141 | Maybe this is a bug in the playground

| 2024-07-01T03:34:30 | 2024-07-01T03:34:30 | {
"confused": 1
} | MEMBER |
vuejs | core | 2,202,042,937 | 11,253 | allenye0909 | 感谢回复,@liangqi2510 是有点类似, @yyx990803 已经处理了,或者是我使用方式不正确,那应该怎么使用呢?

[https://github.com/vuejs/core/pull/3106#issuecomment-807584522](url) | 2024-07-02T06:24:54 | 2024-07-02T06:24:54 | {} | NONE |
vuejs | core | 2,209,930,162 | 11,296 | linzhe141 | [playground](https://play.vuejs.org/#eNrNVclu2zAQ/RVCF8lAIiFoT64cNA0MpEXaBkmOujDS2GZCkQJJuQ5c/3tnKFnyWqeHArnYnJWPbxYtg6uqiuc1BMMgtbkRlWMWXF0xydV0lAXOZsFlpkRZaeOYe62ALdmj4coKJ7S6M7qybMUmRpcsxDzhp855yQxMjtiunnTtWkuceIlQhJ3DjS6hs5PQmjOVa2Udq/gU7jH9iC5Jbx6/344llKAc+81ULeVlRL8DvLHxv9aYV5HdR0SUcrA2uu33DPceOGLLTDGmeAlDFtLd4Rk... | 2024-07-05T03:23:08 | 2024-07-05T03:23:08 | {} | MEMBER |
vuejs | core | 2,212,735,583 | 11,309 | linzhe141 | `render(null, ele);` | 2024-07-08T01:17:03 | 2024-07-08T01:17:03 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,212,966,000 | 11,313 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34.2 kB | 30.8 kB |
| vue.global.prod.js | 146 kB | 53.6 kB | 47.7 kB |
### Usages
| Name | Size |... | 2024-07-08T04:00:15 | 2024-07-08T04:00:15 | {} | NONE |
vuejs | core | 2,216,549,079 | 11,318 | LinusBorg | That's because the elements are removed from the DOM when the component is unmounted, so they will be garbage collected and so there's no need to remove the listeners. Removing them individually would just be overhead | 2024-07-09T05:17:54 | 2024-07-09T07:09:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,216,786,151 | 11,312 | LinusBorg | Generics are only supported when using the type interface declaration
| 2024-07-09T07:15:36 | 2024-07-09T07:15:36 | {
"confused": 1
} | MEMBER |
vuejs | core | 2,198,419,063 | 4,314 | LAMMUpro | The native slot function can only be used under the shadow dom.... | 2024-06-30T03:23:17 | 2024-06-30T03:23:17 | {} | NONE |
vuejs | core | 2,202,146,099 | 11,253 | liangqi2510 | 我觉得你的情况和我类似,是因为 blockStack 正常情况下,在每次渲染后应该是空的。我现在还不确定你和我遇到的相同的情况。我可以详细说一下我的情况,和我解决的方式。
我遇到的情况是,我在使用element-puls的table组件的自定义 col 的 slot。但我插槽部分内的模版是有问题的,特定情况下,会产生异常。但这个异常被这个插槽所在的渲染函数(table-column)捕获,使 vue 框架没有捕获这个异常(正常应该由vue框架进行处理[参考](https://github.com/vuejs/core/commit/da944cb37987212d1b1a860b79f43a7c85814225))。渲染过程也... | 2024-07-02T07:18:56 | 2024-07-02T11:22:09 | {} | NONE |
vuejs | core | 2,209,410,602 | 11,273 | skirtles-code | This problem does seem to be reproducible using the Playground in SSR mode:
- [Playground](https://play.vuejs.org/#__SSR__eNp9UkFOwzAQ/IrlSwGVRBWcQloJqkrAARBw9CUkm8StY1u20wZV+TtrWy2VQL1E3p2ZeGa9e3qvdbLtgWY0t6Xh2hELrtdEFLKZM+osowsmeaeVcWSphDKkNqojkyQN1YTJUkmLGJlHnMk8jb9CIRYOOi0KB1gRkrezxSMIofIUT556AmNp3bfwx3ZG9p6fXhH... | 2024-07-04T17:56:50 | 2024-07-04T17:56:50 | {} | CONTRIBUTOR |
vuejs | core | 2,209,858,276 | 11,294 | edison1105 | Thanks @jh-leong
closing as duplicate of https://github.com/vuejs/core/issues/7256 | 2024-07-05T01:46:10 | 2024-07-05T01:46:10 | {} | MEMBER |
vuejs | core | 2,212,552,681 | 7,980 | vgorloff | Assuming that "Functional components" are components, then we can use [Deep Selectors](https://vuejs.org/api/sfc-css-features.html#deep-selectors) to style JSX.
<details>
<summary>Sample code</summary>
```html
<script lang="jsx" setup>
const JSXComponent = (props) => {
return (
<div class="jsxRoot">
... | 2024-07-07T19:56:41 | 2024-07-07T19:56:41 | {} | NONE |
vuejs | core | 2,216,543,686 | 11,320 | LinusBorg | Thats because the el-checkbox-group mutates the array, it does not set a new new array as the value. | 2024-07-09T05:14:24 | 2024-07-09T05:14:24 | {} | MEMBER |
vuejs | core | 2,196,100,737 | 11,245 | yangxiuxiu1115 | 只能在script setup语法下才能使用哟 | 2024-06-28T04:12:32 | 2024-06-28T04:12:32 | {} | CONTRIBUTOR |
vuejs | core | 2,196,474,387 | 11,239 | MQYForverT | > > check my repo link without unocss,no style because vue api no support this case
>
> ok. I will do it tomorrow, good night!
Hello, have you confirmed this question? Will there be a schedule | 2024-06-28T09:13:55 | 2024-06-28T09:13:55 | {} | NONE |
vuejs | core | 2,196,513,112 | 11,239 | MQYForverT | > Vue 的自定义元素在设计时,就期望自定义元素每个子组件都是一个自定义元素,现在我们来看一下自定义元素组件的生效问题,目前解决方案还在进一步中,目前临时的解决方案是遵循 Vue 的规则,即每个子组件都是一个自定义元素。
Okay, until there is a further solution, I will use the one provided by unocss: import the styles of each subcomponent into the root component.
But as a user, let me share my thoughts.
Because many b... | 2024-06-28T09:37:47 | 2024-06-28T09:37:47 | {
"+1": 1
} | NONE |
vuejs | core | 2,204,973,744 | 11,287 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | -------------------- |
| runtime-dom.global.prod.js | 89.6 kB (**+253 B**) | 34.3 kB (**+93 B**) | 30.9 kB (**+80 B*... | 2024-07-03T02:59:38 | 2024-07-03T03:05:18 | {} | NONE |
vuejs | core | 2,206,457,050 | 4,476 | HaNdTriX | Just to clarify.
## ✅ VueCustomElements share Context between each other
### Example
```tsx
<custom-element-1>
<custom-element-2 />
<custom-element-1 />
```
`custom-element-2` gets the `provide('foo', 'bar')` from `custom-element-1` via `inject('foo')`
### Vue Core Code
https://github.com/... | 2024-07-03T15:05:04 | 2024-07-03T15:11:25 | {} | NONE |
vuejs | core | 2,210,293,517 | 11,293 | LinusBorg | > If there is a solution I think it would need to come from outside, e.g. via the language tools or ESLint.
We actually do have an eslint rule for that:
https://eslint.vuejs.org/rules/no-side-effects-in-computed-properties.html#vue-no-side-effects-in-computed-properties
> However this does not retain full back... | 2024-07-05T06:49:37 | 2024-07-05T06:53:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,211,679,659 | 11,235 | TotomInc | Hello, thanks for the PR. Is there any chance it will get merged? | 2024-07-06T06:29:52 | 2024-07-06T06:29:52 | {} | NONE |
vuejs | core | 2,212,621,315 | 8,284 | skirtles-code | The warning is no longer shown as of 3.4.4. The relevant change seems to be #9948. I'm not sure whether that fully fixes the issue or not, but the reproduction given here does seem to be working since 3.4.4.
Note that the original reproduction link is set to 3.3.1 in the import map, so despite appearances it isn't a... | 2024-07-07T23:51:22 | 2024-07-07T23:51:22 | {} | CONTRIBUTOR |
vuejs | core | 2,218,602,241 | 8,397 | skirtles-code | It looks like the underlying problem was fixed by #9948. I tried running the test case added in this PR and it does pass since that PR was merged.
That PR didn't add any test cases for the specific scenario being handled here, so perhaps this PR could be repurposed just to add the relevant tests? | 2024-07-09T20:01:36 | 2024-07-09T20:01:36 | {} | CONTRIBUTOR |
vuejs | core | 2,219,315,153 | 7,542 | SampsonCrowley | honestly I wish the leading and trailing whitespace were _also_ removed for static content it's very inconvenient that code formatting affects layout.
I would _much_ rather have that leading/trailing whitespace _always_ removed. and if I need to guarantee a space, that's what either ` ` is for, or margin or pad... | 2024-07-10T01:45:20 | 2024-07-10T01:45:20 | {} | NONE |
vuejs | core | 2,198,039,583 | 11,252 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34.2 kB | 30.8 kB |
| vue.global.prod.js | 146 kB | 53.6 kB | 47.7 kB |
### Usages
| Name | Size |... | 2024-06-29T08:06:15 | 2024-06-29T08:06:15 | {} | NONE |
vuejs | core | 2,199,140,974 | 11,260 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34.2 kB | 30.8 kB |
| vue.global.prod.js | 146 kB | 53.6 kB | 47.7 kB |
### Usages
| Name | Size |... | 2024-07-01T03:14:42 | 2024-07-01T03:14:42 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.