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
889,370,309
4,203
lidlanca
for the most part you can also just add a space to trigger re compilation with the selected version.
2021-07-29T18:36:29
2021-07-29T18:36:29
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
889,907,025
4,212
posva
That would be a breaking change though. That kind of feature request should go through an RFC in the rfcs repo anyway
2021-07-30T13:51:24
2021-07-30T13:51:24
{}
MEMBER
vuejs
core
889,909,690
4,214
jods4
> Then don't open an issue without a repro. It looks like every time I think there couldn't be "more" to the issue, every time I'm wrong and it's dependent on weird conditions I couldn't even imagine 😓 BTW I wanted to create a repro in the SFC explorer first (link in issue), but as I mentioned you can't choose i...
2021-07-30T13:55:37
2021-07-30T13:55:37
{}
CONTRIBUTOR
vuejs
core
885,560,087
4,181
posva
Open an issue with an actual reproduction and in English thank you
2021-07-23T10:57:00
2021-07-23T10:57:00
{}
MEMBER
vuejs
core
889,320,944
3,460
yyx990803
After 0867222, `@vue/server-renderer` when bundled will default to the esm-bundler build which should no longer have coupling to Node.js.
2021-07-29T17:16:02
2021-07-29T17:16:02
{}
MEMBER
vuejs
core
884,681,450
4,170
edison1105
see https://developer.mozilla.org/zh-CN/docs/Web/API/HTMLSelectElement > HTMLSelectElement.value A DOMString reflecting the value of the form control. Returns the value property of the first selected option element if there is one, otherwise the empty string. that's means `event.target.value` always be a string....
2021-07-22T06:19:30
2021-07-22T06:22:25
{}
MEMBER
vuejs
core
885,471,706
4,171
DrMabuse23
https://twitter.com/youyuxi/status/1414594164168269828?s=21 i just have this information @yyx990803
2021-07-23T08:06:23
2021-07-23T08:08:05
{}
NONE
vuejs
core
885,646,467
4,180
exodusanto
This is the compiler error after update from 3.1.5 to 3.2.0-beta.4 ``` TS2322: Type '{ readonly value: readonly { readonly label: string; readonly value: string; }[]; readonly dep?: ReadonlySet<{ readonly fn: () => any; readonly scheduler: EffectScheduler | null; readonly active: boolean; ... 7 more ...; readonly s...
2021-07-23T13:40:05
2021-07-23T13:40:05
{}
NONE
vuejs
core
886,295,571
4,191
edison1105
@LBJDJW ```javascript import { useSlots } from 'vue' //... const slots = useSlots() ```
2021-07-26T01:00:59
2021-07-26T01:00:59
{}
MEMBER
vuejs
core
887,932,046
4,201
edison1105
uh~ sorry. it's my fault.
2021-07-28T01:02:50
2021-07-28T01:13:18
{ "+1": 1 }
MEMBER
vuejs
core
888,028,741
2,143
obadakhalili
@yaquawa > Now it shows the `<router-view />` but not showing the `<template #fallback>`, is this is the intended behavior? https://v3.vuejs.org/guide/migration/suspense.html#:~:text=Vue%20Router%20has,the%20usual%20way.
2021-07-28T05:48:02
2021-07-28T05:48:02
{}
NONE
vuejs
core
884,724,994
4,172
posva
Use the chat and forum for questions. Thanks.
2021-07-22T07:59:57
2021-07-22T07:59:57
{}
MEMBER
vuejs
core
885,004,831
4,178
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). --- The experimental ref sugar syntax changed, check...
2021-07-22T15:27:48
2021-07-22T15:27:48
{}
MEMBER
vuejs
core
887,403,995
1,600
aztack
> @areve, it's great to see you got it working, thanks for sharing your config! 👍 > > I still can't make it work with slots though. > I've created a reproduction on CodeSandbox where I demo exactly the problem: https://codesandbox.io/s/interesting-cookies-dy7wn?file=/src/App.vue > > The whitespaces (new lines i...
2021-07-27T10:37:07
2021-07-27T10:37:07
{}
NONE
vuejs
core
887,507,856
4,198
posva
Updated the repro so it doesn't contain vue router
2021-07-27T13:21:53
2021-07-27T13:21:53
{}
MEMBER
vuejs
core
884,082,749
4,165
github-actions[bot]
## Size report | Path | Size | | -------------------------- | ------------- | | vue.global.prod.js | 45.65 KB (0%) | | runtime-dom.global.prod.js | 30.12 KB (0%) | | size-check.global.prod.js | 17.32 KB (0%) |
2021-07-21T10:32:38
2021-07-28T08:26:32
{}
NONE
vuejs
core
889,885,596
4,214
jods4
Well, I tried variations and it is a bit fiddly. It reproduces with `lang=ts` but the only case that seems _not_ to work is an `import` with a capital `V`, like so: `import VDir from "./dir"`. If you try a small `v` it works. It you try a local function named `VDir` it works as well. Here's a repro: https://gi...
2021-07-30T13:14:55
2021-07-30T13:14:55
{}
CONTRIBUTOR
vuejs
core
889,888,984
4,212
lidlanca
@posva I might not have been too clear, but this was not a question on how to get the raw value for a ref or computed it was a proposal to make toRaw work consistently whether you pass ref/computed/reactive object. as to extract the raw value and **not trigger reactivity**. The ref wrapping a reactive object was...
2021-07-30T13:20:17
2021-07-30T13:20:17
{}
CONTRIBUTOR
vuejs
core
884,800,438
4,098
pikax
I was thinking we could have something similar to what React does https://github.com/vuejs/vue-next/pull/3370
2021-07-22T10:12:47
2021-07-22T10:12:47
{ "hooray": 1 }
MEMBER
vuejs
core
885,452,157
4,179
flicat
完整代码: #### App.vue ```html <template> <myCom></myCom><!--能正常显示--> </template> <script> import { getCurrentInstance } from 'vue' import my_plugin from './my_plugin.js' import option_com from './option_com.vue' import my_com from './my_com.vue' export default { setup() { const app = getCurrentI...
2021-07-23T07:24:59
2021-07-23T08:24:29
{}
NONE
vuejs
core
885,530,192
4,179
flicat
> @flicat > see [#2097 (comment)](https://github.com/vuejs/vue-next/issues/2097#issuecomment-707975628) thanks, give up :joy:
2021-07-23T09:57:58
2021-07-23T09:57:58
{}
NONE
vuejs
core
886,030,034
4,187
edison1105
@wellfrog16 `default: function () {return ''}` 应该也可以推断出正确的类型。需要优化。
2021-07-24T10:00:49
2021-07-24T10:00:49
{}
MEMBER
vuejs
core
887,335,853
4,197
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-27T08:55:19
2021-07-27T08:55:19
{}
CONTRIBUTOR
vuejs
core
887,952,552
4,203
edison1105
this is because `createElementBlock` is a feature of v3.2. It's will render failed when changing the version from v3.2 to v3.1. Maybe should re-generate the render function when changing the version. as workaround 1. clear content of App.vue 2. change the version 3. edit App.vue
2021-07-28T02:04:44
2021-07-28T02:04:44
{}
MEMBER
vuejs
core
885,359,085
4,122
Fallsleep
this is cause by [antfu/vite-plugin-components#107](https://github.com/antfu/vite-plugin-components/issues/107),and is fixed with vite-plugin-components 0.13.2
2021-07-23T02:34:18
2021-07-23T02:34:18
{}
NONE
vuejs
core
887,348,944
4,196
posva
I think it would make sense to unwrap the injected properties in the template like when they are returned in setup: ```js export default { setup() { return { user: inject('user') } } } ```
2021-07-27T09:14:08
2021-07-27T09:14:08
{}
MEMBER
vuejs
core
887,448,676
4,198
yaquawa
@edison1105 Thanks! I've subscribed the PR.
2021-07-27T11:54:04
2021-07-27T11:54:04
{}
NONE
vuejs
core
888,119,736
4,165
posva
I see. Well, in that case, I'm not sure if this is needed at all. It can definitely wait since it's trivial to implement in userland.
2021-07-28T08:28:56
2021-07-28T08:28:56
{}
MEMBER
vuejs
core
888,788,482
3,944
catrope
The fix from Vue 2 was retained in Vue 3 at first, and was also proposed to be retained in #1100, but was (accidentally?) removed in 3c60d40827f65cbff024cfda4bb981a742bb83a7. I've submitted a pull request to put the old behavior back
2021-07-29T04:18:27
2021-07-29T04:18:27
{}
CONTRIBUTOR
vuejs
core
889,790,230
4,214
jods4
Kind of confirming my suspicion of 5a3ccfd being the cause: it last worked in beta.4 and is broken since beta.5 (where that changed was introduced). Doesn't work up to latest beta.7.
2021-07-30T10:11:42
2021-07-30T10:11:42
{}
CONTRIBUTOR
vuejs
core
889,835,838
4,214
posva
Couldn't reproduce on an epmty vite project. Please open a new issue with an actual reproduction.
2021-07-30T11:41:12
2021-07-30T11:41:12
{}
MEMBER
vuejs
core
885,385,504
4,179
flicat
createApp 之后 调用 mount 方法,或者还有别的方法可以添加第三方组件的DOM到页面中?
2021-07-23T04:10:25
2021-07-23T04:10:25
{}
NONE
vuejs
core
885,481,971
4,179
edison1105
@flicat see https://github.com/vuejs/vue-next/issues/2097#issuecomment-707975628
2021-07-23T08:24:18
2021-07-23T08:34:41
{}
MEMBER
vuejs
core
886,327,216
3,849
aztack
> **In Vite** it works in version `vue@3.1.0-beta.6`, with explicit load of `"@vue/compiler-sfc": "3.1.0-beta.6"` with this config: > > ```js > export default defineConfig({ > plugins: [ > vue({ > template: { > compilerOptions: { > whitespace: 'preserve' > } > } >...
2021-07-26T02:35:40
2021-07-26T02:35:40
{}
NONE
vuejs
core
886,546,557
4,191
LBJDJW
THANK YOU
2021-07-26T09:43:08
2021-07-26T09:43:08
{}
NONE
vuejs
core
887,765,162
4,196
lidlanca
@posva are you suggesting that `toDisplayString` should always `unref` any object that is passed to it? or you saying that using setup is the fix
2021-07-27T19:11:03
2021-07-27T19:14:01
{}
CONTRIBUTOR
vuejs
core
887,784,611
4,196
posva
Neither. Using setup is a workaround. In the template, you should only need to write `user` not `user.value` in both cases (option and setup api). But I'm only suggesting it and giving one argument for it
2021-07-27T19:42:45
2021-07-27T19:42:45
{}
MEMBER
vuejs
core
887,795,061
4,196
jmcooper
Having not looked at the code, I don't know if this would be possible (or how difficult), but to avoid a breaking change it could perhaps unwrap the value, but also ignore `.value` in the template for previously wrapped items if the user provides it in the template for something that is already unwrapped. Might be mess...
2021-07-27T20:00:10
2021-07-27T20:00:10
{}
NONE
vuejs
core
888,305,919
4,208
Justineo
#3564 is an intentional change to align the behavior with [this RFC](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0024-attribute-coercion-behavior.md).
2021-07-28T13:23:05
2021-07-28T13:23:05
{ "+1": 1 }
MEMBER
vuejs
core
872,304,309
2,863
TimWeidner
> Thanks for the effort @chrislone @yyx990803. This issue was closed by your PR, however, the original repro still doesn't work even after updating to 3.0.11. > Has this been published? Just for the record, this currently works with Vue 3.1.2
2021-07-01T14:40:38
2021-07-01T14:40:38
{}
NONE
vuejs
core
872,753,640
4,052
skirtles-code
Seems like the same issue reported against the CLI repo: https://github.com/vuejs/vue-cli/issues/6562
2021-07-02T06:31:35
2021-07-02T06:31:35
{}
CONTRIBUTOR
vuejs
core
872,937,013
4,054
yyx990803
repro link seems broken.
2021-07-02T11:45:58
2021-07-02T11:45:58
{}
MEMBER
vuejs
core
873,404,786
4,058
posva
Duplicate of https://github.com/vuejs/vue-next/issues/2828
2021-07-03T13:01:23
2021-07-03T13:01:23
{}
MEMBER
vuejs
core
873,585,088
4,060
LinusBorg
Hm, indeed. I'll open it for now as I'm not sure from the top of my head wether that was intentional etc.
2021-07-04T12:58:49
2021-07-04T12:58:49
{}
MEMBER
vuejs
core
874,070,367
4,061
LinusBorg
I'm not sure what you think is wrong. * You initially render the component -> console.log * You destroy the component with v-if="false" * You render the component again -> console.log - which is correct. Refreshing the page doesn't change anything about this for me.
2021-07-05T12:21:00
2021-07-05T12:21:00
{}
MEMBER
vuejs
core
875,074,115
1,228
mgdodge
As a less-than-ideal workaround, I just copied the file from `node_modules/@vue/runtime-core/dist/runtime-core.d.ts` into a `src/types` directory in my project, and commented out the lines where the const enums were (currently lines 1112-1113, 1593, and 1621). I then put the following into my `tsconfig.json` `paths` co...
2021-07-06T20:53:54
2021-07-06T20:53:54
{}
NONE
vuejs
core
873,024,233
4,050
jods4
Here's a new API proposal. Async code is really tricky, I hope I thought of everything, even if I didn't spell it out fully -- and that's already a very long post. 🤞 I am not a huge fan but I don't have a better idea right now, I tried to balance ease of use and correctness as much as possible... ### Far future...
2021-07-02T14:04:20
2021-07-02T14:04:20
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
873,575,170
4,060
xanf
@LinusBorg this behavior differs from Vue2 :) Probably should note that at least for compat build :)
2021-07-04T12:00:29
2021-07-04T12:00:29
{}
CONTRIBUTOR
vuejs
core
874,824,636
4,072
yyx990803
Closing as duplicate
2021-07-06T14:45:16
2021-07-06T14:45:16
{}
MEMBER
vuejs
core
872,706,870
2,195
basvanmeurs
Thanks for the `getEffectScope` addition @antfu. I can see your point about the global effect scope :+1: Thanks for resolving but @yyx990803 has added your PR to the roadmap for 3.2 (https://github.com/vuejs/vue-next/projects/4). I think that you need to rebase your PR to branch 3.2? The 3.2 branch contains mor...
2021-07-02T04:37:04
2021-07-02T04:37:04
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
872,787,027
4,052
haoqunjiang
Caused by a TypeScript version bump. We should never set the target to `esnext` again. Workaround: ```js // vue.config.js module.exports = { transpileDependencies: ['@vue/reactivity'] } ```
2021-07-02T07:34:57
2021-07-02T07:34:57
{ "+1": 7, "heart": 2 }
MEMBER
vuejs
core
872,904,805
4,050
jods4
I'm sharing one failed idea, just in case it inspires someone: I thought I could subclass `Promise` into a `VuePromise`, or just create a `VueThenable`. (Subclassing `Promise` is super-tricky, but doable) My idea was to set/remove context in `.then()` just so that it happens synchronously with the continuation i...
2021-07-02T10:46:14
2021-07-02T10:46:14
{}
CONTRIBUTOR
vuejs
core
872,999,742
4,049
edison1105
duplicate of https://github.com/vuejs/vue-next/issues/3921
2021-07-02T13:29:31
2021-07-02T13:29:31
{ "+1": 1 }
MEMBER
vuejs
core
874,026,260
4,063
LinusBorg
Hello .. Thank your for your interest in this project. However, your issue is a usage/support question, and the issue tracker is reserved exclusively for bug reports and feature requests (as outlined in our [Contributing Guide](https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md)). We encourage you t...
2021-07-05T11:09:02
2021-07-05T11:09:02
{}
MEMBER
vuejs
core
874,036,698
4,061
attackam
https://codesandbox.io/s/compassionate-lovelace-tft0x?file=/src/App.vue:0-663
2021-07-05T11:24:10
2021-07-05T11:24:10
{}
NONE
vuejs
core
874,073,723
4,065
robertmoura
These are some quick shots of the performance reports for the click listeners: Unoptimised check list <img width="904" alt="Screen Shot 2021-07-05 at 10 23 05 pm" src="https://user-images.githubusercontent.com/17804984/124471002-b344ad00-dddf-11eb-8571-9fc2b22177f3.png"> Optimised check list - component <img wi...
2021-07-05T12:26:54
2021-07-05T12:26:54
{ "+1": 6 }
NONE
vuejs
core
874,557,082
4,049
posva
Duplicate of #3921
2021-07-06T08:14:22
2021-07-06T08:14:22
{}
MEMBER
vuejs
core
874,856,612
3,596
nfplee
I've been looking at [petite-vue](https://github.com/vuejs/petite-vue) this weekend and that's exactly how I've been using Vue. This is why I believe these warnings should be removed since they interfere with SSR and Vue should ideally be a superset of Petite-Vue.
2021-07-06T15:23:54
2021-07-06T15:23:54
{}
NONE
vuejs
core
874,870,112
4,073
posva
Please follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro (e.g. no TS, no router in reproduction) when opening an issue. You should also check existing issues to see if this has already been fixed.
2021-07-06T15:41:13
2021-07-06T15:41:13
{}
MEMBER
vuejs
core
874,551,561
4,068
posva
Introducing something like `<style critical>` should definitely go through an RFC
2021-07-06T08:06:13
2021-07-06T15:41:58
{}
MEMBER
vuejs
core
875,394,278
4,050
jods4
@yyx990803 03e2684 is not a complete, proper fix. I noticed: 1. You can't restore context in case of failure inside a `.catch()`. That's like restoring context in case of succes inside `.then()`. The continuation of `.catch()` runs in a micro-task so anything could run inbetween. Restoring the context has to h...
2021-07-07T08:17:32
2021-07-07T08:17:32
{}
CONTRIBUTOR
vuejs
core
872,563,902
4,033
yyx990803
That's expected - deep watches are by definition expensive because it traverses the entire data structure and collect every single property as dependencies for that watcher. There's not much we can do here - since there is no magic deep watch natively in JS. Even with the pending improvements in 3.2, I don't think y...
2021-07-01T21:31:23
2021-07-01T21:31:23
{}
MEMBER
vuejs
core
873,656,930
4,060
posva
It does with a reactive object but `$attrs` is not a reactive object (https://v3.vuejs.org/guide/composition-api-setup.html#context). Maybe something to add for compat build if possible
2021-07-04T20:31:03
2021-07-04T20:31:03
{ "+1": 1 }
MEMBER
vuejs
core
874,893,004
4,050
yyx990803
Thanks for the research into this @jods4 - I think it's ok for the API to be a bit unwieldy as long as it is easy to automatically generate. It isn't that much a burden for userland composition functions to ensure proper placement of `await` - in fact I'd say it's good to discourage `await` in composition functions ...
2021-07-06T16:09:37
2021-07-06T16:09:37
{ "+1": 1 }
MEMBER
vuejs
core
872,847,955
4,052
BoBo-Git
> Caused by a TypeScript version bump. > We should never set the target to `esnext` again. > > Workaround: > > ```js > // vue.config.js > module.exports = { > transpileDependencies: ['@vue/reactivity'] > } > ``` It works, and no need to lock Vue version to 3.1.2.
2021-07-02T09:12:56
2021-07-02T09:12:56
{}
NONE
vuejs
core
874,544,951
4,070
posva
Duplicate of #4062
2021-07-06T07:55:49
2021-07-06T07:55:49
{}
MEMBER
vuejs
core
874,833,477
4,071
DV8FromTheWorld
As a note, this was originally noticed in `focus-trap-vue` after it started using `expose({ ... })` to expose some methods since it was returning a render function from the `setup` function. The workaround to handle this (at least for now while the userbase is migrating) involves exposing a `renderImpl` function pub...
2021-07-06T14:56:02
2021-07-06T14:56:41
{}
CONTRIBUTOR
vuejs
core
875,131,807
4,065
andrewcourtice
@yyx990803 That's great news! It looks like Jason Miller has got a few tricks up his sleeve for improving the performance in Preact: https://twitter.com/_developit/status/1412451442946981890?s=20 Could Vue also benefit from any of the concepts Jason is referring to (linked lists, stack machine etc) or does Vue al...
2021-07-06T22:46:39
2021-07-06T22:46:39
{}
NONE
vuejs
core
872,159,850
4,034
Trinovantes
I'm currently working around this by manually checking `IS_SSR || document.querySelector('#id').hasChildNodes() ? createSSRApp(App) : createApp(App)` This is pretty messy and couples the root app creation step with the DOM. AFAIK, there's no way to disable hydration in the DOM in Vue 3 since `createSSRApp` alway...
2021-07-01T11:22:53
2021-07-01T11:22:53
{ "+1": 1 }
NONE
vuejs
core
872,595,099
3,998
inspire22
Brilliant, thanks so much to everyone for their help!
2021-07-01T22:48:31
2021-07-01T22:48:31
{}
NONE
vuejs
core
872,857,711
4,050
jods4
My fault. The design I proposed for `withAsyncContext` is flawed. The problem is that `withAsyncContext` itself returns a promise. It is awaited. Continuation code doesn't run synchronously after it. What happens in this bug report is: - Comp 1 runs before - Comp 1 saves its context and awaits 7 - Comp 2 run...
2021-07-02T09:27:44
2021-07-02T09:27:44
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
872,939,330
4,007
yyx990803
See 34d4991d - unfortunately this PR doesn't cover other cases in which `v-model` input elements can also have non-string bindings: `:value`, `:true-avlue` and `:false-value`.
2021-07-02T11:50:35
2021-07-02T11:50:35
{}
MEMBER
vuejs
core
873,392,092
4,057
LinusBorg
typing setup's argument doesn't type the external Prop interface of the component. ```js import { defineComponent, PropType } from 'vue'; export default defineComponent({ props: { icon: String // as PropType<'home' | 'user' | 'edit'> }, setup(props) { return () => ( <div> <butt...
2021-07-03T11:19:11
2021-07-03T11:42:29
{}
MEMBER
vuejs
core
874,555,198
4,069
posva
The rule of thumb is: if the element is consumed by an external library, let the external library **completely** handle it, so no elements inside of it that are handled by Vue. Otherwise, Vue will try to manipulate assuming it's the only one doing so to be able to apply the correct updates.
2021-07-06T08:11:44
2021-07-06T08:11:44
{}
MEMBER
vuejs
core
875,172,733
4,017
yyx990803
I'll try to review and merge this one after we resolve #2195 so hopefully this should be the last time 😅
2021-07-07T00:27:03
2021-07-07T00:27:03
{}
MEMBER
vuejs
core
872,672,613
2,775
Liangzhihe
> 1. use `defineComponent()` to let TS know you are actually defining a Vue component > 2. try annotating the return values of the computed's: > > ```ts > showMachines(): boolean { > ``` > > For more help, please use chat.vuejs.org thank you very much!
2021-07-02T02:47:03
2021-07-02T02:47:03
{}
NONE
vuejs
core
872,753,058
4,052
mdunisch
same problem here, works fine with vue@3.1.2 @vue/compiler-sfc@3.1.2 but breaks with vue@3.1.3 @vue/compiler-sfc@3.1.3
2021-07-02T06:30:20
2021-07-02T06:30:20
{}
NONE
vuejs
core
872,762,919
4,052
scuiadmin
!same problem
2021-07-02T06:50:20
2021-07-02T06:50:20
{}
NONE
vuejs
core
872,836,841
4,052
LonHon
Resolved by locking Vue version to 3.1.2
2021-07-02T08:56:37
2021-07-02T08:57:05
{ "+1": 1, "heart": 2 }
NONE
vuejs
core
873,056,212
4,055
DV8FromTheWorld
As a note, we may want to consider introducing something like `ExposeInstanceProxyHandlers` and turn the contents of `PublicInstanceProxyHandlers` into an HOF and make `PublicInstanceProxyHandlers` use that. The thought here would be something like: ```js const buildInstanceProxyHandlers = (restrictInstanceInfo)...
2021-07-02T14:49:59
2021-07-02T14:49:59
{}
CONTRIBUTOR
vuejs
core
874,393,401
4,068
danelowe
Just realised I'm not entirely sure if this would be in `sfc-compiler` or `vite` or both.
2021-07-06T01:16:10
2021-07-06T01:16:10
{}
NONE
vuejs
core
874,823,831
4,071
yyx990803
I would suggest *not* using expose (which isn't even a merged RFC yet) before you migrate to Vue Router 4.x. This is unfortuanately a wontfix.
2021-07-06T14:44:22
2021-07-06T14:44:43
{}
MEMBER
vuejs
core
874,846,541
2,136
andredewaard
@yuxino How did you solve this problem? i have the same thing ```typescript export const usePagination = <T>({ url }: { url: string }) => { const client = API const index = ref<T[]>([]) const get = async (): Promise<IndexResponse<T>> => { const { data } = await client.get<IndexResponse<T>>(`${ur...
2021-07-06T15:11:36
2021-07-06T15:14:31
{}
NONE
vuejs
core
874,876,082
4,073
masx200
https://github.com/vuejs/vue-next/issues/3857 https://github.com/vuejs/vue-next/issues/3548
2021-07-06T15:48:46
2021-07-06T15:48:46
{}
NONE
vuejs
core
872,439,090
4,046
dependabot[bot]
OK, I won't notify you about codemirror again, unless you re-open this PR or update it yourself. 😢
2021-07-01T17:52:36
2021-07-01T17:52:36
{}
CONTRIBUTOR
vuejs
core
873,360,166
2,195
antfu
@0x009922 please go to the RFC for design discussions. For the return forwarding, here are the original discussions https://github.com/vuejs/rfcs/pull/212#issuecomment-696459422
2021-07-03T07:09:11
2021-07-03T07:09:29
{ "+1": 2 }
MEMBER
vuejs
core
874,544,391
4,070
posva
Probably fixed already as it works in [the playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IGlkPVwiYXBwXCI+XG4gICAgPGgxPnt7bWVzc2FnZX19PC9oMT5cblxuICAgIDxwPlxuICAgICAgTGVhcm4gbW9yZSB3aXRoIHRoZVxuICAgICAgPGFcbiAgICAgICAgaHJlZj1cImh0dHBzOi8vdnVlanMub3JnL1wiXG4gICAgICAgIHRhcmdldD1cIl9ibGFua1wiXG...
2021-07-06T07:54:59
2021-07-06T07:54:59
{}
MEMBER
vuejs
core
872,441,567
3,971
yyx990803
Thanks for the PR - this is addressed in #4019 which also bumps puppeteer.
2021-07-01T17:57:04
2021-07-01T17:57:04
{}
MEMBER
vuejs
core
872,607,735
4,031
yyx990803
fixed via ba89ca9
2021-07-01T23:20:30
2021-07-01T23:20:30
{ "+1": 1 }
MEMBER
vuejs
core
872,935,563
4,051
yyx990803
Is this a regression?
2021-07-02T11:43:07
2021-07-02T11:43:07
{}
MEMBER
vuejs
core
873,574,373
4,059
LinusBorg
That's an internal API that you should not touch. Why would you even do that? just render the vnodes directly. You can i.e. use `<component :is="vnodes here">`
2021-07-04T11:55:01
2021-07-04T11:55:01
{}
MEMBER
vuejs
core
874,317,733
2,195
yyx990803
Just rebased on 3.2 and split effectScope specific logic into a separate file. I may do some more fine-tuning for memory and bundle size optimizatons.
2021-07-05T20:33:21
2021-07-05T20:33:21
{}
MEMBER
vuejs
core
874,809,870
4,072
edison1105
duplicate of #3993
2021-07-06T14:27:51
2021-07-06T14:27:51
{}
MEMBER
vuejs
core
872,438,085
4,039
yyx990803
@dependabot ignore this dependency
2021-07-01T17:50:48
2021-07-01T17:50:48
{}
MEMBER
vuejs
core
872,438,106
4,039
dependabot[bot]
OK, I won't notify you about todomvc-app-css again, unless you re-open this PR or update it yourself. 😢
2021-07-01T17:50:50
2021-07-01T17:50:50
{}
CONTRIBUTOR
vuejs
core
872,765,929
3,930
qmhc
@yyx990803 我发现这个问题似乎是和 link 协议有关,并不是 vue 本身的问题,在 serve 模式下 esbuild 可以准确追踪到 link 协议的文件夹,但是在 build 模式下 rollup 似乎没办法追踪 link 协议关联的包。然而我不确定这个问题是出在 vite 或是 rollup 上面,所以我仅报告这个问题。如果你觉得这个问题可能与 vite 有关,你可以考虑是否要迁移这个 issue。
2021-07-02T06:56:06
2021-07-02T06:57:56
{}
NONE
vuejs
core
872,977,608
4,050
jods4
While working on the new proposal I noticed another bug. If you use the current `withAsyncContext` in an asynchronous composable function, e.g.: ```js async function useRemoteSum() { const data = await withAsyncContext(fetch("/data")); return computed(() => data.reduce((a, b) => a + b, 0)); } ``` Then t...
2021-07-02T12:57:49
2021-07-02T12:57:49
{}
CONTRIBUTOR
vuejs
core
872,171,969
4,033
FabianSchwartau
Thanks for the suggestion, but I need a watch on that complete large structure. It's for an undo/redo feature and this struct holds my complete state. Can you tell what Vue is actually doing in the background in that case?
2021-07-01T11:39:05
2021-07-01T11:39:05
{}
NONE
vuejs
core
872,947,449
4,002
0x1af2aec8f957
This is a very difficult problem, and I have encountered it.
2021-07-02T12:05:52
2021-07-02T12:05:52
{}
NONE
vuejs
core
873,075,908
4,051
07akioni
> Is this a regression? Yes. 3.0.10 works without error.
2021-07-02T15:18:35
2021-07-02T15:19:20
{}
CONTRIBUTOR