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,008,359,401 | 5,227 | lidlanca | https://github.com/vuejs/rfcs/discussions/366
This RFC discussion was about fundamentally supporting toRaw for all vue reactive types.
the good old "escape hatch" statement/trap in docs was why I also opened a fruit less RFCdiscussion.
hope this save you the effort.
| 2022-01-09T19:28:10 | 2022-01-09T19:29:08 | {} | CONTRIBUTOR |
vuejs | core | 1,008,946,925 | 5,235 | LinusBorg | Well it seems like you already have a solution to your problem?
I don't think that making this a built-in default is desirable as it would be a difference to props defined without script-setup, and would also be untrue: you *can* mutate properties of objects received as props, and while we *recommend* against doing ... | 2022-01-10T14:51:03 | 2022-01-10T14:51:03 | {} | MEMBER |
vuejs | core | 1,008,995,816 | 4,294 | nborko | @LinusBorg That does work but negates the benefit of type checking the props using interfaces. Since the import in question is effectively a mixin, the props can be used in several places, and the interface may contain simple string literal types or something a lot more complex. It's helped me find a bunch of usage er... | 2022-01-10T15:29:56 | 2022-01-10T15:31:14 | {} | NONE |
vuejs | core | 1,006,469,843 | 4,294 | invokermain | This severely hinders wrapping 3rd party components via type script, as you have to copy and paste the interfaces into your SFC, greatly increasing maintenance burdens and destroying readability. Unless there is an easier way to do this?
```
<script setup lang="ts">
import { Datepicker, DatePickerProps } from 'vue... | 2022-01-06T10:48:54 | 2022-01-06T10:48:54 | {
"+1": 29,
"eyes": 5
} | NONE |
vuejs | core | 1,007,099,245 | 5,194 | macheteHot | @edison1105
Because is any how to use expectType test it ? | 2022-01-07T02:52:30 | 2022-01-07T02:52:30 | {} | NONE |
vuejs | core | 1,007,266,908 | 5,215 | zhangenming | I wonder if any of this is necessary
If so, I will continue | 2022-01-07T09:39:24 | 2022-01-07T09:39:24 | {} | CONTRIBUTOR |
vuejs | core | 1,007,886,932 | 5,224 | 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... | 2022-01-08T05:01:50 | 2022-01-08T05:01:50 | {} | CONTRIBUTOR |
vuejs | core | 1,008,221,864 | 5,166 | mesqueeb | @knightly-bot build this | 2022-01-09T03:27:34 | 2022-01-09T03:27:34 | {} | NONE |
vuejs | core | 1,003,303,993 | 5,190 | posva | Closing as this is a question and Thorsten provided you with the solution.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-12-31T08:11:42 | 2021-12-31T08:11:42 | {} | MEMBER |
vuejs | core | 1,004,219,042 | 4,707 | runxc1 | I commented on your post in the forum @soylomass but yes I think its the same bug in Vue. | 2022-01-03T16:48:18 | 2022-01-03T16:48:18 | {} | NONE |
vuejs | core | 1,005,704,049 | 5,208 | LinusBorg | Edit: I misinterpreted the screenshot as I didn't see that doctor profiler setup thing initially. That might make my point here moot:
~~Can you clarify what you see as a memory *leak* here? I only see increased memory *usage* which is not a *leak* and could be perfectly explained by the fact that in one case you cre... | 2022-01-05T13:53:10 | 2022-01-05T14:03:46 | {} | MEMBER |
vuejs | core | 1,006,266,870 | 5,193 | zhangenming |
const words = document.querySelector("body > pre").innerText.split('(unrecognized-spelling)')
.map(e=>e.split('Warning - `')[1]?.slice(0,-28).toLocaleLowerCase()).filter(e=>e)
const results = words.reduce((all,now)=>{
if(!all[now]) all[now] = 0
all[now]++
return all
}, {});
console.log(Object.e... | 2022-01-06T04:02:35 | 2022-01-06T04:02:35 | {} | CONTRIBUTOR |
vuejs | core | 1,006,708,912 | 3,596 | nfplee | Any update on this? Another idea would be to add a config option to ignore particular warnings. | 2022-01-06T16:05:51 | 2022-01-06T16:05:51 | {
"+1": 1
} | NONE |
vuejs | core | 1,007,064,515 | 5,194 | edison1105 | @macheteHot
Could you add a test case? | 2022-01-07T01:22:53 | 2022-01-07T01:22:53 | {} | MEMBER |
vuejs | core | 1,008,239,508 | 5,215 | caozhong1996 | > interal api
Update: should be type. | 2022-01-09T06:32:06 | 2022-01-09T06:32:06 | {} | CONTRIBUTOR |
vuejs | core | 1,009,014,300 | 4,294 | LinusBorg | Thanks for the response. I'm unsure about the verdict though.
Is using a props object with additional `PropType<>` annotation able to do what you need or is something still missing? Is that a route that gives you typings for all props in the way you need?
| 2022-01-10T15:50:12 | 2022-01-10T15:50:12 | {} | MEMBER |
vuejs | core | 1,003,234,306 | 5,191 | jw-foss | > Do I have to use Composition API in every component?
I don't think so, the way I think Composition API is that we can reduce duplication without using **Mixin**, especially for libraries.
> element calendar code Is this kind of code the best code practicing ?
I don't think so, at least for now, element-plus ... | 2021-12-31T01:29:18 | 2021-12-31T01:31:10 | {
"+1": 2
} | NONE |
vuejs | core | 1,003,278,450 | 5,186 | SakuOtonashi | ```typescript
function handleInit(outVal: string) {
return function (inVal: string) {
console.log('init', outVal, inVal)
}
}
function handleDestroy(outVal: string) {
return function (inVal: string) {
console.log('destroy', outVal, inVal)
}
}
```
```html
<AttrItem
v-if="currItem"
:ke... | 2021-12-31T05:56:51 | 2021-12-31T05:58:46 | {} | NONE |
vuejs | core | 1,000,933,007 | 5,167 | posva | Global is for a whole selector: https://v3.vuejs.org/api/sfc-style.html#style-scoped.
1. You don’t need global on that one
2. You should use a deep selector instead
3. That’s expected and actually the point of the global pseudo selector | 2021-12-24T21:15:23 | 2021-12-31T07:54:19 | {} | MEMBER |
vuejs | core | 1,003,518,540 | 5,148 | edison1105 | @posva
I found something. Maybe this is not the right fix. Just a hint here.
- `currentScopeId` is null when `createVNode` from `TopLevelAwait.vue` in `RouterView`.
- when suspense resolved, we will cl... | 2022-01-01T07:16:14 | 2022-01-01T07:33:39 | {
"+1": 2,
"rocket": 1
} | MEMBER |
vuejs | core | 1,003,753,048 | 4,707 | soylomass | Maybe related: https://forum.vuejs.org/t/emitsoptions-error-impossible-to-debug/125512
Solved replacing v-if with v-show | 2022-01-02T18:00:31 | 2022-01-02T18:00:31 | {
"+1": 1
} | NONE |
vuejs | core | 1,004,352,038 | 5,202 | sqal | More info, this is related to the v-model directive. If I replace `v-model` with `:checked` attribute in Switch.vue then it's fine
[Updated example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IHsgcmVmLCBjb21wdXRlZCwgd2F0Y2hFZmZlY3QgfSBmcm9tICd2dWUnXG4gIGltcG9ydCBSb3cgZnJvbSAnLi9Sb3cudnVlJ... | 2022-01-03T20:53:57 | 2022-01-03T20:54:38 | {} | CONTRIBUTOR |
vuejs | core | 1,005,196,495 | 5,202 | LinusBorg | Unfortunately it seems not to be as simple as that ... We will need to look deeper into other remedies | 2022-01-04T21:50:33 | 2022-01-04T21:50:33 | {} | MEMBER |
vuejs | core | 1,006,587,130 | 4,928 | yangliguo7 | hi~ I use v-html in SSR to render HTML content from TinyMCE，but I want to Lazy loading the img。like
```
the TinyMCE code
<img v-lazy='imgSrc' />
```
Can I parse this directive in v-html to implement this directive ？
@LinusBorg | 2022-01-06T13:20:48 | 2022-01-06T13:21:10 | {} | CONTRIBUTOR |
vuejs | core | 1,007,272,054 | 5,219 | caozhong1996 | > 直接传递onEvent和@event表现是一致的，都能够触发原生事件以及被注册为Vue自定义事件
不是这样的，请使用@vnodeMounted，直接使用onVnodeMounted作为prop名字会命中这个特殊逻辑从而导致错误
```ts
// onVnodeMounted
if (
!isAsyncWrapperVNode &&
(vnodeHook = props && props.onVnodeMounted)
) {
const scopedInitialVNode = initialVNode
queuePostRenderEffect(
() => invokeVN... | 2022-01-07T09:47:56 | 2022-01-07T09:47:56 | {} | CONTRIBUTOR |
vuejs | core | 1,007,501,063 | 5,220 | JohMun | Thank you for your quick response! | 2022-01-07T15:34:34 | 2022-01-07T15:34:34 | {} | NONE |
vuejs | core | 1,003,238,817 | 5,191 | caozhong1996 | 发表一下我的看法，我认为可以无脑使用 Composition API，原因有如下几点
* 目前 TS 成为了前端项目的标配，但是 Option 语法在设计之初就没有考虑到类型系统，使用起来要有很多奇奇怪怪的 hack。但是 Composition API 是基于函数的，天生对于类型友好。如果你想使用 TS 那么 Composition API 是你的不二选择。
* 关于逻辑复用，Composition API 相对于 Mixin 的优势你们都很清楚，所以重点是当没有逻辑复用的时候是不是应该使用 Option 语法？我认为还是应该使用 Composition API 。原因是因为它给你提供了更大的自由度，你可以抽象你的代码。我... | 2021-12-31T01:58:37 | 2021-12-31T01:58:37 | {
"+1": 5,
"eyes": 1,
"rocket": 1
} | CONTRIBUTOR |
vuejs | core | 1,003,305,019 | 5,178 | posva | Duplicate of https://github.com/vuejs/rfcs/pull/284 | 2021-12-31T08:16:24 | 2021-12-31T08:16:24 | {} | MEMBER |
vuejs | core | 1,005,852,295 | 5,211 | HcySunYang | Oh my, I thought I was in my fork repo.... | 2022-01-05T15:58:53 | 2022-01-05T15:58:53 | {} | MEMBER |
vuejs | core | 1,005,857,598 | 5,211 | HcySunYang | Closed, create a new one. | 2022-01-05T16:04:54 | 2022-01-05T16:04:54 | {} | MEMBER |
vuejs | core | 1,007,061,167 | 5,217 | edison1105 | maybe it's a duplicate of https://github.com/vuejs/vue-next/issues/4984
/cc @ygj6 | 2022-01-07T01:14:27 | 2022-01-07T08:14:10 | {} | MEMBER |
vuejs | core | 1,007,602,686 | 5,220 | sqal | @JohMun something like this can easily be implemented as a composable function [here is an example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IHsgcmVhY3RpdmUgfSBmcm9tICd2dWUnXG4gIGltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG4gIFxuICBjb25zdCBlID0gcmVhY3RpdmUoeyBmb286IHRydWUsIGJhcjogZmFsc2UgfSlc... | 2022-01-07T17:43:47 | 2022-01-07T17:43:47 | {
"+1": 1,
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 1,007,757,694 | 5,221 | LinusBorg | > is this intended?
Yes. See https://github.com/vuejs/vue-next/blob/master/CHANGELOG.md#3225-2021-12-12 | 2022-01-07T21:36:23 | 2022-01-07T21:37:29 | {} | MEMBER |
vuejs | core | 1,007,766,386 | 5,222 | oswaldofreitas | sure, I can do it. I used that service since it's one of the suggested in the Vue 3 [official docs](https://v3.vuejs.org/api/sfc-tooling.html#online-playgrounds) and it was really hard to find one that I could setup the vue compat plugin. I'll create a repo for it now and share as soon as I get it.
Before sharing th... | 2022-01-07T21:53:15 | 2022-01-07T21:53:15 | {} | NONE |
vuejs | core | 1,007,921,614 | 5,224 | LinusBorg | Normally, Refs are unwrapped in the template. But as you put it on a nonreactive object, this one is not. ou can (and have to) access it's value here as `foo.name.value`
```html
<template>
<div>
{{ foo.name.value }}
</div>
</template>
``` | 2022-01-08T09:21:58 | 2022-01-08T09:21:58 | {} | MEMBER |
vuejs | core | 1,008,621,957 | 4,997 | honghuangdc | if the component name is a variable, can this syntactic sugar support ? | 2022-01-10T08:06:21 | 2022-01-10T08:06:21 | {} | NONE |
vuejs | core | 1,003,393,260 | 5,148 | posva | Thanks @edison1105
~~Still [works on SFC Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IENvbXBvbmVudCBmcm9tICcuL0NvbXAudnVlJ1xuICBpbXBvcnQgUlZpZXcgZnJvbSAnLi9SVmlldy50cydcbiAgaW1wb3J0IHsgc2hhbGxvd1JlZiwgcHJvdmlkZSwgb25Nb3VudGVkLCBtYXJrUmF3IH0gZnJvbSAndnVlJ1xuICBcbiAgY29uc3Qgdmll... | 2021-12-31T14:48:03 | 2022-01-03T16:06:56 | {} | MEMBER |
vuejs | core | 1,004,795,922 | 5,196 | maritaria | The tampermonkey extension seems to inline the `@require`-ed script ahead of the user script, this produces the following total script:
<details>
<summary>The tampermonkey script (15k+ lines)</summary>
```javascript
(function(that){((context, fapply, console) => {with (context) {(module => {"use strict";try {... | 2022-01-04T13:08:33 | 2022-01-04T13:08:33 | {} | NONE |
vuejs | core | 1,166,261,303 | 6,179 | edison1105 | thanks for your PR, but there is another PR cover this case see https://github.com/vuejs/core/pull/5831 | 2022-06-25T11:22:40 | 2022-06-25T11:25:16 | {} | MEMBER |
vuejs | core | 1,169,716,915 | 6,198 | LinusBorg | the old value is the same as the new value because both are the same object that has been mutated.
If you would need to detect the actual differences, you would have to clone the object i.e. like this:
```js
watch(
() => _.cloneDeep(obj)
(newObj, oldObj) => { do something }
)
``` | 2022-06-29T09:00:11 | 2022-06-29T09:00:11 | {} | MEMBER |
vuejs | core | 1,172,024,350 | 2,562 | xsdream | > I found binding.instance work normal in development, but it turned out to be VNode in production. I use vite for building.
Finally solved? please | 2022-07-01T07:20:02 | 2022-07-01T07:20:02 | {} | NONE |
vuejs | core | 1,173,015,838 | 5,165 | mutolee | @yyx990803 尝试了3.2.37版本，这个问题依然存在，希望能在下个版本中看到它被修复了，虽然刷新一下浏览器，它就没问题了，但每次热更它总出现在控制台里，很烦人， #4387 #5073 都是这个问题，谢谢了。 | 2022-07-03T05:37:45 | 2022-07-03T05:37:45 | {} | NONE |
vuejs | core | 1,166,255,207 | 6,178 | LinusBorg | No, it's not. Hint: have a closer look at `DrawerBodyWrapper.tsx`' props | 2022-06-25T10:51:15 | 2022-06-25T10:51:15 | {} | MEMBER |
vuejs | core | 1,166,562,457 | 3,671 | K4T | > Vue2 + Composition API, it got the same problem in setup function
I had the same problem when I used incorrect import (automatically added by IDE):
```
import { onMounted } from '@vue/composition-api/dist/vue-composition-api.js'
```
Solution:
```
import { onMounted } from '@vue/composition-api'
``` | 2022-06-26T15:19:01 | 2022-06-26T15:19:01 | {
"+1": 4,
"eyes": 1
} | NONE |
vuejs | core | 1,166,659,262 | 6,180 | DanSweeney23 | I don't think you can really expect it to keep the same keys. You are deleting the vnodes with that v-if and creating new ones. Imagine every time you added something like `<div v-for="(item, index) of items" :key="index">` in an app, vnodes would identical keys. | 2022-06-26T22:10:22 | 2022-06-26T22:10:22 | {} | NONE |
vuejs | core | 1,166,781,123 | 6,018 | tangjinzhou | same issue https://sfc.vuejs.org/#eNp9kcFugzAMhl/FywUqpaBut4qiTdphb7DDsgMFU+hCEiWh1YR49zlhrapO2iWK7d/fn9gTezEmO43Itqxwte2NB4d+NKVQ/WC09TDBufJ1x8FiG46q9v0JYYbW6gES6k2EEqrWynkY3AF2QZkmbyilhndtZfOQrC6CytooWCjpx4Y/8qdPKkeTlMoc0tWuhEkogNCjJWZSH9IkKgIg4eHMnOxrTFfUO3OYWjm6bguJ+1Z1Ml/9uko1El9RokcyTldwYUeEiYwN31DDnd3VKBgIVeTL... | 2022-06-27T03:01:36 | 2022-06-27T03:01:36 | {} | CONTRIBUTOR |
vuejs | core | 1,167,043,822 | 6,187 | webfansplz | > The problem with this change is that now we communicate via our types that it's fine to mutate this property in userland - it's part of the types, after all. But that's not* what people should be doing.
>
> So I think a better solution would be to have a dedicated getter for retrieving this information.
Updated... | 2022-06-27T08:27:40 | 2022-06-27T08:27:40 | {} | MEMBER |
vuejs | core | 1,167,602,303 | 6,144 | LinusBorg | I can't reproduce this. As you didn't really give instructions about how you tested this, here's what I did:
* run `build`
* run `preview` and open the url shown in the console
* open Memory tab in Chrome dev Tools
* quickly switch between two routes.
* see memory grow towards 40 - 50 - 70 MB
* wait a bit / cli... | 2022-06-27T16:50:27 | 2022-06-27T18:06:12 | {} | MEMBER |
vuejs | core | 1,169,433,928 | 6,194 | edison1105 | `treatDefaultAsFactory` default value is `false`
Examples in the documentation may need to be modified.
).
We enc... | 2022-06-29T11:54:47 | 2022-06-29T11:54:47 | {} | MEMBER |
vuejs | core | 1,169,987,943 | 6,200 | LinusBorg | https://github.com/vuejs/core/issues/6198 | 2022-06-29T13:34:06 | 2022-06-29T13:34:06 | {} | MEMBER |
vuejs | core | 1,170,221,309 | 5,657 | BabOuDev | hey! got the same thing here:
For us, this was triggered when Firefox is auto-filling some inputs, but I don't think it's relevant. The important thing is that it's only happening in prod mode...
Aft... | 2022-06-29T16:39:09 | 2022-06-29T16:41:01 | {
"+1": 13
} | NONE |
vuejs | core | 1,170,257,957 | 6,202 | jmaloon | Commenting because we've come across a similar issue/bug since upgrading from `3.2.33` => `3.2.37` | 2022-06-29T17:16:06 | 2022-06-29T17:16:06 | {} | NONE |
vuejs | core | 1,170,716,360 | 5,970 | geng130127 | The latest version still has this problem | 2022-06-30T03:43:41 | 2022-06-30T03:43:41 | {} | NONE |
vuejs | core | 1,165,346,123 | 6,172 | LinusBorg | Don't mess with the DOM that Vue controls. | 2022-06-24T08:42:45 | 2022-06-24T08:42:45 | {} | MEMBER |
vuejs | core | 1,166,311,389 | 5,690 | u10k | function1:
```
import { useRouter } from 'vue-router';
export default {
setup() {
// 第一步将useRouter函数执行放在顶部
const router = useRouter();
// 第二步在方法里面调用router
function toPage(){
router.push("/about");
}
return {
toPage
}
}
}
```
funtion2:
```
import router ... | 2022-06-25T15:34:42 | 2022-06-25T15:34:42 | {} | NONE |
vuejs | core | 1,167,139,085 | 6,160 | Innei | Hi, @antfu @yyx990803
Since this PR is unresponsive for a long time. I noticed that you are a recent committer for this project. May I ask do you mind applying this changes to the project? | 2022-06-27T09:52:04 | 2022-06-27T09:52:04 | {} | CONTRIBUTOR |
vuejs | core | 1,172,003,353 | 6,209 | LinusBorg | Thanks!
> I assumed that was the purpose of requiring the SFC playground link and why you all didn't ask for a repo in the walkthrough.
Do you mean this, from the issue form?
> The easiest way to provide a reproduction is by showing the bug in [The SFC Playground](https://sfc.vuejs.org/).
If it cannot be repr... | 2022-07-01T06:55:05 | 2022-07-01T06:55:05 | {} | MEMBER |
vuejs | core | 1,165,516,685 | 3,671 | lowdog136 | +1 | 2022-06-24T12:17:02 | 2022-06-24T12:17:02 | {} | NONE |
vuejs | core | 1,167,202,231 | 5,443 | xiaoyongchen | // template
<input
:disabledColor="disabledColor"
:class="[
{
required: required,
'is-color-disabled': disabled,
'is-invalid': required && invalid && !value,
},
]"
/... | 2022-06-27T10:55:04 | 2022-06-27T10:55:04 | {} | NONE |
vuejs | core | 1,167,281,748 | 813 | ronssij | I am having the same issue for Vue2.
but mine is on `v-on="$listeners"` rendered on a functional component.
```
<template>
<div class="aft-list-item" v-on="$listeners">
<slot />
</div>
</template>
<script>
export default {
name: 'AftListItem',
props: {
noDivider: {
type: Boolean... | 2022-06-27T12:18:40 | 2022-06-27T12:31:10 | {
"+1": 1
} | NONE |
vuejs | core | 1,168,590,345 | 4,609 | doom-9-zz | @yyx990803 | 2022-06-28T11:19:01 | 2022-06-28T11:19:01 | {} | NONE |
vuejs | core | 1,169,778,349 | 6,194 | niceplugin | I think so too.
So I opened an issue in vuejs/docs.
However, the member told me to report the issue here as it is not a document issue.
I just hope this problem gets resolved quickly. | 2022-06-29T09:54:42 | 2022-06-29T09:54:42 | {} | NONE |
vuejs | core | 1,169,817,540 | 6,194 | NataliaTepluhina | @edison1105 we also have this export:
```
export function inject<T>(
key: InjectionKey<T> | string,
defaultValue: T | (() => T),
treatDefaultAsFactory: true
): T
```
see https://github.com/vuejs/core/blob/8edf4b344179d0a8d3c1090ce63f466f4e787976/packages/runtime-core/src/apiInject.ts#L36
Are we sure ... | 2022-06-29T10:34:33 | 2022-06-29T10:37:00 | {} | MEMBER |
vuejs | core | 1,170,993,115 | 6,202 | GrapevineLin | due to the diff algorithm, you should add unique keys to differentiate these two `<Comp>`
```vue
<Comp3>
<template v-if="data % 2 === 0" #actions>
<Comp key="1">
<template #foo>
{{ data }}
</template>
</Comp>
</template>
<template v-else #actions>
<C... | 2022-06-30T09:36:45 | 2022-06-30T09:38:08 | {} | NONE |
vuejs | core | 1,173,333,068 | 6,221 | zhangmo8 | 
只要加一点其他属性，就有了....不知道为啥 | 2022-07-04T04:33:15 | 2022-07-04T04:33:15 | {} | NONE |
vuejs | core | 1,165,157,705 | 6,170 | baiwusanyu-c | ```
rollupOptions: {
external: ['vue'],
output: {
globals: {
vue: 'Vue',
},
},
}
``` | 2022-06-24T03:32:14 | 2022-06-24T03:32:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,165,543,687 | 6,171 | liulinboyi | This issue may be `vite`, when modify the file such as add a new line, it will run correctly.
I feel the issue because of cache.
https://user-images.githubusercontent.com/41336612/175538613-a70b4056-a7f0-4900-b290-01b5c9834d4d.mp4
| 2022-06-24T12:51:24 | 2022-06-24T12:51:24 | {} | MEMBER |
vuejs | core | 1,166,296,223 | 6,179 | billypon | OK, I close my PR, and wait for another PR. | 2022-06-25T14:13:18 | 2022-06-25T14:13:18 | {} | NONE |
vuejs | core | 1,167,011,458 | 6,187 | LinusBorg | The problem with this change is that now we communicate via our types that it's fine to mutate this property in userland - it's part of the types, after all. But that's not* what people should be doing.
So I think a better solution would be to have a dedicated getter for retrieving this information. | 2022-06-27T07:56:22 | 2022-06-27T07:56:22 | {} | MEMBER |
vuejs | core | 1,170,062,029 | 6,201 | skirtles-code | @LinusBorg Yeah, it is in the JS tab, but not in the SSR tab. | 2022-06-29T14:33:45 | 2022-06-29T14:35:03 | {} | CONTRIBUTOR |
vuejs | core | 1,170,290,959 | 3,671 | theosherman | > > Vue2 + Composition API, it got the same problem in setup function
>
> I had the same problem when I used incorrect import (automatically added by IDE):
>
> ```
> import { onMounted } from '@vue/composition-api/dist/vue-composition-api.js'
> ```
>
> Solution:
>
> ```
> import { onMounted } from '@vue/... | 2022-06-29T17:43:54 | 2022-06-29T17:43:54 | {} | NONE |
vuejs | core | 1,170,707,873 | 6,200 | YouthguyZ | > #6198
ok i got thanks bro🤠 | 2022-06-30T03:25:06 | 2022-06-30T03:25:06 | {} | NONE |
vuejs | core | 1,171,083,491 | 6,202 | Akryum | Having different content should work without having to use keys. | 2022-06-30T11:07:22 | 2022-06-30T11:07:22 | {} | MEMBER |
vuejs | core | 1,172,916,625 | 5,603 | 07akioni | I think this should be tagged as bug. | 2022-07-02T15:31:11 | 2022-07-02T15:31:11 | {
"+1": 4
} | CONTRIBUTOR |
vuejs | core | 1,173,177,074 | 6,220 | ShGKme | "Global provide/inject API" could not exists by design.
Provide/Inject works in component's subtree in Vue App. Value is provided in one instance in one place of tree and injected in another instance in any place of subtree.
In simple words, injected value depends on all upper tree and may be various in differen... | 2022-07-03T21:44:37 | 2022-07-03T22:05:52 | {
"+1": 2
} | NONE |
vuejs | core | 1,165,159,281 | 6,170 | zhazhazhu | > ```
> rollupOptions: {
>
> external: ['vue'],
> output: {
>
> globals: {
> vue: 'Vue',
> },
> },
> }
> ```
success | 2022-06-24T03:35:48 | 2022-06-24T03:35:48 | {} | NONE |
vuejs | core | 1,166,271,239 | 5,701 | LinusBorg | I looked at this again and think the docs are fine as they are - at least I personally don't know how to change them in a way that would make this more clear without being to in-your-face about it.
If you think you see a better way to phrase it, feel free to submit a PR in the `docs` repo | 2022-06-25T12:16:10 | 2022-06-25T12:16:17 | {} | MEMBER |
vuejs | core | 1,166,407,880 | 6,171 | we125182 | @liulinboyi thanks for replying. I will refer this to vite | 2022-06-26T03:18:03 | 2022-06-26T03:18:03 | {} | NONE |
vuejs | core | 1,170,006,009 | 6,201 | LinusBorg | weirdly, as in the JS tab of the playground, _unref seems to be imported ... | 2022-06-29T13:49:35 | 2022-06-29T13:49:35 | {} | MEMBER |
vuejs | core | 1,172,079,492 | 6,206 | dxvladislavvolkov | @LinusBorg But if I use UI library for vue 3 and I don't have the opportunity to set compatConfig inside the component?
In this case, how can I fix the warning? | 2022-07-01T08:23:33 | 2022-07-01T08:23:44 | {} | NONE |
vuejs | core | 1,165,158,859 | 6,170 | liulinboyi | First of all, the [repo](https://github.com/zhazhazhu/vu3-project) can't running correctly, the `The component does not work` maybe your `vite.config.ts` is wrong😉. | 2022-06-24T03:34:51 | 2022-06-24T03:34:51 | {} | MEMBER |
vuejs | core | 1,166,255,452 | 6,174 | LinusBorg | that's expected. during dev, comments are used as markers for various things such as fragments, for reasons such as better debugability, HMR etc.
We can think about how to make it easier to get the actual children, though | 2022-06-25T10:52:27 | 2022-06-25T10:52:27 | {} | MEMBER |
vuejs | core | 1,166,620,503 | 6,169 | WORMSS | > [Fix Preview](https://deploy-preview-6169--vue-sfc-playground.netlify.app/#__DEV__eyJBcHAudnVlIjoiPHNjcmlwdD5cbmltcG9ydCB7IHJlZiwgd2F0Y2hFZmZlY3QsIHdhdGNoLCB1bnJlZiwgZGVmaW5lQ29tcG9uZW50IH0gZnJvbSAndnVlJ1xuZXhwb3J0IGRlZmF1bHQgZGVmaW5lQ29tcG9uZW50KHtcbiAgc2V0dXAoKSB7XG4gICAgY29uc3QgY291bnQgPSByZWYoNSk7XG4gICAgY29uc3Qg... | 2022-06-26T19:15:48 | 2022-06-26T19:16:01 | {} | NONE |
vuejs | core | 1,169,182,985 | 6,197 | LinusBorg | With the proposed type you would also be forced to cast it pretty much whenever using it, wouldn't you?
* want to access a property of an HTMLElement? property does not exist on `DefineComponent` -> need to cast
* want to access a component API method, like $emit? property does not exist on `HTMLElement` -> need to... | 2022-06-28T20:10:10 | 2022-06-28T20:11:12 | {} | MEMBER |
vuejs | core | 1,171,922,422 | 6,211 | baiwusanyu-c | 
How is this going? Even though I didn't make any changes, I ran this test from the forked project and it still didn't pass | 2022-07-01T04:28:48 | 2022-07-02T13:19:18 | {} | MEMBER |
vuejs | core | 1,173,015,412 | 6,160 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 694007a662bb543f3e3e36e86b8ade8eb61f1082 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-07-03T05:33:35 | 2022-07-03T05:33:35 | {} | NONE |
vuejs | core | 1,165,765,140 | 2,855 | JamesManningR | > > ...I am only seeing this error when running a production build - dev builds don't throw the error
>
> for me it's the opposite 🤷♂️ runs fine on prod build, only watch and dev complain...
I also get it only in the production build 🤷♂️ weird | 2022-06-24T17:04:14 | 2022-06-24T17:04:14 | {} | NONE |
vuejs | core | 1,165,965,700 | 4,356 | NielsJorck | I'm far from in-depth with the core functionality of vue. But I did some digging and posting it here in case it is helpful. 🙈
The dev tools isn't showing since no apps are registered with the dev tools. If you mount a regular vue app on the same page it will show normally, but only have the regular app registered.
... | 2022-06-24T21:48:03 | 2022-06-24T21:48:03 | {} | NONE |
vuejs | core | 1,166,258,940 | 5,378 | LinusBorg | My current implementation would be a breaking change as it would break camelCase listeners that were added programmatically, for example.
Could we get around this by emitting the event both in camel- and kebap-case?
That could also break _something_, but I'd consider that to be the most extreme of edge cases. | 2022-06-25T11:10:20 | 2022-06-25T12:02:29 | {} | MEMBER |
vuejs | core | 1,170,797,946 | 5,996 | Ashiria7 | I met this problem too. It seems like an async problem. I try my best made a [minimal reproduction](https://github.com/AXiLiYa/element-plus-message-bug). This problem can be fixed by `nextTick`:
```js
function createMessage() {
nextTick(() => ElMessage('Bug occurs'))
}
```
or change open event to opened event:
... | 2022-06-30T05:56:47 | 2022-06-30T05:56:47 | {} | NONE |
vuejs | core | 1,171,960,339 | 6,209 | aphex | @LinusBorg absolutely here ya go. https://github.com/aphex/vue-memory-test
I assumed that was the purpose of requiring the SFC playground link and why you all didn't ask for a repo in the walkthrough.
Let me know if you need anything else, thanks! | 2022-07-01T05:46:58 | 2022-07-01T05:46:58 | {} | NONE |
vuejs | core | 1,172,310,735 | 6,205 | Adoew | It is fixed. I just removed the --inline-vue in the build command in the library's package.json and everything is working fine, just as in dev mode. I don't know if this can help the community in any way so I leave this comment and close the issue. | 2022-07-01T12:48:17 | 2022-07-01T12:48:17 | {} | NONE |
vuejs | core | 1,173,028,568 | 5,670 | javastation | > How far away do you think this PR will be ready for review @javastation? I am quite keen to have this as I believe this will fix an issue I have
Tried my best, wait a little longer. | 2022-07-03T07:26:02 | 2022-07-03T07:26:02 | {
"heart": 3
} | CONTRIBUTOR |
vuejs | core | 1,166,255,815 | 6,163 | LinusBorg | This is not really caused by the scoped CSS attribute specifically, but any custom attribute/property added to a WC that doesn't have any props defined. | 2022-06-25T10:54:38 | 2022-06-25T10:54:38 | {} | MEMBER |
vuejs | core | 1,170,211,552 | 6,194 | LinusBorg | Apart from the question of what Evan's intended behavior was, the main question is: What's the more common usage?
My gut tells me that it's more common to provide a function (and thus need a function as a default was well), than it is to require a factory function for creating the default value.
Mainly because `... | 2022-06-29T16:30:26 | 2022-06-29T16:44:39 | {} | MEMBER |
vuejs | core | 1,171,240,593 | 5,670 | javastation | hi @edison1105, it seems that quite a few people have encountered this problem and I hope you can help review this pr. Thanks for your suggestions on my previous pr. | 2022-06-30T13:46:02 | 2022-06-30T13:46:02 | {
"+1": 6
} | CONTRIBUTOR |
vuejs | core | 1,171,916,293 | 4,294 | arthurbergmz | > If you are using Vite, you can use this plugin https://github.com/wheatjs/vite-plugin-vue-type-imports as a patch until this is officially supported.
This is great, thank you!! | 2022-07-01T04:16:33 | 2022-07-01T04:16:33 | {} | NONE |
vuejs | core | 1,172,551,760 | 5,603 | runxc1 | I'm running into the same issue if the app is mounted to a specific element and then later that element is removed from the page. The entire app goes away correctly but the Teleported item that is disabled then displays and is left on the page | 2022-07-01T17:08:11 | 2022-07-01T17:08:11 | {} | NONE |
vuejs | core | 1,165,377,945 | 6,173 | LinusBorg | This is not a bug, it's simply not supported (and nothing in our docs say it would be)
This could be made possible if we decide to work a feature for #5540 | 2022-06-24T09:18:15 | 2022-06-24T09:18:15 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.