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,239,503,042 | 6,617 | zjffun | Related issue #6568 | 2022-09-07T14:56:42 | 2022-09-07T14:56:42 | {} | NONE |
vuejs | core | 1,239,514,371 | 6,309 | micheal-parks | This issue is affecting our team as well. For our app (which is using Vue3) some web components are not rendering correctly in very specific circumstances. One circumstance involves rendering web components within `v-for` loops, another involves un-mounting and re-mounting an element, and others are more unpredictable.... | 2022-09-07T15:05:49 | 2022-09-07T15:05:49 | {
"confused": 4
} | NONE |
vuejs | core | 1,242,098,138 | 5,767 | EzeFSpa | Exactly the same thing happens to me too.
When I modify a property of a component, the web page does not refresh it. If I modify any common html element (div, span) it does refresh.
This solution:
`server: { watch: { usePolling: true, }, },`
it didn't work for me.
Versions:
vite: 3.1.0
vuejs: 3.2.39 | 2022-09-09T15:09:11 | 2022-09-09T15:09:11 | {} | NONE |
vuejs | core | 1,242,468,033 | 6,573 | jhughes-dev | Is is possible that a directive is being applied while another is being processed? | 2022-09-09T21:01:57 | 2022-09-09T21:01:57 | {} | NONE |
vuejs | core | 1,238,576,795 | 6,609 | Sight-wcg | Minimal reproduction with vant
https://sfc.vuejs.org/#eNqVlE2P2jAQhv+K5UuMFGwtSD1QWLFCPVTqpVV7anrIJpNdbxPbtR1YhPjvHTsfBdrdshEHZ2b8zJuxXw70zhi+bYEu6NIVVhpPHPjW3GZKNkZbTw7EQpWSXe6Lx1Srb6bMPZTpA/hNay0o/1E5n6sCyJFUVjckQVwybt/oxvRxLsJL6Ja8H/PbXPmUHL7q3PkRgDEkEJKpQiOdyKHFivzdl00Q1q95bsxGKw/PPix564AFGpYE2iifscnqlhxCNK/Beja... | 2022-09-06T19:41:11 | 2022-09-06T19:58:58 | {} | NONE |
vuejs | core | 1,239,050,343 | 6,609 | LinusBorg | We don't have the capacity to debug vant, or arco-design.
Please open an issue with them.
Maybe they can verify it and create a reproduction that does *not* involve their big third party library, so we can actually evaluate the problem with Vue alone. | 2022-09-07T08:05:10 | 2022-09-07T08:08:46 | {} | MEMBER |
vuejs | core | 1,239,583,251 | 6,309 | einavk | @micheal-parks I agree that it seems the props are not passed to custom element. Does this happen with custom elements that have vue binded props as well? | 2022-09-07T15:56:59 | 2022-09-07T15:56:59 | {} | NONE |
vuejs | core | 1,240,202,669 | 6,564 | Ryokusitai | @joaovinicius
Works fine for focusout, such as tabbing and clicking elsewhere.
However, if you type Jacob and press Enter, the characters in the input element will still be Jacob.
I use Google Chrome 104.0.5112.102 | 2022-09-08T04:28:38 | 2022-09-08T04:31:04 | {} | NONE |
vuejs | core | 1,241,209,840 | 6,309 | einavk | @micheal-parks this is very similar to what we've done, except we bind some randomly generated string to data-id. | 2022-09-08T20:38:47 | 2022-09-08T20:38:47 | {
"+1": 1
} | NONE |
vuejs | core | 1,242,530,793 | 2,015 | Obapelumi | Modified @patforg's component to use the mutation observer so it works even when the teleport wrapper component gets mounted before the target element is rendered:
```vue
<template>
<Teleport :to="target" v-if="target" :disabled="!target || disabled">
<slot></slot>
</Teleport>
</template>
<script set... | 2022-09-09T22:33:58 | 2022-09-09T22:39:46 | {
"+1": 5
} | NONE |
vuejs | core | 1,238,841,783 | 4,609 | gyhyfj | same problem | 2022-09-07T02:38:11 | 2022-09-07T02:38:11 | {} | NONE |
vuejs | core | 1,239,104,167 | 6,614 | LinusBorg | I'll keep this issue open and keep #6609 closed because this issue here as a minimal reproduction out of the gate and focusses on the actual issue. | 2022-09-07T08:54:59 | 2022-09-07T08:54:59 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,240,393,382 | 6,612 | basonwoo | #6222
use the latest version of chrome could avoid this bug temporarily | 2022-09-08T08:25:43 | 2022-09-08T08:25:43 | {} | NONE |
vuejs | core | 1,240,834,132 | 4,745 | gplusdotgr | We cleaned up all the `::v-deep` occurrences in our code but I believe the warnings keep happening because third party libraries use still `::v-deep ` with the old syntax. | 2022-09-08T14:56:40 | 2022-09-08T15:23:21 | {
"+1": 4
} | NONE |
vuejs | core | 1,242,642,481 | 6,591 | michaelperel | [Here is a link](https://sfc.vuejs.org/#eNp9UctOxDAM/BUrF0CiSQEhoVW7LAfuHBCnXEo3LYHmocQtQlX/HWcLpSwSN9sz9oztkd15z4desQ0rYh20R+gq25aSYZQMosLeb6XVxruAMEJQDUzQBGfghNpOFujeePx4qFr1BXKxVNJ8ItbORoS6DyUNOc3PpG16W6N2FtC1baeetHo/PYNRWkg0PlRdr8qfqCzz24tNLu0kbSFmt+SNElTGdxUqygCKvR4OAYXPPSLN39Wdrt/SUouQZNvHQ1KImfTdQt0wZLohdvJaXhBz... | 2022-09-10T06:17:20 | 2022-09-10T06:17:20 | {} | NONE |
vuejs | core | 1,242,894,390 | 6,643 | Dedicatus546 | `InstanceType` tool would expose many properties that you don't need.
or you can create a type to describe Comp instance instead of depend on `InstanceType` tool.
```typescript
type CompInst = {
... | 2022-09-11T06:04:12 | 2022-09-11T06:04:45 | {} | NONE |
vuejs | core | 1,242,907,129 | 6,633 | Dedicatus546 | i think you could write a `ConfigProvider.vue` to config some custom component
like naive-ui
i think using `resolveComponent` has significant limitations, such as can't get component context, can't... | 2022-09-11T07:30:52 | 2022-09-11T07:30:52 | {} | NONE |
vuejs | core | 1,236,834,647 | 6,600 | LinusBorg | Works fine outside of your repro: https://jsfiddle.net/7vo168gm/1/
Might be related to Vite's processing/parsing of index.html maybe because `width` & `height` cannot have units, they must be plain numbers.
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img?retiredLocale=de#attributes
| 2022-09-05T10:42:13 | 2022-09-05T10:42:13 | {} | MEMBER |
vuejs | core | 1,237,662,416 | 6,222 | leyue | 升级chrome到最新版本可以解决，但还是有些场合无法升级浏览器版本。 | 2022-09-06T05:04:09 | 2022-09-06T05:04:09 | {
"-1": 8
} | NONE |
vuejs | core | 1,237,763,001 | 6,110 | misaon | +1
| 2022-09-06T07:28:32 | 2022-09-06T07:28:32 | {} | NONE |
vuejs | core | 1,239,278,163 | 3,848 | zouhangwithsweet | Are there any updates? | 2022-09-07T11:40:04 | 2022-09-07T11:40:04 | {} | CONTRIBUTOR |
vuejs | core | 1,241,030,140 | 4,980 | nazar1ua | @yyx990803 I still need the `defineRender` function | 2022-09-08T17:39:05 | 2022-09-08T17:39:05 | {
"+1": 15
} | NONE |
vuejs | core | 1,237,822,844 | 4,662 | tcnijmeijer | Hello there, I have created an alternate PR to try and fix this issue. I believe it is a bit more robust than the other attempt (https://github.com/vuejs/core/pull/4309). It additionally supports async components and the use of `<script setup>`. The only missing feature I can think of is the support of globally registe... | 2022-09-06T08:25:21 | 2022-09-06T08:27:47 | {
"hooray": 3
} | NONE |
vuejs | core | 1,238,520,352 | 6,591 | michaelperel | I am experiencing the same issue in multiple projects I am working on using vue 3 with the router | 2022-09-06T18:40:20 | 2022-09-06T18:40:20 | {} | NONE |
vuejs | core | 1,238,984,279 | 4,339 | chenhaihong | 应该大部分都是做多tab单页应用的来提这个feature.
@liweijian1 在页面组件外面包个壳，像下面这样子，能完全可控操作keep-alive缓存，
而且不需要额外的内部规范，比如，页面组件必须强制加上组件名，配合在meta里配置上页面组件名称，
```vue
<template>
<router-view v-slot="{ Component, route }">
<keep-alive :include="include">
<component :is="wrap(route.fullPath, Component)" :key="route.fullPath"... | 2022-09-07T06:56:52 | 2022-09-07T06:56:52 | {
"+1": 30,
"heart": 1
} | NONE |
vuejs | core | 1,239,027,665 | 4,339 | hezhongfeng | 我这边是想完全自主的管理缓存，不用`keep-alive`，要使用自己的组件，只是确实这个APi | 2022-09-07T07:42:48 | 2022-09-07T07:42:48 | {} | NONE |
vuejs | core | 1,242,464,589 | 6,573 | jhughes-dev | I saw this through the following nuxt issue: https://github.com/nuxt/framework/discussions/7296
I had some comments there, but I think there's a core issue in
`function invokeDirectiveHook(vnode, prevVNode, instance, name)`
It assumes vnode and prevVNode have the same number of "dirs". I was able to catch a case ... | 2022-09-09T20:57:27 | 2022-09-09T20:58:28 | {
"+1": 1
} | NONE |
vuejs | core | 1,242,892,500 | 6,643 | Dedicatus546 | use `render` property.
render by `h` fn
```html
<script lang="ts">
import { defineComponent, h } from "vue";
export default defineComponent({
name: "HelloWorld",
setup() {
const msg = () => {
console.log("msg");
};
return { msg };
},
render() {
return h("div", "hello");... | 2022-09-11T05:47:05 | 2022-09-11T05:48:52 | {
"eyes": 1
} | NONE |
vuejs | core | 1,242,901,183 | 6,633 | chenhaihong | @Dedicatus546 thanks for your comment. People will not directly use those components which contains default placeholder. | 2022-09-11T07:00:05 | 2022-09-11T07:00:05 | {} | NONE |
vuejs | core | 1,238,853,378 | 5,657 | TheTrunk | We were facing the same problem and as of complexity of our application non of the suggestions were easily applicable/not working (such as v-if -> v-show, playing with :key, tabindex, div nesting..).
So we ended up applying #5670 locally in postinstall script - that resolved it. | 2022-09-07T03:03:20 | 2022-09-07T03:03:20 | {} | NONE |
vuejs | core | 1,239,095,141 | 6,614 | tazyong | @LinusBorg Both Vant's Toast component and Arco-Design's Message component are implemented using Vue.render. Here is the core code. [demo](https://sfc.vuejs.org/#eNp9U8Fu2zAM/RVOGBAXdawAu2VOsaHYH+yoQx2ZSdzJkiDRLgbD/z7aclMj7XoRRD/xPZKPHsRP74u+Q7EXZdSh8QQRqfNgKns+KEFRiQdlm9a7QDDAJYeAp+mwNYYcXirSFxjhFFwLGybafFdWWe1sJAidfX... | 2022-09-07T08:47:05 | 2022-09-07T08:47:05 | {
"+1": 1
} | NONE |
vuejs | core | 1,239,206,629 | 6,613 | LinusBorg | Duplicate of #6554 . Solution was meeged but hasnt been released yet. | 2022-09-07T10:29:36 | 2022-09-07T10:29:36 | {} | MEMBER |
vuejs | core | 1,239,326,764 | 6,614 | edison1105 | related to https://github.com/vuejs/core/blob/78c199d6dbe8931520b75d8bfe0d49366a06922a/packages/runtime-core/src/renderer.ts#L2333-L2334
| 2022-09-07T12:30:28 | 2022-09-07T12:30:28 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,241,408,452 | 6,628 | muchenfine | I don't think it's a ref<string> and string type problem,
I am passing an object, not a REF
```
useHook({
name:'tom',age:18
})
```
Now T type would be
```
{name:string;age:number}
```
```
const initData = input;
let data = $ref(initData );
data = {
name:'tom',age:18
}
```
This is a failur... | 2022-09-09T01:49:08 | 2022-09-09T01:49:08 | {} | NONE |
vuejs | core | 1,241,568,146 | 5,474 | raphaelmenges | I would also highly appreciate a merge! | 2022-09-09T06:48:19 | 2022-09-09T06:48:40 | {} | NONE |
vuejs | core | 1,242,036,285 | 6,404 | emosheeep | sounds helpful to locate the trouble 😄 | 2022-09-09T14:21:44 | 2022-09-09T14:21:44 | {} | NONE |
vuejs | core | 1,242,553,619 | 181 | decademoon | This doesn't work (anymore?): [SFC playground](https://sfc.vuejs.org/#eNp9UMsOwiAQ/JXNXtCk0uixURO/Qzz4oLamPLKAmjT8u2BLvHkAdnZm2Z0d8WAtfwaJDW7dlXrr90ID5NMra8jDCB1EaMkoYEnICi3fX/om23MYkiznAEjqm6TFsuCc8YE0HAsG6BbsErw3mlWgwzBUkPS7PbA1W1b/ZGPp1pSKDYP4qzlNQcxPuoTe1rMnrHCys1Jnyx/O6GT4O6KYCSewKUMLTEYzFth5b11T16695jU9HDd0r1PEKW... | 2022-09-09T23:24:05 | 2022-09-09T23:24:05 | {} | NONE |
vuejs | core | 1,242,901,266 | 6,643 | WalkAlone0325 | why not this
```tsx
<script lang="ts">
import { defineComponent, h } from "vue";
export default defineComponent({
name: "HelloWorld",
setup(_props, { expose }) {
const msg = () => {
console.log("msg");
};
expose({ msg })
return () => (
h("div", "hello");
)
... | 2022-09-11T07:00:59 | 2022-09-11T07:00:59 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,179,704,315 | 6,246 | LinusBorg | I'll reopen this to take another look | 2022-07-10T10:53:09 | 2022-07-10T10:53:09 | {} | MEMBER |
vuejs | core | 1,180,603,611 | 6,222 | zengshenggit | +1 | 2022-07-11T16:13:20 | 2022-07-11T18:10:40 | {} | NONE |
vuejs | core | 1,183,222,194 | 4,662 | milespetrov | One workaround I'm using it to generate the `style.css` by building my app in lib mode. I then move that file into the public directory and then link to it from inside the template in my main `app.ce.js` file:
```
<template>
<link href="/style.css" rel="stylesheet" />
...
```
I need to rebuild that styles... | 2022-07-13T13:25:46 | 2022-07-13T13:25:46 | {} | NONE |
vuejs | core | 1,185,232,983 | 4,745 | webturtles18 | `[@vue/compiler-sfc] ::v-deep usage as a combinator has been deprecated. Use :deep(<inner-selector>) instead.`
```
::v-deep {
.v-input--dense {}
.v-skeleton-loader {}
}
```
I don't understand how to use :deep() for above scenario.
can anyone help for the same? | 2022-07-15T06:49:37 | 2022-07-15T06:49:37 | {
"+1": 4
} | NONE |
vuejs | core | 1,185,269,361 | 6,274 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 32571b842341109917511ac38b6d8b7cc497ebec |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-07-15T07:40:49 | 2022-07-15T07:40:49 | {} | NONE |
vuejs | core | 1,185,455,990 | 5,657 | duannx | I encounter this issue too. It only happens on SSR and production build.
I tried my best to create the minimal reproduction [sfc.vuejs.org](https://sfc.vuejs.org/#__SSR__eNp9VE1vm0AQ/StTLmDVhp4ptlqllXqp1EOkHEIOGAabBHZWuwtJZPHfO7uLCbar+uKdmbdv5+txCr5LGQ89BmmQ6VI10oBG08tdLppOkjJwAoU1jFAr6iBkaDiHHlQhJao7YhOFmSBxcuW3/OHX... | 2022-07-15T11:31:58 | 2022-07-15T11:31:58 | {
"eyes": 5
} | NONE |
vuejs | core | 1,186,527,879 | 6,286 | chirsChow | 这是来自QQ邮箱的自动回复邮件。您好，我已收到您发给我的邮件，我会尽快给您回复。 | 2022-07-17T14:02:56 | 2022-07-17T14:08:10 | {} | NONE |
vuejs | core | 1,174,791,143 | 6,222 | Enginebeck | same error | 2022-07-05T08:47:25 | 2022-07-11T18:10:31 | {} | NONE |
vuejs | core | 1,178,658,968 | 6,222 | boboZh | +1 | 2022-07-08T07:36:54 | 2022-07-11T18:10:36 | {} | NONE |
vuejs | core | 1,181,764,681 | 6,259 | posva | This is just how browsers differ. The funny part is Vue is not even running because that's Vue 2 syntax but it's importing Vue 3 😄
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2022-07-12T13:31:26 | 2022-07-12T13:31:26 | {} | MEMBER |
vuejs | core | 1,183,087,059 | 6,260 | plehnen | The thing is, in our project this inner component uses Teleport. Sometimes the backend sends an error and vue router redirects to the error page - this redirect happens while the Transition is running, and the inner component is mounted but never removed. So all states are still active, including the Teleport content. ... | 2022-07-13T11:09:21 | 2022-07-13T11:09:21 | {} | NONE |
vuejs | core | 1,184,238,238 | 6,270 | tazyong | This is a bug. It was raised three months ago, and there is no intention to solve it until now. | 2022-07-14T09:51:47 | 2022-07-14T09:51:47 | {} | NONE |
vuejs | core | 1,185,616,897 | 4,745 | edum18 | > @webturtles18 The following worked, but I am not sure if it is the intended use, as @theHacker says.
>
> ```
> :deep() {
> .class {}
> }
> ```
@monaounagi Didn't work in my case. Gives me the following error:
`
Module build failed (from ./node_modules/extract-css-chunks-webpack-plugin/dist/loader.js): ... | 2022-07-15T14:45:13 | 2022-07-15T14:56:20 | {} | NONE |
vuejs | core | 1,186,559,886 | 6,287 | jannikbuscha | If anyone has a similar problem and would like to follow up then track it here:
https://github.com/vitejs/vite/issues/9169 | 2022-07-17T16:11:50 | 2022-07-17T16:11:50 | {} | NONE |
vuejs | core | 1,187,098,784 | 4,707 | matrunchyk | @posva it's not that easy to make a reproduction link as it's not that easy to reproduce. For example, I have a large project which I cannot share for obvious reasons.
I'd love to create a blank project and share it, but I have no clue how to trigger this issue. It does trigger randomly.
From the forums and issues o... | 2022-07-18T11:10:55 | 2022-07-18T11:11:27 | {
"+1": 2
} | NONE |
vuejs | core | 1,179,711,088 | 6,246 | LinusBorg | Tip: use a custom Directive to assign such a random attribute. this keeps it out of the server-generated HTML, and you don't get any hydration errors (which are negative for you intial render performance and give your ugly warnings during dev).
Something like this is enough:
https://sfc.vuejs.org/#__SSR__eNp9kT9r... | 2022-07-10T11:35:47 | 2022-07-10T11:35:47 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,179,992,935 | 6,248 | LinusBorg | or more closely, #6241
None of these use case were intended for `<script setup>` so there's likely a couple of variations of this same basic problem to be found. | 2022-07-11T05:50:11 | 2022-07-11T05:50:11 | {} | MEMBER |
vuejs | core | 1,180,266,633 | 3,936 | titusdecali | I have the same issue (it was near impossible to narrow down), but indeed was related to v-if
@jaulz Thank you for making this issue as I NEVER would have found it (this is the only thing that comes up on Google when I search 'shapeFlag error'.
In my case, it triggers whenever I add the highlighted line here, withi... | 2022-07-11T11:14:47 | 2022-07-11T11:16:11 | {} | NONE |
vuejs | core | 1,181,397,994 | 5,584 | jackkitley | What am i doing thats wrong here? Im setting form data. not modifying a prop
> const form = useForm({
> contact: {
> title: null,
> first_name: null,
> last_name: null,
> email: null,
> cell_number: null,
> national_id_number: null,
> company: null
... | 2022-07-12T07:08:10 | 2022-07-12T07:08:54 | {} | NONE |
vuejs | core | 1,183,325,037 | 4,733 | SassNinja | The helper from @andrey-hohlov works for me!
However I'd feel better if this was built-in officially so that I don't need to worry about that helper stop working after some future update of vue.
I think many people will face this issue, in particular regarding that many posts on stackoverflow mention the simple c... | 2022-07-13T14:51:58 | 2022-07-13T14:51:58 | {
"+1": 1
} | NONE |
vuejs | core | 1,186,527,799 | 6,286 | LinusBorg | Both of these things are expected behavior and documented. | 2022-07-17T14:02:36 | 2022-07-17T14:07:46 | {} | MEMBER |
vuejs | core | 1,187,791,041 | 4,613 | lidlanca | ### workaround
[v-native-template directive as a fix](https://sfc.vuejs.org/#eNqtVsFu2zAM/RXCh8YBEjtxDhuyJNswbNhhLXbore5BtZXEnS0ZkuyuCPzvI2U5dptkw4b10ErkI0U9Pso9eB/LMqgr7i29lU5UVhrQ3FTlJhYAYQh5luZMJAw+QDSLounszXT+FiAW5M+KUioDB1B8OwEprmUlDE+hga2SBYww74iQhE2k0AaBusoNrCnCPyRM8/lSVHk+oWVkl824h5u5g5JjaF+8th8P9/3xenMgE4Ip... | 2022-07-18T17:10:50 | 2022-07-18T17:10:50 | {} | CONTRIBUTOR |
vuejs | core | 1,180,531,968 | 2,097 | aabeborn | > 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-11T15:08:58 | 2022-07-11T15:08:58 | {
"+1": 1
} | NONE |
vuejs | core | 1,186,139,211 | 6,235 | hminghe | > 老哥，你的测试用例是不正确的。
>
> KeepAlive[include='A'] A[key='1'] ==> 缓存A1 KeepAlive[include='A'] A[key='2'] ==> 缓存A2 KeepAlive[include='B'] A[key='2'] ==> 删除A1缓存 KeepAlive[include='B'] B[key='2'] ==> 删除A2缓存
>
> 你的测试用例的过程，之前的代码就能pass的。
我测试了，并不能过。
 😁
Hi, where the origin doc？i don't find this on vue official document site
| 2022-07-11T07:21:45 | 2022-07-11T07:21:45 | {} | NONE |
vuejs | core | 1,180,475,790 | 6,253 | LinusBorg | Here, we create the `legacyLeaveFromClass` only if there isn't a custom classname set.
https://github.com/vuejs/core/blob/6f1b36d0a8e2ec4f7c8f8f082056c6c32226da92/packages/runtime-dom/src/components/Transition.ts#L152-L155
as OP has set one, it stays `undefined`
But here, we try and apply this (undefined) lega... | 2022-07-11T14:23:21 | 2022-07-11T14:23:35 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,180,631,620 | 4,344 | bneeland | I had this issue when trying to build a vue3 project with a library imported as a submodule.
I solved this by:
- Deleting `yarn.lock` files from both root project and submodule
- Deleting `node_modules` from both root project and submodule
- Deleting `dist` directory from both root project and submodule
- Movi... | 2022-07-11T16:41:18 | 2022-07-11T16:54:48 | {
"+1": 2,
"hooray": 2
} | NONE |
vuejs | core | 1,179,888,541 | 6,250 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c2d42211ba3231c78f397eea1fb1c533f9bd3a84 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-07-11T02:14:19 | 2022-07-12T01:08:39 | {} | NONE |
vuejs | core | 1,182,549,631 | 5,584 | tyronksmith | @jackkitley What I was suggesting is; Is your `SelectInput` a custom component? If so, have a look at the `v-model` inside that. My example code above is within my custom component. I could not have `v-model="modelValue"` within the custom / child component. Apologies. I didn't mean to hijack an issue thread. | 2022-07-12T22:17:05 | 2022-07-12T22:17:36 | {} | NONE |
vuejs | core | 1,184,734,605 | 4,339 | hminghe | `include` 其实就可以实现了，把组件包裹一层自定义一下的 `name` 就可以了。
参考： https://github.com/hminghe/md-admin-element-plus/blob/main/src/components/multi-window/components/MultiWindowKeepAlive.vue
`include` actually does that，Wrap the component around a custom `name`.
see: https://github.com/hminghe/md-admin-element-plus/blob/main/src/c... | 2022-07-14T17:50:39 | 2022-07-14T17:52:36 | {
"+1": 2
} | NONE |
vuejs | core | 1,186,530,029 | 6,282 | LinusBorg | Top level await can only be used in children of a Suspense component. | 2022-07-17T14:09:52 | 2022-07-18T06:03:33 | {} | MEMBER |
vuejs | core | 1,179,700,985 | 6,246 | LinusBorg | What you are asking for is technically impossible. The value of a const cant be re-assigned (that's what makes it a const), yet this is what needs to happen to replace the random value generated on the client during `setup` with the one generated on the server.
> When I use a ref instead of direct assignment, it wor... | 2022-07-10T10:31:49 | 2022-07-10T10:35:29 | {} | MEMBER |
vuejs | core | 1,179,894,070 | 6,249 | edison1105 | BTW, you should `markRaw` for `component`.
```javascript
export default {
data() {
return {
component: markRaw(extendedComponent),
};
},
};
``` | 2022-07-11T02:23:32 | 2022-07-11T02:26:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,186,132,911 | 6,245 | binghc | > 你手机系统和浏览器的版本都不提供，这是想让别人怎么帮你呢？ Vite 打包默认目标要求：https://caniuse.com/es6-module-dynamic-import 想支持更旧的浏览器需要用 [@vitejs/plugin-legacy](https://github.com/vitejs/vite/tree/main/packages/plugin-legacy)
>
> 还有，Vite 是 Vite，Vue 是 Vue，这个仓库只处理 Vue 本身的问题。
IOS13.7 13.6 14.7.1 都测过
safari chrome firefox都有，你还需要什么版本？ 实际上根本不需要版本，自己... | 2022-07-16T09:37:20 | 2022-07-16T09:37:20 | {} | NONE |
vuejs | core | 1,181,546,389 | 6,258 | huzedong2015 |
> Youre reaching into instance internals which is not recommended.
>
> The exposed properties live on `.exposed`, not `.proxy`.
But I can use it in dev environment | 2022-07-12T09:39:54 | 2022-07-12T09:39:54 | {} | NONE |
vuejs | core | 1,181,565,072 | 6,258 | LinusBorg | Yes. during dev, the internal proxy exposes all component state so that devtools can access it.
Again, you are reaching into internals, which is not a good idea if you are not intimately familiar with them. | 2022-07-12T09:59:33 | 2022-07-12T09:59:33 | {} | MEMBER |
vuejs | core | 1,181,796,417 | 6,261 | LinusBorg | duplicate of #6248 | 2022-07-12T13:59:14 | 2022-07-12T13:59:14 | {} | MEMBER |
vuejs | core | 1,181,839,565 | 6,262 | LinusBorg | This reproduction does not run as it tries to import a non-existant store. please note that a *runnable* reproduction is required.
My suspicion would be that your parent passes data only on a second re-render, after the store has fetched it.
You can ask the community for guidance on how to work best in this scena... | 2022-07-12T14:35:12 | 2022-07-12T14:35:12 | {} | MEMBER |
vuejs | core | 1,184,215,546 | 6,270 | LinusBorg | duplicate of #5764 | 2022-07-14T09:29:13 | 2022-07-14T09:29:13 | {} | MEMBER |
vuejs | core | 1,186,605,230 | 6,288 | tony19 | Odd. It's working now. | 2022-07-17T20:53:21 | 2022-07-17T20:53:21 | {} | CONTRIBUTOR |
vuejs | core | 1,186,801,551 | 6,283 | LinusBorg | It's still a kind of edge case., or rather, the workaround is simple:
if you don't need a value, skip the `=""`
That's likely why i hasn't come up before - people don't write custom directive like that often. | 2022-07-18T06:06:00 | 2022-07-18T06:06:00 | {} | MEMBER |
vuejs | core | 1,186,600,776 | 6,277 | lidlanca | vue doesn't add the value attribute to the element if its empty .(edited) ( see https://github.com/vuejs/core/issues/6277#issuecomment-1187714777 for more correct analysis)
```js
<button id="a" value='' disabled=''></button>
```
renders to
```html
<button id="a" disabled=''>
```
and so the css selector o... | 2022-07-17T20:19:18 | 2022-07-18T20:24:58 | {} | CONTRIBUTOR |
vuejs | core | 1,179,896,658 | 6,229 | shaobeichen | The correct solution is: you need to split the files that don't contain scss variables and the files that contain scss variables, and introduce the files that contain scss variables in additionalData, so that they won't be introduced repeatedly and the scss variables can be used in each component. | 2022-07-11T02:28:15 | 2022-07-11T02:28:15 | {
"+1": 1,
"hooray": 1,
"laugh": 1
} | NONE |
vuejs | core | 1,181,525,569 | 6,258 | LinusBorg | Youre reaching into instance internals which is not recommended.
The exposed properties live on `.exposed`, not `.proxy`. | 2022-07-12T09:18:18 | 2022-07-12T09:18:18 | {} | MEMBER |
vuejs | core | 1,183,477,913 | 1,758 | hyvyys | https://github.com/sagalbot/vue-select/issues/1603
Use the named import instead of the default one.
```js
import { VueSelect } from 'vue-select';
``` | 2022-07-13T17:12:25 | 2022-07-13T17:12:25 | {} | NONE |
vuejs | core | 1,183,750,928 | 5,781 | daniloribeiro00 | @javastation Any news? | 2022-07-13T22:38:30 | 2022-07-13T22:38:30 | {} | NONE |
vuejs | core | 1,185,207,550 | 6,273 | LinusBorg | the content of the shallow ref is non-reactive. You pass the content to the child. So you pass a non-reactive content to the child. so you can't watch that object. | 2022-07-15T06:07:03 | 2022-07-15T06:07:03 | {} | MEMBER |
vuejs | core | 1,179,887,592 | 6,250 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 7103bde57b40737a7fba2d14d37af8d7f8a900ae |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-07-11T02:13:02 | 2022-07-11T02:13:02 | {} | NONE |
vuejs | core | 1,180,053,765 | 4,344 | xu-Aurora | > I also met the same issue, the parent Application(vue3+vite2.0) share some common component to child Application, but if the common component exist slot , the child Application will throw an exception( vue3+ webpack5), <img alt="image" width="474" src="https://user-images.githubusercontent.com/22649700/172043383-a200... | 2022-07-11T07:21:55 | 2022-07-11T07:21:55 | {} | NONE |
vuejs | core | 1,184,171,319 | 6,270 | liulinboyi | Hope this can help you https://github.com/vuejs/core/issues/5764 | 2022-07-14T08:45:54 | 2022-07-14T08:47:23 | {} | MEMBER |
vuejs | core | 1,186,531,557 | 6,283 | LinusBorg | From a quick first look: Both of these Syntax "errors" in arrays are valid Javascript.
Its just that the implentation expects a expression in the directive value and doesnt account for an empty one - much like Vue's own directives dont like empty values.
The SSR ones need a fix though. | 2022-07-17T14:15:56 | 2022-07-17T14:16:18 | {} | MEMBER |
vuejs | core | 1,186,564,829 | 4,668 | devopg | 
same problem as components and as vars if use only in template | 2022-07-17T16:44:49 | 2022-07-17T16:44:49 | {} | NONE |
vuejs | core | 1,186,787,911 | 6,283 | catrope | Yes, you're right, I didn't realize that double/trailing commas are allowed in arrays, but they are. They're not allowed in function calls though, which is why the SSR ones are broken as you say (and SSR is where I ran into this bug) | 2022-07-18T05:38:19 | 2022-07-18T05:38:19 | {} | CONTRIBUTOR |
vuejs | core | 1,186,800,223 | 6,282 | LinusBorg | Solution: Don't use top-level-await. | 2022-07-18T06:04:00 | 2022-07-18T06:04:00 | {} | MEMBER |
vuejs | core | 1,179,702,390 | 6,246 | Fuzzyma | @LinusBorg Yes you still get the hydration error but the UI updates accordingly to the correct value once the component was hydrated. I tested it in the sfc playground and you can see, that the value logged in the console is the same as the one which is being shown. And that's totally fine for my usecase (and i conside... | 2022-07-10T10:41:17 | 2022-07-10T10:41:17 | {} | NONE |
vuejs | core | 1,179,330,594 | 6,242 | LinusBorg | Good points, I was a bit too quick to judge here, thanks!
Reopened #6241 accordingly. The generated code in that issue's playground even already uses the render proxy correctly to *read* `ctx.query` for the v-model value, but doesn't do so for the generated event listener. That seems fixable.
In this issue here c... | 2022-07-08T20:17:25 | 2022-07-11T05:48:45 | {} | MEMBER |
vuejs | core | 1,184,658,875 | 5,764 | liulinboyi | > I also encountered this problem. This is a bug, yet 3 months have passed, and there is no intention to fix it. Very disappointed!
Template and tsx should choose one for rendering
https://staging-cn.vuejs.org/guide/essentials/template-syntax.html
https://vuejs.org/guide/essentials/template-syntax.html | 2022-07-14T16:39:42 | 2022-07-15T15:17:49 | {
"confused": 1
} | MEMBER |
vuejs | core | 1,186,519,622 | 6,286 | chirsChow | You want to get the old value in the callback method parameter of watch, not just the new value | 2022-07-17T13:32:28 | 2022-07-17T13:32:28 | {} | NONE |
vuejs | core | 1,186,720,163 | 6,282 | littleweb | > https://vuejs.org/api/sfc-script-setup.html#top-level-await
The problem has not been solved！ | 2022-07-18T03:20:19 | 2022-07-18T03:20:19 | {} | NONE |
vuejs | core | 1,179,814,785 | 6,248 | Aniruddh-J | Probably related to #6242 | 2022-07-10T22:46:04 | 2022-07-10T22:46:04 | {} | NONE |
vuejs | core | 1,180,958,100 | 3,652 | mauril26 | > This link explains how these components work together, their order is very important https://v3.vuejs.org/guide/migration/suspense.html#combining-with-other-components, but unfortunately, there are still bugs here
Update: https://vuejs.org/guide/built-ins/suspense.html#combining-with-other-components | 2022-07-11T22:35:50 | 2022-07-11T22:35:50 | {} | NONE |
vuejs | core | 1,181,386,710 | 5,540 | hcg1023 | I created a PR @LinusBorg #6256 | 2022-07-12T06:54:21 | 2022-07-12T06:54:21 | {
"+1": 4
} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.