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,176,188,959 | 5,657 | Oleksii14 | Hi everyone. I also have this issue only in prod mode. A temporary workaround: remove a `key` attribute from your `v-for`. The error will still be in the console, but it fixes the issue with the rendering | 2022-07-06T12:56:15 | 2022-07-06T12:56:15 | {
"+1": 1,
"eyes": 2
} | NONE |
vuejs | core | 1,176,792,681 | 5,525 | vervelover | not working for me as well | 2022-07-06T22:00:07 | 2022-07-06T22:00:07 | {} | NONE |
vuejs | core | 1,179,642,840 | 6,240 | binghc | 请教下，在style标签中能使用v-if么？ | 2022-07-10T02:36:57 | 2022-07-10T02:36:57 | {} | NONE |
vuejs | core | 1,175,301,033 | 6,228 | LinusBorg | You commented out the setting to externalize vue in your libary's config. This had the same effect as `--inline-vue` in your Vue CLI project - it included its own copy of Vue.
After that change, `dedupe: ['vue']` can do what it should: avoid adding another copy of Vue when the *app* imports the lib.
GUI config:
... | 2022-07-05T17:07:48 | 2022-07-05T17:08:37 | {} | MEMBER |
vuejs | core | 1,175,691,825 | 6,225 | hminghe | > 你默认设置了comp1缓存，不会触发unmount, 是单独的钩子https://vuejs.org/guide/built-ins/keep-alive.html#lifecycle-of-cached-instance
你看，第二步，已经把 include 修改成 comp2 了。 | 2022-07-06T01:59:43 | 2022-07-06T01:59:43 | {} | NONE |
vuejs | core | 1,179,103,181 | 6,242 | LinusBorg | This is kind of expected. It's strongly discouraged to mix `script setup` with Options API like that.
In the docs we explain that a second script block should be used for:
> * Declare options that cannot be expressed in <script setup>, for example inheritAttrs or custom options enabled via plugins.
However we... | 2022-07-08T15:17:08 | 2022-07-08T15:17:08 | {} | MEMBER |
vuejs | core | 1,179,368,675 | 6,169 | WORMSS | Can I ask what the hold up is for this PR? Maybe I can help unblock it? | 2022-07-08T21:21:49 | 2022-07-08T21:21:49 | {} | NONE |
vuejs | core | 1,174,698,510 | 2,779 | LinusBorg | This is now documented better: https://vuejs.org/api/application.html#app-config-compileroptions
Closing this | 2022-07-05T07:09:25 | 2022-07-05T07:09:25 | {} | MEMBER |
vuejs | core | 1,174,956,244 | 6,228 | LinusBorg | Ypu need to add that to the app's config, not the library's.
```js
module.exports = defineConfig({
plugins: [vue()],
resolve: {
dedupe: ['vue'],
alias: {
//vue: path.resolve(`./node_modules/vue`),
'@': path.resolve(__dirname, './src'),
},
},
});
``` | 2022-07-05T11:34:37 | 2022-07-05T11:36:34 | {} | MEMBER |
vuejs | core | 1,174,963,048 | 6,222 | chenhaihong | > vue@3.2.37 ， vue-router@4.0.16, vite@2.9.13 , @vitejs/plugin-vue@2.3.3 当 router-view 被 keep-alive 包裹的时候，无论 key 是什么，热更新 router-view 下的根组件 都会报错 ，子组件不会
>
> ```
> TypeError: parentComponent.ctx.deactivate is not a function
> ```
盲猜你是把 component 套了自定义组件里了，导致找不到 keepalive 实例，所以 `deactivate` 函数找不到。
| 2022-07-05T11:42:47 | 2022-07-05T11:42:47 | {} | NONE |
vuejs | core | 1,175,054,560 | 6,220 | HipyCas | I think I may have not explained myself properly.
I am using the provide/inject inside a component, but in the `onMounted` hook, outside the setup scope. In the code that I need this, I check whether the users prefers dark mode with a media query and a class in the body tag, which require to be check when the compon... | 2022-07-05T13:22:01 | 2022-07-05T13:22:01 | {} | NONE |
vuejs | core | 1,175,690,577 | 6,225 | snowwolfjay | 你默认设置了comp1缓存，不会触发unmount, 是单独的钩子https://vuejs.org/guide/built-ins/keep-alive.html#lifecycle-of-cached-instance | 2022-07-06T01:57:22 | 2022-07-06T01:57:22 | {} | NONE |
vuejs | core | 1,175,979,272 | 6,230 | uCloudCastle | 为了同时支持 Vue2 和 Vue3，我改成了这样（xxx-plugin 中没有依赖 vue 库）：
Vue2：
```
import { install } from 'xxx-plugin'
install(
{
...config,
createInstance: (container, router) => {
return new Vue({
router: router,
store: store,
render: h => h(App),
}).$mount(container ? container... | 2022-07-06T09:10:32 | 2022-07-06T09:10:32 | {} | NONE |
vuejs | core | 1,176,013,075 | 6,220 | UnluckyNinja | I think you mistook "provide" as a method to provide a default value rather than to create a store for later use.
As above replies said, you should provide a reactive variable (either a `ref` or a `reactive`), then you can change the actual value/object property later at anytime. I suggest that you can read official g... | 2022-07-06T09:43:06 | 2022-07-06T09:43:06 | {
"rocket": 1
} | NONE |
vuejs | core | 1,179,103,684 | 6,242 | LinusBorg | /cc @skirtles-code What do you think about this in terms of docs, expected behavior and such? | 2022-07-08T15:17:40 | 2022-07-08T15:17:40 | {} | MEMBER |
vuejs | core | 1,173,978,085 | 3,842 | kerch83 | > How to fix that, i have same error today. Its complete project, what working 2 years, nad that problems goin only today in 1765 files, wow. How i can ifx that?
i have same problem 2 days ago(
are you fix it? | 2022-07-04T16:15:42 | 2022-07-04T16:15:42 | {} | NONE |
vuejs | core | 1,174,437,061 | 5,584 | ArkoxHub | This needs to be fixed as soon as possible. I wasted more than 2 hours because of this no-sense problem. Working dev but not in production without explanation is frustrating.
And there is no official solution. | 2022-07-04T22:32:22 | 2022-07-04T22:33:00 | {
"+1": 7,
"confused": 2,
"eyes": 1
} | NONE |
vuejs | core | 1,174,973,065 | 6,219 | chenhaihong | 有官方大佬回复个吗？这个确实是有很大用处的提议。
keep-alive 可选地把 slots.default() 的 key 用作 root VNode 的 [cache key](https://github.com/vuejs/core/blob/769e5555f9d9004ce541613341652db859881570/packages/runtime-core/src/components/KeepAlive.ts#L289)
```html
<keep-alive ref="ka">
<component :is="Component" :key="route.fullPath" />
... | 2022-07-05T11:55:09 | 2022-07-05T11:55:09 | {
"+1": 1
} | NONE |
vuejs | core | 1,177,187,729 | 5,525 | vervelover | Hi, thank you for the answer, unfortunately all workarounds posted seem to add values to the ref array, but contrary to what I was able to do in vue 2, in vue 3 I cannot access any method defined on the ref. So let's say I have a `validate()` method on the first ref of the itemRefs array, in vue 2 I was able to call it... | 2022-07-07T07:23:14 | 2022-07-07T07:23:14 | {} | NONE |
vuejs | core | 1,177,265,394 | 5,952 | Hugofgx9 | when will this be release ? This issue causes bugs on nuxt 3 which make it difficult to use in production for the moment | 2022-07-07T08:46:22 | 2022-07-07T16:20:00 | {
"+1": 19
} | NONE |
vuejs | core | 1,178,696,839 | 6,192 | mayank1513 | Please follow proper Vue syntax. `testBind` isn't a reactive ref. | 2022-07-08T08:18:24 | 2022-07-08T08:18:24 | {} | NONE |
vuejs | core | 1,173,851,248 | 5,584 | preeteshjain | Hi @yyx990803 @LinusBorg
I have created a playground for this problem: [**Link**](https://sfc.vuejs.org/#eNp9kj9vgzAQxb/K1QtESmDoRkmkKqrUpVKndqg70HBJiPCf2iYZEN+9Z5NCSKtM5uzH7/neuWWPWifHBlnGcrsxlXZg0TV6xWUltDIOWjC4hQ62RgmISBoNR+t9VZdrJfT5MEmHHc+MHrjkcqOkdSDsDpaeFEfPWNcK3pWpy7toRpo87Z3JkwqHQteFQ6oA8tHiuBCqxHrJGbE4W+W... | 2022-07-04T13:55:22 | 2022-07-04T13:55:22 | {
"confused": 3
} | NONE |
vuejs | core | 1,175,079,920 | 2,969 | pdanpdan | Isn't it `@vnode-mounted` / onVnodeMounted?
https://github.com/vuejs/core/issues/3178
https://github.com/vuejs/core/issues/4345
The problem is we only have access to the wrapper, which emits mounted, but the async component is not known (loader/component) | 2022-07-05T13:45:48 | 2022-07-05T13:49:32 | {
"+1": 1
} | NONE |
vuejs | core | 1,174,548,811 | 2,097 | WormGirl | > It's not documented but yes it's possible to render using existing app context:
>
> ```js
> import { h, render } from 'vue'
>
> const childTree = h('div', 'some message')
> treeToRender.appContext = app._context
> render(childTree, document.getElementById('target'))
> ```
>
> We can make this a method on... | 2022-07-05T02:56:57 | 2022-07-05T03:15:39 | {} | NONE |
vuejs | core | 1,174,959,824 | 6,228 | Adoew | @LinusBorg I already tried that and the error is still triggered. | 2022-07-05T11:38:51 | 2022-07-05T11:38:51 | {} | NONE |
vuejs | core | 1,175,140,491 | 6,220 | Sanicboi | You can use Pinia state management to achieve global provide/inject. It is just easier.[More details here](https://pinia.vuejs.org/) | 2022-07-05T14:39:27 | 2022-07-05T14:39:27 | {} | NONE |
vuejs | core | 1,176,180,594 | 6,194 | UnluckyNinja | > 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/ap... | 2022-07-06T12:47:33 | 2022-07-06T12:53:50 | {} | NONE |
vuejs | core | 1,177,324,677 | 5,525 | vervelover | > Use defineExpose()wink, [docs](https://vuejs.org/api/sfc-script-setup.html#defineexpose).
That was awesome, thank you!
I still do not understand why this bug is closed though, because I still get an empty array of refs when not using the object wrap workaround.. | 2022-07-07T09:43:33 | 2022-07-07T09:43:33 | {} | NONE |
vuejs | core | 1,177,738,876 | 5,952 | atinux | What is stopping this PR from changing its draft status? | 2022-07-07T14:51:27 | 2022-07-07T14:51:27 | {
"+1": 30
} | NONE |
vuejs | core | 1,178,455,388 | 5,525 | edison1105 | @vervelover
`:ref="itemRefs"` value only support `string, ref, function`.
`itemRefs` in template will be compiled to $setup.itemRefs(in DEV) or itemRefs.value(in PROD)
it unwrap into a `Proxy` value. so this is a limitaion for directly use a ref in `:ref=""`.
| 2022-07-08T02:03:26 | 2022-07-08T02:03:26 | {} | MEMBER |
vuejs | core | 1,179,542,725 | 6,244 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 489df2e2db55d0847f762b7fb5be43127b9e440a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-07-09T13:09:33 | 2022-07-09T13:09:33 | {} | NONE |
vuejs | core | 1,174,722,111 | 4,635 | NielsJorck | This would likely also fix the issue with devtools not working in Custom Elements:
https://github.com/vuejs/core/issues/4356 | 2022-07-05T07:37:54 | 2022-07-05T07:37:54 | {
"+1": 4
} | NONE |
vuejs | core | 1,174,964,661 | 6,214 | LinusBorg | but in practice, when using class selectors, this is not a real issue. This is the only problematic scenario:
```html
<div class="upper-class">
<div class="inner-class">this should be red</div>
</div>
<div class="inner-class">
This can turn out red if `outer-class` is also used in a parent component.
But... | 2022-07-05T11:44:44 | 2022-07-05T11:45:30 | {} | MEMBER |
vuejs | core | 1,175,068,799 | 2,969 | LinusBorg | Cleaning up old issues....
at least the `mounted` part of the requirement is achievable like this:
```html
<myAsyncComponent @vue:mounted="handler">
``` | 2022-07-05T13:35:21 | 2022-07-05T13:35:21 | {} | MEMBER |
vuejs | core | 1,175,566,399 | 5,584 | ArkoxHub | Hi guys, I have found a solution for my case and I really wish if someone can explain me why is working like this instead of what I've doing until now.
This is the parent Component calling BaseSelect child component. v-model now is linked with object attribute of parent. Like this is working.
```
<BaseSelect
... | 2022-07-05T22:32:34 | 2022-07-05T22:39:58 | {
"heart": 1
} | NONE |
vuejs | core | 1,175,763,707 | 5,584 | tyronksmith | FWIW. I changed the child component so that the `v-model` in the child was not `v-model="modelValue"` but rather implemented a ref variable. ie.
```
const childValue = ref(props.modelValue)
<input v-model="childValue">
```
By no means am I suggesting this is the right way to do it, but it worked for me. As L... | 2022-07-06T04:20:06 | 2022-07-06T04:20:06 | {} | NONE |
vuejs | core | 1,175,939,342 | 6,210 | yyx990803 | Closing as stale (no valid reproduction) | 2022-07-06T08:31:13 | 2022-07-06T08:31:13 | {} | MEMBER |
vuejs | core | 1,179,105,268 | 6,241 | LinusBorg | See #6242 - the explanation in that issue also applies here. Solutions can be discussed in that ticket. | 2022-07-08T15:19:18 | 2022-07-08T15:19:18 | {} | MEMBER |
vuejs | core | 1,217,447,008 | 6,387 | sadeghbarati | https://stackoverflow.com/questions/14883250/css-transform-doesnt-work-on-inline-elements
https://htmlreference.io/
> **Note**: `span` is inline element
| 2022-08-17T04:26:51 | 2022-08-17T04:26:51 | {
"+1": 1
} | NONE |
vuejs | core | 1,219,278,342 | 6,498 | LinusBorg | duplicate of #6347 | 2022-08-18T09:43:40 | 2022-08-18T09:43:40 | {} | MEMBER |
vuejs | core | 1,221,262,123 | 2,513 | semiaddict | I wouldn't recommend overriding the userAgent as this can have side effects within and outside of Vue.
I've personally been patching Vue 3 with the changes in my [pull request ](https://github.com/vuejs/core/pull/5474) using [patch-package](https://www.npmjs.com/package/patch-package) without issues.
I just hope... | 2022-08-20T08:58:10 | 2022-08-20T08:58:10 | {
"+1": 1
} | NONE |
vuejs | core | 1,221,395,531 | 6,512 | LinusBorg | That would depend on your editor/IDE Integration, not Vue core.
For VSCode, that would be Volar. But I can't replicate this issue in VSCode with Volar, I get proper error highlights. | 2022-08-20T19:47:22 | 2022-08-20T21:07:25 | {} | MEMBER |
vuejs | core | 1,221,690,593 | 6,517 | tony19 | > first, at Stackblitz B, button 3 also is const , but is changed.
I don't see that behavior in the demos you linked.
If you click button 3, `var_const_random` does **not** change despite the post-increment operator on it in the `click`-handler. Its value is always `0`.
> and, Stackblitz B and plyground A has ... | 2022-08-22T01:37:23 | 2022-08-22T01:37:23 | {} | CONTRIBUTOR |
vuejs | core | 1,221,827,302 | 6,517 | tony19 | Ah, I see it now. It wasn't reproducing earlier because I wasn't properly following the reproduction steps. However, the behavior is the same in both StackBlitz and the Vue Playground.
There's not really a bug to fix here, but I believe this is what's happening:
1. In dev mode, the Vue compiler transforms `const ... | 2022-08-22T05:01:08 | 2022-08-22T05:02:28 | {} | CONTRIBUTOR |
vuejs | core | 1,222,001,381 | 6,525 | LinusBorg | I'm not sure what you are asking.
You should direct support questions to [this repo's discussions](https://github.com/vuejs/core/discussions) or our discord server | 2022-08-22T08:09:16 | 2022-08-22T08:09:16 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,222,652,106 | 6,499 | EmmyMay | > ```
> v-for="{x} of[{x:'1'}]"
> ```
([\s\S]*?)(?:in|of)([\s\S]*)
This regex would work. Let me look into making a PR
| 2022-08-22T17:09:08 | 2022-08-22T17:09:08 | {
"-1": 1
} | NONE |
vuejs | core | 1,227,065,555 | 6,222 | qinpeip | same error!!! | 2022-08-25T10:17:43 | 2022-08-25T10:17:43 | {} | NONE |
vuejs | core | 1,216,732,775 | 6,483 | LinusBorg | The compiler produces this code:
```js
(_ctx.$emit('myclick', new _unref(TestClass)())
```
which is invalid. This should be fixable with an additional set of paranthesis if we need to unwrap directly after `new`:
```js
(_ctx.$emit('myclick', new (_unref(TestClass))())
```
| 2022-08-16T14:41:01 | 2022-08-16T14:41:19 | {} | MEMBER |
vuejs | core | 1,220,528,294 | 5,996 | not-Ryan | For anyone wanting the patch file that can be used with [patch-package](https://www.npmjs.com/package/patch-package):
`patches/@vue+runtime-core+3.2.36.patch`
```diff
diff --git a/node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js b/node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js
in... | 2022-08-19T10:44:36 | 2022-08-19T10:46:19 | {
"rocket": 3
} | NONE |
vuejs | core | 1,221,263,840 | 2,513 | semiaddict | @LinusBorg,
@yyx990803,
Any chance of getting the pull request reviewed?
I'm totally open on working on a different solution if for any reason the one proposed in the pull request doesn't quite fit the Vue coding practices.
Thanks in advance. | 2022-08-20T09:11:04 | 2022-08-20T09:11:04 | {
"+1": 4,
"heart": 1
} | NONE |
vuejs | core | 1,221,518,464 | 6,514 | LinusBorg | This is expected. toRefs creates a new refs for all properties, regardless of their (raw) content. It will not give the same ref potentially nested inside the `reactive()` proxy's raw target object. | 2022-08-21T10:32:11 | 2022-08-21T10:32:11 | {} | MEMBER |
vuejs | core | 1,221,615,126 | 6,518 | djom202 | @LinusBorg Ok but Why I can't access them into the methods?
In the `doLogin` Method, Im suposing as V2 I should be able to access them, rigth or not? | 2022-08-21T20:26:14 | 2022-08-21T20:28:43 | {} | NONE |
vuejs | core | 1,221,915,744 | 6,515 | LinusBorg | Please open an issue with troisJS or provide a repo not using this 3rd party libary. | 2022-08-22T06:40:05 | 2022-08-22T06:40:05 | {} | MEMBER |
vuejs | core | 1,221,934,966 | 6,504 | cokuna-pavelkosolapov | @EmmyMay type mismatch is not the problem! The point is that the grandparent attribute overrides the property set by the direct parent! In my opinion this is a wrong behaviour, the direct property should have more weight.
I spent a lot of time to find this out by removing my code line by line...
> Are you claiming ... | 2022-08-22T07:03:02 | 2022-08-22T07:03:02 | {
"eyes": 1
} | NONE |
vuejs | core | 1,222,812,906 | 6,531 | LinusBorg | duplicate of #4294 | 2022-08-22T19:22:49 | 2022-08-22T19:22:49 | {} | MEMBER |
vuejs | core | 1,223,806,358 | 6,535 | LinusBorg | `:style="g.value"`
list is a non-reactive array, so refs inside of it are not unwrapped. | 2022-08-23T09:28:15 | 2022-08-23T09:28:15 | {} | MEMBER |
vuejs | core | 1,224,153,410 | 5,836 | klausXR | I'm also interested in this | 2022-08-23T14:26:04 | 2022-08-23T14:26:04 | {} | NONE |
vuejs | core | 1,226,888,654 | 6,543 | LinusBorg | The reproduction link does not demonstrate the problem. We can't investigate without a runnable reproduction. | 2022-08-25T07:35:13 | 2022-08-25T07:35:13 | {} | MEMBER |
vuejs | core | 1,227,342,293 | 6,222 | olddriverads | > 相同的
请问有解决方法吗 | 2022-08-25T14:31:34 | 2022-08-25T14:31:34 | {} | NONE |
vuejs | core | 1,227,439,940 | 6,532 | pikax | I would say having `| undefined` or `?:` on a prop should generate basically the same code, because in `vue` if a prop is declare it will be always available.
I think this problem is related with the generation of the code when using `script setup` and `Volar`. | 2022-08-25T15:38:21 | 2022-08-25T15:38:21 | {} | MEMBER |
vuejs | core | 1,216,732,160 | 6,482 | mayakokits | Found a workaround by using `Suspense` with component `:is`, replacing the suspense with a dummy wrapper once it has resolved.
```html
<component
:is="suspenseResolved ? 'SimpleWrapper' : 'suspense'"
@resolve="suspenseResolved = true"
>
<my-async-tree-root-node />
<template #fallback>
<loading-compo... | 2022-08-16T14:40:32 | 2022-08-16T14:41:46 | {} | NONE |
vuejs | core | 1,219,367,392 | 6,497 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c7c51486519714ac511df08a69375db3332756ad |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-08-18T11:14:44 | 2022-08-18T11:14:44 | {} | NONE |
vuejs | core | 1,219,818,967 | 5,767 | daniloribeiro00 | I tried it too, but it didn’t work for me. | 2022-08-18T18:45:30 | 2022-08-18T18:45:30 | {} | NONE |
vuejs | core | 1,221,317,589 | 6,138 | DrJume | Hey, just wanted to ask if there is anything I can do to get this fix merged 🙂 | 2022-08-20T13:44:01 | 2022-08-20T13:44:29 | {} | CONTRIBUTOR |
vuejs | core | 1,221,973,318 | 6,515 | benoitlahoz | Thank you. Just to be complete: the error disappears when I define my component with `defineComponent`. | 2022-08-22T07:41:55 | 2022-08-22T07:41:55 | {} | NONE |
vuejs | core | 1,218,201,037 | 6,222 | JackDeng666 | same | 2022-08-17T15:49:04 | 2022-08-17T15:49:04 | {} | NONE |
vuejs | core | 1,219,035,007 | 6,467 | edison1105 | this seems not to fix #6463. see [demo with your deploy preview](https://deploy-preview-6467--vue-sfc-playground.netlify.app/#eNqlVMuK2zAU/ZWLNuNAZKVQppBxAmE2hW4KU+jGGze+blRsSUiy0zD436uHHSsz09lMNtF9nXPPsexnclAqH3okW1JY7FRbWdyXAqCo+bAHAH920VNvFAoTayHj63MwhV+xbWXBXlS+IapDy4dlNqQfOwUD5c2uJNw8neRZlASYp5x+CQR7jZHSFOxmvblUsE... | 2022-08-18T04:48:29 | 2022-08-18T04:48:29 | {} | MEMBER |
vuejs | core | 1,219,021,692 | 6,494 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | f6ac3a43131a122a44fdab0da3b2671698d92e3b |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-08-18T04:13:49 | 2022-08-18T06:33:33 | {} | NONE |
vuejs | core | 1,221,615,597 | 6,518 | LinusBorg | You can. The code would run. But you did not wrap the component in `defineComponent()`, so Typescript doesn't recognize the object as a component and consequently gives you type errors as if it was a plain object. | 2022-08-21T20:29:20 | 2022-08-21T20:30:26 | {} | MEMBER |
vuejs | core | 1,223,806,290 | 6,532 | 2-5 | That's what I originally tried, but I also have `"exactOptionalPropertyTypes": true` in my `tsconfig.json` (https://devblogs.microsoft.com/typescript/announcing-typescript-4-4-beta/#exact-optional-property-types) and I get `vue-tsc` errors:
```
Type '{ modelValue: number | undefined; }' is not assignable to type
... | 2022-08-23T09:28:12 | 2022-08-23T09:28:12 | {} | NONE |
vuejs | core | 1,224,224,493 | 6,504 | woai3c | see [Fallthrough Attributes](https://vuejs.org/guide/components/attrs.html), the `:a="343"` is fallthrough. you can add the following code:
```js
const props = defineProps({
a: { type: String, default: 'ok' }
})
```
in `Comp.vue` to fix this problem. | 2022-08-23T15:19:59 | 2022-08-23T15:19:59 | {} | NONE |
vuejs | core | 1,221,722,735 | 6,517 | tony19 | I cannot reproduce that behavior in Chrome 104 on macOS. What browser are you using? | 2022-08-22T02:34:34 | 2022-08-22T02:34:34 | {} | CONTRIBUTOR |
vuejs | core | 1,221,893,336 | 6,525 | LinusBorg | 1. using internals in this way is hacky and risks breaking in the future
2. the reproduction doesn't demonstrate the problem described so I kinda need to guess.
3.
However I think your problem is that you have two projects, with two `node_modules` folders, each containing a copy of the vue package, and both are bei... | 2022-08-22T06:18:11 | 2022-08-22T06:18:11 | {} | MEMBER |
vuejs | core | 1,223,424,345 | 6,504 | EmmyMay | Maybe someone at the core team can help you, but other than the fact that it should work the way it used to, I actually feel like the grandparent should take precedence. But I understand your frustration since it wasn't like this. | 2022-08-23T01:55:31 | 2022-08-23T01:55:31 | {} | NONE |
vuejs | core | 1,225,890,719 | 5,847 | Guebbit | The problem is still there, I thought it was a little ugly to put an additional check, hope it will be fixed soon | 2022-08-24T15:35:45 | 2022-08-24T15:35:45 | {
"+1": 3
} | NONE |
vuejs | core | 1,226,987,352 | 4,294 | soerenmartius | > Many thanks to Evan You and the rest of the community for developing and maintaining Vue, but I'm sorry I have to comment because this issue has been around for a year and I don't mean to rush you to fix it, I just want to know if there's a temporary solution, thanks again for your efforts.
Have you seen this http... | 2022-08-25T09:05:17 | 2022-08-25T09:05:17 | {
"+1": 2
} | NONE |
vuejs | core | 1,227,211,700 | 6,532 | 2-5 | In plain TypeScript there is no problem with leaving the question mark in, so it is related to Vue & co somehow. There are no reported errors in the code below with `exactOptionalPropertyTypes: true`
```typescript
// test.ts
interface Props {
required: string
optional?: string | undefined
}
const p1: P... | 2022-08-25T12:47:25 | 2022-08-25T12:51:15 | {} | NONE |
vuejs | core | 1,217,656,825 | 4,339 | liweijian1 | 已换react，但是还是想问什么时候可以提供，至少vue2还提供了$destroy，vue3把这个api去掉了，还不提供删除keepalive缓存的方法，也不提供动态修改组件name的方法 | 2022-08-17T08:08:00 | 2022-08-17T08:08:00 | {
"+1": 2
} | NONE |
vuejs | core | 1,220,902,264 | 6,486 | 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). | 2022-08-19T17:10:42 | 2022-08-19T17:10:42 | {} | MEMBER |
vuejs | core | 1,221,123,108 | 5,474 | Hyperblaster | Any chance we can actually get this merged? | 2022-08-19T22:01:46 | 2022-08-19T22:01:46 | {
"+1": 1
} | NONE |
vuejs | core | 1,221,616,741 | 6,518 | djom202 | Ok nevertheless the docs don't mention nothing about that Into the migration part. Also the docs show multiples examples that works with the exactly the code that I shared with you, you should think in change that parts. | 2022-08-21T20:36:16 | 2022-08-21T20:36:16 | {} | NONE |
vuejs | core | 1,226,998,119 | 4,294 | myesn | > > Many thanks to Evan You and the rest of the community for developing and maintaining Vue, but I'm sorry I have to comment because this issue has been around for a year and I don't mean to rush you to fix it, I just want to know if there's a temporary solution, thanks again for your efforts.
>
> Have you seen thi... | 2022-08-25T09:13:07 | 2022-08-25T09:13:07 | {
"+1": 1
} | NONE |
vuejs | core | 1,227,133,618 | 6,532 | 2-5 | The problem also appears with simple properties, so it's not `modelValue` specific:
| 2022-08-25T11:27:39 | 2022-08-25T11:27:39 | {} | NONE |
vuejs | core | 1,219,097,861 | 6,493 | LinusBorg | This is all expected behavior. I'll move this to Q&A discussions so the community can help you understand. | 2022-08-18T06:44:13 | 2022-08-18T06:44:13 | {} | MEMBER |
vuejs | core | 1,221,258,502 | 2,513 | Kyon147 | @Hyperblaster this was the only thing that worked for me.
````
/*
* This fixes the current issue with event timestamps when running vue in a window or iframe.
* */
let ua = window.navigator.userAgent;
Object.defineProperty(window.navigator, 'userAgent', {
get: () => {
l... | 2022-08-20T08:31:14 | 2022-08-21T11:48:45 | {} | NONE |
vuejs | core | 1,221,705,875 | 6,517 | zhangenming | 
button 3,
left is 0
right is 1
What is expected?
1
1
1
1
What is actually happening?
left 1 0 0 1
right 1 0 1 1 | 2022-08-22T02:06:49 | 2022-08-22T02:07:32 | {} | CONTRIBUTOR |
vuejs | core | 1,223,937,288 | 6,536 | LinusBorg | there is no `this` in templates. `{{ _ymdhms }}` | 2022-08-23T11:31:10 | 2022-08-23T11:31:10 | {} | MEMBER |
vuejs | core | 1,225,965,998 | 6,540 | LinusBorg | If you don't want to nest these refs, maybe this is what you want?
https://sfc.vuejs.org/#eNqFk01v4yAQhv/KiEsTKTHyrvYSOVmtVr320DOXNCGNK/MhwGkly/+9M0Co3c+bgeF9Zx5eD+yftdWll2zDGn9wrQ3gZejtTuhWWeMCDODkCUY4OaPgBktvytF/o2zerzgtSAmPhT4Y7QMccOseL29JYqH7rlsK3fDkgw64CFLZbh8krgCac72769WDdNBqyJ1tYBiuSn8rnY7HseFYHC/FLtBgK1guE2z... | 2022-08-24T16:34:42 | 2022-08-24T16:34:42 | {} | MEMBER |
vuejs | core | 1,217,309,985 | 6,485 | edison1105 | you should add the focus method in Comp.vue. see [demo](https://sfc.vuejs.org/#eNp9Ue1qwzAMfBVjBmmhsf+HbFD2Gv6TJkrjEn9gKd2g9N0nu+koLRT8w2fpzrrTRe5jVOcFZCNb7JONJBBoiV/GWxdDIvEdXBRjCk5USmeQ2yvjW33r586VyTf4LZwBxm6ZSVyMF8KFxRMMm+0NCkGTRfWRYERlfVxIjaFfcLPN1avxfB60GRC4OHcEjIRoyzxM/jSysI0UOs+g/9vkTt5mr10X1QmDZ3flb6aUAhrZ3Kcxk... | 2022-08-17T00:37:11 | 2022-08-17T00:37:11 | {} | MEMBER |
vuejs | core | 1,217,825,552 | 6,483 | hcg1023 | I created a PR for the bug
delpoy preview in vue playground
https://deploy-preview-6491--vue-sfc-playground.netlify.app/#eNpNUF1Lw0AQ/CvLIaSFXoIggjWKpS/+AB/vJU02enpf3O21hpL/7iap1cedmZ2Z3bPYhVAeM4qtqFMbdSBISDk8K6dt8JHgDBF7GKGP3kLB0uJKvWGivWlSupBlRYy0E1J+puJRubpaTNmOB0IbTEPIE0B9yETewUtrdPv1pMQNWk2rwg4zUGzA4ekvYrVeKzE... | 2022-08-17T10:24:24 | 2022-08-17T10:33:58 | {} | CONTRIBUTOR |
vuejs | core | 1,221,500,082 | 2,513 | lidlanca | @semiaddict @Kyon147 the source of this snippet is from here
https://github.com/vuejs/core/issues/3933#issuecomment-1157259673
and it doesn't override the user-agent, it actually overrides the `match()` call of the userAgent
to minimize impact, and target the check vue does.
| 2022-08-21T08:42:42 | 2022-08-21T08:42:42 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,216,946,405 | 6,458 | woai3c | ```html
<component v-bind:is="opts.is">just "v-bind:is"</component>
<component is="h2" v-bind="opts">"is" set to different component, should be overriden by v-bind</component>
```
The first component tag is parsed as `_createBlock(_resolveDynamicComponent($setup.opts.is)`.
The second component tag is parsed as... | 2022-08-16T17:36:06 | 2022-08-16T17:36:49 | {} | NONE |
vuejs | core | 1,221,364,995 | 6,506 | dsonet | This introduces a temporary variable that is unnecessary and not as easy to read as the current code.
| 2022-08-20T16:47:57 | 2022-08-20T16:47:57 | {} | CONTRIBUTOR |
vuejs | core | 1,223,497,943 | 6,533 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 3941fa8ee9874438a03266ec48572187abb616bb |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-08-23T03:47:44 | 2022-08-23T03:47:44 | {} | NONE |
vuejs | core | 1,225,959,375 | 6,541 | LinusBorg | That wrror is correct. You cant v-bind without a value. And no, this is not supposed to work like v-if/v-else, so it doesnt. | 2022-08-24T16:29:23 | 2022-08-24T16:29:23 | {} | MEMBER |
vuejs | core | 1,227,342,838 | 6,222 | olddriverads | > 同样的错误！！！
请问有解决方案吗 | 2022-08-25T14:31:59 | 2022-08-25T14:31:59 | {} | NONE |
vuejs | core | 1,216,884,788 | 5,998 | segevfiner | I think a trigger for this is `flushPreFlushCbs` getting called recusively from inside the `activePreFlushCbs`, setting it to `null` and returning back to `flushPreFlushCbs`. `activePreFlushCbs` is a global, so it effects the caller `flushPreFlushCbs` as well. But I'm not sure on the exact combination of reactive effec... | 2022-08-16T16:40:13 | 2022-08-16T16:44:16 | {
"+1": 1
} | NONE |
vuejs | core | 1,221,664,218 | 6,517 | zhangenming | > Yes, const variables cannot be changed in Javascript. No, this is not a bug. Is part of the language
please reopen it.
first, at Stackblitz B, button 3 also is const , but is changed.
and, Stackblitz B and plyground A has produce different results, it is not a bug?
finally, const will complie to $setup.con... | 2022-08-22T00:49:01 | 2022-08-22T00:49:01 | {} | CONTRIBUTOR |
vuejs | core | 1,221,756,179 | 6,499 | fisker | The `\s` should be replaced with a RegExp allow all non-indentifier characters. | 2022-08-22T03:31:16 | 2022-08-22T03:31:16 | {} | CONTRIBUTOR |
vuejs | core | 1,223,419,531 | 3,529 | chaimHL | I encountered this problem again in version 3.27
我在3.27版本也遇到这个问题了 | 2022-08-23T01:47:59 | 2022-08-23T01:47:59 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.