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 | 861,541,558 | 3,958 | sqal | oh my somehow i missed that this behaviour is intentional and I should configure compat build like this:
```configureCompat({ COMPONENT_ASYNC: false });```
I think we can close it now, sorry for false alarm
| 2021-06-15T14:21:08 | 2021-06-15T14:21:08 | {} | CONTRIBUTOR |
vuejs | core | 857,324,840 | 3,913 | HcySunYang | duplicated of #3910 | 2021-06-09T02:36:18 | 2021-06-09T02:36:18 | {} | MEMBER |
vuejs | core | 857,513,743 | 3,919 | mwwm1 | هلا | 2021-06-09T08:52:09 | 2021-06-09T08:52:09 | {} | NONE |
vuejs | core | 857,732,471 | 3,899 | mlzzen | Win10 Edge 91.0.864.41
when openning devtool, 0, 2, 4, 6, 8 | 2021-06-09T14:16:03 | 2021-06-09T14:16:03 | {} | NONE |
vuejs | core | 858,749,131 | 3,936 | jaulz | I think it's related to this piece of code in my dependencies:
https://github.com/inertiajs/inertia/blob/1580d2ba887c4f50b57e8dc0fa0707da3e123b2b/packages/inertia-vue/src/form.js#L181-L190
There is no render function and maybe thus the vnode is empty? | 2021-06-10T16:04:09 | 2021-06-10T16:04:09 | {} | CONTRIBUTOR |
vuejs | core | 859,550,210 | 3,941 | 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-11T12:34:53 | 2021-06-11T12:34:53 | {} | CONTRIBUTOR |
vuejs | core | 862,175,590 | 2,794 | patak-cat | Closing as this was resolved by https://github.com/vuejs/vue-next/commit/8b94464a3b9759a7a98c23efeafc7a9359c9807d | 2021-06-16T08:46:39 | 2021-06-16T08:46:39 | {} | MEMBER |
vuejs | core | 862,196,280 | 3,758 | oliverzy | https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aDE+e3sgbXNnIH19PC9oMT5cbiAgPENoaWxkIHJlZj1cImNoaWxkXCI+PC9DaGlsZD5cbjwvdGVtcGxhdGU+XG5cbjxzY3JpcHQgc2V0dXA+XG5pbXBvcnQgeyByZWYsIG9uTW91bnRlZCB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBDaGlsZCBmcm9tICcuL0NoaWxkLnZ1ZSdcbmNvbnN0IG1zZyA9ICdIZWxsbyBXb3JsZCEnXG5jb25zdCBjaGlsZCA9I... | 2021-06-16T09:16:44 | 2021-06-16T09:16:44 | {} | NONE |
vuejs | core | 856,970,666 | 3,910 | lidlanca | The fix #3675 for #3673 for the case of `obj[x[0]]`
regressed the case of `obj[0][0]` | 2021-06-08T17:50:09 | 2021-06-08T17:50:09 | {} | CONTRIBUTOR |
vuejs | core | 858,533,077 | 3,927 | nabaonan | > I'm a bit unsure what you are trying to achieve here.
>
> `<script setup>` is definitely not designed to export default a functional TSX component.
>
> It's designed to work with a template. for the most part, it exists so you can have an authoring experience similar to that of a .tsx file - no need to register... | 2021-06-10T11:13:40 | 2021-06-10T11:13:40 | {} | NONE |
vuejs | core | 861,243,017 | 3,953 | posva | This makes attrs and props have a consistent behavior after https://github.com/vuejs/vue-next/issues/3288: you shouldn't differentiate the cases where `undefined` is explicitly passed vs the prop is missing | 2021-06-15T07:12:08 | 2021-06-15T07:31:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 861,984,572 | 3,953 | wenfangdu | @posva Thanks for clarifying, another change I overlooked is the following, which caused the confusion, attaching it here for future reference:
> [**BREAKING**: No longer removes attribute if the value is boolean `false`. Instead, it's set as attr="false". To remove the attribute, use `null` or `undefined`.](https:/... | 2021-06-16T02:19:30 | 2021-06-16T02:24:52 | {} | NONE |
vuejs | core | 856,955,889 | 3,896 | lidlanca | v-if and v-else , etc uses auto increment key, which is set on the node.key as well on the node.props.key
making it impossible for you to know if the key was set via a prop or via the magical implicit v-if v-else conditional rendering .
your mistake was that you use **key** attribute/prop which is not just special... | 2021-06-08T17:27:33 | 2021-06-08T17:27:33 | {} | CONTRIBUTOR |
vuejs | core | 857,298,964 | 3,913 | edison1105 | duplicated of #3910 | 2021-06-09T01:20:20 | 2021-06-09T01:20:28 | {} | MEMBER |
vuejs | core | 857,417,427 | 3,914 | posva | Can you open an RFC on the rfcs repository? | 2021-06-09T06:23:56 | 2021-06-09T06:23:56 | {} | MEMBER |
vuejs | core | 859,242,760 | 3,936 | jaulz | @leopiccionia yep, that did the job and was anyway the longterm solution. Thanks! 😊 Shall we keep the issue open or is this error too specific? | 2021-06-11T03:52:06 | 2021-06-11T03:52:06 | {} | CONTRIBUTOR |
vuejs | core | 859,562,988 | 3,942 | posva | Please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next&lang=zh-cn#why-repro and open issues in English | 2021-06-11T12:57:36 | 2021-06-11T12:57:36 | {} | MEMBER |
vuejs | core | 859,542,160 | 3,924 | posva | You can declare a prop named `onEvent` to detect an attached event `@event` on `props.onEvent` ([example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aDE+e3sgbXNnIH19IHt7IG4gfX08L2gxPlxuICA8Y29tcD48L2NvbXA+XG4gIDxjb21wIEBmb289XCJtc2dcIj48L2NvbXA+XG4gIDxocj5cbiAgPGNvbXAyLz5cbiAgPGNvbXAyIEBmb289XCJuKytcIi8... | 2021-06-11T12:20:32 | 2021-06-11T12:58:37 | {
"+1": 1
} | MEMBER |
vuejs | core | 860,259,841 | 3,933 | lidlanca | same story for elements moved to an iframe. | 2021-06-13T19:36:33 | 2021-06-13T19:36:33 | {} | CONTRIBUTOR |
vuejs | core | 857,207,307 | 3,912 | benlesh | Really thinking about all of the implications of this, some sort of `Observable` type is more ideal for this (not necessarily an RxJS observable), but a push stream that is lazy and cancellable. AsyncIterable, while cool because of `for await`, may not be the best way to go. | 2021-06-08T22:07:56 | 2021-06-08T22:07:56 | {} | NONE |
vuejs | core | 858,428,527 | 3,929 | posva | Open a new issue with a proper bug report like asked in the new issue website. You can use sfc.vuejs.org for simple reproductions | 2021-06-10T08:35:23 | 2021-06-10T08:35:23 | {} | MEMBER |
vuejs | core | 858,542,294 | 1,380 | yaquawa | no workaround for this? | 2021-06-10T11:29:34 | 2021-06-10T11:29:34 | {} | NONE |
vuejs | core | 860,469,984 | 3,944 | posva | As a workaround, you can use a regular function.
The relevant commit in Vue 2 was https://github.com/vuejs/vue/commit/0e4e45ec741416e0042c29a53bbc0e58c8663f6e | 2021-06-14T07:55:02 | 2021-06-14T07:55:02 | {} | MEMBER |
vuejs | core | 856,898,331 | 3,891 | LinusBorg | Posting "same here" on a closed issue without providing a reproduction won't help us to solve this.
please open a new issue and provide a real reproduction | 2021-06-08T16:03:09 | 2021-06-08T16:03:09 | {} | MEMBER |
vuejs | core | 857,197,786 | 3,912 | benlesh | I did add a second commit that considers the issues that may arise with refs that are contained by a component that gets unmounted. It's probable that this isn't something that would be a problem.
Ultimately though, it might be that this is another example of where `Promise` falls on it's face because it's non-cance... | 2021-06-08T21:57:48 | 2021-06-08T21:57:48 | {} | NONE |
vuejs | core | 857,327,089 | 3,910 | HcySunYang | RegExp cannot cover all use cases, maybe it is more reasonable to use babel to check the validity of expressions, but considering the compiler in the browser environment, including babel is not a good solution. | 2021-06-09T02:41:47 | 2021-06-09T02:46:38 | {} | MEMBER |
vuejs | core | 857,348,765 | 3,896 | tangjinzhou | Thank you for your suggestions.
I know this is an unreasonable way to use it, but due to the high cost of component changes to the API, it will be a breaking change.
Is it possible for Vue to expose the `key` to users and use other name or use special values as Vue-generated keys. | 2021-06-09T03:45:21 | 2021-06-09T03:45:21 | {} | CONTRIBUTOR |
vuejs | core | 857,458,668 | 3,919 | zhangenming | 
why CI Failing...
but is it OK for my locally, I tried several times...
thanks... | 2021-06-09T07:29:32 | 2021-06-09T07:29:32 | {} | CONTRIBUTOR |
vuejs | core | 859,534,937 | 3,936 | posva | @jaulz please read https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro | 2021-06-11T12:07:39 | 2021-06-11T12:07:39 | {} | MEMBER |
vuejs | core | 857,853,799 | 906 | r4pt0s | I tried what @dacxjo mentioned in a standard project created with @vue/cli 4.5.13 which works with webpack.
Somehow, the issue only exists while developing with the webpack dev server.
Once the project is build with
`yarn run build`
the finished build is working properly.
The issue only exists by using
... | 2021-06-09T16:34:07 | 2021-06-09T16:39:01 | {
"+1": 1
} | NONE |
vuejs | core | 859,937,490 | 3,944 | LinusBorg | > Confusingly, however, I've also seen zero people talking about this being a problem!
I personally only every "dumped" objects in interpolations for debugging. I've never seen `toString()` being used in that way anywhere. I know it exists, but you are kind of the first person I learn of that relies on this behavior... | 2021-06-11T22:21:11 | 2021-06-11T22:21:40 | {
"+1": 1,
"-1": 1
} | MEMBER |
vuejs | core | 860,307,813 | 2,775 | nandodrw | @ravenclaw900 @bobohuochai as @LinusBorg point as soon you define the return types of your computed properties the types from the data properties will work just fine(looks like not doing it breaks all the typing on the component). | 2021-06-14T01:18:57 | 2021-06-14T01:18:57 | {} | NONE |
vuejs | core | 860,879,812 | 3,951 | LinusBorg | Hint: you can import the image in JS and then insert the path you get from that import to your runtime template.
I suggest you use chat.vuejs.org to ask for more help. | 2021-06-14T17:59:04 | 2021-06-14T17:59:04 | {} | MEMBER |
vuejs | core | 861,252,399 | 3,953 | wenfangdu | @posva Please pardon me, am I understanding consistency wrong? I've updated my [repro](https://github.com/wenfangdu/vue-attrs-repro), please have a look.
```jsx
import { defineComponent } from 'vue'
export default defineComponent({
inheritAttrs: false,
props: {
baz: String,
},
setup(props, { att... | 2021-06-15T07:24:14 | 2021-06-15T07:24:33 | {} | NONE |
vuejs | core | 857,723,092 | 3,899 | edison1105 | yes,I opened dev tools.but still works fine. | 2021-06-09T14:04:43 | 2021-06-09T14:04:43 | {} | MEMBER |
vuejs | core | 860,276,166 | 3,668 | lidlanca | feel free to close this issue, another fix was merged for the unicode fix. | 2021-06-13T22:03:09 | 2021-06-13T22:03:09 | {} | CONTRIBUTOR |
vuejs | core | 860,474,601 | 3,948 | jacekkarczmarczyk | > `type: null` which currently allows anything (as allowing a prop only when it's null makes no sense)
On the other hand `[whatever, null]` doesn't make sense as well, if `null` means "anything" then adding other types to the array is pointless. And because of that it's very unlikely that it would be a breaking chan... | 2021-06-14T08:01:28 | 2021-06-14T08:01:28 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 792,437,448 | 1,228 | privatenumber | Experiencing this in my project too. In my use-case, I'm trying to reference the [`NodeTypes` enum from `@vue/compiler-core`](https://github.com/vuejs/vue-next/blob/540e26f49c09edf09b6a60ac2a978fdec52686bf/packages/compiler-core/src/ast.ts#L25) to do template node type checks at run-time.
Curious what the expected s... | 2021-03-08T03:35:56 | 2021-06-15T00:51:56 | {} | CONTRIBUTOR |
vuejs | core | 861,348,635 | 3,955 | posva | Please don't use fake reproductions. Follow https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro and provide a boiled down repro **on the right repository** (vue if Vue 2, vue-next if Vue 3).
This could help: https://ssr.vuejs.org/ | 2021-06-15T09:37:09 | 2021-06-15T09:37:09 | {} | MEMBER |
vuejs | core | 851,146,869 | 3,849 | HcySunYang | If it works correctly in vite, then it should not be a problem with Vue, please make sure you install the correct dependencies when using with `vue-cli`. | 2021-05-31T03:40:54 | 2021-05-31T03:40:54 | {
"confused": 3,
"eyes": 1
} | MEMBER |
vuejs | core | 851,249,421 | 3,853 | SeregPie | already posted.
#3839
^^ | 2021-05-31T07:06:00 | 2021-05-31T07:06:00 | {
"+1": 1
} | NONE |
vuejs | core | 851,267,684 | 3,855 | LinusBorg | `h1styles` should be a computed property. Your code permanently writes the initial prop value to the ref's `fonSize` property. | 2021-05-31T07:30:18 | 2021-05-31T07:30:58 | {} | MEMBER |
vuejs | core | 851,282,522 | 3,855 | nickngqs | Thanks for the help. Just curious, shouldn't the behaviour of HMR also update it too, since the attribute value has been edited. (purely from a HMR point of view)
| 2021-05-31T07:49:37 | 2021-05-31T07:49:37 | {} | NONE |
vuejs | core | 851,381,228 | 3,854 | posva | Follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro. or use the chat/forum to ask questions. | 2021-05-31T10:08:24 | 2021-05-31T10:08:24 | {} | MEMBER |
vuejs | core | 852,407,792 | 3,870 | LinusBorg | ~~Prerendering as you describe it is not meant to be hydrated. It's meant to create purely static pages.~~
~~If you want to hydrate, you should render the pages with an actual SSR setup. That will produce DOM that can actually be hydrated.~~
Edit: i misread. It seems you actually run a full Vue SSR setup from whi... | 2021-06-01T19:59:53 | 2021-06-01T20:08:31 | {
"-1": 2
} | MEMBER |
vuejs | core | 852,870,118 | 3,868 | LinusBorg | > let's for Vue 4 where options api is removed completely theoretically
Just to be clear: That won't happen. The Options API is not and will not be deprecated.
Further discussion can happen in the RFC discussion topic that you opened. | 2021-06-02T09:33:02 | 2021-06-02T09:33:02 | {} | MEMBER |
vuejs | core | 853,355,553 | 3,858 | dependabot[bot] | Superseded by #3876. | 2021-06-02T20:18:42 | 2021-06-02T20:18:42 | {} | CONTRIBUTOR |
vuejs | core | 853,741,698 | 3,874 | posva | I updated the expected and actually happening based on what you explained. Edit it if that's not what you meant | 2021-06-03T09:49:42 | 2021-06-03T09:49:42 | {
"+1": 1
} | MEMBER |
vuejs | core | 854,094,553 | 3,875 | cryi | Yea looks nice @posva. I made pull request with this. Please let me know if you require any changes.
I would like to get this feature out so we can continue with library migration. | 2021-06-03T18:42:56 | 2021-06-03T18:42:56 | {} | NONE |
vuejs | core | 856,420,305 | 3,897 | mannok | > I think this is a duplicate of #3557
Sorry I don't understand, so the key is that I need to check for `el` is `null` or `undefined` at first before assigning `el` into variable? Or I cannot use object instead of array to store `el`? | 2021-06-08T04:01:58 | 2021-06-08T04:04:26 | {} | NONE |
vuejs | core | 856,511,713 | 3,897 | posva | You need to check `el`: https://v3.vuejs.org/guide/composition-api-template-refs.html#usage-inside-v-for | 2021-06-08T07:03:40 | 2021-06-08T07:03:40 | {} | MEMBER |
vuejs | core | 851,497,884 | 3,846 | posva | The error comes from replit not implementing the needed functionality | 2021-05-31T13:37:22 | 2021-05-31T13:37:22 | {} | MEMBER |
vuejs | core | 852,476,521 | 3,111 | klarkc | +1 In my use case, we're using native esm in the server and in the client. Even running in the server, because ssrUtils use CJS to detect the node target, it assumes that is not a SSR (which is not true).
https://github.com/vuejs/vue-next/blob/44996d1a0a2de1bc6b3abfac6b2b8b3c969d4e01/packages/runtime-core/src/index.... | 2021-06-01T21:57:48 | 2021-06-01T21:57:48 | {} | NONE |
vuejs | core | 852,667,455 | 3,682 | 07akioni | Must we create a new class for props definition? | 2021-06-02T02:36:41 | 2021-06-02T02:36:41 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 853,327,572 | 3,600 | yyx990803 | Great work in this PR - I tried to rebase it locally while figuring out a better caching strategy. We don't want to run options merging for every instance since this was a major perf overhead in Vue 2, but in Vue 3 caching becomes a bit tricky due to different app instances may have different global mixins and merge st... | 2021-06-02T19:31:06 | 2021-06-02T19:31:06 | {} | MEMBER |
vuejs | core | 854,343,615 | 3,885 | Picknight | I tried above reproduction link, `beforeEnter` and `beforeEnter` has indeed triggered.
| 2021-06-04T04:11:35 | 2021-06-04T04:11:35 | {} | CONTRIBUTOR |
vuejs | core | 854,430,281 | 3,886 | 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-06-04T07:19:42 | 2021-06-04T07:19:42 | {} | MEMBER |
vuejs | core | 854,860,653 | 3,889 | posva | This was intended. You have a workaround at https://github.com/vuejs/vue-next/issues/3288#issuecomment-835566953
Maybe this should be documented | 2021-06-04T16:32:40 | 2021-06-04T16:32:40 | {} | MEMBER |
vuejs | core | 855,162,326 | 3,883 | yyx990803 | Vuex 3 should also work with the migration build in theory. | 2021-06-05T01:28:24 | 2021-06-05T01:28:24 | {} | MEMBER |
vuejs | core | 856,007,153 | 3,896 | posva | > We use instance.vnode.key to process the component logic. Due to historical reasons, changing the api design is a costly thing.
Rather than saying _"We just don't want to update our codebase"_, what is the actual case for reliying on `vnode.key` ? | 2021-06-07T14:55:12 | 2021-06-07T14:55:12 | {} | MEMBER |
vuejs | core | 851,342,718 | 3,856 | Soviut | It isn't just to be able to reuse the name. It would also be useful for migration to the composition API by being explicit about which values are returned to the template. As a long-time Vue 2 user, the props being appended to `this` made sense to me. However, the composition API is so explicit with a `props` argument ... | 2021-05-31T09:06:05 | 2021-05-31T09:08:35 | {} | NONE |
vuejs | core | 851,902,053 | 3,867 | posva | https://github.com/vuejs/vue-next/issues/3846#issuecomment-851901982 | 2021-06-01T07:41:14 | 2021-06-01T07:41:14 | {} | MEMBER |
vuejs | core | 852,402,875 | 3,870 | Trinovantes | Maybe this title should omit "SSG" if my terminology is mixed up?
My issue is that prerendering seems to be impossible in Vue 3 since the DOM generated by an SPA cannot be hydrated later due to hydration mismatch.
This does not actually hydrate:
```ts
const app = createApp(App)
app.mount('#app', true) // This ... | 2021-06-01T19:51:22 | 2021-06-01T19:51:22 | {
"+1": 2
} | NONE |
vuejs | core | 852,421,201 | 3,870 | LinusBorg | Well, as I said, I think that if you prerender in the sense of saving the output of a SSR-rendered app, it should be hydratable.
If you have troubles with that, find help in the community. If you think you found a bug, please open a bug issue with a reproduction. | 2021-06-01T20:23:00 | 2021-06-01T20:23:00 | {} | MEMBER |
vuejs | core | 853,356,006 | 3,861 | dependabot[bot] | Superseded by #3878. | 2021-06-02T20:19:26 | 2021-06-02T20:19:26 | {} | CONTRIBUTOR |
vuejs | core | 853,592,876 | 3,879 | ouronghuang | Sorry, the typesetting order is wrong and fixed. | 2021-06-03T06:06:22 | 2021-06-03T06:06:22 | {} | NONE |
vuejs | core | 853,888,395 | 1,056 | chadrackkanza | > @johnsoncodehk Object is possibly 'null'. How to solve this?
Vuejs and TypeScript ? | 2021-06-03T13:54:46 | 2021-06-03T13:54:59 | {} | NONE |
vuejs | core | 853,946,039 | 3,881 | yyx990803 | 1. Are you using Suspense?
2. Can you confirm that: (1) it works in beta.4, and (2) still broken in beta.7?
There are only 7 commits between beta.4 and beta.5 so if possible you can build and link `@vue/runtime-core` locally to isolate the commit that caused the issue. | 2021-06-03T15:12:09 | 2021-06-03T15:12:09 | {} | MEMBER |
vuejs | core | 854,125,710 | 1,414 | jfbrennan | Thanks to everyone else who has shared.
This is what worked for me (i.e. I'm building with mode=development and expect the warnings about custom elements to go away, and they finally did):
```
// package.json
{
"name": "...",
"version": "0.1.0",
"private": true,
"scripts": {
"build": "vue-cli-serv... | 2021-06-03T19:36:14 | 2021-06-03T19:38:21 | {
"+1": 3
} | NONE |
vuejs | core | 854,443,493 | 1,056 | chadrackkanza | Put ! in end of value to force it.
Example :
let a = my_var!
Le ven. 4 juin 2021 à 02:18, ZeHung ***@***.***> a écrit :
> @johnsoncodehk <https://github.com/johnsoncodehk> Object is possibly
> 'null'. How to solve this?
>
> Vuejs and TypeScript ?
>
> Yes~
>
> —
> You are receiving this because you commented.
> Reply... | 2021-06-04T07:35:32 | 2021-06-04T07:35:32 | {} | NONE |
vuejs | core | 854,461,360 | 3,885 | sh-winter | okay, thank you | 2021-06-04T08:00:12 | 2021-06-04T08:00:12 | {} | NONE |
vuejs | core | 855,302,027 | 3,891 | LinusBorg | the linked "reproduction" does not contain the code mentioned in the description.
Please open a new issue with a real reproduction. | 2021-06-05T22:05:18 | 2021-06-05T22:05:18 | {} | MEMBER |
vuejs | core | 856,206,852 | 3,892 | lidlanca | @HcySunYang I am not totally against the `<pre></pre>` enveloping as a possible workaround.
Is there a reason for example, why the `v-pre` directive is not being considered by the compiler, as a flag to indicate
leave the content raw.
```
<customScript v-pre>
var msg = "hello"
alert(msg)
</customScript>... | 2021-06-07T19:43:53 | 2021-06-07T19:43:53 | {} | CONTRIBUTOR |
vuejs | core | 851,284,004 | 3,855 | LinusBorg | No it should not. | 2021-05-31T07:51:30 | 2021-05-31T07:51:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 851,451,637 | 3,856 | LinusBorg | Agree with posva. See:
https://github.com/vuejs/rfcs | 2021-05-31T12:17:52 | 2021-05-31T12:17:52 | {} | MEMBER |
vuejs | core | 851,012,532 | 3,851 | xieyezi | I find it myself ,That is because my HotList.vue name is error.... | 2021-05-30T14:53:04 | 2021-05-30T14:53:04 | {} | NONE |
vuejs | core | 853,340,000 | 991 | inca | I don't really mind going for a workaround — as long as it a) works (i.e. the `ref.value = ref.value` hack doesn't work with typed arrays) and b) is documented. I think it's the least Vue can do to support those niche users with their niche use cases 🙏 | 2021-06-02T19:52:40 | 2021-06-02T19:52:40 | {} | NONE |
vuejs | core | 853,703,637 | 1,324 | ssipos90 | so why'd you close it? | 2021-06-03T08:51:46 | 2021-06-03T08:51:46 | {} | NONE |
vuejs | core | 853,947,647 | 3,881 | AlexandreBonaventure | 1. Not using Suspense
2. It works in 3.x including (beta.4) and still broken in beta.7, yup!
OK doing that now! | 2021-06-03T15:14:24 | 2021-06-03T15:14:24 | {} | CONTRIBUTOR |
vuejs | core | 853,974,309 | 3,792 | toams69 | Uses Capitalized Case for needed attributes can help without create a directive. | 2021-06-03T15:49:18 | 2021-06-03T15:49:28 | {} | NONE |
vuejs | core | 855,372,300 | 3,258 | nandi95 | @posva
Could you perhaps tag some team members to get some movement on this? | 2021-06-06T10:00:52 | 2021-06-06T10:00:52 | {} | CONTRIBUTOR |
vuejs | core | 856,388,162 | 3,896 | tangjinzhou | `vnode.key` does not have to be dependent. We can use other attributes instead. But because the historical component has already used the key to process the component logic.
Our usage scenario is that the child component passes the key to the parent component through the inject method. The parent component will use th... | 2021-06-08T02:24:19 | 2021-06-08T02:24:19 | {} | CONTRIBUTOR |
vuejs | core | 852,063,018 | 3,796 | chenjiahan | @posva @pikax The type of `Component.props` is missing after wrapping the `defineComponent` method, which makes it difficult to create HOC.
```js
import { defineComponent } from 'vue';
const Component1 = {
props: {
foo: String,
},
};
const Component2 = defineComponent(Component1);
Component1.... | 2021-06-01T11:53:25 | 2021-06-08T05:19:20 | {} | CONTRIBUTOR |
vuejs | core | 856,760,945 | 3,891 | MrJuliuss | Hi, i got the same error since `@vue/compiler-sfc` `3.1.1`. It works fine with `3.0.11`
```
VueCompilerError: v-model value must be a valid JavaScript member expression.
v-model="selectedFilters[index][value]"
``` | 2021-06-08T13:20:07 | 2021-06-08T13:24:24 | {} | NONE |
vuejs | core | 851,333,517 | 3,856 | posva | So you want an option to disable the ability to use `this.aProp` and `aProp` just so it's possible to reuse the same name to create a normalized/transformed version of a prop.
This looks rather confusing when reading a component props and then checking its template and other methods (for people not using setup).
If a... | 2021-05-31T08:53:24 | 2021-05-31T08:53:24 | {} | MEMBER |
vuejs | core | 852,115,768 | 3,869 | yyx990803 | This is expected because you need to explicitly handle SSRed Teleports.
They are exposed on the ssr context:
```js
const ctx = {}
const html = await renderToString(app, ctx)
console..log(ctx.teleports)
```
You need to return this from `render` in `entry-server.js` and then inject them into the final HTML... | 2021-06-01T13:16:30 | 2021-06-01T13:16:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 852,838,910 | 2,781 | drl990114 | 可能是引入了无法解析的html标签，我使用vite时遇到了相同的错误，我替换了标签后不再报错了。 | 2021-06-02T08:15:19 | 2021-06-02T08:15:19 | {} | NONE |
vuejs | core | 853,627,125 | 3,879 | posva | This is expected for objects because vue mutâtes the object. It's also documented | 2021-06-03T07:03:08 | 2021-06-03T07:03:08 | {} | MEMBER |
vuejs | core | 854,499,164 | 3,888 | zezhongmiao | 1 | 2021-06-04T09:00:25 | 2021-06-04T09:00:25 | {} | NONE |
vuejs | core | 854,985,921 | 3,889 | yyx990803 | Yes, this is an unfortunate case where the behavior inconsistency between Vue 2 and Vue 3 led to code that relies on the Vue 3 behavior. However it is still considered a fix since the behavior consistency has a higher priority.
I've updated pending 3.1 docs update to document this in https://github.com/vuejs/docs-ne... | 2021-06-04T20:38:40 | 2021-06-04T20:38:40 | {} | MEMBER |
vuejs | core | 852,415,366 | 3,870 | Trinovantes | No I don't have any SSR right now
> Prerendering as you describe it is not meant to be hydrated. It's meant to create purely static pages.
Thanks for confirming my suspicions. I will be rewriting my app into SSR to fix my issue
---
The process that I've described for "prerendering" is exactly what the `prer... | 2021-06-01T20:12:21 | 2021-06-01T20:12:21 | {
"+1": 3
} | NONE |
vuejs | core | 853,160,870 | 3,872 | yyx990803 | The migration build **does** handle the render function `h` compat behavior: https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/compat/renderFn.ts#L44
The reproduction error in fact has nothing to do with render function behavior. The root cause is that some BoostrapVue components somehow declar... | 2021-06-02T16:13:30 | 2021-06-02T16:16:55 | {
"+1": 2
} | MEMBER |
vuejs | core | 856,402,193 | 3,896 | Justineo | I think relying on Vue's internal implementation isn't a very good idea. For your use case, it seems that you can just treat numbers as Vue-generated keys as your API says user-provided keys should be strings. But again, it's not safe as Vue may alternate the type of auto-generated keys in the future. | 2021-06-08T03:05:47 | 2021-06-08T03:05:47 | {
"+1": 6
} | MEMBER |
vuejs | core | 853,735,821 | 3,873 | 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-06-03T09:39:51 | 2021-06-03T09:39:51 | {} | MEMBER |
vuejs | core | 855,513,791 | 3,894 | edison1105 | as a workaround:
```diff
<template>
+ <div style="display:none">{{isDisplayed}}</div>
<transition>
<div v-if="isDisplayed" class="bloc">
[CompositionAPI]
{{ isDeferred ? "deferred" : "not deferred" }}
</div>
</transition>
</template>
```
The root cause is `useCssVars` called befor... | 2021-06-07T01:24:33 | 2021-06-07T12:36:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 851,400,011 | 3,846 | 07akioni | I found that the reason why the tests passed is jest mutates Promise. Emmm...
https://github.com/facebook/jest/issues/11497 | 2021-05-31T10:42:35 | 2021-05-31T10:42:35 | {} | CONTRIBUTOR |
vuejs | core | 852,126,356 | 3,846 | posva | I think the problem is you shouldn't be using `on('data')`, which creates the need for `read()` but I'm really not sure. | 2021-06-01T13:30:46 | 2021-06-01T13:30:46 | {} | MEMBER |
vuejs | core | 853,344,605 | 991 | inca | One other thing: it feels like the only non-tree-shakable payload boils down to just few hundred bytes https://github.com/vuejs/vue-next/pull/991/files#diff-a2a50542bbbe44521ef0f006956cf18fe68602c8fa520aefcb32d3addecbc2cfR56-R69 — everything else is imports, tests and type defs, which don't affect the production builds... | 2021-06-02T20:00:23 | 2021-06-02T20:00:23 | {} | NONE |
vuejs | core | 853,735,675 | 3,875 | posva | I personally think `v-deep` and `v-slotted` as attributes (with the `v-`) or a new attribute value (so there can only be one) like
```vue
<style scoped="deep" />
<style scoped="slotted" />
```
are a better fit | 2021-06-03T09:39:38 | 2021-06-03T09:39:38 | {
"+1": 11,
"heart": 1
} | MEMBER |
vuejs | core | 855,984,346 | 3,892 | HcySunYang | ~~You should set the compiler's `whitespace` option to `preserve`:~~
~~https://vue-next-template-explorer.netlify.app/#%7B%22src%22%3A%22%3Ch1%3E%7B%7B%20msg%20%7D%7D%3C%2Fh1%3E%5Cn%3CPreComponent%3E%5Cn%20%20%20%20Line1%5Cn%20%20%20%20Line2%5Cn%20%20%20%20Line3%5Cn%3C%2FPreComponent%3E%5Cn%5Cn%22%2C%22ssr%22%3Afals... | 2021-06-07T14:35:45 | 2021-06-07T14:54:34 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.