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,254,395,585 | 11,442 | jh-leong | Hello team, could you please help run the ecosystem-ci? Thanks! | 2024-07-28T08:37:05 | 2024-07-28T08:37:05 | {} | MEMBER |
vuejs | core | 2,255,515,334 | 11,452 | ChrisXv1999 | > 我看是执行了第二个`watch(flush:'post')`
>
> ![image](https://private-user-images.githubusercontent.com/40790268/353001262-ee830341-088b-40b9-92a8-5048ea44e3b9.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjIyNDczNDAsIm5iZiI6... | 2024-07-29T10:03:29 | 2024-07-29T10:03:29 | {} | NONE |
vuejs | core | 2,256,003,404 | 11,453 | yyx990803 | Like @LinusBorg explained - this is because the `.value` of a ref is deeply unwrapped for potential refs, so the type doesn't always match the raw class type.
Closing as a wontfix as there is no direct way to make this work without introducing breaking changes. | 2024-07-29T13:50:04 | 2024-07-29T13:50:04 | {
"heart": 2
} | MEMBER |
vuejs | core | 2,258,039,113 | 6,309 | episage | @einavk I tried with
```
:key="`${Math.random()}`" :key-x="`${Math.random()}`"
```
but to no avail.
Is this what you had in mind? | 2024-07-30T10:40:00 | 2024-07-30T10:40:00 | {} | NONE |
vuejs | core | 2,260,397,455 | 11,463 | jh-leong | duplicate of #10351 | 2024-07-31T12:23:18 | 2024-07-31T12:23:18 | {} | MEMBER |
vuejs | core | 2,262,685,154 | 11,471 | edison1105 | /ecosystem-ci run | 2024-08-01T10:21:27 | 2024-08-01T10:21:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,252,653,686 | 11,427 | kakkokari-gtyih | Works fine with the fix in #11431: https://deploy-preview-11431--vue-sfc-playground.netlify.app/#eNrNVE1v2kAQ/StT9xAigQ1pTsggQZRD26iNSm5xDos9wCb2rrW7NiDEf+/seu1ClaaReunFWs+8efN2PvYQzMoyrCsMxkGsU8VLAxpNVU4TwYtSKgMHULiCI6yULOCCoBed60YW5cw7wsj9Wa5zwPwMMPeARKRS6AZxx+kwgcdEQEPZb09zOj210LRSCoVFkqDe8NKSRBGMQlhsuUk3YKRPuMSVVOj... | 2024-07-26T12:24:21 | 2024-07-26T12:24:21 | {} | CONTRIBUTOR |
vuejs | core | 2,253,329,458 | 389 | skirtles-code | I think the changes proposed here are essentially the same as #11287, and I believe the same reasoning that justified closing that PR would apply here too. | 2024-07-26T19:16:22 | 2024-07-26T19:16:22 | {} | CONTRIBUTOR |
vuejs | core | 2,254,892,659 | 11,450 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 90 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 147 kB | 54 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-07-29T03:55:26 | 2024-07-29T03:55:26 | {} | NONE |
vuejs | core | 2,259,576,152 | 4,662 | SavkaTaras | I used the following plugin to resolve all issues:
https://github.com/baiwusanyu-c/unplugin-vue-ce/tree/master
Works like magic. I understand this is not an official fix, but this is good. | 2024-07-31T03:37:56 | 2024-07-31T03:37:56 | {} | NONE |
vuejs | core | 2,260,437,665 | 11,464 | jh-leong | You should use [withDefaults](https://vuejs.org/api/sfc-script-setup.html#default-props-values-when-using-type-declaration) to provide default values for the props, like this:
```ts
interface Props {
color?: string;
}
withDefaults(defineProps<Props>(), {
color: 'red',
});
``` | 2024-07-31T12:44:25 | 2024-07-31T12:44:25 | {} | MEMBER |
vuejs | core | 2,260,491,368 | 10,351 | JoCa96 | I am unsure, if I understand the use-case of `defineModel` correctly?
E.g., we are building a component library and `defineModel` creates typings which allow setting the property without v-model and or event handler: `<Comp :modelProp="true" />`. But with the current implementation of `defineModel` it will always be... | 2024-07-31T13:10:51 | 2024-07-31T13:12:11 | {
"+1": 2
} | NONE |
vuejs | core | 2,198,541,803 | 9,270 | unshame | If your target consistently renders before your source, you can disable the teleport until onMounted and it should work. | 2024-06-30T12:11:43 | 2024-07-28T12:53:05 | {} | NONE |
vuejs | core | 2,254,754,055 | 11,447 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 90 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 147 kB | 54 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-07-29T01:02:09 | 2024-07-29T01:02:09 | {} | NONE |
vuejs | core | 2,254,761,513 | 9,270 | edison1105 | fixed via https://github.com/vuejs/core/commit/59a3e88903b10ac2278170a44d5a03f24fef23ef
It will be out in v3.5 | 2024-07-29T01:13:10 | 2024-07-29T01:13:10 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,257,730,493 | 11,427 | kakkokari-gtyih | Any updates on this? | 2024-07-30T08:06:20 | 2024-07-30T08:06:20 | {} | CONTRIBUTOR |
vuejs | core | 2,260,196,466 | 11,462 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ---------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 95.3 kB (**+5.21 kB**) | 36.3 kB (**+1.81 kB**) ... | 2024-07-31T10:31:51 | 2024-07-31T10:31:51 | {} | NONE |
vuejs | core | 2,253,772,641 | 11,442 | jh-leong | It seems that this PR breaks the vueuse dts build. I will convert this to a draft and work on fixing this. | 2024-07-27T05:13:17 | 2024-07-28T08:34:00 | {} | MEMBER |
vuejs | core | 2,254,771,728 | 11,445 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 90 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 147 kB | 54 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-07-29T01:27:47 | 2024-07-29T01:27:47 | {} | NONE |
vuejs | core | 2,255,366,568 | 11,392 | chuyuandu | > https://github.com/vuejs/core/blob/fd5c001ec732197b1bbfc42b666a72ba65c4c4d7/packages/runtime-core/src/vnode.ts#L232-L233
>
> appContext can't be set in that way, it's only set on a root node when creating an app with `createApp`
is there a solution to render vue component programmatically and set its parent vno... | 2024-07-29T08:52:10 | 2024-07-29T08:52:10 | {} | NONE |
vuejs | core | 2,256,008,996 | 11,437 | yyx990803 | To avoid ambiguity, you should use PascalCase components in SFC templates. | 2024-07-29T13:52:22 | 2024-07-29T13:52:22 | {
"+1": 2,
"-1": 2
} | MEMBER |
vuejs | core | 2,257,291,534 | 11,456 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90 kB (**+121 B**) | 34.5 kB (**+68 B**) | 31.1 kB (**+50 B**) |
... | 2024-07-30T01:34:13 | 2024-07-30T02:48:23 | {
"+1": 1
} | NONE |
vuejs | core | 2,257,362,073 | 11,456 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/10155305785)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10138361984) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-07-30T02:56:40 | 2024-07-30T02:56:40 | {} | CONTRIBUTOR |
vuejs | core | 2,259,428,675 | 11,459 | yyx990803 | `ComponentExposed` is used to extract explicitly exposed properties via `defineExpose()` or `setupContext.expose()`, not the component instance type. | 2024-07-31T00:46:33 | 2024-07-31T00:46:33 | {} | MEMBER |
vuejs | core | 2,248,436,717 | 8,482 | Sinled | Any updates here? I am having this problem when importing `InferType` from yup | 2024-07-24T16:24:58 | 2024-07-24T16:24:58 | {
"+1": 1
} | NONE |
vuejs | core | 2,254,785,862 | 11,442 | yyx990803 | @jh-leong I've invited you to the team btw. Thank you for your contributions! | 2024-07-29T01:46:12 | 2024-07-29T01:46:12 | {
"heart": 2,
"hooray": 2
} | MEMBER |
vuejs | core | 2,255,845,661 | 11,423 | qtencent7 | 这个东西，我觉得无解吧，我试了，就算不是vue里面，像你那样写，也会出现这种卡死 | 2024-07-29T12:49:25 | 2024-07-29T12:49:25 | {} | NONE |
vuejs | core | 2,259,550,232 | 11,382 | yyx990803 | @nathan-de-pachtere I can't find the invitation in my emails. Can you just post the link to the private repo here? | 2024-07-31T03:06:01 | 2024-07-31T03:06:01 | {} | MEMBER |
vuejs | core | 2,262,227,169 | 11,469 | LinusBorg | No, it does not. You change the shallow Ref's value, because you assigned a new object. **That** triggers the re-render on the next tick, which happens after you also changed a non-reactive `name` property on that object. So when the DOM is updated (because of the new object, not because of the change to `name`), the c... | 2024-08-01T07:18:17 | 2024-08-01T07:18:43 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,257,356,338 | 11,456 | edison1105 | /ecosystem-ci run | 2024-07-30T02:49:36 | 2024-07-30T02:49:36 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,258,479,919 | 11,458 | yyx990803 | @skirtles-code
> Should strategies be provided with a way to do tear down logic? e.g. If an async component is removed before it is hydrated, the strategy may need to remove listeners on document, or watchers on a store.
Good point, I should also add a test case for a non-hydrated tree to be removed before ever ... | 2024-07-30T14:22:00 | 2024-07-30T14:22:00 | {} | MEMBER |
vuejs | core | 2,248,260,148 | 11,400 | obulat | The new `targetStart` property of the teleport vnode is not populated when hydrating an SSR-rendered teleport. So,
`n1` here is not `null`, but does not have `targetStart`:
https://github.com/vuejs/core/blob/422ef34e487f801e1162bed80c0e88e868576e1d/packages/runtime-core/src/components/Teleport.ts#L73-L74
So, the... | 2024-07-24T15:08:05 | 2024-07-24T15:22:35 | {} | NONE |
vuejs | core | 2,249,900,189 | 11,298 | houfeng0923 | @yangliguo7 i don't think so .
if setup throw error, run template render is not necessary.
the error message need indicated the root reason, it's an exception in setup ,not mistake from template . | 2024-07-25T09:34:28 | 2024-07-25T09:34:28 | {} | NONE |
vuejs | core | 2,252,356,124 | 9,702 | lvjiaxuan | @yangxiuxiu1115 Why not keep doing this PR? | 2024-07-26T09:37:27 | 2024-07-26T09:37:27 | {} | NONE |
vuejs | core | 2,254,754,068 | 11,448 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 90 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 147 kB | 54 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-07-29T01:02:10 | 2024-07-29T01:02:10 | {} | NONE |
vuejs | core | 2,258,059,085 | 6,309 | einavk | Yes, yet we did not bind to key but to a custom data attribute, such as data-id.
I'm not sure it matters. We are working with vue version 3.3.7 which might also make some difference. | 2024-07-30T10:51:37 | 2024-07-30T10:51:37 | {} | NONE |
vuejs | core | 2,260,489,776 | 11,459 | TheDutchCoder | Okay interesting, this issue here recommends using it: https://github.com/vuejs/language-tools/issues/3206
Maybe there's some misunderstanding on my side and these are different issues? | 2024-07-31T13:10:04 | 2024-07-31T13:10:04 | {} | NONE |
vuejs | core | 2,043,957,701 | 10,664 | baiwusanyu-c | It is recommended to change the title to English, and this is not a bug fix. It is recommended to use 'perf' as the beginning. | 2024-04-09T01:09:40 | 2024-04-09T01:09:40 | {} | MEMBER |
vuejs | core | 2,046,501,845 | 3,435 | yyx990803 | Yes, I believe this PR is stale now, sorry for letting it hang and thanks for the PR regardless 🙏 | 2024-04-10T04:04:41 | 2024-04-10T04:04:41 | {} | MEMBER |
vuejs | core | 2,047,603,009 | 5,407 | skirtles-code | I believe the problem described here is with **comment** nodes, not **text** nodes.
I migrated the reproduction to the Vue SFC Playground:
- [Reproduction](https://play.vuejs.org/#eNqNU8lu2zAQ/ZUxL3YAS0LRnlzZ6IIUaA9p0QbohRdHHslMKFLgorgw/O8dkoqXxFlOEue9N5x5M9yyz12X9x7ZjJW2MqJzYNH5bsGVaDttHPwVbv1Vty0qd6VXCLXRLYzz4l... | 2024-04-10T13:49:10 | 2024-04-10T13:49:10 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,050,894,284 | 7,017 | skirtles-code | I think this problem may have been fixed in 3.4.7 by this commit:
- https://github.com/vuejs/core/commit/7976f7044e66b3b7adac4c72a392935704658b10
I'm not able to access the original reproduction for #7021 to confirm. I made a Playground to try to replicate the issue based on the description, and it starts working... | 2024-04-12T03:19:58 | 2024-04-12T03:19:58 | {} | CONTRIBUTOR |
vuejs | core | 2,051,614,631 | 10,677 | quiteeasy | #10688 | 2024-04-12T11:53:43 | 2024-04-12T11:53:43 | {} | CONTRIBUTOR |
vuejs | core | 2,053,810,018 | 7,637 | skirtles-code | I think this problem was resolved in 3.4.0 by #8950. | 2024-04-14T00:07:32 | 2024-04-14T00:07:32 | {} | CONTRIBUTOR |
vuejs | core | 2,044,308,818 | 10,667 | quiteeasy | preFetch is handled by the Quasar framework internally, it is not a part of Vue. It seems that components with preFetch are not converted to async components by Quasar and Suspense works only with async components or async setup function according to [docs](https://vuejs.org/guide/built-ins/suspense.html#async-dependen... | 2024-04-09T07:22:26 | 2024-04-09T07:22:26 | {} | CONTRIBUTOR |
vuejs | core | 2,046,182,292 | 4,273 | skirtles-code | I believe this problem was fixed in #6671, so this PR can now be closed. | 2024-04-09T23:12:13 | 2024-04-09T23:12:13 | {} | CONTRIBUTOR |
vuejs | core | 2,049,143,332 | 10,678 | LinusBorg | Please provide a minimal reproduction. We can't debug your docker image | 2024-04-11T07:59:54 | 2024-04-11T07:59:54 | {} | MEMBER |
vuejs | core | 2,049,258,410 | 10,676 | zigomir | > > https://vuejs.org/guide/components/props.html#boolean-casting
>
> ```ts
> const value = defineModel<boolean | string>({ required: true });
> ```
Thanks!
I now see that if I change order from `<string | boolean>` to `<boolean | string>` then both prod and dev work the same, which is definitely better. Alt... | 2024-04-11T09:10:03 | 2024-04-11T09:10:03 | {} | NONE |
vuejs | core | 2,049,713,295 | 10,678 | microwin7 | the person who created the docker file said that the version should not have changed, which means all packages should correspond to those in yarn.lock
https://github.com/GravitLauncher-SUPPORT/LauncherWiki/blob/main/yarn.lock | 2024-04-11T13:37:03 | 2024-04-11T13:37:03 | {} | NONE |
vuejs | core | 2,049,769,788 | 10,678 | microwin7 | > Giving us instructions on how to run your app in docker does not qualify as a "minimal runnable reproduction"
>
> Please read the issue guidelines
Sorry if I couldn’t understand you on this issue, last time, when providing an error, I only sent a link to the site and the problem was found | 2024-04-11T14:04:00 | 2024-04-11T14:04:00 | {} | NONE |
vuejs | core | 2,051,570,740 | 10,684 | LinusBorg | Overloading like this is simply not supported. You even get a dev warning informing you that "Computed property "myItem" is already defined in Props."
So the solution is: use different names for the prop and the computed. That makes for clear, understandable code that does not rely on implicit behavior.
Sidenote:... | 2024-04-12T11:22:19 | 2024-04-12T11:29:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,051,617,795 | 10,688 | quiteeasy | fix #10677 #2482 | 2024-04-12T11:55:49 | 2024-04-12T12:00:21 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,053,881,697 | 7,869 | skirtles-code | I believe #8012 added these same tests. | 2024-04-14T03:22:00 | 2024-04-14T03:22:00 | {} | CONTRIBUTOR |
vuejs | core | 2,053,967,141 | 10,383 | yyx990803 | Tested with the recent commits (4bc9f39f028af7313e5cf24c16915a1985d27bf8, 6af733d68eb400a3d2c5ef5f465fff32b72a324e, ca84316bfb3410efe21333670a6ad5cd21857396) on your repo, they did improve things significantly. On my machine the curl response time stays consistent within the 0.006 to 0.02s range throughout the k6 run.
... | 2024-04-14T08:37:35 | 2024-04-14T08:37:35 | {} | MEMBER |
vuejs | core | 2,054,029,936 | 10,652 | edison1105 | /ecosystem-ci run | 2024-04-14T12:16:52 | 2024-04-14T12:16:52 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,044,380,196 | 10,664 | haoqunjiang | Closing as it's already part of the `for` loop condition. | 2024-04-09T07:59:27 | 2024-04-09T07:59:27 | {} | MEMBER |
vuejs | core | 2,045,947,668 | 2,575 | skirtles-code | I know this PR is very old, but...
Isn't the functionality being added here already available with `renderToString`? If I've understood correctly, this PR is proposing adding something like this:
```js
const { result, context } = await renderToContext(app)
```
But I think this can already be achieved using:
... | 2024-04-09T19:52:52 | 2024-04-09T19:52:52 | {} | CONTRIBUTOR |
vuejs | core | 2,046,685,599 | 10,672 | troy351 | Duplicate of #7754
Using `shallowRef` as a workaround, though it can't be watched anymore | 2024-04-10T07:11:35 | 2024-04-10T07:18:32 | {} | NONE |
vuejs | core | 2,049,326,616 | 10,682 | TonisfelTr | > https://play.vuejs.org/#eNp9klFv1DAMx7+KlZdt0qllsKejnNjQHuABEPBGEMoS7y63NokS57ip6nfHadfeHqapUmv7b8c/O+3FdQjVIaNYi4awC60i3EgH0ISIm76HEL3JmhIMQ1OX2CjeZSLvgB4DfpBi8qSAj7q1+oEjyhgpNtfGNPUkcllTP2vAbtLRBmIbj8FHAoP3KrcEfelgFKnzi8kGiEg5utmDBWoNv/+spuDwvnyH0euQdt6w+lTANKezAOoamAz83R41gWUqIA8qRvU4p9DOpmruUoWcduc9ONXhGs5ulOPnbA... | 2024-04-11T09:49:11 | 2024-04-11T09:49:11 | {} | NONE |
vuejs | core | 2,050,409,737 | 6,319 | skirtles-code | I was wondering whether this change is still required? It seems quite similar to #3820, which was released in 3.2.42. | 2024-04-11T19:49:37 | 2024-04-11T19:49:37 | {} | CONTRIBUTOR |
vuejs | core | 2,050,858,395 | 10,681 | guaijie | > Workaround: `const props = defineProps<Props,>()` https://stackoverflow.com/a/32697733/2302258
>
> 热更新出错是合理的，不过可能需要看一下为什么初次加载时没出错。
你给的链接中的情况和这里的情况并不一样，链接中提到的是在 tsx 中定义一个泛型时出现报错的原因和解决方法。
这里定义了一个泛型 T1.
但是在使用时是不会报错的:
... | 2024-04-12T02:34:16 | 2024-04-12T02:37:51 | {} | CONTRIBUTOR |
vuejs | core | 2,053,523,771 | 5,423 | bosens-China | Thank you! | 2024-04-13T06:27:54 | 2024-04-13T06:27:54 | {} | NONE |
vuejs | core | 2,053,970,621 | 10,383 | prashantpalikhe | That is absolutely amazing @yyx990803
Thank you so much! | 2024-04-14T08:49:51 | 2024-04-14T08:49:51 | {} | NONE |
vuejs | core | 2,040,868,219 | 10,652 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.6 kB (**+57 B**) | 34.4 kB (**+24 B**) | 31.1 kB (**+38 B**) |
... | 2024-04-06T02:04:55 | 2024-04-14T12:17:52 | {} | NONE |
vuejs | core | 2,054,114,910 | 8,083 | leeeisok | I get this error (only during build) when importing a type with relative path eg:
```
'../types/myfile' ❌
```
when I use project root import, it resolves without errors
```
'@/types/myfile' ✅
```
I should note that this error arises when I import a file to use in defineProps<MyType>() since we can do that now... | 2024-04-14T16:31:53 | 2024-04-14T16:31:53 | {} | NONE |
vuejs | core | 2,054,150,011 | 4,635 | ankitsinghaniyaz | Is this still something that Vue will support? | 2024-04-14T18:39:04 | 2024-04-14T18:39:04 | {} | NONE |
vuejs | core | 2,049,017,509 | 10,680 | LinusBorg | This is not a bug. They don't "affect each other". Vue components update the whole template with *all* latest data when *any* reactive dependency changes. | 2024-04-11T06:38:16 | 2024-04-11T06:38:16 | {} | MEMBER |
vuejs | core | 2,049,720,048 | 10,678 | microwin7 | the local yarn.lock file, where the assembly was without a container, corresponds to the one I sent via the link on Github | 2024-04-11T13:40:27 | 2024-04-11T13:40:27 | {} | NONE |
vuejs | core | 2,049,728,326 | 10,678 | microwin7 | ```
app-DvS0BFpB.js:17 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'nextSibling')
at nextSibling (app-DvS0BFpB.js:17:669)
at f (app-DvS0BFpB.js:13:24971)
at m (app-DvS0BFpB.js:13:26626)
at d (app-DvS0BFpB.js:13:25940)
at f (app-DvS0BFpB.js:13:25133)
at Oe (app... | 2024-04-11T13:44:27 | 2024-04-11T13:44:41 | {} | NONE |
vuejs | core | 1,984,784,025 | 10,397 | rschristian | Some of it is likely only relevant to Preact signals, and not necessarily this change here in Vue, but there's a blog article going over why we (Preact) used linked lists (amongst other things) here: https://preactjs.com/blog/signal-boosting | 2024-03-07T23:37:29 | 2024-04-12T22:19:02 | {
"+1": 3,
"heart": 8,
"rocket": 1
} | NONE |
vuejs | core | 2,053,980,230 | 9,421 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8679202970)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8657200885) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-04-14T09:22:16 | 2024-04-14T09:22:16 | {} | CONTRIBUTOR |
vuejs | core | 2,008,579,962 | 10,551 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-03-20T02:36:08 | 2024-04-15T07:30:53 | {} | NONE |
vuejs | core | 2,043,954,075 | 10,664 | baiwusanyu-c | /ecosystem-ci run | 2024-04-09T01:04:30 | 2024-04-09T01:04:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,046,837,264 | 10,673 | limit81995 | 破案了，没有超能力无法访问，js无法加载。 使用了超能力就可以访问了。 | 2024-04-10T08:07:39 | 2024-04-10T08:07:39 | {
"eyes": 1,
"laugh": 3
} | NONE |
vuejs | core | 2,047,366,702 | 10,676 | sqal | https://github.com/vuejs/core/pull/9603 | 2024-04-10T12:03:37 | 2024-04-10T12:03:37 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,049,997,077 | 8,576 | rcjiang | This issue can lead to application corruption after updating dependencies.
I only discovered this discussion after mentioning an RFC.
https://github.com/vuejs/rfcs/discussions/660 | 2024-04-11T15:44:39 | 2024-04-11T15:44:39 | {} | NONE |
vuejs | core | 2,050,179,709 | 6,162 | skirtles-code | This PR looks good to me, but it seems that #8558 made essentially the same changes, and that has been merged into `main`. Unless I'm missing something, I think this PR can now be closed. | 2024-04-11T17:34:44 | 2024-04-11T17:34:44 | {} | CONTRIBUTOR |
vuejs | core | 2,053,978,008 | 9,421 | yyx990803 | /ecosystem-ci run | 2024-04-14T09:15:22 | 2024-04-14T09:15:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,046,731,715 | 10,672 | YunHuiRan | > Duplicate of #7754 Using `shallowRef` as a workaround, though it can't be watched anymore
Thank you! I think it will be just find even if it can't be watched. | 2024-04-10T07:32:14 | 2024-04-10T07:32:14 | {} | NONE |
vuejs | core | 1,766,400,998 | 9,413 | rudyxu1102 | > I think this PR and #7444 can be combined into one. WDYT?
Of course.Thank you for your positive response. | 2023-10-17T13:17:25 | 2024-04-10T07:38:20 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 2,049,563,671 | 8,900 | rudolfbyker | A workaround specifically for Sentry: Use this integration https://docs.sentry.io/platforms/javascript/configuration/integrations/captureconsole/ along with the compile time flag https://vuejs.org/api/compile-time-flags.html#VUE_PROD_HYDRATION_MISMATCH_DETAILS . But this is not a general solution. | 2024-04-11T12:14:40 | 2024-04-11T12:14:40 | {} | NONE |
vuejs | core | 2,051,011,446 | 10,677 | quiteeasy | It also affects `<transition-group>` the same way | 2024-04-12T05:34:16 | 2024-04-12T05:35:05 | {} | CONTRIBUTOR |
vuejs | core | 2,051,179,561 | 10,681 | guaijie | > 不好意思，是我看错了。我再仔细研究一下。
还有一个问题，setup tsx 的方式封装组件，热更新会很慢（控制台没有输出热更新，或者很久才会输出热更新成功）。需要手动刷新浏览器，且重新加载的过程十分缓慢（就好像是所有缓存被清理，需要重新加载所有依赖的并缓存一样），大多需要重新启动项目才能正常使用
| 2024-04-12T07:30:26 | 2024-04-12T07:37:54 | {} | CONTRIBUTOR |
vuejs | core | 2,054,080,271 | 10,697 | LinusBorg | https://vuejs.org/guide/components/attrs.html#fallthrough-attributes | 2024-04-14T14:29:31 | 2024-04-14T14:29:31 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,054,081,249 | 10,696 | LinusBorg | Refs in v-for involve a bit of compile-time work. That can'r happen when the compiler can't see the ref prop in the template.
I'd say we need to document this, at least I dont see a realistic way to "fix" it - but someone else might have an idea? | 2024-04-14T14:33:04 | 2024-04-14T14:33:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,054,846,048 | 7,800 | skirtles-code | Since 3.4.0, the Playground I shared above does show hydration mismatch warnings. The warning includes the following note:
> Note: this mismatch is check-only. The DOM will not be rectified in production due to performance overhead.
> You should fix the source of the mismatch.
In my opinion, there's nothing more... | 2024-04-15T03:56:45 | 2024-04-15T03:56:45 | {} | CONTRIBUTOR |
vuejs | core | 2,047,163,332 | 10,674 | guaijie | > Duplicate of #9882
>
> See also: [vuejs/vue#4792](https://github.com/vuejs/vue/issues/4792) [vuejs/vue#7646](https://github.com/vuejs/vue/issues/7646)
麻烦认真看下别人的提出的 issue ，不要直接选择关闭，你对我的 issue 有什么问题请答复，可以互相交流。我查过别人提出的 issue，别人没有正确的的回复，而且你回给我的链接都是被关闭的。我正是因为你们关闭了这些issues 才重新提的。 | 2024-04-10T10:30:00 | 2024-04-10T10:36:38 | {} | CONTRIBUTOR |
vuejs | core | 2,047,406,102 | 6,095 | KaelWD | @ml1nk @Akryum Are you still getting this with vue 3.4? | 2024-04-10T12:24:34 | 2024-04-10T12:24:34 | {} | CONTRIBUTOR |
vuejs | core | 2,049,209,230 | 10,682 | Shyam-Chen | https://play.vuejs.org/#eNp9klFv1DAMx7+KlZdt0qllsKejnNjQHuABEPBGEMoS7y63NokS57ip6nfHadfeHqapUmv7b8c/O+3FdQjVIaNYi4awC60i3EgH0ISIm76HEL3JmhIMQ1OX2CjeZSLvgB4DfpBi8qSAj7q1+oEjyhgpNtfGNPUkcllTP2vAbtLRBmIbj8FHAoP3KrcEfelgFKnzi8kGiEg5utmDBWoNv/+spuDwvnyH0euQdt6w+lTANKezAOoamAz83R41gWUqIA8qRvU4p9DOpmruUoWcduc9ONXhGs5ulOPnbAWq... | 2024-04-11T08:40:42 | 2024-04-11T08:40:42 | {} | CONTRIBUTOR |
vuejs | core | 2,049,692,776 | 10,682 | haoqunjiang | Remove `v-bind="product.name"`, `v-bind="product.name"`, ` v-bind="product.amount"`, etc.
That's not how it's supposed to be used.
https://vuejs.org/api/built-in-directives.html#v-bind
Next time, before opening a bug report, please read the issue form:
> **Before You Start...**
>
> This form is only for sub... | 2024-04-11T13:26:32 | 2024-04-11T13:26:47 | {} | MEMBER |
vuejs | core | 2,050,260,626 | 6,169 | skirtles-code | I believe this same fix was merged in #6714, and was released in 3.2.41. The symptoms in the bug report for that PR were slightly different, but the fix ended up being the same. | 2024-04-11T18:20:04 | 2024-04-11T18:20:04 | {} | CONTRIBUTOR |
vuejs | core | 2,053,591,495 | 10,688 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------------------ | ------------------ |
| runtime-dom.global.prod.js | 90.5 kB | 34.4 kB (**-1 B**) | 31 kB (**+11 B**) |
| vue.global.prod.js | 148 kB | 5... | 2024-04-13T09:36:42 | 2024-04-13T09:36:42 | {} | NONE |
vuejs | core | 2,056,129,805 | 8,550 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.6 kB | 34.4 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-04-15T08:22:09 | 2024-04-15T08:22:09 | {} | NONE |
vuejs | core | 2,046,171,357 | 2,575 | arpowers | Agree. Haven't had an issue with it lately. It must have been resolved. | 2024-04-09T22:59:19 | 2024-04-09T22:59:19 | {} | NONE |
vuejs | core | 2,046,332,145 | 4,990 | skirtles-code | #6858 (merged in 3.2.45) seems to be trying to fix the same problem. Is this PR still required, or can it be closed? | 2024-04-10T02:09:29 | 2024-04-10T02:09:29 | {} | CONTRIBUTOR |
vuejs | core | 2,046,683,394 | 8,173 | troy351 | Duplicate of #7754 | 2024-04-10T07:10:19 | 2024-04-10T07:10:19 | {} | NONE |
vuejs | core | 2,047,194,667 | 10,674 | Justineo | This is a known issue that has been discussed for several times. Changing the behavior will be a breaking change that we cannot make at the point in Vue 3. | 2024-04-10T10:46:53 | 2024-04-10T10:46:53 | {} | MEMBER |
vuejs | core | 2,049,767,814 | 10,678 | microwin7 | Sorry, I solved my problem, it was a crookedly configured proxy server in the container
```nginx
server {
listen 80;
root /app;
location / {
try_files $uri /index.html;
}
}
```
And it was necessary like this:
```nginx
server {
listen 80;
root /app;
location / {
... | 2024-04-11T14:03:03 | 2024-04-11T14:03:03 | {} | NONE |
vuejs | core | 2,049,863,754 | 10,677 | quiteeasy | I have identified an issue in the Vue 3 repository that seems to persist even in the absence of an 'appear' prop. Specifically, when clicking on the overlay to close it, there is a short period during which no transition classes are applied, causing the styles to revert to their final state(there are flicks because of ... | 2024-04-11T14:45:39 | 2024-04-11T14:45:39 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,043,959,176 | 10,664 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8608757149)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8594783393) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-04-09T01:11:47 | 2024-04-09T01:11:47 | {} | CONTRIBUTOR |
vuejs | core | 2,047,010,356 | 10,167 | juliusmarminge | Seems fixed now with latest versions | 2024-04-10T09:25:06 | 2024-04-10T09:25:06 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.