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,261,599,383 | 6,766 | yyx990803 | Unfortunately this is because ref values have to expose the "unwrapped" type, which unwraps nested refs, to ensure value access correctness:
```ts
const a = { b: ref(0) }
const c = ref(a)
c.value.b // should be number
c.value = a // same error you saw
```
To fix this we will need TypeScript to allow spec... | 2022-09-29T00:27:42 | 2022-09-29T00:27:42 | {} | MEMBER |
vuejs | core | 1,261,818,726 | 6,763 | LinusBorg | use `createApp` instead of `render` and re-register all global components with that new app.
If you have further questions, use our Discord server or open a discussion in the repo discussions area. | 2022-09-29T06:20:07 | 2022-09-29T06:20:07 | {} | MEMBER |
vuejs | core | 1,257,064,993 | 6,674 | vis97c | https://github.com/vuejs/core/pull/6652 Seems to fix this | 2022-09-24T21:04:04 | 2022-09-24T21:04:04 | {} | NONE |
vuejs | core | 1,257,099,963 | 6,573 | KaelWD | If you're using Vuetify, update to 3.0.0-beta.11
If you aren't then idk, in our case it was caused by reusing vnodes (calling h() in a computed) | 2022-09-25T02:02:40 | 2022-09-25T02:03:22 | {} | CONTRIBUTOR |
vuejs | core | 1,257,151,326 | 6,724 | LinusBorg | As I said, you need to use a ref for this. reassigning variables can't reactive in Javascript.
Please use this repository's "discussions" Section or our discord chat to ask for more help. This issue is not the place for that. | 2022-09-25T09:04:33 | 2022-09-25T09:04:33 | {} | MEMBER |
vuejs | core | 1,257,181,703 | 6,660 | shigma | Note: I'm not sure the fix touches the the core of problem (although it indeed fixes the regression introduced in 00036bb52c4e641b2be7fa55c39ced9448163b0f).
```ts
type Slot = (...args: any[]) => VNode[]
```
From the above typings, a `Slot` should not return `undefined`. However it does in the simple reproductio... | 2022-09-25T12:16:01 | 2022-09-25T12:17:04 | {} | CONTRIBUTOR |
vuejs | core | 1,257,955,850 | 6,596 | LinusBorg | closing for inactivity and missing reproduction | 2022-09-26T12:24:58 | 2022-09-26T12:24:58 | {} | MEMBER |
vuejs | core | 1,261,003,248 | 6,770 | derdem | > You need to use `defineExpose()` (which you do) to define properties that are available as properties on the instance object. Those will be exposed through the proxy you see logged to the console. you can verify that by logging`options.instance.myFunc`.
thanks for the tipp. That way quite a nasty bug on my side to... | 2022-09-28T14:30:54 | 2022-09-28T14:30:54 | {} | NONE |
vuejs | core | 1,261,036,534 | 6,770 | LinusBorg | script setup instances are intentionally closed by default. no instance state is exposed to the outside unless it's explicitly mean to be.
This is a learning we had: When any property you use *in* your component can implicitly become part of its API consumed by other parts of the app through template refs or custom... | 2022-09-28T14:54:32 | 2022-09-28T14:54:58 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,256,921,118 | 5,513 | sydney-d | @antfu Awesome :3, will this also apply to keep-alive components ? | 2022-09-24T09:22:32 | 2022-09-24T09:22:32 | {} | NONE |
vuejs | core | 1,258,871,979 | 6,763 | yyx990803 | Manually calling `render` creates a tree that doesn't belong to the current app instance, so it can't resolve components registered under the app's scope. | 2022-09-27T02:10:24 | 2022-09-27T02:10:24 | {} | MEMBER |
vuejs | core | 1,258,931,946 | 5,256 | pengfan2013 | > This only keeps the first component instance in memory, so it's technically not a memory leak because the total memory won't increase over time. It's still inefficient though and can be improved.
这种场景放到动态路由上: 反复大量的不同内容的相同页面组件, 递增的量就异常可观了, 浏览器标签爆掉就非常的简单了. | 2022-09-27T03:47:46 | 2022-09-27T03:47:46 | {} | NONE |
vuejs | core | 1,259,238,660 | 6,678 | yyx990803 | Thanks for the PR - however #6652 should provide a more generic fix. | 2022-09-27T09:30:45 | 2022-09-27T09:30:45 | {} | MEMBER |
vuejs | core | 1,260,885,889 | 6,770 | LinusBorg | You need to use `defineExpose()` (which you do) to define properties that are available as properties on the instance object. Those will be exposed through the proxy you see logged to the console. you can verify that by logging`options.instance.myFunc`. | 2022-09-28T13:07:26 | 2022-09-28T14:20:15 | {} | MEMBER |
vuejs | core | 1,261,927,264 | 6,467 | moushicheng | > Hello, any progress with this PR? Need any help?
Thank you for your kindness!, but this PR should be suspended first as the reason for this bug is complex，I think it needs further study。 | 2022-09-29T08:15:10 | 2022-09-29T08:15:10 | {} | CONTRIBUTOR |
vuejs | core | 1,261,996,277 | 4,339 | maxwls | 需要这个特性。 | 2022-09-29T09:11:12 | 2022-09-29T09:11:12 | {} | NONE |
vuejs | core | 1,263,059,189 | 5,993 | willjayyyy | > 我想问一下 这样使用时并没有生效
include数组需要加入组件名，而不是路由名 | 2022-09-30T03:26:16 | 2022-09-30T03:26:16 | {} | NONE |
vuejs | core | 1,256,945,722 | 6,738 | edison1105 | duplicate of #4930 | 2022-09-24T11:23:13 | 2022-09-24T11:23:13 | {} | MEMBER |
vuejs | core | 1,257,535,865 | 4,745 | ken-tan3 | @yyx990803
` WARN [@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead.`
- This warning is really disturbing in console, just because it occurs too much.
- I hope it's displayed less time or removed at all as soon as possible.
> Is there any way to disable ... | 2022-09-26T06:22:12 | 2022-09-26T06:22:12 | {
"+1": 1
} | NONE |
vuejs | core | 1,261,291,086 | 6,591 | michaelperel | Thank you so much for clearing that up! I figured because it said “prod” that it meant they were disabled.
Thank you all so much for your work on this issue, I really really appreciate it :) | 2022-09-28T18:10:01 | 2022-09-28T18:10:01 | {} | NONE |
vuejs | core | 1,261,815,339 | 6,763 | huzedong2015 | @LinusBorg | 2022-09-29T06:15:55 | 2022-09-29T06:15:55 | {} | NONE |
vuejs | core | 1,257,813,192 | 6,757 | wenkm | <img width="1178" alt="image" src="https://user-images.githubusercontent.com/3335540/192251618-4f61384e-704a-478e-a084-55a211fcda4e.png">
上图为编译错误截图
The picture above is a screenshot of the compilation error.
```js
const { ctx } = getCurrentInstance();
const .....
```
这样分开定义没问题
It's okay with separate defini... | 2022-09-26T10:18:14 | 2022-09-26T10:18:14 | {} | NONE |
vuejs | core | 1,258,926,573 | 6,762 | edison1105 | ok, I see.
the `target.value` will be set as a new element every time `bindKey` changed
So, you need to observe the new element again. | 2022-09-27T03:38:57 | 2022-09-27T03:42:46 | {} | MEMBER |
vuejs | core | 1,258,929,142 | 6,762 | joisun | Thanks that you’ve solved my puzzle
获取 Outlook for iOS<https://aka.ms/o0ukef>
________________________________
发件人: edison ***@***.***>
发送时间: Tuesday, September 27, 2022 11:39:07 AM
收件人: vuejs/core ***@***.***>
抄送: Zhongyi Sun ***@***.***>; Author ***@***.***>
主题: Re: [vuejs/core] 在IntersectionObserver 的回调函数中,... | 2022-09-27T03:43:09 | 2022-09-27T03:43:09 | {} | NONE |
vuejs | core | 1,259,200,821 | 5,165 | xuxing409 | I tried vue@3.2.37 version and still have this error | 2022-09-27T08:59:52 | 2022-09-27T09:00:45 | {} | NONE |
vuejs | core | 1,260,104,732 | 6,651 | spacedawwwg | Just hit this same issue upgrading from 3.2.37
| 2022-09-27T22:09:17 | 2022-09-27T22:09:17 | {} | NONE |
vuejs | core | 1,260,524,838 | 6,688 | LinusBorg | @yyx990803 You closed #6669 as "not a bug", so I assume my PR can be closed? | 2022-09-28T07:53:28 | 2022-09-28T07:53:28 | {} | MEMBER |
vuejs | core | 1,260,672,227 | 6,591 | yyx990803 | The "leak" only happens when:
- Using the dev build
- Has Vue Devtools enabled
- Hasn't opened the Vue devtools tab
Vue Devtools buffers devtool-specific events in a global object before the devtools tab is activated. The buffered events hold references to the component instances triggering them, so those compo... | 2022-09-28T09:57:49 | 2022-09-28T09:59:01 | {
"eyes": 1
} | MEMBER |
vuejs | core | 1,261,067,168 | 6,614 | Akryum | @yyx990803 I can still reproduce the issue on a deployed app (Vue 3.2.39 in production mode) but it's very difficult to create a reproduction as it seems to be random. I guess there is a timing or race condition at play...
Here is a screenshot of requests failing becase watchers are being executed while unmounting c... | 2022-09-28T15:16:17 | 2022-09-28T15:16:17 | {} | MEMBER |
vuejs | core | 1,261,197,266 | 6,771 | VividLemon | 
redblobgames in the vue land discord also put out this, to help possibly narrow the issue. | 2022-09-28T16:56:26 | 2022-09-28T16:56:26 | {} | NONE |
vuejs | core | 1,261,264,024 | 6,771 | VividLemon | > if you wanted to set text specifically as an attribute even though achors do not have such an attribute as per the spec, you could do it like this:
It was actually an accidental passthrough of a prop using v-bind=$props to a dynamic child component that rendered an `<a>`. Was quite a pain to find, not knowing that... | 2022-09-28T17:52:28 | 2022-09-28T17:52:38 | {} | NONE |
vuejs | core | 1,256,890,271 | 5,513 | antfu | Made this that could probably be a solution: https://github.com/vuejs/core/pull/6736 | 2022-09-24T07:12:38 | 2022-09-24T07:12:38 | {
"+1": 14,
"rocket": 6
} | MEMBER |
vuejs | core | 1,254,963,525 | 6,715 | jonaskuske | Yup! Looking into it atm.
I think one approach would be to pass `true` for the `keepComment` arg, another to change the generated SSR code so it doesn't output the comment HTML anymore (`_push('<!---->')`).
I suspect the first option causes issues because then the comment node is passed to `setTransitionHooks()`, but... | 2022-09-22T12:37:13 | 2022-09-24T10:38:26 | {} | CONTRIBUTOR |
vuejs | core | 1,259,187,585 | 6,757 | wenkm | > I have played around with the provided example and here are some observations:
>
> * the issue disappears with any of these changes:
>
> * removing props definition;
> * removing emit definition;
> * swapping { ctx } definition with props or emit definitions;
> * adding another definition.
> * the... | 2022-09-27T08:48:16 | 2022-09-27T08:48:16 | {} | NONE |
vuejs | core | 1,260,306,806 | 6,639 | yyx990803 | fixed via 8963c550 | 2022-09-28T02:27:24 | 2022-09-28T02:27:24 | {} | MEMBER |
vuejs | core | 1,260,549,634 | 6,605 | SailSpring | After a round of searching, there is really no good solution, unless you use less | 2022-09-28T08:15:54 | 2022-09-28T08:15:54 | {} | NONE |
vuejs | core | 1,262,790,877 | 6,779 | wahid-moh | I think this is related to files catch, because when I tried with new chrome session (New incognito window) I didn't get any issue. | 2022-09-29T20:40:31 | 2022-09-29T20:40:31 | {} | NONE |
vuejs | core | 1,263,050,650 | 5,993 | KyrieY | 我想问一下
<keep-alive>
<router-view ></router-view>
</keep-alive>
这样使用时并没有生效 | 2022-09-30T03:08:38 | 2022-09-30T03:08:38 | {} | NONE |
vuejs | core | 1,102,683,919 | 5,755 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). | 2022-04-19T13:52:12 | 2022-04-19T13:52:12 | {} | MEMBER |
vuejs | core | 1,103,314,339 | 5,747 | edison1105 | duplicate of #4984 | 2022-04-20T00:54:36 | 2022-04-20T00:54:36 | {} | MEMBER |
vuejs | core | 1,104,059,307 | 5,761 | bodograumann | Not completely sure what you want to say, @coder-hxl .
The visible output is fine, but the `key` attributes contain duplicates.
You need to use the devtools to look at them. | 2022-04-20T15:20:44 | 2022-04-20T15:20:44 | {} | NONE |
vuejs | core | 1,104,176,270 | 5,763 | LinusBorg | This behavior is documented and not really avoidable due to some TS limitations:
https://vuejs.org/guide/typescript/options-api.html#caveats | 2022-04-20T16:51:44 | 2022-04-20T16:51:44 | {} | MEMBER |
vuejs | core | 1,104,823,263 | 5,769 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 6a8a428663c335bc530acfa48a95cb640525cf0f |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-21T07:40:02 | 2022-04-21T07:47:28 | {} | NONE |
vuejs | core | 1,105,322,036 | 5,773 | LinusBorg | In the body of `for (const key in newProps) {/* handle newProps */}`, which you commented out, we *do* check wether the old value is equal to the new one before doing an actual patch, so we kinds already do what `hasPropsChanged` does. though yes, we do a second loop over `oldProps` after this first one.
Your propos... | 2022-04-21T14:48:06 | 2022-04-21T14:48:41 | {} | MEMBER |
vuejs | core | 1,102,708,021 | 5,742 | justin-schroeder | @posva I think it is only possible if we control the type of object passed to us. In our scenario, we expect users to be able to pass in a `ref` or a `reactive` without discrimination — and in this scenario I don't think `customRef` is enough (I would love to be proved wrong).
From reading the Vue reactivity source ... | 2022-04-19T14:13:04 | 2022-04-19T14:13:04 | {} | NONE |
vuejs | core | 1,103,971,543 | 5,760 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 27e1c872446d834bd8496fda78a3a401e4670625 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-20T14:02:37 | 2022-04-20T14:06:04 | {} | NONE |
vuejs | core | 1,104,823,253 | 5,769 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 6a8a428663c335bc530acfa48a95cb640525cf0f |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-21T07:40:01 | 2022-04-21T07:42:37 | {} | NONE |
vuejs | core | 1,105,242,104 | 5,774 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8c85e168d471207410c0f0efb1d036951719c3d6 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-21T13:54:35 | 2022-04-21T13:55:32 | {} | NONE |
vuejs | core | 1,105,242,101 | 5,774 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8c85e168d471207410c0f0efb1d036951719c3d6 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-21T13:54:35 | 2022-04-21T13:59:38 | {} | NONE |
vuejs | core | 1,106,495,901 | 5,782 | edison1105 | 
work as expected.🤔 | 2022-04-22T13:06:23 | 2022-04-22T13:06:23 | {} | MEMBER |
vuejs | core | 1,106,217,434 | 5,781 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 66084bcc9ef971cdb79c4a3369e2afec7ced3bf8 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-22T09:05:08 | 2022-04-22T14:44:48 | {} | NONE |
vuejs | core | 1,102,833,043 | 5,742 | justin-schroeder | Thats interesting @posva — I suppose that works because the flush timing on those updates causes only 1 mutation to be made (wouldn't want multiple triggers).
Unfortunately — im not sure it works in our specific use case where v-model comes into play since the `emits` does not squash any events. A more fleshed out e... | 2022-04-19T16:08:04 | 2022-04-19T16:13:52 | {} | NONE |
vuejs | core | 1,103,367,117 | 5,756 | ted59438 | >You are passing the msg ref to the component, while you really want to pass msg.value
@LinusBorg However, if I pass ref to msg propety, there are some issue:
1. The msg result is "MyEvent123456" not MyEvent123456
![image](https://user-images.githubusercontent.com/55058204/164131241-02dcab2e-9653-40f4-8ec3-1fb7... | 2022-04-20T01:58:01 | 2022-04-20T02:37:29 | {} | NONE |
vuejs | core | 1,100,143,051 | 5,726 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | e9266aae308bbd60291daf2ff9bacb843a423b03 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-15T14:29:57 | 2022-04-20T12:49:34 | {} | NONE |
vuejs | core | 1,105,242,112 | 5,774 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8c85e168d471207410c0f0efb1d036951719c3d6 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-21T13:54:36 | 2022-04-21T13:57:03 | {} | NONE |
vuejs | core | 1,106,074,283 | 5,778 | LinusBorg | Your generated code does inject the CSS into the `<head>` at runtime, which it does for HMR, and only because you built without `NODE_ENV=production`, in other words - this is a development behavior, not production behavior.
1. Build with NODE_ENV=production
2. which will build an individual .css file in /dist
3. ... | 2022-04-22T06:57:42 | 2022-04-22T06:57:52 | {
"-1": 1
} | MEMBER |
vuejs | core | 1,105,823,298 | 5,777 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 7c1ac6bf4a54900513b67cebd748eb4243d021f8 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-21T22:29:13 | 2022-04-22T07:17:32 | {} | NONE |
vuejs | core | 1,105,823,317 | 5,777 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 7c1ac6bf4a54900513b67cebd748eb4243d021f8 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-21T22:29:15 | 2022-04-22T07:19:03 | {} | NONE |
vuejs | core | 1,106,411,207 | 5,778 | khanakia | Yes, but I do not want the external CSS to be generated. As I will have dynamic parameters for some styles e.g. color prop can be red, green, etc.
So I want `renderToString` from `vue/server-renderer` to give me the generated CSS also along with the HTML.
React.js does the same thing it gives the generated CSS wh... | 2022-04-22T11:14:19 | 2022-04-22T11:14:19 | {} | NONE |
vuejs | core | 1,106,217,455 | 5,781 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 66084bcc9ef971cdb79c4a3369e2afec7ced3bf8 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-22T09:05:09 | 2022-04-22T14:49:19 | {} | NONE |
vuejs | core | 1,102,685,332 | 5,756 | LinusBorg | You are passing the msg ref to the component, while you really want to pass `msg.value` | 2022-04-19T13:53:31 | 2022-04-19T13:53:31 | {} | MEMBER |
vuejs | core | 1,104,024,850 | 5,762 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 930b84eb8d5964e55dd7ae2c46eb7ef99a9fd1fc |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-20T14:50:23 | 2022-04-20T14:53:45 | {} | NONE |
vuejs | core | 1,104,601,246 | 5,761 | edison1105 | should be a bug.
this is because `v-if` with a default key.
| 2022-04-21T00:55:58 | 2022-04-21T02:47:51 | {} | MEMBER |
vuejs | core | 1,040,726,814 | 4,836 | netlify[bot] | ### <span aria-hidden="true">👷</span> Deploy Preview for *vue-sfc-playground* processing.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 73e035c161e85dba0a3a67e5044e86e06575febd |
|<span aria-hidden="true">🔍</span> Latest deploy log ... | 2022-02-15T19:51:48 | 2022-04-22T06:50:55 | {} | NONE |
vuejs | core | 1,106,090,616 | 5,780 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a776522131780b9342b808500ccc9428fe66e51e |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-22T07:15:14 | 2022-04-22T07:16:03 | {} | NONE |
vuejs | core | 1,106,588,733 | 5,772 | edison1105 | @LinusBorg
maybe this should be considered a bug, as it is inconsistent with vue2.🤔 | 2022-04-22T14:46:02 | 2022-04-22T14:46:02 | {} | MEMBER |
vuejs | core | 1,106,760,986 | 5,784 | posva | This is native behavior:
<img width="829" alt="Screenshot 2022-04-22 at 20 28 54" src="https://user-images.githubusercontent.com/664177/164773375-fb0841a6-9903-4f35-a48b-6f4f2efcc0b9.png">
Your props object has a property of `size` being `undefined` so it sets it and it produces that warning. Ensure the object ... | 2022-04-22T18:31:14 | 2022-04-22T18:31:14 | {} | MEMBER |
vuejs | core | 1,103,511,380 | 5,756 | LinusBorg | 1. Because this is what a stringified ref looks like.
2. The error happens because you pass a ref.
* If you *want* to pass a ref, use `type: Object` for the props definition.
* If you don't want to pass a ref, then don't pass a ref.
3. Yes, props are not unreffed, because they should not be refs, usually.
4.... | 2022-04-20T06:16:45 | 2022-04-20T06:17:33 | {} | MEMBER |
vuejs | core | 1,103,582,227 | 5,757 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). | 2022-04-20T07:53:01 | 2022-04-20T07:53:01 | {} | MEMBER |
vuejs | core | 1,103,813,921 | 5,657 | baixiaoyu2997 | hi ,i use `nuxt3 + element plus`，also have this issue， there this my can do `minimal` repo:
https://stackblitz.com/edit/nuxt-starter-hfqdfg?file=app.vue
error will show in `console` | 2022-04-20T11:15:19 | 2022-04-20T11:15:19 | {
"heart": 6
} | NONE |
vuejs | core | 1,101,978,974 | 5,749 | onurusluca | Just confirmed. It is a [Volar ](https://github.com/johnsoncodehk/volar/tree/master/extensions/vscode-vue-language-features)problem. With Vetur it is fine. Volar is becoming default though. Hope this will be fixed soon. I looked at the code. I will try to fix and request a pull.
Update
**FIX** :For now anyone wit... | 2022-04-19T04:19:07 | 2022-04-21T02:44:40 | {} | NONE |
vuejs | core | 1,105,395,736 | 5,773 | masterX89 | > Your proposed change would effectively _save_ one loop over the props keys when props did _not_ change, and _add_ one more loop over the props keys when props _did_ change.
>
> This _seems_ like a small net benefit in (the likely common) scenarios where you have more elements with unchanged props than elements wit... | 2022-04-21T15:40:51 | 2022-04-21T15:40:51 | {} | NONE |
vuejs | core | 1,102,266,962 | 5,750 | sxzz | There's a demo.
https://deploy-preview-5752--vue-sfc-playground.netlify.app/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmltcG9ydCB7IGdldEN1cnJlbnRJbnN0YW5jZSB9IGZyb20gJ3Z1ZSdcbmNvbnN0IGEgPSAnZm9vJyxcbiAgYTIgPSAnYmFyJ1xuY29uc3QgYTMgPSAnYmF6J1xuY29uc3QgYTQgPSBbJ3F1eCddXG5jb25zdCBhNSA9ICgnZnJlZCcsICd0aHVkJyk7XG... | 2022-04-19T08:16:59 | 2022-04-20T07:55:22 | {} | MEMBER |
vuejs | core | 1,104,145,569 | 5,763 | DrJume | Try:
```js
props: {
initValue: {
type: Object,
default: () => ({}),
},
},
```
In JavaScript, `() => {}` is a function which returns `undefined`, because the `{}` is an empty function block. When you want to return an empty object `{}`, use:
```js
props: {
initValue: {
... | 2022-04-20T16:33:03 | 2022-04-20T16:34:44 | {} | CONTRIBUTOR |
vuejs | core | 1,106,090,693 | 5,780 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a776522131780b9342b808500ccc9428fe66e51e |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-22T07:15:17 | 2022-04-22T07:17:58 | {} | NONE |
vuejs | core | 1,102,766,239 | 5,742 | posva | Can't you set one of the reactive properties only [like so](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IGN1c3RvbVJlZiwgcmVmLCByZWFjdGl2ZSwgd2F0Y2gsIHRvUmF3IH0gZnJvbSAndnVlJ1xuXG4vLyAtLS0tLS0tLS0tLSBTRVRVUCAoZW5kLXVzZXIgY29udHJvbGxlZCkgLS0tLS0tLS0tLVxuLy8gSnVzdCBhIGZsYWcgdG8gZGV0ZXJtaW5lIGlmI... | 2022-04-19T15:05:03 | 2022-04-19T15:05:03 | {} | MEMBER |
vuejs | core | 1,103,629,091 | 4,528 | foooooops | 请问找到问题了吗，我也是一样的问题 | 2022-04-20T08:41:34 | 2022-04-20T08:41:34 | {} | NONE |
vuejs | core | 1,100,142,982 | 5,726 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | e9266aae308bbd60291daf2ff9bacb843a423b03 |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-04-15T14:29:50 | 2022-04-20T12:49:41 | {} | NONE |
vuejs | core | 1,103,912,432 | 5,745 | SnowingFox | Before you use `Object.assign`, first understand that these two situations will output different results
```js
//first
const obj = Object.create({foo: 1}, {
bar: {
value: 2
},
})
// second
const obj = { ...{foo: 1}, ...{bar: { value: 2 }} }
```
the first result is
```js
{
"bar": 2
}
... | 2022-04-20T13:08:26 | 2022-04-20T13:09:04 | {} | CONTRIBUTOR |
vuejs | core | 1,104,177,517 | 5,765 | LinusBorg | Seems you spotted the right place. Up for a PR? | 2022-04-20T16:52:52 | 2022-04-20T16:52:52 | {} | MEMBER |
vuejs | core | 1,104,860,623 | 5,770 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d7e859f2be2c107f62eb04a65876120e21594443 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-21T08:22:41 | 2022-04-21T09:06:14 | {} | NONE |
vuejs | core | 1,106,093,354 | 5,775 | shadowings-zy | Hi, I create a PR #5780 to fix this issue | 2022-04-22T07:16:06 | 2022-04-22T07:16:06 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 1,106,217,439 | 5,781 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 66084bcc9ef971cdb79c4a3369e2afec7ced3bf8 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-22T09:05:08 | 2022-04-22T14:43:06 | {} | NONE |
vuejs | core | 1,102,629,108 | 5,752 | sxzz | I'm considering whether this feature is enabled by default, or is it an experimental feature and not enabled by default? | 2022-04-19T13:06:11 | 2022-04-19T13:06:11 | {} | MEMBER |
vuejs | core | 1,102,702,218 | 5,730 | westbrma | > I'm not sure what you mean when you say:
>
> > since all props are passed when you do not use defineComponent
>
> I suspect you mix this up with functional components which are a different thing.
Correct, that is what I meant (functional components). The only difference is one does not keep state, however th... | 2022-04-19T14:08:04 | 2022-04-19T14:08:04 | {} | NONE |
vuejs | core | 1,104,467,887 | 5,767 | lingosandi | Correction: this phenomenon doesn't only happen with Vite. The same test library built with @vue/cli exhibits identical behavior. | 2022-04-20T21:23:06 | 2022-04-20T21:23:06 | {
"+1": 22,
"hooray": 15
} | NONE |
vuejs | core | 1,104,595,326 | 5,768 | edison1105 | this is not supported yet.
see https://github.com/vuejs/core/issues/4294 | 2022-04-21T00:53:09 | 2022-04-21T00:53:09 | {} | MEMBER |
vuejs | core | 1,105,255,312 | 5,772 | btea | Yes, I have solved it like this at the moment, but in vue2 the appearance is as I expected. this is a [link](https://codesandbox.io/s/red-waterfall-6xzsqr?file=/src/App.vue). | 2022-04-21T14:03:47 | 2022-04-21T14:03:47 | {} | CONTRIBUTOR |
vuejs | core | 1,106,072,006 | 5,776 | LinusBorg | This plugin is for Vue 2. | 2022-04-22T06:53:47 | 2022-04-22T06:53:47 | {} | MEMBER |
vuejs | core | 1,040,726,801 | 4,836 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 73e035c161e85dba0a3a67e5044e86e06575febd |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-02-15T19:51:47 | 2022-04-22T06:57:16 | {} | NONE |
vuejs | core | 1,102,164,510 | 5,752 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ef61ebe326e91400407afc8bf3da53312e437f4d |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-19T06:59:47 | 2022-04-20T08:45:15 | {} | NONE |
vuejs | core | 1,102,164,542 | 5,752 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ef61ebe326e91400407afc8bf3da53312e437f4d |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-19T06:59:49 | 2022-04-20T08:48:33 | {} | NONE |
vuejs | core | 1,105,240,512 | 5,767 | rtek | @lingosandi the `vue3-bug-example` repo is missing the source. I might be having the same issue demoed at https://stackblitz.com/edit/vite-auuvqt?file=src%2Fcomponents%2FWrapper.vue
| 2022-04-21T13:53:26 | 2022-04-21T13:53:26 | {} | NONE |
vuejs | core | 1,106,071,754 | 4,836 | defaude | Trying to keep this up to date with the `main` branch here :) | 2022-04-22T06:53:20 | 2022-04-22T06:53:20 | {} | CONTRIBUTOR |
vuejs | core | 1,106,196,482 | 1,081 | loreberti89 |
> @aztalbot , this doesn't seem to work when using an empty object:
>
> ```
> const linkedNodes = reactive({})
> . . .
> Object.assign(links,{})
> ```
yes, same here, with empty object doesn't work. | 2022-04-22T08:40:21 | 2022-04-22T08:40:32 | {} | NONE |
vuejs | core | 1,106,419,069 | 5,779 | yuwu9145 | I will add tests soon | 2022-04-22T11:25:05 | 2022-04-22T11:25:05 | {} | CONTRIBUTOR |
vuejs | core | 1,106,508,305 | 5,782 | delowardev | @edison1105 Looks like it happens only in chromium browsers on Mac, Chrome (version: 100.0.4896.127), Brave & Edge has this issue; It works fine in Safari & Firefox. | 2022-04-22T13:19:29 | 2022-04-22T13:19:29 | {} | NONE |
vuejs | core | 1,103,921,415 | 5,745 | Justineo | > ```js
> const obj = Object.create({foo: 1}, {
> ```
It's `Object.assign`, not `Object.create`.
| 2022-04-20T13:17:18 | 2022-04-20T13:17:18 | {} | MEMBER |
vuejs | core | 1,104,860,627 | 5,770 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d7e859f2be2c107f62eb04a65876120e21594443 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-21T08:22:42 | 2022-04-21T09:04:37 | {} | NONE |
vuejs | core | 1,105,060,118 | 5,652 | coder-hxl | You can annotate components prop types using TypeScript。
reference: https://vuejs.org/guide/typescript/composition-api.html#typing-component-props
`
defineProps<{
num: bigint
}>
` | 2022-04-21T11:01:08 | 2022-04-21T11:07:01 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.