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,550,590,878 | 8,341 | baiwusanyu-c | > Hi, I have fixed this in #8338 , I think the regex used in parse Name should be modified to fix this.
https://deploy-preview-8338--vue-sfc-playground.netlify.app/#eNqFUM1KxDAQfpUhCG1BNvealhXxJLiggpdcajorwTQJybQiy767ky3Kspe95Zt8fzMHcR/jZplRtEJlk2wkyEhzBDf4z04Lylr02tsphkTwEKYI+xQmqDaygCKttDfBZ4LgDUIHdQNdD4PDRLUWZahF... | 2023-05-17T02:18:08 | 2023-05-17T02:18:08 | {} | MEMBER |
vuejs | core | 1,550,943,136 | 8,018 | Merkushin-AY | @sxzz Why is component that has `defineModel` not working without `v-model` from outside?
Example from your demo:
`App.vue`:
```html
<script setup>
import Comp from './Comp.vue'
import {ref} from 'vue'
const count = ref(0)
</script>
<template>
<Comp /> <!-- NOT WORKING -->
<hr />
<Comp v-mode... | 2023-05-17T08:05:32 | 2023-05-17T08:05:32 | {} | NONE |
vuejs | core | 1,552,405,974 | 8,226 | yyx990803 | Sorry for missing this PR - a fix was landed in b2be75bad4ba70da1da6930eb914e51ce2c630b2
Thanks for your contribution regardless. | 2023-05-18T05:09:21 | 2023-05-18T05:09:21 | {} | MEMBER |
vuejs | core | 1,553,852,433 | 8,367 | yyx990803 | Also note: it is expected behavior for both props to be `false` here because they both are either boolean or contains boolean in its union: https://vuejs.org/guide/components/props.html#boolean-casting | 2023-05-19T00:37:38 | 2023-05-19T00:37:38 | {} | MEMBER |
vuejs | core | 1,554,218,902 | 8,301 | jenshoffmann1331 | Hi there! Had anyone of you time to investigate? 🙂 Using the new cool vue 3.3 interface features (that is importing interfaces from elsewhere) our jest suite is now broken too 🥲 Would really like to step forward with vue 3.3 🥳. | 2023-05-19T08:21:15 | 2023-05-19T08:21:15 | {} | NONE |
vuejs | core | 1,554,322,294 | 8,371 | edison1105 | duplicate of https://github.com/vuejs/core/issues/6123 ?
| 2023-05-19T09:52:59 | 2023-05-19T09:52:59 | {} | MEMBER |
vuejs | core | 1,550,588,131 | 8,341 | Alfred-Skyblue | Hi, I have fixed this in #8338 , I think the regex used in parse Name should be modified to fix this. | 2023-05-17T02:14:41 | 2023-05-17T02:14:41 | {} | MEMBER |
vuejs | core | 1,551,340,868 | 8,346 | pangao66 | the same question as https://github.com/vuejs/core/issues/8117
When using the 'v-bind css' function, expressions can be added.
```vue
<script>
const color = '255 0 0'
</script>
<style>
div {
background: v-bind('`rgb(${color})`');
}
</style>
``` | 2023-05-17T12:55:12 | 2023-05-17T12:59:01 | {
"+1": 1
} | NONE |
vuejs | core | 1,551,509,267 | 8,303 | arpowers | @xiaoxiangmoe which library has the bug? | 2023-05-17T14:29:04 | 2023-05-17T14:29:04 | {} | NONE |
vuejs | core | 1,552,569,879 | 8,353 | kirklin | +1 | 2023-05-18T06:51:08 | 2023-05-18T06:51:08 | {} | NONE |
vuejs | core | 1,552,577,935 | 8,353 | aurelsserban | +1 | 2023-05-18T06:55:51 | 2023-05-18T06:55:51 | {} | NONE |
vuejs | core | 1,550,566,213 | 8,332 | nooooooom | > Thanks for the PR - could you please add type tests in https://github.com/vuejs/core/blob/main/packages/dts-test/setupHelpers.test-d.ts?
I'm planning to do this! | 2023-05-17T01:41:17 | 2023-05-17T01:41:17 | {} | NONE |
vuejs | core | 1,550,950,044 | 8,310 | Dobril | After I update to 3.3.2 same error occurred:
When I use interface instead of type there are error too:
... | 2023-05-17T08:10:34 | 2023-05-17T08:11:50 | {} | NONE |
vuejs | core | 1,551,529,169 | 4,662 | soultice | > Any update, or is it time to ditch Vue and switch to Svelte?
Oddly enough, Svelte has the exact same issue: https://github.com/sveltejs/svelte/issues/4274 where there is talk about switching to Vue.
| 2023-05-17T14:41:15 | 2023-05-17T14:41:15 | {
"laugh": 18
} | NONE |
vuejs | core | 1,551,539,924 | 4,662 | haoqunjiang | > Should we by any chance expect a fix anytime soon
This issue is labeled as "p4-important".
I can't promise, but in an ideal world, the priority queue could be like this:
1. Fixing v3.3 regressions
2. p4 issues in core / important issues in other core repos / other planned 3.4 features
3. p3 issues
4. … | 2023-05-17T14:47:25 | 2023-05-17T14:58:04 | {
"+1": 12
} | MEMBER |
vuejs | core | 1,550,586,352 | 8,332 | nooooooom | This feature is imperfect because I do not know how to change the parameter type for an overloaded function. 🤔 | 2023-05-17T02:11:24 | 2023-05-18T03:39:05 | {} | NONE |
vuejs | core | 1,552,448,574 | 8,353 | BARNZ | I'm seeing this as well after upgrading my codebase to vue 3.3 - for me it seems to be caused by any components that do some sort of `v-bind="$attrs"`
Is this not something that is supported anymore?
![image](https://gi... | 2023-05-18T05:47:49 | 2023-05-18T05:47:49 | {
"+1": 2
} | NONE |
vuejs | core | 1,552,608,558 | 8,353 | HENANWADE | I have the same error, $attrs | 2023-05-18T07:12:19 | 2023-05-18T07:12:19 | {} | NONE |
vuejs | core | 1,553,766,649 | 4,662 | mrcego | > Since this problem has caused me some troubles, and I don’t know when the official vue will fix it, as a temporary solution, I made my PR into a vite plugin and injected the code through compilation to temporarily solve this problem problem, but for more complex scenarios still need testing, if you happen to need it ... | 2023-05-18T23:08:48 | 2023-05-18T23:08:48 | {
"+1": 1
} | NONE |
vuejs | core | 1,554,258,249 | 8,352 | pikax | There's a couple issues on the typescript
Here's running on the latest version of vue (3.3.4)
<img width="769" alt="image" src="https://github.com/vuejs/core/assets/4620458/a9cb3dbf-29aa-4ada-8b2a-a71a28a9fb85">
Some changes to the files:
```html
<template>
<div>
<div v-for="item of data">
<s... | 2023-05-19T08:57:01 | 2023-05-19T08:57:01 | {} | MEMBER |
vuejs | core | 1,550,537,181 | 8,317 | yyx990803 | Closing as duplicate of #8314, but thanks for the PR. | 2023-05-17T00:58:11 | 2023-05-17T00:58:11 | {} | MEMBER |
vuejs | core | 1,551,156,755 | 7,556 | niksy | Any updates on this? What can we do to get this merged? In the meantime, for those looking for a quick fix, use https://github.com/ds300/patch-package and patch local version of Vue. | 2023-05-17T10:41:15 | 2023-05-17T10:41:15 | {} | NONE |
vuejs | core | 1,551,781,596 | 7,342 | seahindeniz | How can we prioritize it? Seems like it already has PRs waiting in line and no need to wait for more | 2023-05-17T17:14:52 | 2023-05-17T17:14:52 | {} | NONE |
vuejs | core | 1,552,333,682 | 8,332 | yyx990803 | After testing this locally, it seems this doesn't actually fix vuejs/language-tools#3197 - the actual issue seems to be in Volar, not in the types of `defineEmits`.
The kebab-case and camelCase conversions are mostly meant for parent consumers. Locally, `defineEmits` should just keep the exact event names for consis... | 2023-05-18T02:53:18 | 2023-05-18T03:39:06 | {} | MEMBER |
vuejs | core | 1,552,510,351 | 8,353 | ns265422 | +1
| 2023-05-18T06:23:29 | 2023-05-18T06:23:29 | {} | NONE |
vuejs | core | 1,552,574,164 | 8,353 | daehyun-thevc | I also have this issue. in v3.3.3 caused by wrong bundle `node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js`
<img width="856" alt="image" src="https://github.com/vuejs/core/assets/87633241/a656231d-5651-45a7-a06a-8daab354ae74">
| 2023-05-18T06:53:40 | 2023-05-18T06:53:51 | {} | NONE |
vuejs | core | 1,552,601,568 | 8,353 | StrangeXin | +1 | 2023-05-18T07:08:39 | 2023-05-18T07:08:39 | {} | NONE |
vuejs | core | 1,552,613,401 | 8,357 | BARNZ | Yep same for me. Related https://github.com/vuejs/core/issues/8353 | 2023-05-18T07:14:54 | 2023-05-18T07:14:54 | {} | NONE |
vuejs | core | 1,552,629,693 | 8,357 | edison1105 | caused by https://github.com/vuejs/core/pull/8314/files | 2023-05-18T07:23:56 | 2023-05-18T07:23:56 | {} | MEMBER |
vuejs | core | 1,552,666,162 | 8,353 | kirklin | #8358 | 2023-05-18T07:43:42 | 2023-05-18T07:43:42 | {} | NONE |
vuejs | core | 1,553,884,364 | 8,368 | Boux | I understand, I will try posting this in the `@vitejs/plugin-vue` issues page
**EDIT**: I posted it here: https://github.com/vitejs/vite-plugin-vue/issues/178
Here's the version numbers just in case
`@vitejs/plugin-vue`: `4.2.3` (works with vue 3.2, but not 3.3)
`vite`: `4.3.8` (works with vue 3.2, but not 3.3)
... | 2023-05-19T01:25:32 | 2023-05-19T02:05:19 | {} | NONE |
vuejs | core | 1,550,535,704 | 8,303 | yyx990803 | Probably related to our addition of `vue/jsx-runtime`? Although I have no idea how this could cause tsx to compile things differently. Closing as I don't think there's anything actionable on our side (happy to reopen if otherwise) | 2023-05-17T00:55:48 | 2023-05-17T00:55:48 | {} | MEMBER |
vuejs | core | 1,550,536,921 | 8,315 | yyx990803 | Thanks for the PR, please note this isn't the right fix as it is intentional to preserve the process env check in the generated code. | 2023-05-17T00:57:48 | 2023-05-17T00:57:48 | {} | MEMBER |
vuejs | core | 1,551,514,012 | 7,342 | haoqunjiang | I'm afraid we still need some time before we get to this issue.
There are too many open issues and PRs.
The current priorities, in my opinion:
1. v3.3 regressions
2. p4 issues
3. p3 issues | 2023-05-17T14:31:54 | 2023-05-17T14:31:54 | {} | MEMBER |
vuejs | core | 1,551,087,129 | 8,332 | nooooooom | > This feature is imperfect because I do not know how to change the parameter type for an overloaded function. 🤔
All usage scenarios are currently supported! | 2023-05-17T09:48:23 | 2023-05-18T03:39:05 | {} | NONE |
vuejs | core | 1,552,345,356 | 8,332 | nooooooom | The original intention of this PR is to keep defineEmits consistent in logic and type. Still, from the perspective of developing components, it will undoubtedly confuse the code specification of components.
I was going in the wrong direction for vuejs/language-tools#3197; we should enhance type hints on component us... | 2023-05-18T03:13:37 | 2023-05-18T03:39:06 | {} | NONE |
vuejs | core | 1,552,358,779 | 8,332 | yyx990803 | I think we can agree to close this one then? Regardless, thanks for your effort on the PR 👍 | 2023-05-18T03:41:01 | 2023-05-18T03:41:01 | {} | MEMBER |
vuejs | core | 1,552,670,985 | 6,028 | will-YT | I have the same problem | 2023-05-18T07:46:24 | 2023-05-18T07:46:24 | {} | NONE |
vuejs | core | 1,590,497,806 | 8,556 | haoqunjiang | /ecosystem-ci run | 2023-06-14T05:33:58 | 2023-06-14T05:33:58 | {} | MEMBER |
vuejs | core | 1,595,986,036 | 8,474 | edison1105 | The name of the slot is a special attribute. It is handled specially during compilation, so it cannot be added dynamically. | 2023-06-18T06:31:33 | 2023-06-18T06:31:33 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,599,979,211 | 8,612 | Neverflow |
> > You can only use the current file's type or interface at present.
>
> I dont follow, you can use the interface like this in the sfc just fine. However, trying to use it for `defineProps` fails and it's not immediately clear to the programmer why you can use it like shown below but not use it for defining p... | 2023-06-21T02:30:21 | 2023-06-21T02:30:21 | {} | NONE |
vuejs | core | 1,590,456,336 | 8,542 | Justineo | This affects all Vue components inside an app including third-party ones. I'd say setting `inheritAttrs: false` at global level has a fairly big chance to break some of them but the problem it brings can be very hard to identify and locate. | 2023-06-14T04:38:34 | 2023-06-14T04:38:34 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,592,310,848 | 8,575 | alecgibson | Okay looks like I should [RTFM](https://vuejs.org/guide/typescript/overview.html#note-on-vue-cli-and-ts-loader).
Anyone else migrating to Vue 3 with this build: you should skip type checking in `ts-loader` with `transpileOnly: true` and add type checking as a separate step using `vue-tsc`. | 2023-06-15T03:53:31 | 2023-06-15T03:53:31 | {} | NONE |
vuejs | core | 1,595,977,155 | 8,579 | edison1105 | This is caused by the form's input event being executed earlier than the select's change event.
- The first time the select is selected, `changed=true` causes the component to be re-rendered and the select is reset. When the select's change event (v-model is based on the change event) is executed select is already bac... | 2023-06-18T06:12:37 | 2023-06-18T06:12:37 | {} | MEMBER |
vuejs | core | 1,596,107,135 | 8,581 | phonty29 | It changes color no matter is comment there or not | 2023-06-18T11:13:35 | 2023-06-18T11:13:35 | {} | NONE |
vuejs | core | 1,599,145,492 | 8,617 | xrsdww | I saw some workarounds like [this](https://github.com/vueComponent/ant-design-vue/blob/main/components/vc-checkbox/Checkbox.tsx#L76) in mature UI libraries | 2023-06-20T16:41:21 | 2023-06-20T16:43:54 | {
"confused": 1
} | NONE |
vuejs | core | 1,599,974,584 | 8,615 | sxzz | It's by design.
Like `defineProps`, Vue need `Boolean` type for runtime usage. So either add runtime type property `type: [String, Number, Boolean] as PropType<RadioModelValue>`, or add a type generic `defineModel<RadioModelValue>()`
---
In production mode, runtime type checking will be skipped, so only `Boole... | 2023-06-21T02:23:48 | 2023-06-21T02:26:18 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,600,778,142 | 7,874 | ken1987 | try [`app.config.errorHandler`](https://vuejs.org/api/application.html#app-config-errorhandler) | 2023-06-21T12:51:27 | 2023-06-21T12:51:27 | {} | NONE |
vuejs | core | 1,590,498,121 | 8,556 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/5263453626)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/5263453626/jobs/9513612995) | :white_check_mark: success |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/52634536... | 2023-06-14T05:34:24 | 2023-06-14T05:41:42 | {} | CONTRIBUTOR |
vuejs | core | 1,590,703,985 | 8,376 | shengxinjing | You could try upgrading your typescript to the latest 5.1.3 | 2023-06-14T08:17:22 | 2023-06-14T08:18:39 | {} | CONTRIBUTOR |
vuejs | core | 1,591,540,757 | 8,574 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 324085c5576939fc811bd374b4cc09e2bb70b108 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-06-14T15:59:34 | 2023-06-14T15:59:34 | {} | NONE |
vuejs | core | 1,594,963,415 | 8,577 | sxzz | Try `export class VueSamplePlugin implements Pick<Plugin, keyof Plugin>` | 2023-06-16T16:40:27 | 2023-06-16T16:40:27 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,599,031,679 | 8,613 | Neverflow | This writing cause infinite loop | 2023-06-20T15:33:52 | 2023-06-20T15:33:52 | {
"+1": 1
} | NONE |
vuejs | core | 1,599,999,693 | 8,612 | Neverflow | > > You can only use the current file's type or interface at present.
>
> I dont follow, you can use the interface like this in the sfc just fine. However, trying to use it for `defineProps` fails and it's not immediately clear to the programmer why you can use it like shown below but not use it for defining props. ... | 2023-06-21T02:58:45 | 2023-06-21T02:58:45 | {} | NONE |
vuejs | core | 1,587,401,422 | 8,556 | sxzz | /ecosystem-ci run | 2023-06-12T14:00:44 | 2023-06-14T05:41:56 | {} | MEMBER |
vuejs | core | 1,591,657,345 | 8,575 | alecgibson | I don't know if it's possible to just add a `@ts-ignore` directive or something to the injected code? | 2023-06-14T16:57:48 | 2023-06-14T16:57:48 | {} | NONE |
vuejs | core | 1,596,126,597 | 8,581 | edison1105 | > It changes color no matter is comment there or not
The root cause is the scopeId is missing | 2023-06-18T12:22:31 | 2023-06-18T12:22:31 | {} | MEMBER |
vuejs | core | 1,596,185,324 | 8,572 | liulinboyi | Maybe you can find the solution in the [typescript jsx](https://www.typescriptlang.org/docs/handbook/jsx.html). | 2023-06-18T15:35:14 | 2023-06-18T15:35:14 | {} | MEMBER |
vuejs | core | 1,590,971,923 | 8,409 | yyx990803 | Yes, so in our case `auto` would be effectively equal to `0s` - the fix would still be a safety net for users using Chrome Canary right now, or other browsers that may interpret the spec differently and do not implement the compat behavior like Chrome does. | 2023-06-14T11:00:07 | 2023-06-14T11:00:07 | {} | MEMBER |
vuejs | core | 1,593,447,141 | 8,577 | shigeyf | @Alfred-Skyblue, thanks for your comments.
Yes, that's what I am doing for my plugin module.
There is a type definition of "**Plugin**" in Vue types. But. it's not usable. Then, why is it there?
So, that's why I came here to raise this issue. I am seeking a solution with leveraging the Vue types in the box, rather... | 2023-06-15T17:12:20 | 2023-06-15T17:15:12 | {} | NONE |
vuejs | core | 1,596,148,242 | 8,592 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 1c147956466fdc596598f836b0a670e5db6b0b1f |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-06-18T13:28:45 | 2023-06-18T13:28:45 | {} | NONE |
vuejs | core | 1,596,330,592 | 8,474 | zhangenming | > The name of the slot is a special attribute. It is handled specially during compilation, so it cannot be added dynamically.
At least this should work, It can be done at compile time
```<slot
v-bind="{
name: customNamee
}"
></slot>``` | 2023-06-19T00:41:14 | 2023-06-19T00:41:32 | {} | CONTRIBUTOR |
vuejs | core | 1,600,641,029 | 8,611 | seggewiss | > This seems to be a duplicate of #2981
Yes that seems to be the case. Thank you for pointing out 💙 | 2023-06-21T11:09:52 | 2023-06-21T11:09:52 | {
"heart": 1
} | NONE |
vuejs | core | 1,590,868,437 | 8,409 | sxzz | @yyx990803 96c76facb7de37fc241ccd55e121fd60a49a1452 won't fix this issue. `auto` doesn't equal to `0`. The specific value will be calculated by browser. | 2023-06-14T09:50:37 | 2023-06-14T09:50:37 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,590,959,058 | 8,409 | yyx990803 | AFAIK `auto` is only meant for group animations and scroll animations, and is considered to be same as 0 for "normal animations", which is currently what Vue transitions are used for.
The actual use case for `auto` is still yet to be implemented by the browser, and we can consider how to properly support those cases... | 2023-06-14T10:51:39 | 2023-06-14T10:51:39 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,590,963,396 | 8,409 | Justineo | Chrome is about to implement backward compat for Vue:
https://bugs.chromium.org/p/chromium/issues/detail?id=1452130#c5
It seems that the breakage won't land in the stable channel. | 2023-06-14T10:54:48 | 2023-06-14T10:54:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,592,238,304 | 8,527 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 9492dff43c4858e28b972c761ee323f512e18d33 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-06-15T02:16:48 | 2023-06-15T04:31:56 | {} | NONE |
vuejs | core | 1,596,166,871 | 1,745 | rendomnet | I have this error.
Vue3 error log is mess. Cant event udnerstand where it happens | 2023-06-18T14:23:41 | 2023-06-18T14:24:12 | {
"+1": 1
} | NONE |
vuejs | core | 1,597,062,997 | 7,568 | yingpengsha | @sxzz PTAL
| 2023-06-19T12:04:15 | 2023-06-19T12:04:15 | {} | NONE |
vuejs | core | 1,599,037,948 | 8,609 | goncharof | > see here
very very thank You! I need to delve deeper into real project in order to eliminate such problems | 2023-06-20T15:37:36 | 2023-06-20T15:37:36 | {} | NONE |
vuejs | core | 1,591,068,915 | 7,713 | incutonez | Just to add to this, and maybe it's my misunderstanding of how v-bind works internally, but [this example](https://play.vuejs.org/#eNptkD1uAyEUhK8yeVUiBW+fYEtRmhwgJQ1ZswoSf4K3TmH57gFWa69kUzHwDcybM32ktDvNht5IljHbxCiG53RQwfoUM+Mz+oQpRw9Fu6Gpxit6V0EOi6XCVbDxyWk2VQGy24a6l8P1gl5p9bf/NgbFUme2o2tCPgmB719bUFxkTNq6Ajvhz2AOY/TeB... | 2023-06-14T12:08:45 | 2023-06-14T12:09:27 | {} | NONE |
vuejs | core | 1,592,487,499 | 8,474 | zhangenming | v-bind={key:x, ref:x}
Both key and ref are effective, so it is unreasonable for `name` alone not to be effective
| 2023-06-15T07:11:10 | 2023-06-15T07:11:10 | {} | CONTRIBUTOR |
vuejs | core | 1,598,906,968 | 8,609 | LinusBorg | It's called with Options API as well, [see here](https://play.vuejs.org/#eNqNVMGO2jAQ/RUrF0BLEu2ypyggVuqlh/bErenBGw/EJbEj2wEqxL93bMdJ2NJVIwTMzJs3b8bjXKO3tk1OHURZlOtS8dZsCsGbVipDdpLJrwYasleyIbMkDQ6bMCsEIYWAi4My2NOuNuRqvaXEfAHC6IxcR5bb0gYZNXS+8EBCFJhOiWARIuBs8Tu4mIzMZi7DPgadyPYj2GRMsQ9nGXkewC6BmxqQ4oskpgLCuK5AO83+8WL+QfX... | 2023-06-20T14:30:16 | 2023-06-20T14:31:04 | {
"heart": 3
} | MEMBER |
vuejs | core | 1,600,559,706 | 8,131 | jcarlosroldan | Is there any update / some way I can help to fix it? | 2023-06-21T10:06:50 | 2023-06-21T10:06:50 | {} | NONE |
vuejs | core | 1,591,540,327 | 8,574 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 324085c5576939fc811bd374b4cc09e2bb70b108 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-06-14T15:59:19 | 2023-06-14T15:59:19 | {} | NONE |
vuejs | core | 1,592,197,844 | 8,577 | Alfred-Skyblue | In Vue, the Plugin interface is a union type. A class cannot implement a union type, so you can define its custom type.
```typescript
interface IPlugin<T = any> {
install: (app: App, options: T) => any
}
class MyPlugin implements IPlugin<Record<name,string>> {
install(app: App, options: Record<name,string... | 2023-06-15T01:30:00 | 2023-06-15T01:32:23 | {} | MEMBER |
vuejs | core | 1,596,196,723 | 8,572 | liulinboyi | Maybe the Typescript or the Volar has update, so i suggest you can find the solution in the [typescript jsx](https://www.typescriptlang.org/docs/handbook/jsx.html) or the [Volar release log](https://github.com/vuejs/language-tools/releases) or the both repo issue. | 2023-06-18T16:23:05 | 2023-06-18T16:23:05 | {} | MEMBER |
vuejs | core | 1,597,456,973 | 8,577 | shigeyf | @sxzz
Thanks for sharing the workaround. | 2023-06-19T16:21:52 | 2023-06-19T16:21:52 | {} | NONE |
vuejs | core | 1,599,048,085 | 8,612 | Neverflow | You can only use the current file's type or interface at present. | 2023-06-20T15:42:35 | 2023-06-20T15:42:35 | {} | NONE |
vuejs | core | 1,600,110,710 | 8,618 | edison1105 | this is planned in Vapor mode | 2023-06-21T05:34:10 | 2023-06-21T05:34:10 | {} | MEMBER |
vuejs | core | 1,595,704,262 | 8,592 | zqran | > `defaults` should not be hoisted if it's used by other assignments.
Ok, with this situation in mind, I think there might be a few things to confirm:
1. `defaults.foo = 'xxx'` -> set property
2. `defaults = {}` -> set new value
3. `defaults.xxx` -> read property
4. `someFunc(defaults)` -> as parameter | 2023-06-17T10:37:13 | 2023-06-17T10:37:13 | {} | CONTRIBUTOR |
vuejs | core | 1,596,127,759 | 5,007 | ms2d | @LinusBorg this looks like a bug. As I understand it, the entire purpose of `<style scoped>` is to _prevent_ styles from being applied globally... so shouldn't @olemarius 's request be the default behavior? | 2023-06-18T12:27:09 | 2023-06-18T12:27:09 | {} | NONE |
vuejs | core | 1,596,346,553 | 8,572 | laterdayi | Thank you. I think it's volar
| 2023-06-19T01:17:43 | 2023-06-19T01:17:43 | {} | NONE |
vuejs | core | 1,596,951,245 | 8,112 | henkvhest | Ah good find, seems like it's intentional indeed! I'll close this one | 2023-06-19T10:44:11 | 2023-06-19T10:44:11 | {} | NONE |
vuejs | core | 1,598,703,902 | 8,609 | Alfred-Skyblue | Due to the update in `todos`, the elements are being re-rendered, and `TodoItem` relies on `todos`. | 2023-06-20T12:45:51 | 2023-06-20T12:45:51 | {} | MEMBER |
vuejs | core | 1,598,945,614 | 8,613 | Alfred-Skyblue | This writing is incorrect. The render function depends on count, and every time the render function is executed, it will run data.slot. Within data.slot, count is changed, causing the render function to be executed again, resulting in an infinite loop. | 2023-06-20T14:51:29 | 2023-06-20T14:51:29 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,599,130,045 | 8,609 | goncharof | if anyone could explain how to avoid re-rendering in this example, i would really appreciate it, thanks!
https://play.vuejs.org/#eNqNUtuOmzAQ/ZURqypESqDceqFk1fahf9CnZR8IGGrF2JZtoo0Q/96xYSkb7UMfQMw5M8OcMzN6P6QMrgPxcq/QtaLSgCZmkI8lp70UysCvite3n4MxgkOrRA+7INxgtnhXcoAlfQRFWpiW1FfSPrXg2uB74AZONst/et6/JakhvUbyyUIAI696ksMu... | 2023-06-20T16:33:18 | 2023-06-20T16:49:12 | {} | NONE |
vuejs | core | 1,600,256,141 | 8,612 | Disservin | Oh great well somehow missed that completely, only annoying thing is that it's still missing from the typescript declarations. Ty for the help | 2023-06-21T06:27:13 | 2023-06-21T06:27:13 | {} | CONTRIBUTOR |
vuejs | core | 1,600,801,207 | 8,083 | MaxHammermann | > @yyx990803 should we expect this feature in `vue@2.7`? thank you!
This would be very nice, although I couldn't think it will be.
Is there a place where I can look up what went into the compat build 2.7 and if there will be another version > 2.7.14? | 2023-06-21T13:06:04 | 2023-06-21T13:06:04 | {} | NONE |
vuejs | core | 1,590,532,705 | 8,570 | yyx990803 | Vue's native element list does not include any of the deprecated elements, and `<font>` is one of them.
If you need Vue to parse it as a native element, configure `isCustomElement` following these instructions: https://vuejs.org/guide/extras/web-components.html#skipping-component-resolution | 2023-06-14T06:10:17 | 2023-06-14T06:10:17 | {} | MEMBER |
vuejs | core | 1,590,535,985 | 8,567 | yyx990803 | You should do it in `mounted` instead of `created`. In `created` the component hasn't rendered the `#my-svg` node yet.
Note: this is a generic usage question, please make sure to only open issues if you are certain it's a bug, and use the [Discussions](https://github.com/vuejs/core/discussions) tab for questions. | 2023-06-14T06:13:52 | 2023-06-14T06:13:52 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,590,762,150 | 6,908 | off-border | Also having this issue during vue3 migration | 2023-06-14T08:52:08 | 2023-06-14T08:52:08 | {
"+1": 1
} | NONE |
vuejs | core | 1,594,815,995 | 8,286 | Disservin | I agree with the comments above me. I recently ran into this issue when trying to extend from a global interface.
You can find the code here:
https://github.com/Disservin/vue-ts-error
I personally think this case is rather common, where you have a global interface but a component needs to extend it because has ... | 2023-06-16T14:47:02 | 2023-06-16T14:49:11 | {} | CONTRIBUTOR |
vuejs | core | 1,598,377,031 | 5,657 | gbyesiltas | Yeah I'm getting this as well and moving all the root level `v-if`s would be quite some work for our project so would be great if it could be addressed :,) Also, we are getting some `Cannot destructure property 'bum' of 'Y' as it is null.` errors from the `unmountComponent` function which I doubt may be related?
<im... | 2023-06-20T08:52:17 | 2023-06-20T08:52:17 | {
"+1": 1
} | NONE |
vuejs | core | 1,591,050,003 | 8,518 | Chuuone | Closing as this issue is directly related to https://github.com/vuejs/language-tools/issues/2709 | 2023-06-14T11:55:50 | 2023-06-14T11:55:50 | {} | NONE |
vuejs | core | 1,594,964,637 | 8,587 | sxzz | Duplicate of #8409. Please wait the next patch version. | 2023-06-16T16:41:38 | 2023-06-16T16:41:38 | {} | MEMBER |
vuejs | core | 1,595,813,285 | 3,883 | AliaksandrFitzner | Hello Guys! Con you please confirm that compat build not working with vuex 3. Thx a lot! | 2023-06-17T17:31:19 | 2023-06-17T17:31:19 | {} | NONE |
vuejs | core | 1,596,394,499 | 8,409 | edison1105 | fixed via https://chromium-review.googlesource.com/c/chromium/src/+/4607459
| 2023-06-19T02:30:58 | 2023-06-19T02:30:58 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,596,438,981 | 8,112 | mannymu | I use webpack and have the same problem | 2023-06-19T03:28:27 | 2023-06-19T03:28:27 | {} | NONE |
vuejs | core | 1,597,212,568 | 8,592 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 1c147956466fdc596598f836b0a670e5db6b0b1f |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-06-19T13:39:37 | 2023-06-19T13:39:37 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.