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,882,965,806 | 10,039 | LinusBorg | If you check your network tab - that happens because of the other package you have incluced, which you get from jsdelivr.
jsdelivr's esm support automatically rewrites imports the the matching urls on jsdelivr, and that rewrite results in a rewrite to esm-bundler.
Are you saying this exact same file from jsdelivr... | 2024-01-09T12:15:21 | 2024-01-09T12:16:16 | {} | MEMBER |
vuejs | core | 1,883,840,047 | 10,036 | lehni | @yyx990803 I finally found time to do the test, and I can confirm that this works in my case! | 2024-01-09T21:38:32 | 2024-01-09T21:38:32 | {} | CONTRIBUTOR |
vuejs | core | 1,883,968,330 | 4,423 | Kadeluxe | Yes, still not resolved. | 2024-01-09T23:44:09 | 2024-01-09T23:44:09 | {} | NONE |
vuejs | core | 1,880,081,951 | 9,987 | briankchan | Thanks for that pointer; there's also a part of the [`defineModel` documentation in the source code](https://github.com/vuejs/core/blob/68e5cc6ac8fc289372831c5fbdff09e63728fc00/packages/runtime-core/src/apiSetupHelpers.ts#L237) that reads:
```
* The the returned ref behaves differently depending on whether the paren... | 2024-01-07T14:56:04 | 2024-01-07T14:56:04 | {} | NONE |
vuejs | core | 1,881,863,586 | 10,039 | LinusBorg | The error message you posted shows that you used runtime-core.esm-BUNDLER.js, while you want to use runtime-core.esm-BROWSER.js
As there was no runnable reproduction provided, I'm assuming that already was the mistake and can close this. | 2024-01-08T21:39:18 | 2024-01-08T21:39:43 | {} | MEMBER |
vuejs | core | 1,881,990,853 | 10,041 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.7 kB (**+154 B**) | 34.1 kB (**+44 B**) | 30.7 kB (**+33 B**)... | 2024-01-08T23:40:08 | 2024-01-08T23:40:08 | {} | NONE |
vuejs | core | 1,881,996,987 | 10,041 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7454541028)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7443374236) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/745... | 2024-01-08T23:47:36 | 2024-01-08T23:47:36 | {} | CONTRIBUTOR |
vuejs | core | 1,882,113,934 | 9,206 | Alfred-Skyblue | @ferferga The functionality has temporarily shifted to be implemented in #9651. I noticed your mention in the RFC that state changes in internal components during the execution of a Transition animation would disrupt the animation state. Regarding the solution you proposed:
> Stop dependency/effect tracking of the c... | 2024-01-09T01:14:35 | 2024-01-09T01:14:35 | {} | MEMBER |
vuejs | core | 1,755,243,157 | 9,370 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.6 kB (**+84 B**) | 34.1 kB (**+56 B**) | 30.7 kB (**+28 B**) |
... | 2023-10-10T12:06:55 | 2024-01-09T10:07:19 | {} | NONE |
vuejs | core | 1,883,319,512 | 10,039 | LinusBorg | > I have the same issue. I can reproduce it with the example given by [Parcel](https://parceljs.org/languages/vue/) with a production build.
>
> It still worked in version v3.4.0-rc.1 and is broken since version v3.4.0-rc.2. I assume it broke with this commit: [ee68c52#diff-5ab5fe7b450649335062cee0ca4f1499ae23f78f14... | 2024-01-09T15:57:12 | 2024-01-09T15:57:12 | {} | MEMBER |
vuejs | core | 1,884,241,670 | 10,058 | Alfred-Skyblue | During the getter execution, the ReactiveEffect of the computed value is stored in the Ref (show.dep), preventing it from being garbage collected.
See: [playground](https://play.vuejs.org/#eNqNU1Fv2jAQ/iu3vDRoxdHUSZMQsG6oD5vUdip9jDRCckncOnZkO4CE+O872xAyNlV9Afu+z3ff3X3ZR9/alm06jCbR1GLTisziPJUA03VnrZJwmwuev87SSMmFO6XR... | 2024-01-10T06:01:28 | 2024-01-10T06:01:28 | {} | MEMBER |
vuejs | core | 1,884,260,170 | 9,647 | wangcch | Again, how do you set `EmitsOptions` in `Functional Signature` mode ?
```ts
import type { SetupContext } from 'vue';
const Comp = defineComponent(
<T extends string | number>(
props: { modelValue: T },
ctx: SetupContext<{ 'update:modelValue': (val: T) => void }>
) => {
return () => {
... | 2024-01-10T06:23:31 | 2024-01-10T06:23:31 | {} | NONE |
vuejs | core | 1,880,118,163 | 10,028 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| ---------------------------- | -------------------- | -------------------- | -------------------- |
| runtime-dom.global.prod.js | 90.2 kB (**+809 B**) | 34.3 kB (**+263 B**) | 30.9 kB ... | 2024-01-07T17:23:07 | 2024-01-07T17:23:07 | {} | NONE |
vuejs | core | 1,877,145,937 | 9,999 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 89.4 kB (**+8 B**) | 34 kB (**+5 B**) | 30.7 kB (**+2 B**) |
| vue.... | 2024-01-04T14:04:28 | 2024-01-08T07:55:53 | {} | NONE |
vuejs | core | 1,881,648,310 | 10,038 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34.1 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-08T18:54:24 | 2024-01-08T18:54:24 | {} | NONE |
vuejs | core | 1,879,745,297 | 10,024 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.6 kB (**+58 B**) | 34.1 kB (**+22 B**) | 30.7 kB (**+32 B**) |
... | 2024-01-06T16:26:37 | 2024-01-09T03:42:49 | {} | NONE |
vuejs | core | 1,882,541,293 | 9,991 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/7457921370)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/7443374236) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/745... | 2024-01-09T07:32:08 | 2024-01-09T07:32:08 | {} | CONTRIBUTOR |
vuejs | core | 1,882,834,517 | 10,044 | major-mayer | Crazy, soo fast :astonished: Thanks a lot!
I was scratching my head so hard yesterday, wondering where in the migration process I made the fault.
I already debated if I should really report it or if it was just my stupidity, but apparently it made sense ^^ | 2024-01-09T10:44:55 | 2024-01-09T10:44:55 | {} | NONE |
vuejs | core | 1,882,975,018 | 10,050 | edison1105 | duplicate of #5256 | 2024-01-09T12:21:45 | 2024-01-09T12:21:45 | {} | MEMBER |
vuejs | core | 1,883,233,562 | 10,054 | yyx990803 | Even if we include the banner in dist files, bundlers are not guaranteed to preserve them. This is not something we can enforce so like you said, this is probably not the place to discuss that. | 2024-01-09T15:12:03 | 2024-01-09T15:12:03 | {} | MEMBER |
vuejs | core | 1,879,794,326 | 9,989 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-06T19:24:38 | 2024-01-06T19:24:38 | {} | NONE |
vuejs | core | 1,880,299,548 | 10,030 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.4 kB | 34 kB | 30.7 kB |
| vue.global.prod.js | 146 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2024-01-08T02:12:26 | 2024-01-08T02:12:26 | {} | NONE |
vuejs | core | 1,881,667,696 | 6,643 | NathanAP | This is really problematic, just lost 2 hours trying to do something really easy, but using `generic components` with `defineExpose` is impossible right now. We need a fix.
#4397 was closed and had no solution. | 2024-01-08T19:08:25 | 2024-01-08T19:25:10 | {
"+1": 1
} | NONE |
vuejs | core | 1,882,018,635 | 10,038 | jacekkarczmarczyk | Shouldn't computed setter be checked as well? | 2024-01-09T00:11:28 | 2024-01-09T00:11:28 | {} | CONTRIBUTOR |
vuejs | core | 1,882,757,884 | 9,370 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c011f34db42f51f7dd21c9124f3a585b9135d7b4 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-01-09T09:59:52 | 2024-01-09T09:59:52 | {} | NONE |
vuejs | core | 1,882,782,009 | 10,044 | yyx990803 | fixed by 923d560d0 (out in 3.4.7) | 2024-01-09T10:14:03 | 2024-01-09T10:15:42 | {
"hooray": 2
} | MEMBER |
vuejs | core | 1,883,016,972 | 9,783 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d5fe8ba60f8dc7a0fffa4d0fe7a185889fd4286a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-01-09T12:52:59 | 2024-01-09T12:52:59 | {} | NONE |
vuejs | core | 1,883,216,574 | 10,050 | yyx990803 | > I tend to disagree @yyx990803. In my "large" application, the `v-for` iterates on some dynamic user input elements. Because of these detached elements, the memory increases and increases indefinitely.
I'm speaking specifically about this reproduction. If you have a memory leak case, please provide a reproduction. ... | 2024-01-09T15:03:12 | 2024-01-09T15:03:12 | {} | MEMBER |
vuejs | core | 1,883,227,327 | 10,054 | Disservin | Yes, but users who use vue, will end up without a license in their js code . The end customer who visits the users webpage doesnt know about npm and certainly cant tell from the minified code that it's vue (or any other package).
So right now essentially every vue user is missing license information about vue in thei... | 2024-01-09T15:08:47 | 2024-01-09T15:08:47 | {} | CONTRIBUTOR |
vuejs | core | 1,880,309,540 | 10,006 | zlx1134558955 | I encounter the same thing. | 2024-01-08T02:32:42 | 2024-01-08T02:32:42 | {} | NONE |
vuejs | core | 1,881,876,237 | 10,014 | 4refael | Appreciate the input @LinusBorg. I actually forgot v-model supports objects as a value.
A different strategy could be using a Set to track the indexes of selected options, rather than their values.
I've tested and seems to work fine, it even simplifies my previous implementation.
Possibly there are more edge-cases... | 2024-01-08T21:50:06 | 2024-01-08T21:50:06 | {} | NONE |
vuejs | core | 1,881,876,269 | 10,039 | thinlizzy | I am literally using this:
```
<script type="importmap">
{
"imports": {
"vue": "https://unpkg.com/vue@3/dist/vue.esm-browser.js"
}
}
</script>
``` | 2024-01-08T21:50:07 | 2024-01-08T21:50:07 | {} | NONE |
vuejs | core | 1,882,532,749 | 10,041 | yyx990803 | Closing, I don't think this is the right fix. | 2024-01-09T07:23:34 | 2024-01-09T07:23:34 | {} | MEMBER |
vuejs | core | 1,770,819,090 | 9,431 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34.1 kB | 30.7 kB |
| vue.global.prod.js | 147 kB | 53.3 kB | 47.6 kB |
### Usages
| Name | Size |... | 2023-10-19T12:09:29 | 2024-01-09T09:39:10 | {} | NONE |
vuejs | core | 1,882,757,881 | 9,370 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c011f34db42f51f7dd21c9124f3a585b9135d7b4 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2024-01-09T09:59:52 | 2024-01-09T09:59:52 | {} | NONE |
vuejs | core | 1,883,535,626 | 10,039 | LinusBorg | You're right insofar as the handling of the defaults happens in the build tool integrations, and Parcel's vue integration is not maintained by us. (You also don't find a Parcel section on our docs.
We can likely amend the docs in that regard.
Still, no related to this issue here. | 2024-01-09T18:02:00 | 2024-01-09T18:02:22 | {} | MEMBER |
vuejs | core | 1,884,159,972 | 10,060 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.5 kB | 34.1 kB | 30.7 kB |
| vue.global.prod.js | 147 kB | 53.3 kB | 47.7 kB |
### Usages
| Name | Size |... | 2024-01-10T04:07:44 | 2024-01-10T04:07:44 | {} | NONE |
vuejs | core | 2,144,371,135 | 11,059 | edison1105 | - The `afterLeave` here is meant to render `page2` to the container after the transition of `page1` has ended. This `afterLeave` only needs to be executed once. Therefore, I believe the correct fix should be:
```js
activeBranch!.transition!.afterLeave = () => {
// ....
// remove afterLeave
activeBranch!.tr... | 2024-06-03T06:24:27 | 2024-06-03T13:54:31 | {} | MEMBER |
vuejs | core | 2,145,724,974 | 11,060 | LinusBorg | This is expected. Slots in Vue 3 now always behave like scoped slots in Vue 2 - meaning the child will only update when the slot content changed.
You can check out the Migration guide for details | 2024-06-03T17:09:38 | 2024-06-03T17:09:38 | {} | MEMBER |
vuejs | core | 1,729,670,842 | 8,545 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.9 kB | 34.6 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size |... | 2023-09-21T14:13:46 | 2024-05-30T13:21:21 | {} | NONE |
vuejs | core | 2,144,116,272 | 10,575 | edison1105 | Close as duplicate | 2024-06-03T01:23:58 | 2024-06-03T01:23:58 | {} | MEMBER |
vuejs | core | 2,146,936,050 | 9,219 | yyx990803 | Closing in favor of https://github.com/vuejs/core/pull/11067 | 2024-06-04T08:35:54 | 2024-06-04T08:35:54 | {} | MEMBER |
vuejs | core | 2,146,944,476 | 11,049 | haoqunjiang | `execa` is mostly used in build and release scripts, which are not covered by tests, so we need to deal it with more caution. Let me finish reading all the release notes before merging this PR. | 2024-06-04T08:40:03 | 2024-06-04T08:40:28 | {} | MEMBER |
vuejs | core | 2,146,978,711 | 11,066 | edison1105 | /ecosystem-ci run | 2024-06-04T08:56:21 | 2024-06-04T08:56:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,148,464,762 | 4,404 | EranGrin | The latest version of https://www.npmjs.com/package/vue-web-component-wrapper can now generate vue web component
**without Shadow DOM** with slots and name slots and nested web-component
Here is the demo of web component **without shadow DOM**
https://stackblitz.com/~/github.com/EranGrin/web-component-no-shadow-dom-... | 2024-06-04T21:43:56 | 2024-06-04T21:43:56 | {
"-1": 1
} | NONE |
vuejs | core | 2,148,907,971 | 11,072 | edison1105 | duplicate of https://github.com/vuejs/core/issues/7334, https://github.com/vuejs/core/issues/6080, will be fixed by #7387 or #6238 | 2024-06-05T05:47:57 | 2024-06-05T05:52:58 | {} | MEMBER |
vuejs | core | 2,141,051,268 | 6,429 | skirtles-code | Looks good to me. Might be worth adding a test for this scenario to `directives.spec.ts`.
The original bug report was about webpack and compiler-generated code, but I believe this type change would also be useful when writing render functions directly with `"strict": true`. e.g. [Playground](<https://play.vuejs.org/... | 2024-05-31T00:40:57 | 2024-05-31T00:40:57 | {} | CONTRIBUTOR |
vuejs | core | 2,141,422,432 | 8,639 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9314767454)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9313156194) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-05-31T07:54:28 | 2024-05-31T07:54:28 | {} | CONTRIBUTOR |
vuejs | core | 2,143,674,791 | 7,247 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9335065724)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9313156194) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-06-02T02:45:39 | 2024-06-02T02:45:39 | {} | CONTRIBUTOR |
vuejs | core | 2,143,771,584 | 7,745 | edison1105 | /ecosystem-ci run | 2024-06-02T09:30:21 | 2024-06-02T09:30:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,146,664,977 | 11,065 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 91 kB | 34.6 kB | 31.2 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-06-04T05:50:07 | 2024-06-04T05:50:07 | {} | NONE |
vuejs | core | 2,147,254,033 | 11,067 | yyx990803 | /cc @huang-julien
Nuxt has one test case failing here https://github.com/vuejs/ecosystem-ci/actions/runs/9365657120/job/25781312030#step:7:1279 because there are no longer `pushScopeId` calls for hoisted nodes. I think line 118 and 121 can be removed. | 2024-06-04T11:05:55 | 2024-06-04T11:05:55 | {
"eyes": 1
} | MEMBER |
vuejs | core | 2,147,374,441 | 8,412 | Disservin | I think all of this is related to how vue has difficulties with resolving the types properly evan talked about this in some other issues or pr's iirc.
I seem to have deleted my reproduction repository some time ago, since this issue is now missing a reproduction feel free to post a reproduction for the case where usi... | 2024-06-04T12:08:56 | 2024-06-04T12:08:56 | {} | CONTRIBUTOR |
vuejs | core | 2,142,452,106 | 11,036 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9320085378)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9313156194) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-05-31T14:59:46 | 2024-05-31T14:59:46 | {} | CONTRIBUTOR |
vuejs | core | 2,143,773,926 | 7,745 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9337257704)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9313156194) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/933... | 2024-06-02T09:37:32 | 2024-06-02T09:37:32 | {} | CONTRIBUTOR |
vuejs | core | 2,144,117,932 | 11,057 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 91 kB | 34.6 kB | 31.2 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-06-03T01:26:20 | 2024-06-03T01:26:20 | {} | NONE |
vuejs | core | 2,141,358,708 | 11,046 | edison1105 | 用户可以很简单的解决这个问题： `const tag = '"张三"';`
如果进行特殊处理，可能会是一个 breaking change, 因为有些用户可能已经 `'"张三"'` 这么做了。 | 2024-05-31T07:06:28 | 2024-05-31T07:06:29 | {} | MEMBER |
vuejs | core | 2,142,149,551 | 11,036 | jh-leong | To address the issue at the type level, reactive array and normal arrays must be differentiated in the watch API type inference.
Currently, the code can't distinguish between them, as shown below:
```ts
// Both are inferred as Ref<number>[]
const arr1 = [ref(1)]
const arr2 = reactive(arr1)
```
To solve th... | 2024-05-31T13:18:33 | 2024-05-31T13:18:33 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,142,347,403 | 3,077 | yyx990803 | As of 3.4 types for props with `default: undefined` are handled as expected. | 2024-05-31T14:24:54 | 2024-05-31T14:24:54 | {} | MEMBER |
vuejs | core | 2,142,348,326 | 3,081 | yyx990803 | As of 3.4 types for props with default: undefined are handled as expected. | 2024-05-31T14:25:09 | 2024-05-31T14:25:09 | {} | MEMBER |
vuejs | core | 2,142,798,314 | 11,049 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 91 kB | 34.6 kB | 31.2 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-05-31T18:39:38 | 2024-05-31T18:39:38 | {} | NONE |
vuejs | core | 2,142,909,394 | 8,952 | TheAlexLichter | > This is a type restriction of defineComponent, as a current solution you can use generic. This will bypass defineComponent and define the component as a functional component.
>
> ```
> <script setup lang="ts" generic="T">
> interface CommonProps {
> size?: 'xl' | 'l' | 'm' | 's' | 'xs'
> }
> // ...
> </scr... | 2024-05-31T20:05:58 | 2024-05-31T20:05:58 | {} | NONE |
vuejs | core | 2,143,858,544 | 11,053 | roberthand9 | I'm using suspense and allow errors in async child components to bubble to the parent component where they're handled by an onErrorCaptured hook. There's a check to see if the source of the error is a setup function as that's where I would expect any 'expected' errors to be thrown e.g. api request failed - I can then r... | 2024-06-02T13:40:38 | 2024-06-02T13:40:38 | {} | NONE |
vuejs | core | 2,143,943,660 | 7,745 | skirtles-code | > It only logs twice for now, maybe that already fixed via some commits.
Good point.
I did some digging... this is a bit difficult to explain, but I'll try my best.
`invalidateJob` still contains the original bug, that hasn't been fixed on `main`. The test case I added still fails on `main` and passes with my ... | 2024-06-02T17:00:59 | 2024-06-02T17:00:59 | {} | CONTRIBUTOR |
vuejs | core | 2,147,181,171 | 8,368 | nbennke | Is there any update in progress, solving this issue? We're also faced with this error preventing us to upgrade `vue` beyond `v3.2.47` in our project using `vue` and `coffeescript` together. | 2024-06-04T10:28:49 | 2024-06-04T10:28:49 | {
"+1": 2
} | NONE |
vuejs | core | 2,140,600,641 | 9,783 | skirtles-code | @xvaara I'm not sure exactly what problem you're having, but based on the example you gave I don't think this PR will fix it. This change only impacts cases where `disabled` is `false` and the `to` is `null`/`undefined`, which doesn't seem to be what you're describing. | 2024-05-30T18:32:57 | 2024-05-30T18:32:57 | {} | CONTRIBUTOR |
vuejs | core | 2,141,243,212 | 5,312 | jd1378 | with a combination of `<!-- @vue-expect-error -->`, `<!-- @vue-skip -->`, and using `defineSlots` on both of my parent and child components I managed to get the types and ignore the errors | 2024-05-31T05:10:57 | 2024-05-31T05:10:57 | {} | NONE |
vuejs | core | 2,142,511,518 | 4,778 | bobvandevijver | This can be achieved with `app.runWithContext(() => inject('myVar'))`, so this issue can be closed. | 2024-05-31T15:33:15 | 2024-05-31T15:33:15 | {
"+1": 1
} | NONE |
vuejs | core | 2,142,564,940 | 9,370 | yyx990803 | /ecosystem-ci run | 2024-05-31T16:05:58 | 2024-05-31T16:05:58 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,143,481,865 | 11,051 | skirtles-code | For anyone else wondering, I believe the point of this change is to allow for code like this:
```js
onUpdated(() => {
onMounted(() => {
console.log('here')
})
})
```
In this scenario, the callback would be called immediately as the component is already mounted. I would imagine that the intended use ... | 2024-06-01T15:11:48 | 2024-06-01T15:11:48 | {} | CONTRIBUTOR |
vuejs | core | 2,143,522,638 | 11,038 | Joebayld | > I accessed here and was able to see the problem happening. Below is a screenshot:
>
> 
>
>
Yeah that's the issue. Seems to be a vue bug. | 2024-06-01T17:28:14 | 2024-06-01T17:28:14 | {} | NONE |
vuejs | core | 2,143,771,076 | 7,745 | edison1105 | >[SFC Playground](https://sfc.vuejs.org/#eNqdU02PmzAQ/SsjSxWsNoFVjyhErXLoqdLe6x4IGRK2YFu2ybZC/PeObZaQZJX9uCTMB2/ezHv07LtSybFDlrGVKXWtLBi0nVpzUbdKags9aKxggErLFiJqjabSz3+bQ93sxlKSjrHDOzX1sG/ktmg2shN2wklSY6XG5MlQJwAXVSdKW0sBVhfln/gOepcvpTCywaSR+zh6LDQSBP3sUNdiH91xMXCxSgNxokyBxVY1hUWKAFYvDDM8osg5m1P5Al8hz3N44AzSNfT9NHrwqBM... | 2024-06-02T09:28:28 | 2024-06-02T09:28:28 | {} | MEMBER |
vuejs | core | 2,146,993,429 | 11,066 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9364179654)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9344510539) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-06-04T09:03:17 | 2024-06-04T09:03:17 | {} | CONTRIBUTOR |
vuejs | core | 2,141,007,033 | 5,717 | skirtles-code | I'm not sure that the fix proposed here is correct, but I do agree that there's a problem.
In theory, we have this warning:
https://github.com/vuejs/core/blob/f8994da00f523d5d792997671f4f55eca43d6598/packages/runtime-core/src/componentPublicInstance.ts#L414-L419
In practice, it's quite difficult to hit that wa... | 2024-05-30T23:39:55 | 2024-05-30T23:39:55 | {} | CONTRIBUTOR |
vuejs | core | 2,141,975,418 | 9,403 | RodrigoProjects | Will this be merged in the next minor? This problem is making it very hard to predict if each deploy we do as a problem or not! | 2024-05-31T12:26:03 | 2024-05-31T12:26:03 | {} | CONTRIBUTOR |
vuejs | core | 2,142,528,208 | 6,859 | yyx990803 | As of latest Chrome, this is no longer reproducible. | 2024-05-31T15:43:27 | 2024-05-31T15:43:27 | {} | MEMBER |
vuejs | core | 2,143,523,071 | 11,052 | catcoon33 | I suggest you write like this ```h('div', {}, `Preview: ${inputValue.value}`),``` | 2024-06-01T17:29:47 | 2024-06-01T17:29:47 | {} | NONE |
vuejs | core | 2,143,533,722 | 11,052 | drozdzynski | > I suggest you write like this `` h('div', {}, `Preview: ${inputValue.value}`), ``
I used `h` only in the example to reproduce the issue, I found this issue when using TSX/JSX:
```
<div>Preview: {inputValue.value}</div>
``` | 2024-06-01T18:03:25 | 2024-06-01T18:03:25 | {} | NONE |
vuejs | core | 2,143,789,100 | 11,053 | edison1105 | Is your codebase dependent on error codes? I think this way, users can quickly navigate to the error code page.
Perhaps the documentation needs to be updated to avoid causing confusion for users. | 2024-06-02T10:20:34 | 2024-06-02T10:20:34 | {} | MEMBER |
vuejs | core | 2,144,252,706 | 11,048 | yyx990803 | This is server-side code so we are not limited to ES2015 but more like what is supported in latest Node LTS. dotAll seems to have been supported in Node since version 8 so I don't think this is necessary? | 2024-06-03T04:26:58 | 2024-06-03T04:26:58 | {} | MEMBER |
vuejs | core | 2,139,918,114 | 8,533 | yyx990803 | Agreed | 2024-05-30T15:21:04 | 2024-05-30T15:21:04 | {} | MEMBER |
vuejs | core | 2,141,412,679 | 8,639 | edison1105 | /ecosystem-ci run | 2024-05-31T07:47:29 | 2024-05-31T07:47:29 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,143,031,266 | 4,874 | vallemar | @LinusBorg This would be quite useful for custom renderers. In these cases we can create an application in each navigation, modals or any other flow in which you need to inject a component into a new native view. The proposed solutions do not work with `ref`.
Of course this is not something that is used on the fro... | 2024-05-31T21:57:44 | 2024-05-31T22:49:38 | {} | NONE |
vuejs | core | 2,143,991,989 | 10,575 | skirtles-code | #6765 has now been merged. The fix and test in that PR are slightly different from those found here. I'm unclear whether this PR is still worth pursuing, but it will need the conflicts resolving if it is. | 2024-06-02T19:15:11 | 2024-06-02T19:15:11 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 2,144,967,360 | 4,314 | EranGrin | The latest version of https://www.npmjs.com/package/vue-web-component-wrapper can now generate vue web component
without **Shadow DOM** with slots and name slots | 2024-06-03T11:34:48 | 2024-06-03T11:36:02 | {
"eyes": 1,
"hooray": 3
} | NONE |
vuejs | core | 2,146,911,996 | 9,559 | leookun | This is because components are created by functions, and if this is the case for you, you should use closures in your functions to cache the created components
<img width="976" alt="image" src="https://github.com/vuejs/core/assets/131544788/82b95482-2372-4895-ad74-3c13fed3d129">
<img width="882" alt="image" src="http... | 2024-06-04T08:24:15 | 2024-06-04T08:24:15 | {} | NONE |
vuejs | core | 2,140,366,749 | 11,041 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.9 kB | 34.6 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-05-30T17:23:52 | 2024-05-30T17:23:52 | {} | NONE |
vuejs | core | 2,141,316,773 | 5,666 | yxw007 |
> ### Version
> 3.2.31
>
> ### Reproduction link
> [github.com](https://github.com/lloydjatkinson/bug-report-2)
>
> ### Steps to reproduce
> Using Vue CLI create a Vue 3 + TS(X) project.
>
> Create a component with the following where `as` is a string prop:
>
> ```tsx
> render () {
> co... | 2024-05-31T06:29:27 | 2024-05-31T06:29:27 | {} | NONE |
vuejs | core | 2,142,673,240 | 8,952 | occitaneUbald | > This is a type restriction of defineComponent, as a current solution you can use generic. This will bypass defineComponent and define the component as a functional component.
>
> ```
> <script setup lang="ts" generic="T">
> interface CommonProps {
> size?: 'xl' | 'l' | 'm' | 's' | 'xs'
> }
> // ...
> </scr... | 2024-05-31T17:14:38 | 2024-05-31T17:14:38 | {} | NONE |
vuejs | core | 2,144,230,483 | 9,451 | StrikeAgainst | Just FYI, I had to learn the hard way that this does NOT work with index / key values from list renderings.
`<component v-for="(entry, key) in list" :key ... />` will instead re-render your whole list on any update. You'll have to stick with `:key="key"`. | 2024-06-03T03:59:18 | 2024-06-03T03:59:18 | {} | NONE |
vuejs | core | 2,141,089,486 | 6,752 | skirtles-code | I suspect this may have the same underlying cause as #6080.
Here's a [Playground](<https://play.vuejs.org/#eNp9kk1vEzEQhv/K4EtB6u4iAZewjYCqIJD4EHD0xWxmE7de27Jnt4mi/HfG9iZppao3z8zzjsevZy8+el9PI4qFaGMXtCeISKNfSqsH7wLBHgL2cIA+uAEuGL04lb7vrjfarOZS3cxx6seQtJ2zkftt3D1cpS4ve2UivpK2bcpdfAsHhIM3ipAjgPbfSOQsfOiM7u6upJjlFEaUYv... | 2024-05-31T01:36:30 | 2024-05-31T01:36:30 | {} | CONTRIBUTOR |
vuejs | core | 2,142,438,394 | 11,036 | Alfred-Skyblue | /ecosystem-ci run | 2024-05-31T14:52:32 | 2024-05-31T14:52:32 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,144,478,158 | 11,053 | LinusBorg | > I don't see why you wouldn't want to pass in the code as it's described
Providing not just the code, but an URL to a description of the code is better DX as developers who might have been unaware of that page in the docs which is providing these explanations of error codes can directly jump there instead of wonde... | 2024-06-03T07:33:37 | 2024-06-03T07:33:37 | {
"+1": 4
} | MEMBER |
vuejs | core | 2,146,842,477 | 11,061 | edison1105 | - the second one ~~never works on 3.4.x~~ duplicate of #4933 will be fixed by https://github.com/vuejs/core/pull/4941, see [playground](https://deploy-preview-4941--vue-sfc-playground.netlify.app/#eNqFVMGO2jAQ/ZWpL0kkGg7tCQHt7opKraq26nJbc8iGCTEYO7IdSoX49x3bwGZ3gc0hsj1vnt/Yb7xjN02Tb1pkAza0pRGNA4uubcZciXWjjYMdTE2hrHBCqx7... | 2024-06-04T07:48:47 | 2024-06-04T09:10:36 | {} | MEMBER |
vuejs | core | 1,820,383,975 | 8,533 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.9 kB | 34.6 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size |... | 2023-11-21T07:39:36 | 2024-05-30T10:20:03 | {} | NONE |
vuejs | core | 2,139,600,613 | 8,533 | sxzz | We should at least report a warning if users do that. | 2024-05-30T13:48:56 | 2024-05-30T13:48:56 | {} | MEMBER |
vuejs | core | 2,142,797,948 | 11,050 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 91 kB | 34.6 kB | 31.2 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-05-31T18:39:20 | 2024-05-31T18:39:20 | {} | NONE |
vuejs | core | 2,142,798,328 | 11,049 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 4b22123c9bb3d7b6cee7be7806b59edce9fc3a1d |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-05-31T18:39:38 | 2024-05-31T18:39:38 | {} | NONE |
vuejs | core | 2,144,118,120 | 11,058 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 91 kB | 34.6 kB | 31.2 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-06-03T01:26:35 | 2024-06-03T01:26:35 | {} | NONE |
vuejs | core | 2,144,414,035 | 9,451 | kissu | > Just FYI, I had to learn the hard way that this does NOT work with index / key values from list renderings. `<component v-for="(entry, key) in list" :key ... />` will instead re-render your whole list on any update. You'll have to stick with `:key="key"`.
If the `key` here is an index of an array it might not be t... | 2024-06-03T06:55:30 | 2024-06-03T06:55:30 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.