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 | 925,251,993 | 1,359 | johnsoncodehk | > I guess this does not supported `v-slot` anyway? `v-slot="{ item as SomeType }"`
>
> `[plugin:vite:vue] Error parsing JavaScript expression: Unexpected type cast in parameter position. (1:1)`
I am not sure if this is supported. But if it is, the syntax should be: `v-slot="{ item }: { item: SomeType }`. | 2021-09-22T19:26:52 | 2021-09-22T19:26:52 | {
"heart": 2
} | MEMBER |
vuejs | core | 921,390,924 | 4,605 | WJCHumble | @edison1105 Yesterday, I wrote the same code as you to solve this issue, but when I delete the child of the `teleport` and then add the child to the `teleport`, the `setVarsOnVNode` function is not triggered.
Then I found that the `MutationObserver` in the `useCssVars` function is to observe the `instance.subTree.e... | 2021-09-17T01:57:52 | 2021-09-17T05:47:49 | {} | NONE |
vuejs | core | 921,765,208 | 4,595 | leopiccionia | Anyway, since 0cfa2112ce2210300cf2edf272c8c8d11b9355e4 commit, Vue won't try to convert `String` props to number. | 2021-09-17T12:40:14 | 2021-09-17T12:40:14 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 921,826,119 | 4,620 | catsmeatman | Yes, I tried to use it as
```
const App = Vue.createApp({});
App.config.compilerOptions.isCustomElement = tag => tag === 'test-case-inside';
```
but it not work. Add compilerOptions in attached CodePan | 2021-09-17T14:07:42 | 2021-09-17T14:09:01 | {} | NONE |
vuejs | core | 923,066,244 | 4,632 | yyx990803 | Actually, the proxy created by typesafe-i18n intercepts all property access which includes `__v_skip` so it will never be `true`. Essentially, its a proxy that is infinitely chainable on any property - and unfortunately this kind of proxies are fundamentally incompatible with how Vue's reactivity system currently works... | 2021-09-20T16:06:31 | 2021-09-20T16:06:31 | {
"+1": 1
} | MEMBER |
vuejs | core | 923,743,028 | 4,633 | LinusBorg | What bug? | 2021-09-21T08:10:28 | 2021-09-21T08:10:28 | {} | MEMBER |
vuejs | core | 924,151,749 | 4,638 | yyx990803 | This is because you are using Vue template syntax (`:test-value="true"`) in plain HTML. | 2021-09-21T16:27:31 | 2021-09-21T16:27:31 | {} | MEMBER |
vuejs | core | 924,638,080 | 4,646 | zhangenming | https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPiBcbiAgPGRpdiBpZD1cImNvbnNvbGVcIj5cbiAgPC9kaXY+XG4gIDxpbnB1dCA6cGxhY2Vob2xkZXI9XCJgVGhpcyBpcyBDb21wYFwiIDpyZWY9XCJkb21cIiA+XG48L3RlbXBsYXRlPlxuXG48c2NyaXB0PlxuaW1wb3J0IHsgcmVmIH0gZnJvbSAndnVlJ1xuZXhwb3J0IGRlZmF1bHQge1xuICBzZXR1cCgpe1xuICAgIFxuICAgIGNvbnN0IGlucHV0ID0gc... | 2021-09-22T06:51:59 | 2021-09-22T06:51:59 | {} | CONTRIBUTOR |
vuejs | core | 924,979,805 | 4,638 | catsmeatman | Thanks | 2021-09-22T14:22:04 | 2021-09-22T14:22:04 | {} | NONE |
vuejs | core | 925,236,838 | 1,359 | chojnicki | I guess this does not supported `v-slot` anyway? `v-slot="{ item as SomeType }"`
`[plugin:vite:vue] Error parsing JavaScript expression: Unexpected type cast in parameter position. (1:1)`
| 2021-09-22T19:14:13 | 2021-09-22T19:14:13 | {} | NONE |
vuejs | core | 925,258,959 | 1,359 | chojnicki | > > I guess this does not supported `v-slot` anyway? `v-slot="{ item as SomeType }"`
> > `[plugin:vite:vue] Error parsing JavaScript expression: Unexpected type cast in parameter position. (1:1)`
>
> I am not sure if this is supported. But if it is, the syntax should be: `v-slot="{ item }: { item: SomeType }`.
D... | 2021-09-22T19:32:03 | 2021-09-22T19:32:03 | {} | NONE |
vuejs | core | 921,885,226 | 4,547 | tjk | If someone can tell me which part of my code exploration above sounds like the problem (if any), I can attempt a patch.
Also, while I noticed a problem during HMR I imagine this could cause other problems too perhaps? | 2021-09-17T15:25:19 | 2021-09-17T15:25:19 | {} | CONTRIBUTOR |
vuejs | core | 922,238,044 | 4,626 | ygj6 | Make sure `vue` and `@vue/compiler-sfc` are the same version. | 2021-09-18T08:09:12 | 2021-09-18T08:09:12 | {} | MEMBER |
vuejs | core | 923,097,708 | 4,636 | yyx990803 | That's expected because comments are considered part of your template and thus rendered making your component a fragment instance.
If you want to avoid that, put the comment outside `<template>` or nested. | 2021-09-20T16:45:42 | 2021-09-20T16:45:42 | {} | MEMBER |
vuejs | core | 925,313,009 | 4,655 | qgates | It's not just a volar issue. I see a compilation error from vite and on the browser as well. | 2021-09-22T20:39:54 | 2021-09-22T20:39:54 | {} | NONE |
vuejs | core | 922,049,293 | 4,590 | mnlipp | Problem was caused by typescript compiler being too old (3.9.10). Upgrading to current (4.4.3) fixes it. | 2021-09-17T20:03:24 | 2021-09-17T20:03:24 | {
"+1": 8
} | NONE |
vuejs | core | 922,381,027 | 4,624 | yyx990803 | This is not something Vue or Vite can fix, it's only because SCSS doesn't allow the syntax.
This should be valid in SCSS though: `v-bind("height + 'px'");` | 2021-09-18T22:12:55 | 2021-09-18T22:14:59 | {} | MEMBER |
vuejs | core | 923,098,988 | 2,860 | yyx990803 | Now also fixed in `vue-loader` 16.6+ (https://github.com/vuejs/vue-loader/commit/11e3cb8a8a4a4e0aedc2978ce6d7e549a61de3d7) | 2021-09-20T16:47:36 | 2021-09-20T16:47:36 | {} | MEMBER |
vuejs | core | 924,385,173 | 4,646 | cyfung1031 | > see #4084
> This is expected, setRef will execute on each time patch and unmount.
I think your case is okay, since the content or prop is changed.
But to my case here, there is no any change to the DOM. There is only one rendering. ( just mount to the page and that's all ) | 2021-09-21T21:08:31 | 2021-09-21T21:09:36 | {} | NONE |
vuejs | core | 924,907,118 | 4,646 | yyx990803 | That's expected behavior because the initial ref is empty before render, and is changed on first render when the element is created. Your ref function accesses the value which registers it as a dependency of your render process, so the render will run again because you mutated a dependency right afterwards. The depende... | 2021-09-22T13:01:03 | 2021-09-22T13:01:03 | {} | MEMBER |
vuejs | core | 921,364,087 | 4,573 | oooplz | Thanks for your replying. | 2021-09-17T00:46:48 | 2021-09-17T00:46:48 | {} | NONE |
vuejs | core | 922,233,607 | 4,627 | posva | You need the mounted hook for that | 2021-09-18T07:36:16 | 2021-09-18T07:36:16 | {} | MEMBER |
vuejs | core | 923,415,264 | 4,622 | catrope | It looks like these confusing conditions (only in the migration build and with client-side compilation) are not actually necessary, but instead it looks like this bug is triggered by `compilerOptions.whitespace` being set to `'preserve'` (which the migration build does, for client-side compiled templates). The text nod... | 2021-09-20T23:00:17 | 2021-09-20T23:00:17 | {} | CONTRIBUTOR |
vuejs | core | 924,166,012 | 4,625 | yyx990803 | Please rebase your branch on top of master to exclude the unintended commit. | 2021-09-21T16:44:53 | 2021-09-21T16:44:53 | {} | MEMBER |
vuejs | core | 924,388,986 | 4,646 | sqal | hm ok, that's weird then.. if you switch to script-setup it works as you intended [demo](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPiBcbiAgPGRpdiBpZD1cImNvbnNvbGVcIj5cbiAgPC9kaXY+XG4gIDxpbnB1dCA6cGxhY2Vob2xkZXI9XCJgVGhpcyBpcyBDb21wYFwiIDpyZWY9XCJkb21cIiA+XG48L3RlbXBsYXRlPlxuXG48c2NyaXB0IHNldHVwPlxuICBpbXBvcnQg... | 2021-09-21T21:14:18 | 2021-09-21T21:14:18 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 924,651,751 | 4,644 | lidlanca | ```pre
Error: [@vue/compiler-sfc] `defineProps()` in <script setup> cannot reference
locally declared variables because it will be hoisted
outside of the setup() function.
If your component options requires initialization in the module scope,
use a separate normal <script> to export the options instead.
```
... | 2021-09-22T07:13:29 | 2021-09-22T07:13:29 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 925,253,253 | 1,359 | Spittal | I can confirm that syntax like this does work:
| 2021-09-22T19:27:51 | 2021-09-22T19:27:51 | {
"heart": 2
} | NONE |
vuejs | core | 922,262,756 | 2,614 | mesqueeb | Friendly bump | 2021-09-18T11:32:48 | 2021-09-19T04:54:46 | {} | NONE |
vuejs | core | 922,538,162 | 2,860 | yyx990803 | This is now fixed by https://github.com/vitejs/vite/commit/316d7afc0c84e51359938a12ebe1b09ca34ea8bd + cb2d7c0e
Will need `@vitejs/plugin-vue` >= 1.8.1.
`vue-loader@next` will get similar fix soon. | 2021-09-19T21:16:01 | 2021-09-19T21:16:01 | {
"hooray": 3
} | MEMBER |
vuejs | core | 923,845,612 | 4,497 | Justineo | Why do you think `style` string should be parsed into objects? It doesn't seem to be a bug to me as we do not expect this behavior. | 2021-09-21T10:25:54 | 2021-09-21T10:25:54 | {} | MEMBER |
vuejs | core | 924,539,082 | 4,644 | ygj6 | According to: https://github.com/vuejs/rfcs/blob/master/active-rfcs/0040-script-setup.md
* The options passed to defineProps and defineEmits will be hoisted out of setup into module scope. Therefore, the options cannot reference local variables declared in setup scope. Doing so will result in a compile error. However,... | 2021-09-22T02:53:19 | 2021-09-22T02:53:19 | {
"confused": 1
} | MEMBER |
vuejs | core | 921,799,489 | 4,620 | yyx990803 | https://v3.vuejs.org/guide/web-components.html#skipping-component-resolution | 2021-09-17T13:31:02 | 2021-09-17T13:31:02 | {} | MEMBER |
vuejs | core | 922,234,931 | 4,627 | LinusBorg | https://v3.cn.vuejs.org/guide/custom-directive.html#%E9%92%A9%E5%AD%90%E5%87%BD%E6%95%B0 | 2021-09-18T07:47:05 | 2021-09-18T07:47:05 | {} | MEMBER |
vuejs | core | 922,364,925 | 4,620 | catsmeatman | Thanks | 2021-09-18T19:54:47 | 2021-09-18T19:54:47 | {} | NONE |
vuejs | core | 923,118,775 | 4,632 | Pentadome | Although `WeakMaps` has worse performance, I believe there should be an exception for objects passed to `markRaw`. Isn't the main use case of `markRaw` that you want an object not change by Vue?
I realize that this is a niche use case, but I believe that using `markRaw` is niche too. Therefore, I don't believe the a... | 2021-09-20T17:12:48 | 2021-09-20T17:19:18 | {} | CONTRIBUTOR |
vuejs | core | 923,809,240 | 1,359 | jods4 | > @jods4 you can do this:
>
> ```
> <template v-for="i of items">
> <a
> v-if="'linkText' in i"
> @click="'linkText' in i ? goToLink(i) : undefined"
> >{{ i.linkText }}</a>
> <div
> v-else
> @click="'linkText' in i ? undefined : openGroup(i)"
> >{{ i.groupHeader }}</div>
> </templat... | 2021-09-21T09:38:58 | 2021-09-21T09:38:58 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 923,931,150 | 4,641 | zhangenming | or should we move `toReactive` function code from collectionHandlers.ts to reactive.ts ? | 2021-09-21T12:21:17 | 2021-09-21T12:21:17 | {} | CONTRIBUTOR |
vuejs | core | 924,426,218 | 4,640 | qgates | @yyx990803 maybe I'm missing something but I still see errors in template compilation and Volar with the above? | 2021-09-21T22:12:40 | 2021-09-21T22:28:38 | {} | NONE |
vuejs | core | 925,322,337 | 4,655 | qgates | Essentially:
`v-bind="var as string"` works, as expected ie. clearing any ts2322 error where valid. But `v-model="var as string"` does not and complains about invalid expression syntax.
Thanks for looking into this 👍
| 2021-09-22T20:54:23 | 2021-09-22T20:54:53 | {} | NONE |
vuejs | core | 938,289,942 | 4,758 | ygj6 |
> Is there some other way that I can use to specify complex types for my prop members?
You could try to use like this:
```vue
<script lang="ts">
export interface Post {
Message: string;
}
</script>
<script setup lang="ts">
interface Props {
Args: {Post: Post};
}
const props = withDefaults(def... | 2021-10-08T02:32:03 | 2021-10-08T02:32:03 | {} | MEMBER |
vuejs | core | 938,432,473 | 4,760 | posva | Open the issue in vant repository first. | 2021-10-08T08:04:02 | 2021-10-08T08:04:02 | {} | MEMBER |
vuejs | core | 938,507,674 | 4,759 | zhaozhongyu | actually i have a pull request to fix this issue, please check https://github.com/vuejs/vue-next/pull/4762 | 2021-10-08T09:52:00 | 2021-10-08T09:52:00 | {} | NONE |
vuejs | core | 939,287,042 | 4,769 | edison1105 | @zhaozhongyu Okay, Your PR looks better. I will close this one. | 2021-10-09T12:11:13 | 2021-10-09T12:11:13 | {} | MEMBER |
vuejs | core | 942,200,483 | 4,760 | Justineo | Why are you applying side effects in `computed` instead of `watch`/`watchEffect`? | 2021-10-13T11:23:51 | 2021-10-13T11:23:51 | {
"+1": 1
} | MEMBER |
vuejs | core | 938,200,855 | 4,757 | ElMassimo | Since `plugin-vue` is [still](https://github.com/vuejs/vue-next/commit/aa8908a8543c5151a2cc06ed4d8fab3a1461692a#diff-ccebe74771d12151844d4d2de4cf16c6f7fb7ed6584d30964dae54a23454a942L69) providing `_sfc_main` as a [second parameter](https://github.com/vitejs/vite/blob/main/packages/plugin-vue/src/main.ts#L126) to the HM... | 2021-10-07T22:31:35 | 2021-10-07T22:31:35 | {} | NONE |
vuejs | core | 939,213,664 | 4,299 | edison1105 | @zhangshichun 可以提供一个可以复现的 demo 吗，越简单越好。 | 2021-10-09T03:09:03 | 2021-10-09T03:09:03 | {} | MEMBER |
vuejs | core | 939,287,454 | 4,770 | edison1105 | BTW, the test case should cover https://github.com/vuejs/vue-next/pull/4424 | 2021-10-09T12:14:12 | 2021-10-09T12:14:12 | {} | MEMBER |
vuejs | core | 939,599,391 | 4,781 | edison1105 | For the new feature, open an RFC on the RFCs repo, please. | 2021-10-11T01:20:20 | 2021-10-11T01:20:20 | {} | MEMBER |
vuejs | core | 939,862,691 | 4,783 | phucnguyen035 | My bad, I have updated with link to repository, as well as revising description | 2021-10-11T09:41:01 | 2021-10-11T09:41:01 | {
"+1": 1
} | NONE |
vuejs | core | 939,955,922 | 4,779 | StarHosea | @edison1105 I did not , I will try to reproduct it by a miniDemo | 2021-10-11T11:48:49 | 2021-10-11T11:48:49 | {} | NONE |
vuejs | core | 941,249,078 | 4,716 | flanagankp | I believe I'm seeing the same problem:
https://github.com/vuejs/vue-next/issues/4789 | 2021-10-12T18:07:07 | 2021-10-12T18:07:07 | {} | NONE |
vuejs | core | 941,307,131 | 4,647 | posva | This doesn't look like the right fix as Transition direct children should be elements (so classes can be added) 🤔 Are you sure this fixed #4622 ? A previously failing test would also help to move things forward. | 2021-10-12T19:04:43 | 2021-10-12T19:04:43 | {} | MEMBER |
vuejs | core | 941,828,021 | 4,788 | emojiiii | > What is the bug you found? Can you provide a reproduction?
If you try to register a Vue built-in component in the component, the component is invalid, so we need to add verification built-in components
such as [reproduction](https://codesandbox.io/s/wild-cloud-hpm92?file=/src/App.vue) | 2021-10-13T01:36:16 | 2021-10-13T01:36:16 | {} | CONTRIBUTOR |
vuejs | core | 941,904,912 | 4,785 | yizhi996 | @yyx990803
There may be multiple pages rendered at the same time, and the current page cannot be determined in `createElement`.
```typescript
export function renderPage(route: string) {
const page = new Page(pid += 1, route)
pages.set(page.pid, page)
const pageComponent = pageComponents.get(pag... | 2021-10-13T04:16:49 | 2021-10-13T04:16:49 | {} | NONE |
vuejs | core | 942,079,930 | 3,648 | edison1105 | @haoziqaq 还没有，PR 还是 open 的呢。 | 2021-10-13T08:54:58 | 2021-10-13T08:54:58 | {} | MEMBER |
vuejs | core | 938,286,853 | 4,758 | ygj6 | Duplicate of #4294 | 2021-10-08T02:23:54 | 2021-10-08T02:23:54 | {} | MEMBER |
vuejs | core | 938,471,809 | 4,760 | wensc1996 | > @wensc1996 Try like this:
>
> ```js
> const name = computed(() => {
> if (x.value == 0) {
> return "张三";
> } else {
> nextTick(() => {
> Toast("你好");
> });
> return "李四";
> }
> });
> ```
thanks, maybe the vue-createVnode conficts wit... | 2021-10-08T08:59:04 | 2021-10-08T08:59:04 | {} | NONE |
vuejs | core | 939,275,244 | 906 | khalo-sa | oh man, I wasted so many hours on this... is this acknowledged as a bug? | 2021-10-09T10:44:08 | 2021-10-09T10:44:08 | {} | NONE |
vuejs | core | 939,376,309 | 4,770 | yyx990803 | It seems unnecessary to store the state in an additional property. 3f38d599 should revert it to original behavior while still fixing #4424. | 2021-10-09T23:34:15 | 2021-10-09T23:34:15 | {} | MEMBER |
vuejs | core | 939,555,644 | 4,780 | 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).
Also, you should read and follow https://new-issue.vuej... | 2021-10-10T21:26:59 | 2021-10-10T21:26:59 | {
"confused": 3
} | MEMBER |
vuejs | core | 939,867,899 | 4,323 | guozhenqianga | > [vitejs/vite#4573 的](https://github.com/vitejs/vite/issues/4573#issuecomment-896893090)临时解决方案[（评论）](https://github.com/vitejs/vite/issues/4573#issuecomment-896893090)
How to solve vue2 | 2021-10-11T09:48:43 | 2021-10-11T09:48:43 | {
"eyes": 1
} | NONE |
vuejs | core | 940,721,131 | 4,786 | ygj6 | > According to the offical doc, `nextTick` is a global api method, why do I still have to do the import if it is global ?
You may have misunderstood the meaning of the global API.**[Global API](https://v3.vuejs.org/api/global-api.html#global-api)** | 2021-10-12T06:58:57 | 2021-10-12T06:58:57 | {} | MEMBER |
vuejs | core | 942,092,095 | 4,760 | ygj6 | @posva :sweat_smile: I simplified test case, But not sure if it's a bug.
[sfc.vuejs.org](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgY29tcHV0ZWQsIGNyZWF0ZUFwcCB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG4gIFxuY29uc3QgbXVtYmVyID0gcmVmKDApXG5jb25zdCBuYW1lID0gY29tcHV0ZWQ... | 2021-10-13T09:08:54 | 2021-10-13T09:11:43 | {} | MEMBER |
vuejs | core | 937,399,313 | 4,738 | yyx990803 | Ideally we want to know that there's just no devtools installed so it should not buffer anything. But the easy fix I can think of right now is a setTimeout to clear the buffer if the devtools is not injected after a certain period of time. | 2021-10-07T02:46:09 | 2021-10-07T02:46:09 | {} | MEMBER |
vuejs | core | 938,075,643 | 3,842 | dev-itsheng | Since I submitted this PR, no one has dealt with it for more than 5 months. I don't want to wait any longer and decide what to do on my own. So I do that, You can also try [my loader named `vue-template-pug-remove-indent-loader`](https://www.npmjs.com/package/vue-template-pug-remove-indent-loader) to solve this problem... | 2021-10-07T19:06:22 | 2021-10-07T19:06:22 | {
"+1": 1,
"confused": 1,
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 938,286,400 | 4,758 | phasetri | I think I found the reason why:
https://v3.vuejs.org/api/sfc-script-setup.html#typescript-only-features
```
Currently complex types and type imports from other files are not supported. It is theoretically possible to support type imports in the future.
```
Is there some other way that I can use to specify comp... | 2021-10-08T02:22:33 | 2021-10-08T02:22:33 | {} | NONE |
vuejs | core | 938,432,571 | 4,761 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4760 | 2021-10-08T08:04:11 | 2021-10-08T08:04:11 | {} | MEMBER |
vuejs | core | 938,444,095 | 4,760 | wensc1996 | > Then please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org).
Ok, let me check check the vant's sourcecode then reply you. | 2021-10-08T08:20:58 | 2021-10-08T08:20:58 | {} | NONE |
vuejs | core | 938,547,086 | 3,933 | AurelieV | For information, this is how we temporaly fix it for our usecase (App which load components inside iframe)
iframe.onload = () => {
performance.now = iframe.contentWindow.performance.now
}
Tested only on Chrome, this is a way to resynchronise the timestamps used by Vue | 2021-10-08T10:55:46 | 2021-10-08T10:55:46 | {} | NONE |
vuejs | core | 938,743,326 | 4,765 | yyx990803 | Why is this closed? | 2021-10-08T15:44:52 | 2021-10-08T15:44:52 | {} | MEMBER |
vuejs | core | 939,296,789 | 4,770 | zhaozhongyu | > BTW, the test case should cover #4424
i had test undefined and it seems to work well. | 2021-10-09T13:23:48 | 2021-10-09T13:23:48 | {} | NONE |
vuejs | core | 941,296,005 | 4,621 | posva | - The first warning is because transition doesn't accept an attribute `class` and it cannot fallthrough it because it has multiple children, you should remove the attribute or make multi element have one root element to silence the warning
- Your transition-group needs one single root element as its direct children in... | 2021-10-12T18:55:42 | 2021-10-12T19:08:44 | {} | MEMBER |
vuejs | core | 941,320,740 | 4,622 | catrope | Apologies, it looks like I accidentally messed up the CodeSandbox; it should be correct now. The template code that triggers this bug is:
```
<button @click="showImage = !showImage">Toggle transition</button>
<transition-group name="foo-bar" class="foo-bar">
<p key="hello">Hello</p>
<p key="img" v-if="... | 2021-10-12T19:12:00 | 2021-10-12T19:12:26 | {} | CONTRIBUTOR |
vuejs | core | 942,204,277 | 4,760 | posva | Calling the createApp inside of a `computed()` seems really weird. [It should run outside](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgY29tcHV0ZWQsIGNyZWF0ZUFwcCB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG4gIFxuY29uc3QgbXVtYmVyID0gcmVmKDApXG5jb25zdCBuYW1lID0gY29tcHV0ZW... | 2021-10-13T11:28:51 | 2021-10-13T11:28:51 | {
"+1": 1
} | MEMBER |
vuejs | core | 937,690,300 | 2,513 | AurelieV | I confirm that the problem is still here, is there any update on that? | 2021-10-07T11:08:17 | 2021-10-07T11:08:17 | {} | NONE |
vuejs | core | 938,465,707 | 4,760 | ygj6 | @wensc1996 Try like this:
```js
const name = computed(() => {
if (x.value == 0) {
return "张三";
} else {
nextTick(() => {
Toast("你好");
});
return "李四";
}
});
``` | 2021-10-08T08:52:23 | 2021-10-08T08:52:23 | {} | MEMBER |
vuejs | core | 939,735,184 | 4,782 | Justineo | The current code is more performant and memory-efficient. Thank you. | 2021-10-11T06:51:28 | 2021-10-11T06:51:28 | {} | MEMBER |
vuejs | core | 942,021,078 | 3,648 | haoziqaq | 请问这个问题在Vue的正式版本中修复了么？我在查阅更新日志的过程中没有搜索到相关的信息 | 2021-10-13T07:45:00 | 2021-10-13T07:45:00 | {} | NONE |
vuejs | core | 937,391,405 | 4,738 | yyx990803 | /cc @Akryum this is caused by the devtools emit buffer holding references to component instances. When the browser has no devtools installed, the buffer is kept forever so the unmounted instances are never released. This can happen in production too if the user has PROD_DEVTOOLS enabled.
The late injection seems to ... | 2021-10-07T02:22:21 | 2021-10-07T02:22:49 | {} | MEMBER |
vuejs | core | 937,399,974 | 4,753 | dependabot[bot] | Looks like @babel/parser is up-to-date now, so this is no longer needed. | 2021-10-07T02:48:00 | 2021-10-07T02:48:00 | {} | CONTRIBUTOR |
vuejs | core | 938,513,781 | 4,646 | cyfung1031 | I made a solution for this issue.
[SFC Playground - non-reactive refDom](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPiBcbiAgPGRpdiBpZD1cImNvbnRhaW5lclwiPlxuICAgIDxkaXYgaWQ9XCJjb25zb2xlXCI+PC9kaXY+XG4gIDwvZGl2PlxuICA8aW5wdXQgOnBsYWNlaG9sZGVyPVwiYFRoaXMgaXMgQ29tcGBcIiA6cmVmPVwiZG9tXCIgPlxuPC90ZW1wbGF0ZT5cblxuP... | 2021-10-08T10:01:13 | 2021-10-08T10:06:16 | {} | NONE |
vuejs | core | 939,830,508 | 4,783 | LinusBorg | It would be helpful if the repro provided your actually demonstrate the issue. | 2021-10-11T09:01:49 | 2021-10-11T09:01:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 940,786,481 | 4,716 | akibrk | Anything on this? | 2021-10-12T08:30:12 | 2021-10-12T08:30:12 | {} | NONE |
vuejs | core | 940,903,593 | 4,785 | yizhi996 | > > The custom renderer need to do a things depending on the container.
>
> That doesn't really qualify as a use case / problem description. Can you provide more details? When do you need this? What for? Why?
```typescript
const customNodeOps: Omit<RendererOptions<CustomNode, CustomElement>, 'patchProp'> = {
... | 2021-10-12T11:04:28 | 2021-10-12T11:14:20 | {} | NONE |
vuejs | core | 940,961,663 | 4,785 | LinusBorg | That doesn't really show any use cases for that code. | 2021-10-12T12:21:59 | 2021-10-12T12:21:59 | {} | MEMBER |
vuejs | core | 941,627,307 | 4,621 | catrope | Are you saying a `<transition-group>` works only with a single child tag that uses `v-for` to multiply itself, but not with multiple separate children? If that's the case, I would ask that the documentation be updated to make that clear. I ran into this issue when migrating code that my colleagues wrote from Vue 2 to V... | 2021-10-12T21:55:12 | 2021-10-12T21:55:12 | {} | CONTRIBUTOR |
vuejs | core | 941,865,096 | 4,785 | yyx990803 | This is a very specific design constraint for your custom renderer - i.e. your element creation requires access to the current custom "page" object - but it doesn't logically leads to "createElement should pass the parent container".
Where is your page created? Why can't it be made available to your renderer methods... | 2021-10-13T02:47:53 | 2021-10-13T02:47:53 | {} | MEMBER |
vuejs | core | 937,643,074 | 1,033 | olemarius | I started getting these errors after installing storybook 3.6.10. My project's stack is vite + vue3 (typescript), while storybook is using webpack and is based on react, so I'm making a wild guess that by adding storybook, these errors started surfacing because of react dependencies.
_Type '{ class: string; }' is... | 2021-10-07T10:02:42 | 2021-10-07T10:02:42 | {
"+1": 16,
"eyes": 2
} | NONE |
vuejs | core | 938,297,785 | 4,758 | phasetri | That works.
Interesting, I also found that you can create the same warning using this:
```vue
<script lang="ts">
import {
Post,
} from "./PostDef";
</script>
<script setup lang="ts">
interface Props {
Args: {Post: any};
}
const props = withDefaults(defineProps<Props>(), {});
</script>
<templ... | 2021-10-08T02:54:36 | 2021-10-08T02:58:09 | {
"+1": 2
} | NONE |
vuejs | core | 939,214,858 | 4,299 | zhangshichun | > @zhangshichun 可以提供一个可以复现的 demo 吗，越简单越好。
嗯嗯，晚一点哈 | 2021-10-09T03:18:10 | 2021-10-09T03:18:10 | {} | NONE |
vuejs | core | 939,603,570 | 4,781 | moander | It's just an alias like `watchPostEffect` and `watchSyncEffect`. Nothing fancy :) | 2021-10-11T01:29:58 | 2021-10-11T01:29:58 | {} | NONE |
vuejs | core | 941,300,650 | 4,622 | posva | as a temporary workaround you can remove ~~the HTML comment before the `<p v-if="...">`~~ the whitespace between the two p nodes | 2021-10-12T19:00:02 | 2021-10-12T19:17:20 | {} | MEMBER |
vuejs | core | 939,284,244 | 4,769 | zhaozhongyu | 您的这个提交有bug, 没有考虑到如果用户使用的写法如果是`:style="{ 'display': xxx }"`的情况, 而且, 也没有考虑到如果用户不通过`v-show`的方式在style计算中将display设为none的情况. | 2021-10-09T11:51:09 | 2021-10-09T11:51:09 | {} | NONE |
vuejs | core | 939,297,544 | 4,771 | edison1105 | - 新版本的文档还在重写当中 see https://vue-docs-preview.netlify.app/api/reactivity-core.html 会对类型进行说明。
- 你提到的类型错误确实存在。能否重新提一个issue，尽量用英文。这样如果还有其他人遇到了类似的问题，也能找到相关的解决方案。
| 2021-10-09T13:28:15 | 2021-10-09T13:28:37 | {} | MEMBER |
vuejs | core | 939,838,395 | 4,770 | zhaozhongyu | > It seems unnecessary to store the state in an additional property. [3f38d59](https://github.com/vuejs/vue-next/commit/3f38d599f5aacdd3eeaa9475251a24f74e7ae3b4) should revert it to original behavior while still fixing #4424.
The commit 3f38d599f5aacdd3eeaa9475251a24f74e7ae3b4 has conflicts between v-show and style ... | 2021-10-11T09:10:22 | 2021-10-11T09:10:22 | {} | NONE |
vuejs | core | 940,810,719 | 4,785 | LinusBorg | > The custom renderer need to do a things depending on the container.
That doesn't really qualify as a use case / problem description. Can you provide more details? When do you need this? What for? Why? | 2021-10-12T09:00:30 | 2021-10-12T09:00:30 | {} | MEMBER |
vuejs | core | 941,242,948 | 4,647 | catrope | This PR has been waiting for three weeks, could someone look at this please? It blocks the Vue 3 migration for the Wikimedia Foundation (Wikipedia and related websites) | 2021-10-12T17:59:23 | 2021-10-12T17:59:23 | {} | CONTRIBUTOR |
vuejs | core | 941,324,926 | 4,621 | posva | Updated the comment to be clearer, the children should be direct to transition-group or use the [transition-group inside](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBNdWx0aUVsZW1lbnQgZnJvbSAnLi9NdWx0aUVsZW1lbnQudnVlJztcblxuY29uc3Qgc2hvd0ltYWdlID0gcmVmKGZhbHN... | 2021-10-12T19:14:27 | 2021-10-12T19:14:27 | {} | MEMBER |
vuejs | core | 941,828,702 | 4,785 | yizhi996 | > That doesn't really show any use cases for that code.
```typescript
// run in JSCore context or WebWorker
export function createCustomElement(tagName: string, container: CustomElement, options?: ElementCreationOptions): CustomElement {
const page = container.page
const el = new CustomElement(tagName)
... | 2021-10-13T01:38:00 | 2021-10-13T01:38:32 | {} | NONE |
vuejs | core | 938,444,982 | 4,760 | posva | Sure, make sure it's boiled down. Obviously don't copy paste the code from vant's Toast in the SFC... | 2021-10-08T08:22:28 | 2021-10-08T08:22:28 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.