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 | 933,694,153 | 4,314 | dbaumannlt | @yyx990803 This is a critical feature for my current client. We are developing web components that will be served by a Content Management System where the CSS will be included in the header of the page. Not being able to pierce the veil of the shadow root is a show stopper. We are currently using Vue 2 with the follow... | 2021-10-04T17:22:25 | 2021-10-04T17:22:25 | {
"+1": 12
} | NONE |
vuejs | core | 934,156,497 | 4,736 | LinusBorg | There's a workaround by defining the event in `props` instead of `emits`:
```html
<template>
<div>
<Child v-bind="{ ...$attrs, onMyEvent }" />
<button @click="$emit('my-event')">Mid emit</button>
</div>
</template>
<script>
import Child from "./Child.vue";
export default {
//emits: ["m... | 2021-10-05T07:50:41 | 2021-10-05T07:51:41 | {
"+1": 3
} | MEMBER |
vuejs | core | 935,897,180 | 4,739 | LinusBorg | repositories will be moved when we have done the new docs, which is currently the main focus of our efforts.
We won't start renaming repositories until then. | 2021-10-06T10:08:14 | 2021-10-06T10:08:14 | {} | MEMBER |
vuejs | core | 928,964,049 | 4,693 | posva | Can you open an issue at https://github.com/vuejs/docs to keep track of this? | 2021-09-28T08:17:01 | 2021-09-28T08:17:01 | {} | MEMBER |
vuejs | core | 929,064,397 | 4,662 | raffobaffo | Ok, this should be safer now. This addition will add any child component style to the main parent, no matter how deeply nested it is | 2021-09-28T10:32:03 | 2021-09-28T10:32:14 | {} | NONE |
vuejs | core | 929,580,697 | 1,359 | Spittal | There seems to be an issue with `v-model` whenever there is a type annotation in the template.
```
v-model value must be a valid JavaScript member expression.vue(42)
```
This can be reproduced with something as simple as:
```
<script setup lang="ts">
import { ref } from 'vue';
const hi = ref('hi');
</s... | 2021-09-28T20:01:14 | 2021-09-28T20:01:14 | {} | NONE |
vuejs | core | 930,959,512 | 4,706 | dvh91 | @posva Thanks for the reply!
The use case I have is that I basically want to use this function-prop also as a flag and not having to pass another prop.
At the same time, I don't want to lose the typings of the emit.
Can this decision be reconsidered somehow? | 2021-09-30T07:49:55 | 2021-09-30T07:49:55 | {} | NONE |
vuejs | core | 931,470,087 | 4,710 | RollingTL | I've been working with vue 3 and TS since the very beginning. And the behavior was that any TS error stopped compilation. Now this behavior is broken, and you try to prove it is normal, which is not.
Cud you invite somebody else to conversation, as it seems to me your are wrong.
| 2021-09-30T16:18:22 | 2021-09-30T16:18:22 | {} | NONE |
vuejs | core | 933,284,261 | 4,733 | posva | Instead of being slot specific, it could also be vnode specific, like `isVNodeEmpty(arrayOrSingleVNode)`:
```js
const slotContent = slots.default?.(props)
isVNodeEmpty(slotContent)
```
One issue is using this in a template would be much verbose in order to reuse the vnodes. So maybe there is an alternative way... | 2021-10-04T08:59:18 | 2021-10-04T08:59:18 | {
"+1": 3
} | MEMBER |
vuejs | core | 934,191,738 | 4,736 | marina-mosti | To document another workaround, explicitly listening for and then re-emitting the event also works.
```html
<template>
<div>
<Child v-bind="$attrs" @myEvent="$emit('myEvent')" />
<button @click="$emit('my-event')">Mid emit</button>
</div>
</template>
<script>
import Child from "./Child.vue";
... | 2021-10-05T08:36:58 | 2021-10-05T08:36:58 | {
"+1": 2
} | NONE |
vuejs | core | 934,881,405 | 4,611 | crutchcorn | I would be happy to make a PR to add this export in runtime. Is this something I could potentially add?
If so, should it be under a namespace? What should it be? | 2021-10-05T21:36:56 | 2021-10-05T21:36:56 | {} | NONE |
vuejs | core | 935,959,576 | 906 | PaulAshraf | @r4pt0s Cant thank you enough for this. | 2021-10-06T10:50:33 | 2021-10-06T10:50:33 | {
"heart": 1
} | NONE |
vuejs | core | 936,885,184 | 4,740 | julie777 | > See https://github.com/antfu/unplugin-auto-import
>
This is great. I hope it will be mentioned/suggested in the new Vue 3 docs.
| 2021-10-06T18:44:35 | 2021-10-06T18:44:35 | {} | NONE |
vuejs | core | 936,907,014 | 4,717 | Oleksii14 | @posva any details? | 2021-10-06T18:56:32 | 2021-10-06T18:56:32 | {} | NONE |
vuejs | core | 937,375,503 | 4,727 | yyx990803 | @dependabot ignore this dependency | 2021-10-07T01:39:36 | 2021-10-07T01:39:36 | {} | MEMBER |
vuejs | core | 930,299,612 | 1,359 | Spittal | No problem, for anyone else looking for the recreation, here is a repo.
https://github.com/Spittal/v-model-repo | 2021-09-29T15:43:58 | 2021-09-29T15:43:58 | {} | NONE |
vuejs | core | 930,306,053 | 1,359 | avenmore | This works fine for me now that didn't work before `v-model="employeeEditModel.editingEmployeeDTO.value!.cLastName"` (or else Volar complained that it may be undefined), but `hi!` also does give me the error. | 2021-09-29T15:51:45 | 2021-09-29T15:51:45 | {} | NONE |
vuejs | core | 931,366,516 | 4,710 | RollingTL | As far as I remember until today any TS Error prevented page from rendering. Why the behavior changed?
Ok which errors should stop rendering and with should not? Is there a list?
| 2021-09-30T14:18:57 | 2021-09-30T14:18:57 | {} | NONE |
vuejs | core | 931,492,341 | 4,710 | posva | That depends on how you configure your dev server.
If you can provide a boiled down repro with steps that shows how it used to work with a previous version of Vue and it doesn't work anymore, I will take another look. | 2021-09-30T16:48:20 | 2021-09-30T16:48:20 | {} | MEMBER |
vuejs | core | 932,030,005 | 4,713 | posva | In order to check if it exists, you should declare it as a prop: https://github.com/vuejs/rfcs/pull/154#issuecomment-614724480
| 2021-10-01T08:28:36 | 2021-10-01T08:28:36 | {} | MEMBER |
vuejs | core | 932,531,663 | 2,860 | mgdodge | @yyx990803 thanks for all the work on this - you are amazing! Updated to the latest vite release, and when writing the library in vite, then using in a vite app, the code does in fact seem tree-shakeable. Testing tree-shakeability with `npx agadoo` also looks good. But when using the library in a vue cli app, tree shak... | 2021-10-01T20:31:08 | 2021-10-01T20:31:08 | {} | NONE |
vuejs | core | 933,653,905 | 4,731 | yyx990803 | Using const enum is intentional. If anything we should move the const enum into `@vue/shared` and change all node type checks to use it. | 2021-10-04T16:32:29 | 2021-10-04T16:32:29 | {
"+1": 1
} | MEMBER |
vuejs | core | 934,221,551 | 4,736 | marina-mosti | As suggested, discussion open here: https://github.com/vuejs/rfcs/discussions/397 | 2021-10-05T09:14:07 | 2021-10-05T09:14:07 | {
"+1": 3
} | NONE |
vuejs | core | 935,901,599 | 4,741 | livthomas | Sorry, I thought it's pretty clear so I didn't want to spend half an hour creating a repo with a reproducer. Here's the code:
```ts
setup(props) {
const style = computed<StyleValue>(() => ({
'--menu-item-color': props.color ?? '',
}));
return {style};
}
```
Or simply:
```ts
const styl... | 2021-10-06T10:11:02 | 2021-10-06T10:11:02 | {} | NONE |
vuejs | core | 930,283,152 | 1,359 | Spittal | Hey @avenmore Thanks for the tip unfortunately I can still replicate the issue.
I have double and triple checked that I am on `3.2.19` | 2021-09-29T15:25:06 | 2021-09-29T15:25:06 | {} | NONE |
vuejs | core | 930,487,458 | 4,699 | yyx990803 | We already mostly use `.slice` across the codebase so I think it's better to be consistent and use `.slice` everywhere. It's also shorter. | 2021-09-29T19:42:45 | 2021-09-29T19:42:45 | {} | MEMBER |
vuejs | core | 931,100,135 | 4,707 | 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).
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.o... | 2021-09-30T09:08:55 | 2021-09-30T09:08:55 | {
"-1": 5,
"confused": 1
} | MEMBER |
vuejs | core | 931,622,418 | 4,703 | unuseless | @ygj6 Thanks for closing the issue and including the link. | 2021-09-30T19:59:58 | 2021-09-30T19:59:58 | {} | NONE |
vuejs | core | 931,870,962 | 4,712 | caozhong1996 | > This will lead to performance degradation.
From my point of view, `new Array(toBePatched).fill(0)` is faster.
This is a simple test in chrome 93.0.4577.63
 | 2021-10-06T07:50:20 | 2021-10-06T07:50:20 | {} | MEMBER |
