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,834,140,213 | 9,725 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 86.7 kB | 33 kB | 29.8 kB |
| vue.global.prod.js | 133 kB | 49.8 kB | 44.6 kB |
### Usages
| Name | Size |... | 2023-11-30T16:42:17 | 2023-11-30T16:42:17 | {} | NONE |
vuejs | core | 1,835,390,200 | 8,897 | yyx990803 | I decided to rethink how import usage check should work and implemented AST-based checks in https://github.com/vuejs/core/pull/9729
Still, thanks for the PR! | 2023-12-01T03:17:29 | 2023-12-01T03:17:29 | {} | MEMBER |
vuejs | core | 1,835,410,518 | 1,900 | zhaohui90-lee | > ### Why?
> @jods4 and I noticed that `ref`s can be made much faster and more memory efficient by using classes (prototypes) instead of the current objects ([vuejs/rfcs#197 (comment)](https://github.com/vuejs/rfcs/issues/197#issuecomment-671119767) and onwards).
>
> ### What?
> This changes the implementation of ... | 2023-12-01T03:47:44 | 2023-12-01T03:47:44 | {} | NONE |
vuejs | core | 1,835,700,545 | 7,723 | yyx990803 | Thanks a lot for the PR, the issue is that doing so in `compileTemplate` ignores the columns change for the source maps, so it has to be done during the parse / source map gen phase. See 634519720 | 2023-12-01T08:47:05 | 2023-12-01T08:47:05 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,835,998,128 | 9,697 | WIStudent | > Now, we could add additional magic to properly convert 'true' and 'false' to true and false
I would advise against adding some conversion magic. The HTML Living Standard explicitly states:
> A number of attributes are boolean attributes. The presence of a boolean attribute on an element represents the true valu... | 2023-12-01T11:55:09 | 2023-12-01T12:01:23 | {
"+1": 1
} | NONE |
vuejs | core | 1,840,847,909 | 9,756 | Alfred-Skyblue | /cc @pikax Do you think this PR is helpful? | 2023-12-05T13:59:38 | 2023-12-05T13:59:38 | {} | MEMBER |
vuejs | core | 1,833,473,146 | 9,702 | pikax | @RicardoErii thank you for the PR, is it possible to also add tests, for this case and for the props with object definition?
Tests should be added on this file `packages/dts-test/defineComponent.test-d.tsx` | 2023-11-30T10:19:11 | 2023-11-30T10:19:11 | {} | MEMBER |
vuejs | core | 1,833,489,662 | 9,680 | Doctor-wu | @pikax That's also great news, thx for your reply~ | 2023-11-30T10:29:54 | 2023-11-30T10:29:54 | {} | MEMBER |
vuejs | core | 1,834,653,268 | 9,712 | wpj | `vue2-component` is a stand-in for a third party component that's been compiled with Vue 2 and installed from npm, so I wouldn't necessarily have control over whether or not it's been compiled with `@vue/compat`. My understanding of how `@vue/compat` works is that only the application is required to be compiled with it... | 2023-11-30T22:21:27 | 2023-11-30T22:21:27 | {} | NONE |
vuejs | core | 1,835,249,840 | 8,989 | edison1105 | @LinusBorg approved | 2023-12-01T01:20:29 | 2023-12-01T01:20:29 | {} | MEMBER |
vuejs | core | 1,837,166,925 | 6,497 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 86.7 kB | 33 kB | 29.8 kB |
| vue.global.prod.js | 133 kB | 49.8 kB | 44.6 kB |
### Usages
| Name | Size |... | 2023-12-02T14:55:44 | 2023-12-02T14:55:44 | {} | NONE |
vuejs | core | 1,837,193,722 | 9,439 | sxzz | I agree with dropping number support. | 2023-12-02T16:17:42 | 2023-12-02T16:17:42 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,838,103,078 | 8,105 | avaz | Yay!! 🙌🏼 | 2023-12-04T08:58:57 | 2023-12-04T08:58:57 | {
"hooray": 6
} | NONE |
vuejs | core | 1,839,891,825 | 9,663 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8b8be0f20356a73d791cdf67b4e1fd4eb06ad501 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-12-05T02:26:54 | 2023-12-05T02:26:54 | {} | NONE |
vuejs | core | 1,833,706,751 | 5,540 | padcom | Any progress on that over-a-year-old shortcoming of Vue's implementation of webcomponents? Is that ever going to land in Vue or should we just create and use a fork to get it implemented? | 2023-11-30T12:42:45 | 2023-11-30T12:42:45 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,839,820,207 | 9,712 | adam-te | Ran into this as well.
It can be worked around with:
```
<slot name="mySlotName" v-if="'mySlotName' in $slots"></slot>
<template v-else>Fallback Content</template>
```
Note that you have to use `in` rather than `$slots.mySlotName` as the latter seems to trigger some side effect via Getter/proxy which breaks ... | 2023-12-05T00:59:55 | 2023-12-05T00:59:55 | {} | NONE |
vuejs | core | 1,838,455,391 | 9,750 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 86.8 kB (**+82 B**) | 33 kB (**+31 B**) | 29.8 kB (**+16 B**) |
... | 2023-12-04T11:38:55 | 2023-12-05T07:16:56 | {} | NONE |
vuejs | core | 1,841,669,589 | 9,757 | DrJume | Is the prefix `test(types/defineProps): ` of the PR ok? Or should I change it to `test(dts-test): `? | 2023-12-05T21:48:19 | 2023-12-05T21:49:02 | {} | CONTRIBUTOR |
vuejs | core | 1,833,971,789 | 9,649 | pikax | This is caused because Functional components are very barebones, basically what we return is the function with props.
One issue sort of related https://github.com/microsoft/TypeScript/issues/14729, since it would be nice to also add some typing for using in JSX | 2023-11-30T15:12:28 | 2023-11-30T15:12:28 | {} | MEMBER |
vuejs | core | 1,836,280,072 | 9,734 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 86.7 kB | 33 kB | 29.8 kB |
| vue.global.prod.js | 133 kB | 49.8 kB | 44.6 kB |
### Usages
| Name | Size |... | 2023-12-01T15:10:03 | 2023-12-01T15:10:03 | {} | NONE |
vuejs | core | 1,837,357,979 | 9,651 | Alfred-Skyblue | @johnsoncodehk This's great! Looking forward to you merging https://github.com/johnsoncodehk/core/commit/21a2864c89358acfaab47dfd2826843ebef5fc65 over.
| 2023-12-03T04:17:17 | 2023-12-03T04:17:17 | {} | MEMBER |
vuejs | core | 1,772,044,996 | 8,824 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------------------- | ------- |
| runtime-dom.global.prod.js | 86.7 kB | 33 kB (**-21 B**) | 29.7 kB |
| vue.global.prod.js | 133 kB | 49.8 kB (**+32 B**) | 44.7 kB |... | 2023-10-20T04:06:09 | 2023-11-30T10:31:53 | {} | NONE |
vuejs | core | 1,834,009,552 | 9,721 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 86.7 kB | 33 kB | 29.8 kB |
| vue.global.prod.js | 133 kB | 49.8 kB | 44.6 kB |
### Usages
| Name | Size |... | 2023-11-30T15:33:07 | 2023-11-30T15:33:07 | {} | NONE |
vuejs | core | 1,836,344,549 | 9,726 | LinusBorg | My suspicion would be that Turbo replaces the content of `<body>` before everthing has been unmounted, but unfortunately Turbo's down don't really provide a detailed picture of the lifecycle. | 2023-12-01T15:52:19 | 2023-12-01T15:52:19 | {} | MEMBER |
vuejs | core | 1,837,264,944 | 9,651 | johnsoncodehk | I have no opinion on whether to add this. If we decide to add it, this might be an appropriate simplifying modification: https://github.com/johnsoncodehk/core/commit/21a2864c89358acfaab47dfd2826843ebef5fc65 | 2023-12-02T22:04:27 | 2023-12-02T22:04:27 | {
"+1": 1,
"heart": 1
} | MEMBER |
vuejs | core | 1,837,381,999 | 9,691 | GabrielHangor | I've found a solution, you just have to do it like that:
Now the types can be properly obtained by volar
Maybe this should be added to the docs as an example because the current one is not correct... | 2023-12-03T06:08:40 | 2023-12-03T06:09:54 | {
"+1": 1
} | NONE |
vuejs | core | 1,838,644,787 | 9,134 | TomasSestak | when this will get merged? It's making nuxt unusable | 2023-12-04T13:27:47 | 2023-12-04T13:27:47 | {
"+1": 3,
"eyes": 1
} | NONE |
vuejs | core | 1,839,500,175 | 9,707 | lttr | Awesome, you guys are fast! | 2023-12-04T21:23:31 | 2023-12-04T21:23:31 | {} | NONE |
vuejs | core | 1,839,888,418 | 9,712 | adam-te | I found that `compat/vue.runtime.esm-bundler.js` has a function:
```
function legacyRenderSlot(instance, name, fallback, props, bindObject) {
if (bindObject) {
props = mergeProps(props, bindObject);
}
return renderSlot(instance.slots, name, props, fallback && (() => fallback));
}
```
Changing the... | 2023-12-05T02:22:05 | 2023-12-05T02:57:23 | {} | NONE |
vuejs | core | 1,840,877,952 | 3,024 | ESP-Marc | I was getting this problem when trying clone reactive objects for the purpose of saving an undo state.
You can't use `structuredclone` because you get some `window` error.
If you use `JSON.parse(JSON.stringify(value))` you will get some unwanted conversion of empty special types outputting as NULL `object` and in... | 2023-12-05T14:15:55 | 2023-12-05T14:15:55 | {
"heart": 1
} | NONE |
vuejs | core | 1,835,667,872 | 9,728 | pikax | Looks to be right to me, because component can be many things, the generated runtime `type` is `null`, that's expected and intended.
> The type is correct or the prop contains `skipCheck: true`
Not sure what you mean by this, where would `skipCheck` come from? | 2023-12-01T08:20:44 | 2023-12-01T08:20:44 | {} | MEMBER |
vuejs | core | 1,835,720,069 | 9,439 | pikax | @xiaoxiangmoe provide already allows `number` but inject does not.
> How about allow bigint, Array of number, Array of int and so on?
We should only support `PropertyKey` ts type. | 2023-12-01T09:00:54 | 2023-12-01T09:01:05 | {} | MEMBER |
vuejs | core | 1,836,022,994 | 9,697 | WoJiaoFuXiaoYun | > > Now, we could add additional magic to properly convert 'true' and 'false' to true and false
>
> I would advise against adding some conversion magic. The HTML Living Standard explicitly states:
>
> > A number of attributes are boolean attributes. The presence of a boolean attribute on an element represents the... | 2023-12-01T12:14:50 | 2023-12-01T12:14:50 | {} | NONE |
vuejs | core | 1,772,044,264 | 8,511 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 86.7 kB | 33 kB | 29.8 kB |
| vue.global.prod.js | 133 kB | 49.8 kB | 44.6 kB |
### Usages
| Name | Size |... | 2023-10-20T04:05:09 | 2023-12-01T13:18:21 | {} | NONE |
vuejs | core | 1,837,182,430 | 9,439 | sxzz | Since this is a key for fetching data from an object, I don't think it's a good idea to get/set the same data from the key that is different types but has the same value.
```ts
inject(1) === inject('1')
```
So for TypeScript, I think we'd better disallow the `number` type. | 2023-12-02T15:30:20 | 2023-12-02T15:30:20 | {} | MEMBER |
vuejs | core | 1,838,274,964 | 9,335 | davidmatter | Good point! I too have been wondering how to connect defineProps and defineModel on a type level with regards to discriminated unions. Let me think about it. Maybe @pikax has an idea too? | 2023-12-04T10:41:17 | 2023-12-04T10:41:17 | {} | CONTRIBUTOR |
vuejs | core | 1,840,850,553 | 9,756 | pikax | @Alfred-Skyblue yes, even if very few people use it, is still good for the overall vue typescript usage :) | 2023-12-05T14:01:13 | 2023-12-05T14:01:13 | {
"rocket": 1
} | MEMBER |
vuejs | core | 1,884,373,624 | 10,064 | tuskermanshu |
> In reality, after assigning `foo.value = []`, the updated value of `foo.value` can only be accessed in the child component after the next execution of the render function. Therefore, when you use `foo.value.push({/**/})`, you are actually pushing onto the old `foo.value` rather than the new one. After the child... | 2024-01-10T08:14:10 | 2024-01-10T08:14:10 | {} | NONE |
vuejs | core | 1,884,416,795 | 10,051 | Josepdal | It looks like changes are being made, let's see if it solves these problems as well.
https://github.com/vuejs/core/commit/972facee0d892a1b6d9d4ad1da5da9306ed45c3f | 2024-01-10T08:46:19 | 2024-01-10T08:47:10 | {
"hooray": 2
} | NONE |
vuejs | core | 1,885,208,338 | 10,068 | LinusBorg | You haven't defined a type for the model, so it's unknown - you should do that, that's why you are using typescript, presumably
```ts
defineModel<string>()
``` | 2024-01-10T16:40:34 | 2024-01-10T17:03:49 | {} | MEMBER |
vuejs | core | 1,886,383,054 | 7,276 | 719media | Just updating, still a problem in v3.4.8:
https://play.vuejs.org/#eNrVVU1zmzAQ/SsaDok9MZDEPXRc7EmayaE9tJm2t5ADgbWtGCRGEo47DP+9KwkEdj4m6am9IEu7b3f1tPtce5dlGWwr8GZeJFNBS0UkqKpcxIwQWpRcKHLFi5IsBS/IcRDqjQYcDxxuEgFMORe7PXSqM1hSBpfyN0t1EM7QaSJgOUlxVynImjZCB0w5kwq/ra8kc3JLtIGQ52KNRuP5gtxgCCohECB5voWRNo/Hk/fC7B3GY427+6S/fUU... | 2024-01-11T06:36:29 | 2024-01-11T06:36:29 | {
"eyes": 2
} | NONE |
vuejs | core | 1,886,875,274 | 10,059 | so1ve | Still experimental, but it should resolve your problem. If you find any bug plz report it :) | 2024-01-11T10:59:31 | 2024-01-11T10:59:31 | {} | MEMBER |
vuejs | core | 1,888,801,398 | 10,087 | nova1751 | Actually, this is caused by the fact that if you insert annotations into the elements with `v-if` and `v-else`,this fragment is regarded as multiple nodes, because you should always keep the annotations inside the fragment to make it be in the right position.Thus,in this case, wrap the whole fragment into a single elem... | 2024-01-12T10:09:44 | 2024-01-12T10:14:30 | {} | NONE |
vuejs | core | 1,888,838,570 | 10,091 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 89.7 kB (**+16 B**) | 34.2 kB (**+3 B**) | 30.8 kB (**+8 B**) |
| v... | 2024-01-12T10:31:46 | 2024-01-12T10:31:46 | {} | NONE |
vuejs | core | 1,888,938,853 | 10,077 | pikax | The issue seems to be caused by `Vue/language-tools` and `ComponentInstance` from `vue`.
After https://github.com/vuejs/core/pull/9556 lands into 3.5 I'll work on tweaking language tools to support the new helpers added. Currently the PR by itself won't be closing this issue.
| 2024-01-12T11:38:19 | 2024-01-12T11:38:19 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,889,064,027 | 10,091 | edison1105 | this doesn't seem to fix that, this [demo](https://deploy-preview-10091--vue-sfc-playground.netlify.app/#eNp9kk1rwjAYx79KyEVFaSfepArb8LAdtrF5DIzSPmpcmoS8dIXS774nzVqFDQ+F5v+S/p4mLb3XOqk90DXNbGG4dsSC83rLJK+0Mo60xMBhUahKewcl6cjBqIpMsDNhslDSOlLnwgPZhOD0bjao2qial2DQGNrT6YxstjGfxNYcTWl9BSYKY32Q/9ZbJsn1HvN5EAxiG0kmn03TIFmHGzG... | 2024-01-12T12:32:42 | 2024-01-12T12:35:13 | {
"eyes": 1
} | MEMBER |
vuejs | core | 1,885,243,999 | 10,051 | yyx990803 | I can't seem to reproduce the class related warnings, can only see mismatch for `readonly` which is fixed in https://github.com/vuejs/core/commit/972facee0d892a1b6d9d4ad1da5da9306ed45c3f | 2024-01-10T17:01:23 | 2024-01-10T17:01:23 | {} | MEMBER |
vuejs | core | 1,885,579,420 | 10,051 | Josepdal | I tried the new release and my console is full of hydration warns. I think it still needs some work to fix it.
In my particular case I am using Vuetify and I am getting now "Hydration attribute mismatch" on many components.
```
[Vue warn]: Hydration attribute mismatch on <li class="v-breadcrumbs-item" style>
... | 2024-01-10T19:33:59 | 2024-01-10T19:33:59 | {} | NONE |
vuejs | core | 1,886,474,992 | 10,051 | pjninnim | I too agree with the above, some more work is still required to resolve this. I've just tested the new release and although it has resolved some of the issues, such as the one with the `readonly` attribute. This is still occurring on others, such as the `list` attribute:
```
[Vue warn]: Hydration attribute mismatch o... | 2024-01-11T07:33:22 | 2024-01-11T07:33:22 | {
"eyes": 1,
"heart": 1
} | NONE |
vuejs | core | 1,886,848,392 | 10,059 | so1ve | Use https://github.com/so1ve/vue.ts/tree/main/packages/complex-types. | 2024-01-11T10:49:35 | 2024-01-11T10:49:35 | {} | MEMBER |
vuejs | core | 1,887,544,255 | 10,069 | paro-paro | Thanks for the clarification!
| 2024-01-11T16:37:35 | 2024-01-11T16:37:35 | {} | NONE |
vuejs | core | 1,888,417,729 | 10,038 | skirtles-code | I've switched this to a draft while the conversation in #9974 is ongoing. It seems unlikely that this can be merged in its present form, but some parts of it (such as just warning for lifecycle hooks) may be salvageable. | 2024-01-12T04:33:21 | 2024-01-12T04:33:21 | {} | CONTRIBUTOR |
vuejs | core | 1,889,467,703 | 10,097 | LinusBorg | We require a runnable reproduction, preferably one that does not involve Nuxt (we don't debug Nuxt, that's or the Nuxt Team's experts to do) . If you can provide one, we can re-open the issue. | 2024-01-12T15:09:34 | 2024-01-12T15:10:26 | {
"-1": 1
} | MEMBER |
vuejs | core | 1,884,539,879 | 10,055 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7473152199)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7470525368) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/747... | 2024-01-10T10:03:49 | 2024-01-10T10:03:49 | {} | CONTRIBUTOR |
vuejs | core | 1,885,031,046 | 5,407 | AimForNaN | The warning should at least be more descriptive. It can get fairly difficult trying to track down what directive exactly it is complaining about. | 2024-01-10T15:10:20 | 2024-01-10T15:10:20 | {
"+1": 6
} | NONE |
vuejs | core | 1,885,206,872 | 10,017 | yyx990803 | A note on why we can't just do `initialVNode.el = placeholder.el`:
In component's render effect on initial mount, we use the presence of `el` to serve as a check for adopted server-rendered DOM. If `el` is present, it will perform hydration instead of client mount. This is why the previous fix broke Nuxt in ecosyste... | 2024-01-10T16:39:44 | 2024-01-10T16:39:44 | {} | MEMBER |
vuejs | core | 1,885,968,381 | 4,314 | kendru | > Any update on this? I want the user to be able to change the styling of my custom element with their CSS, but with shadow DOM it doesn't seem to be possible?
I also want a fix to this so that I can use Tailwind CSS utility classes within my Vue 3 Web Components. However, there is a way to allow users to change sel... | 2024-01-11T00:16:30 | 2024-01-11T00:16:30 | {} | NONE |
vuejs | core | 1,883,087,241 | 10,055 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.7 kB (**+61 B**) | 34.2 kB (**+6 B**) | 30.8 kB (**+17 B**) |
... | 2024-01-09T13:53:45 | 2024-01-11T09:24:18 | {} | NONE |
vuejs | core | 1,887,173,106 | 10,051 | yyx990803 | @Josepdal 3907c87ce | 2024-01-11T13:33:17 | 2024-01-11T13:33:17 | {} | MEMBER |
vuejs | core | 1,888,817,878 | 10,087 | hoshyo | > Actually, this is caused by the fact that if you insert annotations into the elements with `v-if` and `v-else`,this fragment is regarded as multiple nodes, because you should always keep the annotations inside the fragment to make it be in the right position.Thus,in this case, wrap the whole fragment into a single el... | 2024-01-12T10:17:51 | 2024-01-12T10:17:51 | {} | NONE |
vuejs | core | 1,889,102,295 | 10,091 | Doctor-wu | Whatever, I will take a look, mention me if you commit another issue~ | 2024-01-12T12:47:52 | 2024-01-12T12:47:52 | {} | MEMBER |
vuejs | core | 1,889,167,674 | 10,091 | yyx990803 | Btw good job @Doctor-wu ! I was looking at this as well before dinner and also located the issue to be in `triggerEffects`. Came back and found that you have fixed it :) | 2024-01-12T13:13:03 | 2024-01-12T13:13:03 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,889,180,283 | 10,092 | yyx990803 | Thanks for the PR, but there's already #8593 with test cases (just haven't got to merge it) | 2024-01-12T13:16:50 | 2024-01-12T13:16:50 | {} | MEMBER |
vuejs | core | 1,884,358,175 | 10,064 | Alfred-Skyblue | In reality, after assigning `foo.value = []`, the updated value of `foo.value` can only be accessed in the child component after the next execution of the render function. Therefore, when you use `foo.value.push({/**/})`, you are actually pushing onto the old `foo.value` rather than the new one. After the child compone... | 2024-01-10T08:01:21 | 2024-01-10T08:01:21 | {} | MEMBER |
vuejs | core | 1,886,740,089 | 10,076 | Doctor-wu | You should use `useCssModule` directly under the setup scope, extracting the `$style` outside to the setup scope should work | 2024-01-11T09:48:59 | 2024-01-11T09:48:59 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,887,928,253 | 10,081 | Ky6uk | @manniL yeah, and I can confirm that mine one was just fixed in the `v3.4.10` a couple of hours ago 😅 | 2024-01-11T20:40:08 | 2024-01-11T20:40:08 | {} | NONE |
vuejs | core | 1,888,709,424 | 10,088 | jacekkarczmarczyk | It's a TS issue, nothing to do with Vue
https://www.typescriptlang.org/play?#code/O4SwdgJg9sB0DOALGBlAhgNwKYDEQBssAFEAYwGssAnIA | 2024-01-12T09:11:51 | 2024-01-12T09:11:51 | {} | CONTRIBUTOR |
vuejs | core | 1,889,137,849 | 8,593 | yyx990803 | Saw this from #10087 - can you rebase? :) | 2024-01-12T13:01:47 | 2024-01-12T13:01:47 | {} | MEMBER |
vuejs | core | 1,889,171,820 | 10,090 | yyx990803 | I'm not sure if this is something we should account for (mutating state in a computed getter) as this is something we explicitly warn people against in the docs. | 2024-01-12T13:14:21 | 2024-01-12T13:14:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,889,173,665 | 10,091 | Doctor-wu | @yyx990803 glad to help~ | 2024-01-12T13:14:36 | 2024-01-12T13:14:36 | {} | MEMBER |
vuejs | core | 1,884,433,969 | 6,529 | Joshua-Leee | Hello, has this submission been published yet? If not, when is it planned to be released? | 2024-01-10T08:57:58 | 2024-01-10T08:57:58 | {} | NONE |
vuejs | core | 1,885,574,642 | 9,083 | nobunobu | up | 2024-01-10T19:30:26 | 2024-01-10T19:30:26 | {} | NONE |
vuejs | core | 1,877,061,327 | 9,992 | LinusBorg | use :deep()
https://play.vuejs.org/#eNqNU8lOHDEQ/RXLJ5AYWxGndDqIBHFIDkmU5OhLYxczBm+yq4eJ0Px7ym4YmmE9tWt/71XXLf+SkliPwDveF51tQlYAx3SigvUpZmRnK+sMu8zRM8WFbGatUFyFXk41lE0Ggk9uQCCLsd7YdXvQc2ohJ7+cAr2cpZNZ8J8DVnRMYMgjdKvpDEA66Gw5EAgFPxwe3tYmF4O+XuY4BtOxDOaTCtsGpvY4YfyIT9gXfkjiqsRA7FqdugsUxTvWPNXXyHT0WCGm0kmpTaAyA86uswiAM... | 2024-01-04T13:01:57 | 2024-01-11T07:37:35 | {} | MEMBER |
vuejs | core | 1,886,598,586 | 10,069 | yyx990803 | @jianggangsheng this is a separate issue fixed in dcc68ef7d | 2024-01-11T08:20:44 | 2024-01-11T08:20:44 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,886,726,035 | 10,036 | yyx990803 | /ecosystem-ci run | 2024-01-11T09:40:17 | 2024-01-11T09:40:17 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,886,859,996 | 10,059 | jahnli | > 使用https://github.com/so1ve/vue.ts/tree/main/packages/complex-types。
Thank you for your suggestion. I would like to ask, is this package suitable for production environment? | 2024-01-11T10:52:12 | 2024-01-11T10:52:12 | {} | NONE |
vuejs | core | 1,886,883,418 | 10,051 | pjninnim | > I too agree with the above, some more work is still required to resolve this. I've just tested the new release and although it has resolved some of the issues, such as the one with the `readonly` attribute. This is still occurring on others, such as the `list` attribute:
>
> ```
> [Vue warn]: Hydration attribute ... | 2024-01-11T11:04:06 | 2024-01-11T11:04:06 | {} | NONE |
vuejs | core | 1,887,285,769 | 6,391 | gdubicki | Hi [719media](https://github.com/719media) and everyone!
The related Safari bug tracker ticket: https://bugs.webkit.org/show_bug.cgi?id=190031
Perhaps someone here can help get it fixed. | 2024-01-11T14:22:00 | 2024-01-11T14:41:01 | {} | NONE |
vuejs | core | 1,887,354,263 | 6,715 | detheuss | Hey, I just experienced the same issue.
I only had a few child elements in the TransitionGroup, so I decided to use `v-show` directive instead of ` v-if `.
This seems to have resolved the HM issue in my case and kept the intended animation.
Hope this helps! | 2024-01-11T14:54:43 | 2024-01-11T14:54:43 | {} | NONE |
vuejs | core | 1,887,501,469 | 10,051 | Josepdal | > I tried the new release and my console is full of hydration warns. I think it still needs some work to fix it.
>
> In my particular case I am using Vuetify and I am getting now "Hydration attribute mismatch" on many components.
>
> ```
> [Vue warn]: Hydration attribute mismatch on <li class="v-breadcrumbs-ite... | 2024-01-11T16:14:03 | 2024-01-11T16:14:03 | {} | NONE |
vuejs | core | 1,888,209,407 | 9,607 | Alfred-Skyblue | /ecosystem-ci run | 2024-01-12T00:42:25 | 2024-01-12T00:42:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,717,608,041 | 8,593 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------- | ------------------ |
| runtime-dom.global.prod.js | 89.7 kB (**+5 B**) | 34.2 kB (**+13 B**) | 30.8 kB (**-1 B**) |
| vue.... | 2023-09-13T13:10:31 | 2024-01-12T13:47:27 | {} | NONE |
vuejs | core | 1,884,395,036 | 10,051 | Josepdal | I am reopening it because there still seems to be a problem.
Examples:
Hydration attribute mismatch on <input...
https://stackblitz.com/edit/nuxt-starter-14rqc1
Also migueabellan is having same issues with VNavigationDrawer and VAppBar.
Hydration attribute mismatch on <header...
Here is his code: https://... | 2024-01-10T08:30:30 | 2024-01-10T08:30:30 | {} | NONE |
vuejs | core | 1,886,696,113 | 10,069 | yyx990803 | For this specific warning in Vuetify, it is indeed related to #5300 because Vuetify uses `computed` to manage nested z-index for layouts, so this is no longer an issue with the hydration mismatch detection logic itself, but rather the detection is revealing real issues in other areas. | 2024-01-11T09:21:06 | 2024-01-11T09:21:06 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,886,836,510 | 10,059 | jahnli | But we are not sure which types can be parsed at present. Currently, `boolean` cannot be parsed, but `number` can. If `@vue-ignore` is not used, external props cannot be imported.
@yyx990803 | 2024-01-11T10:45:31 | 2024-01-11T10:46:27 | {} | NONE |
vuejs | core | 1,887,568,039 | 10,077 | zomakus | I've been doing some more digging and the issue seems to be caused by the fact that `typeof GenericComponent<TypeParameter>` (in the case of the provided example, this would be `typeof OrderedList<ListItem>`) matches the following type condition used when defining `ComponentInstance`: `T extends FunctionalComponent<inf... | 2024-01-11T16:51:13 | 2024-01-11T16:51:49 | {} | NONE |
vuejs | core | 1,887,724,336 | 10,069 | jiangdotgs | > @jianggangsheng[这是dcc68ef](https://github.com/vuejs/core/commit/dcc68ef7d48973abd8dd3178b46e50e3b0785ea4)中修复的一个单独问题[](https://github.com/vuejs/core/commit/dcc68ef7d48973abd8dd3178b46e50e3b0785ea4)
但好像没有完全解决这个问题，el-form组件写出来的错误是没有了，不过el-dialog和el-alert的警告还在
<img width="1512" alt="image" src="https://github.com/vue... | 2024-01-11T18:24:34 | 2024-01-11T18:24:34 | {} | NONE |
vuejs | core | 1,889,142,987 | 8,593 | edison1105 | @yyx990803 done | 2024-01-12T13:03:59 | 2024-01-12T13:03:59 | {} | MEMBER |
vuejs | core | 1,886,328,762 | 4,314 | conanliuhuan | > Any update on this? I want the user to be able to change the styling of my custom element with their CSS, but with shadow DOM it doesn't seem to be possible?
通过createApp后直接mount的方式挂载，可避免shadowRoot。这可能算是一个Hack方法。不过我用起来很有效。感兴趣的话可以看一下我的博客：
https://blog.panda-studio.cn/vue_web_component_webpack_compiler | 2024-01-11T05:46:25 | 2024-01-11T05:46:25 | {
"+1": 1
} | NONE |
vuejs | core | 1,886,615,152 | 10,050 | peter-gy | > Closing this one for now then - please open a new issue if you find out the root cause of your leak is still from Vue core.
We had multiple leak sources, but running the tests using a production build as per your suggestion and patching the leak in a Vuetify component (vuetifyjs/vuetify#19024) seem to have solved ... | 2024-01-11T08:33:04 | 2024-01-11T08:33:04 | {
"+1": 1
} | NONE |
vuejs | core | 1,887,145,859 | 10,059 | jahnli | @so1ve Do you still need to specify @vue-ignore after using complex-types? | 2024-01-11T13:16:54 | 2024-01-11T13:16:54 | {} | NONE |
vuejs | core | 1,887,354,146 | 10,078 | yyx990803 | The link is not a valid reproduction as it's using slot syntax inside native `div`. It's working as intended if it's a component:
https://play.vuejs.org/#eNp9UcFOAjEQ/ZVmPHDB3QM3giZgOOhBjXrsZV0GKHbbpp0iCeHfnXZZXKJw67z3Zvpm3h6mzhXbiDCGSai9ciQCUnT30qjGWU9iOotE1oilt40YFOWDbXLHQJpJ2bawmAvCxumKkCshJtXtZ+7LFdcdK25UfUIlrVF... | 2024-01-11T14:54:39 | 2024-01-11T14:56:14 | {} | MEMBER |
vuejs | core | 1,887,896,401 | 10,081 | Ky6uk | Could be related, but looks like the issue below was fixed in the `v3.4.10`.
With `v3.4.9` the code `<input :maxlength="undefined" />` also causes the hydration issue
```
[Vue warn]: Hydration attribute mismatch on <input value>
- rendered on server: maxlength="undefined"
- expected on client: maxlength=... | 2024-01-11T20:15:50 | 2024-01-11T20:15:50 | {} | NONE |
vuejs | core | 1,888,216,289 | 9,607 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7496351878)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7470525368) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/749... | 2024-01-12T00:49:44 | 2024-01-12T00:49:44 | {} | CONTRIBUTOR |
vuejs | core | 1,888,757,438 | 10,090 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.9 kB (**+136 B**) | 34.2 kB (**+49 B**) | 30.9 kB (**+35 B**)... | 2024-01-12T09:42:30 | 2024-01-12T09:42:30 | {} | NONE |
vuejs | core | 1,889,121,554 | 10,087 | edison1105 | duplicate of https://github.com/vuejs/core/issues/5203 | 2024-01-12T12:54:58 | 2024-01-12T12:54:58 | {} | MEMBER |
vuejs | core | 1,889,399,367 | 10,051 | Josepdal | > Should be fixed now by [08b60f5](https://github.com/vuejs/core/commit/08b60f5d0d5b57fcf3347ef66cbeab472c475a88) and released in 3.4.11
We are getting close.
**ERRORS IN THE PAST:**
```
[Vue warn]: Hydration attribute mismatch on <li class="v-breadcrumbs-item" style>
<li class="v-breadcrumbs-item" style="... | 2024-01-12T14:44:23 | 2024-01-12T14:44:23 | {} | NONE |
vuejs | core | 1,886,738,071 | 10,036 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7486885832)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7470525368) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/748... | 2024-01-11T09:47:42 | 2024-01-11T09:47:42 | {} | CONTRIBUTOR |
vuejs | core | 1,886,845,188 | 10,059 | jahnli | But I found that if I remove @vue-ignore, the parsing is still wrong | 2024-01-11T10:48:33 | 2024-01-11T10:48:33 | {} | NONE |
vuejs | core | 1,886,930,747 | 10,051 | PP-Tom | With Nuxt Image I'm getting a lot of hydration errors on the latest Vue (`3.4.9`)
```
- rendered on server: referrerpolicy="undefined"
- expected on client: referrerpolicy=""
- rendered on server: usemap="undefined"
- expected on client: usemap=""
- rendered on server: crossorigin="undefined"
... | 2024-01-11T11:21:44 | 2024-01-11T11:22:11 | {
"+1": 1,
"eyes": 2
} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.