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 | 1,247,260,593 | 5,584 | LinusBorg | @M1CK431 Hi. Yes, we have an inconsistencies here. The one originally reported in this issue is an edge case as really, it's an invalid use of v-model on a prop. As such, it does not have high priority.
The one you now reported sounds similar, yet would be a separate issue as the original one is related to a compile... | 2022-09-14T20:20:42 | 2022-09-14T20:24:04 | {} | MEMBER |
vuejs | core | 1,247,799,783 | 6,018 | dattn | I got exactly the same problem.
When splicing an element out of an reactive Array, computed values are triggered too early.
The item has been sucessfully removed, but the array.length is unchanged when the computed value recompution is triggered.
Which causes errors when looping over that array. | 2022-09-15T08:57:57 | 2022-09-15T08:57:57 | {} | NONE |
vuejs | core | 1,244,903,359 | 6,656 | moushicheng | Looks good when remove this comment in component
```html
<!-- info -->
```
I guess the reason is that the Transition can only have one node
[playground](https://sfc.vuejs.org/#eNqNU8tu4zAM/BVClzZAbSHuab1ukUX/YM+6OLay0cZ6QKKSQ5B/L2XZqdMXCugynOFQJKUz++NceYyS1awJnVcOIUiM7lkYpZ31CGcI+3YY7Omv3MEFdt5quKOMu6vixWq3noiSj... | 2022-09-13T05:06:21 | 2022-09-13T05:07:20 | {} | CONTRIBUTOR |
vuejs | core | 1,244,976,178 | 6,222 | midfar | > > chrome 105.0.5195.102 依然存在该问题
>
> 关浏览器什么事
我也觉得和浏览器无关，试了好几个vue旧版本，有的版本即使控制台不报错，KeepAlive的页面，多次切换或热更新显示也有异常 | 2022-09-13T06:51:22 | 2022-09-13T06:51:22 | {} | NONE |
vuejs | core | 1,245,248,153 | 4,443 | AlvaroBrasilia | Same issue here.
Does anyone have any solution? | 2022-09-13T11:01:53 | 2022-09-13T11:01:53 | {} | NONE |
vuejs | core | 1,245,315,043 | 6,616 | LinusBorg | Looking at it again, this issue is even mentioned here in the comment in line 66.
But I guess it does not work like intended because the type check is a bit all over the place:
* `typeof input.max // => 'string'`
* `typeof input.size // => 'number'`
* `typeof img.size // => 'undefined'` | 2022-09-13T12:03:05 | 2022-09-13T12:03:05 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,240,321,918 | 6,616 | ivanmem | @edison1105 What does "if it is specified" have to do with it? Vue doesn't allow you to not specify a size.
I want not to specify size. This attribute is optional! A warning in the console is bothering me.
... | 2022-09-08T07:16:08 | 2022-09-13T12:10:26 | {} | NONE |
vuejs | core | 1,246,105,357 | 6,657 | edison1105 | duplicate of https://github.com/vuejs/core/issues/5830 | 2022-09-14T01:03:39 | 2022-09-14T01:03:39 | {} | MEMBER |
vuejs | core | 1,242,947,165 | 6,643 | WalkAlone0325 | Yes, I also think so, if `vue` want to mount to the component instance, it must first `return { xx }`.
| 2022-09-11T11:47:22 | 2022-09-11T11:47:22 | {} | CONTRIBUTOR |
vuejs | core | 1,243,174,078 | 6,651 | shigma | Duplicate of #6639 | 2022-09-12T03:26:05 | 2022-09-12T03:26:05 | {} | CONTRIBUTOR |
vuejs | core | 1,245,446,753 | 5,940 | yusufkandemir | I believe `defineProps<{ foo: number | undefined }>` needs to be tested as well(_[in compileScript.spec.ts](https://github.com/vuejs/core/blob/769e5555f9d9004ce541613341652db859881570/packages/compiler-sfc/__tests__/compileScript.spec.ts#L774-L872)_) as the target issue(#5471) is mainly about it. | 2022-09-13T13:52:53 | 2022-09-13T13:52:53 | {} | NONE |
vuejs | core | 1,245,967,360 | 5,584 | fzn0x | > Ok guys (and @mileusna in particular) we've just faced this issue when releasing in production. We had a component which used a "mixed mode". We had a `<script setup>` with all the imports and a legacy `<script>` section with the old-style component code using `data()`. In development it worked flawlessy but in produ... | 2022-09-13T21:22:35 | 2022-09-13T21:22:35 | {} | NONE |
vuejs | core | 1,247,582,559 | 6,222 | chenhaihong | @midfar 贴下你的代码看下。 | 2022-09-15T04:57:58 | 2022-09-15T04:57:58 | {} | NONE |
vuejs | core | 1,249,222,191 | 6,677 | xcash | So.. here we state that mixing both styles is an antipattern.
I agree tha using `.value` is annoying but it is explicit when reading code. You have the ability to control the use of the reactive object or the value. | 2022-09-16T10:54:52 | 2022-09-16T10:54:52 | {} | NONE |
vuejs | core | 1,243,030,763 | 6,649 | LinusBorg | TS infers the required property of this plain object as `boolean`, not `true` - because other code could change that initial value.
Thats why the prop cant be correctly inferred.
Solution: use `as const` to tell TS this object wont change.
```ts
const props = {
// ...
} as const
``` | 2022-09-11T19:48:56 | 2022-09-11T19:49:33 | {} | MEMBER |
vuejs | core | 1,246,104,376 | 6,656 | edison1105 | duplicate of https://github.com/vuejs/core/pull/6238 | 2022-09-14T01:01:50 | 2022-09-14T01:01:50 | {} | MEMBER |
vuejs | core | 1,246,107,226 | 6,651 | edison1105 | @shigma PR welcome. | 2022-09-14T01:07:12 | 2022-09-14T01:07:12 | {} | MEMBER |
vuejs | core | 1,246,414,722 | 4,339 | wcldyx | 为什么这么好的提议不被支持呢 | 2022-09-14T08:22:40 | 2022-09-14T08:22:40 | {} | NONE |
vuejs | core | 1,247,117,317 | 4,294 | wynn-w | when this type will be used in other files.
```typescript
// types.ts
interface Test {
a: string;
}
// component.vue
<script lang="ts" setup>
import type { Test } from 'types';
type Props<T extends unkown> = {
[P in keyof T]: T[P];
}
defineProps<Props<Test>>()
</script>
// other.ts
impor... | 2022-09-14T17:57:03 | 2022-09-14T17:57:03 | {
"-1": 3
} | NONE |
vuejs | core | 1,249,152,444 | 6,678 | Dunqing | > It seems duplicate of #6652
Oh, I didn't see that, it looks simpler | 2022-09-16T09:38:13 | 2022-09-16T09:38:13 | {} | CONTRIBUTOR |
vuejs | core | 1,249,212,814 | 5,584 | xcash | > We also have official advises here:
>
> * https://vuejs.org/guide/introduction.html#api-styles
> * https://vuejs.org/guide/extras/composition-api-faq.html#trade-offs
>
> I guess this is enough, right? wink
Well, the docs states:
```
For learning purposes, go with the style that looks easier to understan... | 2022-09-16T10:43:34 | 2022-09-16T10:43:34 | {} | NONE |
vuejs | core | 1,242,943,425 | 6,633 | Dedicatus546 | @chenhaihong 一般用英语交流 | 2022-09-11T11:26:50 | 2022-09-11T11:26:50 | {} | NONE |
vuejs | core | 1,243,390,698 | 5,830 | vaban-ru | I have a similar error, created a repository to show it
https://github.com/vaban-ru/vue-tsc-reproduction-issue | 2022-09-12T08:27:15 | 2022-09-12T08:27:15 | {} | NONE |
vuejs | core | 1,243,413,801 | 6,633 | Justineo | I believe what you need is `app.component(name)` (without the second argument). But still, I think `app.provide` fits better to your use case for reasons I mentioned above. | 2022-09-12T08:48:20 | 2022-09-12T08:52:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,245,054,227 | 6,656 | ihengshuai | Flat when the node does not filter out the comment node
| 2022-09-13T08:11:25 | 2022-09-13T08:11:25 | {} | NONE |
vuejs | core | 1,245,780,750 | 4,662 | SavkaTaras | > We will solve this, it might take a few more days or weeks though.
Hi, could you please provide an estimated time on resolving this issue? We are loving developing custom elements using Vue, but are blocked by this issue.
Thank you so much,
Taras Savka | 2022-09-13T18:11:16 | 2022-09-13T18:11:16 | {
"+1": 1
} | NONE |
vuejs | core | 1,246,038,366 | 6,658 | qxygene | any fix yet? | 2022-09-13T23:08:28 | 2022-09-13T23:08:28 | {} | NONE |
vuejs | core | 1,247,709,943 | 6,222 | chenhaihong | @midfar 你别把壳组件集合放到响应式数据里，这里改一改。
https://github.com/midfar/vue3-element-admin/blob/7217ef5a567915789a0f3e6b8ad8bde76990bb14/src/layout/components/AppMain.vue#L21
你在你的 `tagsView` 模块里就把 `wrapperMap` 写成一个普通的变量好了，然后 export 出去。
在 `AppMain` 组件导入 `wrapperMap` 吧。
| 2022-09-15T07:45:35 | 2022-09-15T07:45:35 | {} | NONE |
vuejs | core | 1,248,254,266 | 6,669 | LittleSound | I think this is a bug, because reactive between child and parent components should be done through `props`, `emits` and other agreed-upon ways, so when I call `emits` in `watchEffect` I should not receive side effects from the parent component in the child component, they should be isolated by design intent.
This me... | 2022-09-15T15:22:27 | 2022-09-15T15:22:27 | {} | MEMBER |
vuejs | core | 1,248,700,598 | 6,677 | M1CK431 | Thanks for the detailed explanation of what happens under the hood, it's heavily interesting! :ok_hand:
TBH, I was not having the feeling of doing something "wrong", even after carefully read the documentation.
In fact, reading https://vuejs.org/guide/extras/composition-api-faq.html#can-i-use-both-apis-together, I... | 2022-09-15T22:28:55 | 2022-09-15T22:28:55 | {
"+1": 1
} | NONE |
vuejs | core | 1,244,948,800 | 6,656 | GuoDoubleV | > Looks good when remove this comment in component
>
> ```
> <!-- info -->
> ```
>
> I guess the reason is that the Transition can only have one node [playground](https://sfc.vuejs.org/#eNqNU8tu4zAM/BVClzZAbSHuab1ukUX/YM+6OLay0cZ6QKKSQ5B/L2XZqdMXCugynOFQJKUz++NceYyS1awJnVcOIUiM7lkYpZ31CGcI+3YY7Omv3MEFdt5quKOMu... | 2022-09-13T06:16:30 | 2022-09-13T06:16:30 | {} | NONE |
vuejs | core | 1,237,956,837 | 5,458 | d0peCode | This changes would make possible building teleport and suspense with vite. Currently we have workaround (binding teleport component) which makes it ugly and difficult to unit test (stub not replacing binded teleport component in time). | 2022-09-06T10:20:09 | 2022-09-14T13:58:57 | {} | NONE |
vuejs | core | 1,249,220,796 | 5,584 | M1CK431 | @xcash take a look at #6677, that type of setup is unsupported in fact. Dev have to choose one single API per component.
I have take a long time to explain why it could be a good idea to start supporting it, but TBH I think its a lost cause, unfortunately.
Anyway we now have a clear statement and it's already a goo... | 2022-09-16T10:52:59 | 2022-09-16T10:52:59 | {} | NONE |
vuejs | core | 1,249,740,895 | 5,831 | PixsaOJ | > Is there any news on solving this error?
Call variable `primary` something else. | 2022-09-16T19:42:45 | 2022-09-16T19:42:45 | {} | NONE |
vuejs | core | 1,243,130,501 | 6,649 | Dedicatus546 | @LinusBorg Thanks, it work well. | 2022-09-12T02:08:38 | 2022-09-12T02:08:38 | {} | NONE |
vuejs | core | 1,243,299,452 | 5,657 | Aliuet | > I also had this issue only in prod mode. [vue3报错TypeError: Cannot read properties of null (reading 'insertBefore')](https://juejin.cn/post/7095997262878212104) helped me fix it.
>
> Before
>
> ```
> <el-table :columns="columns" :dataSource="dataSource">
> <template #default="{ row }">
> <span>{{ row.l... | 2022-09-12T07:00:03 | 2022-09-12T07:00:03 | {} | NONE |
vuejs | core | 1,245,051,250 | 6,656 | ihengshuai | The comment will be rendered into a COMMENT NODE，effect the transition of course
| 2022-09-13T08:08:37 | 2022-09-13T08:08:37 | {} | NONE |
vuejs | core | 1,247,094,403 | 6,638 | mmis1000 | It seems suspense only works with async setup instead of async component?
https://stackblitz.com/edit/github-fktkzl-bhp65u?file=src%2FApp.vue
If it changed to async setup, then everything works | 2022-09-14T17:36:12 | 2022-09-14T17:36:12 | {} | CONTRIBUTOR |
vuejs | core | 1,256,982,609 | 4,294 | Mon-ius | So, the typescript in Vue3.x is a fake concept;
I first found the `props` concept can work in Vue3.x along with `ts` that way, which make me feel like home at first glance;
For example, in foo.vue;
```typescript
import { defineProps } from 'vue'
interface Props {
foo: string;
bar?: number;
}
con... | 2022-09-24T14:30:09 | 2022-09-24T14:30:09 | {
"-1": 17
} | NONE |
vuejs | core | 1,257,881,927 | 6,757 | Amixx | I have played around with the provided example and here are some observations:
- the issue disappears with any of these changes:
- removing props definition;
- removing emit definition;
- swapping { ctx } definition with props or emit definitions;
- adding another definition.
- the source of the error ... | 2022-09-26T11:22:40 | 2022-09-26T11:23:22 | {} | NONE |
vuejs | core | 1,259,252,873 | 6,755 | n1c | Much appreciated Evan 🙏 | 2022-09-27T09:43:15 | 2022-09-27T09:43:15 | {} | NONE |
vuejs | core | 1,260,523,364 | 6,591 | yyx990803 | Looks like the simplified reproduction is a bit different from the original case, where there is a legit memory leak that is still present in 3.2.40. | 2022-09-28T07:51:59 | 2022-09-28T07:51:59 | {} | MEMBER |
vuejs | core | 1,259,185,321 | 6,573 | yyx990803 | Can't reproduce the issue with latest Vuetify anymore - is there anyone who's running into this but **not** using Vuetify? | 2022-09-27T08:46:17 | 2022-09-27T08:46:17 | {} | MEMBER |
vuejs | core | 1,259,297,874 | 2,279 | tylerrrkd | > This problem lost me an entire afternoon. I was trying the same in the vue 2 codepen for the same feature and it was working, so it ended up being a really frustrating day.
>
> It might help someone who will have the same problem in the future:
>
> Because I was iterating an array (json schema to generate input... | 2022-09-27T10:23:17 | 2022-09-27T11:10:16 | {
"+1": 1
} | NONE |
vuejs | core | 1,257,014,649 | 6,742 | Akryum | The compiler should probably generate
```js
_withDirectives(_createElementVNode("input", _mergeProps(attrs, {
"onUpdate:modelValue": _cache[0] || (_cache[0] = $event => ((msg).value = $event)),
onBlur: onBlur,
}, {
[_toHandlerKey(validateEvent)]: onValidateEvent
}, _toHandlers(listeners, true)), null, 16... | 2022-09-24T16:53:15 | 2022-09-24T16:53:15 | {} | MEMBER |
vuejs | core | 1,257,596,301 | 6,754 | LinusBorg | Functional components do not automatically inherit any attributes, that is left to the author. they do not have a component instance, they are just functions creating vdom. | 2022-09-26T07:28:17 | 2022-09-26T07:28:17 | {} | MEMBER |
vuejs | core | 1,258,855,457 | 6,762 | joisun | > It works fine without `v-animate`. see [playground](https://sfc.vuejs.org/#eNqtVE1v1DAQ/SuDT6m0cQrHNFsJiR4QQhzghjnkY/LROnZkO9ldRfvfmcTedClFXJqL7bHnvefxm8zs4zDwaUSWssyWphscWHTjADJXzV4wZwW7F6rrB20czGCw3oFWX/WoHFY7KHU/jOvskLuyDcNDXWPpdnQ6L103IZyhNroHwYhKsDuhSq2sg6JT1Rc8wX7BjQQ7Ho+C3WzbLjcNurCrRimXrXpUhKnVEjRo2+gGZqHggsW... | 2022-09-27T01:38:08 | 2022-09-27T01:38:08 | {} | NONE |
vuejs | core | 1,258,866,062 | 6,762 | joisun | > 
>
> What is ur expected?
this only trigger once while loaded page, the refresh funciton should call every time while the page scroll to the bottom. you can comment the line6 `bindKey.value=xxxx` to se... | 2022-09-27T01:59:29 | 2022-09-27T01:59:29 | {} | NONE |
vuejs | core | 1,259,206,510 | 6,659 | yyx990803 | https://github.com/vuejs/core/pull/4443#issuecomment-1259205410 | 2022-09-27T09:04:42 | 2022-09-27T09:04:42 | {} | MEMBER |
vuejs | core | 1,259,213,080 | 6,664 | yyx990803 | I think I used an array just for consistency with other properties on `RootNode`, but I agree a Set would be better. Open to a PR to refactor it. | 2022-09-27T09:10:03 | 2022-09-27T09:10:03 | {} | MEMBER |
vuejs | core | 1,262,160,865 | 4,294 | paddotk | @Mon-ius The entire discussion is about just that. | 2022-09-29T11:44:22 | 2022-09-29T11:44:22 | {
"laugh": 15
} | NONE |
vuejs | core | 1,263,021,446 | 4,745 | baoxianggao | 
用的nuxt2开发项目，项目代码已经没有::v-deep和>>>语法了，应该是第三方库存在的问题，每次启动编译很长时间都花在打印这个warn上了，有时候甚至会编译超时，希望官方后面能够优化一下这个提示！
本地开发的话，可以直接注释掉图片对应文件对应的代码即可解决，不过每次重新下载一次都需要重新修改一下，线上因... | 2022-09-30T02:11:27 | 2022-09-30T02:11:27 | {} | NONE |
vuejs | core | 1,257,090,433 | 6,573 | timolson | > Same problem here. Does anyone have any solution?
Our project's only solution so far has been to pin the version to 3.2.37 :(
Can anyone confirm that this is merely a manifestation of #6659 ? If so, then that's p4 with a pending fix which would be great.
This bug is literally show-stopping, site-breaking f... | 2022-09-25T00:30:19 | 2022-09-25T00:34:39 | {} | NONE |
vuejs | core | 1,258,431,959 | 6,760 | LinusBorg | you can simply await one tick with `await nextTick()`. That ensures that everything being mounted in the current render cycle has been mounted properly.
```js
onMounted(async () => {
await nextTick()
props.parentRef // will not be defined
})
```
An alternative would be to not use a lifecycle hook and ins... | 2022-09-26T18:19:46 | 2022-09-26T18:19:46 | {} | MEMBER |
vuejs | core | 1,258,851,095 | 6,762 | edison1105 | It works fine without `v-animate`. see [playground](https://sfc.vuejs.org/#eNqtVE1v1DAQ/SuDT6m0cQrHNFsJiR4QQhzghjnkY/LROnZkO9ldRfvfmcTedClFXJqL7bHnvefxm8zs4zDwaUSWssyWphscWHTjADJXzV4wZwW7F6rrB20czGCw3oFWX/WoHFY7KHU/jOvskLuyDcNDXWPpdnQ6L103IZyhNroHwYhKsDuhSq2sg6JT1Rc8wX7BjQQ7Ho+C3WzbLjcNurCrRimXrXpUhKnVEjRo2+gGZqHggsWnX... | 2022-09-27T01:29:48 | 2022-09-27T01:29:48 | {} | MEMBER |
vuejs | core | 1,258,864,800 | 6,762 | edison1105 | 
What is ur expected?
| 2022-09-27T01:56:37 | 2022-09-27T01:56:37 | {} | MEMBER |
vuejs | core | 1,257,746,148 | 6,755 | woganmay | The bundlers are lowercasing keys they don't recognize:
By adding viewBox to the propsToAttrMap const in all the renderers, the toLowerCase() is skipped and you get the output you need:
![image](https:... | 2022-09-26T09:22:43 | 2022-09-26T09:22:43 | {} | NONE |
vuejs | core | 1,258,281,251 | 6,758 | woai3c | Here is the correct usage:
```vue
// App.vue
<script setup>
import { ref } from 'vue'
import Comp from "./Comp.vue"
const msg = ref('Hello World!')
const onRenderClick = e=>{
console.log(1)
}
</script>
<template>
<div>
<Comp @renderClick="onRenderClick"/>
</div>
</template>
```
```vue... | 2022-09-26T16:09:54 | 2022-09-26T16:09:54 | {} | NONE |
vuejs | core | 1,258,906,736 | 6,102 | techbirds | hi @LinusBorg , Do you have time to help review this pr? | 2022-09-27T03:05:03 | 2022-09-27T03:05:03 | {} | NONE |
vuejs | core | 1,259,205,410 | 4,443 | yyx990803 | Closing because this fix does not address the underlying issue.
Detailed explanation:
Directives are a template-only feature. Vue's directive handling code paths all assume that directives on vnodes are generated from the template by the compiler. That is to say, there should not be cases where the same vnode's p... | 2022-09-27T09:03:48 | 2022-09-27T09:04:19 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,259,358,116 | 6,222 | Geniusning | 官方还没有解决方案么 | 2022-09-27T11:23:39 | 2022-09-27T11:23:39 | {} | NONE |
vuejs | core | 1,261,063,726 | 6,770 | derdem | got it, thank you 😄 | 2022-09-28T15:13:59 | 2022-09-28T15:13:59 | {} | NONE |
vuejs | core | 1,258,221,448 | 6,759 | LinusBorg | > When the parent created lifecycle hook has an asynchronous call, the child component is still created and rendered before the parent's lifecycle hook is finished.
Thats how it works, yes. This is not a bug. Its how it works.
> As in Vue 2, I would expect the child components to not be rendered or created until ... | 2022-09-26T15:31:13 | 2022-09-26T15:53:57 | {} | MEMBER |
vuejs | core | 1,260,540,424 | 6,591 | yyx990803 | More investigation: the leak in the original repro is actually caused by the devtools. There is no leak in production. | 2022-09-28T08:07:46 | 2022-09-28T08:07:46 | {} | MEMBER |
vuejs | core | 1,261,640,908 | 5,657 | an501920078 | Development and production are not unified
![C99E1221-A137-4a97-9AFC-77E3FB9F7A98](https://user-images.githubusercontent.com/45625953/192919415-0170c686-8d75-4900-9fc7-fee500a... | 2022-09-29T01:43:58 | 2022-09-29T01:43:58 | {} | NONE |
vuejs | core | 1,262,515,746 | 6,757 | shengxinjing | [preview url](https://deploy-preview-6778--vue-sfc-playground.netlify.app/#eNptUE1PwzAM/StWLu0k0t4YKtskhDhwgjvh0GXuyGg+lLgbVdX/jrtB2QGf8vye/Zw3iIcQimOHohKrpKMJBAmpCxvljA0+EgywR3rsYkRHzy5R7TTCCE30FjKezJRTTntmWKrpi7n1PyP54kY5OFeIPiQW7bAxDl8nlA+/JIAhtBVcNQCoD1jBy/aAmuY1U/GKumupgnwB6w3kw/hnAzDO76s2WkOz+RODlL9lujX6M3tf3Cu3K... | 2022-09-29T16:24:42 | 2022-09-30T01:05:14 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,257,190,407 | 6,573 | Zehir | Yes @KaelWD I was using Vuetify, I updated vue to 3.2.39 and I don't have issues with Vuetify 3.0.0-beta.11 but I think I should keep this issue open in case not everybody is using Vuetify too. | 2022-09-25T13:05:36 | 2022-09-25T13:05:36 | {} | NONE |
vuejs | core | 1,259,206,616 | 6,573 | yyx990803 | https://github.com/vuejs/core/pull/4443#issuecomment-1259205410 | 2022-09-27T09:04:47 | 2022-09-27T09:04:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,259,231,173 | 6,669 | yyx990803 | This is not a bug. `watchEffect` by definition tracks during its sync operation.
If you want safe, non-tracking side effects, use `watch` with a callback - it explicitly separates the "tracking" and the "side effects" - pretty much designed for this case. | 2022-09-27T09:24:11 | 2022-09-27T09:24:11 | {} | MEMBER |
vuejs | core | 1,260,094,071 | 6,467 | mefcorvi | Hello, any progress with this PR? Need any help? | 2022-09-27T21:54:36 | 2022-09-27T21:54:36 | {} | CONTRIBUTOR |
vuejs | core | 1,260,328,041 | 6,602 | yyx990803 | The root cause is that `@vue/compat` did not list its own dependencies, so it was resolving to a hoisted & newer version of `estree-walker` that doesn't have CJS build. | 2022-09-28T03:06:43 | 2022-09-28T03:06:43 | {} | MEMBER |
vuejs | core | 1,260,726,873 | 4,512 | wvffle | Over a year has passed since this PR got created :/ Merging it would help to really simplify our project :) | 2022-09-28T10:47:48 | 2022-09-28T10:47:48 | {
"+1": 1
} | NONE |
vuejs | core | 1,261,175,898 | 6,591 | Akryum | @michaelperel What your are describing is exactly what @yyx990803 said in the previous comment:
| 2022-09-28T16:44:58 | 2022-09-28T16:44:58 | {} | MEMBER |
vuejs | core | 1,261,288,464 | 6,771 | LinusBorg | The linked MDN page documents the HTML element's attributes, and it doesn't have a text *attribute*
it does have a text *property* documented here, for its DOM interface: https://developer.mozilla.org/en-US/docs/Web/API/HTMLAnchorElement
But yeah, agreed, it's an odd one that I also didn't know about until a coup... | 2022-09-28T18:07:13 | 2022-09-28T18:07:13 | {} | MEMBER |
vuejs | core | 1,261,618,390 | 6,766 | ycmjason | @yyx990803 understood.
Perhaps at least we can deal with generics that extend primitive types?
https://stackblitz.com/edit/vitejs-vite-hmunsf?file=src%2Fmain.ts
E.g.
```ts
const f = <T extends string>(someT: T) => {
const t = ref(someT);
t.value = someT; // expected no error
};
const g = <T exten... | 2022-09-29T00:58:01 | 2022-09-29T00:58:07 | {} | CONTRIBUTOR |
vuejs | core | 1,238,845,803 | 6,506 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a28411427860032781fd5239bd77383e38b8ebf5 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-09-07T02:46:55 | 2022-09-29T05:05:39 | {} | NONE |
vuejs | core | 1,262,105,072 | 6,774 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | dc4fc13aa600e199d906136bc65c29d2e5e3186a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-09-29T10:48:07 | 2022-09-29T10:48:07 | {} | NONE |
vuejs | core | 1,262,105,609 | 6,774 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | dc4fc13aa600e199d906136bc65c29d2e5e3186a |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-09-29T10:48:39 | 2022-09-29T10:48:39 | {} | NONE |
vuejs | core | 1,258,859,270 | 6,763 | huzedong2015 | Why global components cannot be resolved | 2022-09-27T01:45:22 | 2022-09-27T01:45:22 | {} | NONE |
vuejs | core | 1,259,926,241 | 5,584 | lucassimines | > I had a similar issue recently, the workaround I went with was creating a computed with a get and set. Passing the get to model and having the set emit the update.
>
> ```js
> const value = computed({
> get() {
> return props.modelValue;
> },
> set(value) {
> emit("update:modelValue", value);
... | 2022-09-27T18:59:57 | 2022-09-27T18:59:57 | {
"+1": 2
} | NONE |
vuejs | core | 1,260,718,212 | 6,767 | LinusBorg | Repeoduction missing. | 2022-09-28T10:39:12 | 2022-09-28T10:39:12 | {} | MEMBER |
vuejs | core | 1,256,583,705 | 4,745 | jeremyabraham7 | Maybe this will help someone resolve this issue in larger code bases. We made the changes above to use `:deep() { ... }` and did so using regex find/replace
Find: `::v-deep (.*?) \{`
Replace `:deep($1) {`
And for any that are strung together:
Find: `::v-deep (.*?),`
Replace `:deep($1),` | 2022-09-23T19:15:47 | 2022-09-23T19:15:47 | {
"+1": 4,
"heart": 3,
"hooray": 1,
"rocket": 2
} | NONE |
vuejs | core | 1,257,386,908 | 6,745 | jonaskuske | There are two issues at play here:
1. Components used in `<TransitionGroup>` break if they don't have a single-element root but render a Fragment (multiple root nodes). This is currently not documented for `<TransitionGroup>`, only for `<Transition>`:
![image](https://user-images.githubusercontent.com/30421456... | 2022-09-26T02:17:04 | 2022-09-26T03:43:33 | {
"+1": 4
} | CONTRIBUTOR |
vuejs | core | 1,257,197,868 | 6,714 | baiwusanyu-c | wdyt？ @yyx990803 😂 | 2022-09-25T13:46:11 | 2022-09-27T13:08:56 | {} | MEMBER |
vuejs | core | 1,260,934,943 | 3,921 | hxgqh | vue 2.7 with vite in production mode also fails.
reproduction: https://github.com/hxgqh/vite_vue2.7
visit: http://localhost:28847/#/TestVbind | 2022-09-28T13:41:39 | 2022-09-28T13:41:39 | {} | NONE |
vuejs | core | 1,261,098,713 | 6,591 | michaelperel | @yyx990803 I believe the memory leak still exists, in prod, in [the original case](https://sfc.vuejs.org/#eNrlVMGO0zAQ/ZVROLQrNXHpFoRCW8qBAxIHDohTLmnipqaJbdlOl6rqv/OcNGmyu0LcuUSemTfz/GbGuQSftY5ONQ/iYGUzI7SjMpXFOgmcTQKy3NV6k0hRaWUcXShTla4dz2dk+J6utDeqogkKTHrQ97Tg39Kzqt0tGrG7y3PdoV8q7c4+2CN7zw2YyH0tMyeUJKeKouQ/BX+aPtAlkU... | 2022-09-28T15:40:26 | 2022-09-28T15:41:46 | {} | NONE |
vuejs | core | 1,261,608,589 | 6,768 | yyx990803 | See https://github.com/microsoft/TypeScript/issues/42873
Not really an issue that Vue can fix, since we do have correct dependency relationships between the packages.
But if you are trying to emit types for your Vue components, you should use [vue-tsc](https://github.com/johnsoncodehk/vue-tsc) instead (this is wh... | 2022-09-29T00:41:08 | 2022-09-29T00:41:08 | {} | MEMBER |
vuejs | core | 1,263,047,507 | 6,779 | baiwusanyu-c | I don't know if you have the Google Chrome plugin 'Vue.js devtools' installed, if you have it, try turning it off to see if the problem persists. Because I was getting an error from 'Vue.js devtools' when I was trying to locate the problem, when I turned it off, the problem went away and everything worked fine. This is... | 2022-09-30T03:02:08 | 2022-09-30T03:02:08 | {} | MEMBER |
vuejs | core | 1,263,082,992 | 6,784 | baiwusanyu-c | 这有什么问题吗？shallowReactive 只会对对象第一层做响应式化处理，而 reactive 则会根据你访问的 key 是否为对象递归调用 reactvie 再次做响应式处理，你的例子中把一个 reactive 赋值到 b 上，不就是手动给 b 的值做了一次响应式处理？然后在 effect 中访问被收集，赋值时又被触发 | 2022-09-30T04:17:40 | 2022-09-30T04:18:16 | {} | MEMBER |
vuejs | core | 1,257,122,066 | 6,724 | huifer | @LinusBorg | 2022-09-25T05:12:47 | 2022-09-25T05:12:47 | {} | NONE |
vuejs | core | 1,258,921,275 | 6,763 | huzedong2015 | > Manually calling `render` creates a tree that doesn't belong to the current app instance, so it can't resolve components registered under the app's scope.
Then how should I deal with this problem | 2022-09-27T03:29:20 | 2022-09-27T03:29:20 | {} | NONE |
vuejs | core | 1,260,310,981 | 6,660 | yyx990803 | Thanks for the PR, sorry I didn't notice it when pushing 8963c550 - I'm merging this for the unit test.
Regarding the return type - the return value is `undefined` when the slots are SSR-compiled. In SSR mode the slots have two branches based on whether the child component consuming the slots is also SSR-compiled or... | 2022-09-28T02:35:43 | 2022-09-28T02:35:43 | {} | MEMBER |
vuejs | core | 1,260,416,913 | 6,602 | cexbrayat | @yyx990803 @sheremet-va I bumped VTU to Vue v3.2.40 and tried the latest vitest release, and the issue is still there https://github.com/vuejs/test-utils/actions/runs/3141055322/jobs/5103078070 | 2022-09-28T05:44:38 | 2022-09-28T05:44:38 | {} | MEMBER |
vuejs | core | 1,261,023,757 | 6,770 | derdem | out of curiosity, is the need for `defineExpose` intended or a limitation of the `script setup` syntax? | 2022-09-28T14:45:34 | 2022-09-28T14:45:34 | {} | NONE |
vuejs | core | 1,261,173,952 | 6,591 | Akryum | @michaelperel The devtools are enabled on the SFC playground even in production mode. | 2022-09-28T16:43:09 | 2022-09-28T16:43:09 | {} | MEMBER |
vuejs | core | 1,257,174,052 | 6,747 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 63eaaf3987a5671e5e1aa1c967de955538a9643c |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-09-25T11:30:55 | 2022-09-25T11:30:55 | {} | NONE |
vuejs | core | 1,257,519,417 | 6,751 | LinusBorg | This is expected behavior. | 2022-09-26T06:00:15 | 2022-09-26T06:00:15 | {} | MEMBER |
vuejs | core | 1,260,524,602 | 6,688 | edison1105 | I feel this PR is necessary though ##6669 is closed. | 2022-09-28T07:53:14 | 2022-09-28T07:53:14 | {} | MEMBER |
vuejs | core | 1,259,161,408 | 6,591 | yyx990803 | Update: the fix only addresses the simplified cases [here](https://github.com/vuejs/core/issues/6591#issuecomment-1237662316) and [here](https://github.com/vuejs/core/issues/6591#issuecomment-1242642481).
---
This is fixed in https://github.com/vuejs/core/commit/fc5bdb36ed429d6c3c956f373206ce75467adaf3
Some no... | 2022-09-27T08:25:38 | 2022-09-28T07:55:23 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,261,226,452 | 6,771 | LinusBorg | This is a weird/funny edge case. The explanation is in the fact that Vue generally prefers to set values through element properties rather than element attributes. And anchor elements do have a `text`*property* which you can use to get or set the text of an anchor:
https://www.w3schools.com/jsref/prop_anchor_text.as... | 2022-09-28T17:23:59 | 2022-09-28T17:24:30 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.