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
836,295,674
2,548
viniciuskneves
Hey @HcySunYang , as a heads up, this https://github.com/vuejs/vue-next/pull/3317 has some discussion about this change. Please, also close there if this one gets merged.
2021-05-10T07:29:25
2021-05-10T07:29:25
{}
NONE
vuejs
core
836,606,395
3,752
yanbowe
这样写传入的就不是一个函数类型了吧 //Syntax Error: TypeError: Cannot read property 'content' of null //type argument passed to defineEmit() must be a function type or a literal type with call signatures
2021-05-10T11:56:37
2021-05-10T11:56:37
{}
NONE
vuejs
core
830,207,404
3,693
TakNePoidet
There is one advantage to specifying the type. Highlighted if methods, props and getters are not required ![image](https://user-images.githubusercontent.com/23022574/116723939-77fdba80-a9f9-11eb-9ade-bccafb7f4bd5.png)
2021-04-30T16:20:29
2021-04-30T16:20:29
{}
NONE
vuejs
core
830,700,058
3,716
A-Babin
It has something to do with specifying classes on the transition component. If I only add the class for my transition onto the elements inside the transition, everything works okay. But if I then also set **_any_** class on the transition component, even one that doesn't exist, by binding or attribute, the same errors ...
2021-05-01T21:56:46
2021-05-01T21:56:46
{ "+1": 1 }
NONE
vuejs
core
834,464,281
3,740
Sociosarbis
I found another bug on current `VariableDeclaration` string removal implementation. If user has `defineEmit` after `defineProps` or vice versa and the number of declarations is 2 like the following code. ```js const props = defineProps({ foo: String }), myEmit = defineEmit(['bar']) ``` The above code ...
2021-05-07T14:37:12
2021-05-07T14:40:52
{}
NONE
vuejs
core
836,509,569
3,478
ercmage
@LinusBorg Can vue3 make auto unwrapping ref is optional via params in the future? It's a source of confusion, personally i prefer no auto unwrap even it's ugly (have to write .value everytime), at least it's clear its a ref, and i don't have to fight/double think when assign/use it (lowering dev experience). ...
2021-05-10T10:11:16
2021-05-10T10:11:16
{ "+1": 3 }
NONE
vuejs
core
836,804,511
3,752
HcySunYang
@yanbowe 这样: ```js const emit = defineEmit<{(e: 'close', id: number): void; (e: 'show', name: string, age: number): void}>() emit('close', 1) emit('show', '1', 2) ```
2021-05-10T14:58:35
2021-05-10T14:58:35
{}
MEMBER
vuejs
core
830,550,216
3,710
github-actions[bot]
## Size report | Path | Size | | -------------------------- | ------------- | | vue.global.prod.js | 41.75 KB (0%) | | runtime-dom.global.prod.js | 27.62 KB (0%) | | size-check.global.prod.js | 16.8 KB (0%) |
2021-05-01T05:39:08
2021-05-01T05:39:08
{}
NONE
vuejs
core
830,554,419
3,711
dependabot-preview[bot]
One of your CI runs failed on this pull request, so Dependabot won't merge it. - [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/13567?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) Dependabot will still automatically merge this pull request if you amend it and your tes...
2021-05-01T05:50:50
2021-05-01T05:50:50
{}
CONTRIBUTOR
vuejs
core
834,082,596
3,718
HcySunYang
I see, maybe you can use `HTMLAttributes['style']` directly: ```js import { HTMLAttributes } from 'vue' export interface AProps { style?: HTMLAttributes['style'] } ```
2021-05-07T05:40:42
2021-05-07T05:40:42
{}
MEMBER
vuejs
core
837,176,345
3,014
klevron
Just another component : https://v3.vuejs.org/api/options-composition.html#extends
2021-05-10T19:14:04
2021-05-10T19:14:04
{}
NONE
vuejs
core
831,106,279
3,717
HcySunYang
```js [h(VButton, null, { default: () => 'button' }), ' in notify'] ``` The children array will be implicitly normalized, if the array is reactive, it will potentially trigger an update. For any VNode-related data, you should use `markRaw` to wrap it.
2021-05-03T08:23:40
2021-05-03T08:23:40
{}
MEMBER
vuejs
core
831,233,130
3,674
posva
Thanks @wenfangdu !
2021-05-03T12:40:28
2021-05-03T12:40:28
{}
MEMBER
vuejs
core
831,373,502
2,733
pikax
For future reference [RFC to allow this](https://github.com/vuejs/rfcs/pull/310)
2021-05-03T16:22:07
2021-05-03T16:22:07
{ "+1": 10 }
MEMBER
vuejs
core
832,262,160
3,716
lidlanca
@A-Babin maybe changing `v-if` with `v-show` will get you where you want to get. I am not sure what breaks the logic with v-if and transition, but v-show behaves better.
2021-05-04T21:31:58
2021-05-04T21:31:58
{}
CONTRIBUTOR
vuejs
core
833,928,593
3,731
dependabot[bot]
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
2021-05-06T22:55:57
2021-05-06T22:55:57
{}
CONTRIBUTOR
vuejs
core
834,039,127
3,727
HcySunYang
This is not a bug, you should use the `persisted` prop https://v3.vuejs.org/api/built-in-components.html#transition
2021-05-07T03:36:42
2021-05-07T03:36:42
{ "+1": 1 }
MEMBER
vuejs
core
834,046,074
3,718
HcySunYang
Is this for JSX type support?
2021-05-07T03:59:42
2021-05-07T03:59:42
{}
MEMBER
vuejs
core
763,507,499
3,070
github-actions[bot]
## Size report | Path | Size | | -------------------------- | -------------------- | | vue.global.prod.js | 41.81 KB (+0.13% 🔺) | | runtime-dom.global.prod.js | 27.66 KB (+0.16% 🔺) | | size-check.global.prod.js | 16.84 KB (+0.24% 🔺) |
2021-01-20T10:33:10
2021-05-07T15:57:28
{}
NONE
vuejs
core
835,707,951
2,020
binhonglee
I found out this thread in the process of migrating my project from Vue 2 to Vue 3. In Vue 2, I've used `Vue` type for passing around a component as a param but now that `CreateComponentPublicInstance` isn't exported as a type (returning type of `defineComponent()`), I can no longer do the same. As a workaround, I'm te...
2021-05-09T06:24:30
2021-05-09T06:24:30
{}
NONE
vuejs
core
836,460,665
3,751
HcySunYang
Minimum reproduction, please. A minimal reproduction means "the minimum amount of code necessary to demonstrate the problem".
2021-05-10T09:27:41
2021-05-10T09:27:41
{}
MEMBER
vuejs
core
830,549,996
3,709
github-actions[bot]
## Size report | Path | Size | | -------------------------- | ------------- | | vue.global.prod.js | 41.75 KB (0%) | | runtime-dom.global.prod.js | 27.62 KB (0%) | | size-check.global.prod.js | 16.8 KB (0%) |
2021-05-01T05:38:32
2021-05-01T05:38:32
{}
NONE
vuejs
core
830,611,898
2,513
LinusBorg
> I also tested the initial bug that introduced this modification and I cannot reproduce it in Vue 3 ( with the timestamp check disabled ), so, I am not sure if the initial problem is still valid in Vue 3. @zauan Here's a demo of the behaviour this check is meant to protect against, simulated with a custom directiv...
2021-05-01T10:51:15
2021-05-01T10:53:16
{}
MEMBER
vuejs
core
831,834,182
3,721
LinusBorg
As you can see in the "JS" tab of your SFC Playground link, using `await` at the top level results in an async setup function: ```js const __sfc__ = { expose: [], // setup is now `async` async setup(__props) { async function test(){ return 'hello' } const msg = await test() ...
2021-05-04T10:17:11
2021-05-04T10:17:11
{}
MEMBER
vuejs
core
835,766,808
3,746
posva
As you found out, you need to specify it with isCustomElement. Like other tags, they will be added if they reach standardisation across browsers but they currently are not: https://developer.mozilla.org/en-US/docs/Web/MathML#browser_compatibility. Your repro only fails on Firefox because it's the only browser supportin...
2021-05-09T09:41:15
2021-05-09T09:41:15
{}
MEMBER
vuejs
core
836,548,084
3,752
yanbowe
I tried to write it this way, but I got the same error
2021-05-10T10:53:16
2021-05-10T10:53:16
{}
NONE
vuejs
core
837,159,486
3,014
WingDust
@klevron what is Parent ?
2021-05-10T19:02:53
2021-05-10T19:02:53
{}
NONE
vuejs
core
837,766,811
3,756
HcySunYang
A workaround, use a `span` tag to wrap the `{{ number }}`: ```html <div v-loading="loading"><span>{{ number }}</span></div> ```
2021-05-11T04:11:15
2021-05-11T04:11:15
{}
MEMBER
vuejs
core
830,549,001
3,703
github-actions[bot]
## Size report | Path | Size | | -------------------------- | ------------- | | vue.global.prod.js | 41.75 KB (0%) | | runtime-dom.global.prod.js | 27.62 KB (0%) | | size-check.global.prod.js | 16.8 KB (0%) |
2021-05-01T05:35:55
2021-05-01T05:35:55
{}
NONE
vuejs
core
830,551,736
3,708
dependabot-preview[bot]
One of your CI runs failed on this pull request, so Dependabot won't merge it. - [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/13561?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) Dependabot will still automatically merge this pull request if you amend it and your tes...
2021-05-01T05:43:38
2021-05-01T05:43:38
{}
CONTRIBUTOR
vuejs
core
830,673,545
3,668
lidlanca
added dark mode to editor ( mode persist ) <img src="https://user-images.githubusercontent.com/8693091/116791366-c78ac780-aa87-11eb-8120-a894fbc68d3b.png" width=400 /> <img src="https://user-images.githubusercontent.com/8693091/116791377-d5404d00-aa87-11eb-964e-61560732647f.png" width=400 /> ![image](https://u...
2021-05-01T18:19:58
2021-05-02T04:26:17
{}
CONTRIBUTOR
vuejs
core
833,258,360
3,716
HcySunYang
Bind the `class`(or other non-props binding) to the `transition` component, which will perform the attribute fallthrough: https://github.com/vuejs/vue-next/blob/293b41ba3be095452f9648b0b35dfd9022a3621e/packages/runtime-core/src/componentRenderUtils.ts#L144 This resulted in cloning the original VNode and rendering ...
2021-05-06T06:18:24
2021-05-06T06:18:24
{ "+1": 2 }
MEMBER
vuejs
core
834,300,635
3,738
Hozeee
> What about `data-key` or `key-prop` ? Unfortunately, we can't modify the external webcomponent lib attributes, also these elements are set to custom elements in Vue.
2021-05-07T11:46:29
2021-05-07T11:46:29
{}
NONE
vuejs
core
835,818,024
2,143
yaquawa
Now it shows the `<router-view />` but not showing the `<template #fallback>`, is this is the intended behavior?
2021-05-09T14:27:15
2021-05-09T14:27:15
{ "eyes": 4 }
NONE
vuejs
core
830,549,051
3,704
github-actions[bot]
## Size report | Path | Size | | -------------------------- | ------------- | | vue.global.prod.js | 41.75 KB (0%) | | runtime-dom.global.prod.js | 27.62 KB (0%) | | size-check.global.prod.js | 16.8 KB (0%) |
2021-05-01T05:36:03
2021-05-01T05:36:03
{}
NONE
vuejs
core
830,549,548
3,707
github-actions[bot]
## Size report | Path | Size | | -------------------------- | ------------- | | vue.global.prod.js | 41.75 KB (0%) | | runtime-dom.global.prod.js | 27.62 KB (0%) | | size-check.global.prod.js | 16.8 KB (0%) |
2021-05-01T05:37:21
2021-05-01T05:37:21
{}
NONE
vuejs
core
830,549,826
3,704
dependabot-preview[bot]
One of your CI runs failed on this pull request, so Dependabot won't merge it. - [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/13555?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link) Dependabot will still automatically merge this pull request if you amend it and your tes...
2021-05-01T05:38:01
2021-05-01T05:38:01
{}
CONTRIBUTOR
vuejs
core
833,555,270
2,860
bjkippax
> Should this issue be labelled as a bug instead of a feature? Tree shaking seems like a critical feature for vue 3 given the changes to the global API and the switch from options to composition. I'd be inclined to agree here. Tree-shaking is fantastic and to have it not working is inconvenient.
2021-05-06T14:11:17
2021-05-06T14:11:17
{}
NONE
vuejs
core
836,318,087
3,317
HcySunYang
Hey @viniciuskneves, thanks for this PR, but I will close it because https://github.com/vuejs/vue-next/pull/2548 precedes this PR
2021-05-10T07:50:17
2021-05-10T07:51:48
{ "+1": 1 }
MEMBER
vuejs
core
875,670,633
3,618
rashfael
I get your point about computed properties being transient and storing references to it this way is problematic. I our real world case the computed property actually has dependencies, which get transformed. Looks like I went too minimal in my reproduction. The event used is also much more short lived (mouseenter/mo...
2021-07-07T14:50:55
2021-07-07T14:50:55
{}
NONE
vuejs
core
876,170,197
4,076
posva
Yeah, thanks! So, it's what I said before: the inject should happen before the `createApp()`
2021-07-08T06:34:25
2021-07-08T06:34:25
{}
MEMBER
vuejs
core
876,477,740
4,076
tangjinzhou
This is not friendly for user, and we have no way to judge whether there is a createApp before inject
2021-07-08T14:16:39
2021-07-08T14:16:39
{}
CONTRIBUTOR
vuejs
core
877,034,946
4,083
skirtles-code
I haven't checked your repo in detail but from the symptoms I suspect you're pulling in two copies of Vue. See https://github.com/vuejs/vue-next/issues/2064#issuecomment-797365133 for a possible solution.
2021-07-09T09:03:38
2021-07-09T09:05:17
{}
CONTRIBUTOR
vuejs
core
878,245,750
4,106
posva
Thanks for the links! So the `as` cast can always be used while the other one cannot. That is enough of a reason to not use the half working syntax. After all, the `as` cast was introduced because of the incompatibility of the old cast syntax with jsx. If right now tsx works in `lang=ts`, introducing the change you ...
2021-07-12T12:39:53
2021-07-12T12:48:05
{}
MEMBER
vuejs
core
878,327,403
4,106
posva
> So if this is specific to script setup compilation, then it's still marked as experimental and this is the last moment to fix it! That's true! It would be acceptable to change the behavior right now and I doubt it will affect a lot of people. I haven't tried the different combinations but keeping the behavior c...
2021-07-12T14:29:11
2021-07-12T14:29:11
{}
MEMBER
vuejs
core
879,187,874
2,533
FossPrime
I had the same problem, here is a reproduction, try to run `vue serve` under pwa after bootup https://codesandbox.io/s/2533-ovbws?file=/sandbox.config.sh
2021-07-13T15:29:08
2021-07-13T15:29:15
{}
NONE
vuejs
core
879,741,612
4,092
jods4
Yes, I agree. I opened this when my slot was implicitly typed as `any` in IDE. Now I think this was because the component providing the slot was a script-classic, as it seems that script-setup is inferred by Volar / vue-tsc. There's no need for manually declaring `defineSlots` if they can be automatically infer...
2021-07-14T09:27:39
2021-07-14T09:27:39
{}
CONTRIBUTOR
vuejs
core
880,845,834
3,993
vricosti
Same problem here: > <td> <input type="text" v-model="getValuesMarginMin()[0]" :class="'entry '+getUserInputStatusClass(getValuesMarginMin()[3])" disabled /> </td> `export default { store: store, name: "ValuesConstraintsMarginUnit", mixin...
2021-07-15T16:34:48
2021-07-15T16:52:14
{}
NONE
vuejs
core
880,875,601
4,104
yyx990803
fixed by c0db8078
2021-07-15T17:17:57
2021-07-15T17:17:57
{}
MEMBER
vuejs
core
875,634,758
3,621
yyx990803
https://github.com/vuejs/vue-next/issues/3618#issuecomment-875633557
2021-07-07T14:06:44
2021-07-07T14:06:44
{}
MEMBER
vuejs
core
875,826,603
4,017
yyx990803
Great work, thank you so much @basvanmeurs ! Note I refactored this PR in ab8bc719860c25ba3895489471fba22bce061d41 mainly to cut down the size increase (+0.29kb -> 0.21kb) since the new additions are non-tree-shakeable.
2021-07-07T18:19:42
2021-07-07T18:19:42
{ "laugh": 1, "rocket": 3 }
MEMBER
vuejs
core
877,777,086
3,678
Bruce-Ming
@YY88Xu 解决了,是webview的触发时机不一致的问题,你也是用的webview?可以在加载vue之前就注册监听。然后发布订阅模式出发vue里面的回调
2021-07-11T10:36:59
2021-07-11T10:36:59
{}
NONE
vuejs
core
877,927,707
4,093
likeswinds
@LinusBorg It's not work for computed,you need to rewrap the ref, why? ![image](https://user-images.githubusercontent.com/7099174/125223078-bc60dd00-e2fd-11eb-9a6e-b3ed6be30f72.png) [demo](https://codesandbox.io/s/nostalgic-dew-dktzr?file=/src/components/HelloWorld.vue)
2021-07-12T02:44:02
2021-07-12T02:44:02
{}
NONE
vuejs
core
877,980,350
4,104
ycs77
@edison1105 Need to modify 2 times and save 1. replace line 3 class `max-w-screen-sm` to `max-w-screen-md` and save file 2. replace line 3 class `max-w-screen-md` to `max-w-screen-lg` and save file 3. look the error message: ![console-shotcut](https://user-images.githubusercontent.com/38133356/125235524-2d5fbf00-e31...
2021-07-12T05:20:34
2021-07-12T05:30:08
{}
NONE
vuejs
core
879,078,544
4,088
yyx990803
This is not necessary. Warnings are dropped only in client builds to reduce bundle size. These warnings are intentionally kept in SSR.
2021-07-13T13:15:30
2021-07-13T13:15:30
{}
MEMBER
vuejs
core
875,646,289
1,811
yyx990803
This is fixed by d05c9a7b (will be out in 3.2)
2021-07-07T14:20:19
2021-07-07T14:20:19
{ "hooray": 2 }
MEMBER
vuejs
core
875,648,546
4,051
yyx990803
/cc @pikax @johnsoncodehk would appreciate some insights into this
2021-07-07T14:23:03
2021-07-07T14:23:03
{}
MEMBER
vuejs
core
875,661,875
4,051
pikax
> would appreciate some insights into this Caused by https://github.com/vuejs/vue-next/pull/3656 I'll work on a fix.
2021-07-07T14:39:50
2021-07-07T14:39:50
{}
MEMBER
vuejs
core
876,287,430
4,080
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).
2021-07-08T09:32:09
2021-07-08T09:32:09
{}
MEMBER
vuejs
core
877,323,701
4,097
posva
Another workaround is to use a function: ```html <Input v-if="mode === 'broken'" :modelValue="state.text" @update:modelValue="e => state['text'] = e" /> ```
2021-07-09T16:55:43
2021-07-09T16:55:43
{}
MEMBER
vuejs
core
878,208,463
4,106
posva
Does this happen in other cases than the old version of casting? You should use `as any` instead as it was introduced in TS to avoid this kind of issues. (https://github.com/vuejs/vue-next/issues/3598)
2021-07-12T11:40:47
2021-07-12T11:40:47
{}
MEMBER
vuejs
core
878,286,207
4,106
jods4
I agree using `as` instead of cast is not a big deal. Generics problems can be complex to work-around as demonstrated in the SO discussion. > That one works in the SFC playground. For the anecdote, generics problems happen. I had opened an issue in eslint-vue plugin exactly for that, some of my generic code wa...
2021-07-12T13:36:56
2021-07-12T13:36:56
{}
CONTRIBUTOR
vuejs
core
878,358,694
2,179
ctrlplusb
Thank the heavens. 😀 Stoked to see these utilities being considered. I've extracted the `ComponentProps` utility from this PR into my project and am using it now. 🙏
2021-07-12T15:09:11
2021-07-12T15:20:55
{ "+1": 1 }
NONE
vuejs
core
879,093,669
4,113
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-07-13T13:35:18
2021-07-13T13:35:18
{}
CONTRIBUTOR
vuejs
core
879,272,227
4,107
lidlanca
source: ``` transformOn const isMemberExp = isMemberExpression(exp.content); ``` `a?.b` evals to false, that is where the logic differ compared to the `a.b` expression. also `isMemberExpression` is used to check for assignability of an expression, and optional chaining is not assignable. that is not...
2021-07-13T17:33:27
2021-07-13T18:10:09
{}
CONTRIBUTOR
vuejs
core
879,365,478
3,792
yyx990803
Closed via 34a0eadb
2021-07-13T20:05:09
2021-07-13T20:05:09
{ "+1": 3 }
MEMBER
vuejs
core
875,611,528
1,942
turrsis
It seems to me that checking for type .__ hmrId is unnecessary : https://github.com/vuejs/vue-next/blob/03e26845e2c220b1350a35179acf3435e2711282/packages/runtime-core/src/componentProps.ts#L201
2021-07-07T13:37:55
2021-07-07T13:37:55
{}
CONTRIBUTOR
vuejs
core
875,698,511
4,076
posva
This is expected, it's even used at https://github.com/vueuse/vueuse/blob/main/packages/core/createGlobalState/index.ts) until `effectScope()` is released. You need to move any provide/inject inside `setup()` before any `createApp` call. You shouldn't call `createApp()` inside of a Vue component either BTW yo...
2021-07-07T15:23:58
2021-07-07T15:23:58
{}
MEMBER
vuejs
core
876,538,603
4,083
posva
Open an issue in the two repositories or open an issue that doesn't use those repositories. If the bug is within vue compiler, you should be able to use https://sfc.vuejs.org to generate the js and copy paste on the same website to create sharable reproduction
2021-07-08T15:33:26
2021-07-08T15:33:26
{}
MEMBER
vuejs
core
878,329,939
1,679
posva
See https://v3.vuejs.org/api/options-misc.html#delimiters for updated instructions
2021-07-12T14:32:29
2021-07-12T14:32:29
{}
MEMBER
vuejs
core
879,075,406
4,110
yyx990803
That's a won't fix. Just use a semicolon.
2021-07-13T13:11:44
2021-07-13T13:11:44
{}
MEMBER
vuejs
core
876,051,565
4,076
tangjinzhou
@posva sorry, I change new reproduction. can you review this issue again? thank you very much
2021-07-08T01:40:40
2021-07-08T01:40:40
{}
CONTRIBUTOR
vuejs
core
876,834,377
4,084
edison1105
This is expected, `setRef` will execute on each time patch and unmount.
2021-07-09T00:50:42
2021-07-09T00:50:42
{}
MEMBER
vuejs
core
877,084,925
4,093
likeswinds
Currently, this can only be done using the function h() ``` js import { defineComponent, h, ref, resolveComponent } from 'vue' export default defineComponent({ setup() { const data = ref({ v1: 'test', v2: 'test2' }) return { data } }, render() { const props = { modelValue: this.data....
2021-07-09T10:28:39
2021-07-09T10:28:39
{}
NONE
vuejs
core
877,103,519
4,091
posva
Do you have a boiled down reproduction or a failing test case?
2021-07-09T11:04:22
2021-07-09T11:04:22
{}
MEMBER
vuejs
core
877,428,419
4,084
yyx990803
This is intended behavior. The cost of setting a ref with the same value is negligible and it enables the pattern of constructing fresh ref lists on each render.
2021-07-09T20:07:30
2021-07-09T20:07:30
{ "+1": 2 }
MEMBER
vuejs
core
878,971,740
4,111
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-07-13T10:28:49
2021-07-13T10:28:49
{}
CONTRIBUTOR
vuejs
core
880,535,380
3,943
AurelieV
For information, we had a similar bug with a combination of v-for and slot which raised many error in the console and break a component when we change the v-for data. We try the propose fix at it also solves our problem.
2021-07-15T09:15:44
2021-07-15T09:15:44
{}
NONE
vuejs
core
877,696,876
4,101
posva
This is expected because extends is like mixins as doesn't reuse anything from the template as it has been discussed before under the name of code blocks and others in vue repo. You need to [forward the slots yourself](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8cGFyZW50LWNvbT5cbiAgICBwYXJlbnQgY29udGVud...
2021-07-10T20:06:43
2021-07-10T20:06:43
{}
MEMBER
vuejs
core
877,795,573
3,678
YY88Xu
我看了一下应该是 Vue Router 4 的原因;单纯的 Vue3 是支持的,使用 Vue Router 然后在 setup 中注册是不起作用的。
2021-07-11T12:59:27
2021-07-11T12:59:27
{}
NONE
vuejs
core
877,984,621
4,104
edison1105
@ycs77 uh~ sorry for that. I will check it later.
2021-07-12T05:32:02
2021-07-12T05:32:02
{}
MEMBER
vuejs
core
878,295,380
1,679
guilhermemart
I have the same problem. Doing: Vue.createApp({ delimiters: ['{%', '%}'] ... }) we lose all the functionalities of Vue.createApp(App) How can we still rendering App but with delimiters changed?
2021-07-12T13:49:22
2021-07-12T13:49:22
{}
NONE
vuejs
core
879,740,538
3,548
RemMai
老哥,我就问这个问题解决没有。 我使用 ```html <suspense> <router-view /> </suspense> ``` 包含子页面的时候,子页面全部是 async setup {} , 如果切换过快的话,会出现`TypeError: Cannot read property 'parentNode' of null` 而且后面 router.push() 无法进行跳转。 啥时候解决啊,谢谢大佬啊
2021-07-14T09:25:58
2021-07-14T09:25:58
{ "confused": 19 }
NONE
vuejs
core
879,775,930
4,091
jaulz
Hm, I tried the whole morning to create a reproducible simple test case but for some reason it only appears in my "big" app. Also, as soon as I set breakpoint in one of the triggers (that I can see in the stacktrace) the issue does not appear anymore. The issue appears when I leave the tab and activate it again. I ...
2021-07-14T10:22:07
2021-07-14T10:22:07
{}
CONTRIBUTOR
vuejs
core
880,969,358
4,121
yyx990803
Hmm, the logic is guarded to be only applied to component vnodes: https://github.com/vuejs/vue-next/blob/4f17be7b1ce4872ded085a36b95c1897d8c1f299/packages/runtime-core/src/compat/componentVModel.ts#L18 I'd love to see a reproduction to make sure we find the right fix.
2021-07-15T19:51:03
2021-07-15T19:51:03
{}
MEMBER
vuejs
core
876,053,498
3,930
qmhc
@xsdream 你提醒了我,我想起我之前在 monorepo 下两个子应用包同时引用全局 store 包时会发生 store 被初始化两次(被解析成两个包),需要使用 `resolve.dedupe` 选项解决。 这个问题估计是由于 link 协议会让 vite 重新解析依赖,导致打包了多份 vue 而导致的错误,通过 `resolve.dedupe` 显式指定 vue 为同一副本。至于第二点应该是没有影响的。
2021-07-08T01:46:06
2021-07-08T01:46:06
{}
NONE
vuejs
core
876,481,626
4,076
tangjinzhou
I cannot give some warning.
2021-07-08T14:21:28
2021-07-08T14:21:28
{}
CONTRIBUTOR
vuejs
core
876,811,014
4,082
TANGENNT
> I think you should use new Array (length) instead of [] for the test. Thanks for replying. I test again both on apple m1 mac and x86 amd win10. And the result shows that using new Array(length), `fill` is not the fastest. m1 mac: ![m1](https://user-images.githubusercontent.com/37934144/125002589-2f223d80-e0...
2021-07-08T23:40:12
2021-07-08T23:40:12
{}
NONE
vuejs
core
877,599,404
4,099
posva
Lodash is a dev dependency, it's not exposed in the final package
2021-07-10T08:50:03
2021-07-10T08:50:03
{}
MEMBER
vuejs
core
879,078,782
4,089
yyx990803
https://github.com/vuejs/vue-next/pull/4088#issuecomment-879078544 `useSSRContext` is server only so the warning is also intentionally preserved.
2021-07-13T13:15:49
2021-07-13T13:15:49
{}
MEMBER
vuejs
core
880,229,712
4,092
yyx990803
If the remaining utility is only related to generic components, I think it would be better discussed as part of the generic components proposal. So closing this one here.
2021-07-14T21:42:27
2021-07-14T21:42:27
{ "+1": 1 }
MEMBER
vuejs
core
876,930,721
4,084
LinusBorg
It's currently implemented this way intentionally, yes I wonder if we can optimize it though. We should be able to compare the ref value for the old and vnode and skip the operation if they have the same value. Edit: That's colliding a bit with the pattern of using a ref function on a v-for element, were we recommen...
2021-07-09T05:46:00
2021-07-09T06:25:59
{}
MEMBER
vuejs
core
877,078,696
3,990
jods4
@posva can you please re-open this? At first I had issues inside Volar, so I was unsure where the problem was, but now I'm seeing similar errors in my build that fails because of this. @johnsoncodehk's last comment showed one repro of this issue. In my project, the following fails to compile: ```html <!-- Comp...
2021-07-09T10:17:47
2021-07-09T10:17:47
{}
CONTRIBUTOR
vuejs
core
877,431,999
1,791
vertcitron
@CyberAP Your idea is very good, and I think I'll try to implement it this way, and maybe I will not have to modify the server-renderer package, if I'm able to call the renderToString of the server renderer function from the render function of this cache wrapper on the default slot content... And on Client Side, the c...
2021-07-09T20:14:10
2021-07-09T20:14:10
{}
NONE
vuejs
core
877,726,222
2,043
thexeos
I'm trying to inject a Boolean value into all components (SFC), which provide/inject seems best suited for. I have Vue 3.1.2. I tried calling: ```javascript const injectedRef = ref(getCurrentState()) app.provide('injectedName', injectedRef) ``` ![UZu7neyjaw](https://user-images.githubusercontent.com/2260539...
2021-07-11T01:28:52
2021-07-11T01:28:52
{}
NONE
vuejs
core
878,223,620
4,106
jods4
I wasn't aware this syntax was _old_ or not recommended. The [official docs](https://www.typescriptlang.org/docs/handbook/2/everyday-types.html#type-assertions) say: > You can also use the angle-bracket syntax (except if the code is in a .tsx file), which is equivalent And in [the as section](https://www.typescrip...
2021-07-12T12:06:16
2021-07-12T12:06:16
{}
CONTRIBUTOR
vuejs
core
879,273,037
4,114
posva
It's ```js import { h } from "vue"; import Test from "./Test.vue"; export default { name: "App", render() { return h(Test, { hello: "world", }); }, }; ```
2021-07-13T17:34:43
2021-07-13T17:34:43
{}
MEMBER
vuejs
core
880,799,154
4,124
yyx990803
👍
2021-07-15T15:37:19
2021-07-15T15:37:19
{ "+1": 1 }
MEMBER
vuejs
core
875,596,184
1,942
turrsis
A similar error with custom directives. Component properties are not updated while a custom directive is set.
2021-07-07T13:18:24
2021-07-07T13:18:24
{}
CONTRIBUTOR
vuejs
core
875,679,660
4,051
johnsoncodehk
Sorry about that. 🙈 Maybe combine `[K in keyof O]?: unknown;` and `[K in OptionalKeys<O>]?: InferPropType<O[K]>;` is works. ```ts export declare type ExtractPropTypes<O> = O extends object ? { [K in RequiredKeys<O>]: InferPropType<O[K]>; } & { [K in keyof O]?: InferPropType<O[K]>; } : { [K in s...
2021-07-07T15:01:15
2021-07-07T15:02:40
{}
MEMBER