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 | 870,914,955 | 1,359 | jods4 | I would like to contribute a sample use case that I encountered today.
I was rendering a list of heterogeneous items.
Let's say your list has `Link` and `Group` in there (e.g. a navigation menu). You want to render them differently and when you click them different stuff happens.
```html
<template v-for="i of ... | 2021-06-29T21:02:48 | 2021-06-29T21:03:52 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 871,404,951 | 4,027 | sqal | ```js
function useOptions() {
const options = computed(() => [])
return { options }
}
export default {
props: { options: Array },
setup() {
const { options } = useOptions()
return {
options
}
}
}
export default {
props: { options: Array },
setup() {
return {
... | 2021-06-30T13:28:26 | 2021-06-30T13:33:18 | {} | CONTRIBUTOR |
vuejs | core | 871,541,658 | 4,028 | posva | Can you open an issue on the vuejs/docs repo please? | 2021-06-30T16:16:58 | 2021-06-30T16:16:58 | {} | MEMBER |
vuejs | core | 871,671,176 | 3,998 | liamdebeasi | Thanks! I added the webpack config and changed the click handler to `v-on:click.native` and now the click events are working as expected. I think I got confused by the `The migration build runs in Vue 2 mode by default` line in the docs and thought that the webpack part was not necessary unless you needed to customize ... | 2021-06-30T19:30:41 | 2021-06-30T19:39:20 | {} | NONE |
vuejs | core | 872,020,360 | 2,389 | basvanmeurs | Let's close this PR because of the following reasons:
* computeds can be stopped by wrapping it in an effectScope (https://github.com/vuejs/vue-next/pull/2195), and stopping that
* for convenience and to avoid having to create effectScopes, we could add a `stop` method to the computed class which simply invokes `this... | 2021-07-01T08:03:47 | 2021-07-01T08:03:47 | {} | CONTRIBUTOR |
vuejs | core | 869,151,794 | 4,008 | kooriookami | > duplicate of #3953
@edison1105 Sorry, I didn't want to mention `undefined attrs are not being passed`, so I changed the description. I give all type.props a default value.
How can the props convert to camel case automatically? Like `a-b-c` to `aBC`. And is there any way to merge type.props to props? | 2021-06-27T12:12:22 | 2021-06-27T13:10:57 | {} | NONE |
vuejs | core | 871,349,751 | 4,027 | userquin | ```ts
// Options.vue
setup(props) {
const { options } = useOptions(props)
return {
// passed directly works!!!!!
// options: o.options,
options,
}
}
```
or just return `options` instead `{ options }` on `useOptions`. | 2021-06-30T12:12:24 | 2021-06-30T12:13:44 | {} | MEMBER |
vuejs | core | 871,396,799 | 4,027 | sqal | @posva I am still kind of confused by this behavior. You're saying _"Make sure to name it differently."_ but **it works** when I return computed named `options` directly in the setup. Shouldn't the component then render `oprions` from props (```["foo"]```) and not my computed property?
> It works with the script ... | 2021-06-30T13:17:52 | 2021-06-30T13:17:52 | {} | CONTRIBUTOR |
vuejs | core | 871,683,525 | 3,998 | inspire22 | @liamdebeasi I've made the .native updates to my ionic-based repo and click is still not fired - could this be related to the changed defineComponent vs what vue/ionic does? https://github.com/inspire22/ionic-click-bug
I'd been confused in thinking that .native wasn't supported because the included .eslint.rc had "... | 2021-06-30T19:52:09 | 2021-06-30T19:52:09 | {} | NONE |
vuejs | core | 872,126,850 | 3,910 | posva | @JoeriTheGreat It seems to be working with the given example on this issue. Maybe it's a compat bug but I'm unsure if the compiler does a different work on compat mode | 2021-07-01T10:38:04 | 2021-07-01T10:38:04 | {} | MEMBER |
vuejs | core | 872,147,492 | 4,034 | posva | You can find multiple workarounds like having one index.html that isn't ssr rendered to avoid doing the hydration. After all, you are purposely hydrating the page with the wrong content | 2021-07-01T11:07:48 | 2021-07-01T11:07:48 | {} | MEMBER |
vuejs | core | 867,787,575 | 3,998 | posva | The syntax you are using for the functional component seems off. It should be:
```js
import { defineComponent, h } from 'vue';
const defineContainer = (name) => {
const Container = ((props, { slots }) => {
return h(name, props, slots.default && slots.default());
});
Container.displayName = name... | 2021-06-24T16:35:00 | 2021-06-24T16:35:00 | {} | MEMBER |
vuejs | core | 868,121,740 | 2,513 | alexbeae | This issue is a nightmare for big projects. Adding events manually doesn't work for elements with v-if conditions. I hope this bug will be fixed soon. | 2021-06-25T01:32:02 | 2021-06-25T01:32:02 | {
"+1": 7
} | NONE |
vuejs | core | 869,504,692 | 4,010 | posva | I would say having a function gives you the flexibility of ordering the nodes however you want but I'm not sure if this was intended | 2021-06-28T08:58:14 | 2021-06-28T08:58:14 | {} | MEMBER |
vuejs | core | 869,568,875 | 4,013 | beastrovich | I'm trying, but honestly there is no reproduction code, because the missing thing is obvious just by looking at the source code.
I literally just added a single line into "\node_modules\@vue\runtime-core\dist\runtime-core.esm-bundler.js" and it fixed the problem.
Like this:
```
const ErrorTypeStrings = {
["s... | 2021-06-28T10:28:14 | 2021-06-28T10:29:12 | {} | CONTRIBUTOR |
vuejs | core | 871,368,150 | 4,027 | sqal | I know that now but why does it matter if I return a property `XYZ` directly or if I spread an object with a property `XYZ`? should it work the same in both cases? Shouldn't the setup context be taken into account first when accessing properties in the template? and why it currently works differently in the reproductio... | 2021-06-30T12:41:05 | 2021-06-30T12:41:05 | {} | CONTRIBUTOR |
vuejs | core | 871,698,843 | 3,998 | LinusBorg | @inspire22 The compiler config is not the solution in terms of Ionic.
Ionic exports Vue 3 components. But in compat mode, the app would treat them like Vue 2 components by default. You can do the following:
```js
import {IonContent, IonHeader, IonPage, IonTitle, IonToolbar, IonButton} from "@ionic/vue";
import ... | 2021-06-30T20:16:18 | 2021-06-30T20:19:33 | {
"+1": 1
} | MEMBER |
vuejs | core | 872,154,525 | 4,035 | 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).
---
This is too much for a reproduction (it shouldn'... | 2021-07-01T11:16:25 | 2021-07-01T11:16:25 | {} | MEMBER |
vuejs | core | 867,778,241 | 4,000 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/3392 | 2021-06-24T16:25:50 | 2021-06-24T16:25:50 | {} | MEMBER |
vuejs | core | 868,490,551 | 4,004 | posva | Vue still needs to parse it to create the [JS function that renders the VDOM](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICAgICAgPGgxPkxvbmcgTGlzdDwvaDE+XG4gICAgPHVsIHYtb25jZT5cbiAgICAgIDxsaT57eyBtZXNzYWdlIH19PC9saT5cbiAgICAgIDxsaT48L2xpPlxuICAgICAgPGxpPjwvbGk+XG4gICAgICA8bGk+PC9saT5cbiAgICAgIDxsaT48L2xpPlx... | 2021-06-25T13:13:24 | 2021-06-25T13:13:24 | {} | MEMBER |
vuejs | core | 869,520,741 | 3,414 | hezhongfeng | I don’t like Vue’s KeepAlive cache policy , So I want to create a component like KeepAlive.
But When I use my Component with transition，there is a error Uncaught TypeError: Cannot read property '_' of null.
This error is create by packages/runtime-core/src/componentSlots.ts initSlots.
Looking forward to this PR.
| 2021-06-28T09:18:44 | 2021-06-28T09:18:44 | {} | NONE |
vuejs | core | 871,540,467 | 4,029 | posva | This breaking change should be documented at https://v3.vuejs.org/guide/migration/custom-directives.html#overview. Could you check if there isn't an open issue already and open one on the vuejs/docs repo | 2021-06-30T16:15:16 | 2021-06-30T16:16:11 | {} | MEMBER |
vuejs | core | 871,679,423 | 3,998 | LinusBorg | in step 3 of the Installation instructions it explicitly states:
> In the build setup, alias vue to @vue/compat and enable compat mode via Vue compiler options.
Should that be changed to be clearer? Or should the introduction further up which threw you off be changed? If so, do you have something in mind? The fol... | 2021-06-30T19:45:10 | 2021-06-30T19:45:10 | {} | MEMBER |
vuejs | core | 872,001,528 | 2,195 | basvanmeurs | @antfu I'd like to use this PR to solve memory leaks in my project. Could you give me write permissions on this branch so that I can resolve the conflicts for 3.2?
I would like to run some performance tests as well. One thing is that I'd prefer to use the class-based approach in line with the class-based ReactiveEff... | 2021-07-01T07:34:29 | 2021-07-01T09:11:02 | {} | CONTRIBUTOR |
vuejs | core | 868,159,467 | 3,594 | casWangyy | > @edison1105
>
> It may cause by element-plus. I'm not sure.
>
> 
i have the problem too | 2021-06-25T02:44:41 | 2021-06-25T02:44:41 | {} | NONE |
vuejs | core | 869,109,893 | 3,921 | huangxiaochang | > The root cause is:
> `loaderContext.mode` is `undefined `in the reproduction project.
> https://github.com/vuejs/vue-loader/blob/next/src/resolveScript.ts#L35
>
> And
> https://github.com/vuejs/vue-loader/blob/next/src/stylePostLoader.ts#L17
> `this.mode` is `production`
>
> so the generated name of `cssVar... | 2021-06-27T06:23:34 | 2021-06-27T06:23:34 | {} | NONE |
vuejs | core | 869,570,675 | 4,013 | beastrovich | Just take a look please, I swear I'm not just wasting your time.
Thank you! | 2021-06-28T10:31:22 | 2021-06-28T10:31:22 | {} | CONTRIBUTOR |
vuejs | core | 871,300,315 | 4,024 | posva | There was https://github.com/vuejs/vue-next/issues/2325 but it was only referring to `v-model`. There is still an open PR: https://github.com/vuejs/vue-next/pull/2353
[Here is a workaround](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aW5wdXQgdHlwZT1cInJhbmdlXCIgOnZhbHVlPVwibnVtYmVyXCIgbWluPVwiMFwiIG... | 2021-06-30T10:55:21 | 2021-06-30T10:55:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 871,311,852 | 4,025 | 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-06-30T11:12:40 | 2021-06-30T11:12:40 | {} | CONTRIBUTOR |
vuejs | core | 871,312,870 | 4,025 | LeonVlad | [LeoVue3Error.txt](https://github.com/vuejs/vue-next/files/6740376/LeoVue3Error.txt)
| 2021-06-30T11:14:16 | 2021-06-30T11:14:16 | {} | NONE |
vuejs | core | 871,326,586 | 4,026 | LeonVlad | Thanks | 2021-06-30T11:35:46 | 2021-06-30T11:35:46 | {} | NONE |
vuejs | core | 871,329,899 | 4,026 | posva | Read and follow https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro | 2021-06-30T11:41:33 | 2021-06-30T11:41:33 | {} | MEMBER |
vuejs | core | 871,708,806 | 4,019 | leopiccionia | It partially overlaps with #3971. | 2021-06-30T20:33:28 | 2021-06-30T20:33:28 | {} | CONTRIBUTOR |
vuejs | core | 868,508,847 | 4,004 | jan-vodila | Thanks for the reply and provided solution.
However, the problem is when the static content is coming from CMS therefore it is dynamic. Then you cannot pre-compile it, unless you are using Headless CMS and consuming the content via SSR. For that you would need completely different architecture.
Currently the weig... | 2021-06-25T13:42:10 | 2021-06-25T13:42:10 | {} | NONE |
vuejs | core | 871,166,695 | 4,021 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4022 | 2021-06-30T07:33:00 | 2021-06-30T07:33:00 | {} | MEMBER |
vuejs | core | 871,172,801 | 4,022 | posva | Closing in favor of https://github.com/vuejs/vue-next/issues/4023 without vue-router | 2021-06-30T07:43:38 | 2021-06-30T07:43:38 | {} | MEMBER |
vuejs | core | 871,684,543 | 3,998 | liamdebeasi | Let's move the conversation back to the Ionic Framework repo and we can continue to discuss there. | 2021-06-30T19:53:51 | 2021-06-30T19:53:51 | {} | NONE |
vuejs | core | 871,689,266 | 3,998 | LinusBorg | @inspire22 Your repro is also missing the compiler config here:
https://github.com/inspire22/ionic-click-bug/blob/ee441b9083a54d3e43a904213f8494c39f5f7121/myApp/vue.config.js#L16 | 2021-06-30T20:01:26 | 2021-06-30T20:01:26 | {} | MEMBER |
vuejs | core | 872,096,722 | 4,032 | NorthSeacoder | > https://v3.vuejs.org/guide/reactivity-computed-watchers.html#watching-reactive-objects
>
> 
thanks | 2021-07-01T09:47:07 | 2021-07-01T09:47:07 | {} | NONE |
vuejs | core | 884,776,158 | 4,173 | 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-22T09:28:55 | 2021-07-22T09:28:55 | {} | MEMBER |
vuejs | core | 884,989,013 | 4,171 | mgibas | @yyx990803 You mentioned SFC - is there any other way to get `defineCustomElement` works with styles in Shadow DOM, even without SFC ? | 2021-07-22T15:07:36 | 2021-07-22T15:07:36 | {} | NONE |
vuejs | core | 885,034,626 | 3,183 | jods4 | @yyx990803 it's fantastic you could fix that!
On top of what was already said above, it really messed up with VS Code auto-complete.
When you try to auto-import a type, VS Code always adds it to an existing plain `import` and you must go back and manually split things in two imports. | 2021-07-22T16:08:27 | 2021-07-22T16:08:27 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 887,425,577 | 2,077 | yuanjinyong | I used the following code, it seems ok:
```
<router-view v-slot="{Component, route}">
<keep-alive ref="keepAlive"><component :key="route.path" :is="Component" /></keep-alive>
</router-view>
```
```
onCloseTab(targetName) {
const route = this.tabRoutes.find(route => targetName ===... | 2021-07-27T11:14:48 | 2021-07-27T11:22:29 | {
"+1": 2,
"-1": 6
} | NONE |
vuejs | core | 887,443,052 | 4,198 | edison1105 | duplicate of #4183, the `dynamicChildren` is an empty array and will be fixed in #4186 (if it's the right fix😄) | 2021-07-27T11:44:33 | 2021-07-27T14:51:12 | {
"+1": 1
} | MEMBER |
vuejs | core | 888,127,830 | 4,207 | LinusBorg | No, that's not how events work.
Please use our discord (chat.vuejs.org) to ask for help | 2021-07-28T08:41:39 | 2021-07-28T08:41:39 | {} | MEMBER |
vuejs | core | 888,277,887 | 4,208 | posva | having `value=""` rendered with `:value="null"` was a bug. You can still pass `value=""` yourself and initialize the `selected` to `""` [Example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuPGZvcm0gaWQ9XCJ2LW1vZGVsLXNlbGVjdC1keW5hbWljXCI+XG4gIDxzZWxlY3Qgdi1tb2RlbD1cInNlbGVjdGVkXCI+XG4gICAgPG9wdGlvbiB2YWx1ZT1... | 2021-07-28T12:43:49 | 2021-07-28T12:43:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 888,799,696 | 4,184 | basvanmeurs | Thanks @yyx990803 , I can see how your commit is more robust. The fix does indeed dereference correctly. But alas it doesn't work in our case due to performance issues..
> stopping a nested scope should be a relatively low-frequency operation?
This feature might be used more intensively than you think.
Our us... | 2021-07-29T04:50:47 | 2021-07-29T07:56:44 | {} | CONTRIBUTOR |
vuejs | core | 889,230,225 | 4,209 | yyx990803 | Oh I see the original issue is about duplicated Vue runtime so I guess leaving `@vue/compiler-ssr` as-is should be fine. | 2021-07-29T15:13:15 | 2021-07-29T15:13:15 | {
"+1": 1
} | MEMBER |
vuejs | core | 889,906,281 | 4,214 | posva | > Please don't make me fill everything again... you could have kept the issue open just a day and given me a chance to append the repro here.
Then don't open an issue without a repro. Pinging me with a repro is fine, I still take a look 😉 . Using `vDir` is a workaround | 2021-07-30T13:50:10 | 2021-07-30T13:50:10 | {} | MEMBER |
vuejs | core | 884,489,841 | 4,161 | yyx990803 | This is a bug specific to `useAttrs`. For now you can simply bind to `$attrs` directly in the template.
It's also not teleport or transition related. Any component that renders default slot can lead to this behavior. | 2021-07-21T20:49:23 | 2021-07-21T20:50:49 | {} | MEMBER |
vuejs | core | 885,413,281 | 4,179 | edison1105 | your reproduction link is broken.
is this what you looking for.
https://v3.vuejs.org/guide/migration/global-api.html#share-configurations-among-apps | 2021-07-23T05:42:06 | 2021-07-23T07:10:54 | {} | MEMBER |
vuejs | core | 886,028,783 | 4,187 | wellfrog16 | > as a workaround:
> use arrow function instead.
>
> ```js
> props: {
> id: {
> type: String,
> default: ()=>'any',
> },
> },
> ```
太棒了，可以正常工作了。原来的写法我是从官方文档中看到的。
[https://www.vue3js.cn/docs/zh/guide/component-props.html#prop-%E9%AA%8C%E8%AF%81](url)
最好可以... | 2021-07-24T09:48:48 | 2021-07-24T09:49:15 | {} | NONE |
vuejs | core | 886,543,110 | 4,193 | basvanmeurs | Closing, as this is not a Weak-only issue, but also counts for other reactive Maps or Sets when keys are set to object references. | 2021-07-26T09:37:28 | 2021-07-26T09:37:28 | {} | CONTRIBUTOR |
vuejs | core | 887,361,917 | 4,196 | edison1105 | if unwrap the injected properties in the template, this may be a breaking change. | 2021-07-27T09:32:26 | 2021-07-27T09:32:26 | {} | MEMBER |
vuejs | core | 887,973,328 | 4,204 | cheng990629 | > your repro link is broken.
[https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2PlxuICAgIDxzcGFuIHYtdGV4dD1cInZhbFwiPjwvc3Bhbj5cbiAgICA8YnV0dG9uIEBjbGljaz1cInZhbD0nNTY3J1wiPua1i+ivlTwvYnV0dG9uPlxuXG4gICAgPGRpdiA6a2V5PVwiaXRlbS5pZFwiIHYtZm9yPVwiaXRlbSBpbiBhcnJcIj5cblxuICAgICAgPCEtLSAgIGFibm9ybWFsICAgLS0+... | 2021-07-28T03:06:05 | 2021-07-28T03:06:05 | {} | NONE |
vuejs | core | 887,986,790 | 4,204 | edison1105 | I update the [repro](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2PlxuICAgIDxzcGFuIHYtdGV4dD1cInZhbFwiPjwvc3Bhbj5cbiAgICA8YnV0dG9uIEBjbGljaz1cInZhbCs9MVwiPmNoYW5nZTwvYnV0dG9uPlxuXG4gICAgPGRpdiB2LWZvcj1cIml0ZW0gaW4gYXJyXCIgOmtleT1cIml0ZW0uaWRcIj5cbiAgICAgIDwhLS0gICBhYm5vcm1hbCAgIC0tPlxuICAgICAgPGNvbXBv... | 2021-07-28T03:46:58 | 2021-07-28T03:46:58 | {
"heart": 1
} | MEMBER |
vuejs | core | 887,262,692 | 4,121 | jaulz | @yyx990803 thanks for your response! In order to reproduce it you can clone https://github.com/jaulz/vue-repro and run it via `yarn serve`. Just click any of the options at the top. | 2021-07-27T06:59:44 | 2021-07-27T06:59:44 | {} | CONTRIBUTOR |
vuejs | core | 887,340,025 | 4,121 | posva | @jaulz Your reproduction is way too large, can you boil it down to only Vue and no external libs so we can take a look? (https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro) | 2021-07-27T09:01:46 | 2021-07-27T09:01:46 | {} | MEMBER |
vuejs | core | 887,430,577 | 593 | yuanjinyong | In Vue3, I tried the following code, and it can unmount an component (not the whole app):
```
<router-view v-slot="{Component, route}">
<keep-alive ref="keepAlive"><component :key="route.path" :is="Component" /></keep-alive>
</router-view>
```
```
onCloseTab(targetName) {
const r... | 2021-07-27T11:22:46 | 2021-07-27T11:22:46 | {} | NONE |
vuejs | core | 887,860,658 | 4,196 | yyx990803 | I agree unwrapping should be the desired behavior for consistency, but indeed this would technically be a breaking change.
I think the middle ground is raising a warning for now and require explicitly opting into the fixed behavior. Then in the next minor we will default to the fixed behavior. | 2021-07-27T21:56:25 | 2021-07-27T21:56:25 | {} | MEMBER |
vuejs | core | 884,703,423 | 4,171 | DrMabuse23 | I tried also some rules in the vue.config.js but it doesnt fixed the problem
```javascript
config.module
.rule('scss')
.oneOf('vue')
.use('vue-style-loader')
.loader('vue-style-loader')
.tap((options) => {
options.shadowMode = true;
return options;
});
... | 2021-07-22T07:15:30 | 2021-07-22T07:22:14 | {} | NONE |
vuejs | core | 885,533,932 | 4,179 | edison1105 | @flicat <s>为啥呢，我没测试，按照尤大的评论，应该是可以解决的啊。</s>
I did a demo see [playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8bXlDb20+PC9teUNvbT48IS0t6IO95q2j5bi45pi+56S6LS0+XG48L3RlbXBsYXRlPlxuXG48c2NyaXB0PlxuaW1wb3J0IHsgZ2V0Q3VycmVudEluc3RhbmNlIH0gZnJvbSAndnVlJ1xuaW1wb3J0IG15X3BsdWdpbiBmcm9tICcuL215X3BsdWdpb... | 2021-07-23T10:04:34 | 2021-07-23T11:31:46 | {} | MEMBER |
vuejs | core | 885,628,027 | 4,180 | LinusBorg | The link is broken | 2021-07-23T13:11:23 | 2021-07-23T13:11:23 | {
"+1": 1
} | MEMBER |
vuejs | core | 886,133,451 | 4,181 | xaboy | 谢谢, 我试试看能不能通过 demo 复现出来 @edison1105 | 2021-07-25T01:33:11 | 2021-07-25T01:33:11 | {} | NONE |
vuejs | core | 887,964,400 | 4,204 | edison1105 | your repro link is broken. | 2021-07-28T02:37:48 | 2021-07-28T02:37:48 | {} | MEMBER |
vuejs | core | 888,387,895 | 4,205 | yyx990803 | There are edge cases where this can lead to incorrect behavior:
- If the item has been replaced but has the same key
- If the `v-model` is bound on a destructured object which has been replaced
So the de-optimization is necessary to ensure correctness. | 2021-07-28T15:07:16 | 2021-07-28T15:07:16 | {
"+1": 1
} | MEMBER |
vuejs | core | 888,389,826 | 4,195 | yyx990803 | optional chaining is intentionally prohibited in the codebase because it needs to be transpiled for Vue's support baseline (ES2015) and generates unnecessarily verbose code. | 2021-07-28T15:09:40 | 2021-07-28T15:09:40 | {} | MEMBER |
vuejs | core | 889,231,799 | 4,209 | Igloczek | From what I tested locally, it works with just this one in ESM, since the `ssrUtils` was the main problem, so unless there is some singleton-wannabe stuff in `@vue/compiler-ssr`, we should be fine. | 2021-07-29T15:15:24 | 2021-07-29T15:15:24 | {} | CONTRIBUTOR |
vuejs | core | 885,288,732 | 4,171 | DrMabuse23 | What tooling updates are needed? Can you please explain? or sending a link please | 2021-07-22T22:59:29 | 2021-07-22T22:59:29 | {} | NONE |
vuejs | core | 885,885,705 | 4,165 | yyx990803 | Checking presence of `effect` should be safe - normal refs would never have an effect attached to it. | 2021-07-23T20:04:56 | 2021-07-23T20:04:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 886,026,209 | 4,187 | edison1105 | as a workaround:
use arrow function instead.
```javascript
props: {
id: {
type: String,
default: ()=>'any',
},
},
``` | 2021-07-24T09:23:14 | 2021-07-24T09:23:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 886,030,539 | 4,187 | posva | That's not a valid repro. Use the chat or forum for questions | 2021-07-24T10:05:00 | 2021-07-24T10:05:00 | {} | MEMBER |
vuejs | core | 887,955,772 | 4,203 | tgly307 | > 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
so that's... | 2021-07-28T02:12:49 | 2021-07-28T02:12:49 | {} | NONE |
vuejs | core | 884,559,677 | 4,161 | andrewcourtice | @yyx990803 Thanks for sorting those out so quickly! That's great!
I have a few lingering questions regarding this though.
To give you a bit of context, the reason this has become an issue for me is because I have a composition that splits the `attrs` object in a higher-order component with `inheritAttrs: false` s... | 2021-07-21T23:22:24 | 2021-07-21T23:24:29 | {} | NONE |
vuejs | core | 884,724,869 | 4,172 | LinusBorg | You need to provide a runnable reproduction | 2021-07-22T07:59:42 | 2021-07-22T07:59:42 | {} | MEMBER |
vuejs | core | 885,352,494 | 4,176 | Otto-J | What does it mean: "p1-chrone" ? | 2021-07-23T02:10:56 | 2021-07-23T02:10:56 | {} | NONE |
vuejs | core | 885,575,450 | 4,181 | edison1105 | @xaboy 如果你可以提供一个可以复现的demo，我愿意帮你看看。 | 2021-07-23T11:28:38 | 2021-07-23T11:28:38 | {} | MEMBER |
vuejs | core | 886,612,907 | 4,189 | posva | I would also say a watcher is more adapted for validation. In any case, this needs to go through an RFC. If you still think this is worth pursuing, follw the RFC proccess in the rfcs repo | 2021-07-26T11:19:00 | 2021-07-26T11:19:00 | {} | MEMBER |
vuejs | core | 888,432,593 | 4,184 | yyx990803 | Wondering if the removal optimization is necessary, considering stopping a nested scope should be a relatively low-frequency operation?
I implemented a simpler fix in 1867591e - essentially the removal is only necessary on manual `stop()` calls. Can you confirm that fixes the memory leak issue for you? | 2021-07-28T16:05:35 | 2021-07-28T16:09:40 | {} | MEMBER |
vuejs | core | 889,228,198 | 4,209 | yyx990803 | Hmm, I realized this alone probably isn't enough since `@vue/server-renderer` depends on `@vue/compiler-ssr` which is currently cjs-only. | 2021-07-29T15:10:45 | 2021-07-29T15:10:45 | {} | MEMBER |
vuejs | core | 889,692,116 | 4,212 | posva | It's `toRaw(aRef.value)` or `toRaw(unref(aRef.value))`. | 2021-07-30T07:29:48 | 2021-07-30T07:29:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 884,772,972 | 4,173 | rashagu | ` v-model={[tabsActive.value, "active"]} `
is work, but only ` active` | 2021-07-22T09:23:25 | 2021-07-22T09:23:25 | {} | NONE |
vuejs | core | 884,937,949 | 4,171 | yyx990803 | This is expected because `defineCustomElement` only handles the runtime interop - the styles in SFCs need to be compiled differently when targeting WCs and that will require tooling updates as well. | 2021-07-22T14:02:32 | 2021-07-22T14:02:32 | {} | MEMBER |
vuejs | core | 886,227,902 | 4,191 | posva | Please open a new issue with a link that works and in English | 2021-07-25T16:42:57 | 2021-07-25T16:42:57 | {} | MEMBER |
vuejs | core | 886,310,809 | 4,179 | flicat | > @flicat 为啥呢，我没测试，按照尤大的评论，应该是可以解决的啊。
>
> I did a demo see [playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8bXlDb20+PC9teUNvbT48IS0t6IO95q2j5bi45pi+56S6LS0+XG48L3RlbXBsYXRlPlxuXG48c2NyaXB0PlxuaW1wb3J0IHsgZ2V0Q3VycmVudEluc3RhbmNlIH0gZnJvbSAndnVlJ1xuaW1wb3J0IG15X3BsdWdpbiBmcm9tICcuL215X3BsdWdpbi... | 2021-07-26T01:45:28 | 2021-07-26T02:06:34 | {} | NONE |
vuejs | core | 884,724,222 | 4,170 | posva | You can open an issue or pull request with a proposal in the docs repo but make sure to search first in case it has already been discussed | 2021-07-22T07:58:24 | 2021-07-22T07:58:24 | {} | MEMBER |
vuejs | core | 885,061,713 | 4,178 | ZeronoFreya | 正是问了没有得到回复才发帖的 | 2021-07-22T16:49:49 | 2021-07-22T16:49:49 | {} | NONE |
vuejs | core | 885,461,373 | 4,179 | flicat | 老项目升级，不能解决就不升级了 :cry: | 2021-07-23T07:45:46 | 2021-07-23T07:45:46 | {} | NONE |
vuejs | core | 886,082,770 | 4,189 | lidlanca | doesn't a `watch` with `onTrigger` work for your specific use case? | 2021-07-24T17:18:31 | 2021-07-24T17:18:31 | {} | CONTRIBUTOR |
vuejs | core | 886,017,743 | 4,183 | edison1105 | mini repro see [playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IGlkPVwibW9kYWxzXCI+PC9kaXY+XG4gIDxBIHYtaWY9XCJ0b2dnbGVcIj5cbiAgXHQ8TW9kYWxBPjwvTW9kYWxBPlxuICA8L0E+XG4gIDxidXR0b24gQGNsaWNrPVwiY2hhbmdlXCI+IHRvZ2dsZSA8L2J1dHRvbj5cbjwvdGVtcGxhdGU+XG5cbjxzY3JpcHQgc2V0dXA+XG5pbXBvcnQgeyBjb21wdXRlZ... | 2021-07-24T08:04:47 | 2021-07-26T14:47:13 | {} | MEMBER |
vuejs | core | 888,073,895 | 4,206 | ht-sauce | 应该是vuecli5下面的bug换个地方提 | 2021-07-28T07:16:55 | 2021-07-28T07:16:55 | {} | NONE |
vuejs | core | 888,074,997 | 4,206 | edison1105 | @ht-sauce
这的确不是 vue 的 bug。请参照：
https://babeljs.io/docs/en/babel-plugin-proposal-nullish-coalescing-operator
| 2021-07-28T07:18:43 | 2021-07-28T07:18:43 | {} | MEMBER |
vuejs | core | 889,840,636 | 4,214 | jods4 | @posva Please don't make me fill everything again... you could have kept the issue open just a day and given me a chance to append the repro here.
I tried a minimal JS repro (basically on `npm init vite` and it worked.
Then I added `lang="ts"` on the script tag and it broke. That's the missing bit. | 2021-07-30T11:51:17 | 2021-07-30T11:51:17 | {} | CONTRIBUTOR |
vuejs | core | 884,687,253 | 4,170 | yodarocks1 | Makes sense. Perhaps the documentation should be updated, then. Should I open a new issue there? | 2021-07-22T06:35:55 | 2021-07-22T06:35:55 | {} | NONE |
vuejs | core | 884,949,993 | 4,175 | yyx990803 | Stackblitz doesn't seem to be using the actual `vue-cli` since when I clone the project locally the dependencies aren't even correct. e.g. it doesn't even have `@vue/compiler-sfc` in the dependencies list. It seems to be emulating what `vue-cli` does in their custom in-browser setup while pretending to be a `vue-cli` p... | 2021-07-22T14:17:52 | 2021-07-22T14:20:43 | {} | MEMBER |
vuejs | core | 887,369,671 | 4,196 | posva | Given that the setup equivalent works, I would consider it a fix | 2021-07-27T09:44:19 | 2021-07-27T09:44:19 | {} | MEMBER |
vuejs | core | 887,439,788 | 3,414 | yuanjinyong | > 这个啥时候能用上呢
同问 | 2021-07-27T11:38:42 | 2021-07-27T11:38:42 | {} | NONE |
vuejs | core | 888,382,985 | 4,204 | yyx990803 | This is expected behavior, because when you bind `v-model` to `item.id`, `item` is a closure variable - so every render a new `v-model` callback has to be generated (and cannot be cached due to correctness). This causes the child component to re-render.
See [compiler output example](https://vue-next-template-explore... | 2021-07-28T15:01:09 | 2021-07-28T15:02:11 | {} | MEMBER |
vuejs | core | 888,612,990 | 4,186 | yyx990803 | Good catch in https://github.com/vuejs/vue-next/issues/4183#issuecomment-886017743 - the root cause is we are overwriting `dynamicChildren` when the suspense slot is itself a block. If it's a block we should just skip overwriting it.
See 51ee84fc | 2021-07-28T20:51:52 | 2021-07-28T20:51:52 | {} | MEMBER |
vuejs | core | 889,191,262 | 4,184 | yyx990803 | Yeah I guessed that would be the case seeing your optimizations, just didn't expect the use case to be that extreme 😅
I'll merge this and do some small tweaks - in the future can you allow editing when submitting PRs so I can make small adjustments before merging? | 2021-07-29T14:25:59 | 2021-07-29T14:25:59 | {
"+1": 1,
"hooray": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.