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 | 901,154,925 | 4,378 | ShroXd | > Upgrade the node version to v16.7.0, The test cases can be passed.
>
> For details, see:
> https://nodejs.org/dist/latest-v16.x/docs/api/webstreams.html#webstreams_web_streams_api
It works, Really thank you!
I forgot to check the doc of node, maybe we can add a code comment here? :thinking: | 2021-08-18T14:18:48 | 2021-08-18T14:18:48 | {} | CONTRIBUTOR |
vuejs | core | 901,169,051 | 1,791 | CyberAP | I am using `serverCacheKey` extensively in Vue 2 and I really hope that the caching interface would support stream piping as well as returning just strings. This siginifcantly boosts app performance for streaming rendering if you're caching large html chunks and don't want to deal with unnecessary IO from copying strin... | 2021-08-18T14:36:17 | 2021-08-18T14:36:36 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 901,710,014 | 4,387 | ygj6 | @Iongtao The discussion [#1865](https://github.com/vuejs/vue-next/issues/1865) could help you? | 2021-08-19T08:19:25 | 2021-08-19T08:19:25 | {} | MEMBER |
vuejs | core | 901,740,086 | 4,387 | Iongtao | > @Iongtao The discussion [#1865](https://github.com/vuejs/vue-next/issues/1865) could help you?
我看过了， 但我不太了解这个key该如何使用，官方文档中没有提到component的key这个属性 | 2021-08-19T09:03:15 | 2021-08-19T09:03:15 | {} | NONE |
vuejs | core | 902,387,852 | 4,380 | Bigfish8 | > This shared function `toNumber()` is also used in other places like `v-model` so I don't think it's a good idea to change its behavior
Thanks, I just notice that the Inconsistent between the PR and the docs.
`This is often useful, because even with type="number", the value of HTML input elements always returns ... | 2021-08-20T02:43:53 | 2021-08-20T02:43:53 | {} | CONTRIBUTOR |
vuejs | core | 902,423,360 | 4,395 | lidlanca | https://github.com/vuejs/vue-next/issues/4376 | 2021-08-20T04:32:24 | 2021-08-20T04:32:24 | {} | CONTRIBUTOR |
vuejs | core | 902,476,626 | 4,376 | Bigfish8 | > This is mentioned in the RFC
[https://github.com/vuejs/rfcs/blob/script-setup/active-rfcs/0000-script-setup.md](url)
It seems the condition is not mentioned in the RFC.
Do I find the right place? | 2021-08-20T06:55:55 | 2021-08-20T06:55:55 | {} | CONTRIBUTOR |
vuejs | core | 900,079,479 | 4,283 | posva | I don't think this is a bug because extending `Object.prototype` should be avoided at all costs. It will break any library that iterates through keys with `for in`, which can be used for performance reasons. | 2021-08-17T07:57:56 | 2021-08-17T07:57:56 | {} | MEMBER |
vuejs | core | 900,431,369 | 4,283 | yyx990803 | This is not considered a bug because mutating `Object.prototype` is something you should **never** do in modern JavaScript. While Vue 3 can go out of its way to "support" it, it just incurs performance overhead on all other users (99.9%) for a case where there is no actual benefits.
https://github.com/vuejs/vue-next... | 2021-08-17T16:09:10 | 2021-08-17T16:10:18 | {} | MEMBER |
vuejs | core | 900,891,977 | 4,379 | LinusBorg | This is a deprecated element that you *really* should not use.
If you have to, configure it as a custom element like documented here (see compilerOptions.isCustomElement)
https://v3.vuejs.org/api/application-config.html#compileroptions | 2021-08-18T07:38:56 | 2021-08-18T07:38:56 | {} | MEMBER |
vuejs | core | 901,569,143 | 4,386 | ygj6 | Please open a new issue with a working link. | 2021-08-19T02:54:37 | 2021-08-19T02:54:37 | {} | MEMBER |
vuejs | core | 902,473,905 | 4,396 | posva | You need to mount the app on a parent element, the form element is not being processed by Vue because you are mounting **on it** instead of mounting in a wrapper element.
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-08-20T06:50:20 | 2021-08-20T06:50:20 | {} | MEMBER |
vuejs | core | 900,072,131 | 4,360 | zhangenming | > No that's not possible. WE would have to parse the JS AST for this, which is not something that would fit into the browser build.
sorry,
just use proxy can't Identify which one is spread operation? | 2021-08-17T07:45:27 | 2021-08-17T07:45:27 | {} | CONTRIBUTOR |
vuejs | core | 900,107,984 | 4,192 | chenjigeng | In the case of LazyUppercaseReactive, I've found that to get the effect you want, just change the guardReactiveProps code to look like this.
I think the reason is `object. assign` will trigger the getter ... | 2021-08-17T08:40:33 | 2021-08-17T08:40:33 | {} | NONE |
vuejs | core | 900,157,463 | 4,361 | Justineo | I created a benchmark for this: https://jsbench.me/1fksftarrz/1
Surprisingly, in Chrome and Safari, a plain `for` loop with `Object.keys` is much faster than the original implementation. But in Firefox it's about 60% slower. | 2021-08-17T09:54:52 | 2021-08-17T09:54:52 | {
"eyes": 1
} | MEMBER |
vuejs | core | 901,873,273 | 3,688 | chukwumaokere | > I'm having this very issue running vue 3.2.4
> package.json: "vue": "^3.2.4"
>
> ```
> <script>
> export default {
> ...
> setup(){
> ...
> let boardThemeLight = Themes.cpc_board_theme[0]; // Themes.cpc_board_theme is just a basic array ['#646372','#353340']
> let boardThemeDark = Themes.cpc_boar... | 2021-08-19T12:28:17 | 2021-08-19T12:28:47 | {} | NONE |
vuejs | core | 899,947,444 | 4,357 | HcySunYang | Please be clear about the meaning of the "initial value", there is no reason why it needs to be reactive. | 2021-08-17T02:33:56 | 2021-08-17T02:33:56 | {} | MEMBER |
vuejs | core | 900,127,791 | 4,358 | zhenzhenChange | 嗯嗯，好的，谢谢你。
也感谢 @ygj6 的付出。 | 2021-08-17T09:09:32 | 2021-08-17T09:09:32 | {} | NONE |
vuejs | core | 901,367,600 | 4,381 | posva | Duplicate of #4318 | 2021-08-18T19:19:35 | 2021-08-18T19:19:35 | {} | MEMBER |
vuejs | core | 901,528,301 | 4,383 | ygj6 | Fixed in https://github.com/vuejs/vue-next/commit/57f10812cc7f1e9f6c92736c36aba577943996fd | 2021-08-19T00:59:54 | 2021-08-19T01:32:28 | {} | MEMBER |
vuejs | core | 901,695,089 | 4,387 | Iongtao | > This works fine in a vite and vue/cli project. The codesandbox template you used doesn't seem to be up to date or doesn't handle HMR correctly
我的项目是vite构建的，在本地使用运行也一样会有这样的错误。 | 2021-08-19T07:58:02 | 2021-08-19T07:58:02 | {} | NONE |
vuejs | core | 901,746,573 | 2,220 | huafengThunder | > Hello, I realized a similar problem, and then tried to come to GitHub Issue to find a solution. I found it here, but it was not resolved. Finally, I figured out a way to solve this problem by myself, which is to customize the declaration file through the [module augmentation](https://www.typescriptlang.org/docs/handb... | 2021-08-19T09:11:39 | 2021-08-19T09:11:39 | {
"+1": 1
} | NONE |
vuejs | core | 902,027,585 | 4,390 | posva | Closing in favor of https://github.com/vuejs/vue-next/issues/4391 | 2021-08-19T15:51:03 | 2021-08-19T15:51:03 | {} | MEMBER |
vuejs | core | 902,597,955 | 4,402 | 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-08-20T10:29:58 | 2021-08-20T10:29:58 | {} | MEMBER |
vuejs | core | 900,430,368 | 4,361 | yyx990803 | It should be noted that the Vue 3 codebase uses `for...in` in **many places**, including the props diffing part. Only this change won't ensure correct behavior when `Object.prototype` has been mutated.
So I think it's best to just say: don't mutate `Object.prototype` when using Vue 3. | 2021-08-17T16:07:59 | 2021-08-17T16:07:59 | {
"+1": 2
} | MEMBER |
vuejs | core | 901,295,249 | 4,380 | Bigfish8 | > I don't think this is a real fix/solution for #4370.
>
> While it would improve problems in converting numbers, the real issue is that `_setAttrs` in the custom element class doesn't respect the component's prop type. it should not convert it to a number if the component expects a string.
Thanks for the review！... | 2021-08-18T17:27:02 | 2021-08-18T17:27:47 | {} | CONTRIBUTOR |
vuejs | core | 900,054,817 | 4,358 | zhenzhenChange | 这个问题貌似存在偶然性，我刚刚又跑了一遍第一张图 `Test1.vue` 居然又能正常解析了。。 | 2021-08-17T07:15:16 | 2021-08-17T07:18:44 | {} | NONE |
vuejs | core | 900,072,506 | 4,360 | LinusBorg | no | 2021-08-17T07:46:07 | 2021-08-17T07:46:07 | {} | MEMBER |
vuejs | core | 900,138,056 | 4,358 | ygj6 |
@HcySunYang @zhenzhenChange I can reproduce the problem stably in this project: https://gitee.com/zhenzhenChange/vue-next-issuse-4358, so I think it's a bug. | 2021-08-17T09:24:08 | 2021-08-17T09:24:08 | {
"+1": 2
} | MEMBER |
vuejs | core | 900,304,930 | 4,294 | yibird | 希望Vue团队能早日支持,现在使用vue3.2 defineProps()为Props定义单个单个类型还可以,若涉及到联合或交叉等复杂类型 defineProps就会编译错误, 这对于类型扩展是一件非常糟糕的事情 | 2021-08-17T13:36:06 | 2021-08-17T13:36:06 | {
"+1": 89,
"-1": 8
} | NONE |
vuejs | core | 901,690,335 | 4,387 | posva | This works fine in a vite and vue/cli project. The codesandbox template you used doesn't seem to be up to date or doesn't handle HMR correctly | 2021-08-19T07:50:38 | 2021-08-19T07:50:38 | {} | MEMBER |
vuejs | core | 901,839,051 | 4,390 | 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-08-19T11:32:31 | 2021-08-19T11:32:31 | {} | CONTRIBUTOR |
vuejs | core | 899,946,478 | 4,358 | HcySunYang | 给个最小重现的项目，可运行的。 | 2021-08-17T02:31:02 | 2021-08-17T02:31:02 | {} | MEMBER |
vuejs | core | 900,428,557 | 4,361 | yyx990803 | Looks like mutating `Object.prototype` de-optimizes for...in loops, since removing it leads to very different results: https://jsbench.me/f6ksg9174k/1 | 2021-08-17T16:05:52 | 2021-08-17T16:05:52 | {} | MEMBER |
vuejs | core | 900,788,703 | 4,331 | Bigfish8 | I changed the indentation of the previous test because of the separation between `describe('transform')` with `describe('errors')`.So it seems there are many changes. | 2021-08-18T03:41:29 | 2021-08-18T03:41:29 | {} | CONTRIBUTOR |
vuejs | core | 900,862,462 | 4,376 | lidlanca | export default `<script>` block, can not be after `<script setup>`
error
` ReferenceError: can't access lexical declaration '__default__' before initialization`
input:
```html
<template>
</template>
<script lang="ts" setup>
// do something
</script>
<script lang="ts">
import { defineCompo... | 2021-08-18T06:45:23 | 2021-08-18T06:47:06 | {} | CONTRIBUTOR |
vuejs | core | 901,587,533 | 1,697 | nVitius | I hate to comment on an older issue, especially one that is already closed. I came across this issue when searching for "vue teleport with transition". I didn't find many results or answers; I wanted to leave my solution here in case anyone else came across this.
For my use-case, I wanted to show an alert to the use... | 2021-08-19T03:50:33 | 2021-08-19T03:50:33 | {
"+1": 5,
"heart": 3,
"hooray": 2
} | NONE |
vuejs | core | 901,977,431 | 4,390 | SebastianSpeitel | I'm having the same issue and could provide a minimal example if needed. | 2021-08-19T14:46:22 | 2021-08-19T14:46:22 | {} | NONE |
vuejs | core | 961,174,716 | 4,889 | lockinmarv | > I am glad you spotted this, I was just about to do the PR myself. Saved me the trouble.
Yeah my code was wrong and the TS error showed me the typo. I was a bit surprised but here we go. 😄 | 2021-11-04T15:49:43 | 2021-11-04T15:49:43 | {} | CONTRIBUTOR |
vuejs | core | 961,273,146 | 4,902 | 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-11-04T17:41:57 | 2021-11-04T17:41:57 | {} | MEMBER |
vuejs | core | 961,576,074 | 4,895 | yyx990803 | See fafa7a10 and 7a5c7844
Sorry didn't see this earlier since I didn't check emails last week 😅 | 2021-11-05T02:19:18 | 2021-11-05T02:20:13 | {} | MEMBER |
vuejs | core | 962,400,359 | 4,903 | edison1105 | @sqal
this code not working because component should be a vnode not an vnode array.
```javascript
const array = () => [
h('div', 'foo'),
h('div', 'bar')
]
```
should change to
```javascript
const array = () => h(Fragment,null,[
h('div', 'foo'),
h('div', 'bar')
])
```
this code... | 2021-11-06T05:59:09 | 2021-11-06T05:59:09 | {} | MEMBER |
vuejs | core | 962,424,800 | 4,903 | sqal | @edison1105
> every item in children array must be a vnode
hmm but doesn't have to when using render function in plain JS? (check Comp.vue in my demo),. A little bit of inconsistency here, but if I have to filter out falsy values myself that's fine. | 2021-11-06T09:31:46 | 2021-11-06T09:31:46 | {} | CONTRIBUTOR |
vuejs | core | 962,925,815 | 4,915 | posva | Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org).
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.or... | 2021-11-08T08:38:54 | 2021-11-08T08:38:54 | {} | MEMBER |
vuejs | core | 963,030,544 | 4,916 | posva | Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org).
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.or... | 2021-11-08T10:52:20 | 2021-11-08T10:52:20 | {} | MEMBER |
vuejs | core | 964,735,222 | 4,891 | languanghao | @edison1105
I try to write a samll demo to reproduce but failed. Maybe I can send you my product url ? Please tell me your email.
PS: 看地区你也是中国的，用中文交流可以吗？ | 2021-11-10T02:44:59 | 2021-11-10T02:44:59 | {} | NONE |
vuejs | core | 965,349,187 | 4,928 | dmtkpv | I ran into this issue when displaying data from [TinyMCE](https://github.com/tinymce/tinymce)
Other WYSIWYG editors may also inset `<br />` as line break
| 2021-11-10T15:05:54 | 2021-11-10T15:05:54 | {} | NONE |
vuejs | core | 960,520,507 | 4,358 | edwardnyc | > > 我也遇到了类似这样的问题,一重启项目就解决了,头疼,经常需要重新run
>
> 最大问题是缺乏稳定复现的repro.😵
+ 1
以天为单位的稳定复现. =-= | 2021-11-04T07:37:56 | 2021-11-04T07:37:56 | {} | NONE |
vuejs | core | 960,918,062 | 2,457 | zt50tz | Thank you for solution!
But, now i get error ``Can't find variable: compileCache`` ;(
If i set `window.compileCache = {};` everything is fine, but i see it as dirty hack.
<img width="433" alt="Screenshot 2021-11-04 at 16 16 10" src="https://user-images.githubusercontent.com/33315115/140319984-83a44d35-6f38-4801-... | 2021-11-04T13:23:27 | 2021-11-04T13:23:27 | {} | NONE |
vuejs | core | 961,708,034 | 4,903 | LinusBorg | Seems like a bug, definitely. The new subtree is present in the instance's vnode, but DOM wasn't patched:
| 2021-11-05T08:26:11 | 2021-11-05T08:27:43 | {} | MEMBER |
vuejs | core | 962,712,412 | 4,897 | languanghao | > > 很快会有新版本发布，还是必须降级？（以及哪个版本？）
>
> Currently it is possible to explicitly pass a boolean value to prop. e.g:
>
> ```
> <Children
> :selectable="true"
> />
> ```
3.2.19可以 | 2021-11-08T00:23:51 | 2021-11-08T00:23:51 | {
"+1": 1
} | NONE |
vuejs | core | 962,982,667 | 4,917 | heart-er | OK，thanks, this is my demo repo, it will throws error when i use IIFE in script setup
https://github.com/heart-er/vue3-error-repo
@LinusBorg @yyx990803 | 2021-11-08T09:52:32 | 2021-11-08T10:08:30 | {} | NONE |
vuejs | core | 963,100,745 | 4,917 | LinusBorg | Okay, can reproduce it and also found a workaround/solution: a leading semicolon:
```html
<script setup>
;(() => {
console.log('----')
})()
</script>
```
It seems there's an issue with generated code that's being inserted before that IIFE which breaks ASI.
However, it's also a good practice to have a l... | 2021-11-08T12:24:39 | 2021-11-08T12:25:25 | {
"+1": 4
} | MEMBER |
vuejs | core | 964,640,709 | 4,662 | lucasantunes-ciandt | @raffobaffo would you mind sharing how did you extend it? I tried it here by basically cloning `/runtime-dom/src/apiCustomElement.ts` with your changes but got a lot of syntax error from TS. | 2021-11-09T23:34:25 | 2021-11-09T23:34:25 | {} | NONE |
vuejs | core | 964,757,241 | 4,891 | edison1105 | @languanghao
daiwei521@126.com | 2021-11-10T03:40:13 | 2021-11-10T03:40:13 | {} | MEMBER |
vuejs | core | 965,530,859 | 4,931 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/1503 | 2021-11-10T16:42:37 | 2021-11-10T16:42:37 | {
"+1": 1
} | MEMBER |
vuejs | core | 965,543,656 | 4,932 | posva | This is intended behavior because the value on the parent doesn't change from 45 so the child doesn't update again. You need to force the value on the input to constrain it.
| 2021-11-10T16:56:41 | 2021-11-10T16:56:41 | {} | MEMBER |
vuejs | core | 960,523,288 | 4,358 | Coderclc | 稍等一下,因为我是在vite+vue3的环境下遇到了这个问题,我先排除一下是否与vite有关 | 2021-11-04T07:44:33 | 2021-11-04T07:44:33 | {} | NONE |
vuejs | core | 960,555,554 | 4,358 | zhenzhenChange | 看来这个问题已经有越来越多的人出现了，我觉得我应该是首批发现这个`偶然性 Bug`的人，所以当时提了出来，并且做了大量的测试，但也因为是`偶然性`，就是有时候出现，有时候不出现，所以确实是真的很难复现，在第一次提供的那个仓库中确实是复现了，当时 @ygj6 也解决了这个问题，后续我也一致的认为完完全全搞定了之后（复现仓库也删了。。不过即使没删，现在估计也测试不出来），再过了一段时间，还是会出现，只不过那时候频率非常低，经常修改代码之后，经过了热更新，`Bug`又消失了，所以我也就没有反馈了。
---
我觉得我在这个问题上有一定的发言权：
1. 为什么说我觉得我应该是首批发现这个`偶然性 Bug`的人呢？
因为从`... | 2021-11-04T08:40:07 | 2021-11-04T08:42:23 | {
"+1": 3
} | NONE |
vuejs | core | 962,968,005 | 629 | PavelShishchits | @sh-mokong Technically we can, I'am just trying to find the most "vue" way to render components programmatically in vue 3. Thanks for your answer. | 2021-11-08T09:32:28 | 2021-11-08T09:32:28 | {} | NONE |
vuejs | core | 963,327,009 | 4,918 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4423 | 2021-11-08T16:26:13 | 2021-11-08T16:26:13 | {} | MEMBER |
vuejs | core | 966,361,372 | 4,935 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4783 | 2021-11-11T14:47:10 | 2021-11-11T14:47:10 | {} | MEMBER |
vuejs | core | 961,067,782 | 4,889 | WORMSS | I am glad you spotted this, I was just about to do the PR myself. Saved me the trouble. | 2021-11-04T14:35:33 | 2021-11-04T14:35:33 | {} | NONE |
vuejs | core | 961,269,416 | 4,903 | sqal | Just wanted to add that I have a use case for rendering an existing vnode in the template. I'm building a DataTable component where my api, for example returns a list of table headers. Each object contains a "render" function that returns already created vnode. Unfortunately, Dynamic component is the only "official" w... | 2021-11-04T17:36:51 | 2021-11-04T17:36:51 | {} | CONTRIBUTOR |
vuejs | core | 962,640,827 | 4,906 | lzm0x219 | Declare a component like this, props are props that default to the browser’s native tags. Props cannot get name and age...😟 It seems to be inconsistent with the expected behavior, maybe I misunderstood it? | 2021-11-07T16:26:54 | 2021-11-07T16:43:04 | {} | NONE |
vuejs | core | 962,879,762 | 4,891 | languanghao | @edison1105 I also find this problem in 'product' mode, but everything works fine in 'dev' mode.
From chrome F12, we can find `rv.value` has different value
product mode, need call `rv.value._.exposed.handleConfirm()`
?\/\//` is better. | 2021-11-09T03:58:52 | 2021-11-09T03:58:52 | {} | CONTRIBUTOR |
vuejs | core | 964,467,363 | 4,926 | 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).
---
Here you have a nice template: https://github.co... | 2021-11-09T19:29:32 | 2021-11-09T19:29:32 | {} | MEMBER |
vuejs | core | 965,647,925 | 2,291 | henribru | Are there any plans to fix this issue? The workaround works okay for your own watchers, but I'm running into this with watchers in external libraries as well, in which case I can't affect how they flush. | 2021-11-10T19:01:08 | 2021-11-10T19:01:08 | {
"+1": 3
} | NONE |
vuejs | core | 958,915,854 | 4,890 | zhangyuang | @posva yeah，i will remove window dependencies in next version，but many third party ui component depend on window property and the code maybe not be written in component lifecycle but component top.
Navigator also be mocked commonly. window.htmlelememt looks like a safe condition | 2021-11-03T10:58:30 | 2021-11-04T07:30:31 | {} | CONTRIBUTOR |
vuejs | core | 960,522,535 | 4,358 | ygj6 | > 以天为单位的稳定复现. =-=
你能提供一个例子吗？使用 [sfc.vuejs.org](https://sfc.vuejs.org/)、git、或者gitee。当然最好尽可能的小:smiley:
| 2021-11-04T07:42:50 | 2021-11-04T07:44:56 | {} | MEMBER |
vuejs | core | 960,813,005 | 2,457 | descire | use babel handle vue3 source to ES5，can solve the above problems:
```JavaScript
// vue.config.js
module.exports = {
transpileDependencies: [/@vue\/*/],
...
}
```
but in ios10.x create blank html，because Object.getOwnPropertyNames(Symbol) can enumerate 'arguments' and 'caller'
the browser threw an excep... | 2021-11-04T12:32:19 | 2021-11-04T12:32:19 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 961,572,986 | 4,895 | caozhong1996 | The deep reason for that is `pnpm-lock.yaml` not updated when release. | 2021-11-05T02:11:42 | 2021-11-05T02:11:42 | {} | CONTRIBUTOR |
vuejs | core | 961,750,068 | 2,084 | YowaiCoder | > Closed, tracking here [vuejs/rfcs#284](https://github.com/vuejs/rfcs/pull/284)
Any progress? | 2021-11-05T09:36:32 | 2021-11-05T09:36:32 | {} | NONE |
vuejs | core | 962,043,712 | 4,903 | sqal | @edison1105 while this issue is still open. Do you know why I also can't render a Fragment which may have falsy values as its children? Will your PR fix this case? [check example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IHsgaCwgRnJhZ21lbnQsIHJlZiB9IGZyb20gJ3Z1ZSdcbiAgaW1wb3J0IENvbXAgZnJvb... | 2021-11-05T16:36:03 | 2021-11-05T17:16:02 | {} | CONTRIBUTOR |
vuejs | core | 962,742,451 | 4,906 | mengxiong10 | > Declare a component like this, props are props that default to the browser’s native tags. Props cannot get name and age...😟 It seems to be inconsistent with the expected behavior, maybe I misunderstood it?
I think you should define props.
```jsx
interface TestProps {
name: string;
age?: number;
}
expo... | 2021-11-08T01:46:58 | 2021-11-08T01:46:58 | {} | NONE |
vuejs | core | 962,928,861 | 4,915 | RoosDev | Ok sorry, I'm gonna try to find which part of my code make this error. And I gonna had link of SFC . | 2021-11-08T08:43:36 | 2021-11-08T08:43:36 | {} | NONE |
vuejs | core | 962,951,766 | 4,917 | LinusBorg | If you only can reproduce it in a git repo, please share a git repo.
We can't debug what we can't reproduce reliably.
Issues without reproductions are closed. We can reopen the issue when you provide a runnable reproduction. | 2021-11-08T09:13:16 | 2021-11-08T09:13:16 | {} | MEMBER |
vuejs | core | 966,544,809 | 4,930 | LinusBorg | Currently, for template refs Vue relies on the presence of `instance.exposed` to decide wether this is a closed instance – requiring an `exposeProxy`– or a normal, open instance which exposes the normal `instance.proxy`.
This is usually fine, but becomes a problem with an async component like the one in this issue, ... | 2021-11-11T18:53:41 | 2021-11-11T19:00:36 | {
"+1": 3,
"hooray": 1
} | MEMBER |
vuejs | core | 960,668,613 | 4,896 | Bigfish8 | It is Intentional.It involves active update or passive update of components.
You can use object to aviod unnessary update.
[sfc.vuejs.org/](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgcmVhY3RpdmUgfSBmcm9tICd2dWUnXG5pbXBvcnQgQ29tcCBmcm9tICcuL0NvbXAudnVlJ1xuXG5jb25zdCBtc2cgPSByZWYoJ0h... | 2021-11-04T11:24:31 | 2021-11-04T11:24:31 | {} | CONTRIBUTOR |
vuejs | core | 961,739,570 | 4,903 | edison1105 | Actually, it's a bug. should not take fast path when dynamicChildren is empty.
the root cause is we doesn't track block here.
![image](https://user-images.githubusercontent.com/3705199/140494331-98e4c88e-... | 2021-11-05T09:19:39 | 2021-11-05T10:09:32 | {
"+1": 1
} | MEMBER |
vuejs | core | 963,107,304 | 4,917 | heart-er | OK, Thanks for the solution! | 2021-11-08T12:34:05 | 2021-11-08T12:34:05 | {} | NONE |
vuejs | core | 966,331,237 | 4,930 | languanghao | @edison1105 I tried that, but I do not think it's a good workaround.
As code below, `expose` method need invoke a var returned by a async method.
```
const props = defineProps<id: string>()
const recorder = await getRecorder(props.id)
const save = () => {
// post recorder to server
}
defineExpose({ rec... | 2021-11-11T14:08:51 | 2021-11-11T14:08:51 | {} | NONE |
vuejs | core | 960,519,497 | 4,358 | ygj6 | > 我也遇到了类似这样的问题,一重启项目就解决了,头疼,经常需要重新run
最大问题是缺乏稳定复现的repro.:dizzy_face: | 2021-11-04T07:35:29 | 2021-11-04T07:35:29 | {} | MEMBER |
vuejs | core | 961,038,529 | 4,901 | LinusBorg | For now, if you want to check for declared listeners, define them as `onX` props instead. Props starting with `on` followed by an uppercase letter are considered event listeners. | 2021-11-04T14:21:34 | 2021-11-04T14:21:34 | {} | MEMBER |
vuejs | core | 962,937,455 | 4,916 | nilmadhab | https://ibb.co/NnwYbZS
https://ibb.co/8KssmdT | 2021-11-08T08:56:07 | 2021-11-08T08:56:07 | {} | NONE |
vuejs | core | 963,241,389 | 4,917 | LinusBorg | @edison1105 Well, you need to add a semicolon after `defineExpose()` - that's just a requirement in JS. (A linter would likely warn you about such code as well.)
In your example you caused it yourself and can fix it yourself. In OP's example there's no previous code that would require a semicolon before compilation,... | 2021-11-08T14:57:24 | 2021-11-08T14:57:38 | {
"+1": 2
} | MEMBER |
vuejs | core | 963,868,953 | 4,921 | LinusBorg | Thinking about this a bit, I think something like that has been discussed previously. One of the issues with this approach is that it would then miss reactive data nested within the nonreactive data of `shallowReactive`:
```js
const obj = shallowReactive({
foo: {
bar: ref(0)
}
})
```
In the above ex... | 2021-11-09T07:02:50 | 2021-11-09T07:02:50 | {} | MEMBER |
vuejs | core | 965,559,859 | 4,932 | matanmatrix | thank you for the quick response! | 2021-11-10T17:14:41 | 2021-11-10T17:14:41 | {} | NONE |
vuejs | core | 966,701,805 | 4,662 | lucasantunes-ciandt | @raffobaffo I had only to change the <link> injection a little bit, since I may have multiple instances of the same Custom Element:
```
document.querySelectorAll(customElementName).forEach((element) => {
if (!element.shadowRoot) return;
const styleLink = document.createElement('link');
styleLink.setAttri... | 2021-11-11T23:37:47 | 2021-11-11T23:39:01 | {} | NONE |
vuejs | core | 961,627,648 | 4,896 | yyx990803 | I think this has been raised before and was marked as enhancement. TLDR: the current behavior ensures correctness in edge cases, especially when `$attrs` are involved (which are non-reactive). | 2021-11-05T04:56:46 | 2021-11-05T04:56:46 | {} | MEMBER |
vuejs | core | 961,724,995 | 4,897 | bodograumann | Not sure I want to incurr this debt. For posterity, this is how one could find the problematic props:
```shell
rg --multiline --glob "*.vue" "<[A-Z][^ \n>]*(\s+[a-z-:@]+=\"[^\"]*\")*\s+[a-z-]+\s*[ \n>]"
``` | 2021-11-05T08:56:28 | 2021-11-05T08:56:28 | {} | NONE |
vuejs | core | 962,441,811 | 4,910 | sudongyuer | I love vue,thanks a lot | 2021-11-06T12:05:28 | 2021-11-06T12:05:28 | {} | CONTRIBUTOR |
vuejs | core | 962,619,868 | 4,896 | edison1105 | duplicated of #1181 | 2021-11-07T14:24:01 | 2021-11-07T14:24:01 | {
"+1": 1
} | MEMBER |
vuejs | core | 962,645,964 | 4,836 | defaude | @posva I hope I've covered all functions that are exported from the reactivity module. What do you think?
Regarding the documentation for `proxyRefs` in `ref.ts`, I'm not 100% sure: https://github.com/vuejs/vue-next/pull/4836#issuecomment-949529584 | 2021-11-07T17:03:37 | 2021-11-07T17:08:40 | {} | CONTRIBUTOR |
vuejs | core | 963,715,148 | 4,917 | edison1105 | > In your example you caused it yourself and can fix it yourself. In OP's example there's no previous code that would require a semicolon before compilation, so it must likely be caused and solved by the compiler.
make sence. | 2021-11-09T00:59:10 | 2021-11-09T00:59:10 | {} | MEMBER |
vuejs | core | 965,914,499 | 4,927 | qmhc | @xiuxiuyifan This may lead to the same result. | 2021-11-11T01:39:31 | 2021-11-11T01:39:31 | {} | NONE |
vuejs | core | 966,208,338 | 4,891 | edison1105 | @languanghao there is a workaround, see https://github.com/vuejs/vue-next/issues/4930#issuecomment-966207743
| 2021-11-11T11:01:37 | 2021-11-11T11:01:37 | {} | MEMBER |
vuejs | core | 966,664,696 | 4,662 | lucasantunes-ciandt | Oopsie, actually this works! Thank you @raffobaffo!!
I was a bit confused about the meaning of `.ce.vue`, now I realize the extension is only a Custom Element **MODE** and not actually declaring those components as custom elements. This means I really should have them as `.ce.vue` in order for this to work, even aft... | 2021-11-11T22:16:53 | 2021-11-11T22:19:09 | {
"hooray": 1
} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.