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 | 960,538,646 | 4,358 | Coderclc | https://github.com/Coderclc/vue3-vite-test 问题是运行时的问题,既在项目启动以后导入foo这个组件就会有此提示,还遇到一个相似的问题且没有任何提示,既在运行时手动切换img src 绑定的图片,会加载不出来, 同样的这两个问题都是重启即可解决.我不知道这个现象是否应该如此,虽然vite重新启动很快,但开发时经常会感到疑惑

| 2021-11-04T08:13:38 | 2021-11-04T08:13:38 | {
"+1": 1
} | NONE |
vuejs | core | 958,939,454 | 4,890 | zhangyuang | > > Mock window object is common in some ssr program for compatibility
>
> I would say it's the opposite: Mocking the window object in Node.js is mostly done for testing but should be avoided as it will break many universal libraries relying on that check. Checking `typeof navigator` is another possibility
emmm,m... | 2021-11-03T11:23:24 | 2021-11-04T08:27:59 | {} | CONTRIBUTOR |
vuejs | core | 963,863,823 | 4,923 | LinusBorg | This is not a bug report, this is a usage question. Please use chat.vuejs.org for questions. | 2021-11-09T06:51:21 | 2021-11-09T06:51:21 | {} | MEMBER |
vuejs | core | 965,057,173 | 4,928 | LinusBorg | Vue's SSR renderer doesn't validate the HTML that you provide through `v-html`, so that's kinda expected - `<br />`is invalid HTML.
We could theoretically parse and validate the HTML in the renderer, but I am doubtful that would worth it. | 2021-11-10T11:51:42 | 2021-11-10T11:51:55 | {} | MEMBER |
vuejs | core | 960,571,649 | 4,358 | Coderclc | @zhenzhenChange
I was triggered stably under the condition of vite + ts + syntactic sugar hot update, which caused me to restart every time I introduced a component.
But when I switch the demo to defineComponent, the following problems disappear
1. Invalid vnode type when creating vnode: undefined.
2. The imported ... | 2021-11-04T09:06:01 | 2021-11-05T09:56:44 | {
"+1": 1
} | NONE |
vuejs | core | 963,223,171 | 4,917 | edison1105 | I look into the code and find another problem. see [sfc](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICAgIDxkaXY+XG4gICAgICAgIDEyM1xuICAgIDwvZGl2PlxuPC90ZW1wbGF0ZT5cblxuPHNjcmlwdCBzZXR1cD5cbmRlZmluZUV4cG9zZSh7IGZvbzogMTIzIH0pXG4oKCkgPT4ge1xuICAgIGNvbnNvbGUubG9nKCctLS0tJyk7XG59KSgpO1xuXG48L3NjcmlwdD5cbiIsIml... | 2021-11-08T14:36:43 | 2021-11-08T14:36:43 | {} | MEMBER |
vuejs | core | 965,203,904 | 4,891 | edison1105 | @languanghao thanks for your demo and I made a online [demo](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICAgIDxkaXY+XG4gICAgICAgIDxidXR0b24gdHlwZT1cImJ1dHRvblwiIEBjbGljaz1cImhhbmRsZUNsaWNrXCI+Y2xpY2s8L2J1dHRvbj5cbiAgICA8L2Rpdj5cbiAgPHN1c3BlbnNlPlxuICAgIDxkaXY+XG4gICAgICA8Y29tcG9uZW50IDppcz1cIkNoaWxkXCIgcmVm... | 2021-11-10T13:57:40 | 2021-11-10T13:57:40 | {} | MEMBER |
vuejs | core | 965,294,707 | 4,929 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/1409 | 2021-11-10T14:40:17 | 2021-11-10T14:40:17 | {} | MEMBER |
vuejs | core | 966,326,416 | 4,780 | martinbean | @sixpeteunder Unfortunately not. But, y’know, valid Vue components not compiling is apparently not a bug, so… 🤷♂️ | 2021-11-11T14:02:31 | 2021-11-11T14:02:31 | {
"confused": 1
} | NONE |
vuejs | core | 961,377,448 | 4,889 | WORMSS | Nice. I had only just started doing Vue3 for about 20 minutes.. but I am super nosey of "why/how/what" things are doing and just started digging into the .d.ts files as a good place to start. Spotted that.
Hope I can help more in the future once I got a bit of time under my belt. | 2021-11-04T20:06:37 | 2021-11-04T20:06:37 | {
"rocket": 1
} | NONE |
vuejs | core | 961,627,978 | 4,871 | yyx990803 | Because the AST analysis works at source level, not generated-code level. This is required to analyze TS types.
I do not recommend using coffeescript with Vue 3 anyway, there's little benefit. | 2021-11-05T04:58:02 | 2021-11-05T04:58:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 962,424,475 | 4,908 | ygj6 | vitejs/vite#5561 use `resolveTemplateUsageCheckString` to determine whether the reference variable in the template has been changed.
```ts
function needGlobHMR(
prev: SFCDescriptor | null,
next: SFCDescriptor | null
): boolean {
const isDynamicUpdate = resolveTemplateUsageCheckString(prev!) !== resolveTem... | 2021-11-06T09:28:30 | 2021-11-06T09:28:30 | {} | MEMBER |
vuejs | core | 962,438,348 | 4,903 | edison1105 | @sqal
A vnode is the result of template compilation. If you want to create a vnode with the h function, you have to make sure it is correct and can be rendered into the DOM. | 2021-11-06T11:35:31 | 2021-11-06T11:35:31 | {} | MEMBER |
vuejs | core | 962,922,266 | 4,914 | edison1105 | duplicated of #4605 | 2021-11-08T08:33:15 | 2021-11-08T08:33:15 | {} | MEMBER |
vuejs | core | 961,571,847 | 4,897 | ShaneLee-9 | > 很快会有新版本发布,还是必须降级?(以及哪个版本?)
Currently it is possible to explicitly pass a boolean value to prop. e.g:
```html
<Children
:selectable="true"
/>
``` | 2021-11-05T02:08:52 | 2021-11-05T02:08:52 | {} | NONE |
vuejs | core | 963,864,672 | 4,921 | LinusBorg | ~~Deep watching is only possible on reactive data - watching relies on reactivity. So you are asking for the data in a `shallowReactive` to be reactive. Then just use `reactive`~~
Apologies, I totally misread. | 2021-11-09T06:53:18 | 2021-11-09T06:54:29 | {} | MEMBER |
vuejs | core | 965,398,066 | 4,928 | LinusBorg | ERROR: type should be string, got " https://www.tiny.cloud/docs-3x/reference/Configuration3x/Configuration3x@element_format/" | 2021-11-10T15:28:49 | 2021-11-10T15:28:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 965,768,169 | 4,662 | raffobaffo | @lucasantunes-ciandt sorry but not TS for me on this project. This is pretty much the hack I built:
```
import { defineCustomElement as rootDefineCustomElement } from 'vue'
[...]
export const getChildrenComponentsStyles = (component) => {
let componentStyles = [];
if (component.components) {
component... | 2021-11-10T21:38:01 | 2021-11-10T21:38:01 | {
"+1": 1
} | NONE |
vuejs | core | 966,320,650 | 4,891 | languanghao | @edison1105 thank you, I will try it. | 2021-11-11T13:54:38 | 2021-11-11T13:54:38 | {} | NONE |
vuejs | core | 961,727,012 | 4,903 | zhaozhongyu | return a render function will work. and i did not think it is a bug.
```
return () => h('div', {
style: { color: isChecked ? 'green' : 'red' },
}, `[ ${id} ] ${isChecked ? 'checked' : 'unchecked'}`)
``` | 2021-11-05T08:59:47 | 2021-11-05T08:59:47 | {
"+1": 1
} | NONE |
vuejs | core | 962,747,352 | 4,906 | lzm0x219 | > > Declare a component like this, props are props that default to the browser’s native tags. Props cannot get name and age...😟 It seems to be inconsistent with the expected behavior, maybe I misunderstood it?
>
> I think you should define props.
>
> ```js
> interface TestProps {
> name: string;
> age?: n... | 2021-11-08T02:03:14 | 2021-11-08T02:03:14 | {} | NONE |
vuejs | core | 964,103,798 | 4,891 | edison1105 | @languanghao
I have done a test and it works fine in a production environment. Could you provide a demo with the problem? | 2021-11-09T12:23:36 | 2021-11-09T12:23:36 | {} | MEMBER |
vuejs | core | 964,762,807 | 4,891 | languanghao | @edison1105 I can reproduce the bug.
When the dyanmic component ref to a component with top level `await`, the `ref` will get incorrect value.
Maybe the bug is here
```
const refValue = vnode.shapeFlag & 4
/* STATEFUL_COMPONENT */
? getExposeProxy(vnode.component) || vnode.component.proxy : vnode.el;
```... | 2021-11-10T03:55:53 | 2021-11-10T03:55:53 | {} | NONE |
vuejs | core | 965,896,326 | 4,927 | xiuxiuyifan | You need to write <script></script> on top of <script setup></script> | 2021-11-11T00:56:02 | 2021-11-11T00:56:02 | {} | NONE |
vuejs | core | 966,324,001 | 4,780 | peter-mghendi | I'm having this issue with Vue 3.1.4, Typescript and the Options API. @martinbean did you find a way around this? It has been (seemingly) randomly showing up in my builds. | 2021-11-11T13:59:15 | 2021-11-11T13:59:15 | {} | NONE |
vuejs | core | 966,608,088 | 4,936 | LinusBorg | You should just not type your prop with `Ref<string>` in the first place, as you receive an unwrapped object. | 2021-11-11T20:36:12 | 2021-11-11T20:36:12 | {} | MEMBER |
vuejs | core | 965,330,394 | 4,930 | edison1105 | see https://github.com/vuejs/vue-next/issues/4891#issuecomment-964762807
the component is not resolved when `setRef`.

| 2021-11-10T14:57:06 | 2021-11-10T15:00:32 | {} | MEMBER |
vuejs | core | 966,642,541 | 4,662 | lucasantunes-ciandt | @raffobaffo Thank you so much! I thought you were literally extending the whole file :sweat_smile:
I tried this code here, but unfortunately it doesn't work. I suppose it expects the components are all custom elements, `e.g.` `Component.ce.vue` and `ChildComponent.ce.vue`.
When my components are named `Component.... | 2021-11-11T21:35:21 | 2021-11-11T21:36:32 | {} | NONE |
vuejs | core | 960,802,402 | 4,897 | bodograumann | Will there be a new release soon, or do I have to downgrade? (and to which version?) | 2021-11-04T12:27:11 | 2021-11-04T12:27:11 | {} | NONE |
vuejs | core | 961,703,961 | 4,358 | ygj6 | Oh, I finally understand what the problem is. When we use `lang = 'ts'` in `script setup`.
Vue deletes unused imports. In this case, when we update the template, hmr only updates the template.
So the exact reproduction procedure is this.
* download [sfc.vuejs.org](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRl... | 2021-11-05T08:19:06 | 2021-11-05T08:19:06 | {
"+1": 3
} | MEMBER |
vuejs | core | 963,024,966 | 4,916 | sqal | Most likely your problem [is in this line](https://github.com/webtutsplus/ecommerce-ui/blob/vue-bug/src/views/Product/EditProduct.vue#L63). You are setting a new product, but it may be undefined because the list of products hasn't been fetched yet from the API, therefore you can't access property **name** (product.nam... | 2021-11-08T10:44:10 | 2021-11-08T10:44:10 | {} | CONTRIBUTOR |
vuejs | core | 966,207,743 | 4,930 | edison1105 | as a workaround, from @sodatea
`defineExpose` should run before the first await.
see [demo](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICAgIDxkaXY+XG4gICAgICAgIDxidXR0b24gdHlwZT1cImJ1dHRvblwiIEBjbGljaz1cImhhbmRsZUNsaWNrXCI+Y2xpY2s8L2J1dHRvbj5cbiAgICA8L2Rpdj5cbiAgPHN1c3BlbnNlPlxuICAgIDxkaXY+XG4gICAgICA8Y2... | 2021-11-11T11:00:42 | 2021-11-11T11:00:42 | {} | MEMBER |
vuejs | core | 865,847,677 | 1,033 | lcoder | I create a vue project with vue-cli. the project has a dependency of package named B. B has a dependency with react types.
for example:
```tsx
import type { PropsWithChildren } from 'react';
```
then my project emit errors:
> Type '{ children: Element[]; class: string; }' is not assignable to type 'DetailedH... | 2021-06-22T10:03:48 | 2021-11-04T07:24:42 | {
"+1": 1,
"eyes": 2
} | NONE |
vuejs | core | 961,176,485 | 4,901 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4736#issuecomment-934212424 | 2021-11-04T15:51:49 | 2021-11-04T15:51:49 | {} | MEMBER |
vuejs | core | 961,572,839 | 4,896 | danranVm | 
https://v3.vuejs.org/guide/reactivity.html#how-vue-tracks-these-changes
Does this seem inconsistent with the description in the documentation, or is there a problem with my understanding?
In addition, ... | 2021-11-05T02:11:20 | 2021-11-05T02:11:20 | {} | NONE |
vuejs | core | 961,575,851 | 4,904 | yyx990803 | Thanks, but it's better to let pnpm update the lockfile. See 7a5c7844 | 2021-11-05T02:18:41 | 2021-11-05T02:18:41 | {
"+1": 1
} | MEMBER |
vuejs | core | 962,922,926 | 4,891 | edison1105 | @languanghao I will check it later. | 2021-11-08T08:34:20 | 2021-11-08T08:34:20 | {} | MEMBER |
vuejs | core | 962,937,424 | 629 | PavelShishchits | @sh-mokong
Hi, is it possible to pass slots and events then we are mounting components this way `createApp(PlusMinus,{count:0}).mount('#app');` ? | 2021-11-08T08:56:06 | 2021-11-08T08:56:39 | {} | NONE |
vuejs | core | 975,193,717 | 4,982 | JangCool | @ygj6 Okay, I got it. I was told it might be supported later. May I know the schedule? | 2021-11-22T07:13:39 | 2021-11-22T07:13:39 | {
"+1": 1
} | NONE |
vuejs | core | 977,758,168 | 4,988 | posva | Do you have a failing test of the behavior that is currently not working correctly? It could also be posted using https://sfc.vuejs.org | 2021-11-24T10:50:20 | 2021-11-24T10:50:20 | {} | MEMBER |
vuejs | core | 978,095,752 | 4,309 | adamdehaven | Also, would this inject styles into the shadow DOM from child components imported within the `defineCustomElement` component that originate from external packages?
As an example, if I define and export a component with `defineCustomElement`, but within that element is a button component, imported from an external p... | 2021-11-24T17:44:54 | 2021-11-24T17:44:54 | {} | NONE |
vuejs | core | 979,197,344 | 4,986 | jvgpinheiro | Thank you | 2021-11-25T13:05:08 | 2021-11-25T13:05:08 | {} | NONE |
vuejs | core | 979,367,825 | 4,873 | LinusBorg | Agreed, will make the necessary change | 2021-11-25T17:12:41 | 2021-11-25T17:12:41 | {} | MEMBER |
vuejs | core | 979,988,844 | 5,005 | LinusBorg | Please provide a runnable reproduction.
v-show uses inline styles, so it should always have precedence over any classes from bootstrap. | 2021-11-26T13:44:44 | 2021-11-26T13:45:16 | {} | MEMBER |
vuejs | core | 979,989,851 | 4,987 | Bigfish8 | Can it also fix #4999 ?It seems i did repeated work... | 2021-11-26T13:46:26 | 2021-11-26T13:46:26 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 980,519,228 | 4,960 | LinusBorg | All of these "too many options" existed in a similar form ever since Vue was created. adding top-level await would also not remove these 3 existing ways, it would [add another one on top](https://xkcd.com/927/), so I don't really see an argument *for* top-level await in that reasoning specifically.
What you are argu... | 2021-11-27T07:37:09 | 2021-11-27T07:37:09 | {} | MEMBER |
vuejs | core | 982,356,009 | 5,018 | yangliguo7 | @LinusBorg I've used this method before, but it doesn't work | 2021-11-30T07:26:17 | 2021-11-30T07:26:17 | {} | CONTRIBUTOR |
vuejs | core | 975,207,924 | 4,975 | LinusBorg | it's not contained in the *final* props because it's explicitly filtered out of the props during parsing in line 558 in the code snippet above. | 2021-11-22T07:39:13 | 2021-11-22T07:39:34 | {} | MEMBER |
vuejs | core | 975,214,291 | 4,975 | wood3n | So it's on purpose or it's a bug? Now I have to use regexp to match `v-pre` attribute between tags😥 | 2021-11-22T07:50:53 | 2021-11-22T07:50:53 | {} | NONE |
vuejs | core | 980,503,570 | 5,006 | caozhong1996 | Oh, I think it's unnecessary, we just need escape `"'&<>`. They are HTML reserved characters. | 2021-11-27T05:02:07 | 2021-11-27T05:03:35 | {} | CONTRIBUTOR |
vuejs | core | 975,532,565 | 4,975 | wood3n | > What's the purpose of getting the `v-pre` tag?
>
> Note that `v-pre` is a special directive that affects AST shape in that inside an element with `v-pre`:
>
> 1. Mustaches are ignored and treated as plain text
> 2. Directives inside `v-pre` are parsed as plain attributes
>
> This is similar to how you won't... | 2021-11-22T13:39:13 | 2021-11-22T13:39:13 | {} | NONE |
vuejs | core | 976,208,596 | 4,975 | yyx990803 | I think you should maybe use some other attributes for this purpose since `v-pre` has its own special meaning in templates. | 2021-11-23T06:57:21 | 2021-11-23T06:57:21 | {} | MEMBER |
vuejs | core | 976,223,928 | 4,984 | ygj6 | Maybe you could consider changing `keeps.value = ["tab2"];` to `keeps.value = ["tab1"]; ` as workaround.
```vue
setup() {
const cn = ref("tab1");
// use ref
const keeps = ref([]);
keeps.value = ["tab2"]; -------------> keeps.value = ["tab1"];
setTimeout(() => {
keeps.val... | 2021-11-23T07:33:08 | 2021-11-23T07:33:08 | {} | MEMBER |
vuejs | core | 977,145,525 | 4,986 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-11-23T20:30:08 | 2021-11-23T20:30:08 | {} | CONTRIBUTOR |
vuejs | core | 977,197,381 | 4,950 | yuwu9145 | @kadiryazici your component works as per my testing

| 2021-11-23T21:48:40 | 2021-11-23T21:48:40 | {} | CONTRIBUTOR |
vuejs | core | 977,618,635 | 4,737 | rgaudy | I would like to point out that I encountered the exact same problem. In context I used Teleports to simulate the z-index property in a SVG tree, the feature being especially convenient for this. However this issue forced me to change the structure of the app, to avoid using Teleports. So merging the pull request would ... | 2021-11-24T07:54:43 | 2021-11-24T07:54:43 | {} | NONE |
vuejs | core | 977,751,884 | 4,989 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4294 | 2021-11-24T10:41:57 | 2021-11-24T10:41:57 | {} | MEMBER |
vuejs | core | 978,936,473 | 4,993 | LinusBorg | [Workaround](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG5pbXBvcnQgQ29tcDIgZnJvbSAnLi9Db21wMi52dWUnXG5cbmNvbnN0IHNob3dOb0V4Y2x1ZGVGaXJzdCA9IHJlZih0cnVlKVxuY29uc3Qgc2hvd0V4Y2x1ZGVGaXJzdCA9IHJlZih0cnVlKVxuPC9zY3JpcHQ+XG5cbjx0ZW1w... | 2021-11-25T08:15:52 | 2021-11-25T08:15:52 | {
"+1": 1
} | MEMBER |
vuejs | core | 979,446,466 | 4,998 | sevilyilmaz | It's sad to hear it would be a breaking change because it's controversial to be able to pass attributes in both cases while creating elements but not possible to read them in the same way.
[Here](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdD5cbmltcG9ydCB7IGggfSBmcm9tICd2dWUnO1xuXG5leHBvcnQgZGVmYXVsdCB7XG4gIHJlbm... | 2021-11-25T19:59:54 | 2021-11-25T19:59:54 | {} | NONE |
vuejs | core | 981,602,631 | 5,008 | LinusBorg | You need to configure webpack to point to one absolute path for the `vue` package, so that only one copy is imported into the app.
Not a Vue-next issue. | 2021-11-29T12:47:38 | 2021-11-29T12:47:38 | {} | MEMBER |
vuejs | core | 982,573,416 | 1,865 | doniyorerkinov | why google is stupid
| 2021-11-30T12:05:43 | 2021-11-30T12:05:43 | {} | NONE |
vuejs | core | 978,447,769 | 4,992 | mik-jozef | Sorry, I relied on old info (#671) and had another issue in my code. | 2021-11-24T23:25:39 | 2021-11-24T23:25:39 | {} | NONE |
vuejs | core | 979,015,917 | 4,995 | jzfai | <template>
<div>这是父组件</div>
<div>这是父组件</div>
</template>
这个是vue3支持的写法,我为什么要套一层div呢,我就想要这种写法
> 
>
> Dude, you can do like this 老哥,你把这个组件套一层div,像下面这样应该就可以了
>
> ```js
> <template>
> <div>
> ... | 2021-11-25T09:27:58 | 2021-11-25T09:29:33 | {
"+1": 1,
"confused": 1
} | NONE |
vuejs | core | 979,726,158 | 4,908 | yyx990803 | FYI I tested this further with local `plugin-vue` changes and determined this is sub-optimal - this would cause the component to reload instead of re-render in more cases than necessary (for example any template expression change would cause a reload with the proposed changes in https://github.com/vitejs/vite/pull/5561... | 2021-11-26T06:26:47 | 2021-11-26T06:26:47 | {
"+1": 2
} | MEMBER |
vuejs | core | 980,635,974 | 4,662 | raffobaffo | @adamlewkowicz hard to answer. Depends from how the imported element (third party) is structured. Does it comes with is own inline styles? If yes, it should work, if not, it cant. | 2021-11-27T14:26:43 | 2021-11-27T14:27:06 | {} | NONE |
vuejs | core | 981,060,501 | 4,960 | mrts | > What you are arguing for is a 4th way *that is more ergonomic/elegant* than the 3 existing ones - which absolutely is a fine goal to have, but it won't reduce the number of way to do things, it would increase them.
Thank you for expressing my intent so well. Yes, this is my goal. However, I would argue that the fo... | 2021-11-28T10:32:00 | 2021-11-28T13:23:33 | {} | NONE |
vuejs | core | 982,352,643 | 5,018 | LinusBorg | ```js
<script setup>
const add = () =>{
console.log('click trigger')
}
defineExpose({
add,
})
</script>
```
See: https://v3.vuejs.org/api/sfc-script-setup.html#defineexpose
The source of the difference in behavior is the same as #4980 so I'll close this one as a duplicate. | 2021-11-30T07:20:27 | 2021-11-30T07:20:52 | {} | MEMBER |
vuejs | core | 982,657,130 | 5,023 | posva | It is null because it runs immediately too thanks to `{ immediate: true, flush: 'post' }` | 2021-11-30T13:53:51 | 2021-11-30T13:53:51 | {} | MEMBER |
vuejs | core | 975,970,831 | 2,855 | canidas | Same problem with Vue 3.2.22 SFC + `<script lang="ts">` + `defineComponent` in a webpack project:
```
TS2345: Argument of type '{ new (): { $props: VNodeProps & TeleportProps; }; __isTeleport: true; }' is not assignable to parmeter of type 'VNodeTypes | ClassComponent'.
Type '{ new (): { $props: VNodeProps & T... | 2021-11-22T22:24:02 | 2021-11-22T22:24:02 | {
"+1": 2
} | NONE |
vuejs | core | 979,044,613 | 4,964 | yyx990803 | But why are we passing Symbols as attribute values in the first place? | 2021-11-25T09:53:55 | 2021-11-25T09:53:55 | {} | MEMBER |
vuejs | core | 979,759,487 | 5,001 | ygj6 | Please provide a repl or warehouse address:sweat_smile: | 2021-11-26T07:49:20 | 2021-11-26T07:49:20 | {} | MEMBER |
vuejs | core | 982,399,826 | 5,019 | posva | You are probably looking to write something like vue clickaway: https://www.npmjs.com/package/vue3-click-away
Remember to write issues in English and to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-11-30T08:32:12 | 2021-11-30T08:32:12 | {} | MEMBER |
vuejs | core | 979,887,916 | 777 | avlasiuk | Might be helpful for someone. I had the same issue because of a mistake.
instead of using this
`SomeComponent: defineAsyncComponent(() => import('@/components/SomeComponent.vue'))`
I was using this, That is not a properly way
`SomeComponent: () => defineAsyncComponent(() => import('@/components/SomeComponen... | 2021-11-26T11:07:28 | 2021-11-30T12:08:20 | {
"+1": 5,
"hooray": 2
} | NONE |
vuejs | core | 978,903,646 | 4,996 | LinusBorg | Thar requires a scheduler which `@vue/reactivity` doesn't provide - the Vue package does, and it's `watch*()` APIs do make use of it.
* https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/apiWatch.ts
* https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/scheduler.ts | 2021-11-25T07:24:24 | 2021-11-25T07:26:19 | {} | MEMBER |
vuejs | core | 978,906,567 | 4,995 | caozhong1996 | 
Dude, you can do like this
老哥,你把这个组件套一层div,像下面这样应该就可以了
````js
<template>
<div>
<div>这是父组件</div>
....
</div>
</template>
````
But I think it should be a bug...
但是我觉得这个应该算bug... | 2021-11-25T07:29:32 | 2021-11-25T07:32:47 | {} | CONTRIBUTOR |
vuejs | core | 979,375,967 | 4,873 | LinusBorg | No idea why the PR test runs fail, and the push ones run fine ... 🧐 | 2021-11-25T17:28:47 | 2021-11-25T17:28:58 | {} | MEMBER |
vuejs | core | 979,989,365 | 5,005 | posva | Duplicate of https://github.com/vuejs/vue/issues/3761 | 2021-11-26T13:45:40 | 2021-11-26T13:45:40 | {} | MEMBER |
vuejs | core | 980,489,063 | 5,006 | caozhong1996 | Could you give some introduction about this commit? | 2021-11-27T02:31:19 | 2021-11-27T02:31:19 | {} | CONTRIBUTOR |
vuejs | core | 981,635,167 | 4,662 | dezmound | As a workaround I've created component, which tracks Mutation in `document.head ` and inline style tags (must includes comment `/* VueCustomElementChildren */`) into shadow dom in dev mode, for production it inlines link for stylesheets:
`CustomElements.vue`
```vue
<script setup lang="ts">
/***
* @see htt... | 2021-11-29T13:28:29 | 2021-11-29T13:58:45 | {} | NONE |
vuejs | core | 982,659,445 | 5,023 | zhenzhenChange | `immediate` Is the callback `executed` immediately, or is the callback `registered` immediately? | 2021-11-30T13:56:34 | 2021-11-30T13:56:34 | {} | NONE |
vuejs | core | 975,165,410 | 4,982 | ygj6 | duplicate of #4294 | 2021-11-22T06:18:34 | 2021-11-22T06:18:34 | {} | MEMBER |
vuejs | core | 978,726,103 | 4,988 | lijingfaatcumt | >
1. may you tell me the reason why design like this: 'watching deeply will trace all reactives/refs in the substructure of the watch source'
2.
```javascript
const a = reactive({ msg: '' })
const b = readonly({ someValue: a })
const c = shallowReactive({ b })
watch(() => c, () => console.log('triggered'), { ... | 2021-11-25T01:46:57 | 2021-11-25T01:48:56 | {} | NONE |
vuejs | core | 978,805,108 | 4,986 | yyx990803 | Looks like a legit bug, but a bit of an edge case. | 2021-11-25T03:56:32 | 2021-11-25T03:59:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 980,504,678 | 5,006 | mehanalavimajd | > Oh, I think it's unnecessary, we just need escape `"'&<>`. They are HTML reserved characters.
OK @caozhong1996 , thanks for informing me
| 2021-11-27T05:12:53 | 2021-11-27T05:12:53 | {} | CONTRIBUTOR |
vuejs | core | 981,128,558 | 5,013 | wszerad | @posva This, unfortunately, has nothing to do with it.
Check my example and log from my directive (for vnode):
<img width="316" alt="template" src="https://user-images.githubusercontent.com/8605363/143780460-9dec0c84-7092-42b8-b3a9-dd468a0e6cfa.PNG">
<img width="932" alt="directive" src="https://user-images.github... | 2021-11-28T18:16:04 | 2021-11-28T18:16:25 | {} | NONE |
vuejs | core | 976,371,642 | 4,975 | wood3n | emmm..., any chinese characters in an element with `v-pre`, I don't need to get and convert them. But the AST node's `props` is Empty so I can't judge this element with `v-pre` whether or not.😂That's the [code link](https://github.com/wood3n/v18n/blob/a619a566c6bc8a6485956406ddf0ce7a1455c8cd/lib/transform.ts#L35), If ... | 2021-11-23T10:19:35 | 2021-11-23T10:19:35 | {} | NONE |
vuejs | core | 979,042,751 | 4,970 | yyx990803 | So I misread the initial discussion on wechat because i was on a phone and didn't see the whole test case - in this case it is actually intended - imports and const declarations in normal `<script>` **should** be exposed to the template if (and only if) `<script setup>` is also used. | 2021-11-25T09:51:28 | 2021-11-25T09:51:48 | {} | MEMBER |
vuejs | core | 979,062,105 | 4,962 | yyx990803 | Thanks for the PR! The `OTHER` flag serves as a fallthrough value (in the `switch` check) so that we can skip the checks for future access, so it still needs to be there. I landed a more conservative fix in aac0466. | 2021-11-25T10:16:54 | 2021-11-25T10:17:03 | {} | MEMBER |
vuejs | core | 971,477,016 | 4,955 | yuwu9145 | This issue actually has nothing to do with `$props`, and as per my testing, both `RouterView` & `RouterLink` work, as they serve as legitimate `Component` type. The reason why `Teleport` breaks type Inference is because it has `__isTeleport` property which does not exist in `Component`, same to `Suspense`.
Edit: Ro... | 2021-11-17T11:15:22 | 2021-11-25T10:22:56 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 979,681,477 | 4,873 | yyx990803 | Yeah, it's been reverted in latest master - @LinusBorg can you rebase and add a test case? | 2021-11-26T04:03:55 | 2021-11-26T04:03:55 | {} | MEMBER |
vuejs | core | 980,644,579 | 4,654 | lloydjatkinson | Still an issue with a Vue CLI scaffolded project and vue-loader 16.8.2. | 2021-11-27T15:36:52 | 2021-11-27T15:36:52 | {} | NONE |
vuejs | core | 982,355,108 | 5,020 | LinusBorg | If you look at the generated JS tab, you can see that for the dynamic component, Vue generates code that fits for a *component* that v-model is used on, not an *input element*.
The compile can't verify at build time which type the dynamic component will be at runtime, and as the "usual" usecase is to actually render... | 2021-11-30T07:24:44 | 2021-11-30T07:24:44 | {} | MEMBER |
vuejs | core | 976,823,117 | 1,865 | KevyMbappeOld | > I see it in the branch. The problem is you are using the same key for two different components because you are not filtering what you are keeping alive. So you have either provide a unique key based on the route path/name + the id, that way KeepAlive will be able to restore the correct component, or use
>
> ```
>... | 2021-11-23T16:37:05 | 2021-11-23T16:37:05 | {
"+1": 4
} | NONE |
vuejs | core | 977,359,410 | 4,984 | lejianwen | 谢谢大家
只是感觉各种方式都有点绕,不太符合3.x的风格
@edison1105 的方式很简洁明了,我拿走了
| 2021-11-24T01:20:38 | 2021-11-24T01:20:38 | {} | NONE |
vuejs | core | 978,786,631 | 4,994 | caozhong1996 | You can use [https://sfc.vuejs.org/](https://sfc.vuejs.org/) to reproduce this error. | 2021-11-25T03:25:40 | 2021-11-25T03:25:40 | {} | CONTRIBUTOR |
vuejs | core | 982,444,162 | 5,021 | LinusBorg | messed up the branch | 2021-11-30T09:24:35 | 2021-11-30T09:24:35 | {} | MEMBER |
vuejs | core | 975,148,290 | 4,975 | wood3n | >
but `v-pre` isn't contained in `props`, the `props` is empty.😂 | 2021-11-22T05:44:55 | 2021-11-22T05:44:55 | {} | NONE |
vuejs | core | 976,353,788 | 4,984 | LinusBorg | Seems to me like it would trigger, because of `deep: true` being set: [Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlYWN0aXZlLCByZWYsIHdhdGNoIH0gZnJvbSAndnVlJ1xuXG5jb25zdCBpdGVtcyA9IHJlYWN0aXZlKFsxLDJdKSAgXG5cbndhdGNoKFxuICAoKSA9PiBbaXRlbXNdLFxuICAoKSA9PiB7XG4gICAgY29uc29sZS5sb2... | 2021-11-23T09:57:08 | 2021-11-23T09:57:08 | {} | MEMBER |
vuejs | core | 976,304,381 | 4,984 | edison1105 | as a workround
```javascript
:include="[...keeps]"
```
<s>`include` and `exclude` should not pass reactive data.
see https://v3.vuejs.org/guide/reactivity-computed-watchers.html#watching-reactive-objects
the watch will not trigger if `include` is reactive. maybe we should improve this code:
```javascript
... | 2021-11-23T09:08:06 | 2021-11-23T13:38:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 977,226,029 | 4,950 | kadiryazici | @yuwu9145 it might be because of different version. Mine was `^3.2.4` but it installed `3.2.19`. I will use updated package. | 2021-11-23T22:23:54 | 2021-11-23T22:23:54 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.