owner stringclasses 14
values | repo stringclasses 14
values | id int64 116k 4.61B | issue_number int32 1 181k | author stringlengths 1 39 | body stringlengths 1 262k | created_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:16:18 | updated_at timestamp[us]date 2000-06-06 02:40:44 2026-06-02 20:22:56 | reactions unknown | author_association stringclasses 5
values |
|---|---|---|---|---|---|---|---|---|---|
vuejs | core | 2,180,258,871 | 11,183 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9595156140)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9576400976) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-06-20T09:43:31 | 2024-06-20T09:43:31 | {} | CONTRIBUTOR |
vuejs | core | 2,182,837,370 | 11,183 | Jallasia | Thx indeed, we cannot update to current version because of this issue, nice to see that it will be fixed very soon thx to you :-) | 2024-06-21T14:13:25 | 2024-06-21T14:13:25 | {
"+1": 1
} | NONE |
vuejs | core | 2,167,728,318 | 11,135 | webfansplz | /ecosystem-ci run | 2024-06-14T10:26:30 | 2024-06-14T10:26:30 | {
"+1": 1,
"heart": 1
} | MEMBER |
vuejs | core | 2,167,785,321 | 11,135 | Doctor-wu | This PR's behaviors in test case are aligned with v3.5.0-alpha.2 as well | 2024-06-14T11:02:33 | 2024-06-14T11:06:12 | {} | MEMBER |
vuejs | core | 2,171,762,797 | 11,143 | alexzhang1030 | Looks like `useModel()` does not process the object state properly if there is no `v-model` in the parent component.
```ts
test('useModel() w/ object state', async () => {
let array: any
const update = () => {
if (!array.value) {
array.value = [1]
} else {
array.value.push(2)
}
... | 2024-06-16T16:28:08 | 2024-06-16T16:37:22 | {} | MEMBER |
vuejs | core | 2,176,400,796 | 11,170 | Doctor-wu | /ecosystem-ci run | 2024-06-18T15:35:13 | 2024-06-18T15:35:13 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,179,787,346 | 11,177 | zdm | I am using ExtJS web components:
```
<ext-grid :store="store" ... />
```
where `store` is instance of Store class. | 2024-06-20T04:35:09 | 2024-06-20T04:35:09 | {} | NONE |
vuejs | core | 2,179,781,694 | 11,177 | zdm | yes, give me 2 hours, don't close issue pls | 2024-06-20T04:27:32 | 2024-06-20T04:27:32 | {} | NONE |
vuejs | core | 2,179,871,844 | 8,338 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9592269798)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9576400976) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-06-20T05:52:45 | 2024-06-20T05:52:45 | {} | CONTRIBUTOR |
vuejs | core | 2,179,987,311 | 11,177 | zdm | It works when I replace `String(value)` with just `value` in your package source code.
The error is related exactly to this change and attrs are not converted to the strings by default.
ExtJS process attrs after vue, so the problem should be fixed in vue. | 2024-06-20T07:19:18 | 2024-06-20T07:19:18 | {} | NONE |
vuejs | core | 2,176,354,634 | 11,169 | wanghanzhen | It works fine with both v3.5.0-alpha.2 and v3.4.14 | 2024-06-18T15:14:02 | 2024-06-18T15:14:02 | {} | NONE |
vuejs | core | 2,178,587,353 | 11,071 | thomasaull | Thanks @jh-leong! The only thing necessary to make it work, seems to be to update the type on Props to include the default type I want to use, so this works:
```typescript
interface Props {
type?: TypeBase | Type
}
```
as well as this
```typescript
interface Props {
type?: 'text' | Type
}
```
[Examp... | 2024-06-19T12:31:16 | 2024-06-19T12:31:16 | {
"+1": 1
} | NONE |
vuejs | core | 2,167,257,722 | 11,128 | virtueDe | @jh-leong is that I shouldn't use it that way? Is it my usage that is wrong? I doubt myself | 2024-06-14T05:48:56 | 2024-06-14T05:48:56 | {} | NONE |
vuejs | core | 2,167,722,124 | 11,135 | Doctor-wu | @johnsoncodehk cc this, and we need a ecosystem test as well | 2024-06-14T10:22:39 | 2024-06-14T10:22:39 | {} | MEMBER |
vuejs | core | 2,168,362,617 | 11,121 | wanghanzhen | @johnsoncodehk Thanks for your reply. I understand what you mean, but I think most developers will not deliberately write this logic.
Because of the flexibility of JS, it may happens in some relatively large projects like using `Object.assign` or making nested mutations carelessly. I think these `computed` cases ar... | 2024-06-14T16:25:24 | 2024-06-14T16:26:11 | {} | NONE |
vuejs | core | 2,175,892,597 | 11,071 | jh-leong | @thomasaull Based on your previous example, would this approach work for your needs without using generics?
```vue
interface Props {
type?: 'text' | 'date' | null
}
const props = withDefaults(defineProps<Props>(), {
type: 'text'
})
``` | 2024-06-18T11:39:26 | 2024-06-18T11:39:26 | {} | MEMBER |
vuejs | core | 2,176,416,024 | 11,170 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9568013513)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9542190098) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-06-18T15:42:08 | 2024-06-18T15:42:08 | {} | CONTRIBUTOR |
vuejs | core | 2,183,664,167 | 9,232 | edison1105 | > Any reason not to include test cases for the change to `hydration.ts`?
It seems that `jsdom's innerHTML` does not normalize `\r\n` into `\n`.
I did not figure out a way to test it. | 2024-06-22T01:30:07 | 2024-06-22T01:31:01 | {} | MEMBER |
vuejs | core | 2,167,411,954 | 11,133 | catcoon33 | I think this is as expected, and the correct usage is the part you commented out in your code. | 2024-06-14T07:31:33 | 2024-06-14T07:31:33 | {} | NONE |
vuejs | core | 2,175,863,183 | 11,167 | jh-leong | This behavior is expected and is a limitation of TypeScript. You can see an example in the [TS Playground](https://www.typescriptlang.org/play/?#code/MYewdgzgLgBAZiEMC8MA8AVGBTAHlbMAEwhgHIEQyYAfcogQwOroFdjs4BLMbI2mGFYAbYQD4AFAEoUYmAG8AsACgYMUJFgMAXApgBrXVgC+KPYfKVqpgPQ2cAJwcgHAQhVq7MDAE8ADtjkAESUQdRcpGAgWhAQXADmYAwARsK... | 2024-06-18T11:24:14 | 2024-06-18T11:24:14 | {} | MEMBER |
vuejs | core | 2,178,252,924 | 11,170 | wanghanzhen | Hold on, just found a `Maximum recursion error` in my project after adding `resetTracking`😨
At present, the minimum reproduction has not been found yet. | 2024-06-19T09:51:28 | 2024-06-19T09:51:40 | {} | NONE |
vuejs | core | 2,180,019,755 | 11,177 | LinusBorg | Okay, addendum: I think I can *guess* what the specific issue is:
the extJS behaviour relies on the fact that the browser would call `toString` on objects passed to ``setAttrtibute()`. Likely, this ExtJS store provides this method that would serialize the store into a string which the web component can re-convert in... | 2024-06-20T07:38:24 | 2024-06-20T07:49:50 | {} | MEMBER |
vuejs | core | 2,180,817,508 | 8,482 | rcomesan | I'm also getting the same error when trying to import an inferred zod type
```[plugin:vite:vue] [@vue/compiler-sfc] Unresolvable type reference or unsupported built-in utility type```
```typescript
import { z } from 'zod';
export const EmailVerificationViewPropsSchema = z.object({
initialStage: z.enum(['send... | 2024-06-20T14:14:04 | 2024-06-20T14:14:04 | {
"+1": 3
} | NONE |
vuejs | core | 2,167,212,073 | 11,130 | guaijie | > 我認為是預期的，因為你不沒有傳 `attrs` 而是傳 `{}`
>
> 你可以改用:
>
> https://vuejs.org/guide/components/attrs.html#fallthrough-attributes
>
> ```
> <template>
> <div><slot></slot></div>
> </template>
> ```
怎么会符合预期了，事件、style 和 class 都传递过去了
属性穿透的意思官方文档有明确说明。这跟预先传值有什么关系 | 2024-06-14T04:58:12 | 2024-06-14T04:59:46 | {} | CONTRIBUTOR |
vuejs | core | 2,167,244,130 | 11,130 | guaijie | > This behavior seems to be expected. Ref: [vuejs/rfcs#154](https://github.com/vuejs/rfcs/pull/154)
>
> > Functional components without a `props` declaration will have everything passed in as props. They will only have implicit fallthrough for `class`, `style`, and `v-on` listeners.
>
> ~By the way, I couldn't fi... | 2024-06-14T05:34:15 | 2024-06-14T05:34:15 | {} | CONTRIBUTOR |
vuejs | core | 2,169,890,953 | 11,143 | modos | @gkweb no it's not, the subject you mentioned is that when parent and child mounted, the default value in child doesn't apply to the parent, but if you change it in runtime, then parent value updated, check this out:
https://play.vuejs.org/#eNqFUk1PwzAM/StWLgMBKxKcoEPAxAEkPgQccympN8LSJMrHmFT1v+Ok26jENG6x37P9nOeW3Vg7Xk... | 2024-06-15T15:22:50 | 2024-06-15T15:22:50 | {} | NONE |
vuejs | core | 2,172,115,174 | 11,156 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 91.5 kB | 34.7 kB | 31.3 kB |
| vue.global.prod.js | 149 kB | 54 kB | 48.3 kB |
### Usages
| Name | Size |... | 2024-06-17T03:38:39 | 2024-06-17T03:38:39 | {} | NONE |
vuejs | core | 2,175,867,424 | 11,071 | thomasaull | Is there any other workaround than `// @ts-expect-error` or using runtime code to provide defaults (e.g. via `computed`) | 2024-06-18T11:26:48 | 2024-06-18T11:26:58 | {} | NONE |
vuejs | core | 2,177,987,363 | 11,078 | green-mike | Yes, I noticed that this issue only occurs in the SSR environment. The same code does not produce errors in the browser, so I consider it a bug. | 2024-06-19T07:44:22 | 2024-06-19T07:44:22 | {} | NONE |
vuejs | core | 2,183,569,763 | 10,193 | skirtles-code | I believe this problem has been fixed as of 3.4.28. | 2024-06-21T23:14:35 | 2024-06-21T23:14:35 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,168,144,280 | 11,133 | yyx990803 | This is expected behavior.
From the docs:
> Can also be used to create a ref for a property on a source reactive object.
The source object must be reactive. | 2024-06-14T14:15:27 | 2024-06-14T14:15:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,168,160,261 | 11,136 | yyx990803 | Invalid reproduction - this involves your build setup so a playground link is insufficient to debug the issue. Please provide an actual reproduction. | 2024-06-14T14:24:11 | 2024-06-14T14:24:11 | {} | MEMBER |
vuejs | core | 2,172,069,713 | 11,151 | alexzhang1030 | FYI: I only reproduce it on Chrome v126.0.6478.62, not sure a bug in Chrome. | 2024-06-17T02:43:25 | 2024-06-17T02:43:25 | {} | MEMBER |
vuejs | core | 2,172,545,664 | 6,933 | haoqunjiang | Already fixed in https://github.com/vuejs/core/pull/8052 | 2024-06-17T07:50:01 | 2024-06-17T07:50:01 | {} | MEMBER |
vuejs | core | 2,176,437,461 | 11,164 | jssullivan | If others hit this, you can apply this pnpm patch to `compatRender` in @vue/compat to address this crash.
https://github.com/jssullivan/vue-3-not-running-compiled-script-setup/commit/7dcda5b5f0b2db551cd86c848ed8558aae75f9f0
I can create an MR to add this, or create a new @vue/compat flag to add this. Looking at th... | 2024-06-18T15:52:34 | 2024-06-18T15:52:34 | {} | NONE |
vuejs | core | 2,180,001,100 | 11,177 | LinusBorg | I still don't understand what the nature of the problem *really is*. We already established that the value will be stringified either way. So apparently, the exJS component would re-convert the string into a store instance?
So do we have an issue where our implementation does stringify that store object differently ... | 2024-06-20T07:27:20 | 2024-06-20T07:31:13 | {} | MEMBER |
vuejs | core | 2,180,931,195 | 11,125 | yangxiuxiu1115 | Yes, a lot of these optimizations exist within vue, and I think maybe DefineModel shouldn't be special | 2024-06-20T15:03:46 | 2024-06-20T15:03:46 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,097,074,379 | 10,813 | AtesComp | Same issues:
```
[Vue warn]: Unhandled error during execution of scheduler flush. This is likely a Vue internals bug. Please open an issue at https://github.com/vuejs/core .
at <BaseTransition onAfterEnter=fn<onAfterEnter> onAfterLeave=fn<onAfterLeave> appear=true ... >
at <Transition name="fade-transition... | 2024-05-06T23:08:25 | 2024-05-06T23:08:25 | {} | NONE |
vuejs | core | 2,097,273,526 | 10,873 | Flame-00 | 
| 2024-05-07T02:12:03 | 2024-05-07T02:12:03 | {} | NONE |
vuejs | core | 2,099,553,058 | 10,813 | edison1105 | @nongtan7898's reproduction can't reproduce that error.
@AtesComp
Please provide a minimal reproduction. | 2024-05-08T01:17:04 | 2024-05-08T01:17:04 | {} | MEMBER |
vuejs | core | 2,100,458,612 | 10,869 | jh-leong | > Is it possible to include test cases for this fix?
Yes, I have updated the tests to cover this fix. Thank you for your suggestion! | 2024-05-08T12:23:50 | 2024-05-08T12:23:50 | {} | MEMBER |
vuejs | core | 2,107,184,085 | 10,748 | tonliver | @edison1105 I've added some test cases. | 2024-05-13T10:16:00 | 2024-05-13T10:16:00 | {} | CONTRIBUTOR |
vuejs | core | 2,107,778,723 | 10,920 | jh-leong | Oops, I misunderstood. You can separate `keyof` from `Props` to avoid runtime errors and maintain type inference. See [playground](https://play.vuejs.org/#eNqNU22L2zAM/ivGX9KDWwrbYJClhW6Uvdxt7dqyUc7HyCVql15iB9vpGkr/+yS7Lym0474YW3okPZIfbfmgqsJ1DTzisUl1XllmwNYVKxK57AlujeB9IfOyUtqyj6qs2EKrkgVhlx4UGrwXUshUSWPZdP7tbjhnPTZty... | 2024-05-13T14:35:01 | 2024-05-13T14:35:01 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,108,214,066 | 10,935 | johnsoncodehk | This type is defined in Vue core in the following code: https://github.com/vuejs/core/blob/107e6143e716986269fc7c1d96733cb59dfadc53/packages/runtime-dom/src/components/Transition.ts#L18
@LinusBorg Could you transfer this issue? | 2024-05-13T15:50:51 | 2024-05-13T15:50:51 | {} | MEMBER |
vuejs | core | 2,109,174,476 | 9,572 | wjp980108 | This feature is very useful for me. awesome! | 2024-05-14T02:47:13 | 2024-05-14T02:47:13 | {} | NONE |
vuejs | core | 2,097,110,558 | 10,845 | yyx990803 | Closing as no follow up has been provided. Please open a new one if proper repro can be provided. | 2024-05-06T23:50:44 | 2024-05-06T23:50:44 | {} | MEMBER |
vuejs | core | 2,097,398,315 | 10,863 | littlezo | > Does this have any real impact on usage?
The this instance in the above figure is not a Vue instance but a class instance, and the execution of externally passed hooks depends on the context of the this instance | 2024-05-07T03:56:51 | 2024-05-07T03:56:51 | {} | NONE |
vuejs | core | 2,107,157,416 | 10,882 | neneodonkor | > > Very interesting. But I find it strange that folks actually use 'key' to bind to key. 🤔
>
> Yeah `v-for="key in keys"` would be quite rare and is served as simply a minimal reproduction. A more realistic example would be something where you already have to generate unique keys for a list of objects to iterate t... | 2024-05-13T10:02:32 | 2024-05-13T10:02:32 | {} | NONE |
vuejs | core | 2,096,964,539 | 10,864 | pcoterecollective | @LinusBorg I was able to use and adapt your solution to fit our needs.
Thanks for your valuable input.
Regards, | 2024-05-06T21:35:49 | 2024-05-06T23:00:24 | {} | NONE |
vuejs | core | 2,098,672,219 | 10,813 | AtesComp | The warnings and errors in https://github.com/vuejs/core/issues/10813#issuecomment-2097074379 are introduced in vue@3.4.24
While the example demonstrates the issue within Vuetify3 components, the Vue3 version packaged is the controlled change applied by ```npm update``` after modifying the projects ```package.json`... | 2024-05-07T15:14:24 | 2024-05-07T15:14:24 | {} | NONE |
vuejs | core | 2,098,897,636 | 10,862 | martynchamberlin | We are similarly experiencing this issue, albeit with `reactive()`, FWIW. And similarly, the Vue sandbox environment doesn't show the error, but it's there for us locally.
https://play.vuejs.org/#eNqdUk1v2zAM/SuELk2ATh6wnTw3wFb0sB22YutRF89mEnWyJEi068Hwfy8lo27Qr0NPifke+R6fOImv3suhR1GKirDzpibcKQtQNUdt2g+N67yzaAnKtqb6... | 2024-05-07T16:53:14 | 2024-05-07T16:53:14 | {} | NONE |
vuejs | core | 2,102,233,591 | 10,896 | 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.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-09T08:48:56 | 2024-05-09T08:48:56 | {} | NONE |
vuejs | core | 2,105,460,699 | 10,896 | vue-bot | 📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9040402747)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9027497483) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-c... | 2024-05-11T02:26:00 | 2024-05-11T02:38:39 | {} | CONTRIBUTOR |
vuejs | core | 2,105,954,099 | 10,813 | nongtan7898 | I'm using vite with vue (pinia or vuex) vue-router and datatable.net
This is my project
https://github.com/nongtan7898/vue-project
@edison1105 @AtesComp @jacekkarczmarczyk | 2024-05-11T16:54:55 | 2024-05-11T16:54:55 | {} | NONE |
vuejs | core | 2,106,213,202 | 10,919 | 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.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-12T11:23:37 | 2024-05-12T11:23:37 | {} | NONE |
vuejs | core | 2,106,546,831 | 10,923 | 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.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-13T02:59:58 | 2024-05-13T02:59:58 | {} | NONE |
vuejs | core | 2,108,012,335 | 10,925 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9065558693)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9057461042) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-05-13T15:30:39 | 2024-05-13T15:30:39 | {} | CONTRIBUTOR |
vuejs | core | 2,102,815,875 | 10,652 | ferferga | @edison1105 Sorry for pinging you again.
May we have this PR labeled as "ready to review" to attract a bit more of attention by potential reviewers now that we're starting with the v3.5.z cycle? The original issue has been open for 3 years and it's labeled as priority 4, so definitely this PR is worth it! | 2024-05-09T14:50:10 | 2024-05-09T14:50:10 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 2,103,885,600 | 10,900 | linzhe141 | scope css still doesn’t take effect
---
| 2024-05-10T05:20:50 | 2024-05-10T05:21:25 | {} | MEMBER |
vuejs | core | 2,105,935,590 | 10,913 | louis49 | Humm ok, but TSC seems not aware of that : it concludes to a wrong type | 2024-05-11T15:38:40 | 2024-05-11T15:38:40 | {} | NONE |
vuejs | core | 2,106,229,753 | 10,813 | nongtan7898 | Thank you it's ok But if I want to add data to data, it still gives the same error even though I add
```
await nextTick();
```
Go in. Please take a look. I have commit in github.
@edison1105 | 2024-05-12T12:25:17 | 2024-05-12T12:25:50 | {} | NONE |
vuejs | core | 2,108,023,308 | 10,933 | haoqunjiang | React 也是这么处理的。符合预期：https://zh-hans.react.dev/learn/conditional-rendering#:~:text=%E9%99%B7%E9%98%B1-,%E5%88%87%E5%8B%BF%E5%B0%86%E6%95%B0%E5%AD%97%E6%94%BE%E5%9C%A8%20%26%26%20%E5%B7%A6%E4%BE%A7.,-JavaScript%20%E4%BC%9A%E8%87%AA%E5%8A%A8 | 2024-05-13T15:33:27 | 2024-05-13T15:33:27 | {} | MEMBER |
vuejs | core | 2,097,101,529 | 10,860 | xiaodong2008 | But I think that the signature there has the wrong return type. In TypeScript, the defined return value is `r is Ref<T>`, but it doesn’t compare `T` at runtime, it should only be `r is Ref`
Is this for typecasting in some edge cases? | 2024-05-06T23:41:23 | 2024-05-07T00:54:11 | {} | CONTRIBUTOR |
vuejs | core | 2,097,749,810 | 10,870 | daniluk4000 | For me I was able to reproduce randomly, in production only, and nothing in stacktrace could give a hint.
I'll try to make repro later with same template stucture. If anyone will be able to find proper repro earlier it would be nice. | 2024-05-07T08:34:25 | 2024-05-07T08:34:25 | {} | NONE |
vuejs | core | 2,104,169,397 | 10,898 | jh-leong | > Thanks. I do note the other discussion is not about deep being used though.
Essentially the same issue: fragment-rooted components lack `data-v`.
`:deep() button` will be compiled into `[data-v-foo] button`, you can see in the [docs](https://vuejs.org/api/sfc-css-features.html#deep-selectors). | 2024-05-10T08:23:15 | 2024-05-10T08:23:15 | {} | MEMBER |
vuejs | core | 2,105,649,153 | 10,912 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9042600252)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9027497483) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-05-11T09:15:43 | 2024-05-11T09:15:43 | {} | CONTRIBUTOR |
vuejs | core | 2,106,509,849 | 10,920 | jh-leong | Workaround: use `symbol | string | number` instead of `keyof Record<...>`. See [playground](https://play.vuejs.org/#eNqNU22LGjEQ/itDvqwHVqEtFLarYIvQ9q7VqrTI5Sjr7mjX202WJGtdrP+9k8SXFbTcl5BMnpl5ZuaZHRuUZWdTIQtZpBOVlQY0mqqEPBarHmdGc9bnIitKqQx8lEUJSyULCDpd+7CuwXsuuEik0Aam86/3wzn0YFoXC5m3Al0Xr56xDu7OGLlYE2DHBYDBrQkh+DR8eBgF... | 2024-05-13T02:09:36 | 2024-05-13T02:09:36 | {} | MEMBER |
vuejs | core | 2,098,315,767 | 10,854 | jh-leong | As the issue points out, the endless loop happens because `generateCodeFrame` doesn't handle invalid `end` values correctly, causing the loop.
I fixed this in PR #10883.
About expecting the compiler to report errors, in Vue, always softly fail on failed runtime type inference. You can find the code [here](https:/... | 2024-05-07T12:41:05 | 2024-05-07T12:41:05 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,102,005,309 | 10,880 | kRaviteja7 | hi,
can i work on this issue? | 2024-05-09T06:07:40 | 2024-05-09T06:07:40 | {} | NONE |
vuejs | core | 2,105,647,292 | 10,912 | edison1105 | /ecosystem-ci run | 2024-05-11T09:09:01 | 2024-05-11T09:09:01 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,108,053,265 | 10,932 | haoqunjiang | 抱歉，我们无法处理不能复现的问题。
建议在浏览器隐身模式下重新打开一遍试试。考虑到浏览器里载入的代码与编辑器里完全不同，个人怀疑是其他项目的 main.js 缓存引起的。 | 2024-05-13T15:41:06 | 2024-05-13T15:41:06 | {} | MEMBER |
vuejs | core | 2,108,601,185 | 10,870 | ShuangDa1018 | > For me I was able to reproduce randomly, in production only, and nothing in stacktrace could give a hint.
>
> I'll try to make repro later with same template stucture. If anyone will be able to find proper repro earlier it would be nice.
the demo change, now npm run preview will report error like your code | 2024-05-13T19:05:52 | 2024-05-13T19:05:52 | {} | NONE |
vuejs | core | 2,097,081,051 | 10,874 | yyx990803 | Thank you for the PR! Made a few adjustments:
1. The inline `handler` seems unnecessary. It creates the overhead of extra function allocation and invocation and does not improve readability.
2. Passing `isKeyOf` down as a boolean avoids the object allocation and destructure. In framework code we typically are fine wi... | 2024-05-06T23:16:06 | 2024-05-06T23:16:06 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,098,259,570 | 10,883 | 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.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-07T12:10:13 | 2024-05-07T12:10:13 | {} | NONE |
vuejs | core | 2,103,091,624 | 10,351 | jack-allocate | How can we get around this functionality when we cant directly use ` v-model`?
Example (not the author of this reddit post): https://www.reddit.com/r/vuejs/comments/1clppby/tsx_error_when_registering_event_listener_for_an.
I'm having the same issue where I'm using Cypress component testing, but the `emitted` func... | 2024-05-09T17:25:15 | 2024-05-09T17:25:15 | {} | NONE |
vuejs | core | 2,104,176,306 | 10,898 | dten | I'll close this as not planned. Something to consider for the future though 😜
thanks for trying | 2024-05-10T08:26:59 | 2024-05-10T08:26:59 | {} | NONE |
vuejs | core | 2,105,857,987 | 10,915 | 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.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-11T14:24:31 | 2024-05-11T14:24:31 | {} | NONE |
vuejs | core | 2,097,109,452 | 10,870 | yyx990803 | Can't reproduce from your repro link. (I built the project locally with Vite) | 2024-05-06T23:49:25 | 2024-05-06T23:49:25 | {} | MEMBER |
vuejs | core | 2,098,225,447 | 8,281 | JontyMC | +1 for this, seem odd in order to simply wrap an input and provide support for .lazy you need to this:
```vue
<script setup lang="ts">
import { defineModel } from 'vue'
const [model, modifiers] = defineModel<string>()
function input(event: Event) {
if (modifiers.lazy) {
return
}
model.value = (ev... | 2024-05-07T11:52:31 | 2024-05-07T11:52:46 | {
"+1": 1,
"confused": 1
} | NONE |
vuejs | core | 2,098,590,425 | 10,870 | daniluk4000 | This happens for me also in v-for so I'll try it out and write back here | 2024-05-07T14:50:17 | 2024-05-07T14:50:17 | {
"+1": 1
} | NONE |
vuejs | core | 2,098,909,443 | 10,799 | john-landgrave | I've run into this issue as well and, having dug into the reactivity types, believe that this is ultimately a conflict between the typing of `Ref` and the typing of the `ref` functions especially when you consider the [documentation's recommendations for how to type ref's](https://vuejs.org/guide/typescript/composition... | 2024-05-07T17:00:27 | 2024-05-07T17:07:02 | {
"+1": 1
} | NONE |
vuejs | core | 2,104,027,057 | 10,901 | LinusBorg | This is by design. These hooks only run when the parent needs to re-render - and it doesn't need to, in this example, because the necessary update happens only in the slot, which is evaluated in the child component. | 2024-05-10T07:08:19 | 2024-05-10T07:08:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,104,828,082 | 10,903 | NathanFreeman | ```vue
[Boolean, String, Array]
```
In this case, the boolean operator has a higher precedence than the string. Therefore, it will evaluate to true. | 2024-05-10T15:42:07 | 2024-05-10T15:42:07 | {
"+1": 1
} | NONE |
vuejs | core | 2,105,948,567 | 10,913 | LinusBorg | Because you defined the argument that you pass into `compute()` to be `Register[]` - and the `Register` interface defines `val` to be a `ComputedRef<string>`, so that's what TS expects it to be, but it's not, because of unwrapping.
Here's a working approach:
https://play.vuejs.org/#eNp9Vd9P2zAQ/ldOeSGVskA3tkmlrcQ... | 2024-05-11T16:34:30 | 2024-05-11T16:35:56 | {} | MEMBER |
vuejs | core | 2,107,563,507 | 10,887 | littlezo | > 这是 JavaScript 的工作原理，与 Vue 无关。
该问题于 3.4.25 版本后出现
[10933](https://github.com/vuejs/core/issues/10933) | 2024-05-13T13:20:25 | 2024-05-13T13:20:25 | {} | NONE |
vuejs | core | 2,097,805,430 | 10,851 | quiteeasy | > We have a virtual-scroll component supports dynamic item height, each individual `virtual-scroll-item` grabs slot dom defined in parent via template ref, so its internal logic can use ResizeObserver to respond to the unpredictable slot dom size.
>
> In this case, each slot element's ref attr has an unique ref assi... | 2024-05-07T09:03:33 | 2024-05-07T09:03:33 | {} | CONTRIBUTOR |
vuejs | core | 2,100,173,555 | 10,844 | lukewarlow | > Remaining todos:
> Add a section in https://vuejs.org/guide/best-practices/security.html about trusted types compatibility, we can take https://angular.io/guide/security#enforcing-trusted-types as an example.
Am I correct in thinking this also could have a follow up to allow TrustedHTML objects to be passed to ... | 2024-05-08T09:36:47 | 2024-05-08T09:36:47 | {} | NONE |
vuejs | core | 2,103,959,373 | 10,898 | jh-leong | This issue has been discussed in #2669 previously, and you can find a response from member [here](https://github.com/vuejs/core/issues/2669#issuecomment-747433501). | 2024-05-10T06:34:12 | 2024-05-10T06:34:12 | {} | MEMBER |
vuejs | core | 2,105,635,784 | 10,910 | jh-leong | In your example, `getAttrs1` returns a new object each time it runs, and `v-bind` gets compiled into `_mergeProps($setup.getAttrs1(), { ... })`. This means that whenever the parent component updates, it gets a new object after `_mergeProps` runs again, causing the props to change.
For the situation you mentioned, yo... | 2024-05-11T08:38:28 | 2024-05-11T08:43:38 | {} | MEMBER |
vuejs | core | 2,106,546,920 | 10,924 | 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.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-13T03:00:05 | 2024-05-13T03:00:05 | {} | NONE |
vuejs | core | 2,109,110,992 | 10,938 | 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.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-14T01:34:39 | 2024-05-14T01:34:39 | {} | NONE |
vuejs | core | 2,109,237,268 | 10,939 | 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.glo... | 2024-05-14T04:03:19 | 2024-05-14T04:03:19 | {} | NONE |
vuejs | core | 2,098,292,069 | 10,882 | quiteeasy | The issue is caused by not setting the `.exp` field in `transforms/vFor.ts` for the key prop. The `.exp` property is set after all children are traversed. I'm currently working on a solution to address this problem. | 2024-05-07T12:28:25 | 2024-05-07T12:28:25 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 2,104,057,121 | 10,901 | warmthsea | > This is by design. These hooks only run when the parent needs to re-render - and it doesn't need to, in this example, because the necessary update happens only in the slot, which is evaluated in the child component.
Thanks, I saw the previous discussion.
https://github.com/vuejs/core/issues/4686 | 2024-05-10T07:18:22 | 2024-05-10T07:18:22 | {} | NONE |
vuejs | core | 2,105,441,714 | 10,903 | skirtles-code | This isn't happening by accident, it's intentional. There's an explicit check in the code for this specific case:
https://github.com/vuejs/core/blob/b2b5f57c2c945edd0eebc1b545ec1b7568e51484/packages/runtime-core/src/componentProps.ts#L568-L569
https://github.com/vuejs/core/blob/b2b5f57c2c945edd0eebc1b545ec1b7568e51... | 2024-05-11T01:49:04 | 2024-05-11T01:49:04 | {} | CONTRIBUTOR |
vuejs | core | 2,105,458,413 | 10,896 | haoqunjiang | /ecosystem-ci run | 2024-05-11T02:18:55 | 2024-05-11T02:18:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,105,818,856 | 10,914 | 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.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-11T14:07:08 | 2024-05-11T14:07:08 | {} | NONE |
vuejs | core | 2,106,859,668 | 10,920 | vaibhav11s | using the workaround wont give benefits of type inference.
my use-case
| 2024-05-13T07:36:44 | 2024-05-13T07:46:53 | {} | NONE |
vuejs | core | 2,097,647,726 | 10,852 | haoqunjiang | > I actually digged a little bit further and found an exact commit after which the issue started to happen: [53aaa1e](https://github.com/vuejs/core/commit/53aaa1eb2876baf9de16b2f2c77b2c5fd5173900) (found it using binary search on these commits: [v3.4.0-alpha.3...v3.4.0-alpha.4](https://github.com/vuejs/core/compare/v3.... | 2024-05-07T07:37:50 | 2024-05-07T07:37:50 | {} | MEMBER |
vuejs | core | 2,099,625,127 | 10,888 | 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.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-08T02:37:19 | 2024-05-08T02:37:19 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.