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,622,072,421 | 5,657 | HasanMothaffar | It turns out in my case the component that was causing this bug was wrapped in a `<transition>` component. After removing the transition, everything works fine. (Vue version: `3.2.45`)
Before:
```vue
<template>
<transition name="fade">
<div>
// .. other divs
</div>
</transition>
</template
``... | 2023-07-05T16:09:23 | 2023-07-05T16:09:23 | {
"heart": 1
} | NONE |
vuejs | core | 1,622,696,219 | 8,727 | silentmantra | Your case is opposite of mine : https://github.com/vuejs/core/issues/7999.
Also I've seen your question on stackoverlfow, let's discuss there in the comments.
| 2023-07-05T23:49:24 | 2023-07-05T23:53:30 | {
"+1": 1
} | NONE |
vuejs | core | 1,624,151,880 | 8,728 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d0a2f781496b6bbd0b4418fa631bd576126a90ce |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-07-06T18:42:03 | 2023-07-06T18:42:03 | {} | NONE |
vuejs | core | 1,624,538,828 | 5,836 | MarkSky | > I made a PR. feel free to review. [playground](https://deploy-preview-6548--vue-sfc-playground.netlify.app/#eNqlVm1v4zYM/itcbkPbQ2Wnl7uh9XLFXj4Owwb0MGCAvyg2HWuVJUOSk+aK/vdRku06TtsPu6IFLJJ6+CLyYR8Xv7RtsutwkS3W3zGWqz90ySUUumm1QuVgL1wNRWedbsRXvpEIVmpngasSfru7A2e4ssIJrWySK8Zuc5WrtS2MaB1YdF1LEkFoxkHEroxu4CxJw8n7PhsNHsFgBU... | 2023-07-07T02:06:50 | 2023-07-07T02:11:49 | {} | NONE |
vuejs | core | 1,624,635,027 | 5,836 | edison1105 | @MarkSky
the version of vue in my playground is based on the PR. | 2023-07-07T03:49:09 | 2023-07-07T03:49:09 | {} | MEMBER |
vuejs | core | 1,627,701,375 | 7,689 | jd-solanki | Hi team,
I will be doing some refactoring in [Anu](https://github.com/jd-solanki/anu)'s codebase and doing so might break existing PR that relies on this PR. Is there any chance that it can get merged any time soon?
Regards. | 2023-07-09T12:26:03 | 2023-07-09T12:26:03 | {} | NONE |
vuejs | core | 1,630,583,143 | 8,576 | yyx990803 | FYI, the return type of `defineProps` does take this into account:
```ts
interface Props {
foo?: boolean
}
const p = defineProps<Props>()
// ^ { foo: boolean }
p.foo
// ^ boolean
```
The interface declares `foo` as being optional, but it is **not** the type of the resolved runtime props. The resolve... | 2023-07-11T10:36:08 | 2023-07-11T10:36:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,632,124,200 | 6,841 | simonmaass | @ruslankonev did u ever figure out what this was? I have the same error... | 2023-07-12T09:01:16 | 2023-07-12T09:01:16 | {} | NONE |
vuejs | core | 1,633,430,192 | 8,769 | LittleSaya | > And here's why it only happens in dev, _if I recall correctly_:
>
> In prod, we do a finer-grained props update - ~we do a looseEqual check to catch precisely the case I described before: elements created in the template~ the compiler knows which props are stable (like your static inline array in `:a=""`) and whic... | 2023-07-13T02:08:59 | 2023-07-13T02:08:59 | {} | NONE |
vuejs | core | 1,628,389,979 | 8,745 | LinusBorg | This is issue report is not actionable as there is not way provided for us to reproduce the issue.
you likely made a mistake somewhere else that keeps this component from being mouonted.
a) Ask in the repo discussions (https://github.com/vuejs/core/discussions)
b) as on our discord (chat.vuejs.org)
If you re... | 2023-07-10T07:26:39 | 2023-07-10T07:26:39 | {} | MEMBER |
vuejs | core | 1,630,019,559 | 5,625 | cuonghuynh | @Ge6ben it works for me. Thanks! | 2023-07-11T02:43:32 | 2023-07-11T02:43:32 | {
"hooray": 1,
"rocket": 2
} | NONE |
vuejs | core | 1,630,273,124 | 6,351 | haoqunjiang | This PR seems to have broken vue-i18n's type:
https://github.com/intlify/vue-i18n-next/blob/f092f90ee4c0e26d915e84d8e86a97e999d9aaaa/packages/vue-i18n-core/src/directive.ts#L88C12-L88C12 | 2023-07-11T07:11:46 | 2023-07-11T07:11:46 | {
"eyes": 1
} | MEMBER |
vuejs | core | 1,633,304,860 | 8,760 | SunnyCrypto | @Shyam-Chen
please note the data or state is not reactive.
the flow is doing an action via a lib method, then passing the state to a component and re-render. | 2023-07-12T22:49:55 | 2023-07-12T22:49:55 | {} | NONE |
vuejs | core | 1,618,247,440 | 8,707 | Alfred-Skyblue | CC @sxzz | 2023-07-03T13:18:50 | 2023-07-03T13:18:50 | {} | MEMBER |
vuejs | core | 1,622,268,500 | 8,447 | blakebjorn | Had a similar issue and was able to resolve the runtime error by catching the compilation error inside the render function
```
import {compile, h} from 'vue';
export default {
name: "dynamic-component",
props: {
templateHtml: {templateHtml: true, type: String}
},
render() {
... | 2023-07-05T18:29:23 | 2023-07-05T18:29:23 | {} | NONE |
vuejs | core | 1,623,985,068 | 8,447 | andrewspy | @blakebjorn using `compile()` inside `try {}` does catch and prevent the error, however, the descriptive syntax error is lost in the catch block, i.e.
```
Template compilation error: Element is missing end tag.
1 | <div> with missing end tag...
| ^
at <BadComponent>
at <App>
``` | 2023-07-06T16:39:17 | 2023-07-06T16:39:17 | {
"+1": 1
} | NONE |
vuejs | core | 1,628,394,903 | 8,734 | LinusBorg | Vue slots content comes in the form of functions that retrun vnodes.
But when you wrapp a vue component as a custom element, this component will not receive vue slots content.
Instead, the custom element uses [native `<slot>` elements](https://github.com/vuejs/core/discussions), and those inject actual HTML element... | 2023-07-10T07:30:16 | 2023-07-10T07:30:16 | {} | MEMBER |
vuejs | core | 1,633,667,818 | 7,240 | sgpinkus | > The docs you link here still use a plain object (just one with methods on it), not a class, and certainly not a class with private fields.
Oh OK by POJO I thought you meant something basically something JSON serializable. I'm probably using "POJO" wrong. But, isn't a class *instance* just an object with methods on... | 2023-07-13T06:54:09 | 2023-07-13T06:54:09 | {} | NONE |
vuejs | core | 1,619,451,523 | 8,708 | yanyunwu | 急急急🧐 | 2023-07-04T04:15:25 | 2023-07-04T04:15:25 | {} | NONE |
vuejs | core | 1,619,693,471 | 8,549 | Alfred-Skyblue | TBR | 2023-07-04T07:39:48 | 2023-07-04T07:39:48 | {} | MEMBER |
vuejs | core | 1,619,982,490 | 8,608 | Shyam-Chen | https://vuejs.org/api/general.html#definecomponent | 2023-07-04T10:28:06 | 2023-07-04T10:28:06 | {} | CONTRIBUTOR |
vuejs | core | 1,630,026,475 | 8,602 | zqran | > Where is it blocked now? Why not merge it?
There are no members to review this PR yet, maybe you can `@` some members to take a look. | 2023-07-11T02:53:39 | 2023-07-11T02:53:39 | {} | CONTRIBUTOR |
vuejs | core | 1,631,224,457 | 8,734 | mav-rik | I was hoping ref on a `<slot />` would work, but it doesn't, I have just checked.
Indeed a union return-types increases cognitive load and doesn't seem to be a good solution. And indeed apparently a new API is required. At the end of the day it still looks like a bug, and not like a feature or well reasoned limitati... | 2023-07-11T17:34:30 | 2023-07-11T17:34:30 | {} | NONE |
vuejs | core | 1,628,615,694 | 1,927 | jerrywu001 | more detail:
https://github.com/jerrywu001/vue3-toastify/issues/22 | 2023-07-10T09:51:11 | 2023-07-10T09:51:11 | {} | NONE |
vuejs | core | 1,630,016,382 | 8,602 | rxliuli | Where is it blocked now? Why not merge it? | 2023-07-11T02:39:22 | 2023-07-11T02:39:22 | {} | NONE |
vuejs | core | 1,632,285,074 | 8,767 | LinusBorg | `$slot.header` returns a function. That function, when called, will render the slot content. if there's no slot content, it will return `undefined`
`v-if="$slot.header()"`
Be aware that:
1. This can have a certain runtime cost as the slot function is essentially a render function creating the vdom for the slot... | 2023-07-12T10:54:15 | 2023-07-12T10:54:36 | {} | MEMBER |
vuejs | core | 1,632,375,886 | 8,767 | lct01lct | I don't think it solved this problem.
You can take a look at this link, which provides a more concise description of my problem: https://play.vuejs.org/#eNp9Uk1v2zAM/SuaNqAp0NmH3lLXWDb0sB22Yd1RF8ehXbWyJOjDTRH4v5eU7TgBipxM8pHPj+I78I21WR+Br3nhaydtYKrS7b3gwQvOPIRoS6FlZ40L7MAcNGxgjTMdu8Kxq7sjtpmqWb4hQkKEro32gfXSy60Cdk/jq+... | 2023-07-12T11:40:57 | 2023-07-12T11:40:57 | {} | NONE |
vuejs | core | 1,632,521,041 | 8,487 | dodgex | @mattersj my project is on 3.2.45 and i have multiple components using symbols (InjectionKey to be accurate) as props. and with 3.3.4 i got this issue.
I tested `alpha.1`, `.6`, `.12` and `.13` aswell as `.beta1` and the `3.3.0` release. with versions <= alpha.12 it worked; with >= alpha.13 I got the `Cannot convert... | 2023-07-12T13:21:43 | 2023-07-12T13:21:43 | {} | NONE |
vuejs | core | 1,632,670,027 | 8,760 | SunnyCrypto | @Shyam-Chen
if you want to build a combination of lib + components, the lib should be agnostic of frameworks.
the components are built on top of the lib, and they can be either Vue or React components, even components from other frameworks.
some states are handled in lib, they are not reactive, and the states ar... | 2023-07-12T14:47:48 | 2023-07-12T14:47:48 | {} | NONE |
vuejs | core | 1,632,905,626 | 8,652 | jacekkarczmarczyk | https://v3-migration.vuejs.org/breaking-changes/v-model.html | 2023-07-12T17:08:36 | 2023-07-12T17:08:36 | {} | CONTRIBUTOR |
vuejs | core | 1,623,376,236 | 8,727 | silentmantra | @shareefhadid check my solution https://stackoverflow.com/questions/76621595/vue-3-slots-attributes-can-you-pass-data-through-props/76627568#76627568 | 2023-07-06T09:51:37 | 2023-07-06T09:51:37 | {
"+1": 2
} | NONE |
vuejs | core | 1,626,408,863 | 8,716 | hungify | @edison1105
Maybe I made a mistake somewhere example above.
But help me let check other reproduction:
https://stackblitz.com/edit/vitejs-vite-f41ufy?file=src%2FApp.vue,src%2Fcomponents%2FButton.vue&terminal=dev
> 
... | 2023-07-08T01:33:36 | 2023-07-08T01:34:36 | {} | NONE |
vuejs | core | 1,629,849,584 | 6,420 | wlee221 | As a workaround for now, I'm casting the return type of `toRefs` manually:
```ts
const { prop1, prop2 } = toRefs(props) as Required<ReturnType<typeof toRefs<PropInterface>>>;
``` | 2023-07-10T23:06:28 | 2023-07-10T23:06:28 | {} | NONE |
vuejs | core | 1,619,459,128 | 8,708 | Justineo | 最小化重现是必须的，谢谢。
https://new-issue.vuejs.org/?lang=zh-cn#why-repro | 2023-07-04T04:26:46 | 2023-07-04T04:26:46 | {} | MEMBER |
vuejs | core | 1,619,940,873 | 8,706 | slothvips | So, why not change the name? | 2023-07-04T10:01:12 | 2023-07-04T10:01:12 | {} | NONE |
vuejs | core | 1,630,015,694 | 8,755 | sixdjango | 所以我想知道 defineComponent 里如何实现 slot 泛型 像 template 里一样 | 2023-07-11T02:38:38 | 2023-07-11T02:38:38 | {} | NONE |
vuejs | core | 1,632,755,579 | 8,757 | LinusBorg | Either way we can't do much without a reproduction. Seems like an issue for vite though, yes. | 2023-07-12T15:28:50 | 2023-07-12T15:28:50 | {} | MEMBER |
vuejs | core | 1,634,350,154 | 8,775 | edison1105 | has PR https://github.com/vuejs/core/pull/8671 | 2023-07-13T14:29:57 | 2023-07-13T14:29:57 | {
"heart": 2
} | MEMBER |
vuejs | core | 1,359,030,000 | 7,381 | SailSpring | > Please **DO NOT** abuse pull requests. Do experiments in your own repo. Thanks.
Ok, I got it.Thanks. | 2022-12-20T08:59:23 | 2022-12-20T08:59:23 | {} | NONE |
vuejs | core | 1,359,089,651 | 7,373 | sxzz | Duplicate of #7165 | 2022-12-20T09:46:48 | 2022-12-20T09:46:48 | {} | MEMBER |
vuejs | core | 1,359,383,005 | 7,384 | LinusBorg | ```diff
<script type="module">
- import { createApp } from "https://cdn.bootcdn.net/ajax/libs/vue/3.2.45/vue.esm-browser.js"
+ import { createApp } from "vue"
import HelloWorld from './HelloWorld.es.js'
console.log('HelloWorld', HelloWorld)
const app = createApp({
components: {
... | 2022-12-20T13:49:01 | 2022-12-20T13:49:01 | {} | MEMBER |
vuejs | core | 1,359,440,219 | 7,343 | LinusBorg | Please open a new issue if you manage to create a runnable reproduction that doesn't involve vue-stripe or the stripe API. | 2022-12-20T14:22:16 | 2022-12-20T14:22:29 | {} | MEMBER |
vuejs | core | 1,359,919,092 | 7,293 | SavkaTaras | Hello @baiwusanyu-c ,
I hope you are well.
Is that an issue that the e2e test failed per your change?
Thanks,
Taras | 2022-12-20T18:01:46 | 2022-12-20T18:01:46 | {} | NONE |
vuejs | core | 1,360,879,908 | 7,387 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 0d471c6fbc353a12e768c2a5af38122fe719d45e |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-21T05:37:39 | 2022-12-21T06:08:33 | {} | NONE |
vuejs | core | 1,361,249,107 | 7,390 | Talljack | I'm not sure if this is a bug, so I raised an issue as a suggestion, sorry | 2022-12-21T12:23:32 | 2022-12-21T12:23:32 | {} | CONTRIBUTOR |
vuejs | core | 1,364,060,071 | 7,408 | LinusBorg | This only happens when devtools are enabled. disable your extension and the heap stays nice and clean:
### Vue Devtools enabled
<img width="856" alt="Bildschirmfoto 2022-12-23 um 16 50 12" src="https://user-images.githubusercontent.com/1444526/209363086-81d431f0-43fd-4fc0-aa91-6a57de2e3897.png">
Looking into th... | 2022-12-23T15:53:05 | 2022-12-23T16:11:32 | {
"hooray": 1
} | MEMBER |
vuejs | core | 1,365,257,995 | 7,408 | LinusBorg | > The original issue is in production.
Then I suggest comparing heap snapshots like I did and reporting back what kind of elements are piling up.
The leaky behavior I identified with the code you shared is definitely happening in dev only, because of devtools. The relevant code is being treeshaken in a pro build... | 2022-12-26T15:51:32 | 2022-12-26T22:24:50 | {} | MEMBER |
vuejs | core | 1,357,975,609 | 7,373 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 74cd871d9a0fbe350eaea740162e34a4f9506872 |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-12-19T17:09:40 | 2022-12-20T03:06:09 | {} | NONE |
vuejs | core | 1,316,055,563 | 7,141 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | afaa357d5bb0089af17d7545811ded330829170a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-16T00:01:25 | 2022-12-20T10:07:40 | {} | NONE |
vuejs | core | 1,359,129,521 | 7,370 | LinusBorg | This issue will stay closed until you provide me with a github repository that produces the error upon starting the dev server / build.
| 2022-12-20T10:17:10 | 2022-12-20T10:17:10 | {} | MEMBER |
vuejs | core | 1,362,529,745 | 6,238 | zhangzhonghe | > Will it make differentiation in development mode and production mode?
User-defined comments are removed by the build tool in production mode.
https://github.com/vuejs/core/blob/50f13278f9f90e92201890f2c8d9a5abe278038e/packages/shared/src/patchFlags.ts#L95-L100 | 2022-12-22T08:03:26 | 2022-12-22T08:03:26 | {} | MEMBER |
vuejs | core | 1,362,884,012 | 7,393 | LinusBorg | I cannot reproduce the described behavior with the reproduction link provided. | 2022-12-22T14:10:50 | 2022-12-22T14:10:50 | {} | MEMBER |
vuejs | core | 1,363,608,653 | 7,384 | ddmy | > 你如果是直接在独立的 HTML 页中通过 `<HelloWorld>` 方式调用组件的话，请改成 `<hello-world>`。HTML 是大小写不敏感的。
包括自组件自身传递的props也需要用'-'分割 | 2022-12-23T04:38:15 | 2022-12-23T04:38:15 | {} | NONE |
vuejs | core | 1,363,725,767 | 7,391 | sxzz | I guess we have to avoid `</script>` string in `<script>` block since the compiler cannot perceive if it's a JavaScript string or the end tag when parsing SFC.
There's a workaround, splitting the string.
```vue
<script lang="ts" setup>
const myVar = "</" + "script>";
</script>
``` | 2022-12-23T08:19:46 | 2022-12-23T08:19:46 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,363,888,802 | 7,409 | LinusBorg | Thanks for resurfacing this though, it admittedly fell below the radar. | 2022-12-23T11:52:23 | 2022-12-23T11:52:23 | {} | MEMBER |
vuejs | core | 1,363,892,578 | 7,409 | paul-thebaud | OK. Thanks for the explanation.
No problem to consider this as duplicate. | 2022-12-23T11:58:37 | 2022-12-23T11:58:37 | {} | NONE |
vuejs | core | 1,335,228,372 | 7,266 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 53048f64d5706bd56467e7ce275e2657b0de26d0 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-02T13:19:30 | 2022-12-26T02:17:23 | {} | NONE |
vuejs | core | 1,365,064,615 | 7,401 | Tzyito | I think this problem is related to the online editor. The performance in Vue SFC Playground is normal [=> here](https://sfc.vuejs.org/#eNqdkltO9DAMhbdi5YWLaKP/tX9BAhYAC8hLp3WZoDaJYncQGnXvOOncYBBIvFTxSfzVJydbdR9CuZlQVapmHMPQMN4ZB1Cv/931NhLXWlZZeVzboYOKkfg5+nBrFMcJjVqkJ15jPGr6QCFsveu+xRThnFP4c1CtT2aTktpoAwMhTyFD7Rh8ZFjQf... | 2022-12-26T10:22:53 | 2022-12-26T10:24:51 | {} | NONE |
vuejs | core | 1,365,488,576 | 7,417 | LinusBorg | When the component re-renders because you changed the ref, the *whole* template is updated with *all* of the latest data. That's how re-renders work. the whole component template virtualDOM is re-rendered with the current data and diffed against the previous version. | 2022-12-26T22:22:53 | 2022-12-26T22:24:16 | {} | MEMBER |
vuejs | core | 1,357,978,340 | 7,373 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 74cd871d9a0fbe350eaea740162e34a4f9506872 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-19T17:11:22 | 2022-12-20T03:07:49 | {} | NONE |
vuejs | core | 1,359,129,987 | 7,370 | sj7112 | https://sfc.vuejs.org/#eNp1Um2K2zAQvcqgUpLARk7JPze70BPsBQxFlseOElkS0ji7IfjuHdles7RdjPF4vt6befMQv0KQtwFFKU6EfbCK8KVyAKfG3EBbldJzJazvjPt9RtVgrMQcLziBrVPxqYx/k44mEFjlOi6kVAlISEOYikwffCTYyMLXF9QkKW1+5oD2LnmLkoG2XIWJpKp1JWQ228Hp7W6XsebuCxLdLULSPmAzdc/VK014ZBdA8MmQ8a4EVTPEQDgBAryZhs4l/Dgcvi8e7a2PJXw7Ho+Lp1b62kU/uIbdbduC8w4hY... | 2022-12-20T10:17:33 | 2022-12-20T10:17:33 | {} | NONE |
vuejs | core | 1,362,874,775 | 6,238 | zhangzhonghe | I am trying to express my perspective more clearly:
1. #6080 is definitely a bug.
2. This bug only occurs in development mode because the comments are removed in production mode.
3. Therefore, the code to fix this bug is unnecessary in production mode and can be removed.
4. Vue identifies code that can be removed... | 2022-12-22T14:02:32 | 2022-12-22T14:02:32 | {} | MEMBER |
vuejs | core | 1,363,323,021 | 7,402 | Rawrcasm | I am seeing the issue in #7393 in my app. The app is using SSR and not using Nuxt. When I replicate the problem area in the playground, I am getting a similar but different issue as described in this bug. Strangely enough, in the playground example, nothing even renders for me (SSR on or off) unless:
1. I remove the... | 2022-12-22T20:40:38 | 2022-12-22T20:40:38 | {} | NONE |
vuejs | core | 1,363,366,441 | 7,402 | LinusBorg | It's likely just a bug in the playground, which had to mind of stimulate the Server side step, as it all runs in the client. | 2022-12-22T21:30:31 | 2022-12-22T21:30:31 | {} | MEMBER |
vuejs | core | 1,364,481,112 | 7,408 | alexnivanov | @LinusBorg thanks, disabling dev tools helped indeed! I'll investigate the real app issue further. It's not that we are experiencing any performance issues, but the memory usage grows steadily (like 1-2 gigs per day), and the page crashes eventually... | 2022-12-24T07:46:20 | 2022-12-24T07:46:20 | {} | NONE |
vuejs | core | 1,360,782,474 | 7,384 | ddmy | > ```diff
> <script type="module">
> - import { createApp } from "https://cdn.bootcdn.net/ajax/libs/vue/3.2.45/vue.esm-browser.js"
> + import { createApp } from "vue"
> import HelloWorld from './HelloWorld.es.js'
> console.log('HelloWorld', HelloWorld)
> const app = createApp({
> compon... | 2022-12-21T02:50:49 | 2022-12-21T02:50:49 | {} | NONE |
vuejs | core | 1,361,688,687 | 4,294 | krystof-k | I'm not sure if this is related, but I'm getting warnings when using type intersection like this:
```vue
<script setup lang="ts">
export interface Props {
padding: 'medium' & ('small' | 'medium');
}
defineProps<Props>();
</script>
```
Results in
```
Invalid prop: type check failed for prop "padding... | 2022-12-21T17:14:24 | 2022-12-21T17:14:49 | {
"+1": 1,
"eyes": 2
} | NONE |
vuejs | core | 1,363,023,219 | 7,400 | sj7112 | After restart the computer, the warning is gone...
But there's another one:
checkout my [SFC demo](https://sfc.vuejs.org/#__SSR__eNqNVMGO0zAQ/ZVRLu3utkn3GtICAglxQCCEOOXippPirmMb2+mCovw7YztJ0y5CnBKPZ+bNvJnnLn... | 2022-12-22T16:16:35 | 2022-12-22T16:16:35 | {} | NONE |
vuejs | core | 1,364,505,529 | 7,408 | LinusBorg | Do you see this in production? If so, that would be another story. What I found above related to code that is only present in the bundle during development, it would be tree-shaken in a production build.
If you only see it in dev: do you keep your dev-server and browser tab running for days without closing it? | 2022-12-24T10:28:47 | 2022-12-24T10:28:47 | {} | MEMBER |
vuejs | core | 1,364,507,161 | 3,024 | codeAndxv | @octavioamu thx | 2022-12-24T10:40:21 | 2022-12-24T10:40:21 | {} | NONE |
vuejs | core | 1,364,746,388 | 4,294 | klerpi | Vue macros didn't work for me on this Nuxt 3 layer I'm working on so I found a workaround.
It's annoying but until this gets fixed on Vue it's what I came up with:
```vue
<script lang="ts" setup>
const { props } = defineProps<{ props: NavigationItem }>()
</script>
```
This way I still use the limited "l... | 2022-12-25T22:23:47 | 2022-12-25T22:23:47 | {
"+1": 4
} | NONE |
vuejs | core | 1,365,226,448 | 7,408 | alexnivanov | The original issue is in production. The memory still leaks without dev tools, even though not so badly. I still have to investigate the root cause though. | 2022-12-26T14:39:29 | 2022-12-26T14:39:29 | {} | NONE |
vuejs | core | 1,365,876,060 | 7,408 | alexnivanov | Thanks a lot, it helped to isolate the issue!
Good news is that it's not related with WS updates. It's about with Chart.js library integration: we have some charts that are updated regularly, and it's causing memory leaks.
This issue may be closed it seems. I'll investigate further and open a new one if it's rela... | 2022-12-27T12:44:55 | 2022-12-27T12:44:55 | {
"+1": 1
} | NONE |
vuejs | core | 1,358,769,529 | 7,373 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c3dd1de74005c5dc420d964e2252c4d5e3e0dac3 |
|<span aria-hidden="true">🔍</span> Latest deploy l... | 2022-12-20T02:54:34 | 2022-12-20T02:54:34 | {} | NONE |
vuejs | core | 1,362,962,531 | 7,399 | LinusBorg | `vue/macros` is a valid export of the vue package. Defined here:
https://github.com/vuejs/core/blob/fe77e2bddaa5930ad37a43fe8e6254ddb0f9c2d7/packages/vue/package.json#L41
And you will find the referenced macros.d.ts file in the specified location.
It has been like that for 12 months now, since 3.2.24.
Plea... | 2022-12-22T15:17:59 | 2022-12-22T15:24:29 | {} | MEMBER |
vuejs | core | 1,363,327,786 | 7,403 | roddypratt | > ...Vue overrides the classes with the ones it knows - and `show` is not one of them, so *it's effectively being removed*.
That's more than a little unexpected. Is there a reason that Vue can't leave those classes it *doesn't* know about untouched? Would having and additional (but less flexible) variant of the `:c... | 2022-12-22T20:48:06 | 2022-12-22T20:53:57 | {} | NONE |
vuejs | core | 1,358,725,514 | 7,370 | sj7112 | https://sfc.vuejs.org/#eNp1Um1u2zAMvQqhYUgLNHKG/PPSAjtBL2BgkGXaUSJLgkSnDQLffZTsAMG2/jBMPfKRjx838SsEeZlQ1OJAOAarCN8aB3DozAW0VSm9NsL6wbjfR1QdxkYs/ooD2DpUDzR+Jh1NILDKDUyk1AhISFMoJDMGHwk2svLtCTVtfuYEC2Wl09Xina1ToWsfsCt8+SgEbhkCCD4ZMt7VoNrk7UTIWbPjw3R0rOHHbvd9RbS3Ptbwbb/fr0ir9HmIfnIdw33fg/MOIWJARVw5emthB7sSPRexWeCbeBFLL9tRB... | 2022-12-20T01:52:56 | 2022-12-20T01:52:56 | {} | NONE |
vuejs | core | 1,362,987,351 | 7,400 | LinusBorg | That warning is not related to "two way data binding" but it certainly is not something to ignore if it happens. | 2022-12-22T15:41:41 | 2022-12-22T15:41:41 | {} | MEMBER |
vuejs | core | 1,363,030,424 | 7,400 | sj7112 | 
| 2022-12-22T16:23:19 | 2022-12-22T16:23:19 | {} | NONE |
vuejs | core | 1,363,885,200 | 7,409 | LinusBorg | #7401 also is related to this, in a way. I'll try and get an overall perpective on this over the holidays. | 2022-12-23T11:46:23 | 2022-12-23T11:46:23 | {} | MEMBER |
vuejs | core | 1,365,769,744 | 7,408 | alexnivanov | 
@LinusBorg thanks for insight! I don't have this nice **Objects allocated between...** selector though :( | 2022-12-27T09:56:07 | 2022-12-27T09:56:07 | {} | NONE |
vuejs | core | 1,366,194,746 | 7,408 | LinusBorg | I'll close this here and will talk with Akryum about this on the devtools side. | 2022-12-27T21:43:29 | 2022-12-27T21:43:29 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,359,001,434 | 7,380 | Justineo | Please **DO NOT** abuse pull requests. Do experiments in your own repo. Thanks. | 2022-12-20T08:32:17 | 2022-12-20T08:32:17 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,291,082,969 | 5,844 | michaelpumo | I also witnessed this issue in Nuxt 3.
On hard load I can retrieve the DOM element via ref and acquire its size using getBoundingClientRect() but when navigating between routes (on the client), the onMounted() appears to run before the DOM is ready and present.
Minimal reproduction:
https://stackblitz.com/edit/... | 2022-10-25T20:12:41 | 2022-12-20T17:33:40 | {
"+1": 1
} | NONE |
vuejs | core | 1,362,977,963 | 7,400 | LinusBorg | Reproduction link doesn't reproduced described error, therefore we have no way of investigating this issue.
The effect in the screenshot is because you have SSR on and the simulated SSR Render is still running its timer. In a real world scenario you would not start a timer in setup on the server, hopefully.
> Why... | 2022-12-22T15:32:49 | 2022-12-22T15:32:49 | {} | MEMBER |
vuejs | core | 1,363,340,427 | 7,402 | Rawrcasm | My mistake, I missed the resolve in the playground. I have updated that which can be found in this [playground](https://sfc.vuejs.org/#__SSR__eNp1VEtv00AQ/isjc0hKE9stLSnGrYSQOJVSQTlhDmt7nG5q75rddaIozX9n1q84j0aJMq+d5zezcb6Upbus0AmcUCeKlwY0mqq8iwQvSqkMfJVFCZmSBYxczzLWfBSJSCRSaANlztaoNNzCn0gAbICnAVxMQPDk5YEVGEDkPBAtiI4c2E... | 2022-12-22T21:06:36 | 2022-12-22T21:07:01 | {} | NONE |
vuejs | core | 1,365,105,878 | 7,401 | LinusBorg | No, it's specific to the combo of a boolean kebap-case prop being passed to a Vue component that's being wrapped with `defineCustomElement()`.
https://github.com/vuejs/core/pull/7412 will solve it for the most part, I think, but would still be an edge case left concerning async custom elements, which I hope to addr... | 2022-12-26T11:23:40 | 2022-12-26T11:26:21 | {} | MEMBER |
vuejs | core | 1,359,334,068 | 5,704 | wangzhaohe | @hooray Is this sloved? | 2022-12-20T13:14:17 | 2022-12-20T13:14:17 | {} | NONE |
vuejs | core | 1,360,070,387 | 4,294 | Hecatron |
after running into this myself the quick and easy answer which I think has already been mentioned above
is to just install and use [vue-macros](https://vue-macros.sxzz.moe/features/better-define.html)
which allows this just by adding it as a plugin, really simple
There's also [vueuse](https://vueuse.org/) for ev... | 2022-12-20T19:45:14 | 2022-12-20T19:45:14 | {
"+1": 2,
"heart": 1
} | NONE |
vuejs | core | 1,360,087,748 | 4,344 | Rusinas | Same problem with custom UI library built with Vite and Vue 3 which I'm trying to use in my Nuxt app. The error is in the component which uses onMounted() hook:
```
[Vue warn]: onMounted is called when there is no active component instance to be associated with. Lifecycle injection APIs can only be used during execut... | 2022-12-20T20:03:00 | 2022-12-20T20:03:00 | {} | NONE |
vuejs | core | 1,365,132,566 | 7,391 | jakub791 | Shouldn't it easy to differentiate the two? | 2022-12-26T12:17:03 | 2022-12-26T12:17:03 | {} | NONE |
vuejs | core | 1,366,194,366 | 7,420 | LinusBorg | You were never meant to be able to mix script setup and Options API. Yet it worked in a couple of situations - tough in development. These usages mostly broke in `production`.
In 3.2.45. we fixed these `development`/`production` inconsistencies.
https://github.com/vuejs/core/commit/f73925d76a76ee259749b8b48cb6889... | 2022-12-27T21:42:15 | 2022-12-27T21:42:15 | {} | MEMBER |
vuejs | core | 1,360,788,039 | 7,384 | Justineo | 你如果是直接在独立的 HTML 页中通过 `<HelloWorld>` 方式调用组件的话，请改成 `<hello-world>`。HTML 是大小写不敏感的。 | 2022-12-21T02:58:54 | 2022-12-21T02:58:54 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,363,035,014 | 7,400 | sj7112 | Just solved! should use dlg.modalVIew.value instead!! | 2022-12-22T16:25:12 | 2022-12-22T16:25:12 | {} | NONE |
vuejs | core | 1,363,706,211 | 7,402 | zhangzhonghe | I have found the cause of the problem. The ```vue.runtime.esm-browser.js``` and ```server-renderer.esm-browser.js``` modules contain some of the same code, as shown below:
```js
let currentInstance = null;
const setCurrentInstance = (instance) => {
currentInstance = instance;
instance.scope.on();
};
co... | 2022-12-23T07:53:09 | 2022-12-23T08:35:39 | {} | MEMBER |
vuejs | core | 1,365,515,329 | 7,418 | LinusBorg | The browser will hoist the div out of the paragraph, as it's not allowed to nest a block element in an inline element.
The server renderer though just strings together your HTML as you render it. So you get a hydration mismatch.
Solution: Write valid HTML.
We even have precicely this code as an example in our ... | 2022-12-27T00:10:53 | 2022-12-27T00:12:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,365,783,625 | 7,408 | LinusBorg | Seems you picked the wrong option? You need to pick this:
<img width="862" alt="Bildschirmfoto 2022-12-27 um 11 14 48" src="https://user-images.githubusercontent.com/1444526/209651511-e0ba2376-9f54-4db9-96e9-91e3b7550274.png">
| 2022-12-27T10:15:40 | 2022-12-27T10:15:40 | {} | MEMBER |
vuejs | core | 1,359,121,335 | 7,370 | sj7112 | I only import object.ts, but the setup program will call Object.prototype.testfunc and pop up errors.
It only happens for function names start with "Object.prototype.". I guess it's because the name is conflicted with some internal merge strategy.
. | 2022-12-23T20:32:27 | 2022-12-23T20:32:27 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.