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,273,104,962 | 11,442 | sxzz | https://github.com/vuejs/core/pull/8543#pullrequestreview-1473634506
I noticed this PR was merged into main instead of minor. This may require TS > 5.1 in the next patch, so we should move it to minor. | 2024-08-07T10:06:35 | 2024-08-07T10:06:35 | {} | MEMBER |
vuejs | core | 2,268,762,071 | 11,516 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.1 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 147 kB | 54 kB | 48 kB |
### Usages
| Name | Size |... | 2024-08-05T10:42:04 | 2024-08-05T10:42:04 | {} | NONE |
vuejs | core | 2,270,769,584 | 11,522 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | --------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 97.6 kB (**+7.5 kB**) | 37.1 kB (**+2.53 kB**) | 3... | 2024-08-06T09:05:23 | 2024-08-06T09:05:23 | {} | NONE |
vuejs | core | 2,271,880,239 | 9,341 | yyx990803 | closed via 37ccb9b9a (to be released in 3.5) | 2024-08-06T18:19:31 | 2024-08-06T18:19:31 | {} | MEMBER |
vuejs | core | 2,271,936,405 | 9,006 | yyx990803 | closed via 63689ed77 (to be released in 3.5) | 2024-08-06T18:52:05 | 2024-08-06T18:52:05 | {} | MEMBER |
vuejs | core | 2,272,593,904 | 10,444 | yyx990803 | fixed via 37ccb9b9a | 2024-08-07T04:27:43 | 2024-08-07T04:27:43 | {} | MEMBER |
vuejs | core | 2,272,883,747 | 4,356 | yyx990803 | Closed via https://github.com/vuejs/core/commit/6758c3cd0427f97394d95168c655dae3b7fa62cd | 2024-08-07T08:12:40 | 2024-08-07T08:12:40 | {
"hooray": 3
} | MEMBER |
vuejs | core | 2,273,474,299 | 11,442 | yyx990803 | @jh-leong I've reverted this and #11536 in the `main` branch so we avoid accidentally raising TS version requirements in 3.4.
`minor` branch has merged `main` with both this and #11442 applied so they will be part of 3.5. | 2024-08-07T13:27:02 | 2024-08-07T13:27:02 | {
"+1": 2,
"rocket": 1
} | MEMBER |
vuejs | core | 2,271,732,839 | 11,496 | kakkokari-gtyih | Netlify keeps failing... Are there other PRs affected? | 2024-08-06T16:55:15 | 2024-08-06T16:55:34 | {} | CONTRIBUTOR |
vuejs | core | 2,271,883,407 | 9,351 | yyx990803 | Superseded by 37ccb9b9a which is based on this PR and reuses tests from this PR. Thanks! | 2024-08-06T18:21:19 | 2024-08-06T18:21:19 | {} | MEMBER |
vuejs | core | 2,272,414,656 | 11,533 | edison1105 | @Procrustes5
PR welcome~ | 2024-08-07T00:47:41 | 2024-08-07T00:47:41 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,272,573,038 | 11,530 | yyx990803 | This looks good, I'm merging this so we get it out in 3.5 beta.1 to avoid an API change during the beta phase. We can still make further adjustments during beta. | 2024-08-07T04:05:43 | 2024-08-07T04:06:01 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,272,590,102 | 4,476 | yyx990803 | I don't think this feature should be supported because:
- Real custom elements should not assume or be coupled to the parent framework it is being used in.
- Custom elements are considered normal DOM elements from Vue's perspective.
The separation between the two is quite clear and I don't believe it's a good id... | 2024-08-07T04:22:53 | 2024-08-07T04:22:53 | {} | MEMBER |
vuejs | core | 2,270,827,846 | 11,521 | Disservin | > > However, there's a drawback that the Component which exposes the `item` slot still see's a slot being passed, which I wouldn't expect since the `v-if` condition is false.
> > [Vue Playground](https://play.vuejs.org/#eNqtUk1P4zAQ/Suz3kNYiU2FunvptqDdFQc4AAKOllCUTorBsSN/hEpR/jtjO0mLBD0gbuN5b8Yz817H/jZN3npkC7a0pRGNA4v... | 2024-08-06T09:32:04 | 2024-08-06T09:32:04 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,272,529,727 | 11,496 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------ |
| runtime-dom.global.prod.js | 90.1 kB (**+4 B**) | 34.6 kB (**+2 B**) | 31.1 kB (**+4 B**) |
| vue.glo... | 2024-08-07T03:07:46 | 2024-08-07T03:07:46 | {} | NONE |
vuejs | core | 2,268,988,604 | 11,517 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ---------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 97.6 kB (**+7.46 kB**) | 37.1 kB (**+2.52 kB**) ... | 2024-08-05T12:44:38 | 2024-08-05T12:44:38 | {} | NONE |
vuejs | core | 2,269,204,455 | 9,380 | Zheng-Changfu | It still hasn't been solved? | 2024-08-05T14:23:08 | 2024-08-05T14:23:08 | {} | NONE |
vuejs | core | 2,272,463,767 | 11,536 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.1 kB | 34.6 kB | 31.1 kB |
| vue.global.prod.js | 147 kB | 54 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-08-07T01:47:57 | 2024-08-07T01:47:57 | {} | NONE |
vuejs | core | 2,272,557,777 | 11,538 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 90.2 kB (**+10 B**) | 34.6 kB (**+2 B**) | 31.1 kB (**-5 B**) |
| v... | 2024-08-07T03:45:04 | 2024-08-07T03:45:04 | {} | NONE |
vuejs | core | 2,273,090,557 | 11,543 | edison1105 | > The logic of haschange should judge the custom setter and getter together.
I think the logic that determines whether a change is made cannot use `emittedValue`, it should use the value passed in.
https://github.com/vuejs/core/issues/11526 should not be a bug.
| 2024-08-07T09:59:20 | 2024-08-07T09:59:20 | {} | MEMBER |
vuejs | core | 2,273,475,533 | 11,533 | matej-svejda | Thank you for the quick turnaround 🙂 But this doesn't seem to fix the case with directives and Teleport for which I provided the example ([this one](https://play.vuejs.org/#eNqtVNtu20YQ/ZUtUSBUYVNW2idWNpoYBtqiaIvEjwsUNDkSN17tErtDSYbhf++ZJakbgjzlxRbncnYuZ85r9qHrim1PWZktYx1MxyoS992ddmbT+cDqVQVaqTe1Cn6j3iH0nXba1d5FVttPVF... | 2024-08-07T13:27:33 | 2024-08-07T13:27:33 | {
"eyes": 1
} | NONE |
vuejs | core | 2,273,483,656 | 11,544 | yyx990803 | I think it's still nice to enforce consistency since some commits on `minor` don't go through PRs. | 2024-08-07T13:31:04 | 2024-08-07T13:31:04 | {} | MEMBER |
vuejs | core | 2,273,581,482 | 11,548 | cnzgray | I just checked the [type definition of UnwrapRef](https://github.com/vuejs/core/blob/b1abac06cdb198bd72f8e614b1f68b92e1c78339/packages/reactivity/src/ref.ts#L527C33-L527C48) and found it strange. Why is it defined as `UnwrapRefSimple` instead of the following `UnwrapRef`?
```
T extends ReadonlyArray<any>
... | 2024-08-07T14:14:01 | 2024-08-07T14:14:01 | {} | NONE |
vuejs | core | 2,270,647,597 | 10,799 | Gehbt | Explicitly type will cover type infer, it is better to set type for initialize value.
`const initalizedAsEmpty = ref(undefined as DefAsInterface | undefined)` | 2024-08-06T08:08:21 | 2024-08-06T08:08:21 | {} | CONTRIBUTOR |
vuejs | core | 2,271,174,778 | 11,525 | pbgcommits | Thanks for the quick response time! Glad to see this has been fixed already :) | 2024-08-06T12:29:40 | 2024-08-06T12:29:40 | {} | NONE |
vuejs | core | 2,271,226,289 | 11,527 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 5e3e2dd64b2b8e73724ed420c38820642491a168 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-08-06T12:55:47 | 2024-08-06T12:55:47 | {} | NONE |
vuejs | core | 2,272,031,885 | 11,442 | mefcorvi | @jh-leong After some thought, I conclude that something is indeed broken. Now, it is possible to have code like this, which is correct from a types standpoint but obviously broken. Consider this example:
```typescript
const b = ref(ref(1));
console.log(b.value.toFixed()); // 1
b.value = ref(2);
console.log(b.value... | 2024-08-06T19:51:15 | 2024-08-06T20:56:39 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,272,464,667 | 11,536 | jh-leong | /ecosystem-ci run | 2024-08-07T01:49:03 | 2024-08-07T01:49:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,272,484,909 | 11,537 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.2 kB (**+63 B**) | 34.6 kB (**+19 B**) | 31.2 kB (**+16 B**) |
... | 2024-08-07T02:11:44 | 2024-08-07T02:48:38 | {} | NONE |
vuejs | core | 2,272,584,453 | 7,497 | yyx990803 | closed via 63689ed | 2024-08-07T04:15:57 | 2024-08-07T04:15:57 | {} | MEMBER |
vuejs | core | 2,272,834,850 | 11,541 | TheFlyer1983 | But this feels like a breaking change, because this worked in Vue 3.4.16, and was broken in a patch update between 3.4.16 and 3.4.36.
It originally worked as I expected it to work, and now has broken many instances in my application because of this change. | 2024-08-07T07:45:52 | 2024-08-07T07:46:24 | {} | NONE |
vuejs | core | 2,272,849,974 | 11,541 | edison1105 | related [PR](https://github.com/vuejs/core/pull/11162) | 2024-08-07T07:54:45 | 2024-08-07T07:54:45 | {} | MEMBER |
vuejs | core | 2,272,868,680 | 11,541 | TheFlyer1983 | But surely how it used work was consistent with how `set` function worked in a writeable computed property?
If you select the same value via a writeable computed property it runs the set function regardless. The defineModel should really work the same way. | 2024-08-07T08:04:52 | 2024-08-07T08:04:52 | {} | NONE |
vuejs | core | 2,268,718,612 | 11,515 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.1 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 147 kB | 54 kB | 48 kB |
### Usages
| Name | Size |... | 2024-08-05T10:18:29 | 2024-08-05T10:18:29 | {} | NONE |
vuejs | core | 2,270,864,392 | 11,523 | liukhelloworld | > This is expected behavior, see https://vuejs.org/guide/components/props.html#boolean-casting
明白了,thanks! | 2024-08-06T09:49:54 | 2024-08-06T09:49:54 | {} | NONE |
vuejs | core | 2,272,522,405 | 11,536 | Alfred-Skyblue | Sorry, I didn't notice that you already submitted a PR. I just created #11537. I found that in your PR, you modified the type, but the issue causing #11532 is because when we set a value to a ref, it leads to `this._value = ref(xxx)`, and we didn't unwrap it in the getter. So, this caused the problem in #11532. | 2024-08-07T02:58:43 | 2024-08-07T02:58:43 | {} | MEMBER |
vuejs | core | 2,272,591,304 | 4,511 | yyx990803 | Closing as duplicate / subset of #4635 | 2024-08-07T04:24:25 | 2024-08-07T04:24:25 | {} | MEMBER |
vuejs | core | 2,531,465,669 | 12,522 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-10T12:11:38 | 2024-12-10T12:11:38 | {} | NONE |
vuejs | core | 2,531,482,344 | 12,522 | KazariEX | Also `v-text`. | 2024-12-10T12:18:58 | 2024-12-10T12:18:58 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,531,465,996 | 12,522 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/6c1a95be-10d5-4c27-b805-f396a38c399d)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12522
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-10T12:11:47 | 2024-12-10T12:33:47 | {} | NONE |
vuejs | core | 2,538,480,048 | 12,536 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/8fd8cce0-c7d5-439f-88ff-c15c64ac6401)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12536
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-12T10:25:23 | 2024-12-12T10:25:23 | {} | NONE |
vuejs | core | 2,556,429,709 | 12,520 | Gwynerva | @Ghosterbeef provide a link to an example in [Vue SFC Playground](https://play.vuejs.org/#__SSR__eNp9ks1uwjAQhF9l5YtbCcGhPaWBqlRIpeqfCre6hxA2wZDYke1QJJR379ohwAFxyu7MZP155T17qqr+tkYWsdimRlYOLLq6Ggkly0obB3tYQQOZ0SVwCvIHoYRKtbIOpB0XOt3AEJypkYxWnic5Saubzn4EvpRbDhFwWyWK92imVArNy/z9jcSY3NHUCxBbZ7TKR96JB4cmHvgAh+aWjiA1YBIgNQ7... | 2024-12-20T07:21:53 | 2024-12-20T07:22:46 | {} | NONE |
vuejs | core | 2,556,467,281 | 12,583 | xvvhang | duplicated: https://github.com/vuejs/create-vue/issues/641 and it looks like this should be fixed in vuejs/create-vue. more detail: https://github.com/vuejs/create-vue/blob/93223adec18b203e3d474aeceea03e623f7ed765/index.ts#L353 | 2024-12-20T07:54:07 | 2024-12-20T07:54:07 | {} | NONE |
vuejs | core | 2,558,742,499 | 12,594 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-23T01:45:21 | 2024-12-23T01:45:21 | {} | NONE |
vuejs | core | 2,558,742,803 | 12,595 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.... | 2024-12-23T01:45:32 | 2024-12-23T01:45:32 | {} | NONE |
vuejs | core | 2,543,541,865 | 8,512 | Mini-ghost | Starting from version 0.18.1, esbuild supports the `/* @__NO_SIDE_EFFECTS__ */` comment for functions (https://github.com/evanw/esbuild/commit/cf687c94d9458b6286786850babeefd3e77ff9fb). Would it be possible to consider replacing `/*!` with `/*` ? | 2024-12-15T07:53:02 | 2024-12-15T07:53:02 | {} | CONTRIBUTOR |
vuejs | core | 2,544,245,964 | 12,557 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-16T00:39:34 | 2024-12-16T00:39:34 | {} | NONE |
vuejs | core | 2,544,456,891 | 12,561 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-16T03:15:17 | 2024-12-16T03:15:17 | {} | NONE |
vuejs | core | 2,544,469,653 | 12,555 | edison1105 | This is the expected behavior. The `deep: true` option causes deep traversal of the entire object tree and collects dependencies for all parent properties. This means that even if the target property (e.g., `obj.nested.foo`) does not change, modifying the parent property (e.g., `obj.nested`) will still trigger the call... | 2024-12-16T03:24:31 | 2024-12-16T03:24:31 | {} | MEMBER |
vuejs | core | 2,556,377,468 | 12,578 | linzhe141 | It is similar to this issue
https://github.com/vuejs/core/issues/12460 | 2024-12-20T06:32:38 | 2024-12-20T06:32:38 | {} | MEMBER |
vuejs | core | 2,556,415,270 | 12,520 | Ghosterbeef | @Gwynerva no its not. If component :is="Tag" is not wrapped in a parent tag and is not its only child, a hydration error occurs | 2024-12-20T07:08:57 | 2024-12-20T07:09:25 | {} | NONE |
vuejs | core | 2,538,516,290 | 12,535 | jh-leong | Closing as a duplicate of #9229 | 2024-12-12T10:41:25 | 2024-12-12T10:41:25 | {} | MEMBER |
vuejs | core | 2,543,148,458 | 12,550 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/b9806f95-aa72-4e47-b11f-6d554e66a4c8)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12550
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-14T15:13:10 | 2024-12-14T15:13:10 | {} | NONE |
vuejs | core | 2,544,246,193 | 12,558 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-16T00:39:51 | 2024-12-16T00:39:51 | {} | NONE |
vuejs | core | 2,553,037,793 | 12,575 | Gwynerva | @noootwo Can you please give me an example with Suspense (which is turned on by default in Nuxt on root level) and SSR enabled? I tried to create a workaround yersterday for hours and failed. I am rather new in Vue. | 2024-12-19T08:15:40 | 2024-12-19T08:15:54 | {} | NONE |
vuejs | core | 2,556,817,471 | 12,575 | Gwynerva | Still not applicable because it requires handling the error inside the component where is was thrown. And I plan to have like a few dozens of such "child" components, and all of them can pontentially throw... I really need to handle errors in wrapper, and this wrapper is a "physically" different component, outside of c... | 2024-12-20T11:28:26 | 2024-12-20T12:04:31 | {} | NONE |
vuejs | core | 2,544,246,482 | 12,558 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/eca3d4c7-1211-40c3-bda2-69c350c1f43f)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12558
```
</p></details>
<details><summary><b>@vue/compiler-ssr</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-16T00:40:12 | 2024-12-23T01:45:40 | {} | NONE |
vuejs | core | 2,558,748,251 | 12,588 | edison1105 | As @linzhe141 said, this is a bug of [babel-plugin-jsx](https://github.com/vuejs/babel-plugin-jsx).
Could you please create a new issue at https://github.com/vuejs/babel-plugin-jsx ? | 2024-12-23T01:52:04 | 2024-12-23T01:52:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,538,480,007 | 12,536 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | -------------------- |
| runtime-dom.global.prod.js | 100 kB (**+128 B**) | 38 kB (**+57 B**) | 34.3 kB (**+73 B**) ... | 2024-12-12T10:25:22 | 2024-12-12T10:25:22 | {} | NONE |
vuejs | core | 2,544,424,974 | 12,560 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-16T02:44:51 | 2024-12-16T02:44:51 | {} | NONE |
vuejs | core | 2,552,935,319 | 12,575 | Gwynerva | Well this behaviour is really confusing and right now I don't have even an idea of how to catch async child errors in parent wrapper... I tried `onErrorCaptured`, deep copying child setup, passing `error` ref to child as a prop and etc.
All these solutions just fail because Vue on server-side tries to render templat... | 2024-12-19T07:05:54 | 2024-12-19T07:45:16 | {} | NONE |
vuejs | core | 2,539,374,386 | 6,309 | seriouslysean | I'm seeing a similar issue with custom components not taking the bound props initially.
Vue: `v3.5.13`
CodePen reproduction here, https://codepen.io/seriouslysean/pen/ByBLqpL.
| Initial Load (no error) | Conditional Load (error) |
| --------------------- | ------------------------ |
| 
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/12386674938) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-12-19T08:20:44 | 2024-12-19T08:20:44 | {} | CONTRIBUTOR |
vuejs | core | 2,553,167,613 | 12,575 | noootwo | > @noootwo Can you please give me an example with Suspense (which is turned on by default in Nuxt on root level) and SSR enabled? I tried to create a workaround yersterday for hours and failed. I am rather new in Vue.
@Gwynerva Can you use `try/catch` to handle the error in sub-component's `setup`? Like [this](https... | 2024-12-19T09:21:28 | 2024-12-19T09:22:30 | {} | CONTRIBUTOR |
vuejs | core | 2,556,443,370 | 12,520 | Gwynerva | Yeah now I see. Really weird stuff is happening with SSR... | 2024-12-20T07:33:46 | 2024-12-20T07:34:48 | {} | NONE |
vuejs | core | 2,530,709,340 | 5,433 | edison1105 | Please confirm that your reproduction can reproduce your problem. There is no Profile icon or Dashboard icon shows. | 2024-12-10T07:53:30 | 2024-12-10T07:53:30 | {} | MEMBER |
vuejs | core | 2,531,598,909 | 12,520 | edison1105 | Similar to #6553
see https://github.com/vuejs/core/issues/6553#issuecomment-1232468857
| 2024-12-10T13:11:48 | 2024-12-10T13:11:48 | {} | MEMBER |
vuejs | core | 2,531,734,633 | 12,520 | edison1105 | I think using v-html or v-text on a component(or dynamic component) is somewhat of an anti-pattern, not sure if it will be supported, Let's wait for Evan's input. | 2024-12-10T14:06:45 | 2024-12-10T14:06:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,535,533,419 | 12,520 | Gwynerva | [Tried to use](https://play.vuejs.org/#__SSR__eNp9kU9PAjEQxb/K2Es1IXDQE64YMSRoBI2SeOllszsshW7btF3EkP3uTssfORBunffeTH+T2bIna7vrBlmfZb5w0gbwGBo7EFrW1rgAW1hAC3NnauAU5PdCC10Y7QNIP1SmWMEDBNcgGTt58js1JZK6uD4kHoGXcs2hD9zbXPMOjZVaoxvPJm8kZj44o6vBGJUy8G2cKq+y3l7k0N7QcKoTIKFREbC2Kg9IFUC2/7JHVdY7sViHBU9Uc1l1l95oWnMbGwQrTG2lQvdugy... | 2024-12-11T11:02:02 | 2024-12-11T16:46:16 | {
"+1": 1
} | NONE |
vuejs | core | 2,543,148,448 | 12,550 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.global.prod.js | 158 kB | 57.8 kB | 51.4 kB |
### Usages
| Name | Size | G... | 2024-12-14T15:13:09 | 2024-12-14T15:13:09 | {} | NONE |
vuejs | core | 2,544,699,463 | 12,550 | btea | Handle this issue on vite-plugin-vue side, hence closing this PR. | 2024-12-16T06:18:22 | 2024-12-16T06:18:22 | {} | CONTRIBUTOR |
vuejs | core | 2,544,801,389 | 12,520 | Gwynerva | @edison1105
I'm a relative newcomer to Vue but isn't `<component :is="FooComponent" />` supposed to do exactly the same as writing `<FooComponent />` but with an ability to replace currently rendering component with something else at runtime with `:is` attribute?
And if so, what is wrong (besides loosing reactiv... | 2024-12-16T07:30:52 | 2024-12-16T11:07:02 | {} | NONE |
vuejs | core | 2,550,262,437 | 12,572 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/1472fa40-5df0-44be-aa16-3cb2f1415ada)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12572
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-18T03:50:41 | 2024-12-18T08:34:49 | {} | NONE |
vuejs | core | 2,552,959,039 | 12,571 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/bb67ea1b-91c0-4ab2-b46f-69c03279273d)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12571
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-19T07:23:54 | 2024-12-19T07:23:54 | {} | NONE |
vuejs | core | 2,553,064,399 | 12,570 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/12408875309)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/12386674938) |
|-------|--------|----------------|
| nuxt | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/12408875309... | 2024-12-19T08:28:39 | 2024-12-19T08:28:39 | {} | CONTRIBUTOR |
vuejs | core | 2,530,623,185 | 5,589 | edison1105 | The issue can no longer be reproduced using the latest version of Vue.

see https://template-explorer.vuejs.org/#eyJzcmMiOiI8ZGl2IF5zb21lUHJvcGVydHk9XCJzb21lU3RyaW5nXCI+PC9kaXY+XG48ZGl2IHNvbWVQcm9wZXJ0eS5hdHRyPVwic29tZVN0cml... | 2024-12-10T07:14:18 | 2024-12-10T07:14:18 | {} | MEMBER |
vuejs | core | 2,531,800,488 | 12,520 | Justineo | As the use case doesn’t involve custom components, I think it’s legit for dynamic element tags. | 2024-12-10T14:31:43 | 2024-12-10T14:31:43 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,540,858,269 | 12,404 | dukhevych | Need this. Currently forced to write the whole selector as global or deep, which is not ok. | 2024-12-13T08:26:58 | 2024-12-13T08:26:58 | {} | NONE |
vuejs | core | 2,543,829,384 | 8,952 | alexanderop | @Sengulair nice idea while this works on a type level it currently is not working on a vue component see
[vue palyground](https://play.vuejs.org/#eNp9UsFu2zAM/RVOhyUBsgTDdspcF9sQYNthDboEHTDtkNpMolSWBIn2XHj+91EymqVAkRvF9/j4RLITH52bNTWKhchC4ZUjCEi1y6VRlbOeoAOPO+hh520FI6aOpJGmsCYQVGEPVxEfj76g1hburNflq9FEmmw+yLEQPwgrp7... | 2024-12-15T11:09:48 | 2024-12-15T11:09:48 | {} | NONE |
vuejs | core | 2,543,990,852 | 12,556 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/f8c371a3-e930-424b-bec2-1b41bf4573db)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12556
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-15T18:26:08 | 2024-12-15T18:26:08 | {} | NONE |
vuejs | core | 2,544,411,230 | 12,520 | edison1105 | > [Tried to use](https://play.vuejs.org/#__SSR__eNp9kU9PAjEQxb/K2Es1IXDQE64YMSRoBI2SeOllszsshW7btF3EkP3uTssfORBunffeTH+T2bIna7vrBlmfZb5w0gbwGBo7EFrW1rgAW1hAC3NnauAU5PdCC10Y7QNIP1SmWMEDBNcgGTt58js1JZK6uD4kHoGXcs2hD9zbXPMOjZVaoxvPJm8kZj44o6vBGJUy8G2cKq+y3l7k0N7QcKoTIKFREbC2Kg9IFUC2/7JHVdY7sViHBU9Uc1l1l95oWnMbGwQrTG2lQvdu... | 2024-12-16T02:31:02 | 2024-12-16T02:31:02 | {
"eyes": 1,
"heart": 1
} | MEMBER |
vuejs | core | 2,556,487,600 | 12,583 | cexbrayat | See https://github.com/vuejs/create-vue/issues/641#issuecomment-2556485783 | 2024-12-20T08:09:27 | 2024-12-20T08:09:27 | {} | MEMBER |
vuejs | core | 2,558,713,621 | 12,575 | edison1105 | > The example [without Suspense and SSR](https://play.vuejs.org/#eNqFU01P20AQ/SuPvThIaUxbTiFEKoiq9NAignrygcUekwV719pdO0GW/3tn1wQiRMttd+bNzHvz0YtvTTPrWhJzsXC5VY2HI982y0yrujHWo4dby6oym2sqMaC0pkbCEcnJHsToC2uNPZeNby0Vb3EvyHNTN8+uWRo+ofaIyI12HhTS4HSv5uQwut9UmBBOl+gzjTFk1smqZRuI0YBlDVajlJULhuEw04t01MfK+OOpbirpiX/AolAduk+qPM1... | 2024-12-23T01:12:22 | 2024-12-23T01:12:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,531,059,435 | 12,498 | ihardyslide | I understood that comment in a way, that the **same** API (`useSlots`) can not be used, but a new one would make more sense.
So I would imagine e.g. something like `useNativeSlots` would be possible (just my naive assumption, I have no clue about Vue internals). | 2024-12-10T09:56:35 | 2024-12-10T09:56:54 | {} | NONE |
vuejs | core | 2,540,778,336 | 12,520 | Gwynerva | To sum up, there are two bugs, both working just fine in normal Vue and not working in Vue SSR:
1. `h` is not working in SSR when using `<script setup>` syntax causing hydration errors. There is a [fix](https://github.com/vuejs/core/pull/12533#issue-2734687326) from @linzhe141
2. `<component>` with dynamic `:is` a... | 2024-12-13T07:31:50 | 2024-12-13T07:31:50 | {
"+1": 2
} | NONE |
vuejs | core | 2,541,917,540 | 12,549 | KazariEX | I'm not sure if it's related here.
https://github.com/vitejs/vite-plugin-vue/blob/bebb87b4b477e57d4801ad965659b28dc95e05bc/packages/plugin-vue/src/index.ts#L245-L248 | 2024-12-13T17:26:30 | 2024-12-13T17:27:35 | {} | MEMBER |
vuejs | core | 2,543,324,211 | 12,552 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 100 kB | 37.9 kB | 34.2 kB |
| vue.... | 2024-12-14T19:44:33 | 2024-12-14T19:47:14 | {} | NONE |
vuejs | core | 2,543,324,232 | 12,552 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/b927a24a-7f1e-4ba3-ad83-b800a1e160d2)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12552
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-14T19:44:37 | 2024-12-14T19:47:25 | {} | NONE |
vuejs | core | 2,544,246,186 | 12,557 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/2e7d8201-fa90-4555-aab0-b36d456e2a5b)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12557
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2024-12-16T00:39:51 | 2024-12-16T00:39:51 | {} | NONE |
vuejs | core | 2,544,252,894 | 12,549 | edison1105 | It's a vite-plugin-vue bug, see https://github.com/vitejs/vite-plugin-vue/issues/480 | 2024-12-16T00:48:57 | 2024-12-16T00:48:57 | {} | MEMBER |
vuejs | core | 2,558,719,125 | 12,575 | edison1105 | The original issue arises because we catch exceptions during client-side rendering execution at https://github.com/vuejs/core/blob/a038505c653a1d0cb1e929257d3479cee83dcceb/packages/runtime-core/src/componentRenderUtils.ts#L94 However, on the server-side, we don't catch exceptions at https://github.com/vuejs/core/blob/b... | 2024-12-23T01:19:49 | 2024-12-23T01:19:49 | {
"heart": 2
} | MEMBER |
vuejs | core | 2,536,993,509 | 12,531 | rotu | Maybe both the docs and the return type of `WatchCallback` should be changed to `undefined | Promise<undefined>`?
`void` provides very little type-checking since a function returning `void` may return *any* value.
Relevant discussion:
https://github.com/microsoft/TypeScript/issues/42709 | 2024-12-11T20:01:45 | 2024-12-11T20:01:45 | {} | CONTRIBUTOR |
vuejs | core | 2,556,382,753 | 12,520 | Gwynerva | @Ghosterbeef It does not work when writing `<Tag>` directly but [works](https://play.vuejs.org/#__SSR__eNp9UU1PAjEQ/SuTXqoJgYOe1hUjhkSMX1Fu1sO6DEuh2zadLpKQ/e9OF0EOhlvfR1/fdLbi1vv+ukGRiZzKoH0Ewtj4obK69i5E2MICWpgHV4Nko7xSVtnSWYqgaWRcuYJriKFBFnb0tKiYWpzt5RuQM72WkIEkX1jZ40xtLYb76dMjk5N0hpxicLYaJjIf/AIJ7TnnMu66cSsGEWtvioiMA... | 2024-12-20T06:38:11 | 2024-12-20T06:39:42 | {} | NONE |
vuejs | core | 2,558,781,854 | 12,591 | edison1105 | When rendering on the CSR, it checks if the component contains `onServerPrefetch` hook at https://github.com/vuejs/core/blob/1755ac0a108ba3486bd8397e56d3bdcd69196594/packages/runtime-core/src/component.ts#L876-L879 If it does, it calls `markAsynvBoundary` to make it consistent with SSR behavior. | 2024-12-23T02:29:35 | 2024-12-23T02:32:33 | {} | MEMBER |
vuejs | core | 2,531,669,487 | 12,520 | edison1105 | @Gwynerva
Here is a [workaround](https://play.vuejs.org/#__SSR__eNqlUrtu4zAQ/BWCjR3AkIu7SqcYuEeAS5AXkpRsBGltM6FIhlw5Ngz/e3YpS1GRR5FGXA5nhzMr7uVv77NNCzKXBULjTYmwUFaIotabVFB5tfu3s2Wjq7+u8c6CRYHl6lRJ4igp8jU2hnYThIgTAuZfNkZf2o87i3l3eTEfWSpiFbRHEQFbT3tNigHFO1csg2vEJJszwtkmrNR1L+RM9jBHPqKD2l7UsNQWBrHZWhyOgqz0S1nYJibxytakdc... | 2024-12-10T13:40:51 | 2024-12-10T13:43:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,531,830,856 | 12,521 | edison1105 | try
```js
// in main.js
import { configureCompat } from "vue";
configureCompat({
INSTANCE_LISTENERS: false,
INSTANCE_ATTRS_CLASS_STYLE: false,
});
```
see migration docs https://v3-migration.vuejs.org/migration-build.html#compat-configuration | 2024-12-10T14:43:36 | 2024-12-11T01:16:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,530,690,416 | 12,518 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | --------------------- | -------------------- | -------------------- |
| runtime-dom.global.prod.js | 102 kB (**+1.98 kB**) | 38.8 kB (**+827 B**) | 34.9 kB (**... | 2024-12-10T07:42:05 | 2024-12-11T10:02:29 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.