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,898,185,471 | 10,148 | yyx990803 | Your reproduction doesn't show the error described. A proper reproduction is needed. | 2024-01-18T10:15:23 | 2024-01-18T10:15:23 | {} | MEMBER |
vuejs | core | 1,901,334,341 | 10,156 | felixxxxxs | > By the way I realised thta we dont need to downgrade all the way down to 3.3.x. Vue 3.4.2 is also works fine. This way we can get rid of the error and get benefits from vue 3.4
I can use Vue up to v3.4.8.
**v3.4.9** and higher produce the errors
>
> At your first reproduction, you are not supposed to add `:` before `v-model`
After correcting that, the behavior is unchanged. | 2024-01-21T05:41:06 | 2024-01-21T05:41:06 | {} | NONE |
vuejs | core | 1,894,722,324 | 10,129 | chanmanthau | 
you can find @dataview in node_modules, and change "module": "./es/index.js" to "module": "./es/index.mjs". | 2024-01-17T00:15:43 | 2024-01-17T00:15:43 | {} | NONE |
vuejs | core | 1,898,194,099 | 6,314 | yyx990803 | Closing as stale | 2024-01-18T10:19:59 | 2024-01-18T10:19:59 | {} | MEMBER |
vuejs | core | 1,899,536,975 | 9,603 | yangxiuxiu1115 | Looks like it was closed by me by mistake.
re-open | 2024-01-19T02:20:50 | 2024-01-19T02:20:50 | {
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 1,902,767,162 | 10,167 | pikax | As a workaround you can cast `props: ["msg", "list"] as any,` that will prevent the `props` type being inferred by the argument.
The bug is caused because the component is trying to resolve the props based on the function argument + `props` 2nd parameter. | 2024-01-21T21:21:09 | 2024-01-21T21:21:09 | {} | MEMBER |
vuejs | core | 1,894,504,277 | 10,098 | WenisOK | > > 在nuxt3.91没有修复
>
> this is not related to this issue, please discuss it in relevant repo
已经被修复了，目前看着3.4.14，没有任何问题 | 2024-01-16T21:00:10 | 2024-01-16T21:00:10 | {} | NONE |
vuejs | core | 1,897,688,813 | 10,146 | PengBoUESTC | so fast +_+ | 2024-01-18T02:53:03 | 2024-01-18T02:53:03 | {} | CONTRIBUTOR |
vuejs | core | 1,897,716,914 | 10,141 | yyx990803 | This fix is incorrect because `value` isn't actually rendered as an attribute during SSR.
The real cause is when there is no `value` attribute, `optionElement.value` will return its inner text instead.
See d16a2138a | 2024-01-18T03:20:46 | 2024-01-18T03:20:46 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,898,214,765 | 10,145 | mvgn | The bug only applies to the second blank line. You need Safari 17 on macOS (tested on Safari 17.2.1). On iOS, the bug is paste only — typing works. Tested on multiple devices, with normal and private browsing. Also, the typing bug on macOS seems to be dependent on the characters being typed. No standard ASCII character... | 2024-01-18T10:33:02 | 2024-01-18T10:33:02 | {} | NONE |
vuejs | core | 1,898,342,699 | 10,145 | yyx990803 | This seems to really be a Safari bug / regression then, since Vue really isn't doing anything special for plain textarea elements, and it's working on older versions of Safari and all other browsers. | 2024-01-18T11:57:43 | 2024-01-18T11:57:43 | {} | MEMBER |
vuejs | core | 1,899,972,839 | 9,998 | pikax | Thanks for this, can you add a test for this please? | 2024-01-19T08:31:46 | 2024-01-19T08:31:46 | {} | MEMBER |
vuejs | core | 1,900,660,760 | 10,152 | yangxiuxiu1115 | 能提供一个简单的复现仓库吗，根据你的描述我没有复现对应问题 | 2024-01-19T15:47:45 | 2024-01-19T15:47:45 | {} | CONTRIBUTOR |
vuejs | core | 1,902,522,445 | 10,168 | Doctor-wu | In your first reproduction, it merely do the same thing as [this](https://play.vuejs.org/#eNqVVFGPlDAQ/iuVmLCbABtzb8huTi+n0eid8Ywv4gPC7G73SsFSuL0Q/rszLXSJ2Wz0gYTOfO180++b9t6buo66FrzYS5pc8VqzBnRbb1LJy7pSmt3suSjYVlUl86OVWdEG3wF6tgN9l5UQ0Fb6YYPDP+hKgf96Bs6rsm41FA5kD0tlXslGM0n71w616FPJqEDMFku23ky1FsuAElgQExKeKGbyIwUXS+WAX7... | 2024-01-21T05:46:56 | 2024-01-21T05:53:30 | {} | MEMBER |
vuejs | core | 1,893,291,197 | 10,129 | chanmanthau | I can't install DataV dependency on stackblitz. So I create a github repository: https://github.com/chanmanthau/myissuedemo you can use that to see the problem. | 2024-01-16T08:43:23 | 2024-01-16T08:43:23 | {
"eyes": 1
} | NONE |
vuejs | core | 1,898,871,760 | 10,098 | ferferga | @djixadin I was also experiencing the same issue consistently in my app, so I downgraded to 3.4.8 while had some time to investigate.
I was not able to reproduce it in the playground with the same structure of my App (Suspense + Transition), but I could trace it down to this exact commit: https://github.com/vuejs/c... | 2024-01-18T17:01:43 | 2024-01-18T17:12:31 | {} | CONTRIBUTOR |
vuejs | core | 1,899,768,109 | 10,121 | ocavue | Thanks! I can confirm that Vue 3.4.15 fixes the issue. | 2024-01-19T04:53:45 | 2024-01-19T04:53:45 | {} | NONE |
vuejs | core | 1,899,947,844 | 10,098 | djixadin | Yes i am, it is on by default. I wasn't able to reproduce it at the time but as stated here by the fine gentleman is that the problem is in promises not resolving before navigating https://github.com/nuxt/nuxt/issues/25214#issuecomment-1898592511 | 2024-01-19T08:12:17 | 2024-01-19T08:12:17 | {} | NONE |
vuejs | core | 1,870,945,705 | 9,502 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | --------------------- | -------------------- | ---------------------- |
| runtime-dom.global.prod.js | 91.2 kB (**+995 B**) | 34.9 kB (**+534 B**) | 31.3 kB... | 2023-12-28T08:42:18 | 2024-01-19T13:31:50 | {} | NONE |
vuejs | core | 1,901,081,290 | 10,156 | felixxxxxs | +1 Bug is still present in Vue 3.4.15
This bug also showed up in my Nuxt project after updating dependencies (Nuxt to v3.9.x, which updated Vue to v3.4.x).
Pinning Vue to v3.3.13 resolved the issue. | 2024-01-19T20:39:53 | 2024-01-19T20:39:53 | {
"+1": 1
} | NONE |
vuejs | core | 1,902,574,794 | 10,168 | LinusBorg | * `getName()` returns a non-reactive object...
* ...whose properties are mutated in the child via the inputs' `v-model`.
* also, the `model` ref's value in the child is never updated (as it's always containing the same, nonreactive object)
* and thus, the `setName` in the parent is never being called, either.
Th... | 2024-01-21T09:58:16 | 2024-01-21T09:58:16 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,894,475,348 | 9,556 | pikax | > Will this help resolve question I asked? [radix-vue/shadcn-vue#277](https://github.com/radix-vue/shadcn-vue/issues/277)
@jd-solanki no, the issue you linked is related with the vue compiler being able to infer props like that, bear in mind the compiler must know all the available props ahead of time ,to be able to... | 2024-01-16T20:37:34 | 2024-01-16T20:37:34 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,895,830,546 | 10,098 | Dream403 |
> 当有多个布局时仍然没有修复。恢复到 3.4.8 可以修复该问题，但在 3.4.9 上不起作用
Thanks for this answer, it solved my problem
| 2024-01-17T13:37:14 | 2024-01-17T13:37:14 | {
"+1": 3
} | NONE |
vuejs | core | 1,897,213,300 | 10,142 | modelair | hello. first of all for future: don't provide array index as a :key. this is a bad practice.
your example model array with refs does not work correctly. see [here](https://play.vuejs.org/#eNrlU0Fu2zAQ/MqCKGAbdawGvrlygbTNoT20RZtbmIMqrxwmFCmQlOxC0F/6lr6sQypKfWjygeggrXaHw93hsBcXTbPqWhYbkfvSqSaQ59A2pAuz30oRvBTvpFF1Y12g... | 2024-01-17T22:40:06 | 2024-01-17T22:40:30 | {} | NONE |
vuejs | core | 1,898,333,865 | 10,141 | zh-lx | > Are you sure about this? The warning from the example in #10140 no longer occurs when using the most recent commit.
Ok, it does looks ok in your demo. | 2024-01-18T11:51:25 | 2024-01-18T11:51:25 | {} | CONTRIBUTOR |
vuejs | core | 1,900,930,017 | 10,161 | Doctor-wu | Will add the corresponding test case later, and I think we need an ecosystem ci check. | 2024-01-19T18:47:33 | 2024-01-19T18:48:15 | {} | MEMBER |
vuejs | core | 1,901,268,074 | 10,156 | bayramorhan | > +1 Bug is still present in Vue 3.4.15 This bug also showed up in my Nuxt project after updating dependencies (Nuxt to v3.9.x, which updated Vue to v3.4.x). Pinning Vue to v3.3.13 resolved the issue.
By the way I realised thta we dont need to downgrade all the way down to 3.3.x. Vue 3.4.2 is also works fine. This ... | 2024-01-19T23:03:30 | 2024-01-19T23:32:19 | {} | NONE |
vuejs | core | 1,900,396,974 | 10,156 | typed-sigterm | +1 also appeared in my Nuxt project when use `navigateTo` 3 times in one tick. | 2024-01-19T13:06:02 | 2024-01-20T04:26:56 | {
"+1": 1
} | NONE |
vuejs | core | 1,902,519,532 | 10,168 | Doctor-wu | 
At your first reproduction, you are not supposed to add `:` before `v-model` | 2024-01-21T05:38:01 | 2024-01-21T05:38:01 | {} | MEMBER |
vuejs | core | 1,893,924,092 | 10,129 | Doctor-wu | <img width="950" alt="CleanShot 2024-01-16 at 23 00 05@2x" src="https://github.com/vuejs/core/assets/44631608/76c20c48-069b-44ee-b9eb-4c9c3e224e29">
Some errors occurred, I executed `npm install && npm run dev` | 2024-01-16T15:01:13 | 2024-01-16T15:01:13 | {} | MEMBER |
vuejs | core | 1,896,210,719 | 10,141 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.8 kB | 34.2 kB | 30.8 kB |
| vue.global.prod.js | 147 kB | 53.5 kB | 47.8 kB |
### Usages
| Name | Size |... | 2024-01-17T16:52:36 | 2024-01-17T16:52:36 | {} | NONE |
vuejs | core | 1,897,734,374 | 10,142 | yyx990803 | It doesn't look like the issue has anything specific with `v-model`, it's just that `$t()` is slow?
Calling functions inside the template *will* cause it to be called on every update. This can be improved in finer-grained rendering models like the upcoming Vapor Mode. But even in Vapor Mode or solidjs-like implement... | 2024-01-18T03:40:22 | 2024-01-18T03:40:22 | {} | MEMBER |
vuejs | core | 1,899,415,712 | 9,603 | pgalhardo | Hi! The proposed solution appears to be correct. Why was it closed? `defineModel` has been promoted to stable but the issue persists. | 2024-01-19T00:08:56 | 2024-01-19T00:08:56 | {} | NONE |
vuejs | core | 1,900,260,410 | 9,247 | daaanny90 | There is an idea when this will be merged? | 2024-01-19T11:42:09 | 2024-01-19T11:42:09 | {} | NONE |
vuejs | core | 1,901,935,406 | 10,157 | yangxiuxiu1115 | Add new [playground](https://play.vuejs.org/#eNp9Urtu2zAU/ZULLnYARx6yGXLQNsjQDm3Rx8ZFoa5txhRJkJTiwPDWJUCnTkWBbgW6ZcgHJF+T11/kkooUIwgCCKB4zzmX5x5yzd5amzU1sgnLvXDSBvAYarvPtayscQHW4HA2AqO/27IIWMIGZs5UMCDVgGuuhdGeVAtzAtPIHc4K5XGnB8KpwkeEil15UehS4YGSYkkgDHdgug9rrqEVZE2h6ihLJYBSequK0wkMpFZS4+6RMmJJ5wNsuKaP697hcLsZ2ep7BVcjkcl... | 2024-01-20T08:21:57 | 2024-01-20T08:21:57 | {} | CONTRIBUTOR |
vuejs | core | 1,902,781,911 | 10,167 | juliusmarminge | Ok so that fixes that for now, thanks.
Now if I may borrow your brain for a bit I'm struggling with getting the type narrowed correctly when using the defineComponent. What we want is for the `config.endpoint` to bind a generic and then the rest of the props be inferred based on that.
This works for our React and... | 2024-01-21T22:06:56 | 2024-01-21T22:08:50 | {} | NONE |
vuejs | core | 2,059,561,692 | 10,719 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 5f3c04dbd87c8967b1d09fd1f2a944abba157fc3 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-04-16T17:11:26 | 2024-04-16T17:11:26 | {} | NONE |
vuejs | core | 2,059,751,229 | 8,929 | matthew-dean | Please be aware: when this was released in 3.3.9 (? or 3.3.10?) this caused major breaking changes in our builds.
These selectors:
```css
:is(.button) {}
.button:where(.primary) {}
```
...were rendered as
```css
[data-v-dc180684]:is(.button) {} /* specificity (0,2,0) */
.button[data-v-dc180684]:where(.primar... | 2024-04-16T19:04:44 | 2024-04-16T19:04:44 | {} | NONE |
vuejs | core | 2,060,425,445 | 10,486 | skirtles-code | Does this replace #8507? | 2024-04-17T05:47:54 | 2024-04-17T05:47:54 | {} | CONTRIBUTOR |
vuejs | core | 2,060,523,340 | 3,399 | pikax | /ecosystem-ci run | 2024-04-17T07:02:56 | 2024-04-17T07:02:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,062,108,065 | 6,865 | skirtles-code | I don't think this really fixes the original issue.
The original reproduction needed a `v-if` to hit the relevant code path. Using `v-if="true"` was just the simplest way to achieve that. Adding special handling for `v-if="true"` doesn't fix the underlying problem, it just hides it in that specific example.
The m... | 2024-04-17T19:56:50 | 2024-04-17T19:56:50 | {} | CONTRIBUTOR |
vuejs | core | 1,714,920,161 | 9,190 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48 kB |
### Usages
| Name | Size |... | 2023-09-12T03:50:17 | 2024-04-16T03:41:42 | {} | NONE |
vuejs | core | 2,058,310,033 | 10,709 | haoqunjiang | Seems related to https://github.com/vuejs/core/commit/6af733d68eb400a3d2c5ef5f465fff32b72a324e | 2024-04-16T06:16:21 | 2024-04-16T06:16:21 | {} | MEMBER |
vuejs | core | 2,058,954,571 | 10,711 | LinusBorg | > Since you're creating a new object `{ deep: true }` isn't necessary, right?
If all relevant changes are top-level only, then yes, you don't need it anymore. | 2024-04-16T12:18:39 | 2024-04-16T12:18:39 | {} | MEMBER |
vuejs | core | 2,060,370,084 | 10,193 | skirtles-code | I think this may be a duplicate of #8304. | 2024-04-17T05:16:55 | 2024-04-17T05:16:55 | {} | CONTRIBUTOR |
vuejs | core | 2,060,559,149 | 10,720 | Doctor-wu | 我只是和你解释一下为什么没有响应式, 没有响应式就是现在预期的表现, 如果有提案的话可以去 rfc 的仓库提交, 因为一般 issue 是用来上报不符合 (框架) 预期的问题的。 | 2024-04-17T07:23:47 | 2024-04-17T07:23:47 | {} | MEMBER |
vuejs | core | 2,056,604,160 | 10,636 | yyx990803 | Thanks for the PR, but in compat mode the options need to be per-component and cannot be shared via a cache. There was another bug that caused the compatConfig check for private APIs to always be false, short circuiting this logic during tests as well, so I had to fix them together in https://github.com/vuejs/core/comm... | 2024-04-15T11:29:59 | 2024-04-15T11:29:59 | {} | MEMBER |
vuejs | core | 2,058,591,427 | 10,711 | LinusBorg | Your input it mutating a property of the object that was provided from App.vue. It's still the same object, you only change a property.
That's why old and new value are the same. You can clone the object in the watch's getter to get a before/after snapshot:
```js
watch(
() => ({ ...model.value}),
(newValue... | 2024-04-16T08:59:57 | 2024-04-16T08:59:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,058,946,630 | 10,710 | haoqunjiang | > scoped css `.hehe > *` output `.hehe[data-v-xxx] > *` instead of `.hehe > *[data-v-xxx]`
I think this is expected. What use case does this change break? | 2024-04-16T12:14:16 | 2024-04-16T12:14:16 | {} | MEMBER |
vuejs | core | 2,058,967,672 | 10,710 | haoqunjiang | > Also all the `:class="{ active: isActive }"` type bindings stopped working.
Do you have a runnable reproduction? I can't reproduce this issue https://play.vuejs.org/#eNp9UkFOwzAQ/IrxpSCVRC2cQlqpoErAARAgcbGE0nSbuji2ZTuhVZS/s3aatgfU2+7O7Hpm5IbOtI7qCmhCU5sbrh2x4Co9ZZKXWhlHGmJgRVqyMqokA6QOmGQyV9I6UtqCTDx+OXgEIRT5UkYsL... | 2024-04-16T12:25:40 | 2024-04-16T12:25:40 | {} | MEMBER |
vuejs | core | 2,059,010,139 | 10,710 | haoqunjiang | Caused by https://github.com/vuejs/core/commit/ca84316bfb3410efe21333670a6ad5cd21857396 | 2024-04-16T12:46:59 | 2024-04-16T12:46:59 | {} | MEMBER |
vuejs | core | 2,060,518,526 | 10,720 | Doctor-wu | 
因为在你调用 defineExpose 的时候这个 ref 的值还没有被附上 | 2024-04-17T07:00:00 | 2024-04-17T07:00:00 | {} | MEMBER |
vuejs | core | 2,060,584,814 | 10,720 | Doctor-wu | 文档这里用 ref 是和你说你 expose 出去之后也是具有响应式的, defineExpose 这里的实参是个普通的对象呀 | 2024-04-17T07:37:36 | 2024-04-17T07:37:36 | {} | MEMBER |
vuejs | core | 2,056,811,284 | 10,603 | 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 | 48 kB |
### Usages
| Name | Size | Gzi... | 2024-04-15T13:06:35 | 2024-04-15T13:07:06 | {} | NONE |
vuejs | core | 2,057,014,409 | 10,510 | yyx990803 | Closing since this has been fixed in the related library. | 2024-04-15T14:35:03 | 2024-04-15T14:35:03 | {
"rocket": 1
} | MEMBER |
vuejs | core | 2,057,117,775 | 10,696 | radqut | So why do ref handling work correctly in `v-bind` without using `v-for`? It's a little confusing. It looks like ref handling shouldn't work in "v-bind" at all, doesn't it? | 2024-04-15T15:20:13 | 2024-04-15T15:20:13 | {} | NONE |
vuejs | core | 2,058,154,904 | 8,576 | TuringJest | > FYI, the return type of `defineProps` does take this into account:
>
> ```ts
> interface Props {
> foo?: boolean
> }
> const p = defineProps<Props>()
> // ^ { foo: boolean }
> p.foo
> // ^ boolean
> ```
>
> The interface declares `foo` as being optional, but it is **not** the type of the resolved ... | 2024-04-16T03:15:13 | 2024-04-16T03:17:53 | {} | NONE |
vuejs | core | 2,058,527,083 | 8,988 | Alfred-Skyblue | > The previous version also had a change involving `NOOP`. Has that intentionally been removed?
https://github.com/vuejs/core/pull/8988?notification_referrer_id=NT_kwDOA1EGrbM3NDA0MjMzMzQwOjU1NjQxNzcz#discussion_r1411132332 | 2024-04-16T08:26:24 | 2024-04-16T08:26:24 | {} | MEMBER |
vuejs | core | 2,058,747,705 | 10,713 | quiteeasy | fix #10709 | 2024-04-16T10:21:09 | 2024-04-16T10:21:09 | {} | CONTRIBUTOR |
vuejs | core | 2,059,333,146 | 10,713 | quiteeasy | done in https://github.com/vuejs/core/commit/6df53d85a207986128159d88565e6e7045db2add | 2024-04-16T15:12:24 | 2024-04-16T15:12:24 | {} | CONTRIBUTOR |
vuejs | core | 2,062,882,801 | 9,453 | skirtles-code | The PR title currently indicates that this is a `perf` change. I wonder whether it'd be more accurate to describe it as a `refactor`?
I suspect the performance improvement is negligible at best, so it might be misleading having it listed as a performance improvement in the changelog. | 2024-04-18T02:31:28 | 2024-04-18T02:31:28 | {} | CONTRIBUTOR |
vuejs | core | 2,056,492,706 | 10,704 | LinusBorg | Yes, thats expected. Model names need to be statically defined to be available at compile time, just like normal props | 2024-04-15T10:31:13 | 2024-04-15T10:31:29 | {} | MEMBER |
vuejs | core | 2,056,664,756 | 10,704 | FreeLiC | @LinusBorg But v-model can bind calling methods expression. Is this a problem? | 2024-04-15T12:01:32 | 2024-04-15T12:01:32 | {} | NONE |
vuejs | core | 1,993,723,151 | 10,506 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.6 kB (**+23 B**) | 34.5 kB (**+16 B**) | 31.1 kB (**+27 B**) |
... | 2024-03-13T07:28:17 | 2024-04-15T13:57:28 | {} | NONE |
vuejs | core | 2,056,950,402 | 10,468 | yyx990803 | Looks like you need to update the lockfile to get CI passing. | 2024-04-15T14:07:05 | 2024-04-15T14:07:05 | {} | MEMBER |
vuejs | core | 1,981,325,061 | 10,468 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 332293ce9bafb52d5623f7dee7f1d97e906a5511 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2024-03-06T16:48:08 | 2024-04-15T14:31:11 | {} | NONE |
vuejs | core | 2,058,056,141 | 10,066 | edison1105 | /ecosystem-ci run
| 2024-04-16T01:04:23 | 2024-04-16T01:04:23 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,058,056,320 | 9,213 | edison1105 | /ecosystem-ci run
| 2024-04-16T01:04:39 | 2024-04-16T01:04:39 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,059,094,771 | 10,710 | yyx990803 | Please do not report unrelated issues under an existing one that already has a reproduction. **If your problem is different from OP's, open a separate issue.** | 2024-04-16T13:27:45 | 2024-04-16T13:27:45 | {} | MEMBER |
vuejs | core | 2,054,384,304 | 10,698 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-04-15T02:18:40 | 2024-04-16T14:58:59 | {} | NONE |
vuejs | core | 2,060,590,395 | 10,720 | guaijie | > 那不就刚好和你说了不支持响应式吗
>
> > > 文档这里用 ref 是和你说你 expose 出去之后也是具有响应式的, defineExpose 这里的实参是个普通的对象呀
> >
> >
> > 你可以去看，直接暴露一个 selectRef 是会报警告的。只能传一个 plain object ，我只是跟进它的警告做的修改
我要看的是文档啊，不是它的警告，所以我才提出来的，我明确说明了，一切都表现的很好。唯独它不行。 | 2024-04-17T07:40:47 | 2024-04-17T07:41:18 | {} | CONTRIBUTOR |
vuejs | core | 2,056,666,960 | 10,704 | LinusBorg | I dont see how that should be a problem | 2024-04-15T12:02:45 | 2024-04-15T12:02:45 | {} | MEMBER |
vuejs | core | 2,058,722,820 | 10,710 | Payn | Also all the `:class="{ active: isActive }"` type bindings stopped working. | 2024-04-16T10:07:43 | 2024-04-16T10:07:43 | {} | NONE |
vuejs | core | 2,059,505,799 | 10,717 | 7by24 | > browser apis are not reactive. only reactive data (`reactive()`/`ref()`) is reactive, and only that data can trigger a watch.
well, the weired part is the same codes works great in my other project. that's why i don't understand why this happened | 2024-04-16T16:37:05 | 2024-04-16T16:37:05 | {} | NONE |
vuejs | core | 2,060,440,077 | 10,486 | NoelDeMartin | Lol, it seems like I forgot that I had already opened this PR :sweat_smile:. Thanks for the heads-up @skirtles-code, I'm closing this as a duplicate then.
I'm pinging one of the maintainers @sodatea to take a look, it seems like a fairly safe fix. | 2024-04-17T06:01:06 | 2024-04-17T06:01:06 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,054,384,838 | 10,699 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-04-15T02:18:48 | 2024-04-17T14:00:56 | {} | NONE |
vuejs | core | 2,057,333,412 | 10,696 | quiteeasy | The current behavior works because the ref is resolved at runtime from the object. However, the identifier that the ref is inside a v-for is set at compile time. Due to this, the ref is often set to a random element in the list, typically the last one.
We could set the identifier that a ref is inside a v-for without... | 2024-04-15T16:41:54 | 2024-04-15T16:41:54 | {} | CONTRIBUTOR |
vuejs | core | 2,054,832,173 | 10,703 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48 kB |
### Usages
| Name | Size |... | 2024-04-15T03:53:52 | 2024-04-15T21:43:49 | {} | NONE |
vuejs | core | 2,059,500,033 | 10,717 | LinusBorg | browser apis are not reactive. only reactive data (`reactive()`/`ref()`) is reactive, and only that data can trigger a watch. | 2024-04-16T16:33:53 | 2024-04-16T16:34:28 | {} | MEMBER |
vuejs | core | 2,059,517,528 | 10,715 | LinusBorg | that TS Error is correct, though. `Event` does not fullfill the requirements of `UIEvent`. So that is a bugfix, not a regression. | 2024-04-16T16:44:10 | 2024-04-16T16:45:29 | {} | MEMBER |
vuejs | core | 2,059,581,540 | 10,715 | scottbedard | Excellent, thank you for the fast response! | 2024-04-16T17:24:12 | 2024-04-16T17:24:12 | {} | CONTRIBUTOR |
vuejs | core | 2,056,814,287 | 10,578 | yyx990803 | This is expected behavior - modifiers modify user input, they do not modify values set from JavaScript because you have full control over the values when setting them in JavaScript. | 2024-04-15T13:08:01 | 2024-04-15T13:08:01 | {} | MEMBER |
vuejs | core | 1,981,325,849 | 10,468 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 332293ce9bafb52d5623f7dee7f1d97e906a5511 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-03-06T16:48:23 | 2024-04-15T14:31:25 | {} | NONE |
vuejs | core | 2,058,002,416 | 8,947 | skirtles-code | I believe this section of the code was removed as part of #5912. | 2024-04-15T23:55:45 | 2024-04-15T23:55:45 | {} | CONTRIBUTOR |
vuejs | core | 2,058,063,724 | 9,213 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8698321799)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8683642139) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-04-16T01:14:56 | 2024-04-16T01:14:56 | {} | CONTRIBUTOR |
vuejs | core | 2,058,346,318 | 10,594 | davidmatter | Same as https://github.com/vuejs/core/pull/9336 right? Seems like this one was first | 2024-04-16T06:41:23 | 2024-04-16T06:41:23 | {} | CONTRIBUTOR |
vuejs | core | 2,059,089,980 | 10,710 | haoqunjiang | > I see you already found the cause, do you still want a reproducer from me?
I found the cause for OP's issue, but I'm not sure what you meant by "all the `:class="{ active: isActive }"` type bindings stopped working." It may be a different issue, so please provide a reproduction. | 2024-04-16T13:25:31 | 2024-04-16T13:25:31 | {} | MEMBER |
vuejs | core | 2,059,522,340 | 10,717 | LinusBorg | I doubt that it works like you think it works in your other project. | 2024-04-16T16:47:03 | 2024-04-16T16:47:03 | {} | MEMBER |
vuejs | core | 2,059,563,337 | 10,719 | yangxiuxiu1115 | Still need to add test cases, but it's stumping me | 2024-04-16T17:12:28 | 2024-04-16T17:12:28 | {} | CONTRIBUTOR |
vuejs | core | 2,059,760,372 | 8,929 | matthew-dean | Also, I don't understand the rationale here for the change. Why should the component not be scoped to the main selector? By moving component scoping (the attribute selector) to a `:where()` you effectively lower the specificity below anything not using `:where()`. That breaks the entire idea in Vue of scoping the CSS t... | 2024-04-16T19:10:45 | 2024-04-16T19:12:02 | {} | NONE |
vuejs | core | 2,060,308,625 | 8,576 | guaijie | > FYI, the return type of `defineProps` does take this into account:
>
> ```ts
> interface Props {
> foo?: boolean
> }
> const p = defineProps<Props>()
> // ^ { foo: boolean }
> p.foo
> // ^ boolean
> ```
>
> The interface declares `foo` as being optional, but it is **not** the type of the resolved ... | 2024-04-17T04:10:39 | 2024-04-17T04:11:39 | {} | CONTRIBUTOR |
vuejs | core | 2,060,588,005 | 10,720 | guaijie | > 文档这里用 ref 是和你说你 expose 出去之后也是具有响应式的, defineExpose 这里的实参是个普通的对象呀
你可以去看，直接暴露一个 selectRef 是会报警告的。只能传一个 plain object ，我只是跟进它的警告做的修改，而且同样是不能用的。所以我前面说明了 provide/inject
| 2024-04-17T07:39:22 | 2024-04-17T07:40:04 | {} | CONTRIBUTOR |
vuejs | core | 2,057,011,813 | 10,482 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 90.6 kB (**+10 B**) | 34.5 kB (**+2 B**) | 31.1 kB (**+18 B**) |
| v... | 2024-04-15T14:33:58 | 2024-04-15T14:33:58 | {} | NONE |
vuejs | core | 2,057,064,343 | 10,696 | quiteeasy | The compiler has some optimizations related to refs handling, so moving that logic to runtime to support dynamic ref bindings would be a bad idea. I agree with @LinusBorg that documenting the current behavior would be the better approach. | 2024-04-15T14:56:57 | 2024-04-15T14:56:57 | {} | CONTRIBUTOR |
vuejs | core | 1,718,765,390 | 9,213 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ----------------- |
| runtime-dom.global.prod.js | 90.7 kB (**+66 B**) | 34.5 kB (**+25 B**) | 31.1 kB |
| vue.... | 2023-09-14T04:58:50 | 2024-04-15T15:19:24 | {} | NONE |
vuejs | core | 2,059,814,983 | 9,416 | skirtles-code | I believe the runtime behaviour is correct, but there does seem to be a problem with the types.
To recap:
1. A reactive array does not automatically unwrap any refs it contains.
2. `watch` unwraps a ref source when passing values to the callback.
3. Passing a reactive object to `watch` will create a deep watche... | 2024-04-16T19:49:14 | 2024-04-16T19:49:14 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,060,051,226 | 8,576 | matthew-dean | @TuringJest
> The issue is that there is a wrong assumption at the bottom. Yes, booleans should be true or false BUT assuming you want booleans here is not correct. What is needed in the context of templates, etc. are optional booleans.
100% and I'm so glad you said this. What you're defining with your TypeScrip... | 2024-04-16T23:08:30 | 2024-04-16T23:38:32 | {} | NONE |
vuejs | core | 2,060,288,622 | 8,929 | haoqunjiang | In the latest v3.4.23, the specificity issue is fixed:
It's compiled as:
```
:is(.button[data-v-7ba5bd90]) {} /* specificity (0,2,0) */
.button[data-v-7ba5bd90]:where(.primary) {} /* specificity (0,2,0), but comes later, wins */
```
https://play.vuejs.org/#eNp9Uk1PwzAM/Ssmlw2JdQw4lW4SoEnAARAgccmldN6WkSZR4u6Dq... | 2024-04-17T03:42:51 | 2024-04-17T03:43:32 | {} | MEMBER |
vuejs | core | 2,060,553,157 | 10,720 | guaijie | > 现在还不支持这样的行为, 文档也没有说可以吧, 因为本质上 defineExpose 只是被编译成了 __expose。 ![CleanShot 2024-04-17 at 15 11 06@2x](https://private-user-images.githubusercontent.com/44631608/323116686-57436c81-4279-4148-b91c-22a71fcf57ea.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmN... | 2024-04-17T07:20:20 | 2024-04-17T07:24:15 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.