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,121,517,203 | 10,886 | YiMo1 | 我认为 @neneodonkor 说的很对，所以，我觉得这个问题严格来说不算是一个问题，如果想对`radio`元素使用`.number`，那为什么不直接使用`:value="number"`呢？
所以我认为正因如此，Vue官方才只对`input`元素做了这些修饰符 | 2024-05-21T01:10:42 | 2024-05-21T01:10:42 | {} | NONE |
vuejs | core | 2,121,800,693 | 9,085 | dimitri-grablow | Actually yes, we migrated to vue3 without compat. | 2024-05-21T05:52:34 | 2024-05-21T05:52:34 | {
"+1": 1
} | NONE |
vuejs | core | 2,122,525,094 | 10,985 | Disservin | Sure yes the environments are different, but to me it looks like `size-report` still knows about the pr environment which triggered it because it still thinks it is a pr
```
if: >
github.event.workflow_run.event == 'pull_request' &&
github.event.workflow_run.conclusion == 'success'
```
in my min... | 2024-05-21T12:28:53 | 2024-05-21T12:28:53 | {} | CONTRIBUTOR |
vuejs | core | 2,111,885,875 | 10,891 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ----------------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global... | 2024-05-15T08:26:43 | 2024-05-21T15:39:51 | {} | NONE |
vuejs | core | 2,126,553,223 | 10,991 | Future-came | 非常感谢，尝试了一下，解决了我的问题。 | 2024-05-23T08:40:42 | 2024-05-23T08:40:42 | {} | NONE |
vuejs | core | 2,117,018,810 | 10,813 | edison1105 | @seattlewayne @zhangwannihao
Thanks.
Close this one. | 2024-05-17T08:26:57 | 2024-05-17T08:26:57 | {} | MEMBER |
vuejs | core | 2,121,338,425 | 10,985 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-05-20T22:43:45 | 2024-05-20T22:43:45 | {} | NONE |
vuejs | core | 2,122,633,407 | 10,985 | Disservin | I haven't that's why I first asked if i missed anything. I can give it a shot later, the webhook event payload also seems to have an array of objects named `pull_requests` these objects seem to have the pr number.. i wonder why it is returning an array though | 2024-05-21T13:24:51 | 2024-05-21T13:24:51 | {} | CONTRIBUTOR |
vuejs | core | 2,123,843,920 | 10,990 | dinyo | ah, thanks. i used emit before so i am not aware of this. | 2024-05-22T04:28:35 | 2024-05-22T04:28:35 | {} | NONE |
vuejs | core | 2,109,707,235 | 10,941 | Fuzzyma | thanks for the explanation. Powerful but sometimes unexpected! | 2024-05-14T09:23:12 | 2024-05-14T09:23:12 | {
"+1": 1
} | NONE |
vuejs | core | 2,117,090,378 | 10,963 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9125647679)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9123169209) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-05-17T09:04:56 | 2024-05-17T09:04:56 | {} | CONTRIBUTOR |
vuejs | core | 2,122,096,473 | 10,986 | yyx990803 | Unfortunately, no. Vue 3 requires native ES2015 support. | 2024-05-21T08:45:15 | 2024-05-21T08:45:15 | {} | MEMBER |
vuejs | core | 2,122,167,380 | 10,929 | xuyimingwork | > https://eslint.vuejs.org/rules/require-v-for-key.html
https://play.vuejs.org/#eNqlVW1r2zAQ/iuHv8QBz5mzwSAkZVspWzdoylbYh9gM1VYSdbJkZNlNCfnvu5PsNKajbOuHEOm5507PvUjeBx+qKm4bHsyCeZ0bUVmouW0qkExtFmlg6zQ4S5UoK20s7MHwdQT3zOZbOMDa6BJG6D1KVapyrWoLLZMNhwURwxEGl3w07m26sgIXnXWVKoCOEoHbnG+5MQ/dbjKB0SfDqt5K+6VBWafANWfmZPuDWW5KL... | 2024-05-21T09:19:58 | 2024-05-21T09:19:58 | {} | NONE |
vuejs | core | 2,109,743,771 | 10,927 | quiteeasy | As an alternative to component lifecycle methods, you can utilize [Transition specific hooks](https://vuejs.org/guide/built-ins/transition.html#javascript-hooks). However, I'm unsure if the current behavior is unintended or if it should be modified. While I agree that it feels unsafe and counterintuitive, I'd appreciat... | 2024-05-14T09:39:00 | 2024-05-14T09:39:00 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 2,119,884,027 | 10,979 | haoqunjiang | 我们无法处理没有可靠复现的问题。请在能提供复现代码后再开 issue。 | 2024-05-20T07:56:22 | 2024-05-20T07:56:23 | {} | MEMBER |
vuejs | core | 2,126,285,778 | 10,995 | LinusBorg | That would depend on the implementation of that component. Seems that it rendered nothing, maybe because of a v-if? I cant tell without seeing it | 2024-05-23T05:49:18 | 2024-05-23T05:49:18 | {} | MEMBER |
vuejs | core | 2,110,796,500 | 10,945 | LinusBorg |
> keep $event but refer to an object with Event type
When we talk about custom events in Vue, we do not talk about `CustomEvent` instances from the DOM. We talk about Vue events, and this is how they work.
It's expected and documented behavior, so changing it would be a breaking change anyway.
I think the do... | 2024-05-14T17:49:07 | 2024-05-14T17:49:07 | {} | MEMBER |
vuejs | core | 2,112,049,885 | 10,949 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-15T09:42:51 | 2024-05-15T09:42:51 | {} | NONE |
vuejs | core | 2,114,404,252 | 4,314 | lbineau | Same question here, what's the reason to force shadowDom?
Anyone has a workaround on how to apply global styles without having to inject CSS in each and every Web Components? | 2024-05-16T08:15:07 | 2024-05-16T08:15:07 | {} | NONE |
vuejs | core | 2,114,725,275 | 10,903 | haoqunjiang | It's also documented behavior: https://vuejs.org/guide/components/props.html#boolean-casting | 2024-05-16T09:47:16 | 2024-05-16T09:47:16 | {} | MEMBER |
vuejs | core | 2,115,555,434 | 5,836 | vhovorun | Still waiting when it'll be released | 2024-05-16T15:29:42 | 2024-05-16T15:29:42 | {} | NONE |
vuejs | core | 2,117,016,823 | 10,813 | edison1105 | @nongtan7898
I think `DataTable()` has modified the DOM structure, causing `vnode.el` to be inconsistent with the actual DOM structure, which results in update errors. This approach is incorrect. Since you're using Vue, we should avoid directly manipulating the DOM structure. | 2024-05-17T08:25:52 | 2024-05-17T08:25:52 | {} | MEMBER |
vuejs | core | 2,119,873,988 | 10,964 | linzhe141 | When I comment out the `data` function, it works
```ts
const Comp = defineComponent({
// data() {
// this.$props.propTwo
// return {
// dataOne1: 'Hello World From Data',
// }
// },
props: {
propOne: String,
propTwo: {
default() {
return 'foo'
},
},... | 2024-05-20T07:49:32 | 2024-05-20T07:49:32 | {} | MEMBER |
vuejs | core | 2,120,772,982 | 10,930 | haoqunjiang | Please add a corresponding test case for this fix. | 2024-05-20T16:16:40 | 2024-05-20T16:16:40 | {} | MEMBER |
vuejs | core | 2,121,366,535 | 10,985 | avivkeller | It was an pleasure to help :-) | 2024-05-20T23:10:39 | 2024-05-20T23:36:59 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 2,122,605,296 | 10,985 | sxzz | Did you try it? IIRC, it doesn't work. According to GitHub Docs, Webhook event payload is [`workflow_run` object](https://docs.github.com/en/webhooks/webhook-events-and-payloads#workflow_run) | 2024-05-21T13:10:26 | 2024-05-21T13:10:26 | {} | MEMBER |
vuejs | core | 2,125,985,437 | 10,993 | Justineo | 这不是符合要求的重现，请参考[这里](https://new-issue.vuejs.org/?repo=vuejs/core&lang=zh-cn#why-repro)。 | 2024-05-23T00:27:48 | 2024-05-23T00:27:48 | {} | MEMBER |
vuejs | core | 2,126,222,519 | 10,994 | Simon-He95 | It seems to be a bug in unocss. The performance is normal after turning off unocss. | 2024-05-23T04:47:19 | 2024-05-23T04:47:19 | {} | CONTRIBUTOR |
vuejs | core | 2,126,281,855 | 10,995 | Simon-He95 | @LinusBorg，This is a solution I didn't expect, thanks, but I have one more question。
<img width="719" alt="image" src="https://github.com/vuejs/core/assets/57086651/8374a560-73ad-4b61-b95b-25929345f94b">
<img width="385" alt="image" src="https://github.com/vuejs/core/assets/57086651/af341c69-a06c-45ac-bd07-a54eea87... | 2024-05-23T05:45:48 | 2024-05-23T05:47:13 | {} | CONTRIBUTOR |
vuejs | core | 2,126,771,594 | 10,995 | LinusBorg | Have you checked that `cur.component` is actually containing the component at the moment of rendering? | 2024-05-23T10:31:12 | 2024-05-23T10:31:12 | {} | MEMBER |
vuejs | core | 2,110,354,439 | 10,945 | quiteeasy | Probably, we should clarify in the Vue.js documentation for the [v-on directive](https://vuejs.org/api/built-in-directives.html#v-on) how inline function statements are parsed when using the `$event` variable. The format `$event => ...function code` might not be immediately clear to all users and could result in confus... | 2024-05-14T14:13:41 | 2024-05-14T14:13:41 | {} | CONTRIBUTOR |
vuejs | core | 2,116,736,607 | 10,966 | warunacds | As I understand what's happening here, `plusOne` is a computed property of `count` that returns a copy of `count,` so when you change `plusOne,` it wants to trigger Vue's reactivity system.
Changing the `handleClick` function to change `count directly` will trigger the reactivity system.
```
const handleClick = ()... | 2024-05-17T05:46:38 | 2024-05-17T05:53:00 | {
"heart": 1
} | NONE |
vuejs | core | 2,117,078,536 | 10,963 | haoqunjiang | /ecosystem-ci run | 2024-05-17T08:58:07 | 2024-05-17T08:58:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,120,193,809 | 10,869 | haoqunjiang | /ecosystem-ci run | 2024-05-20T10:49:55 | 2024-05-20T10:49:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,120,271,597 | 10,938 | haoqunjiang | /ecosystem-ci run | 2024-05-20T11:32:30 | 2024-05-20T11:32:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,122,453,645 | 10,985 | sxzz | `size-data` and `size-report` are two distinct workflows. The former runs in an untrusted environment (lacking permissions to write issue/PR comments), while the latter operates in a trusted environment with the necessary permissions.
To link these workflows, we need to pass the target PR number as an argument to th... | 2024-05-21T11:48:11 | 2024-05-21T11:48:11 | {} | MEMBER |
vuejs | core | 2,126,689,506 | 10,929 | Shyam-Chen | https://deploy-preview-10989--vue-sfc-playground.netlify.app/#eNqlVd9v0zAQ/ldOeWkqhZQUnqp2AqYJBtI6wSQemjx4idt6OHbkOFmnqv87d3bSNRqqgD1Utb/77vzdDzv74GNVxW3Dg1kwr3MjKgs1t00FkqnNIg1snQYXqRJlpY2FPRi+juCR2XwLB1gbXcIIvUepSlWuVW2hZbLhsCBiOMLgko/GvU1XVuCis65SBdBRInCbyy035qnbTSYw+mxY1VtpvzQo6xS45cycbH8yy03JpVYoKcODU+XEhk5WBKGKQI... | 2024-05-23T09:49:22 | 2024-05-23T09:49:22 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,154,350,720 | 11,084 | btea | Thanks for the link and detailed instructions.
> When you do node.setAttribute('attribute', null) a casting from null to string is performed by the browser anyway.
You are right, I tried to assign null to the src attribute of the img tag directly, but in fact it got a string `null`.
Perhaps we can keep this PR... | 2024-06-07T08:28:24 | 2024-06-07T08:28:24 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,154,659,975 | 11,086 | anas-js | > 1. Vue re-uses elements where it can, for performance reasons
> 3. Vue cannot track any DOM manipulation that you do imperatively through DOM APIs, anyway.
>
> So as a consequence, it will reuse the div when switching the components, but not remove the attribute you added because it's not aware that it exists.
>
> ... | 2024-06-07T11:38:37 | 2024-06-07T11:39:55 | {
"+1": 1
} | NONE |
vuejs | core | 2,154,679,755 | 11,086 | anas-js | > When you go from home back to about, the `About` component is mounted again, so it adds the attribute again. Works as you designed it to work.
>
> ~~1. Vue re-uses elements where it can, for performance reasons~~
> ~~3. Vue cannot track any DOM manipulation that you do imperatively through DOM APIs, anyway.~~
>
> ~... | 2024-06-07T11:52:09 | 2024-06-07T11:54:04 | {
"+1": 1
} | NONE |
vuejs | core | 2,156,284,094 | 8,482 | Trandx | Okay, thank you for your solution. But, I think that my issue has already
resolved in the resent version that contents Typescript 5.4
Le sam. 8 juin 2024 à 22:55, Clément Nerma ***@***.***> a
écrit :
> I still have problems with generic on the latest version. Even the simple
> following code fails to compile:... | 2024-06-09T02:52:48 | 2024-06-09T02:52:48 | {} | NONE |
vuejs | core | 2,157,619,919 | 11,036 | yyx990803 | Great work! | 2024-06-10T08:07:31 | 2024-06-10T08:07:31 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,157,742,393 | 11,076 | davidmatter | Might be related to
* https://github.com/vuejs/core/pull/9652
* https://github.com/vuejs/core/pull/9418 | 2024-06-10T08:50:16 | 2024-06-10T08:50:16 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,160,369,155 | 10,609 | lzl0304 | The problem is caused by incompatible dependency versions, `Vue` depends on `entities:^4.5.0`, but there are other packages that depend on `entities:^2.2.0`, for some reason the dependency installed by `yarn` is only `entities:^2.2.0`, which leads to runtime errors.
I tried to use npm, `pnpm` to install the dependen... | 2024-06-11T10:16:23 | 2024-06-11T10:16:23 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 2,163,429,524 | 8,803 | skirtles-code | For anyone trying to review this, here's the original reproduction, converted to a Playground:
- [Playground - `main`](https://play.vuejs.org/#eNq1Vktv20YQ/itT9iAZMCk5doCWkd2mgQ/poSnSoJcyKFbkSGK8D2J3KdsQ+N8z+yCp0IqRQ+Ln7sw3s9/Oa3VIBKtl9skkeVKLRmkLByg1MouvmwY62GglYLZvcVbICHCKIM4WrGmyoCxkqaSxQBK4Hl3M6fds1JpS140lQKXKVq... | 2024-06-12T16:11:34 | 2024-06-12T16:11:34 | {
"+1": 1,
"heart": 1,
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 2,165,954,403 | 11,121 | Doctor-wu | > I am unable to focus on this for now, @Doctor-wu are you interested in taking a look at this?
Sure, I'll take a look at this 👀 | 2024-06-13T15:08:14 | 2024-06-13T15:08:14 | {
"heart": 3
} | MEMBER |
vuejs | core | 2,166,765,787 | 4,662 | EranGrin | Just another plugin that resolves the issue as SFC or a full app
https://www.npmjs.com/package/vue-web-component-wrapper | 2024-06-13T20:50:46 | 2024-06-13T20:50:46 | {} | NONE |
vuejs | core | 2,149,401,328 | 11,073 | jacekkarczmarczyk | It's how HTML works
https://github.com/whatwg/html/issues/721 | 2024-06-05T10:04:45 | 2024-06-05T10:04:45 | {
"+1": 1,
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 2,142,933,123 | 6,688 | skirtles-code | Just in case this does get merged, I think the same change would need to be applied to the `onceHandler` a bit further down.
---
As for whether it should be merged, I'm very much on the fence.
I think it's an easy problem for people to fall into without really understanding what's going on.
The exact timing... | 2024-05-31T20:26:09 | 2024-06-06T19:49:34 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 2,154,239,643 | 9,264 | Disservin | > Note that with
>
> ```js
> const getComponent = () => {
> return defineAsyncComponent(() => Promise.resolve(VFoo));
> };
> ```
>
> and
>
> ```
> <component :is="getComponent()">
> ```
>
> **You are defining a new component on every update.** To the parent component, it is rendering a different c... | 2024-06-07T07:17:03 | 2024-06-07T07:18:43 | {} | CONTRIBUTOR |
vuejs | core | 2,154,244,639 | 7,649 | lehni | Thank you @yyx990803 and @AlexVagrant ! Can't wait to finally remove our workarounds for this : ) | 2024-06-07T07:20:34 | 2024-06-07T07:21:30 | {} | CONTRIBUTOR |
vuejs | core | 2,159,816,866 | 11,104 | SheryarGorelo | @edison1105
I am already using hoistStatic as false. I have also updated the compilerOptions in reproducible link, its still not releasing the nodes.
| 2024-06-11T05:21:40 | 2024-06-11T07:37:29 | {} | NONE |
vuejs | core | 2,154,323,398 | 11,078 | yangliguo7 | if u use async setup. u should use <Suspense> boundary
https://play.vuejs.org/#eNqNU01v2zAM/SuCLnaBwEG3nTrHQzfksB22Yi12EjBoNuOqlSVDH06GwP99pJxkztYWzSG2yPeox0d6z6/7vhgi8Cte+tqpPjAtTbsSPHjBmYcQ+0oY1fXWBfbJdj3bONsxwYslnYgruDDlcmIjFg8Bul7LAHhirLyNvgfjoSqJUZWJiI9TnOgzCl/g5bU1G9UWD94a1LanQoLXSFQa3Lc+KGtQ4BVLGcpJre32S4oF... | 2024-06-07T08:12:04 | 2024-06-07T08:12:04 | {} | CONTRIBUTOR |
vuejs | core | 2,154,647,100 | 11,086 | LinusBorg | When you go from home back to about, the `About` component is mounted again, so it adds the attribute again. Works as you designed it to work.
~~1. Vue re-uses elements where it can, for performance reasons~~
~~3. Vue cannot track any DOM manipulation that you do imperatively through DOM APIs, anyway.~~
~~So as ... | 2024-06-07T11:30:21 | 2024-06-07T11:38:32 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,156,200,684 | 8,482 | ClementNerma | I still have problems with generic on the latest version. Even the simple following code fails to compile:
```typescript
export type Test<T> = T
``` | 2024-06-08T21:54:53 | 2024-06-08T21:54:53 | {} | NONE |
vuejs | core | 2,157,141,507 | 11,101 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 91.3 kB | 34.7 kB | 31.3 kB |
| vue.global.prod.js | 148 kB | 54 kB | 48.2 kB |
### Usages
| Name | Size |... | 2024-06-10T03:40:33 | 2024-06-10T03:40:33 | {} | NONE |
vuejs | core | 2,162,101,571 | 11,104 | waleedhasank | @edison1105, I am also facing this same issue in my new Vue 3 app. I was using Vue 3 with Quasar first, then I realized that some UI components were staying in DOM even after leaving the component (verified through the detached elements feature of Microsoft Edge DEV channel browser). I removed Quasar and used simple HT... | 2024-06-12T04:52:13 | 2024-06-12T04:52:13 | {} | NONE |
vuejs | core | 2,167,132,261 | 11,130 | jh-leong | This behavior seems to be expected. Ref: https://github.com/vuejs/rfcs/pull/154
> Functional components without a `props` declaration will have everything passed in as props. They will only have implicit fallthrough for `class`, `style`, and `v-on` listeners.
~~By the way, I couldn't find this mentioned in the do... | 2024-06-14T03:10:56 | 2024-06-14T03:20:35 | {} | MEMBER |
vuejs | core | 2,167,148,681 | 11,130 | Shyam-Chen | ```ts
import { h, useAttrs, useSlots } from 'vue';
const attrs = useAttrs();
const slots = useSlots();
const Comp = () => h('div', attrs, slots);
``` | 2024-06-14T03:35:11 | 2024-06-14T03:35:11 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,150,505,389 | 7,809 | haoqunjiang | Oops. Sorry. Reopened. | 2024-06-05T16:41:11 | 2024-06-05T16:41:11 | {} | MEMBER |
vuejs | core | 2,151,104,871 | 9,370 | skirtles-code | Does this also need to account for `KeepAlive`?
I've put together a couple of Playground examples that might be relevant here:
- [Playground 1](<https://deploy-preview-9370--vue-sfc-playground.netlify.app/#eNp9U01P20AQ/SvTvThIqX3ghhLUlCKVVrQIOO7F2GNnYb1r7YcJivLfmd3FjoVQpCjxzLx58+ZNvGebvs8Hj+yCrWxlRO/AovP9JVei67Vx... | 2024-06-05T23:08:56 | 2024-06-05T23:23:37 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 2,153,739,702 | 11,082 | baiwusanyu-c | /ecosystem-ci run | 2024-06-07T02:28:01 | 2024-06-07T02:28:01 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,154,464,711 | 11,084 | yyx990803 | Vue's behavior has always been "setting to `null` means remove it". This will be a breaking change. | 2024-06-07T09:32:39 | 2024-06-07T09:32:39 | {
"eyes": 1
} | MEMBER |
vuejs | core | 2,156,374,335 | 8,991 | skirtles-code | I was hoping to review this, but I'm unclear what the use case is. Is there a specific tool/library that would benefit from including this extra information? | 2024-06-09T07:54:46 | 2024-06-09T07:54:46 | {} | CONTRIBUTOR |
vuejs | core | 2,156,426,889 | 8,991 | Tofandel | It's not really extra information, it's information that is missing that is normally available. I was trying to build a tool that would have used it, and this is crucial information that is missing, without it there is no way to know what node/tag is the v for on
Without it we cannot edit the existing source as the ... | 2024-06-09T10:11:10 | 2024-06-09T10:13:05 | {} | CONTRIBUTOR |
vuejs | core | 2,162,983,310 | 11,117 | moritz-baecker-integra | Thanks for the response, but as far as i can see the radiobox still gets checked and the value is suddenly a string and not a number. This is not what i would expect within typescript. Or do i understand something else wrong? | 2024-06-12T13:15:16 | 2024-06-12T13:15:16 | {} | NONE |
vuejs | core | 2,164,315,900 | 11,121 | edison1105 | It works fine with v3.5.0-alpha.2 | 2024-06-13T03:58:07 | 2024-06-13T03:58:58 | {} | MEMBER |
vuejs | core | 2,164,548,043 | 11,104 | SheryarGorelo |
@edison1105, I ran it using the following commands:
npm run build
npm run preview
The initial dom nodes were 311 and after toggle they were around 333, we can still see its not being detached. or am I doing something wrong here? attached video demo
https://www.loom.com/share/9e934ba9f4654ab8b7e879ba00f16ded?s... | 2024-06-13T06:14:13 | 2024-06-13T06:14:13 | {} | NONE |
vuejs | core | 2,150,317,246 | 11,073 | yyx990803 | Yeah, this is how HTML works.
Also this is documented in the docs: https://vuejs.org/guide/essentials/component-basics.html#in-dom-template-parsing-caveats | 2024-06-05T15:09:56 | 2024-06-05T15:10:52 | {
"+1": 1,
"eyes": 1
} | MEMBER |
vuejs | core | 2,157,169,517 | 9,336 | davidmatter | [According to the ts team](https://github.com/microsoft/TypeScript/wiki/FAQ#add-a-key-constraint-to-omit) https://github.com/vuejs/core/pull/10596 is the way to go. Not sure if there are any important differences for this usecase between my proposal of
`type OmitKeepDiscriminatedUnion<T, K extends keyof any> = T ext... | 2024-06-10T04:13:50 | 2024-06-10T04:13:50 | {} | CONTRIBUTOR |
vuejs | core | 2,164,968,868 | 8,801 | posva | @skirtles-code I'm surprised they don't both leak. I would consider that usage wrong, but it does show a distinction between _being able to `inject`_ and _being able to use reactive effects_ is important. I think it makes more sense to keep things separate and adding an effectScope to the app would allow to have `app.s... | 2024-06-13T08:22:29 | 2024-06-13T08:22:29 | {} | MEMBER |
vuejs | core | 2,167,143,069 | 11,128 | jh-leong | This behavior is expected. Perhaps you could join the [discussion](https://github.com/vuejs/core/discussions) to provide more information and explore specific solutions? | 2024-06-14T03:27:32 | 2024-06-14T03:27:32 | {} | MEMBER |
vuejs | core | 2,149,422,431 | 11,073 | warmthsea | https://github.com/sveltejs/svelte/issues/11052
😱😱😱😱😱😱 | 2024-06-05T10:14:51 | 2024-06-05T10:14:51 | {} | NONE |
vuejs | core | 2,154,377,987 | 5,256 | yyx990803 | closed via #11067 (will be out in 3.5) | 2024-06-07T08:44:22 | 2024-06-07T08:44:22 | {
"+1": 3
} | MEMBER |
vuejs | core | 2,156,944,446 | 11,097 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 91.3 kB | 34.7 kB | 31.3 kB |
| vue.global.prod.js | 148 kB | 54 kB | 48.2 kB |
### Usages
| Name | Size |... | 2024-06-10T00:43:46 | 2024-06-10T00:43:46 | {} | NONE |
vuejs | core | 2,159,573,500 | 11,087 | edison1105 | close as duplicate | 2024-06-11T00:59:55 | 2024-06-11T00:59:55 | {} | MEMBER |
vuejs | core | 2,159,706,470 | 11,078 | green-mike | Hi, I use boundary in the [Vue SFC Playground](https://play.vuejs.org/#__SSR__eNqNU01v2zAM/SuCLnaBwEG3nTrHQzfksB22Yi12EjBoNuOqlSVDH06GwP99pJxkztYWzSG2yPeox0d6z6/7vhgi8Cte+tqpPjAtTbsSPHjBmYcQ+0oY1fXWBfbJdj3bONsxwYslnYgruDDlcmIjFg8Bul7LAHhirLyNvgfjoSqJUZWJiI9TnOgzCl/g5bU1G9UWD94a1LanQoLXSFQa3Lc+KGtQ4BVLGcpJre32S4oFF2FxjN... | 2024-06-11T03:21:36 | 2024-06-11T03:21:36 | {} | NONE |
vuejs | core | 2,162,533,937 | 11,104 | edison1105 | @waleedhasank @SheryarGorelo
- disable the `vue-devtools`
- or test it in production mode.
| 2024-06-12T09:23:40 | 2024-06-12T09:28:07 | {} | MEMBER |
vuejs | core | 2,167,065,207 | 11,128 | jh-leong | In case 1: The `this.xxx` executed in the constructor updates the state of the `raw object`, which doesn't trigger an effect. You need to modify the state through the `proxy` returned by `ref`. See this [playground](https://play.vuejs.org/#eNp9Ustu2zAQ/JUFL5EBl1aa9pI6BvrIIT20RRv0RKAQlLXNlCIJknIMCPr3DqnK8SGIIAjizHB3dshB... | 2024-06-14T01:49:46 | 2024-06-14T01:49:46 | {} | MEMBER |
vuejs | core | 2,153,744,144 | 11,082 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9410718200)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9378434096) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-06-07T02:35:01 | 2024-06-07T02:35:01 | {} | CONTRIBUTOR |
vuejs | core | 2,154,265,895 | 11,084 | btea | IMO, it's not a question of whether it's worth the extra check, but rather that we should be consistent with the default HTML behavior. | 2024-06-07T07:35:05 | 2024-06-07T07:35:05 | {} | CONTRIBUTOR |
vuejs | core | 2,154,299,091 | 11,084 | ferferga | @btea AFAIK, according to the [spec](https://html.spec.whatwg.org/multipage/embedded-content.html#dom-img-src), src might not be present (since it might be missing when using the ``<source>`` elements for instance). Not present is the same as undefined, but null is completely different (``typeof null === 'object'`` is ... | 2024-06-07T07:57:14 | 2024-06-07T08:03:15 | {} | CONTRIBUTOR |
vuejs | core | 2,162,867,047 | 11,118 | jacekkarczmarczyk | > When a prop is declared to allow multiple types, the casting rules for Boolean will also be applied. However, there is an edge when both String and Boolean are allowed - the Boolean casting rule only applies if Boolean appears before String
https://vuejs.org/guide/components/props.html#boolean-casting | 2024-06-12T12:18:56 | 2024-06-12T12:19:16 | {} | CONTRIBUTOR |
vuejs | core | 2,163,706,125 | 8,801 | skirtles-code | I'm wondering about whether this could cause memory leaks, and whether that matters.
I've put together an example using Vue Router:
- [Playground - `main`](https://play.vuejs.org/#eNp9VU1v2zgQ/SsD7cHywhbRTXYPhhOkLYLtLrrbog16qXqgpbHFWCIFkrIdGPnvHX5Ilhu3RgJR5LzhvHkzo2PScCGzR5MsEtG0Sls4QqGRW3zdtvAMa60amOw6nOQyGmjVWdTx... | 2024-06-12T18:56:37 | 2024-06-12T18:56:37 | {} | CONTRIBUTOR |
vuejs | core | 2,164,352,940 | 11,121 | wanghanzhen | > It works fine with v3.5.0-alpha.2
Could it be fixed in 3.4? I just upgraded to 3.4, Alpha version is unstable.
By the way,do you know which mr or commit fixed it? | 2024-06-13T04:34:22 | 2024-06-13T04:34:22 | {} | NONE |
vuejs | core | 2,164,803,223 | 11,121 | LinusBorg | Sidenote: Mutating external state from within a computed is an anti-pattern. Should still not end in recursive loop, but still ... | 2024-06-13T07:23:30 | 2024-06-13T07:23:30 | {} | MEMBER |
vuejs | core | 2,167,165,562 | 11,130 | guaijie | > ```ts
> import { h, useAttrs, useSlots } from 'vue';
>
> const attrs = useAttrs();
> const slots = useSlots();
>
> const Comp = () => h('div', attrs, slots);
> ```
这只是在这个 bug 尚未解决前的一个临时写法，但不能掩盖作为 bug 的事实 | 2024-06-14T03:59:30 | 2024-06-14T04:00:04 | {} | CONTRIBUTOR |
vuejs | core | 2,150,499,457 | 7,809 | skirtles-code | @sodatea I think this should be reopened, I believe you misunderstood the author's intent.
The type mismatch on the prop was intentional. The problem being fixed here is that the warning message isn't generated correctly. | 2024-06-05T16:37:43 | 2024-06-05T16:37:43 | {} | CONTRIBUTOR |
vuejs | core | 2,163,542,162 | 7,787 | tal-mogendorff | Seems like one of the best feature that should be considered to merge to Main version of Vue.
From my side, we are developing an Shared component Infra library that has "bubbles" inside the root component.
How ever, we have a problem where we did a wrapper for the root component to create our own Shared component a... | 2024-06-12T17:15:27 | 2024-06-12T17:15:27 | {
"+1": 1
} | NONE |
vuejs | core | 2,164,364,158 | 9,607 | Alfred-Skyblue | /ecosystem-ci run
| 2024-06-13T04:46:07 | 2024-06-13T04:46:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,150,471,126 | 7,809 | haoqunjiang | It's because you defined the prop to be of string type, which is incompatible with symbol, thus failing the prop validation.
```ts
const props = defineProps<{
value?: string
}>()
```
It would work if you write `value?: any` instead. | 2024-06-05T16:21:51 | 2024-06-05T16:41:29 | {} | MEMBER |
vuejs | core | 2,151,630,905 | 11,008 | AragakioYui | > I tried to create a Playground based on your code, but I wasn't able to reproduce the problem you reported:
>
> * [Playground](https://play.vuejs.org/#eNqdVE2PmzAQ/SsjX5KV0qB+nBCJmkZ7aKV+aNMjFwJD8K4xCBvKKuK/d2wDcdq0K+0p8Zvn8XvzwZnt6nrdtchCFmksa5Fo3MYSIDq0qkap3InOaVXWlUSp3Rkg5GoTsxlW6wuDTZzuDc+vSR1X/CjQp5RVhuJF1pHL... | 2024-06-06T07:51:17 | 2024-06-06T07:51:17 | {} | NONE |
vuejs | core | 2,153,758,832 | 11,071 | jh-leong | This behavior is expected: [TS Playground](https://www.typescriptlang.org/play/?#code/MYewdgzgLgBAZiEMC8MA8AVGBTAHlbMAEwhgHIEQyA+ACgEoVqYBvAWACgYZRJYBDAFysYAa2FYAvihHjylMjGkB6ZTgBO6kOoCEnbqpgYAngAds5AESVLigJakwIARAh2A5mH4AjADYWoJCgzCzIMMgA6fRhDMmtEWxgHGH5XDy8-AKCACwteaHV+OzBYEDgYYPNycIAaGG8AV1gwxVAG3yJ6i2LofhK7fgJOgHc7... | 2024-06-07T02:56:24 | 2024-06-07T02:56:24 | {} | MEMBER |
vuejs | core | 2,154,242,834 | 11,084 | ferferga | Is this worth really the extra check? Plus in the current state this is not accounted for in the type system.
Simply cast ``null`` to String and you're good to go (or create your own wrapper component that handles this for yourself):
[Playground](https://play.vuejs.org/#eNp9UT1vwjAQ/SsnLwkSCkM7oYD6IYZ2aKvS0UsUjtTUs... | 2024-06-07T07:19:22 | 2024-06-07T07:19:22 | {} | CONTRIBUTOR |
vuejs | core | 2,156,367,240 | 9,264 | yyx990803 | Why not just
```js
const UiComponent = defineAsyncComponent(() => import(`./VFoo.vue`))
```
What's the point of wrapping it in another function? | 2024-06-09T07:33:15 | 2024-06-09T07:33:15 | {} | MEMBER |
vuejs | core | 2,164,370,895 | 9,607 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9493858408)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9476964574) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/949... | 2024-06-13T04:52:37 | 2024-06-13T04:52:37 | {} | CONTRIBUTOR |
vuejs | core | 2,165,127,412 | 11,121 | wanghanzhen | > @wanghanzhen this one #10397
seems such a big change😨. Is there a temporary and simple solution? @johnsoncodehk Looking forward to your advice🙏 | 2024-06-13T09:32:55 | 2024-06-13T09:32:55 | {} | NONE |
vuejs | core | 2,165,303,229 | 8,657 | skirtles-code | For anyone looking to review this, here's a simple example:
- [Playground - `main` (currently broken)](https://play.vuejs.org/#eNp9Uk1vnDAQ/StT98AiETi0p4iN2kZ7aA9t1eRW90DZgXVibOSPzUqI/97BxttNFOUCzJs3M4+ZN7GhEap8sOyaiWHUxsEErcHG4edxLOBQwB47ofDWW6eHncQBlYMZOqMHyI4eM67WwkRZc2WVgDLSuGovm9gydt5kEb5Cmb06bZOiPA9NkrrNxBWARe... | 2024-06-13T10:51:16 | 2024-06-13T10:51:16 | {} | CONTRIBUTOR |
vuejs | core | 2,150,947,616 | 10,192 | skirtles-code | I believe this has now been fixed via #8304. That fix should be available in the next release and is already deployed to the Playground. | 2024-06-05T20:55:26 | 2024-06-05T20:55:26 | {} | CONTRIBUTOR |
vuejs | core | 2,153,752,995 | 11,083 | Dreadom | 由于是subjectList.value = res.data，所以导致数据赋值到了subjectList这个value属性上，在模板使用时需要访问value属性才能拿到值。也就是说subjectList是一个reactive数据，但是数据是保存在了value属性上 | 2024-06-07T02:47:58 | 2024-06-07T02:47:58 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.