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,888,778,303 | 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: cros... | 2024-01-12T09:54:25 | 2024-01-12T09:54:25 | {
"+1": 3
} | NONE |
vuejs | core | 1,888,838,425 | 10,091 | Doctor-wu | <img width="705" alt="CleanShot 2024-01-12 at 15 20 14@2x" src="https://github.com/vuejs/core/assets/44631608/658cc87c-359e-4c62-9338-72e0b9a0548d">
Will add some description and test suite later | 2024-01-12T10:31:39 | 2024-01-12T10:31:39 | {} | MEMBER |
vuejs | core | 1,887,139,110 | 10,059 | jahnli | Ok, thank you | 2024-01-11T13:13:17 | 2024-01-11T13:13:17 | {} | NONE |
vuejs | core | 1,887,097,663 | 10,059 | yyx990803 | It only affects props that have special runtime casting behavior (mostly boolean). | 2024-01-11T12:49:06 | 2024-01-11T12:49:14 | {} | MEMBER |
vuejs | core | 1,888,389,962 | 10,085 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------ |
| runtime-dom.global.prod.js | 89.7 kB (**+8 B**) | 34.2 kB (**+4 B**) | 30.8 kB (**-8 B**) |
| vue.glo... | 2024-01-12T03:48:37 | 2024-01-12T03:48:37 | {} | NONE |
vuejs | core | 1,888,397,208 | 10,086 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.7 kB | 34.2 kB | 30.8 kB |
| vue.global.prod.js | 147 kB | 53.4 kB | 47.8 kB |
### Usages
| Name | Size |... | 2024-01-12T03:59:55 | 2024-01-12T03:59:55 | {} | NONE |
vuejs | core | 1,884,778,050 | 10,039 | thinlizzy | ```
<script>
var __VUE_PROD_DEVTOOLS__ = false
</script>
```
I solved everything with this at the start of my html... | 2024-01-10T12:40:46 | 2024-01-10T12:40:46 | {} | NONE |
vuejs | core | 1,889,028,244 | 10,091 | Doctor-wu | <img width="1081" alt="CleanShot 2024-01-12 at 20 15 42@2x" src="https://github.com/vuejs/core/assets/44631608/297cf088-deac-474f-a9d1-81262e59c59c">
<img width="671" alt="CleanShot 2024-01-12 at 20 14 28@2x" src="https://github.com/vuejs/core/assets/44631608/9d218c0b-2db7-4a19-983c-d12b0b88b849">
| 2024-01-12T12:16:31 | 2024-01-12T12:16:31 | {} | MEMBER |
vuejs | core | 1,889,325,982 | 10,051 | yyx990803 | Should be fixed now by 08b60f5d0 and released in 3.4.11 | 2024-01-12T14:16:55 | 2024-01-12T14:16:55 | {
"eyes": 1,
"heart": 1
} | MEMBER |
vuejs | core | 1,885,678,876 | 10,050 | peter-gy | > Then unfortunately, your demo isn't showing the actual culprit because the detached elements you see are retained by `__vnode` properties which are only attached in development mode for devtools usage. You can verify this by running a production build of your reproduction and see that there won't be any detached node... | 2024-01-10T20:33:38 | 2024-01-10T20:33:38 | {} | NONE |
vuejs | core | 1,886,718,325 | 10,036 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.7 kB | 34.2 kB | 30.8 kB |
| vue.global.prod.js | 147 kB | 53.4 kB | 47.7 kB |
### Usages
| Name | Size |... | 2024-01-11T09:35:09 | 2024-01-11T09:35:09 | {} | NONE |
vuejs | core | 1,886,832,852 | 10,059 | yyx990803 | This is expected behavior because you are using the `@vue-ignore` comment, which means the Vue compiler will not try to resolve the actual types of `UploadProps` and just assume these props have no specified types at runtime.
Unfortunately currently there is no proper fix for this because the `UploadProps` from `nai... | 2024-01-11T10:43:08 | 2024-01-11T10:43:08 | {} | MEMBER |
vuejs | core | 1,886,939,057 | 10,051 | Josepdal | Still having the same errors
Here is an example:
https://stackblitz.com/edit/nuxt-starter-14rqc1 | 2024-01-11T11:27:33 | 2024-01-11T11:27:52 | {
"+1": 2
} | NONE |
vuejs | core | 1,886,431,893 | 10,069 | jiangdotgs | <img width="1057" alt="image" src="https://github.com/vuejs/core/assets/21185192/19b6876f-9b38-44e0-a418-44f7e2d73ea8">
我也遇到了哎，VUE3.4.8 nuxt3.9.1 ELEMENT PLUS2.4.4 | 2024-01-11T07:15:20 | 2024-01-11T07:15:51 | {} | NONE |
vuejs | core | 1,886,601,202 | 10,050 | yyx990803 | 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. | 2024-01-11T08:22:47 | 2024-01-11T08:22:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,886,665,419 | 10,055 | yyx990803 | /ecosystem-ci run | 2024-01-11T09:02:12 | 2024-01-11T09:02:12 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,886,669,327 | 10,075 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 89.7 kB (**-7 B**) | 34.2 kB (**-2 B**) | 30.8 kB (**-8 B**) |
| vue.... | 2024-01-11T09:04:28 | 2024-01-11T09:04:28 | {} | NONE |
vuejs | core | 1,886,678,445 | 10,055 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7486450920)
| 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:09:33 | 2024-01-11T09:09:33 | {} | CONTRIBUTOR |
vuejs | core | 1,886,788,089 | 10,076 | SpukiBugi | That fixed it, thanks! | 2024-01-11T10:16:23 | 2024-01-11T10:16:23 | {} | NONE |
vuejs | core | 1,887,517,136 | 7,215 | paro-paro | Are there any plans on fixing this?
This is still happening on 3.4.10 and is heavily affecting when using vuetify components.
Related [vuetify issue](https://github.com/vuetifyjs/vuetify/issues/18021) | 2024-01-11T16:22:34 | 2024-01-11T16:50:55 | {} | NONE |
vuejs | core | 1,888,899,269 | 10,092 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.8 kB (**+61 B**) | 34.2 kB (**+45 B**) | 30.8 kB (**+16 B**) |
... | 2024-01-12T11:10:25 | 2024-01-12T11:10:25 | {} | NONE |
vuejs | core | 1,888,996,963 | 10,090 | Doctor-wu | Maybe properly fixed in https://github.com/vuejs/core/pull/10091 | 2024-01-12T12:02:04 | 2024-01-12T12:02:04 | {} | MEMBER |
vuejs | core | 1,889,142,424 | 10,093 | yyx990803 | This is expected because the options for `defineModel` is used as the props options and will be moved outside of setup scope. Similar to the options in `defineProps` and `defineOptions`.
Note if the constant is a primitive value that can be safely hoisted out, this will work; however, your constant value is an objec... | 2024-01-12T13:03:44 | 2024-01-12T13:50:11 | {} | MEMBER |
vuejs | core | 1,884,370,402 | 10,064 | LinusBorg | When you keep in mind that `defineModel()` is a convenience shortcut for the following, it becomes more appearant:
```js
const props = defineProps(['modelValue'])
const emits = defineEmits(['update:modelValue'])
// you basically did this:
emit('update:modelValue', [])
props.modelValue.push(....)
``` | 2024-01-10T08:11:28 | 2024-01-10T08:11:49 | {} | MEMBER |
vuejs | core | 1,884,527,697 | 10,055 | edison1105 | /ecosystem-ci run | 2024-01-10T09:56:34 | 2024-01-10T09:56:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,885,532,663 | 10,068 | rakkur | @LinusBorg - Thank you! That didn't fire on any other definition, so I didn't realize I had to specify it. Appreciate your time! | 2024-01-10T19:18:24 | 2024-01-10T19:18:24 | {} | NONE |
vuejs | core | 1,886,851,738 | 4,465 | yyx990803 | Closed in favor of #9556 | 2024-01-11T10:50:28 | 2024-01-11T10:50:28 | {} | MEMBER |
vuejs | core | 1,887,326,019 | 10,059 | so1ve | No | 2024-01-11T14:39:28 | 2024-01-11T14:39:28 | {} | MEMBER |
vuejs | core | 1,887,909,424 | 10,081 | TheAlexLichter | @Ky6uk thanks, updated the issue and indeed, the `disabled` part is gone but `draggable` is still causing a hydration error. | 2024-01-11T20:25:42 | 2024-01-11T20:25:42 | {} | NONE |
vuejs | core | 1,888,191,346 | 10,078 | Plumbiu | Sorry for the invalid reproduction, it suddenly stopped reporting errors this morning, I think it’s because my computer’s performance is not good enough, causing the html structure to not be recognized successfully. | 2024-01-12T00:23:31 | 2024-01-12T00:23:31 | {} | CONTRIBUTOR |
vuejs | core | 1,889,099,850 | 10,091 | Doctor-wu | > this doesn't seem to fix that, this [demo](https://deploy-preview-10091--vue-sfc-playground.netlify.app/#eNp9kk1rwjAYx79KyEVFaSfepArb8LAdtrF5DIzSPmpcmoS8dIXS774nzVqFDQ+F5v+S/p4mLb3XOqk90DXNbGG4dsSC83rLJK+0Mo60xMBhUahKewcl6cjBqIpMsDNhslDSOlLnwgPZhOD0bjao2qial2DQGNrT6YxstjGfxNYcTWl9BSYKY32Q/9ZbJsn1HvN5EAxiG0kmn03TIFmHG... | 2024-01-12T12:46:48 | 2024-01-12T12:46:48 | {} | MEMBER |
vuejs | core | 1,884,691,586 | 6,529 | edison1105 | @Joshua-Leee It's released in v3.3.6. | 2024-01-10T11:43:15 | 2024-01-10T11:43:15 | {} | MEMBER |
vuejs | core | 1,885,237,076 | 10,051 | yyx990803 | ~~Looks like a duplicate of #10057~~ | 2024-01-10T16:57:13 | 2024-01-10T16:58:09 | {} | MEMBER |
vuejs | core | 1,885,245,993 | 10,051 | yyx990803 | If the `readonly` issues are the only ones left then I'm closing this. Please let me know if the `class` mismatch issue persists. | 2024-01-10T17:02:33 | 2024-01-10T17:02:33 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,889,031,961 | 10,091 | Doctor-wu | @johnsoncodehk Could you help to review this? First time to read the new reactivity system, not sure if it's totally ok, but it works to solve the issue and pass all tests | 2024-01-12T12:18:09 | 2024-01-12T12:18:09 | {} | MEMBER |
vuejs | core | 1,889,147,881 | 10,091 | yyx990803 | I think this is the right fix for #10082. The other case from #10090 is not the same underlying issue (mutating state in another computed) | 2024-01-12T13:05:28 | 2024-01-12T13:05:28 | {
"rocket": 4
} | MEMBER |
vuejs | core | 1,889,182,747 | 10,069 | yyx990803 | These are z-index issues probably with the same cause (#5300 computed z-index not updated during SSR) | 2024-01-12T13:17:57 | 2024-01-12T13:17:57 | {} | MEMBER |
vuejs | core | 1,881,896,826 | 9,206 | ferferga | @Alfred-Skyblue Besides Keep-Alive, I guess this is something that could also be applicable here?: https://github.com/vuejs/rfcs/discussions/501 | 2024-01-08T22:06:37 | 2024-01-08T22:06:37 | {} | CONTRIBUTOR |
vuejs | core | 1,882,749,456 | 9,370 | Disservin | Any update on this? ^^ There have been 3 issues related to this #9264, #8898 and #9617 and another issue which was opened in pinia. | 2024-01-09T09:54:52 | 2024-01-09T09:54:52 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 1,884,233,701 | 10,058 | Inori-Lover | > This is the expected behavior: during the access of `computed`, it is stored in the `ref` (show.dep) that is accessed during execution. This is done to notify the `computed` to update when the value of `show` changes.
you mean: computed is not composable?
please do not misundestand: i do not mind ReactiveEffect... | 2024-01-10T05:51:22 | 2024-01-10T05:55:55 | {} | NONE |
vuejs | core | 1,882,643,206 | 10,046 | yyx990803 | You are mutating the same plain object and then assigning that same object to a ref's value - that's expected to not trigger any changes by default because to the ref, the old `value` and the new `value` are the same object. (even in 3.3 you need the `triggerRef` line for it to work).
~~The fact that `triggerRef` do... | 2024-01-09T08:53:29 | 2024-01-09T09:03:44 | {} | MEMBER |
vuejs | core | 1,849,161,290 | 9,783 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d5fe8ba60f8dc7a0fffa4d0fe7a185889fd4286a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-12-11T00:54:47 | 2024-01-09T12:53:12 | {} | NONE |
vuejs | core | 1,883,162,920 | 10,050 | boutils | I think you closed this issue too quickly, I can reproduce these detached nodes even when `hoistStatic` is set to `false`. | 2024-01-09T14:35:06 | 2024-01-09T14:35:25 | {} | NONE |
vuejs | core | 1,883,204,289 | 10,050 | peter-gy | > Do note the detached elements do **not** increase over time so it is **not** a memory leak (which implies the memory would keep growing indefinitely).
In our case this is exactly what we experience. We have an E2E test suite where thousands of scenarios are executed one after the other. The memory occupied by the ... | 2024-01-09T14:56:50 | 2024-01-09T14:57:20 | {} | NONE |
vuejs | core | 1,820,379,919 | 9,563 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2023-11-21T07:35:44 | 2024-01-06T19:24:24 | {} | NONE |
vuejs | core | 1,881,939,604 | 10,039 | LinusBorg | That may be the case. I can't replicate what you do since you did not share a reproduction.
Something on your end seems to import the bundler vue version. Thats not normal. What that is, I cant guess. | 2024-01-08T22:44:53 | 2024-01-08T22:44:53 | {} | MEMBER |
vuejs | core | 1,882,928,184 | 9,651 | ferferga | @Alfred-Skyblue Great then! That's exactly what I had in mind for my RFC and I think it should be enough to solve all the quirks demoed in the different playgrounds.
I thought you meant that only pausing the first child node of Transition would not be enough and it had to be done recursively. | 2024-01-09T11:49:35 | 2024-01-09T11:49:35 | {} | CONTRIBUTOR |
vuejs | core | 1,879,795,512 | 10,010 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------ |
| runtime-dom.global.prod.js | 89.4 kB (**+4 B**) | 34 kB (**+3 B**) | 30.7 kB (**+8 B**) |
| vue.glo... | 2024-01-06T19:30:53 | 2024-01-06T19:30:53 | {} | NONE |
vuejs | core | 1,879,823,236 | 10,016 | skirtles-code | The underlying problem here is similar to #9968. The `reactivity-transform` package has been removed, but it may still be present on your system because it contains uncommitted files (e.g. the output from an old build).
I've encountered this myself a few times when moving back and forth between branches. To fix it y... | 2024-01-06T20:43:03 | 2024-01-06T20:43:03 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,880,054,290 | 10,027 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.5 kB (**+90 B**) | 34.1 kB (**+33 B**) | 30.7 kB (**+19 B**) |
... | 2024-01-07T13:03:16 | 2024-01-07T14:09:55 | {} | NONE |
vuejs | core | 1,880,407,649 | 10,026 | edison1105 | > @edison1105 Yes I noticed that too. Is there any way to opt out of the optimization and receive the actual vnode?
there seems no other way except for what you mentioned above. | 2024-01-08T05:31:52 | 2024-01-08T05:31:52 | {} | MEMBER |
vuejs | core | 1,880,752,264 | 10,014 | LinusBorg | using a Set would indeed be more performant, but it doesn't cover all use cases, unfortunately.
We currently use a `looseEqual()` function to compare values, because v-model select does support objects, and also supports *inline-defined* objects like this:
```html
<option :value="{ size: 'small' }"></option>
<o... | 2024-01-08T10:39:00 | 2024-01-08T18:42:17 | {} | MEMBER |
vuejs | core | 1,884,296,577 | 10,058 | Inori-Lover | cool, thanks | 2024-01-10T07:03:45 | 2024-01-10T07:03:45 | {} | NONE |
vuejs | core | 1,879,881,379 | 10,026 | LinusBorg | Hey Alex, I think you inserted the wrong link for the repro. | 2024-01-06T23:51:45 | 2024-01-06T23:52:04 | {} | MEMBER |
vuejs | core | 1,880,055,633 | 10,026 | TheAlexLichter | @edison1105 Yes I noticed that too. Is there any way to opt out of the optimization and receive the actual vnode? | 2024-01-07T13:08:19 | 2024-01-07T13:08:19 | {} | NONE |
vuejs | core | 1,880,438,917 | 9,790 | yyx990803 | Closing this for now - we will figure out a better way in the next minor cycle. | 2024-01-08T06:18:07 | 2024-01-08T06:18:07 | {} | MEMBER |
vuejs | core | 1,882,912,428 | 9,765 | marakalwa | Also experiencing this exact error, using computed worked for me, toRefs working correctly would be even better though | 2024-01-09T11:38:30 | 2024-01-09T11:38:30 | {} | NONE |
vuejs | core | 1,883,034,367 | 10,039 | thinlizzy | > If you check your network tab - that happens because of the other package you have incluced, which you get from jsdelivr.
>
> jsdelivr's esm support automatically rewrites imports the the matching urls on jsdelivr, and that rewrite results in a rewrite to esm-bundler.
>
> Are you saying this exact same file fro... | 2024-01-09T13:09:09 | 2024-01-09T13:09:09 | {} | NONE |
vuejs | core | 1,883,180,453 | 10,054 | yyx990803 | The license inclusion requirement only applies to users using the software, not the copyright owner distributing it. Technically the license is already distributed as part of the npm package (e.g. https://unpkg.com/browse/vue@3.4.7/LICENSE), but I guess we can include a small banner in individual files as well. | 2024-01-09T14:44:30 | 2024-01-09T14:44:30 | {} | MEMBER |
vuejs | core | 1,883,202,743 | 10,050 | boutils | I tend to disagree @yyx990803. In my "large" application, the `v-for` iterates on some dynamic user input elements. Because of these detached elements, the memory increases and increases indefinitely. | 2024-01-09T14:56:00 | 2024-01-09T14:56:00 | {} | NONE |
vuejs | core | 1,880,082,357 | 6,745 | VladBrok | > There are two issues at play here:
>
> 1. Components used in `<TransitionGroup>` break if they don't have a single-element root but render a Fragment (multiple root nodes). This is currently not documented for `<TransitionGroup>`, only for `<Transition>`:
> 
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7418172018) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/744... | 2024-01-08T01:06:23 | 2024-01-08T01:06:23 | {} | CONTRIBUTOR |
vuejs | core | 1,880,528,444 | 9,336 | davidmatter | @pikax do you know when this one will be merged? | 2024-01-08T08:01:22 | 2024-01-08T08:01:22 | {
"+1": 6
} | CONTRIBUTOR |
vuejs | core | 1,882,538,638 | 10,016 | yyx990803 | This is a nice to have since the lingering folder isn't checked in the branches that don't have it, so ignoring it saves the trouble. (we may have such packages in the future) | 2024-01-09T07:29:23 | 2024-01-09T07:30:24 | {} | MEMBER |
vuejs | core | 1,884,257,433 | 10,058 | yyx990803 | This is incorrect usage - you should not be creating `computed` inside other `computed`... please don't do this.
`computed` should be created during component setup. In your case `acc` should just be returning the value directly:
https://play.vuejs.org/#eNqNUk1r20AQ/SvTvVimsURxoWBk163JoYXEpclRUGRpZG8i7S77YRuM/ntn... | 2024-01-10T06:20:20 | 2024-01-10T06:25:36 | {} | MEMBER |
vuejs | core | 1,880,202,983 | 10,001 | modelair | this is related to oruga, not vue. author must fix his library use-hooks | 2024-01-07T22:45:33 | 2024-01-07T22:45:33 | {} | NONE |
vuejs | core | 1,880,570,738 | 10,011 | yyx990803 | A note on [e2ac3b5](https://github.com/vuejs/core/pull/10011/commits/e2ac3b547be9bfa3fb248a0376e749275c060b78) - `getSSRProps` is only initialized on the directives during server render, and is not available in the client build, so we can't rely on that to handle SSR injected props.
For now, we'll just special-case ... | 2024-01-08T08:36:05 | 2024-01-08T08:36:05 | {} | MEMBER |
vuejs | core | 1,880,904,372 | 10,024 | yangxiuxiu1115 | Updated fix | 2024-01-08T12:24:59 | 2024-01-08T12:24:59 | {} | CONTRIBUTOR |
vuejs | core | 1,881,057,361 | 10,034 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34.1 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-08T13:54:33 | 2024-01-08T13:54:33 | {} | NONE |
vuejs | core | 1,881,133,910 | 10,036 | lehni | @yyx990803 apologies for not creating the issue for this yet, it's still on my TODO list. Do you still need the issue now? I will test ASAP and report back in a bit. | 2024-01-08T14:37:35 | 2024-01-08T14:37:35 | {} | CONTRIBUTOR |
vuejs | core | 1,882,792,313 | 9,651 | ferferga | @Alfred-Skyblue (Follow-up of [this discussion](https://github.com/vuejs/core/pull/9206#issuecomment-1881896826))
If there's not a better way to pass the "paused" state down (with inject/provide for example) and must be done with recursivity, instead of doing it from the top to the bottom as you suggested, what if i... | 2024-01-09T10:19:57 | 2024-01-09T10:19:57 | {
"+1": 1,
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 1,882,937,172 | 10,039 | thinlizzy | Sorry. Here is http://baudejogos.net/vuetest.html
It's a simple test example that worked before and now it keeps crashing with that same error. This is happening in the rest of the site.
Wondering why suddenly the bundler became in the way... | 2024-01-09T11:55:43 | 2024-01-09T11:55:43 | {} | NONE |
vuejs | core | 1,883,015,495 | 10,039 | interesse | I have the same issue. I can reproduce it with the example given by [Parcel](https://parceljs.org/languages/vue/) with a production build.
It still worked in version v3.4.0-rc.1 and is broken since version v3.4.0-rc.2. I assume it broke with this commit: https://github.com/vuejs/core/commit/ee68c525f06e02c78655ade68... | 2024-01-09T12:51:47 | 2024-01-09T12:51:47 | {} | NONE |
vuejs | core | 1,883,346,227 | 10,039 | interesse | > That sounds like a different issue, namely that Parcel doesn't support that new Flag yet which the bundler version expects to be set one way or another. You should be able to inject that as a global yourself through parcel's config
Then the documentation is wrong because it states in multiple places:
> Vue will w... | 2024-01-09T16:12:08 | 2024-01-09T16:12:08 | {} | NONE |
vuejs | core | 1,884,134,664 | 10,058 | Alfred-Skyblue | This is the expected behavior: during the access of `computed`, it is stored in the `ref` (show.dep) that is accessed during execution. This is done to notify the `computed` to update when the value of `show` changes. | 2024-01-10T03:30:35 | 2024-01-10T03:30:35 | {} | MEMBER |
vuejs | core | 1,884,234,406 | 10,057 | KazariEX | ``nuxt-img`` has the same issue. | 2024-01-10T05:52:21 | 2024-01-10T05:52:21 | {} | MEMBER |
vuejs | core | 1,879,884,422 | 10,026 | TheAlexLichter | Hey Thorsten! Whoops, you are right, my bad. Updated the link 🙏 | 2024-01-07T00:03:31 | 2024-01-07T00:03:31 | {} | NONE |
vuejs | core | 1,882,129,964 | 9,990 | Joshua-Leee | I'm sorry, do you mean the memory that the memory snapshot shows? Because my company's project is relatively large, there are a lot of page data, and keepalive is also used, opening a page will increase tens of megabytes of memory, when closing the page, there will be a lot of free dom elements, resulting in the browse... | 2024-01-09T01:33:39 | 2024-01-09T01:33:39 | {} | NONE |
vuejs | core | 1,882,707,233 | 10,049 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34.1 kB | 30.7 kB |
| vue.global.prod.js | 147 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-09T09:33:02 | 2024-01-09T09:33:02 | {} | NONE |
vuejs | core | 1,882,909,088 | 9,651 | Alfred-Skyblue | @ferferga My expression may have been unclear. What I meant is to pause only the components that affect the Transition animation, without recursively pausing all child components. In other words, I will only invoke `scope.pause` on a specific component that influences the animation. Conversely, if we perform recursion,... | 2024-01-09T11:35:59 | 2024-01-09T11:35:59 | {
"+1": 1,
"hooray": 1,
"rocket": 1
} | MEMBER |
vuejs | core | 1,884,326,632 | 10,064 | tuskermanshu | After testing, it was found that if the array is not cleared when clicking, the data can be displaye
d correctly. | 2024-01-10T07:32:47 | 2024-01-10T07:32:47 | {} | NONE |
vuejs | core | 1,880,299,380 | 10,029 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-08T02:12:03 | 2024-01-08T02:12:03 | {} | NONE |
vuejs | core | 1,880,713,039 | 10,001 | yyx990803 | I've added a warning if `getCurrentInstance()` is called inside a `computed` getter in https://github.com/vuejs/core/commit/324e817ef8d00c091e5d1537789542241c876d66
The usage is incorrect and should be fixed in `oruga`. | 2024-01-08T10:14:54 | 2024-01-08T10:14:54 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,882,533,794 | 9,991 | yyx990803 | /ecosystem-ci run | 2024-01-09T07:24:38 | 2024-01-09T07:24:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,880,258,598 | 10,027 | edison1105 | /ecosystem-ci run | 2024-01-08T00:58:56 | 2024-01-08T00:58:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,880,724,796 | 10,027 | yyx990803 | See simpler fix in d9162dfc2 | 2024-01-08T10:20:50 | 2024-01-08T10:20:50 | {} | MEMBER |
vuejs | core | 1,880,890,218 | 10,024 | yangxiuxiu1115 | From the commit perspective, it seems that this part of the code was intentionally removed, so I changed PR to draft | 2024-01-08T12:16:22 | 2024-01-08T12:16:22 | {} | CONTRIBUTOR |
vuejs | core | 1,882,019,020 | 8,678 | 719media | Just noting for reference, verified this is still a problem with vue v3.4.6 | 2024-01-09T00:11:42 | 2024-01-09T00:11:42 | {} | NONE |
vuejs | core | 1,883,195,111 | 10,050 | yyx990803 | Do note the detached elements do **not** increase over time so it is **not** a memory leak (which implies the memory would keep growing indefinitely). | 2024-01-09T14:52:01 | 2024-01-09T14:52:01 | {} | MEMBER |
vuejs | core | 1,884,254,253 | 10,060 | yyx990803 | The better fix is dealing with boolean attributes w/ separate logic - handling special cases like this is fragile. | 2024-01-10T06:16:34 | 2024-01-10T06:16:34 | {} | MEMBER |
vuejs | core | 1,884,261,116 | 10,059 | yangxiuxiu1115 | 请提供一个最小可复现问题的仓库链接，就图片来看不能确定到底是谁的问题 | 2024-01-10T06:24:37 | 2024-01-10T06:24:37 | {} | CONTRIBUTOR |
vuejs | core | 1,884,304,237 | 10,059 | jahnli | @RicardoErii
https://github.com/jahnli/test1
运行后只需要关注
`src\views\login\login.vue`
`src\components\base-ui\base-upload\base-upload.vue` | 2024-01-10T07:11:51 | 2024-01-10T07:12:02 | {} | NONE |
vuejs | core | 1,880,557,112 | 10,012 | sporritt | This was reported by a jsPlumb Toolkit licensee also, in relation to one of our demonstration apps:
```html
<jsplumb-toolkit ref="toolkitComponent"
surface-id="surfaceId"
:render-params="this.renderParams()"
:view="this.viewPa... | 2024-01-08T08:24:52 | 2024-01-08T08:24:52 | {} | NONE |
vuejs | core | 1,880,591,787 | 10,026 | yyx990803 | The purpose of `getSSRProps` isn't for you to **alter** the vnode - you are not supposed to mutate anything, only returning additional props to be added. It also needs to work for both optimized and vdom based SSR, so there is no way to provide the vnode when there is no vdom being created. | 2024-01-08T08:52:44 | 2024-01-08T08:52:44 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,881,353,309 | 5,161 | cexbrayat | This is no longer necessary now that https://github.com/vuejs/core/pull/9997 has been merged | 2024-01-08T15:58:54 | 2024-01-08T15:58:54 | {} | MEMBER |
vuejs | core | 1,882,782,219 | 10,049 | yyx990803 | Proper fix in 923d560d0 | 2024-01-09T10:14:11 | 2024-01-09T10:14:11 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,883,209,820 | 10,050 | yyx990803 | Then unfortunately, your demo isn't showing the actual culprit because the detached elements you see are retained by `__vnode` properties which are only attached in development mode for devtools usage. You can verify this by running a production build of your reproduction and see that there won't be any detached nodes.... | 2024-01-09T14:59:47 | 2024-01-09T15:00:17 | {} | MEMBER |
vuejs | core | 1,883,241,976 | 10,054 | Disservin | Even worse in the bundlers case I'd say. From what I can tell vite/rollup at least preserves any comments starting with `@license`, like the pinia banner. | 2024-01-09T15:16:36 | 2024-01-09T15:16:36 | {} | CONTRIBUTOR |
vuejs | core | 1,879,907,670 | 10,026 | edison1105 | It is always null in SSR optimization mode. That may be a limitation.
https://github.com/vuejs/core/blob/bfe6b459d3a0ce6168611ee1ac7e6e789709df9d/packages/server-renderer/src/helpers/ssrGetDirectiveProps.ts#L12-L22 | 2024-01-07T01:36:47 | 2024-01-07T01:38:14 | {} | MEMBER |
vuejs | core | 1,881,990,691 | 10,041 | yyx990803 | /ecosystem-ci run | 2024-01-08T23:39:58 | 2024-01-08T23:39:58 | {
"+1": 2
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.