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,600,228,981 | 8,618 | wenfangdu | @edison1105 Where is it documented and how can I try it? | 2023-06-21T05:57:37 | 2023-06-21T05:57:37 | {} | NONE |
vuejs | core | 1,600,382,728 | 7,556 | TechAkayy | Would be good to have this merged in please, as devtools is still having the issue. Thanks in advance! | 2023-06-21T08:06:51 | 2023-06-21T08:06:51 | {} | NONE |
vuejs | core | 1,592,238,204 | 8,527 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 9492dff43c4858e28b972c761ee323f512e18d33 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-06-15T02:16:38 | 2023-06-15T04:31:58 | {} | NONE |
vuejs | core | 1,594,825,967 | 8,525 | ghiscoding | I have the same problem with Vue Transition, the issue starts after upgrading to 3.3.0 and higher, 3.2.47 is unaffected by this issue. Vue 3.3.0 brings better support with Volar and TypeScript, so I would guess it's probably related. The issue is only for kebab case which we decided to use in our project
 as Document
const templateContainer = doc && /... | 2023-06-21T06:33:04 | 2023-06-21T06:33:04 | {
"+1": 2
} | NONE |
vuejs | core | 1,594,542,274 | 5,993 | favouredddd | 对组件包一层div可以解决这个问题。 | 2023-06-16T11:40:18 | 2023-06-16T11:40:18 | {
"+1": 1
} | NONE |
vuejs | core | 1,594,647,774 | 6,908 | niksy | Also having the same issue and it’s hard to replicate, but applying these changes fixes the problem. What can we do to get this merged and ready for next release? | 2023-06-16T13:06:14 | 2023-06-16T13:06:14 | {} | NONE |
vuejs | core | 1,595,945,939 | 8,286 | fabon-f | As a workaround, component definition with `defineComponent` in vue 3.3 ([doc](https://vuejs.org/api/general.html#function-signature)) works well with complex types. I think it works on both SFC and TSX.
```html
<script lang="ts">
import { h } from 'vue';
export default defineComponent((props: ComplexType, cont... | 2023-06-18T04:07:43 | 2023-06-18T17:22:19 | {
"+1": 1
} | NONE |
vuejs | core | 1,596,760,649 | 8,112 | mannymu | <img width="450" alt="image" src="https://github.com/vuejs/core/assets/15630104/06acf149-c2a9-4135-82d9-5e29b1c7a940">
getSSRProps does not support rendering of these properties. But I use v-html in ssr server is normal | 2023-06-19T08:41:29 | 2023-06-19T08:41:29 | {} | NONE |
vuejs | core | 1,597,208,489 | 8,474 | zhangenming | >
In my opinion, v-bind={is,key,ref,name}, this all four should behave the same
| 2023-06-19T13:36:35 | 2023-06-19T13:36:35 | {} | CONTRIBUTOR |
vuejs | core | 1,597,800,113 | 8,373 | oddcelot | Just found out about this issues and maybe I got some workaround for now (feedback to verify welcome 🤞)
For my use case this seems to work with `props` and `defineExpose()`
So for usage I landed on:
```ts
type TestType = { id: number; thing: string }
type MyGenericComponentType = PseudoComponent<typeof MyGeneri... | 2023-06-19T21:52:21 | 2023-06-19T21:52:40 | {
"+1": 1
} | NONE |
vuejs | core | 1,598,754,121 | 5,303 | letoast | > https://www.npmjs.com/package/vue-deepunref
This package breaks my deploys on Netlify.
the solution by @Hulkmaster works however! | 2023-06-20T13:12:53 | 2023-06-20T13:12:53 | {} | NONE |
vuejs | core | 1,598,765,431 | 8,609 | goncharof |
> Due to the update in `todos`, the elements are being re-rendered, and `TodoItem` relies on `todos`.
Hello, thank you for your assistance, but why "updated" hook in options api is not called ? and do you know how to avoid re-render on all child components in computed lists, because they can be really big ? | 2023-06-20T13:17:11 | 2023-06-20T13:28:48 | {} | NONE |
vuejs | core | 1,599,993,182 | 8,612 | Neverflow | I read the source code, found that framework will register your imports when compiling the template,
You didn't import the Test type explicitly, so it can't recognize your type.
If you want to import type from d.ts files, yo... | 2023-06-21T02:49:31 | 2023-06-21T02:49:31 | {} | NONE |
vuejs | core | 1,600,031,581 | 8,612 | Neverflow | > @Neverflow external imports type are already supported in 3.3. for global type
>
> ```ts
> vue({
> script: {
> globalTypeFiles: [
> './src/types/index.d.ts'
> ]
> }
> })
> ```
>
> and
>
> ```ts
> //src/types/index.d.ts
> declare interface Test {
> name: string;
> }
> ```
... | 2023-06-21T03:47:12 | 2023-06-21T03:47:12 | {} | NONE |
vuejs | core | 1,600,098,762 | 8,619 | baiwusanyu-c | ~Added an internal hook to suspense to execute teleport after suspense is resolved~ | 2023-06-21T05:27:35 | 2023-06-21T07:35:42 | {} | MEMBER |
vuejs | core | 1,600,899,341 | 8,083 | sxzz | You can try [betterDefine](https://vue-macros.sxzz.moe/features/better-define.html) of Vue Macros. | 2023-06-21T14:03:58 | 2023-06-21T14:03:58 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,590,453,843 | 8,529 | Justineo | > 当我显示tab-A时改变的commonProps一样会影响到tab-B，但预期的效果是tab-B不受影响
把这两个 tab 的数据隔离开才是更容易维护的做法，而不是绑同样的数据却预期进行不同的渲染。在数据层做适当的抽象，也可以进行优雅地处理。 | 2023-06-14T04:34:57 | 2023-06-14T04:34:57 | {} | MEMBER |
vuejs | core | 1,591,004,287 | 7,836 | sto3psl | @sxzz that would be fantastic! | 2023-06-14T11:22:49 | 2023-06-14T11:22:49 | {} | CONTRIBUTOR |
vuejs | core | 1,594,003,859 | 8,527 | wangyewei | > LGTM.
>
> But it would be advisable to add JSDoc for enhanced robustness
I have added JSDoc. | 2023-06-16T02:27:39 | 2023-06-16T02:27:39 | {} | CONTRIBUTOR |
vuejs | core | 1,596,187,553 | 8,572 | laterdayi | @liulinboyi I'm not sure what caused it, but before it was OK
| 2023-06-18T15:44:57 | 2023-06-18T15:44:57 | {} | NONE |
vuejs | core | 1,596,197,807 | 8,572 | liulinboyi | I think the [Attribute type checking part](https://www.typescriptlang.org/docs/handbook/jsx.html#attribute-type-checking) can solve this issue.
vite-env.d.ts
```typescript
/// <reference types="vite/client" />
declare module "*.vue" {
import { DefineComponent } from "vue";
const component: DefineCom... | 2023-06-18T16:28:45 | 2023-06-18T16:32:19 | {} | MEMBER |
vuejs | core | 1,599,997,002 | 8,613 | Alfred-Skyblue | Do not modify variables dependent on the render function in the render function. | 2023-06-21T02:54:50 | 2023-06-21T02:54:50 | {} | MEMBER |
vuejs | core | 1,600,030,885 | 8,612 | edison1105 | @Neverflow
external imports type are already supported in 3.3.
for global type
```ts
vue({
script: {
globalTypeFiles: [
'./src/types/index.d.ts'
]
}
})
```
and
```ts
//src/types/index.d.ts
declare interface Test {
name: string;
}
``` | 2023-06-21T03:45:54 | 2023-06-21T03:45:54 | {} | MEMBER |
vuejs | core | 1,600,611,280 | 8,611 | jakob-kruse | This seems to be a duplicate of #2981 | 2023-06-21T10:46:49 | 2023-06-21T10:46:49 | {
"eyes": 1
} | NONE |
vuejs | core | 1,587,402,141 | 8,556 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/5244536085)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/5244536085/jobs/9470702218) | :white_check_mark: success |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/52445360... | 2023-06-12T14:01:07 | 2023-06-14T05:42:02 | {} | CONTRIBUTOR |
vuejs | core | 1,590,996,103 | 8,376 | KaelWD | @shengxinjing No difference with 5.1.3 | 2023-06-14T11:17:04 | 2023-06-14T11:17:04 | {} | CONTRIBUTOR |
vuejs | core | 1,593,849,543 | 8,587 | edison1105 | see #8409 | 2023-06-15T23:40:30 | 2023-06-15T23:40:30 | {} | MEMBER |
vuejs | core | 1,593,851,444 | 8,577 | Alfred-Skyblue | Because `Plugin` is a union type, its original intention is to constrain objects, rather than to implement a class, or you can directly implement a plugin using the object-oriented approach.
```ts
const myPlugin: Plugin = {
install(app: App) {}
}
``` | 2023-06-15T23:44:17 | 2023-06-15T23:44:17 | {} | MEMBER |
vuejs | core | 1,596,166,617 | 8,572 | laterdayi | same https://github.com/vuejs/language-tools/issues/3301 | 2023-06-18T14:22:23 | 2023-06-18T14:22:23 | {} | NONE |
vuejs | core | 1,596,337,570 | 8,474 | edison1105 | @zhangenming
Like @shaileshnighojkar said:
> you are passing 'name' as a data to the slot content.
Most developers think so, don't they?
It's technically possible, but it's not worth it and this change may even be a breaking change.
IMO, If a slot has a name, it should be clearly defined, which is good practi... | 2023-06-19T01:01:52 | 2023-06-19T01:01:52 | {} | MEMBER |
vuejs | core | 1,596,374,800 | 8,373 | ErikSeyferth | Same problem here:
```javascript
const overviewTable = ref<InstanceType<typeof OverviewTable> | null>(null)
```
| 2023-06-19T02:00:16 | 2023-06-19T02:00:16 | {} | NONE |
vuejs | core | 1,597,010,065 | 8,112 | edison1105 | I think it needs to be fixed, and this only happens in optimized compilation. For client-compiled render functions it works.
https://github.com/vuejs/core/blob/d2c3d8b70b2df6e16f053a7ac58e6b04e7b2078f/packages/server-renderer/src/render.ts#L317 | 2023-06-19T11:24:13 | 2023-06-19T11:24:13 | {
"+1": 9
} | MEMBER |
vuejs | core | 1,597,165,921 | 5,625 | Ge6ben | I fixed it by installing it !!
```
npm install --save-dev @babel/types | 2023-06-19T13:09:37 | 2023-06-19T13:09:37 | {
"+1": 6,
"heart": 3,
"rocket": 2
} | NONE |
vuejs | core | 1,599,130,304 | 8,612 | Disservin | > You can only use the current file's type or interface at present.
I dont follow,
you can use the interface like this in the sfc just fine. However, trying to use it for `defineProps` fails and it's not immediately clear to the programmer why you can use it like shown below but not use it for defining props. Also,... | 2023-06-20T16:33:26 | 2023-06-20T16:33:26 | {} | CONTRIBUTOR |
vuejs | core | 1,600,007,755 | 8,613 | RayforReal | https://play.vuejs.org/#eNptUUFqhDAUvUpwY2REne00CqVX6NKNaCxCTEJMpBACvUVv0FXbRaEwB5q21+iPSkll/iL5+Xn//fcSG91Kmc2GRqeIaDpK1mha1RxBWNsKw7Vz65F0w1xZi7pGN9nEhMYJco7kvlxzkgfdZGrVIDVkwyiF0sgiRfsUdbQfOL0TUOSUa+RQr8SIYpgf17zm9HFBA6wxbNlDOLarkIlqI2H4dvTRCj5pWEEuKv0sXCQ3nvE/wEvf7oPmhRP8nBCQllXIG7YLRjMmHvDRh2ffgxToUhzFl/PT9/vn19vz... | 2023-06-21T03:09:46 | 2023-06-21T03:09:46 | {} | NONE |
vuejs | core | 1,601,140,491 | 8,373 | padcom | Here's a plot twist:
The actual shape of type T defined by the generic component is known when this component's genericaly-typed prop is being assigned.
```vue
<template>
<div><slot :item="item" /></div>
</template>
<script lang="ts" setup generic="T = any">
defineProps<{
item: T
}>()
defineSlots<... | 2023-06-21T16:15:56 | 2023-06-21T16:32:32 | {} | CONTRIBUTOR |
vuejs | core | 1,733,019,943 | 9,288 | renovate[bot] | ### Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for *any* future 1.x releases. But if you manually upgrade to 1.x then Renovate will re-enable `minor` and `patch` updates automatically.
If you accidentally closed this PR, or if you ch... | 2023-09-25T06:47:27 | 2023-09-25T06:47:27 | {} | CONTRIBUTOR |
vuejs | core | 1,734,007,573 | 6,095 | devonik | Anything new here ? | 2023-09-25T15:46:22 | 2023-09-25T15:46:22 | {
"eyes": 7
} | NONE |
vuejs | core | 1,736,397,930 | 7,383 | skirtles-code | Similar to #6484. | 2023-09-26T22:38:19 | 2023-09-26T22:38:19 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,738,708,218 | 9,308 | baiwusanyu-c | This is similar to #7256, let me think about how to solve it
https://deploy-preview-7266--vue-sfc-playground.netlify.app/#eNp9U01v2zAM/SuaLm2BNj70FrjZR9AB22Erth11UWzaUSNLgiSnAQz991FU7ATDNl9s8j0+kdTzxD86tzqOwNe8Do1XLrIAcXQbYdTgrI9sYh46lljn7cBukHqzQFtrolQG/BlcVVs7kBxyhGmsCSi3t2/sKYvcdlIHuBOmrspReAgGEQanZQSMGKt3Y4zWsA+... | 2023-09-28T08:31:02 | 2023-09-28T08:31:02 | {} | MEMBER |
vuejs | core | 1,733,548,051 | 9,281 | avinean | What you said makes sense and clear for me.
But I'm talking not about inferring types but about generating types.
I mean watch components during development and dynamically generate types. | 2023-09-25T12:06:11 | 2023-09-25T12:06:11 | {} | NONE |
vuejs | core | 1,735,494,080 | 9,261 | xiaoxiangmoe | > I'm not sure if bundler and minifier can handle it perfectly (cross module boundary). But yeah, I get the idea.
You can try it
```ts
import { defineConfig } from 'vite'
export default defineConfig({
plugins: [],
build: {
minify: 'terser'
}
})
```
And add code to here
<img width="725" alt="... | 2023-09-26T12:58:25 | 2023-09-26T13:30:34 | {} | CONTRIBUTOR |
vuejs | core | 1,737,171,192 | 9,297 | SebbeJohansson | WAIT! thats the reason for the issue?! THats weird | 2023-09-27T10:58:35 | 2023-09-27T10:58:35 | {} | NONE |
vuejs | core | 1,737,256,867 | 9,303 | baiwusanyu-c | The reason why the console prints 'Unexpected call the func' is because when the function parameter passed to `createVNode` is a function, the parameter will be processed as a functional component. | 2023-09-27T12:02:08 | 2023-09-27T12:02:08 | {} | MEMBER |
vuejs | core | 1,732,778,262 | 9,206 | Alfred-Skyblue | Can someone take a look at this PR? | 2023-09-25T01:44:38 | 2023-09-25T01:44:38 | {} | MEMBER |
vuejs | core | 1,735,167,908 | 6,494 | skirtles-code | It is quite common for events to be emitted without a listener in the parent. Component libraries do this all the time. There doesn't need to be a warning for this.
The addition of a warning causes many of the unit tests to fail. I suggest running `pnpm test-unit` before opening a PR to confirm that your changes don... | 2023-09-26T09:28:02 | 2023-09-26T09:28:02 | {} | CONTRIBUTOR |
vuejs | core | 1,735,471,382 | 9,297 | edison1105 | duplicate of #7775 | 2023-09-26T12:44:12 | 2023-09-26T12:44:12 | {} | MEMBER |
vuejs | core | 1,736,775,759 | 6,347 | LeonChen1024 | > https://twitter.com/edison11051/status/1706625485655208263 Is this thread discussing this issue?
yes | 2023-09-27T06:24:09 | 2023-09-27T06:24:09 | {} | NONE |
vuejs | core | 1,736,908,993 | 5,952 | maximilliangeorge | @sodatea Thanks for updating us 💖 I can vouch for the aforementioned workarounds, I'm currently using them successfully. But it will be great to see a proper solution. | 2023-09-27T08:08:16 | 2023-09-27T08:08:36 | {} | NONE |
vuejs | core | 1,737,998,443 | 9,305 | Disservin | > Link to minimal reproduction
runtime-dom.esm-bundler.js
This is no reproduction. | 2023-09-27T20:00:51 | 2023-09-27T20:00:51 | {} | CONTRIBUTOR |
vuejs | core | 1,738,872,266 | 9,303 | posva | Using [PascalCase in your component](https://play.vuejs.org/#eNqNU8Fu2zAM/RXBl7RAbWHoTplrdCt62A7bsG43XzyZidXZlCDRaYAi/z5KbhzXToECAWLxUY+PT+Rz8tnabNdDsk5ygs62FUFRohB586GgRnvBP84RynTWICDlkpGY8UCVozuDO3C+Im1QyAEIuUUu41+JuZwQ89Erpy0JD9QHWDOvI7Ek2zjTiVUmF0jQu/o03rzjMmNyOBzxEpVBz5UW1Dfi4lLcFOI5yA1JpoWsNduL1R+EvQVFUAtVta3Grdj... | 2023-09-28T10:18:06 | 2023-09-28T10:18:06 | {} | MEMBER |
vuejs | core | 1,730,940,011 | 5,912 | johnsoncodehk | > LGTM. Plz resolve the conflicts
Done. | 2023-09-22T07:30:15 | 2023-09-22T07:30:15 | {} | MEMBER |
vuejs | core | 1,731,142,122 | 8,940 | skirtles-code | Would it be worth adding some tests for this? I can easily imagine somebody trying to tweak that RegExp in future and accidentally breaking support for Chinese characters. | 2023-09-22T09:53:47 | 2023-09-22T09:53:47 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,731,412,915 | 8,987 | funkso2010 | Hello @baiwusanyu-c & @sxzz ,
I hope you are doing well.
Do you guys have any estimates when the new version of vue3 is going to be released?
Thank you! | 2023-09-22T13:24:01 | 2023-09-22T13:24:01 | {} | NONE |
vuejs | core | 1,732,187,741 | 9,134 | Alfred-Skyblue | @coreyworrell Can you put the use case into the Playground to help me better troubleshoot the issue? | 2023-09-23T02:38:15 | 2023-09-23T02:38:15 | {} | MEMBER |
vuejs | core | 1,732,862,948 | 9,288 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 85.9 kB | 32.6 kB | 29.5 kB |
| vue.global.prod.js | 132 kB | 49.3 kB | 44.4 kB |
### Usages
| Name | Size |... | 2023-09-25T03:51:56 | 2023-09-25T03:51:56 | {} | NONE |
vuejs | core | 1,734,904,608 | 9,263 | yangmingshan | @xiaoxiangmoe The benefits of your approach are:
1. More friendly for minifier (possible inline output).
2. Slightly smaller size.
Right? | 2023-09-26T06:26:44 | 2023-09-26T06:26:44 | {} | CONTRIBUTOR |
vuejs | core | 1,735,234,716 | 9,263 | xiaoxiangmoe | Yes. | 2023-09-26T10:08:52 | 2023-09-26T10:08:52 | {} | CONTRIBUTOR |
vuejs | core | 1,735,296,880 | 9,261 | xiaoxiangmoe | <details>
<summary>Some source code in packages/compiler-core/src/errors.ts</summary>
```ts
export enum ErrorCodes {
// parse errors
ABRUPT_CLOSING_OF_EMPTY_COMMENT,
CDATA_IN_HTML_CONTENT,
DUPLICATE_ATTRIBUTE,
END_TAG_WITH_ATTRIBUTES,
END_TAG_WITH_TRAILING_SOLIDUS,
EOF_BEFORE_TAG_NAME,
EO... | 2023-09-26T10:52:52 | 2023-09-26T10:59:53 | {} | CONTRIBUTOR |
vuejs | core | 1,736,904,779 | 9,264 | posva | I think someone reported the same bug in Pinia but with a boiled down repro so I added it here [simplified](https://play.vuejs.org/#eNp9VE1zmzAQ/Ssqh5jMOHDIzXUybdN0Jj20mTpHLgQvhERIjD6wMwz/vU+SwcRNwwlp9+0+7cfro69tm3SWolW01oWqW8M0GdsynovqKouMzqLrTNRNK5VhPVNULtkuN8UTG1ipZMOyCPAs+jw53RVSjKYkdSeXYO7RM6vpxmojm42Rio6hktRfJC4t... | 2023-09-27T08:05:14 | 2023-09-27T08:05:14 | {} | MEMBER |
vuejs | core | 1,736,975,775 | 5,952 | daniluk4000 | > @sodatea Dear Vue team members.
>
> I would like to inquire if there is a plan for merging PRs? While I have been in the process of upgrading to Vue 3, I have encountered several issues, and some of these issues could be resolved through specific PRs. However, these PRs have remained in a state of suspension for s... | 2023-09-27T08:48:07 | 2023-09-27T08:48:07 | {} | NONE |
vuejs | core | 1,733,019,982 | 9,289 | renovate[bot] | ### Renovate Ignore Notification
Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for *any* future 7.x releases. But if you manually upgrade to 7.x then Renovate will re-enable `minor` and `patch` updates automatically.
If you accidentally closed this PR, or if you ch... | 2023-09-25T06:47:29 | 2023-09-25T06:47:29 | {} | CONTRIBUTOR |
vuejs | core | 1,734,134,853 | 7,958 | ubeytd | In our case, build problems were caused because the package imports `@vue/runtime-dom@3.3.4` was imported to our shared library and from there to the frontend by mistake, when we find that the build problem is resolved, BUT we still have red lines in the editor everywhere about ref. @yanniznik | 2023-09-25T16:57:42 | 2023-09-25T16:57:56 | {
"+1": 1,
"confused": 2
} | NONE |
vuejs | core | 1,735,286,761 | 9,261 | yangmingshan | > @yangmingshan It's not about vue's size. It's about the size of application which using the new export enum.
I think this has a very slight impact on the size of the application. | 2023-09-26T10:45:21 | 2023-09-26T10:45:21 | {} | CONTRIBUTOR |
vuejs | core | 1,736,999,401 | 5,952 | daniluk4000 | > @daniluk4000 I hope it can be processed as soon as possible, many issues have been bothering me for a long time.
Lol I didn't see you literally commented the last one, sorry.
> I hope it can be processed as soon as possible
So do I. | 2023-09-27T09:03:13 | 2023-09-27T09:03:13 | {} | NONE |
vuejs | core | 1,739,717,195 | 8,594 | posva | > One might even argue that getCurrentInstance should not be allowed anywhere except for DevTools.
Not at all, it's actually pretty useful. It's used to know if we are in the context of a component's setup.
> In all seriousness my use case is pretty much the same as for plugins. Except plugin installs require boi... | 2023-09-28T17:11:50 | 2023-09-28T17:11:50 | {} | MEMBER |
vuejs | core | 1,728,700,187 | 6,347 | SunnyCrypto | We got the same leak issue when using the `Teleport` component with the `disabled` prop.
The DOM nodes under the Teleport can't be garbage collected after the close or destruction.
**It remains in the Detached Elements forever.**
@AlexandreBonaventure @pkrzyszko @1zxca @zhaokun1219
```vue
<Teleport to="body... | 2023-09-21T03:08:32 | 2023-09-22T06:58:50 | {
"rocket": 1
} | NONE |
vuejs | core | 1,731,550,114 | 8,870 | skirtles-code | I'm not sure I understand the use case here. Is there a legitimate reason for these functions to accept values that aren't strings? Isn't calling `toString()` just hiding the problem rather than fixing it? Perhaps it would be better to add a warning somewhere further up the callstack to report the original mistake that... | 2023-09-22T14:46:44 | 2023-09-22T14:46:44 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,732,470,185 | 9,281 | baiwusanyu-c | Yes, `const comp = ref<InstanceType<typeof Comp>>()` is only responsible for type safety and can ensure that the type is correct when you write code. Vue will not generate its object based on this type during the compilation phase and pass it to the ref function to define a `reactive` object. | 2023-09-24T04:01:17 | 2023-09-24T04:01:17 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,732,789,494 | 9,286 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 85.9 kB | 32.6 kB | 29.5 kB |
| vue.global.prod.js | 132 kB | 49.3 kB | 44.4 kB |
### Usages
| Name | Size |... | 2023-09-25T02:00:08 | 2023-09-25T02:00:08 | {} | NONE |
vuejs | core | 1,733,125,028 | 9,285 | edison1105 | the root cause is:
`\n` will render as an empty text node if preserving whitespace, that lead attrs does not fall through. I feel this is expected behavior for now, because if replace the comment with a text node, the attrs also do not fall through. [see](https://play.vuejs.org/#__DEV__eNp9UstOwzAQ/BXjS0CiyaG3klYCVKl... | 2023-09-25T08:02:42 | 2023-09-25T08:05:37 | {} | MEMBER |
vuejs | core | 1,728,688,702 | 6,256 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 3ca5b986d9bf0c1c3dc3ef3c0b9fa8439bbdce29 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-09-21T02:50:40 | 2023-09-26T02:21:10 | {} | NONE |
vuejs | core | 1,736,617,608 | 9,261 | yangmingshan | LGTM | 2023-09-27T03:29:57 | 2023-09-27T03:29:57 | {} | CONTRIBUTOR |
vuejs | core | 1,737,948,246 | 9,134 | coreyworrell | @Alfred-Skyblue nevermind, I think my [issue was resolved](https://play.vuejs.org/#eNqtVl1v2zYU/SuENsAyZklOu26A5gRphw7oNrTFEmwP0x5k6TpmI1ECSdlODf/3HZKSTbtJ6oe+xOL95rn3HmYbvG7beNVRkAYzVUjeaqZId+1VJnjdNlKzf/jnXJZsIZuajeLEHY3L6JdMzBLnBHMcNNVtlWvCibHZTadaEoqY5jU1nb7MgovpNAusFvo+cDKcB2/23SKvqnle3Pcaxv5s8pKLuziOe9vkOFUy5MLR0... | 2023-09-27T19:18:46 | 2023-09-27T19:18:46 | {} | NONE |
vuejs | core | 1,731,082,029 | 9,276 | baiwusanyu-c | Duplicate of #9249 | 2023-09-22T09:10:12 | 2023-09-22T09:10:12 | {} | MEMBER |
vuejs | core | 1,731,095,062 | 9,276 | FlyingCaiChong | ok~ | 2023-09-22T09:19:49 | 2023-09-22T09:19:49 | {} | NONE |
vuejs | core | 1,734,131,080 | 7,958 | yanniznik | @ubeytd Did you find a solution to this ? Having the exact same symptoms on Vue 2.7, monorepo with a project using @react/types... | 2023-09-25T16:54:52 | 2023-09-25T16:55:27 | {} | NONE |
vuejs | core | 1,728,688,713 | 6,256 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 3ca5b986d9bf0c1c3dc3ef3c0b9fa8439bbdce29 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-09-21T02:50:41 | 2023-09-26T02:21:12 | {} | NONE |
vuejs | core | 1,735,726,117 | 9,177 | leoleoasd | Thank you @chenfan0. Now I understand why this doesn't work.
However, SHOULD this work? Is current behavior considered a bug?
1. If it should work, we should fix this
2. If it shouldn't work (i.e. a 'feature' rather than a 'bug'), we should clarify this in the documentation (like in the FAQ section of reactivity pag... | 2023-09-26T15:01:47 | 2023-09-26T15:02:04 | {} | NONE |
vuejs | core | 1,736,526,269 | 6,037 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 85.9 kB | 32.6 kB | 29.5 kB |
| vue.global.prod.js | 132 kB | 49.3 kB | 44.4 kB |
### Usages
| Name | Size |... | 2023-09-27T01:22:53 | 2023-09-27T01:22:53 | {} | NONE |
vuejs | core | 1,737,154,058 | 6,897 | baiwusanyu-c | Thank you for your PR, the original issue has been closed, and now close this PR | 2023-09-27T10:45:56 | 2023-09-27T10:45:56 | {
"laugh": 1
} | MEMBER |
vuejs | core | 1,738,614,210 | 9,308 | jleifeld | If anyone else have this issue and need a hack to solve this problem you can use `<div style="display: none;"></div>` inside the slot. Then it works again. | 2023-09-28T07:21:43 | 2023-09-28T07:21:43 | {} | NONE |
vuejs | core | 1,739,159,832 | 5,912 | skirtles-code | I think there's a problem with the ordering of the `deps` array. New `deps` get pushed on the end, but they need to be inserted in the order they are accessed to ensure the dirtiness checks run in the correct order.
Here's an example to illustrate what I mean. Sorry it's so convoluted, but it's a difficult problem t... | 2023-09-28T13:22:33 | 2023-09-28T13:22:33 | {} | CONTRIBUTOR |
vuejs | core | 1,732,797,356 | 9,285 | yanghoxom | @edison1105
> if so, this is the expected behavior. here is a warning:
if I remove config whitespace: 'preserve',
it will be able to inherit normally even if the first element in template is a comment
this is why I think is the conflict between them | 2023-09-25T02:10:48 | 2023-09-25T02:13:13 | {} | NONE |
vuejs | core | 1,733,201,806 | 9,285 | yanghoxom | @edison1105
thank you for reply
it still works fine in vue 2, where \n will be converted to whitespace, and despite the comment at the top, style and class extend still works fine.
Are you sure this is expected behavior and not a bug? | 2023-09-25T08:51:35 | 2023-09-25T08:51:35 | {} | NONE |
vuejs | core | 1,736,534,301 | 5,912 | edison1105 | also fix #6018 @johnsoncodehk | 2023-09-27T01:34:47 | 2023-09-27T01:34:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,736,996,085 | 5,952 | stoner-w | @daniluk4000 I hope it can be processed as soon as possible, many issues have been bothering me for a long time. | 2023-09-27T09:01:11 | 2023-09-27T09:01:11 | {
"confused": 1
} | NONE |
vuejs | core | 1,737,147,495 | 6,897 | skirtles-code | I think this was fixed by #6182. Should this PR be closed? | 2023-09-27T10:40:50 | 2023-09-27T10:40:50 | {} | CONTRIBUTOR |
vuejs | core | 1,737,456,507 | 7,095 | Tahul | Hey @zhangzhonghe ; in your reproduction there is missing code/content.
If I implement the `nested-slots` component, and simple data in the example, I get it running with no hydration mismatches.
[Here](https://play.vuejs.org/#__SSR__eNqNVE2P0zAQ/SuWQQpITSK2nEp3tYD2AIcFsdw2K62bTFsviW3ZTlsU5b8zY/crLSpc2nrem5k3Y792... | 2023-09-27T13:57:34 | 2023-09-27T13:58:12 | {} | NONE |
vuejs | core | 1,731,811,439 | 9,263 | yangmingshan | esbuild refused, which was not surprising.
If Vue want transform `enum` to simple object, then @xiaoxiangmoe's PR is better. Feel free to close this one.
But since there is no simple way to do this, is it worth it?
Are there any unknown downsides? E.g. type and runtime mismatch 🤔️. | 2023-09-22T17:46:45 | 2023-09-22T17:46:45 | {} | CONTRIBUTOR |
vuejs | core | 1,732,754,891 | 9,233 | edison1105 | like @Alfred-Skyblue said above. this is not a memory leak.
as far as I know, vue-devtools will lead to [memory leaks](https://github.com/vuejs/devtools/issues/1875).
@matej-svejda Could you test in your application with vue-devtools disabled? | 2023-09-25T01:12:20 | 2023-09-25T01:12:20 | {} | MEMBER |
vuejs | core | 1,733,485,258 | 9,281 | avinean | @baiwusanyu-c Why `Vue will not generate its object based on this type during the compilation phase`?
Why it's not planned?
Do you plan to deprecate render-functions? | 2023-09-25T11:32:39 | 2023-09-25T11:32:39 | {} | NONE |
vuejs | core | 1,736,132,110 | 5,789 | skirtles-code | This fix looks like it's on the right track to me.
@hchlq There have been other tweaks made to that RegExp since you opened this PR, causing merge conflicts. Would you be able to merge in the latest `main` and resolve the conflicts? | 2023-09-26T19:07:27 | 2023-09-26T19:07:27 | {} | CONTRIBUTOR |
vuejs | core | 1,738,295,060 | 9,305 | edison1105 | please provide a runnable reproduction next time. | 2023-09-28T00:56:11 | 2023-09-28T00:56:11 | {} | MEMBER |
vuejs | core | 1,738,858,597 | 9,310 | posva | What you are looking for is `.capture`: https://play.vuejs.org/#eNqFVE1z0zAQ/SuLYSZliO3iAAMmdCilM8ChdCgDB8xBtTeOWlnSSHKa0Ml/ZyXXiUM/uNjW6u3z067eXkeHWieLFqM8mjpstGAODwoJMK34Anj1roiY1kUUYhTlTQ1MOAr/aBGEqlURgTUlBebOaZunKbFd2ESZOuUNq9GmHpVoWRMy7Xk+oRDqpzKigvel4OUlEXBZGrS2QekIigt6x5I1SFsBUkSbdBJ3cH0NpWqlQwPr9TT1ofvIs1327E56... | 2023-09-28T10:08:07 | 2023-09-28T10:08:07 | {} | MEMBER |
vuejs | core | 1,736,663,306 | 6,347 | FrankFang | https://twitter.com/edison11051/status/1706625485655208263
Is this thread discussing this issue? | 2023-09-27T04:40:36 | 2023-09-27T04:40:36 | {} | NONE |
vuejs | core | 1,738,869,768 | 8,594 | posva | The existing behavior is more flexible as it allows differentiating if you are running within a component + `runWithContext()`.
If anything, I would say `getCurrentInstance()` should be `null` within `runWithContext()` but I think it's fine to keep the behavior unspecified. The goal of `runWithContext()`
The ques... | 2023-09-28T10:16:09 | 2023-09-28T10:16:09 | {} | MEMBER |
vuejs | core | 1,732,198,688 | 9,206 | Alfred-Skyblue | Regarding the `v-show` directive, when it's bound to a component, it forces the child component to update along with the parent component's updates. However, `v-show` does not affect the rendering structure inside the component; it is solely used to control the display/hidden state of the component. Currently, this beh... | 2023-09-23T03:39:08 | 2023-09-23T03:39:08 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.