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,206,305,206 | 6,391 | posva | Same as https://github.com/vuejs/core/issues/4680#issuecomment-927166733 | 2022-08-05T10:41:04 | 2022-08-05T10:41:04 | {} | MEMBER |
vuejs | core | 1,206,798,302 | 4,662 | murphybob | Hey @soultice that's great news but unfortunately I won't be able to try it out for a bit anyway, I just left my job and am awaiting starting the next one so I'm between dev laptops atm! (Yeah my personal one sucks I know I should do something about that lol but company ones are always better because I'm a total cheaps... | 2022-08-05T19:40:13 | 2022-08-05T19:40:13 | {} | NONE |
vuejs | core | 1,196,587,043 | 6,314 | nbaizaq | In my case I wanted K would be `string` and value T would be `Function` type. Currently, when I inject the function it doesn't provide typings and show errors that the injected object is type of `{}`, but I wanted it to be `Function` | 2022-07-27T11:06:47 | 2022-07-27T11:06:47 | {} | NONE |
vuejs | core | 1,198,921,173 | 6,366 | Tyh2001 | 组件自己通过文件名推导出来的组建名感觉尽可以适用于调试工具的正常使用，获取组件的名称为 `undefined`，所以感觉自动推断出来的好像并没有什么用，还是需要手动设置
The component name derived from the file name itself feels that it can be used for the normal use of debugging tools. The name of the component obtained is undefined, so it seems that the automatically inferred name is useless, and ... | 2022-07-29T06:19:20 | 2022-07-29T06:19:20 | {} | NONE |
vuejs | core | 1,199,018,906 | 4,294 | wangrongding | > 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.
That's all for now🫡 | 2022-07-29T08:32:50 | 2022-07-29T08:32:50 | {
"+1": 1,
"-1": 1
} | NONE |
vuejs | core | 1,200,738,210 | 6,389 | jacekkarczmarczyk | Thanks for the solution, wouldn't it be a breaking change though? I mean technically it isn't, as prior to 3.x/2.7 there was no `ref()` and `watch()`, but what is the reason for being it inconsistent with options API?
Working options API examples: [2.7.8](https://codepen.io/jkarczm/pen/BarJVmj?editors=0010), [3.2.2... | 2022-08-01T05:48:07 | 2022-08-01T05:48:07 | {} | CONTRIBUTOR |
vuejs | core | 1,200,895,509 | 6,222 | feiyayshx | same error | 2022-08-01T08:37:46 | 2022-08-01T08:37:46 | {} | NONE |
vuejs | core | 1,201,419,667 | 6,201 | MichealPearce | I have been experiencing a similar issue on v3.2.37. I am using vite & vite-ssr. The issue seems a bit different for me however.
<details>
<summary>I have a component that looks like this</summary>
```vue
<script lang="ts">
import { provideTheme } from '@social/client/themes'
import globalTheme from '@social/... | 2022-08-01T16:19:35 | 2022-08-01T16:19:35 | {} | NONE |
vuejs | core | 1,203,546,049 | 6,392 | Blackman99 | > I see the point for a now you can use https://vueuse.org/core/usevmodel/#usevmodel
I know this function. Even with this I still need to repeatedly declare `modelValue` prop and `update:modelValue` with `defineProps` and `defineEmits` | 2022-08-03T06:40:04 | 2022-08-03T06:40:04 | {
"confused": 1
} | NONE |
vuejs | core | 1,203,741,394 | 3,791 | SinBirb | Can this also be merged into @vue/composition-api, so we can use it with Vue 2.6 + Pinia? | 2022-08-03T10:01:05 | 2022-08-03T10:01:05 | {
"heart": 2
} | NONE |
vuejs | core | 1,196,499,502 | 6,320 | Harm-Nullix | Any updates about approval? | 2022-07-27T09:39:01 | 2022-07-27T09:39:01 | {
"eyes": 1
} | NONE |
vuejs | core | 1,197,315,411 | 6,358 | lidlanca | double triggering the effect, might be something that can be fixed, but perhaps with a different approach.
Returning the ref when you pass it through `reactive()`
might not be expected or desired.
```js
let myRef = ref(0)
const myReactive = reactive(myRef)
console.log(isReactive(myReactive)) // actual:false.... | 2022-07-27T20:11:17 | 2022-07-27T20:11:17 | {} | CONTRIBUTOR |
vuejs | core | 1,198,842,786 | 6,366 | WhiteCoffee9834 | > 那样可以实现递归组件吗？ @AlanSean
https://staging-cn.vuejs.org/api/sfc-script-setup.html#recursive-components | 2022-07-29T03:29:32 | 2022-07-29T03:30:50 | {
"+1": 1
} | NONE |
vuejs | core | 1,198,903,129 | 6,366 | sxzz | Maybe you should read [this discussion](https://github.com/vuejs/rfcs/discussions/430#discussioncomment-2333745). | 2022-07-29T05:46:25 | 2022-07-29T05:46:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,200,123,811 | 5,882 | Lutymane | > You can use TroisJS as an example: https://github.com/troisjs/trois/blob/master/src/core/Renderer.ts
Hello, they don't seem to be using Vue's custom renderer at all. And the file you referenced seems to be just a wrapper for WebGLRenderer. Which is also strange, since [docs](https://vuejs.org/guide/extras/ways-of-... | 2022-07-30T09:26:47 | 2022-07-30T09:26:47 | {} | NONE |
vuejs | core | 1,200,470,713 | 6,384 | sealor | @lidlanca Thanks in advance! | 2022-07-31T17:55:38 | 2022-07-31T17:55:38 | {} | NONE |
vuejs | core | 1,200,596,882 | 6,387 | Zippowxk | The <Transition> Component works fine, the behavior is the logics of transform | 2022-08-01T02:01:49 | 2022-08-01T02:01:49 | {} | NONE |
vuejs | core | 1,204,470,254 | 4,294 | EmmanuelQ | As someone coming from a strong React + Typescript team I must saying not being able to have shareable reusable types across components is quite a let down. Especially when it comes to things like being able to directly use swagger schema generated Typescript definitions for which I've done a lot of in the past. Is the... | 2022-08-03T20:51:28 | 2022-08-03T20:51:28 | {
"+1": 4
} | NONE |
vuejs | core | 1,204,932,111 | 6,405 | chenyurou | > See @a145789's [comment](https://github.com/vuejs/core/issues/6405#issuecomment-1204912317).
请问，是出于什么原因，又改回数组 | 2022-08-04T08:26:07 | 2022-08-04T08:26:07 | {} | NONE |
vuejs | core | 1,200,362,088 | 6,384 | lidlanca | svg attributes are case sensitive
update to refX and refY
```html
<marker id="marker" markerWidth="8" markerHeight="8" refX="4" refY="4">
``` | 2022-07-31T06:53:52 | 2022-07-31T06:53:52 | {} | CONTRIBUTOR |
vuejs | core | 1,201,922,262 | 6,356 | HydenLiu | I had the same problem | 2022-08-02T01:49:28 | 2022-08-02T01:49:28 | {} | NONE |
vuejs | core | 1,202,204,805 | 6,356 | HydenLiu | Can you help me think about which framework, it seems to be related to the i18n problem, thank you very much 🙏 | 2022-08-02T08:52:17 | 2022-08-02T08:52:17 | {} | NONE |
vuejs | core | 1,203,158,740 | 5,401 | lidlanca | related RFC discussion
https://github.com/vuejs/rfcs/discussions/451 | 2022-08-02T20:01:03 | 2022-08-02T20:01:03 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,207,216,137 | 6,416 | chiboreache | [console-export-2022-8-6_16-34-22.txt](https://github.com/vuejs/core/files/9275131/console-export-2022-8-6_16-34-22.txt)
| 2022-08-06T13:34:46 | 2022-08-06T13:34:46 | {} | NONE |
vuejs | core | 1,197,610,377 | 6,358 | hubvue | https://github.com/vuejs/core/blob/a95554d35c65e5bfd0bf9d1c5b908ae789345a6d/packages/reactivity/src/computed.ts#L55-L64
@lidlanca There is also handling of duplicate triggers in computed, but this does not seem to fix the problem, it only solves the dependency collection on the `_value` attribute, but the `value` attr... | 2022-07-28T03:24:32 | 2022-07-28T03:24:32 | {} | NONE |
vuejs | core | 1,198,304,223 | 6,369 | mfrank3 | Good idea, it would be really helpfull. | 2022-07-28T15:23:02 | 2022-07-28T15:23:02 | {} | NONE |
vuejs | core | 1,198,662,597 | 6,358 | lidlanca | the types seem to be inferred correctly ( unless I miss understand your point)
there is no `reactive` type per say, as it is basically a transparent proxy with the exception of nested refs that get unwrap... | 2022-07-28T21:43:53 | 2022-07-28T21:43:53 | {} | CONTRIBUTOR |
vuejs | core | 1,203,586,890 | 6,392 | Blackman99 | This means the built-in macros need to be used outside a SFC file. That also a solution. I don't know which can be easy to implement. | 2022-08-03T07:27:48 | 2022-08-03T07:27:48 | {
"heart": 1
} | NONE |
vuejs | core | 1,203,606,214 | 5,940 | SimmeNilsson | Was looking for something like this. Any idea when we could expect to see it, @yyx990803 ? | 2022-08-03T07:49:26 | 2022-08-03T07:49:26 | {} | NONE |
vuejs | core | 1,203,663,234 | 6,392 | LittleSound | In my opinion defining built-in macros outside the SFC file also means that built-in macros can be defined repeatedly, otherwise you won't be able to define other parameters and events. | 2022-08-03T08:46:04 | 2022-08-03T08:46:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,204,251,636 | 6,392 | sxzz | I don't think the Vue compiler need to provide such an API. The custom macros need to modify many places of codes. A general way to process and transform macros is to wrote a bundler plugin, parse and manipulate AST yourself.
For example, https://github.com/sxzz/unplugin-vue-macros. I implemented `defineModel` and `... | 2022-08-03T17:17:14 | 2022-08-03T17:33:14 | {} | MEMBER |
vuejs | core | 1,206,057,979 | 5,584 | evanerwee01 | 
My error message | 2022-08-05T05:28:37 | 2022-08-05T05:28:37 | {} | NONE |
vuejs | core | 1,197,816,384 | 5,657 | Oleksii14 | > If anyone is still dealing with this. We worked around the error by replacing most of our `v-if` to `v-show`.
Nice 😄 😄 😄 | 2022-07-28T08:15:57 | 2022-07-28T08:15:57 | {} | NONE |
vuejs | core | 1,200,595,050 | 6,387 | Zippowxk | `<span v-if="show" style='position: absolute'>` | 2022-08-01T01:58:18 | 2022-08-01T01:58:18 | {} | NONE |
vuejs | core | 1,202,135,608 | 6,356 | HydenLiu | I have been looking for two days, still have not found which third-party framework problems, hard to | 2022-08-02T07:44:47 | 2022-08-02T07:44:47 | {} | NONE |
vuejs | core | 1,206,214,603 | 5,363 | qiyuan-wang | Try @JhonWeawer 's reproduce repo on chrome 104.0.5112.79 with vuejs@3.2.37, still reproduce this problem.
It seems not a chrome issue or [the fixed issue](https://bugs.chromium.org/p/chromium/issues/detail?id=1324096) still not work with vuejs.
@LinusBorg @yyx990803 Is this would be fixed? It hurts performance.
... | 2022-08-05T08:58:52 | 2022-08-05T08:58:52 | {} | CONTRIBUTOR |
vuejs | core | 1,206,321,915 | 6,400 | sxzz | I think the example below is better. (We should wait for [the issue](https://github.com/vuejs/core/issues/4294#issuecomment-1204534444))
```ts
// hooks.ts
interface ComposuableProps {
foo: string
}
function useComposuable(props) {
console.log(props.foo)
}
```
```ts
// SFC <script setup>
import typ... | 2022-08-05T11:02:17 | 2022-08-05T11:04:07 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,207,255,271 | 5,657 | jontybrook | I'm also facing this issue using the nuxt-rc6. Real pain. | 2022-08-06T17:53:34 | 2022-08-06T17:53:34 | {
"+1": 4
} | NONE |
vuejs | core | 1,243,524,927 | 4,294 | underdoeg | None of the proposed workarounds really worked for all uses cases but it really makes things easier to pass around the prop types to call some shared functions. I don't have a ton of props so I just ended up declaring them twice, once as an interface and once as a PropType. To keep the maintenance of this redundant co... | 2022-09-12T10:20:03 | 2022-09-12T11:23:46 | {} | NONE |
vuejs | core | 1,244,343,528 | 6,653 | LinusBorg | I can't follow. Changing the the value of a shallowRef is a reactive operation.
Not sure what you are expecting, your description is not very detailed. Could you provide a bit more details? | 2022-09-12T20:07:54 | 2022-09-12T20:07:54 | {} | MEMBER |
vuejs | core | 1,249,259,265 | 6,658 | mcanyucel | this error still exists both on `this.$router.push` and `this.$router.replace` using Vue 3.2.38. | 2022-09-16T11:39:18 | 2022-09-16T12:36:30 | {} | NONE |
vuejs | core | 1,249,719,700 | 1,228 | AaronBeaudoin | I'd like to chime in here that as a fairly new user to TypeScript, this `"skipLibCheck": true` "solution" feels like it puts me in a really bad spot. I'm still learning how to work with all the nuances of TypeScript, and just shutting off type checking for my `d.ts` files seems like a really great way to make learning ... | 2022-09-16T19:19:04 | 2022-09-16T19:19:04 | {
"+1": 1
} | NONE |
vuejs | core | 1,242,945,277 | 6,643 | Dedicatus546 | i have a try, and it can't get type hint from ts by `InstanceType<typeof HelloWorld>`, maybe it is a type bug for `vue`
| 2022-09-11T11:35:11 | 2022-09-11T11:35:11 | {} | NONE |
vuejs | core | 1,246,335,985 | 6,222 | midfar | > > 页面1是集成了echarts图表的KeepAlive页面，页面2是普通的vue KeepAlive页面，页面1切换到页面2后，会发现走了页面1的beforeUnmount \ unmounted 生命周期；再切回1，echarts图表都不显示出来，显示的是白色占位块（因为页面1已经销毁了）。
>
> 你这个不一定是vue的问题，可能是echarts的问题。你这个问题，不附代码，没法定位。
这个是有问题的代码工程：
打包后，登录后的echarts图表页和其他KeepAlive页面切换，再切回来，就能看到问题了。如果两个KeepAlive的页面没问题，就3个KeepAlive的页面切，一定会出问题
https:/... | 2022-09-14T07:05:36 | 2022-09-14T07:05:36 | {} | NONE |
vuejs | core | 1,246,314,791 | 6,222 | Eunknight | Temporary Solutions 临时解决方案
```html
<template v-if="NODE_ENV !== 'development'">
<keep-alive>
<component :is="Component" :key="route.fullPath" />
</keep-alive>
</template>
<template v-else>
<component :is="Component" :key="route.fullPath" />
</template>
```
vue-cli
```js
const NODE_ENV = proces... | 2022-09-14T06:44:12 | 2022-09-14T07:08:55 | {} | NONE |
vuejs | core | 1,246,342,822 | 6,222 | Eunknight | > 这个是有问题的代码工程： 打包后，登录后的echarts图表页和其他KeepAlive页面切换，再切回来，就能看到问题了。如果两个KeepAlive的页面没问题，就3个KeepAlive的页面切，一定会出问题 https://vkceyugu.cdn.bspapp.com/VKCEYUGU-fba5454d-3a27-4ea5-babf-ea74eb4644f5/649066cc-3178-4393-8064-b59df4403c29.zip
今天没时间看，后面有时间我看一下吧，看了可能也解决不了问题。 | 2022-09-14T07:12:55 | 2022-09-14T07:12:55 | {} | NONE |
vuejs | core | 1,247,098,858 | 6,638 | danielroe | Async components _are_ wrapped into suspense when the suspense is triggered on client-side, and `<Suspense>` documentation says that async components should be treated as dependencies: https://vuejs.org/guide/built-ins/suspense.html#async-components. | 2022-09-14T17:40:24 | 2022-09-14T17:40:24 | {} | MEMBER |
vuejs | core | 1,247,457,690 | 6,663 | edison1105 | duplicate of https://github.com/vuejs/core/issues/6313 | 2022-09-15T01:14:32 | 2022-09-15T01:14:32 | {} | MEMBER |
vuejs | core | 1,248,880,487 | 6,222 | midfar | > same error
楼上大佬已经解决了呢 | 2022-09-16T03:33:02 | 2022-09-16T03:33:02 | {} | NONE |
vuejs | core | 1,249,000,530 | 6,678 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ac2114b18c77aa30613946f9051afcbc06ff56e9 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-09-16T07:09:23 | 2022-09-16T07:09:23 | {} | NONE |
vuejs | core | 1,243,228,945 | 6,633 | chenhaihong | @Dedicatus546 兄弟建议你标点符号要加上，还有要加大小写。确实有点难阅读你的句子。 | 2022-09-12T05:11:35 | 2022-09-12T05:11:35 | {} | NONE |
vuejs | core | 1,245,204,789 | 4,745 | dmoKruso | I was able to migrate all to :deep, but I've found out that the style is not the same anymore. It doesn't overwrite the css classes.
I am using vue 2 (2.7.10) + nuxt(2.15.8) + vuetify(2.6.10)
I was changing one component that only have this simple css line:
```
::v-deep.v-text-field.v-text-field--enclosed:not(.... | 2022-09-13T10:20:56 | 2022-09-13T10:20:56 | {
"+1": 2
} | NONE |
vuejs | core | 1,245,221,046 | 4,745 | dmoKruso | So, I discover that `:deep(.class)` works the same as `::v-deep .class` BUT then... how can I do `::v-deep.class` (without spaces) with the new :deep() ? | 2022-09-13T10:35:28 | 2022-09-13T10:35:28 | {
"+1": 1
} | NONE |
vuejs | core | 1,245,244,708 | 6,658 | AlvaroBrasilia | Same issue here. | 2022-09-13T10:58:45 | 2022-09-13T12:03:43 | {} | NONE |
vuejs | core | 1,246,329,837 | 6,222 | midfar | > > > Temporary Solutions 临时解决方案
> > > ```
> > > <template v-if="NODE_ENV !== 'development'">
> > > <keep-alive>
> > > <component :is="Component" :key="route.fullPath" />
> > > </keep-alive>
> > > </template>
> > > <template v-else>
> > > <component :is="Component" :key="route.fullPath" />
> > > </t... | 2022-09-14T06:58:48 | 2022-09-14T06:58:48 | {} | NONE |
vuejs | core | 1,247,144,901 | 6,638 | danielroe | There is only one Suspense in the reproduction here.
And if you look at the PR I think you are referring to, you should see that we already ensure there is only one Suspense there. | 2022-09-14T18:23:35 | 2022-09-14T18:23:35 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,248,021,636 | 6,669 | edison1105 | this is not related to emits. see [simpler demo](https://sfc.vuejs.org/#eNp9UbtuwzAM/BVCS23UsZM1cIJ2yNahQ0ctjkInTm1JoOgYReB/L/1IGrRAN/GOdyKPV/XqfXppUa1VHgxVniEgt36rbdV4RwxXICwT6Ao2p11ZomHooSTXwJPonrTV1jgbGIxrfI2MB9gMkqgs6oDxjW3CccZXgmn74BcV4csaiGLYbOGqLUBVRne39FLULcYjDvKJDa7GtHbHSCxncuA0F11RMVjs4F3GqwJGNDjKPh9Vg67liBJY... | 2022-09-15T12:15:30 | 2022-09-16T03:00:06 | {} | MEMBER |
vuejs | core | 1,249,015,827 | 6,678 | btea | It seems duplicate of #6652 | 2022-09-16T07:26:11 | 2022-09-16T07:26:11 | {} | CONTRIBUTOR |
vuejs | core | 1,248,571,014 | 6,677 | LinusBorg | Hi.
We recently saw a similar issue and our stance is this:
Your mixing of script and script setup is invalid. You are using it as a mere shortcut to get around registering components, while using Options API the define the actual component itself. That's *not* what script setup is designed to support.
Here's... | 2022-09-15T20:18:34 | 2022-09-16T10:26:35 | {
"heart": 2
} | MEMBER |
vuejs | core | 1,250,005,086 | 6,669 | zhangzhonghe | I also think this is a bug, which adds to the confusion of the code. | 2022-09-17T05:35:25 | 2022-09-17T05:35:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,243,265,324 | 6,633 | Justineo | The provide/inject API is designed for your use case but `resolveComponent` isn’t. And like suggested by @Dedicatus546, a ConfigProvider component is also a good choice. Relying on globally registered component with a specific name isn’t a safe design as it makes your component less portable (consider using it inside a... | 2022-09-12T06:13:28 | 2022-09-12T06:13:28 | {} | MEMBER |
vuejs | core | 1,244,358,123 | 6,653 | LinusBorg | Oh, now i get it. You want the changed value of the nonreactive object in `message` not to appear in the template after it updated because of the `radish` triggering?
That's not how re-renders work. When a component re-renders, it updates she *whole* template with all the *latest* data. | 2022-09-12T20:14:17 | 2022-09-12T20:15:07 | {} | MEMBER |
vuejs | core | 1,244,974,344 | 6,222 | like0413 | > chrome 105.0.5195.102 依然存在该问题
关浏览器什么事 | 2022-09-13T06:49:13 | 2022-09-13T06:49:13 | {} | NONE |
vuejs | core | 1,245,215,774 | 6,658 | Dedicatus546 | could you provide a minimal reproduction?
| 2022-09-13T10:30:06 | 2022-09-13T10:30:06 | {} | NONE |
vuejs | core | 1,245,303,413 | 6,616 | LinusBorg | @edison1105 I reopened because I think we have some room for optimization here:
https://github.com/vuejs/core/blob/8772a01a9280b1591e781e20741d32e2f9a836c8/packages/runtime-dom/src/modules/props.ts#L96-L107
This is the place that throws the warning. it does throw because it tries to do `el.size = undefined`, whic... | 2022-09-13T11:52:43 | 2022-09-13T11:54:57 | {} | MEMBER |
vuejs | core | 1,247,114,773 | 6,638 | mmis1000 | https://stackblitz.com/edit/github-fktkzl-ptamri?file=src%2FApp.vue
I think what breaks the source issue is nested suspense.
But that should probably be a separate issue.
The async component under nested suspense seems never be included by parent suspense in any case.
Which is how nuxt 3 use the `Suspense` here... | 2022-09-14T17:54:44 | 2022-09-14T17:58:03 | {} | CONTRIBUTOR |
vuejs | core | 1,247,313,303 | 5,584 | M1CK431 | Thanks for this quick reply and confirmation @LinusBorg :pray:
> 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.
=> I agree, my linter is reporting me this kind of mistake (`v-model` on a `prop`). In addition,... | 2022-09-14T21:18:59 | 2022-09-14T21:18:59 | {
"+1": 1
} | NONE |
vuejs | core | 1,248,459,016 | 5,584 | M1CK431 | @LinusBorg I just open a dedicated issue with a reproduction repo here: #6677
Please notice that, at the end, it's effectively related to `<script>` and `<script setup>` mixed usage. | 2022-09-15T18:34:16 | 2022-09-15T18:34:16 | {
"heart": 1,
"rocket": 1
} | NONE |
vuejs | core | 1,248,735,623 | 6,674 | vis97c | Same issue happened to me on nuxt3.rc10 https://github.com/nuxt/framework/pull/7374
| 2022-09-15T23:10:16 | 2022-09-15T23:17:25 | {} | NONE |
vuejs | core | 1,249,044,720 | 6,677 | M1CK431 | > However I don't really see how this relates to the issue being discussed here.
I'm explaining all of that to demonstrate why it could be a good feature to support both API usage in the same component:
> Sorry for the very long comment, I hope my point of view and experience sharing could be helpful for Vue dev te... | 2022-09-16T07:59:03 | 2022-09-16T07:59:03 | {} | NONE |
vuejs | core | 1,242,914,043 | 6,633 | chenhaihong | @Dedicatus546 that's not a good choice for me.
Bro, u Chinese guy? Chinese directly? | 2022-09-11T08:14:49 | 2022-09-11T08:15:49 | {} | NONE |
vuejs | core | 1,243,332,679 | 6,633 | chenhaihong | @Justineo 感谢回复。因为我只是阅读了`resolveComponent` 的使用文档，没了解过它的设计初衷，所以我在我的项目用它来查找一个可能被注册的全局组件是否有存在。
我在写的项目暴露了一个方法用来创建应用，大概像下面这样子，
```javascript
import { createAdminApp } from 'package-admin'; // 会暴漏类似的方法用来创建管理平台应用
const { app } = createAdminApp({
// ... 一些定义好的配置，比如路由、侧边栏、导航栏、数据接口
});
app.component('custom-user... | 2022-09-12T07:34:45 | 2022-09-12T07:34:45 | {} | NONE |
vuejs | core | 1,243,374,076 | 5,830 | vaban-ru | Is there any news on solving this error? | 2022-09-12T08:15:10 | 2022-09-12T08:15:10 | {} | NONE |
vuejs | core | 1,244,972,141 | 6,222 | midfar | chrome 105.0.5195.102 依然存在该问题 | 2022-09-13T06:46:37 | 2022-09-13T06:46:37 | {} | NONE |
vuejs | core | 1,245,177,325 | 6,656 | GuoDoubleV | Root level comments is working when Transition's mode with "default" or "in-out", why not when the mode with "out-in"?
| 2022-09-13T09:57:59 | 2022-09-13T09:57:59 | {} | NONE |
vuejs | core | 1,245,276,397 | 6,616 | ivanmem | I see that the default value for the `size` is `20`.
Is it really necessary to set the default value `props: {size: {default: 20}}` and see it in the html, even if it is not specified when using the component?
Can vue developers make it so that when trying to specify an undefined value, it is not set at all? So th... | 2022-09-13T11:28:36 | 2022-09-13T11:28:55 | {} | NONE |
vuejs | core | 1,247,112,567 | 6,637 | AaronBeaudoin | I'd like to challenge the classification of this issue as a "minor" bug, because:
- Since it's not exactly clear what specific HTML triggers the issue, it's also not clear how to get around it. I'm stuck just trying random changes until I land on something that works, if possible. This totally sucks.
- If I can't f... | 2022-09-14T17:52:46 | 2022-09-14T17:52:46 | {} | NONE |
vuejs | core | 1,248,811,680 | 6,222 | varzy | same error | 2022-09-16T01:27:36 | 2022-09-16T01:27:36 | {} | NONE |
vuejs | core | 1,248,826,593 | 5,657 | shu16 | > 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-16T01:58:44 | 2022-09-16T01:58:44 | {} | NONE |
vuejs | core | 1,242,971,134 | 6,643 | mengdu | I used tsx files got the same problem.
```tsx
// Demo.tsx
import { defineComponent} from "vue";
export default defineComponent({
name: "HelloWorld",
setup(_props, { expose }) {
const msg = () => {
console.log("msg");
};
expose({ msg })
return () => (<div>xxx</div>)
});... | 2022-09-11T13:58:04 | 2022-09-11T13:58:04 | {} | NONE |
vuejs | core | 1,245,241,799 | 6,573 | AlvaroBrasilia | Same problem here.
Does anyone have any solution? | 2022-09-13T10:55:51 | 2022-09-13T10:55:51 | {} | NONE |
vuejs | core | 1,246,324,408 | 6,222 | Eunknight | > > Temporary Solutions 临时解决方案
> > ```
> > <template v-if="NODE_ENV !== 'development'">
> > <keep-alive>
> > <component :is="Component" :key="route.fullPath" />
> > </keep-alive>
> > </template>
> > <template v-else>
> > <component :is="Component" :key="route.fullPath" />
> > </template>
> > ```
>... | 2022-09-14T06:52:45 | 2022-09-14T06:56:49 | {} | NONE |
vuejs | core | 1,247,666,172 | 6,222 | midfar | > @midfar 贴下你的代码看下。
已上传到这里，注意是keep-alive分支。开发模式下，登录后可以看到控制台警告
https://github.com/midfar/vue3-element-admin/tree/keep-alive | 2022-09-15T07:00:49 | 2022-09-15T07:00:49 | {} | NONE |
vuejs | core | 1,249,741,301 | 5,830 | PixsaOJ | Fixed by naming prop `primary` something else | 2022-09-16T19:43:16 | 2022-09-16T19:43:16 | {} | NONE |
vuejs | core | 1,245,121,978 | 6,222 | poerlang | 换了最新的 chrome 浏览器，也一样报错 | 2022-09-13T09:10:54 | 2022-09-13T09:10:54 | {} | NONE |
vuejs | core | 1,247,256,436 | 5,670 | bapaynter | Any updates on this? | 2022-09-14T20:16:29 | 2022-09-14T20:16:29 | {
"eyes": 3
} | NONE |
vuejs | core | 1,247,717,658 | 6,222 | midfar | > @midfar 你别把壳组件集合放到响应式数据里，这里改一改。
>
> https://github.com/midfar/vue3-element-admin/blob/7217ef5a567915789a0f3e6b8ad8bde76990bb14/src/layout/components/AppMain.vue#L21
>
> 你在你的 `tagsView` 模块里就把 `wrapperMap` 写成一个普通的变量好了，然后 export 出去。 在 `AppMain` 组件导入 `wrapperMap` 吧。
恩，可以了，牛逼啊 | 2022-09-15T07:52:33 | 2022-09-15T07:52:33 | {} | NONE |
vuejs | core | 1,247,852,645 | 6,222 | poerlang | 加壳的操作，有点复杂，而且意义也不明确，最好官方能支持，不用我们加这么多代码 | 2022-09-15T09:42:11 | 2022-09-15T09:42:11 | {} | NONE |
vuejs | core | 1,249,229,750 | 6,677 | M1CK431 | > You have the ability to control the use of the reactive object or the value.
It's a good addition... when you need it. From my personal experience, most of the time, it's not needed. So go for options API most of the time, and use composition API for the rest :man_shrugging: | 2022-09-16T11:04:14 | 2022-09-16T11:04:14 | {} | NONE |
vuejs | core | 1,247,525,779 | 6,222 | midfar | > @midfar 看下这个能不能用 [#4339 (comment)](https://github.com/vuejs/core/pull/4339#issuecomment-1238984279)
>
> 自己给 keep-alive 包裹的 component 包个壳。 我原本在做做多tab单页应用的时候，也遇到这个问题，加了这个壳后，在开发和生产模式下都没有再出现过这个问题。
你这样改貌似可以，但是控制台有另一个警告（好像不影响功能）
[Vue warn]: Vue received a Component which was made a reactive object. This can lead to ... | 2022-09-15T03:10:19 | 2022-09-15T03:10:19 | {} | NONE |
vuejs | core | 1,248,952,096 | 6,677 | LinusBorg | I can understand your POV, and we left both APIs available precisely because many people prefer the Options API. However I don't really see how this relates to the issue being discussed here.
> TBH, I was not having the feeling of doing something "wrong", even after carefully read the documentation.
Yep, as I sai... | 2022-09-16T06:02:49 | 2022-09-16T06:02:49 | {} | MEMBER |
vuejs | core | 1,242,951,068 | 5,767 | EzeFSpa | I was playing a bit with the example (https://stackblitz.com/edit/vite-auuvqt?file=src%2Fcomponents%2FWrapper.vue) and I discovered that if the properties are associated to a **ref** variable, the hmr always works, but not with a value expressed in the template
This was what I tried and works:
![image](https://use... | 2022-09-11T12:10:34 | 2022-09-11T12:23:14 | {
"heart": 1
} | NONE |
vuejs | core | 1,243,299,717 | 5,657 | Aliuet | thank you for this , this is perfectly working | 2022-09-12T07:00:24 | 2022-09-12T07:00:24 | {} | NONE |
vuejs | core | 1,243,374,664 | 5,831 | vaban-ru | Is there any news on solving this error? | 2022-09-12T08:15:44 | 2022-09-12T08:15:44 | {} | NONE |
vuejs | core | 1,243,460,418 | 5,584 | M1CK431 | Hi,
It happens to me with a getter/setter computed.
In the following example, `SomeComponent` accept a `modelValue` prop of `Object` type.
This child component **is not mutating the prop**. Instead, it emits an `update:modelValue` event with a modified `thing` object (for example, the `id` will remains the same ... | 2022-09-12T09:26:34 | 2022-09-12T09:26:34 | {} | NONE |
vuejs | core | 1,244,350,709 | 6,573 | jhughes-dev | I tried my suggestion above locally, but it wasn't a complete solution. I still saw errors unless I protected against the .value property access, but even then, I didn't get the expected behavior of the app. Not sure what the right approach is when the two arrays have different sizes. | 2022-09-12T20:11:03 | 2022-09-12T20:11:03 | {} | NONE |
vuejs | core | 1,246,316,709 | 6,222 | midfar | > Temporary Solutions 临时解决方案
>
> ```
> <template v-if="NODE_ENV !== 'development'">
> <keep-alive>
> <component :is="Component" :key="route.fullPath" />
> </keep-alive>
> </template>
> <template v-else>
> <component :is="Component" :key="route.fullPath" />
> </template>
> ```
>
> vue-cli
>
... | 2022-09-14T06:46:36 | 2022-09-14T06:46:36 | {} | NONE |
vuejs | core | 1,246,331,984 | 6,222 | Eunknight |
> 页面1是集成了echarts图表的KeepAlive页面，页面2是普通的vue KeepAlive页面，页面1切换到页面2后，会发现走了页面1的beforeUnmount \ unmounted 生命周期；再切回1，echarts图表都不显示出来，显示的是白色占位块（因为页面1已经销毁了）。
你这个不一定是vue的问题，可能是echarts的问题。你这个问题，不附代码，没法定位。
| 2022-09-14T07:01:09 | 2022-09-14T07:01:09 | {} | NONE |
vuejs | core | 1,246,435,441 | 6,222 | chenhaihong | @midfar 看下这个能不能用 https://github.com/vuejs/core/pull/4339#issuecomment-1238984279
自己给 keep-alive 包裹的 component 包个壳。
我原本在做做多tab单页应用的时候，也遇到这个问题，加了这个壳后，在开发和生产模式下都没有再出现过这个问题。 | 2022-09-14T08:40:11 | 2022-09-14T08:40:11 | {
"+1": 3,
"rocket": 2
} | NONE |
vuejs | core | 1,247,200,456 | 5,584 | M1CK431 | Just to clarify, there is "Options API" and "Composition API", **none of them are "legacy" or "old style"**.
src: https://vuejs.org/guide/extras/composition-api-faq.html#will-options-api-be-deprecated
In addition, there is still one thing which can't be done in composition API at all: disabling `inheritAttrs`.
src... | 2022-09-14T19:19:07 | 2022-09-14T19:19:07 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.