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,011,620,308 | 5,217 | AK47-dadada | 
我是在这里展开的 但是没用... | 2022-01-13T01:12:37 | 2022-01-13T01:12:37 | {} | NONE |
vuejs | core | 1,011,889,334 | 5,248 | LinusBorg | I don't know, outdated dependencies maybe? Hard to say without looking at the thing myself.
Anyway, if you want to debug this, please take it to chat.vuejs.org - I'm there alongside many other capable people.
This issue is resovled. | 2022-01-13T08:03:15 | 2022-01-13T08:03:15 | {} | MEMBER |
vuejs | core | 1,013,846,130 | 5,216 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/3031 | 2022-01-16T10:07:40 | 2022-01-16T10:07:40 | {} | MEMBER |
vuejs | core | 1,014,062,464 | 5,252 | AK47-dadada | 问题补充：
当A、B、M1、M2都被创建之后，从A到M1你会发现触发的是KeepAlive：如图：
也就是说从A或者B切换到M1和M2时都会触发KeepAlive，但是M1和M2之间切... | 2022-01-17T01:44:42 | 2022-01-17T01:45:24 | {} | NONE |
vuejs | core | 1,010,710,232 | 5,234 | LinusBorg | Sure, as I said I see the use here. So far it's just a blind spot in the spec. One that can be worked around with `:deep()` at least. | 2022-01-12T07:10:46 | 2022-01-12T07:11:08 | {} | MEMBER |
vuejs | core | 1,011,196,820 | 3,122 | zouyaoji | +1
```ts
const todoItemProps = {
item: {
type: String,
default: '',
required: false
},
complete: {
type: Boolean,
default: false,
required: false
}
}
export type TodoItemProps = ExtractPropTypes<typeof todoItemProps>
const myDodoItemProps: TodoItemProps = {
item: 'd'
... | 2022-01-12T16:01:46 | 2022-01-12T16:04:15 | {} | NONE |
vuejs | core | 1,011,270,977 | 5,246 | LinusBorg | This works as intended. Use a computed with a getter and setter to wrap a prop for v-model.
Wrote about it here: https://www.vuemastery.com/blog/vue-3-data-down-events-up/
VueUse also provides a composable to do this. | 2022-01-12T17:12:56 | 2022-01-12T17:12:56 | {} | MEMBER |
vuejs | core | 1,011,657,688 | 5,217 | AK47-dadada | @qq10137383 没玩过这种线上的demo，而且我的跟你的这种差不多，可能会比较麻烦.... 正在想办法给他搞demo | 2022-01-13T01:50:42 | 2022-01-13T01:50:42 | {} | NONE |
vuejs | core | 1,011,776,556 | 5,243 | lidlanca | an object passed to ref()
```
let o = {}
ref(o)
```
is equivalent to
`ref( reactive(o) )`
unref will return the inner value which is a reactive object.
if you need the original object for reason, use
`toRaw(unref(o)) === o `
| 2022-01-13T04:07:16 | 2022-01-13T04:07:16 | {} | CONTRIBUTOR |
vuejs | core | 1,011,793,727 | 5,243 | noootwo | > an object passed to ref()
>
> ```
> let o = {}
> ref(o)
> ```
>
> is equivalent to `ref( reactive(o) )`
>
> unref will return the inner value which is a reactive object.
>
> if you need the original object for reason, use `toRaw(unref(o)) === o `
I know that is also the right way to do, but I am afr... | 2022-01-13T04:48:49 | 2022-01-13T04:54:08 | {} | CONTRIBUTOR |
vuejs | core | 1,011,868,161 | 5,248 | HSchwichtenberg | Thank you very much @LinusBorg for this explanation, especially the details about the different behaviour of new Vue() vs. createApp.
Next, I would have addressed why `y: 0` in the options object doesn't work either :-). It's great that you recognized and addressed this upfront!
But I have the feeling that the d... | 2022-01-13T07:27:21 | 2022-01-13T07:28:22 | {} | NONE |
vuejs | core | 1,012,530,795 | 5,253 | LinusBorg | When using a method like you do, you would have to explicitly type `this: undefined` as the first argument of the method. | 2022-01-13T21:30:12 | 2022-01-13T21:30:12 | {} | MEMBER |
vuejs | core | 1,013,609,631 | 5,262 | MuTsunTsai | @edison1105 Thanks for the tip! It does solve the problem, but that doesn't seem to be consistent with the docs (https://v3.vuejs.org/api/application-config.html#compileroptions-comments), which says that the `compilerOptions.comments` is supposed to be `false` by default. | 2022-01-15T04:37:02 | 2022-01-15T04:37:02 | {} | NONE |
vuejs | core | 1,010,097,476 | 5,227 | aantipov | I found a package which clones and unrefs a **value** deeply it https://github.com/DanHulton/vue-deepunref
At the moment, it handles only primitives, pure objects and arrays. Neither `Array` or `Map`.
I think we can start from there and see if there is really a need in such a thing https://github.com/DanHulton/vue-... | 2022-01-11T15:51:28 | 2022-01-11T15:51:28 | {} | NONE |
vuejs | core | 1,011,898,460 | 5,248 | HSchwichtenberg | Of course I tried in a fresh project based on the latest CLI that npm gave me: @vue/cli 4.5.15
I will try at chat.vuejs.org, altough I have the impression, this might be an issue.
Thanks again for your help! | 2022-01-13T08:15:33 | 2022-01-13T08:15:33 | {} | NONE |
vuejs | core | 1,013,826,046 | 5,249 | yyx990803 | `computed(() => refroot.children.name)` | 2022-01-16T07:32:19 | 2022-01-16T07:32:19 | {} | MEMBER |
vuejs | core | 1,013,903,236 | 5,208 | levchak0910 | @yyx990803 amazing, thanks for quick fix! | 2022-01-16T16:06:08 | 2022-01-16T16:06:08 | {} | NONE |
vuejs | core | 1,009,520,343 | 4,735 | fyeeme | Seems new docs has been released at [https://staging.vuejs.org/](https://staging.vuejs.org/), and still in WIP | 2022-01-11T01:33:49 | 2022-01-11T01:33:49 | {} | NONE |
vuejs | core | 1,009,817,967 | 5,082 | jaulz | @posva any chance to have a look at it again after my explanation? thanks! 😊 | 2022-01-11T10:22:58 | 2022-01-11T10:22:58 | {} | CONTRIBUTOR |
vuejs | core | 1,010,672,561 | 5,234 | OpenGG | @LinusBorg
Noted.
Maybe css-modules fit this use case better, but the Vue community invested in scoped styles, so... | 2022-01-12T06:09:58 | 2022-01-12T06:10:26 | {} | NONE |
vuejs | core | 1,011,243,793 | 5,248 | LinusBorg | y isn't reactive. But since x is reactive, and the component is being re-rendered for that reason, the re-render prints the new value for `y`. You can verify that by commenting out the div that depends on `x`.
This would have behaved absolutely the same in Vue 2, I don't see what you refer to as a breaking change. | 2022-01-12T16:44:43 | 2022-01-12T16:45:07 | {} | MEMBER |
vuejs | core | 1,011,756,319 | 5,243 | noootwo | > Is this really a fix or a breaking change? This change would break the [following example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IHsgcmVmIH0gZnJvbSAndnVlJ1xuIFx0aW1wb3J0IHsgdXNlTWFwcGVkSWRzIH0gZnJvbSAnLi9fLmpzJ1xuICBcbiAgbGV0IGlkID0gMFxuICBjb25zdCBpZHMgPSByZWYoW10pXG4gIGNvbnN0IGFkZCA9... | 2022-01-13T03:34:55 | 2022-01-13T05:41:18 | {} | CONTRIBUTOR |
vuejs | core | 1,011,983,078 | 5,253 | jacekkarczmarczyk | Arrow function seems to work | 2022-01-13T10:06:48 | 2022-01-13T10:06:48 | {} | CONTRIBUTOR |
vuejs | core | 1,013,660,453 | 5,262 | edison1105 | see https://github.com/vuejs/vue-next/blob/master/packages/compiler-sfc/src/compileTemplate.ts#L54
Usually, the user does not manually call the `compileTemplate` method to compile the template, so there is no documentation here.
| 2022-01-15T10:46:28 | 2022-01-15T10:46:28 | {} | MEMBER |
vuejs | core | 1,013,829,685 | 5,241 | yyx990803 | It's already fixed but thanks for the PR. | 2022-01-16T08:04:54 | 2022-01-16T08:04:54 | {} | MEMBER |
vuejs | core | 1,013,830,293 | 5,219 | yyx990803 | `@vnode-mounted` 和 `onVnodeMounted` 实质上是等价的。原 issue 的问题在于没有用 `:` 导致传递的其实是一个字符串。错误也不是内存溢出而是爆栈。 | 2022-01-16T08:08:52 | 2022-01-16T08:08:52 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,009,717,900 | 5,220 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4736#issuecomment-934212424 | 2022-01-11T08:42:41 | 2022-01-11T08:42:41 | {} | MEMBER |
vuejs | core | 1,009,720,503 | 5,231 | posva | Hello, make sure to always provide a reproduction that follows the instructions at https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro.
Open a new issue with a reproduction that follows those instructions if you manage to create a boiled down reproduction. | 2022-01-11T08:46:38 | 2022-01-11T08:46:38 | {} | MEMBER |
vuejs | core | 1,011,760,305 | 5,217 | AK47-dadada | @qq10137383 搞了个线上demo居然没问题................................................................................................................................................
https://codesandbox.io/s/withered-fire-h2c35?file=/src/App.vue | 2022-01-13T03:40:31 | 2022-01-13T03:40:56 | {} | NONE |
vuejs | core | 1,011,866,864 | 5,250 | kalvenschraut | @LinusBorg okay I had a typo and that fixes it if the interface is defined within the component but not if the interface is imported like in [here](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG48L3NjcmlwdD5cbjx0ZW1wbGF0ZT5cbiA8Y29tcCA6c29tZS1vYmpl... | 2022-01-13T07:25:12 | 2022-01-13T07:26:49 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 1,011,874,750 | 5,250 | LinusBorg | Yes, but for that we already have #4294 | 2022-01-13T07:38:43 | 2022-01-13T07:38:43 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,011,900,870 | 5,248 | HSchwichtenberg | Just in case, you are interested: Here is the Vue CLI project with the same code as in <a href="https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuIDxkaXYgaWQ9XCJhcHBcIj5cbiAgIDxkaXY+eCBzaG91bGQgYmUgcmVhY3RpdmU6IHg9e3t4fX08L2Rpdj5cbiAgICA8ZGl2Pnkgc2hvdWxkIE5PVCBiZSByZWFjdGl2ZTogeT17e3kgfX08L2Rpdj5cbiAgICA8YnV0dG9uI... | 2022-01-13T08:19:18 | 2022-01-13T08:21:06 | {} | NONE |
vuejs | core | 1,011,986,854 | 5,253 | hcg1023 | > Arrow function seems to work
Can you give me a simple example? It doesn't seem to work if I try
[sfc.vuejs.org/](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbiAgY29uc3QgcHJvcHMgPSB3aXRoRGVmYXVsdHMoZGVmaW5lUHJvcHM8e1xuICBmbj86IChuYW1lOiBzdHJpbmcpID0+... | 2022-01-13T10:11:18 | 2022-01-13T10:11:18 | {} | CONTRIBUTOR |
vuejs | core | 1,012,717,185 | 5,253 | hcg1023 | > When using a method like you do, you would have to explicitly type `this: undefined` as the first argument of the method.
I specified this: undefined as you said, but it still does not work properly. I have tried three ways of writing, maybe you need to teach me
[sfc.vuejs.org](https://sfc.vuejs.org/#eyJBcHAu... | 2022-01-14T03:28:14 | 2022-01-14T03:28:14 | {} | CONTRIBUTOR |
vuejs | core | 1,013,206,259 | 5,228 | oswaldofreitas | @yyx990803 We got to migrate to Vue 3 using this amazing compat mode, however this is the last issue for us to fix before pushing forward to production. The more we wait on it the more conflicts we have which is pretty hard to handle since it's a big codebase, so... If you prioritize this relatively simple one I can pa... | 2022-01-14T15:06:01 | 2022-01-14T15:11:40 | {} | NONE |
vuejs | core | 1,013,276,008 | 5,228 | LinusBorg | Coffees don't buy a spot in a (non-existant) priority queue, I'm afraid 🙃
Do you have a lot of native event listeners in your codebase? If their occurrences aren't too numerous you should be able to just remove them and make sure the few components you declared them on have their non-native events declared with `em... | 2022-01-14T16:33:02 | 2022-01-14T20:39:58 | {} | MEMBER |
vuejs | core | 1,013,615,781 | 5,262 | edison1105 | @MuTsunTsai
`app.config.compilerOptions.comments` is a `runtime` option.
but in your scenario, there is no runtime. | 2022-01-15T05:24:50 | 2022-01-15T05:25:52 | {} | MEMBER |
vuejs | core | 1,013,862,006 | 5,256 | yyx990803 | 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-01-16T11:56:06 | 2022-01-16T11:56:06 | {} | MEMBER |
vuejs | core | 1,304,410,232 | 6,876 | xsjcTony | > Implemented in Vue Macros. [Read the Docs](https://vue-macros.sxzz.moe/macros/define-props.html)
Thanks, that seems good. Will have a try later on. | 2022-11-05T05:13:17 | 2022-11-05T05:13:17 | {} | NONE |
vuejs | core | 1,299,680,343 | 6,222 | xjtarzan | Uncaught (in promise) TypeError: parentComponent.ctx.deactivate is not a function
我也是一样的问题，热更新就报错 | 2022-11-02T07:14:00 | 2022-11-02T07:14:00 | {} | NONE |
vuejs | core | 1,302,841,917 | 7,019 | edison1105 | @zhangzhonghe thanks.
close as duplicated. | 2022-11-04T01:12:59 | 2022-11-04T01:12:59 | {} | MEMBER |
vuejs | core | 1,304,003,957 | 7,020 | xanf | @LinusBorg you've tagged this one as "need more info". Indeed, my initial description was a bit wrong (that's because behavior is different when HMR takes place), I've updated reproduction and issue description with more precise information
thank you! | 2022-11-04T18:51:11 | 2022-11-04T18:51:11 | {} | CONTRIBUTOR |
vuejs | core | 1,304,291,739 | 6,997 | posva | @webfansplz you are right, the problem happens with [an empty call](https://sfc.vuejs.org/#__SSR__eNp9kLtuwzAMRX+F0JIEiCV0dR0D3ToW6KrFdenYgfUARacoAv97qajI0AbZ+Lg4vJcX9RKjPi+oatWknqbIkJCXCHPnjwerOFnVWj+5GIjhYj1A8O9IZ6Q3wgG5H/fWrzBQcLAR0OY5a+7ptl369j1sd3BoC2ndFW1jymk5JA2ji3PHKB1AMz61rzjPoTFSZeltrfaq2KpcF/UpBS8hrlz7uxDvdb... | 2022-11-04T21:57:42 | 2022-11-04T21:57:42 | {} | MEMBER |
vuejs | core | 1,304,304,901 | 7,030 | posva | Could you try reproducing it with Vue as mentioned at https://github.com/posva/unplugin-vue-router/issues/86#issuecomment-1302645233 please? | 2022-11-04T22:21:11 | 2022-11-04T22:21:11 | {} | MEMBER |
vuejs | core | 1,304,389,239 | 6,997 | webfansplz | > @posva I believe there is a bug in the online sfc-playground because it works fine in my local sfc-playground.
>
> > @webfansplz you are right, the problem happens with [an empty call](https://sfc.vuejs.org/#__SSR__eNp9kLtuwzAMRX+F0JIEiCV0dR0D3ToW6KrFdenYgfUARacoAv97qajI0AbZ+Lg4vJcX9RKjPi+oatWknqbIkJCXCHPnjwerOFnV... | 2022-11-05T03:17:54 | 2022-11-05T03:17:54 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,306,577,823 | 6,781 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 505b35c8d67a46d836529be69745d340ea681ee4 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-08T03:28:25 | 2022-11-08T03:28:25 | {} | NONE |
vuejs | core | 1,306,617,357 | 6,913 | moushicheng | > More simplified [reproduction](https://sfc.vuejs.org/#eNp9Uj1vwjAQ/SsnLwRBYlhTQKq6dEIdkLp4geRSguIP2U4Yovz3nk1CEZVYEt/d87t399yzd2OyrkWWs40rbG08OPSt2QlVS6Othx4sVjBAZbWEGUFn99KHlmbMZzwEgYnKQhVaOQ+qlbAN15P1/C2kifpQS9StT5I5bHcBkXXHpsXFYgnr1WoVcBt+U0IaKPAoTXP0SBHAJrbM6dpWMPoKBpwKG35HsSW7qUvl0WQXpxWN1oe7Yiw4wXKImZAjxSEW7Oy9... | 2022-11-08T04:26:27 | 2022-11-08T04:55:48 | {} | CONTRIBUTOR |
vuejs | core | 1,299,658,852 | 6,994 | edison1105 | I feel this is not strictly called a memory leak. The dynamic creation of `computed` causes memory to continue to grow. This is a result of improper use of `computed`. Let's say you create 1000 objects dynamically and they are all being used, of course, the GC can't recycle them. | 2022-11-02T06:48:51 | 2022-11-02T06:48:51 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,301,190,779 | 6,994 | posva | Also note that you need to put the `computed()` at the level of the `script setup`. By being within a method, it's not attached to the component. But this is not a memory leak because this function
```ts
const pickComputed = (i) => {
return computed(() => {
return computedMap.value[i];
});
};
```
sh... | 2022-11-02T20:29:44 | 2022-11-02T20:29:44 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,302,021,671 | 7,015 | posva | A computed property (or your template) shouldn't throw an error. If you have a realistic reproduction that does create the same situation, please share it.
I checked the issue you linked and the problem is the Error global is not available in the template. I'm not sure if this is intentional so I opened https://gith... | 2022-11-03T12:22:48 | 2022-11-03T12:22:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,302,834,859 | 7,014 | zhangenming | I think it has something to do with vue.
react version code and vue version code exactly same,
but react not have this problem
| 2022-11-04T00:56:51 | 2022-11-04T00:56:51 | {} | CONTRIBUTOR |
vuejs | core | 1,304,011,845 | 7,020 | LinusBorg | Thanks. I now realize I forgot to hit the "Comment" button after setting that label. The comment would have read:
> Works fine for me:
>
> <img width="791" alt="image" src="https://user-images.githubusercontent.com/1444526/199943318-7804253e-5e92-496c-832b-0552e03e48c7.png">
Your clarifications help, thanks. ... | 2022-11-04T18:59:14 | 2022-11-04T18:59:14 | {} | MEMBER |
vuejs | core | 1,304,418,847 | 7,027 | jizai1125 | > I think codesandbox is using an outdated version of vue compiler. You should open an issue in Codesandbox repository
I use the same version 3.2.41. and i have another question to ask, why `v-model:foo-bar` not work when used with `@update:foo-bar`, but if i change to `v-model:fooBar`, they were all work. Intuiti... | 2022-11-05T06:07:19 | 2022-11-05T06:32:07 | {} | NONE |
vuejs | core | 1,304,383,940 | 7,017 | ben-lau | > Thanks for the PR! Pushing and popping into an array every time a component mounts is likely to have a negative impact on performance.
>
> Let's wait until we can confirm #7021 is indeed a bug
Thanks for your reply!
There are not many cases of using the stack, it is only used when the current stack needs to ... | 2022-11-05T02:46:56 | 2022-11-06T02:38:19 | {} | NONE |
vuejs | core | 1,304,801,557 | 6,954 | 2239559319 | please look at this, or help find someone to review @LinusBorg | 2022-11-06T13:27:29 | 2022-11-06T13:27:29 | {} | NONE |
vuejs | core | 1,305,805,316 | 6,961 | LinusBorg | tested in Brave, cannot reproduce. | 2022-11-07T15:46:14 | 2022-11-07T15:46:14 | {} | MEMBER |
vuejs | core | 1,305,907,408 | 6,944 | sxzz | Please be patient, just wait.
| 2022-11-07T16:58:25 | 2022-11-07T16:58:25 | {
"eyes": 1
} | MEMBER |
vuejs | core | 1,305,922,785 | 7,051 | sxzz | Duplicate of #3969? | 2022-11-07T17:07:05 | 2022-11-07T17:07:05 | {} | MEMBER |
vuejs | core | 1,306,568,120 | 6,777 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 2a50d03e5c6a737a860de349e0df16743c654582 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-08T03:16:04 | 2022-11-08T03:16:04 | {} | NONE |
vuejs | core | 1,306,581,753 | 6,808 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 00bbd29285f508ac03f7d45e52d6d5a2f6dca4d3 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-08T03:34:58 | 2022-11-08T03:38:40 | {} | NONE |
vuejs | core | 1,301,719,397 | 7,011 | edison1105 | @zhangzhonghe I also found it. the `currentRenderingInstance` got undefined when I debugged and the code jump into the runtime-dom module in the SFC playground. It's weird.
Please provide a fresh local repro if you can reproduce this problem. | 2022-11-03T07:11:10 | 2022-11-03T07:12:50 | {} | MEMBER |
vuejs | core | 1,302,819,918 | 7,019 | zhangzhonghe | Seems to be a duplicate of #6852. Note the current direct use of ```Text``` as a child of ```Fragment``` is problematic.
@posva @edison1105 The problem has been feedback from many people, hope to increase the priority. | 2022-11-04T00:27:30 | 2022-11-04T00:27:30 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,304,382,250 | 7,021 | ben-lau | Teleport component is not only a declarative component, but also I can't make it singleton. In many ui frameworks there are components rendered by functional calls, such as Notification. I don't think Teleport component is suitable for every situations. | 2022-11-05T02:36:15 | 2022-11-05T02:36:15 | {} | NONE |
vuejs | core | 1,305,778,133 | 4,662 | bogdantica | @yyx990803 Can't this issue be fixed? Is pending for more than one year and is marked as a "minor bug". We have to work with all kinds of workaround so the <style> from SFC to be imported when we make a custom element of a Vue component. | 2022-11-07T15:26:43 | 2022-11-07T15:26:43 | {
"confused": 1
} | NONE |
vuejs | core | 1,303,137,715 | 4,662 | murphybob | The question now is, does the next person say +100 or +19 🤔 | 2022-11-04T08:56:42 | 2022-11-04T08:56:42 | {
"laugh": 8
} | NONE |
vuejs | core | 1,282,515,108 | 6,902 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 20d9ca35aedc1a978a5d098a926a80d411bd1488 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-10-18T14:47:03 | 2022-11-08T03:21:39 | {} | NONE |
vuejs | core | 1,306,770,851 | 7,049 | zhangzhonghe | @yyx990803 你好，我发现这个 PR 与 #6809 重复了，并且你已经合并了 6809。但是我有一个疑问，就是 6809 的修复并不能通过我提供的测试，热更新的时候它没有调用旧组件的```unmounted```生命周期函数。
我觉得被```KeepAlive```包裹的组件热更新的时候应该把旧的组件给卸载了，因为新的组件是重新挂载的。不知道我对不对，望赐教。(●'◡'●) | 2022-11-08T07:52:30 | 2022-11-08T07:52:30 | {} | MEMBER |
vuejs | core | 1,299,885,161 | 6,811 | adamjedlicka | Here is a unit test:
```
test('post flush watchers in toggled components', async () => {
let cnt = 0
const CompA = {
template: `<div>A</div>`,
setup: async () => {
const route = inject<any>('route')
watch(
() => route.value,
() => cnt++,
... | 2022-11-02T08:59:58 | 2022-11-02T08:59:58 | {} | CONTRIBUTOR |
vuejs | core | 1,302,864,414 | 7,014 | zhangenming | "if you remove display: flex rule of body. It will disappear."
好像并不是. 如果你再手动滚动一下滚动条, 这个bug就会重新出现.
而且这个bug只在"三个一"出现在屏幕的时候出现
It doesn't seem to be. If you scroll the scroll bar manually again, the bug will reappear.
And the bug only appears when "three red color '一'" appear on the screen | 2022-11-04T01:58:20 | 2022-11-04T02:00:31 | {} | CONTRIBUTOR |
vuejs | core | 1,303,024,022 | 6,876 | sxzz | Implemented in Vue Macros.
[Read the Docs](https://vue-macros.sxzz.moe/macros/define-props.html) | 2022-11-04T06:15:03 | 2022-11-04T06:15:03 | {} | MEMBER |
vuejs | core | 1,306,828,521 | 7,049 | zhangzhonghe | > @zhangzhonghe 预期的行为是：当KeepAlive卸载的时候才卸载其内部组件。 我觉得热更新时是否调用内部组件的unmounted没那么重要，毕竟只是开发环境下的行为。
是的。但是修改后的新组件是会调用 ```mounted``` 的，这可能产生一些问题。比如，如果用户在 ```mounted``` 阶段注册了一些监听器且需要在 ```unmounted``` 阶段销毁的话，就会有问题，因为旧组件的 ```unmounted``` 没有被调用，也就无法销毁，如果这种情况下频繁热更新的话可能会导致内存泄漏。 | 2022-11-08T08:34:57 | 2022-11-08T08:34:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,301,670,763 | 7,014 | zhangenming | The scroll bar will scroll accidentally,
only when Drag the scroll bar to the bottom(untill see the three red dom )
opposite, the scroll will NOT scroll accidentally. | 2022-11-03T05:38:06 | 2022-11-03T05:38:06 | {} | CONTRIBUTOR |
vuejs | core | 1,302,865,528 | 7,017 | ben-lau | Related to #7021 | 2022-11-04T02:01:00 | 2022-11-04T02:01:00 | {} | NONE |
vuejs | core | 1,304,363,487 | 7,017 | edison1105 | There is a same PR in vue2 https://github.com/vuejs/vue/pull/12866 | 2022-11-05T01:00:50 | 2022-11-05T01:00:50 | {} | MEMBER |
vuejs | core | 1,304,775,756 | 6,944 | tuchg | > LGTM, thanks!
hi, it seems to be forgotten 😭 , could you request a maintainer to approve or review it? (first-time contributor 👀
| 2022-11-06T11:09:24 | 2022-11-06T11:09:24 | {} | NONE |
vuejs | core | 1,305,935,130 | 7,051 | qmhc | @sxzz All right, thanks for you reply, I close this PR. | 2022-11-07T17:15:54 | 2022-11-07T17:15:54 | {} | NONE |
vuejs | core | 1,300,063,021 | 6,997 | webfansplz | > The example on the docs is missing the serialization of the data. Without it, the client is not aware of the initial state when it renders and thus creates a Hydration mismatch. I would say this should be fixed in docs instead
![image](https://user-images.githubusercontent.com/22515951/199472033-63570778-2872-48fc... | 2022-11-02T11:02:49 | 2022-11-02T11:04:20 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,302,022,692 | 7,016 | posva | Thanks but see https://github.com/vuejs/core/issues/7015#issuecomment-1302021671
If `instance` could be undefined, the types should be adapted so I don't think this is fixing an expected scenario | 2022-11-03T12:23:47 | 2022-11-03T12:23:47 | {} | MEMBER |
vuejs | core | 1,302,243,362 | 7,018 | posva | console was requested in the past but it was decided not to be added. I can’t find the issue now. Maybe it was in vue repo and not in core? | 2022-11-03T15:00:02 | 2022-11-03T15:00:02 | {} | MEMBER |
vuejs | core | 1,304,420,357 | 7,021 | posva | Note that the declarative approach is often the preferred way and that you could perfectly do the same you are doing with a Teleport component and an array of notifications | 2022-11-05T06:19:04 | 2022-11-05T06:19:04 | {} | MEMBER |
vuejs | core | 1,304,700,184 | 7,031 | btea | @edison1105 It seems to overlap with #6636 . | 2022-11-06T02:34:46 | 2022-11-06T02:34:46 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,305,323,769 | 7,009 | adamjedlicka | So apparently this completely breaks post-flsuh watchers in Suspense. I'll add more tests and try to do a proper fix. | 2022-11-07T09:24:51 | 2022-11-07T09:24:51 | {} | CONTRIBUTOR |
vuejs | core | 1,306,550,247 | 6,636 | yyx990803 | I decided to remove the unit check altogether since due to vendor prefixes and custom properties, the check seems to be unnecessarily strict for little value (for the end user, the browser render result will be the same). | 2022-11-08T02:52:55 | 2022-11-08T02:52:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,306,558,300 | 6,631 | yyx990803 | FYI the key in this case is redundant anyway. | 2022-11-08T03:04:46 | 2022-11-08T03:04:46 | {} | MEMBER |
vuejs | core | 1,306,761,828 | 7,042 | zhangzhonghe | Duplicate of #6222 | 2022-11-08T07:42:02 | 2022-11-08T07:42:46 | {} | MEMBER |
vuejs | core | 1,306,784,009 | 6,591 | binvb | thank you , help me a lot | 2022-11-08T08:04:24 | 2022-11-08T08:04:24 | {} | NONE |
vuejs | core | 1,306,791,164 | 7,049 | edison1105 | @zhangzhonghe
预期的行为是：当KeepAlive卸载的时候才卸载其内部组件。
我觉得热更新时是否调用内部组件的unmounted没那么重要，毕竟只是开发环境下的行为。 | 2022-11-08T08:09:56 | 2022-11-08T08:09:56 | {} | MEMBER |
vuejs | core | 1,300,251,117 | 7,010 | edison1105 | It works fine in the latest commit because this [PR](https://github.com/vuejs/core/pull/4512) had been merged and not released yet, so not working in 3.2.41 yet. | 2022-11-02T12:13:26 | 2022-11-02T12:13:26 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,302,329,445 | 7,018 | posva | The only use case would be passing `Error()` as a parameter but then we would also have to support the `Promise` global (@znck said offline)
Whatever direction this take, at least we will have a reference issue for future feature requests | 2022-11-03T16:00:43 | 2022-11-03T16:00:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,304,999,191 | 7,014 | zhangenming | So is this really not a vue bug?
@posva @edison1105 | 2022-11-07T02:20:08 | 2022-11-07T02:20:08 | {} | CONTRIBUTOR |
vuejs | core | 1,305,357,171 | 5,864 | renatodeleao | Have a very similar usecase — using [`portal-vue`](https://github.com/LinusBorg/portal-vue) to make it work — but would be nice if `Teleport` supported these scenarios. | 2022-11-07T09:53:36 | 2022-11-07T09:53:36 | {} | NONE |
vuejs | core | 1,306,204,455 | 6,380 | posva | There seem to be more types that are being reported as missing by api-extractor.
I wonder if some of these should be exported but prefixed with an `_` and marked as `@internal` so we don't expose types that aren't meant to be used in userland like this one. | 2022-11-07T21:17:31 | 2022-11-07T21:17:31 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,293,544,121 | 6,975 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ec4b0e9e623434967dbbaf0c4d4bfcdef71d3185 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-10-27T13:40:57 | 2022-11-08T05:37:53 | {} | NONE |
vuejs | core | 1,302,839,244 | 7,014 | zhangenming | please look at this video
https://www.haolu.com/share/V00VJHGR2G/67fca5c391a751f1bef4a1c67625fa5a
@posva | 2022-11-04T01:06:41 | 2022-11-04T01:06:41 | {} | CONTRIBUTOR |
vuejs | core | 1,302,841,801 | 7,014 | zhangenming | and more,
if you Uncomment 59 line code
`// r[5].part = '反';`
this bug will disappear
| 2022-11-04T01:12:40 | 2022-11-04T02:05:37 | {} | CONTRIBUTOR |
vuejs | core | 1,304,288,666 | 7,021 | posva | I don't think this is a good idea, you should use a Teleport component instead. Is there anything blocking you from using Teleport? | 2022-11-04T21:51:56 | 2022-11-04T21:51:56 | {} | MEMBER |
vuejs | core | 1,305,665,113 | 7,047 | baiwusanyu-c | 先别加key, 或者key使用其他值，v-model导致数组值变化，使得v-for中绑定的key发生变化，重新渲染了input，从而失去焦点
Don't add a key, or use other values for the key, v-model causes the array value to change, which makes the key bound in v-for change, re-renders the input, and loses focus | 2022-11-07T14:05:34 | 2022-11-07T14:29:51 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,305,725,501 | 7,047 | LinusBorg | as @baiwusanyu-c explains, you would need to use a stable key. | 2022-11-07T14:49:37 | 2022-11-07T14:49:37 | {} | MEMBER |
vuejs | core | 1,299,905,369 | 4,476 | gnuletik | > Why turn your Vue Components into Web Components if you can only use them in other Vue apps because they depend on provide/inject?
My usecase was to integrate Vue into a MVC framework like Django, which already provides its own template system.
The web components allows you to load vue components and inject varia... | 2022-11-02T09:08:30 | 2022-11-02T09:09:19 | {} | NONE |
vuejs | core | 1,302,225,241 | 7,018 | m0ksem | In case there will be Error global, shouldn't we also be able to use `console` in template context?
This might be more helpful than Error in debugging.
```vue
<template>
<va-tree-view :nodes="nodes">
<template #content="node">
{{ console.log(node) }}
</template>
</va-tree-view>
</template>... | 2022-11-03T14:47:01 | 2022-11-03T14:47:01 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.