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 | 569,726,080 | 562 | yyx990803 | FYI: https://github.com/vuejs/vue-next/commit/bfb0ad5a5e9b0b91d9436e43cb67388de47c7dbc | 2019-12-30T16:30:38 | 2019-12-30T16:31:16 | {} | MEMBER |
vuejs | core | 570,529,829 | 574 | posva | Does it makes sense to pass anything that isn't a string or an `h()` though (in both versions)? | 2020-01-03T10:19:16 | 2020-01-03T10:19:16 | {} | MEMBER |
vuejs | core | 571,628,342 | 590 | yyx990803 | Oh nvm, it's possible with `this.$watch`. | 2020-01-07T15:12:51 | 2020-01-07T15:12:51 | {} | MEMBER |
vuejs | core | 571,636,333 | 585 | yyx990803 | I would suggest a different way of doing this:
``` js
let oldClone = { ...obj }
watch(() => {
const keys = Object.keys(obj)
keys.forEach(key => {
// compare and sync
if (obj[key] !== oldClone[key]) {
// ...
}
})
}, { lazy: true })
```
This tracks both key changes and individual ... | 2020-01-07T15:30:34 | 2020-01-07T15:30:34 | {} | MEMBER |
vuejs | core | 571,915,080 | 595 | 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... | 2020-01-08T06:49:15 | 2020-01-08T06:49:15 | {} | CONTRIBUTOR |
vuejs | core | 573,273,535 | 609 | limingzhiguang | this.state.counter ++ | 2020-01-11T02:57:33 | 2020-01-11T02:57:33 | {} | NONE |
vuejs | core | 573,966,152 | 608 | yangmingshan | I'm doing a small experiment, want to log both props and context, but I'm to lazy to write two parameters😅. Maybe people will write code like this when they debugging. | 2020-01-14T02:14:18 | 2020-01-14T02:14:18 | {} | CONTRIBUTOR |
vuejs | core | 575,070,432 | 625 | posva | I can't see the warning you are talking about:
```html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>Document</title>
</head>
<body>
<div id="app"></div>
<script type="module">
... | 2020-01-16T09:47:19 | 2020-01-16T09:47:19 | {} | MEMBER |
vuejs | core | 575,173,920 | 625 | zeng450026937 | ok, i fixed the reproduction code.
https://codepen.io/itoito-cn/pen/WNbgrdN
it's not make sense if you don't pass any properties when we're talking about arrt fallthrough.
you should not close it so quickly...
-> markAttrsAccessed() is only called from componentProxy
| 2020-01-16T14:23:33 | 2020-01-16T14:24:38 | {} | NONE |
vuejs | core | 575,985,968 | 636 | posva | There is an open PR at https://github.com/vuejs/vue-next/pull/628 as well | 2020-01-19T09:45:12 | 2020-01-19T09:45:12 | {} | MEMBER |
vuejs | core | 576,028,042 | 635 | sqal | A similar issue was reported in 2.x long time ago https://github.com/vuejs/vue/issues/5443
however, emit in vue 3 works differently than `$emit` in 2.x. In vue 3, emit basically calls a prop which name starts with `onXXX` so `emit('click')` is equivalent to calling `props.onClick()`. As we can see [in the source co... | 2020-01-19T17:42:42 | 2020-01-19T19:08:52 | {} | CONTRIBUTOR |
vuejs | core | 577,583,655 | 629 | dxvladislavvolkov | @yyx990803 is it completely removed? or is it possible to use this method? | 2020-01-23T08:48:10 | 2020-01-23T08:48:10 | {} | NONE |
vuejs | core | 570,929,042 | 582 | posva | If you need to react to changes to the reactive object, you need to provide the `{deep: true}` option to `watch`
I don't think the return value of `reactive` is a watchsource. As shown in https://vue-composition-api-rfc.netlify.com/api.html#watch, it's necessary to wrap into a function. So doing `Vue.watch(() => examp... | 2020-01-05T16:58:53 | 2020-01-05T16:58:53 | {
"+1": 1
} | MEMBER |
vuejs | core | 573,113,951 | 608 | posva | I don't think you are supposed to destructure the 2 arguments of setup like that.
Being able to avoid creating the Context object altogether for components not using it (all components that only rely on props) is a big perf boost. The only possible reason to use the spread like that is to pass the args again to a diff... | 2020-01-10T16:48:27 | 2020-01-10T16:48:27 | {} | MEMBER |
vuejs | core | 574,625,677 | 604 | cexbrayat | I opened a dedicated #622 to track this. | 2020-01-15T11:49:33 | 2020-01-15T11:49:33 | {} | MEMBER |
vuejs | core | 575,973,324 | 636 | KaelWD | Duplicate of https://github.com/vuejs/vue-loader/issues/1632 | 2020-01-19T06:52:34 | 2020-01-19T06:52:34 | {} | CONTRIBUTOR |
vuejs | core | 575,985,830 | 637 | posva | The up to date version is at rfcs: https://github.com/vuejs/rfcs/blob/master/active-rfcs/0009-global-api-change.md | 2020-01-19T09:43:52 | 2020-01-19T09:43:52 | {} | MEMBER |
vuejs | core | 576,310,449 | 628 | yyx990803 | 👍 | 2020-01-20T14:57:22 | 2020-01-20T14:57:22 | {} | MEMBER |
vuejs | core | 570,545,157 | 574 | posva | Right, booleans make sense for jsx
Eduardo San Martin Morote
> On 3 Jan 2020, at 11:32, Jacek Karczmarczyk <notifications@github.com> wrote:
>
>
> Also Vue 2.0 allows booleans:
>
> export interface CreateElement {
> (tag?: string | Component<any, any, any, any> | AsyncComponent<any, any, any, any> | (() => Comp... | 2020-01-03T11:18:07 | 2020-01-03T11:18:07 | {} | MEMBER |
vuejs | core | 571,870,207 | 590 | yangmingshan | No, I didn't run into a real memory leak, I just thought it have risk, actually I didn't think about `this.$watch` 😂
But `this.$watch` won't be recorded in effects list right? So, do we need to change the implementation? Can I try? | 2020-01-08T03:01:14 | 2020-01-08T03:01:14 | {} | CONTRIBUTOR |
vuejs | core | 572,442,459 | 593 | wuyun1 | > You can do like this.
>
> ```
> const app = Vue.createApp()
> app.mount(Root, document.getElementById('app'))
>
> setTimeout(() => {
> // equal to $destroy
> Vue.render(null, document.getElementById('app') )
> }, 1000)
> ```
用这个方法可以实现 `unmount ` 效果， 成功触发了 vue 组件的 `beforeUnmou... | 2020-01-09T08:10:33 | 2020-01-09T08:10:33 | {} | NONE |
vuejs | core | 572,939,420 | 608 | yangmingshan | @KaelWD I know. But this is a trap, is it worth it? Maybe document it will help. | 2020-01-10T09:03:54 | 2020-01-10T09:03:54 | {} | CONTRIBUTOR |
vuejs | core | 576,284,576 | 645 | thecrypticace | IE 11 does not support multiple arguments to `add` or `remove` so this will likely need hooks so it can be handled properly in the Vue compat build. | 2020-01-20T13:54:48 | 2020-01-20T13:54:48 | {} | CONTRIBUTOR |
vuejs | core | 570,592,175 | 574 | KaelWD | https://github.com/vuejs/vue/issues/8498 | 2020-01-03T14:47:01 | 2020-01-03T14:47:01 | {} | CONTRIBUTOR |
vuejs | core | 571,881,748 | 590 | yangmingshan | Forget it, I break `KeepAlive` tests and I don't know why. | 2020-01-08T04:01:27 | 2020-01-08T04:01:27 | {} | CONTRIBUTOR |
vuejs | core | 572,002,499 | 585 | yangmingshan | Thanks for your suggestion, It's a much better way, I will close this PR.
Do you think the other part of this PR makes sense for edge case (check if effect is active before running it)? | 2020-01-08T11:09:36 | 2020-01-08T11:09:36 | {} | CONTRIBUTOR |
vuejs | core | 573,633,478 | 611 | posva | Please do your tests on your own repository | 2020-01-13T12:09:57 | 2020-01-13T12:09:57 | {} | MEMBER |
vuejs | core | 573,732,467 | 610 | yyx990803 | This has been fixed in `vue-loader@16.0.0-alpha.2`. The root cause is `vue-loader` incorrectly injecting `__hmrId` even when hot reload is not enabled. | 2020-01-13T15:54:30 | 2020-01-13T15:54:30 | {} | MEMBER |
vuejs | core | 574,084,765 | 608 | yangmingshan | I got your point, nice discussion. | 2020-01-14T09:32:01 | 2020-01-14T09:32:01 | {} | CONTRIBUTOR |
vuejs | core | 576,046,570 | 638 | LinusBorg | I think we should continue to support that. Will do a quick PR. | 2020-01-19T21:00:19 | 2020-01-19T21:00:19 | {
"heart": 2
} | MEMBER |
vuejs | core | 576,378,588 | 643 | yyx990803 | Hmm yes, this happens because optimized patch don't start from component root. I think we will need ~~a flag on vnodes for svg~~ to mark svg as block roots during compilation. | 2020-01-20T17:56:29 | 2020-01-20T17:58:55 | {} | MEMBER |
vuejs | core | 571,914,282 | 594 | 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... | 2020-01-08T06:46:16 | 2020-01-08T06:46:16 | {} | CONTRIBUTOR |
vuejs | core | 576,195,512 | 641 | yyyanghj | Just remove the setter's type and it works well
| 2020-01-20T09:54:08 | 2020-01-20T09:54:08 | {} | CONTRIBUTOR |
vuejs | core | 570,533,377 | 574 | jacekkarczmarczyk | Also Vue 2.6 allows booleans:
```ts
export interface CreateElement {
(tag?: string | Component<any, any, any, any> | AsyncComponent<any, any, any, any> | (() => Component), children?: VNodeChildren): VNode;
(tag?: string | Component<any, any, any, any> | AsyncComponent<any, any, any, any> | (() => Component), d... | 2020-01-03T10:32:13 | 2020-01-03T10:34:32 | {} | CONTRIBUTOR |
vuejs | core | 570,699,583 | 576 | 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... | 2020-01-03T21:12:11 | 2020-01-03T21:12:11 | {} | CONTRIBUTOR |
vuejs | core | 571,626,449 | 590 | yyx990803 | Did you run into a real memory leak with this? I think this is actually fine because watch effects are only recorded if `watch()` is called synchronously within `setup()`. No new watchers will be recorded after the `setup()` of the component, therefore the watchers recorded by an instance is deterministic - i.e. it's n... | 2020-01-07T15:08:26 | 2020-01-07T15:08:26 | {} | MEMBER |
vuejs | core | 573,729,856 | 609 | yyx990803 | In Vue 2, plain objects are converted in-place to become reactive. But in Vue 3, due to the use of proxy-based reactivity system, **the original object and the reactive proxy have different identities.**
So:
``` js
import { reactive } from 'vue'
const a = { count: 0 }
const proxyA = reactive(a)
console.lo... | 2020-01-13T15:49:19 | 2020-01-13T15:49:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 575,349,384 | 629 | yyx990803 | 3.0 doesn't have `Vue.extend` anymore. The lib you are using likely won't work with Vue 3 at this point. | 2020-01-16T21:13:33 | 2020-01-16T21:13:33 | {
"-1": 3,
"confused": 19,
"laugh": 1
} | MEMBER |
vuejs | core | 577,251,891 | 626 | yyx990803 | Since this is a pretty substantial PR, please be patient it takes some time for us to review it. | 2020-01-22T15:52:08 | 2020-01-22T15:52:08 | {} | MEMBER |
vuejs | core | 845,671,734 | 3,653 | unbyte | The cause is that, `Array.length` is both modified and observed in the render function.
btw, IIRC, in vue2, ref is non-reactive. | 2021-05-21T05:47:03 | 2021-05-21T05:47:03 | {} | CONTRIBUTOR |
vuejs | core | 845,711,868 | 3,200 | octo-topi | As I use [depcheck](https://github.com/depcheck/depcheck/pull/626), it causes this error message to de displayed at each `npm install`. When do you plan the next patch? | 2021-05-21T07:03:41 | 2021-05-21T07:03:41 | {
"+1": 4
} | NONE |
vuejs | core | 839,987,174 | 3,685 | daybrush | It seems to be resolved, and closes pr. | 2021-05-12T18:07:11 | 2021-05-12T18:07:11 | {} | NONE |
vuejs | core | 841,192,893 | 3,775 | posva | You can however do `import * as Vue from 'vue';`
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-05-14T11:45:02 | 2021-05-14T11:45:02 | {} | MEMBER |
vuejs | core | 842,356,143 | 3,784 | HcySunYang | are you sure? Not released yet | 2021-05-17T14:09:03 | 2021-05-17T14:09:03 | {} | MEMBER |
vuejs | core | 843,664,290 | 3,792 | edison1105 | you can write a custom directive as a workaround
see https://github.com/vuejs/vue-next/issues/3738 | 2021-05-19T00:52:13 | 2021-05-19T00:52:45 | {} | MEMBER |
vuejs | core | 845,864,406 | 3,809 | littlekie | > deep data change does not **trigger** watch, but it is still a data change (e.g. `shallowReactiveState.age.number` is still modified). So if anyone tries to **pull** the data, he will see the 1000 rather than the original 99.
>
> Then there is the scope of DOM update. There are optimizations built in so that Vue d... | 2021-05-21T10:50:36 | 2021-05-21T10:50:36 | {} | NONE |
vuejs | core | 846,416,215 | 3,792 | Giwayume | @LinusBorg What about adding a map in the Vue configuration like I discussed? That's zero performance loss if you don't use it, and it gives the application writer control over these scenarios where the library author may or may not make a change. In my perspective, having better control over the way a framework works ... | 2021-05-22T14:30:39 | 2021-05-22T14:30:39 | {
"+1": 1
} | NONE |
vuejs | core | 846,482,087 | 3,811 | hearsay316 | > 我克隆了您提供的项目，然后：
>
> ```js
> npm i
> yarn build
> serve dist
> ```
>
> 一切都工作正常，请确保提供有效的复制
我又更新了一个diff 分支
打包之前 npm serve
npm build
然后cd dist
live-serve
=>[h('div', [h('div', footerVNodes)])]
}
)
``` | 2021-05-16T13:47:23 | 2021-05-16T13:49:15 | {} | MEMBER |
vuejs | core | 845,135,602 | 2,364 | deepansh96 | I have the same problem!
Serving a production build didn't help in my case. | 2021-05-20T13:44:15 | 2021-05-20T13:44:15 | {} | NONE |
vuejs | core | 845,168,389 | 3,804 | possibility-of-offense | Okay if someone is seeing something else, please post it in here!
The problem was (or I think that was the problem) that I use the strict operator (===) and the values which was coming from the router parameters was string; the id from store.js was an integer. So I when I use comparison operator (==) everything was fi... | 2021-05-20T14:23:29 | 2021-05-20T14:23:29 | {} | NONE |
vuejs | core | 845,361,042 | 3,804 | possibility-of-offense | I was using Vue 3, I just forgot to set the version in the sandbox. Sorry about that. | 2021-05-20T18:25:23 | 2021-05-20T18:25:23 | {} | NONE |
vuejs | core | 840,105,643 | 3,760 | yyx990803 | It's not really a Vue problem or a Vetur problem, but just how TS works.
`PropType` is defined as a constructor that returns the actual prop type. `Function` never returns `null`, so TS doesn't allow it.
Technically speaking, TS is stricter than Vue's runtime semantics because Vue does allow `null` values for opt... | 2021-05-12T21:22:14 | 2021-05-12T21:22:36 | {
"+1": 2
} | MEMBER |
vuejs | core | 840,114,696 | 3,736 | dependabot[bot] | Superseded by #3765. | 2021-05-12T21:40:25 | 2021-05-12T21:40:25 | {} | CONTRIBUTOR |
vuejs | core | 841,647,149 | 3,777 | posva | Please communicate a little when opening an issue, don't just copy paste 3 lines of code of every form input. Also, provide a reproduction like said in https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro | 2021-05-15T12:02:00 | 2021-05-15T12:02:00 | {} | MEMBER |
vuejs | core | 841,918,268 | 3,779 | LLLeno | > The content of the slot needs to be passed like this:
>
> ```js
> return h(
> Modal,
> {
> modelValue: true,
> ref: 'modal'
> },
> {
> default:()=>[h('div', [h('div', footerVNodes)])]
> }
> )
... | 2021-05-17T01:29:43 | 2021-05-17T01:29:43 | {} | NONE |
vuejs | core | 843,549,798 | 3,792 | liamdebeasi | We are also running into this issue when using Ionic Vue, which is a set of Web Components with Vue component wrappers. When setting a Web Component's property on the instance itself, Vue does not render the property as an attribute in the DOM.
Here is a minimal reproduction of the issue outside of Ionic Vue: https:... | 2021-05-18T20:47:50 | 2021-05-18T21:08:22 | {} | NONE |
vuejs | core | 845,022,894 | 3,803 | edison1105 | see https://v3.vuejs.org/api/application-config.html#iscustomelement | 2021-05-20T11:49:08 | 2021-05-20T11:49:08 | {} | MEMBER |
vuejs | core | 845,837,435 | 3,809 | xinchao-zhang | deep data change does not **trigger** watch, but it is still a data change (e.g. `shallowReactiveState.age.number` is still modified). So if anyone tries to **pull** the data, he will see the 1000 rather than the original 99.
Then there is the scope of DOM update. There are optimizations built in so that Vue does n... | 2021-05-21T10:01:14 | 2021-05-21T10:01:14 | {
"+1": 3
} | NONE |
vuejs | core | 846,301,433 | 3,792 | liamdebeasi | Ok cool - makes sense to me. I think my concerns here are resolved. Thanks for all the help! | 2021-05-21T23:01:18 | 2021-05-21T23:01:18 | {} | NONE |
vuejs | core | 846,343,717 | 3,812 | hyf0 | > ```ts
> // incorrect array length
> arr = [];
> arr[MAX_VALID_ARRAY_LENGTH] = true;
>
> console.log(arr.length);
>
> if (arr.length === 0) {
> console.log('incorrect MAX_VALID_ARRAY_LENGTH');
> }
> ```
This looks like a correct array length to me. The arr.length should be `MAX_VALID_ARRAY_LENGTH` not 0. The val... | 2021-05-22T03:44:16 | 2021-05-22T03:46:27 | {} | CONTRIBUTOR |
vuejs | core | 846,481,246 | 3,811 | hearsay316 | 非常不好意思 ,因为我在国内 ,网络问题,代码没有提交成功 .
这个是npm serve 是有显示dom 和控制台输出
这个是 npm build
用live-server 打开http://127.0.0.1:8080/index.html
![image](https://user-images.githubusercontent.com/10139810/119244212-c9d0d5... | 2021-05-23T00:28:57 | 2021-05-23T00:28:57 | {} | NONE |
vuejs | core | 842,630,821 | 3,786 | germsb | @yyx990803 I don't really agree, sometimes it may be necessary to use preventdefault on a touch / mouse event to avoid side effects with the operating system. For example, the gif below shows accidental history triggering when passive is set to true on chromeOS, very annoying.
[![Imgur](https://i.imgur.com/pTbTgrkt.... | 2021-05-17T20:52:37 | 2021-05-17T20:56:26 | {
"+1": 1
} | NONE |
vuejs | core | 842,819,266 | 3,787 | HcySunYang | This is a minimized repro:
```js
const AsyncComp = defineAsyncComponent(() => new Promise((r) => {}))
const CompA = defineComponent({
render: () => h(AsyncComp)
})
const CompB = defineComponent({
render: () => 'foo'
})
createSSRApp({
setup() {
const comp = shallowRef(CompA)
return ()... | 2021-05-18T04:38:18 | 2021-05-18T04:38:18 | {} | MEMBER |
vuejs | core | 842,821,648 | 3,789 | flipkickmedia | :) | 2021-05-18T04:45:29 | 2021-05-18T04:45:29 | {} | NONE |
vuejs | core | 845,268,417 | 3,804 | Smrtnyk | you are complaining about vue 3.1.0 beta and in repro you are using vue 2 | 2021-05-20T16:26:59 | 2021-05-20T16:26:59 | {
"+1": 2
} | NONE |
vuejs | core | 845,661,380 | 2,138 | unbyte | @iheyunfei Without this patch, you can't even invoke any statement that executes Array.push in the render function, including `(el) =>arr.push(el)`, because it will trigger recursively rendering. | 2021-05-21T05:21:20 | 2021-05-21T05:21:20 | {} | CONTRIBUTOR |
vuejs | core | 845,683,434 | 2,364 | deepansh96 | Solved it.
I was testing my website in Firefox 48. Because I wanted my website to work in kaiOS browsers which run on firefox 48.
The packages I was using were written using ES6 syntax and firefox 48 doesn't support that. So I had to add those packages to a `transpileDependencies` array in my `vue.config.js` and it w... | 2021-05-21T06:12:41 | 2021-05-21T06:12:41 | {
"+1": 3
} | NONE |
vuejs | core | 846,292,053 | 3,792 | LinusBorg | According to [Web Component Best Practices](https://developers.google.com/web/fundamentals/web-components/best-practices#aim-to-keep-primitive-data-attributes-and-properties-in-sync,-reflecting-from-property-to-attribute,-and-vice-versa.) it's on the custom element implementation to ensure that DOM properties and eleme... | 2021-05-21T22:25:17 | 2021-05-21T22:32:22 | {} | MEMBER |
vuejs | core | 841,872,101 | 3,780 | posva | Please follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro or use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions. | 2021-05-16T20:20:17 | 2021-05-16T20:20:17 | {} | MEMBER |
vuejs | core | 838,577,089 | 3,759 | posva | See https://github.com/vuejs/rfcs/blob/script-setup-2/active-rfcs/0000-script-setup.md#closed-by-default | 2021-05-11T14:28:57 | 2021-05-11T14:28:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 842,323,997 | 3,432 | plehnen | > Closing as the original behavior being raised is by design. Whether we need a way to expose declared `emits` listeners should have its own thread.
so... is there already an own thread for this? | 2021-05-17T13:27:13 | 2021-05-17T13:27:13 | {} | NONE |
vuejs | core | 842,742,975 | 3,785 | edison1105 | duplicate of #3623 | 2021-05-18T00:58:20 | 2021-05-18T00:58:20 | {} | MEMBER |
vuejs | core | 844,965,233 | 3,800 | posva | Width must be in pixels, without the unit. This is a native behavior.
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-05-20T10:33:21 | 2021-05-20T10:33:21 | {} | MEMBER |
vuejs | core | 841,008,376 | 3,773 | credred | > You should use the `app.config.errorHandler` to register an error handling function for the first App:
>
> ```js
> try {
> const app = createApp({
> setup() {
> watchEffect(() => {
> throw ""
> }, { flush: 'post' })
> },
> render() {
> return 'asdf'
> }
> })... | 2021-05-14T05:07:00 | 2021-05-14T05:15:23 | {} | NONE |
vuejs | core | 842,378,039 | 3,784 | AnnaYuS | @HcySunYang My bad, all good 👍 | 2021-05-17T14:36:48 | 2021-05-17T14:36:48 | {} | NONE |
vuejs | core | 843,089,234 | 3,789 | pikax | dup https://github.com/vuejs/vue-next/pull/3776? | 2021-05-18T11:28:55 | 2021-05-18T11:28:55 | {} | MEMBER |
vuejs | core | 844,668,185 | 3,653 | mater1996 | ```html
<div :ref="setItemRef" v-for="i in 3" :key="i"></div>
```
```js
const itemRefs = reactive<any>([])
const setItemRef = (el: any) => {
if (el) {
itemRefs.push(el)
}
console.log(itemRefs.length)
}
return {
setItemRef
}
```
this also not work | 2021-05-20T04:00:13 | 2021-05-20T04:02:11 | {} | NONE |
vuejs | core | 846,393,907 | 3,813 | jacekkarczmarczyk | Then maybe `|| el.type === 'number'` could just be removed? | 2021-05-22T11:21:47 | 2021-05-22T11:21:47 | {} | CONTRIBUTOR |
vuejs | core | 846,495,263 | 3,812 | hyf0 | move to #3816 . | 2021-05-23T03:21:25 | 2021-05-23T03:21:25 | {} | CONTRIBUTOR |
vuejs | core | 846,496,244 | 3,810 | hyf0 | move to #3817. | 2021-05-23T03:36:24 | 2021-05-23T03:36:24 | {} | CONTRIBUTOR |
vuejs | core | 841,233,720 | 3,577 | ChrisRAra | I updated to Vue 3.0.11 and compiler-sfc 3.0.11 and still face the issue when I do app.use() | 2021-05-14T13:09:41 | 2021-05-14T13:09:41 | {} | NONE |
vuejs | core | 842,346,840 | 3,784 | AnnaYuS | @HcySunYang it's not exactly fixed yet. Only works with @posva's workaround | 2021-05-17T13:57:30 | 2021-05-17T13:57:30 | {} | NONE |
vuejs | core | 842,777,702 | 3,785 | HcySunYang | > duplicate of #3623
| 2021-05-18T02:31:24 | 2021-05-18T02:31:24 | {} | MEMBER |
vuejs | core | 843,027,793 | 3,790 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/issues/3001 | 2021-05-18T09:51:57 | 2021-05-18T09:51:57 | {} | MEMBER |
vuejs | core | 844,979,385 | 3,801 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/pull/3435, thanks. | 2021-05-20T10:54:22 | 2021-05-20T10:54:22 | {} | MEMBER |
vuejs | core | 845,694,660 | 2,730 | xinchao-zhang | > @asv1 I don't see anything in the docs to suggest that this is by design.
>
> Triggering a `flush: 'pre'` watcher during rendering is an awkward case. There is some wiggle room for deciding what the 'correct' behaviour should be but I don't think it makes sense to leave unflushed items in the queue
Absolutely, ... | 2021-05-21T06:33:26 | 2021-05-21T06:34:22 | {
"heart": 1
} | NONE |
vuejs | core | 846,293,700 | 3,792 | liamdebeasi | I work at the company that manages Stencil, so I can certainly verify with the team 😄 . Will post here when I have more info on that. Also wanted to note that the CodePen I posted in https://github.com/vuejs/vue-next/issues/3792#issuecomment-843549798 is just using a vanilla JS Web Component (no Stencil), so there may... | 2021-05-21T22:31:06 | 2021-05-21T22:31:06 | {} | NONE |
vuejs | core | 846,393,473 | 3,813 | edison1105 | > Where is this behavior described in docs?
There is no such thing, Vue2 also does not have this behavior. `.number` is recommended.
Maybe the PR I submitted is not needed because of the increased runtime overhead. | 2021-05-22T11:17:24 | 2021-05-22T11:17:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 846,498,164 | 3,815 | hyf0 | you could close this issue. duplicate with #2981. see fix #3791. | 2021-05-23T04:04:43 | 2021-05-23T04:04:43 | {} | CONTRIBUTOR |
vuejs | core | 840,116,818 | 3,730 | 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-12T21:45:08 | 2021-05-12T21:45:08 | {} | CONTRIBUTOR |
vuejs | core | 840,707,407 | 1,813 | m4heshd | Facing the same issue. Should `<teleport>` target be in the base HTML? Can't the target be inside a parent component?
Currently need to check if the target is mounted before the teleport is performed. | 2021-05-13T17:20:42 | 2021-05-13T17:42:00 | {} | NONE |
vuejs | core | 840,872,369 | 3,770 | yyx990803 | Some features require the compiler to opt-in to compat mode and `ref` in `v-for` is one of them. It seems you didn't configure the compiler to be in compat mode (at leasts in the sandbox).
See https://github.com/vuejs/vue-next/tree/master/packages/vue-compat#installation - check out the example configs in step 3. | 2021-05-13T22:31:01 | 2021-05-13T22:31:01 | {} | MEMBER |
vuejs | core | 840,935,207 | 3,024 | snwokenk | was getting this same issue with ethersjs Provider objects. wrapping it with markRaw before assignment solved the issue. solved the error | 2021-05-14T01:30:46 | 2021-05-14T01:30:46 | {
"+1": 9
} | NONE |
vuejs | core | 841,372,227 | 1,813 | AjaiKN | @m4heshd I think the `<teleport>` target is supposed to be outside the Vue app: see https://github.com/vuejs/vue-next/issues/992#issuecomment-616126089. I think maybe the docs could be more explicit about that, though.
> The target element cannot be a part of the same component... It needs to be outside of `<div id=... | 2021-05-14T16:56:10 | 2021-05-14T16:56:10 | {} | CONTRIBUTOR |
vuejs | core | 842,313,928 | 3,784 | HcySunYang | Has been fixed in https://github.com/vuejs/vue-next/commit/47da92146c9fb3fa6b1e250e064ca49b74d815e4 | 2021-05-17T13:13:42 | 2021-05-17T13:13:42 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.