vuejs | core | 928,890,658 | 4,686 | LinusBorg | The slot behavior that you find unintuitive exists in order to improve on one of the more common perf problems in Vue 2 applications: slots updates forcing a chain of ancestor components to re-render even though only the slot content is affected.
Bu running the slot rendering in the child component, instead of the p... | 2021-09-28T06:20:25 | 2021-09-28T06:20:25 | {
"+1": 2
} | MEMBER |
vuejs | core | 929,857,720 | 1,359 | avenmore | @Spittal The solution for me was to delete `package-lock.json` and `node_modules` and `npm install`. I see that `ncu` doesn't update `"vue":"3.2.4"` so that's why a re-install worked. A solution may be to ensure that it is at least `"3.2.19"` and then install. | 2021-09-29T05:54:07 | 2021-09-29T05:54:07 | {} | NONE |
vuejs | core | 930,017,246 | 4,701 | posva | Maybe `RefSymbol` should be renamed to `_RefSymbol`, marked as `@internal` in its comment, and exported.
There are probably a few other missing exports reported by api-extractor | 2021-09-29T09:42:05 | 2021-09-29T09:42:05 | {} | MEMBER |
vuejs | core | 931,102,873 | 4,708 | posva | Duplicate of https://github.com/vuejs/vue-router-next/issues/626 | 2021-09-30T09:10:32 | 2021-09-30T09:10:32 | {
"confused": 2,
"eyes": 2
} | MEMBER |
vuejs | core | 931,458,852 | 4,711 | posva | Locking to prevent two parallel conversations | 2021-09-30T16:04:54 | 2021-09-30T16:04:54 | {} | MEMBER |
vuejs | core | 932,322,744 | 4,710 | RollingTL | I understand that developers team thinks it is normal to compile even if there is TS Errors, and it is not a bug.
But it makes no sense - I don't need running application with type errors. It is useless. And instead of Vite telling me that there are TS errors the developer will search red lines in IDE.
Anyway m... | 2021-10-01T15:19:32 | 2021-10-01T15:19:32 | {
"+1": 2
} | NONE |
vuejs | core | 932,751,360 | 4,730 | klwfwdk | 这个本来就是文档里面写了的吧，如果不覆盖你怎么在setup里面处理模板里面的节点
应该避免这两个变量同名。
---原始邮件---
发件人: ***@***.***>
发送时间: 2021年10月2日(周六) 晚上9:10
收件人: ***@***.***>;
抄送: ***@***.***>;
主题: [vuejs/vue-next] setup中返回的属性名与元素模板中使用的ref名相同会导致setup中返回的属性被覆盖 (#4730)
Version
3.2.19
Reproduction link
sfc.vuejs.org/
St... | 2021-10-02T13:21:01 | 2021-10-02T13:21:01 | {} | CONTRIBUTOR |
vuejs | core | 933,541,341 | 4,731 | caozhong1996 | Yep, but I'm not worried about `Node.nodeType`'s compatibility. It's hard to trade-off between performance and maintainability.🥺
| 2021-10-04T14:26:48 | 2021-10-04T14:26:48 | {} | CONTRIBUTOR |
vuejs | core | 937,378,234 | 4,738 | yyx990803 | Interestingly this is caused by https://github.com/vuejs/vue-next/pull/4653, looking into it.
Update: can confirm this only happens in the dev build. | 2021-10-07T01:47:59 | 2021-10-07T01:51:33 | {} | MEMBER |
vuejs | core | 902,792,233 | 4,403 | LinusBorg | I felt like looking into this even though the repo wasn't really minimal with the added dependency.
It's an edge-case issue with the compat behaviour for `app.config.globalProperties`:
https://github.com/vuejs/vue-next/blob/4adc5042f92c384d9aec2d19e05c8bc2c74b2a93/packages/runtime-core/src/componentPublicInstance... | 2021-08-20T15:56:28 | 2021-08-20T15:57:12 | {} | MEMBER |
vuejs | core | 902,844,237 | 4,307 | pikax | I'm not able to reproduce the OP issue
> I have a similar problem using data values https://prnt.sc/1o0ew0a. If I use the simple const variable, everything works as expected.
> Reproduction link: https://github.com/baronkoko/vue-reactive-type-error/blob/main/src/App.vue
> Vue 3.2.2
The project is using an outda... | 2021-08-20T17:25:31 | 2021-08-20T17:25:31 | {
"+1": 2
} | MEMBER |
vuejs | core | 903,132,993 | 4,402 | edison1105 | see https://github.com/vuejs/vue-next/pull/4339 | 2021-08-21T15:26:23 | 2021-08-21T15:26:23 | {} | MEMBER |
vuejs | core | 903,217,205 | 4,410 | JeromeDeLeon | Somehow, creating a new project and migrating all previous setup to the new one fixed the issue. 🤔 | 2021-08-22T05:44:48 | 2021-08-22T05:44:48 | {} | NONE |
vuejs | core | 903,265,429 | 1,001 | DevLucem | If you are using a custom component that takes in `v-model` you need to add the name of your component as a class name in the root element.
Example
```
<template>
<div class="Selector m-2">
<label class="subtitle" :for="title">{{title}}</label>
<select class="m-2 px-4 bg-transparent border border-gree... | 2021-08-22T13:00:16 | 2021-08-22T13:01:31 | {
"+1": 1
} | NONE |
vuejs | core | 903,671,949 | 4,417 | LinusBorg | Vue / its compiler doesn't do autoprefixing. This is the responsibility of the css tooling you choose in your build setup, i.e. postcss-loader + autoprefixer plugin with webpack. | 2021-08-23T11:13:21 | 2021-08-23T11:13:39 | {} | MEMBER |
vuejs | core | 902,193,230 | 4,393 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 45.81 KB (+0.08% 🔺) |
| runtime-dom.global.prod.js | 30.25 KB (+0.11% 🔺) |
| size-check.global.prod.js | 17.41 KB (0%) | | 2021-08-19T19:46:03 | 2021-08-24T08:23:06 | {} | NONE |
vuejs | core | 905,156,936 | 4,424 | Justineo | Thank you for the PR. Can you make a minimal reproduction for the issue you are trying to fix?
I tried to make a repro but [it does work as expected](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgbXNnID0gcmVmKCdIZWxsbyBXb3JsZCEnKVxuPC9zY3JpcHQ+XG5cbjx0ZW1w... | 2021-08-25T03:39:18 | 2021-08-25T03:39:18 | {} | MEMBER |
vuejs | core | 903,241,258 | 4,412 | posva | Using `import type {Plugin} from 'vue'` should work | 2021-08-22T09:39:26 | 2021-08-22T09:39:26 | {} | MEMBER |
vuejs | core | 903,718,698 | 4,420 | GeniusWiki | @posva then why second example, Vue is aware of this "document.getElementById('text1').disabled= false"?
I don't think the problem is aware or not, the problem is Vue update an array, the array updates an irrelevant attribute.
Also, Vue2 seems working as expected, it won't change display=block to display=none... | 2021-08-23T12:27:06 | 2021-08-23T12:31:09 | {} | NONE |
vuejs | core | 904,419,202 | 4,422 | shadowings-zy | @qq974969638 I think we don't need using `Map` to store the relation of `name` and `element_inc`.
I think we can solve this edge case by adding an unique identifier on specific `validAssetId`.
```
export function toValidAssetId(
name: string,
type: 'component' | 'directive' | 'filter'
): string {
// see ... | 2021-08-24T08:07:34 | 2021-08-24T08:07:34 | {} | CONTRIBUTOR |
vuejs | core | 905,462,474 | 4,439 | edison1105 | duplicate of https://github.com/vuejs/vue-next/issues/4370 | 2021-08-25T12:35:20 | 2021-08-25T12:35:20 | {} | MEMBER |
vuejs | core | 906,054,207 | 3,173 | edison1105 | > @edison1105 For `:class="undefined"` and `:class="null"`, `@vue/runtime-dom` v3.1.5 removed `class`, whereas `@vue/runtime-dom` v3.2.4 kept it, which seems like a regression bug.
Good catch. Would you mind commit a new issue with a working repro? | 2021-08-26T03:02:16 | 2021-08-26T03:02:16 | {} | MEMBER |
vuejs | core | 902,828,714 | 2,016 | KaelWD | We use this in vuetify as well. | 2021-08-20T16:58:30 | 2021-08-20T16:58:30 | {} | CONTRIBUTOR |
vuejs | core | 903,103,296 | 4,409 | posva | I think exposing two functions with the same name in two different packages is prone to errors, especially for IDEs as they can import the wrong version and this is problematic because their behavior is not the same, ending up in very difficult to debug errors that are very easy to encounter (`@vue/reactivity` is insta... | 2021-08-21T11:36:26 | 2021-08-21T15:16:44 | {} | MEMBER |
vuejs | core | 903,247,388 | 4,412 | LinusBorg | using `lang="ts"` when using Typescript would also be a good idea. | 2021-08-22T10:33:18 | 2021-08-22T10:33:18 | {} | MEMBER |
vuejs | core | 903,380,780 | 4,414 | Justineo | 请先去 Element Plus 的仓库提交相应问题，确认非第三方依赖问题后，请提供一个不含此类依赖的可复现环境，谢谢。 | 2021-08-23T01:41:13 | 2021-08-23T01:41:13 | {} | MEMBER |
vuejs | core | 903,381,667 | 4,414 | Justineo | 你这个问题比较简单，Vue 3 的 render function 不再有 `on` 属性了，请仔细查看文档：https://v3.vuejs.org/guide/render-function.html#v-on | 2021-08-23T01:44:07 | 2021-08-23T01:44:07 | {} | MEMBER |
vuejs | core | 903,402,392 | 4,403 | Fiona-SUN | Thanks for helping me to explain this problem clearer.
I think that globalProperty with function as value should be a common approach in dependency libraries.such as `ElementUI` ,`Vant` and so on.
Now most of us would like to migrate our project from Vue2 to Vue3(Migration Build)，but the dependency package can not ... | 2021-08-23T02:54:07 | 2021-08-23T03:03:57 | {} | NONE |
vuejs | core | 903,492,081 | 4,416 | LinusBorg | https://new-issue.vuejs.org/?repo=vuejs/vue-next&lang=zh-cn#why-repro | 2021-08-23T06:53:10 | 2021-08-23T06:53:10 | {} | MEMBER |
vuejs | core | 904,641,365 | 3,173 | edison1105 | > @Liwoj Just tried, reproducible for me as well. Ping @yyx990803
I made a [repro](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmNvbnN0IG1zZyA9IHJlZignSGVsbG8gV29ybGQhJylcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIDxkaXYgOnRpdGxlPVwidW5kZWZpbmVkXCIgOmNsYXNzPVwidW5kZWZpbmV... | 2021-08-24T13:26:27 | 2021-08-24T13:33:37 | {} | MEMBER |
vuejs | core | 906,102,278 | 3,173 | wenfangdu | @edison1105 I've updated the issue to reflect that, since the playground doesn't seem to keep the vue version, I included the repro for the latest commit.
| 2021-08-26T05:16:26 | 2021-08-26T05:16:26 | {} | NONE |
vuejs | core | 902,683,669 | 4,400 | cawa-93 | If you make the array a link, it still does not give the desired result ([see this playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICBBQ1RVQUw6XG4gIDxvbD5cbiAgICA8bGkgdi1mb3I9XCIoaXRlbSwgaW5kZXgpIG9mIGl0ZW1zXCIgOmtleT1cImluZGV4XCI+e3sgaXRlbS5sYWJlbCB9fTwvbGk+XG4gIDwvb2w+XG4gIEVYUEVDVEVEOlxuICA8b2w+XG... | 2021-08-20T13:12:58 | 2021-08-20T13:12:58 | {} | CONTRIBUTOR |
vuejs | core | 904,533,459 | 3,173 | Liwoj | I think this should be reopend as the fix in 7013e8f does not work. Problem is the `value` argument of `patchClass` is never `null` because all class values (including `null`, `undefined` etc) are converted into strings using [normalizeClass](https://github.com/vuejs/vue-next/blob/b40845153cd4dbdd76bfb74816f4e6b109c9f... | 2021-08-24T10:50:48 | 2021-08-24T10:58:22 | {} | NONE |
vuejs | core | 905,088,825 | 4,429 | edison1105 | @qq974969638
This PR had already covered your cases.
using a Map also can solve this problem but not that simpler like that in this PR. | 2021-08-25T01:04:35 | 2021-08-25T01:04:35 | {} | MEMBER |
vuejs | core | 905,333,197 | 4,436 | edison1105 | in your yarn.lock `@vue/compiler-sfc@^3.1.5` see https://github.com/TeamPiped/Piped/blob/master/yarn.lock#L1447
before re-install deps, you should remove yarn.lock first. | 2021-08-25T09:23:36 | 2021-08-25T09:23:36 | {} | MEMBER |
vuejs | core | 906,032,926 | 4,397 | klwfwdk | Calling `ctx.expose` while using `setup` function in `defineComponent` seems to have the same problem | 2021-08-26T02:38:42 | 2021-08-26T02:38:42 | {} | CONTRIBUTOR |
vuejs | core | 902,726,845 | 4,400 | posva | ah! you are right @LinusBorg I thought it would output `{ "value": "..." }` | 2021-08-20T14:19:53 | 2021-08-20T14:19:53 | {} | MEMBER |
vuejs | core | 903,390,417 | 4,414 | Justineo | 请先详细了解 Vue 2 迁移到 Vue 3 的非兼容性变化，这是用 Vue 3 进行开发的基础。你这个问题在里面都有提到的。
https://v3.vuejs.org/guide/migration/render-function-api.html#vnode-props-format | 2021-08-23T02:10:24 | 2021-08-23T02:10:24 | {} | MEMBER |
vuejs | core | 904,180,058 | 4,413 | yyx990803 | FYI - we only require using these helpers in client-side code to reduce bundle size. Most callsites here are either in tests or non client-side code. It's fine to leave them as-is. | 2021-08-23T22:35:30 | 2021-08-23T22:35:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 905,194,427 | 4,429 | qq974969638 | @edison1105
Hello, you can view this error demo. I don't know if this issue needs to be dealt with, it's just for communication.
[https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aDE+e3sgbXNnIH19PC9oMT5cbiAgPGE0Nj48L2E0Nj5cbiAgPGEuPjwvYS4+XG48L3RlbXBsYXRlPlxuXG48c2NyaXB0IHNldHVwPlxuY29uc3QgbXNnID0gJ0hl... | 2021-08-25T05:26:59 | 2021-08-25T05:26:59 | {} | NONE |
vuejs | core | 905,334,390 | 4,438 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). | 2021-08-25T09:25:11 | 2021-08-25T09:25:11 | {} | MEMBER |
vuejs | core | 906,001,413 | 3,173 | wenfangdu | @edison1105 For `:class="undefined"` and `:class="null"`, `@vue/runtime-dom` v3.1.5 removed it, whereas `@vue/runtime-dom` v3.2.4 kept it, which seems like a regression bug.
| 2021-08-26T01:24:00 | 2021-08-26T03:21:42 | {} | NONE |
vuejs | core | 903,748,122 | 629 | superkkmax | @seanlandsman Please Please Please can you provide a complete sample code?
> > componentDefinition = defineComponent({ extends: defineComponent({ ...component }), data: () => ({params: params}), created: function() { componentInstance = this.$root }});
> >
> > createApp(componentDefinition).mount(container);
| 2021-08-23T13:05:39 | 2021-08-23T13:05:39 | {} | NONE |
vuejs | core | 904,178,445 | 4,411 | yyx990803 | These functions are only used in compiler-generated code so their type checking should be lax. | 2021-08-23T22:31:30 | 2021-08-23T22:31:30 | {} | MEMBER |
vuejs | core | 904,489,340 | 4,428 | codeplott | The styles of child vue component are not applied if the parent component is a custom element. #4309
Because of this, I have to define my custom input as a custom element, otherwise I cannot use any styles.
I thank you for your help and hope that a solution/workaround will be found soon. 🙂
✌ue is awesome! | 2021-08-24T09:43:06 | 2021-08-24T09:43:06 | {} | NONE |
vuejs | core | 905,903,489 | 4,443 | tochoromero | I don't have the time right now to create a reproduction example, I will this weekend. As I mentioned in the ticket I really don't know how I got into that state.
But the code change is pretty concise, have you seen it? | 2021-08-25T21:56:54 | 2021-08-25T21:56:54 | {} | NONE |
vuejs | core | 906,157,382 | 4,449 | LinusBorg | You likely misunderstood this sentence in the docs for `isCustomElement`:
> This config option is only respected when using the full build (i.e. the standalone vue.js that can compile templates in the browser). If you are using the runtime-only build with a build setup, compiler options must be passed to @vue/compil... | 2021-08-26T07:17:11 | 2021-08-26T07:17:11 | {} | MEMBER |
vuejs | core | 906,164,866 | 4,449 | edison1105 | BTW, you should also upgrade `@vue/compiler-sfc` to 3.2.6 | 2021-08-26T07:29:35 | 2021-08-26T07:29:35 | {} | MEMBER |
vuejs | core | 906,209,807 | 4,450 | posva | Your repro link is broken. Closing as a duplicate of #4447 | 2021-08-26T08:37:28 | 2021-08-26T08:37:28 | {} | MEMBER |
vuejs | core | 902,915,248 | 4,385 | weikinhuang | @LinusBorg I recreated the same scenario with Vue2 SSR:
https://codesandbox.io/s/cranky-elgamal-boc76?file=/src/index.js
This example shows how the `renderStyles` call is returning a style block by Vue's server-renderer. Here's the documentation for Vue 2 `renderStyles`/`renderScripts`: https://ssr.vuejs.org/guid... | 2021-08-20T19:40:43 | 2021-08-20T19:40:43 | {
"+1": 4
} | NONE |
vuejs | core | 904,272,311 | 3,842 | jincan39 | same problem, it's not friendly for migration | 2021-08-24T02:28:58 | 2021-08-24T02:28:58 | {} | NONE |
vuejs | core | 904,711,742 | 4,417 | jods4 | The catch is that this issue is a static inline `style="height: fit-content"`, whereas my understanding is that Vue performs some style auto-prefixing in bound values only: `:style="{ height: 'fit-content' }"`.
At least that's what the docs seem to say, and doing the former would be expensive as it would defeat the ... | 2021-08-24T14:51:04 | 2021-08-24T14:51:28 | {} | CONTRIBUTOR |
vuejs | core | 904,772,507 | 4,429 | qq974969638 | Hello, thank you very much for your efforts. I have a small question here. Maybe there is no need to deal with this issue, just for communication.
If a situation like this occurs, there will still be conflicts.
`<a-b/>` -> `"_component_a_b"`
`<a.b/>` -> `"_component_a46b"`
`<a46b/>` -> `"_component... | 2021-08-24T16:03:29 | 2021-08-24T16:05:57 | {} | NONE |
vuejs | core | 905,145,965 | 4,433 | orziz | 
| 2021-08-25T03:10:33 | 2021-08-25T03:10:33 | {
"+1": 1
} | NONE |
vuejs | core | 905,347,847 | 4,436 | FireMasterK | Thanks! Regenerating the lockfile did the trick! | 2021-08-25T09:44:43 | 2021-08-25T09:44:43 | {} | NONE |
vuejs | core | 906,168,656 | 4,449 | LinusBorg | ...and defining web components like this in a vue file is not really the intended workflow. | 2021-08-26T07:36:05 | 2021-08-26T07:36:05 | {} | MEMBER |
vuejs | core | 902,760,374 | 4,403 | posva | Please report the bug in Vant's repository or provide a repro without Vant | 2021-08-20T15:06:23 | 2021-08-20T15:06:23 | {} | MEMBER |
vuejs | core | 904,280,293 | 4,425 | 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... | 2021-08-24T02:51:47 | 2021-08-24T02:51:47 | {} | CONTRIBUTOR |
vuejs | core | 905,383,512 | 4,423 | Nisgrak | @posva I try with the new version 3.2.6 but stay the same | 2021-08-25T10:37:41 | 2021-08-25T10:37:41 | {} | NONE |
vuejs | core | 903,247,499 | 4,412 | LinusBorg | Jokes aside though, `import type` was generally required in Vite before 2.5 I believe? | 2021-08-22T10:34:27 | 2021-08-22T10:35:12 | {} | MEMBER |
vuejs | core | 904,347,893 | 4,426 | chaichai-fe | maybe you can use `slots.default()[0].children.default()` to get the component instances | 2021-08-24T06:03:16 | 2021-08-24T06:03:16 | {} | NONE |
vuejs | core | 905,388,847 | 3,798 | pikax | @Zclhlmgqzc can you fix `test-dts` errors?
to test locally run `yarn test-dts` | 2021-08-25T10:46:39 | 2021-08-25T10:46:39 | {} | MEMBER |
vuejs | core | 905,403,594 | 3,798 | Zclhlmgqzc | > @Zclhlmgqzc can you fix `test-dts` errors?
>
> to test locally run `yarn test-dts`
Which code is better?
```ts
export type DefineComponent<
...
- Props = Readonly<ExtractPropTypes<PropsOrPropOptions>> &
+ Props = Readonly<ExtractPropTypes<PropsOrPropOptions extends undefined ? {} : PropsOrPropOption... | 2021-08-25T11:09:18 | 2021-08-25T11:09:18 | {} | CONTRIBUTOR |
vuejs | core | 905,407,770 | 3,798 | pikax | > Which code is better?
Can't you just [not pass](https://github.com/vuejs/vue-next/pull/3798/files#diff-efea39c8acfd0a8f4e9b589fe13c1ea5813fc8bc58c371b45e210be6c5ee5afcR116) `undefined` on the generic? | 2021-08-25T11:15:06 | 2021-08-25T11:15:06 | {} | MEMBER |
vuejs | core | 905,415,035 | 3,798 | Zclhlmgqzc | > > Which code is better?
>
> Can't you just [not pass](https://github.com/vuejs/vue-next/pull/3798/files#diff-efea39c8acfd0a8f4e9b589fe13c1ea5813fc8bc58c371b45e210be6c5ee5afcR116) `undefined` on the generic?
because
```
DefineComponent =
...
& {
props: PropsOrPropOptions
}
```
```ts
const C... | 2021-08-25T11:27:05 | 2021-08-25T11:27:57 | {} | CONTRIBUTOR |
vuejs | core | 903,416,480 | 4,307 | dilepremon | All works fine, thanks | 2021-08-23T03:35:52 | 2021-08-23T03:35:52 | {} | NONE |
vuejs | core | 904,575,957 | 3,173 | wenfangdu | @Liwoj Just tried, reproducible for me as well. Ping @yyx990803 | 2021-08-24T12:01:16 | 2021-08-24T12:01:16 | {} | NONE |
vuejs | core | 905,030,307 | 4,417 | DerYeger | > The catch is that this issue is a static inline `style="height: fit-content"`, whereas my understanding is that Vue performs some style auto-prefixing in bound values only: `:style="{ height: 'fit-content' }"`.
If this is the case, I'd expect [this modified playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbX... | 2021-08-24T22:58:23 | 2021-08-24T22:58:23 | {} | NONE |
vuejs | core | 905,209,997 | 3,798 | hairyf | More than 20 days have passed since this merger. When can I merge? | 2021-08-25T06:04:43 | 2021-08-25T08:04:49 | {} | NONE |
vuejs | core | 905,336,720 | 4,437 | posva | Please, next time consider using the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js) for questions first. But feel free to come back and open an issue if it turns out to be a bug 🙂 | 2021-08-25T09:28:30 | 2021-08-25T09:28:30 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.