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,357,308,465 | 4,339 | hminghe | > > 应该大部分都是做多tab单页应用的来提这个feature.
> > @liweijian1 在页面组件外面包个壳，像下面这样子，能完全可控操作keep-alive缓存， 而且不需要额外的内部规范，比如，页面组件必须强制加上组件名，配合在meta里配置上页面组件名称，
> > ```
> > <template>
> > <router-view v-slot="{ Component, route }">
> > <keep-alive :include="include">
> > <component :is="wrap(route.fullPath, Component)" :... | 2022-12-19T08:59:30 | 2022-12-19T08:59:30 | {} | NONE |
vuejs | core | 1,348,298,684 | 7,334 | LinusBorg | please provide a runnable reproduction. you already created a playground, why would you not link it here? | 2022-12-13T11:31:36 | 2022-12-13T11:31:36 | {} | MEMBER |
vuejs | core | 1,351,322,908 | 7,343 | gngrchrl | I have also had this issue and the reason for the bug, while the bug itself is also painful as it makes debugging VERY hard, is that I mixed vue-stripe (which is vue2) and vue3. I didn't notice that until after a few hours after the bug came up and it was very hard to link it back to that issue as the page unmounting e... | 2022-12-14T13:06:51 | 2022-12-14T13:06:51 | {} | NONE |
vuejs | core | 1,352,755,888 | 7,346 | edison1105 | @SimmeNilsson this PR https://github.com/vuejs/core/pull/4951 will fix it. | 2022-12-15T09:07:56 | 2022-12-15T09:07:56 | {} | MEMBER |
vuejs | core | 1,352,778,356 | 4,951 | LinusBorg | @edison1105 this PR is pretty outdated. Meanwhile, the whole templateRef logic has been moved into a separate file.
If @ygj6 is willing to update the PR, that would be great. Otherwise, we should do a fresh one. | 2022-12-15T09:27:47 | 2022-12-15T09:27:47 | {} | MEMBER |
vuejs | core | 1,353,839,985 | 2,097 | infinite-system |
> > > 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'))
> > > ```
... | 2022-12-15T23:21:29 | 2022-12-15T23:21:29 | {} | NONE |
vuejs | core | 1,353,941,493 | 4,874 | infinite-system | Guys! I figured it out! the full solution to maintain full props reactivity and get the `defineExpose()` interface! Here is how:
```js
function createComponent ({ app, component, props, el }) {
let expose = null
const childApp = createApp({ render: () => expose = h(component, props) })
Object.ass... | 2022-12-16T00:25:23 | 2022-12-16T00:34:29 | {
"+1": 6,
"heart": 2
} | NONE |
vuejs | core | 1,354,766,439 | 7,344 | baiwusanyu-c | Do some refinement and unit testing tomorrow 🤣 | 2022-12-16T13:28:31 | 2022-12-16T13:28:31 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,355,418,186 | 6,031 | vanillajonathan | @wsafight Did you ever get around to doing that? | 2022-12-16T18:51:28 | 2022-12-16T18:51:28 | {} | NONE |
vuejs | core | 1,356,120,235 | 7,356 | zhangzhonghe | I don't think you should package the vue code into your library because it will overwrite some of the global variables that vue needs to use. | 2022-12-17T08:32:12 | 2022-12-17T08:32:12 | {} | MEMBER |
vuejs | core | 1,356,268,275 | 6,908 | sxzz | @LinusBorg Sure, I think so. It's a better solution. | 2022-12-17T13:41:45 | 2022-12-17T13:41:45 | {} | MEMBER |
vuejs | core | 1,348,840,690 | 7,338 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 0a98c6921b6997ed7f587ef8ffdff4e22ea177ad |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-13T15:42:07 | 2022-12-13T15:53:54 | {} | NONE |
vuejs | core | 1,351,307,533 | 7,343 | LinusBorg | This reproduction isn't runnable or minimal - it uses stripe api, which fails for a missing API key, and fails with errors when trying to follow step 1 of the reproduction instructions.
I'll leave this open for now as we already have a PR for this type of error, but I would very much be interested in actually gettin... | 2022-12-14T13:00:34 | 2022-12-14T13:02:20 | {} | MEMBER |
vuejs | core | 1,353,065,884 | 7,346 | LinusBorg | Ah, got it. in 3.2.45, we closed a few loopholes in the difference between development and production behaviour of compiled script-setup components.
One of these "loopholes" made the code in this example work in development with 3.2.44. And as you said, it never worked in production in either version.
That's beca... | 2022-12-15T13:26:24 | 2022-12-15T13:26:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,353,371,268 | 5,679 | LinusBorg | Not much, i guess. This patch covered mote of an edge case I'd say from what i recall. | 2022-12-15T16:37:49 | 2022-12-15T16:37:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,353,942,738 | 2,097 | infinite-system | Guys! I figured it out! the full solution to maintain full props reactivity and get the `defineExpose()` interface! Here is how:
```js
function createComponent ({ app, component, props, el }) {
let expose = null
const childApp = createApp({ render: () => expose = h(component, props) })
Object.ass... | 2022-12-16T00:26:27 | 2022-12-16T00:34:20 | {
"+1": 3,
"heart": 1,
"rocket": 1
} | NONE |
vuejs | core | 1,349,196,590 | 7,340 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8162b6aad08d99c5f04cfe8113391194688d2e23 |
|<span aria-hidden="true">🔍</span> Latest deploy l... | 2022-12-13T17:30:13 | 2022-12-13T17:43:24 | {} | NONE |
vuejs | core | 1,351,849,206 | 7,343 | talhameer | > The demo is still unusable because I'd need your secret stripe API key to make it run.
Check now, I've updated the API key for testing. | 2022-12-14T17:49:11 | 2022-12-14T17:49:11 | {} | NONE |
vuejs | core | 1,352,170,671 | 7,343 | LinusBorg | Not sure where to check. the last link still has no API key. | 2022-12-14T21:01:04 | 2022-12-14T21:01:04 | {} | MEMBER |
vuejs | core | 1,353,227,962 | 5,679 | funkyvisions | @LinusBorg
This fix is breaking me. I have 3 nested components (the top page is under a keep-alive) that emit a custom event (for a back button). I see Component3 emit to Component2 and I see Component2 try to emit to Component1, but it's stopped by this code.
```
if (instance.isUnmounted)
return;
```
``... | 2022-12-15T15:01:02 | 2022-12-15T15:44:22 | {} | NONE |
vuejs | core | 1,353,325,099 | 5,679 | LinusBorg | I fail to imagine a scenario where the inner component would need to emit a close event, while its parent (the middle component) is already (being) unmounted - qnd yet somehow your page gets stuck.
so I'll wait for your reproduction
When you have that ready, please open a new issue, thanks. | 2022-12-15T16:05:45 | 2022-12-15T16:06:17 | {} | MEMBER |
vuejs | core | 1,354,363,956 | 7,344 | baiwusanyu-c | I store the 'data-owner-value' in the 'parentComponent' when the element is unmounted, and reset it when it is updated. And maintain a variable 'teleportUTMap' globally, store 'ut', re-execute 'ut' when updating, | 2022-12-16T08:13:21 | 2022-12-16T08:13:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,354,369,583 | 7,344 | baiwusanyu-c | > @baiwusanyu-c great work! but not working with [this scenario](https://deploy-preview-7344--vue-sfc-playground.netlify.app/#__DEV__eNqlkU1u2zAQha8y5cYJYEqLBijgOka76AmaTQFuZGlks6FIYjiSIxi+e4aS4hjJMloIePPzvtHTWf2OsRh6VBu1Zeyiqxh3xgNs9z1z8PCrdrZ+fjQqHcPp6Wj9AR7h21UYtXsKh4ND4Cy35by2WFC5m15ZGW9YEA5jIAYOYrkPzSgGuSvTTJVPlu2... | 2022-12-16T08:18:23 | 2022-12-16T08:18:23 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,356,821,831 | 7,366 | LinusBorg | That's because it's nested in `<Suspense>`, so placeholder/loading fallback content is now `<Suspense>`'s job
| 2022-12-18T15:26:26 | 2022-12-18T15:27:02 | {} | MEMBER |
vuejs | core | 1,357,763,760 | 7,372 | LinusBorg | Because this line does *nothing*:
https://github.com/DivakarSS/WebComponents/blob/main/src/vselect-test1.vue#L21
You register bootstrap-vue on a throwaway app instance. That won't make it work in the component that you do that in.
You can't register plugins with Vue web components, at least not yet, without ha... | 2022-12-19T14:35:42 | 2022-12-19T14:35:42 | {} | MEMBER |
vuejs | core | 1,347,816,675 | 7,329 | sxzz | We also have to wait `@rollup/plugin-commonjs`, `rollup-plugin-node-polyfills`, `@rollup/plugin-inject`, `@rollup/plugin-replace` to upgrade their `magic-string` deps.
relate PR https://github.com/rollup/plugins/pull/1373 | 2022-12-13T06:38:40 | 2022-12-13T16:33:09 | {} | MEMBER |
vuejs | core | 1,350,585,093 | 7,312 | baiwusanyu-c | > This is because Teleport is not patched in the fast path. Maybe we should re-consider the solution in #4609
I made some modifications based on your pr(#4609 ), and I may need your help in some places. In addition, for the implementation of `CSSVars` in `teleport`, I think it really needs further consideration | 2022-12-14T08:00:23 | 2022-12-14T08:00:23 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,353,339,907 | 5,679 | funkyvisions | @LinusBorg I'll try to yank all this out of my app and create a reproducible snippet. In the meantime, what it the harm of me patching my vue install to remove those added lines? | 2022-12-15T16:14:31 | 2022-12-15T16:14:31 | {} | NONE |
vuejs | core | 1,353,734,096 | 7,355 | LinusBorg | As this only happens when a keep-alive has more children than `max` allows do cache ... I think there's a different underlying problem, surfaced by the fix in #5679
Keep-Alive children when 5 children have been created:
<img width="488" alt="Bildschirmfoto 2022-12-15 um 22 27 55" src="https://user-images.githubu... | 2022-12-15T21:33:03 | 2022-12-15T22:29:48 | {} | MEMBER |
vuejs | core | 1,354,345,718 | 6,371 | SxDx | Hey, is there anything I still need to do to get this merged? | 2022-12-16T07:53:08 | 2022-12-16T07:53:08 | {} | CONTRIBUTOR |
vuejs | core | 1,357,258,624 | 7,369 | LinusBorg | Yeah that won't work because the CSS variables generated by using v-bind() in the component don't live in the `:root` context, so they are not accessible there. They are applied to the component's root elements, as you can see by inspecting the DOM.
This is intended behaviour so that variables do not bleed outside o... | 2022-12-19T08:18:13 | 2022-12-19T08:18:13 | {} | MEMBER |
vuejs | core | 1,357,597,999 | 7,356 | abrbabey | > This will ensure that the tree shakes off HMR-related code during build time. It might solve your problem.
I started thinking in this direction after your first comment, and a fresh skim of the code led me to one portion of global HMR registration in Vue's `runtime-core/src/hmr.ts` which looks like this:
```typ... | 2022-12-19T12:28:29 | 2022-12-19T12:28:29 | {} | NONE |
vuejs | core | 1,357,896,377 | 7,370 | sj7112 | src/util/object.ts
Object.prototype.getTuple = function (k: string) {
debugger;
const index = k.indexOf('.');
return null;
};
global.d.ts
export {};
declare global {
interface Object {
getTuple: (k: string) => any;
}}
import src/util/object in your vue file... | 2022-12-19T16:08:17 | 2022-12-19T16:08:17 | {} | NONE |
vuejs | core | 1,350,678,720 | 4,294 | extrem7 | My strange workaround if you need a working props inheritance:
Some other file (even .vue):
```ts
export interface Props {
a: string
}
```
Your component:
```ts
import type { Props as BaseProps } from './other-file.{ts,vue}'
export interface Props extends BaseProps {
b: number
}
const props =... | 2022-12-14T09:05:28 | 2022-12-14T09:05:28 | {
"+1": 1,
"confused": 7
} | NONE |
vuejs | core | 1,352,408,747 | 7,305 | cathino | thankyou | 2022-12-15T00:42:27 | 2022-12-15T00:42:27 | {} | NONE |
vuejs | core | 1,352,414,284 | 6,548 | edison1105 | > Hi @edison1105 , Thanks for your work Do you know if this one will be merge soon?
This is an enhancement to an existing feature that may not be merged as quickly | 2022-12-15T00:51:11 | 2022-12-15T00:51:11 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,352,985,650 | 4,951 | ygj6 | OK. Please do a new one. | 2022-12-15T12:24:04 | 2022-12-15T12:24:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,354,072,947 | 7,281 | zhoufanglu | > Well I think there are two solutions to this problem. If you don't use [script-setup](https://vuejs.org/api/sfc-script-setup.html#script-setup) I think you simply have to export Api interface from Child component and use it as ref's type, otherwise it just doesn't work
>
> Parent.vue
>
> ```
> <script lang="ts... | 2022-12-16T02:01:02 | 2022-12-16T02:01:02 | {} | NONE |
vuejs | core | 1,009,989,592 | 5,228 | oswaldofreitas | can't we move it to p1 or p2? 😀
I'm trying to migrate a big project to Vue 3 and this issue is blocking me
Thank you for the PR | 2022-01-11T13:58:07 | 2022-01-11T13:58:07 | {
"+1": 1
} | NONE |
vuejs | core | 1,010,906,935 | 5,217 | qq10137383 | > >
>
> 我的还是不行啊...
你是和我一样的问题么，展开cachedView之后我的缓存正常了。 | 2022-01-12T10:46:51 | 2022-01-12T10:46:51 | {} | NONE |
vuejs | core | 1,011,441,091 | 5,248 | LinusBorg | Yeah but that's because you *add* it to the component instance returned from `new Vue()`, then attempt to *read* it from `instance.$options` - where you did not add it.
Your two examples simply don't do the same thing.
~~If your Vue 2 example actually did add `y` to the options object, like you do in the Vue 3 ex... | 2022-01-12T20:51:27 | 2022-01-12T21:40:57 | {} | MEMBER |
vuejs | core | 1,011,652,980 | 5,217 | AK47-dadada | > >  我是在这里展开的 但是没用...
>
> 暂时不知道你这个是什么情况，我试了一下即使去掉transaction组件和你一样，我这个也是正常的。按原理来说只要提示组件的更新到上一级就可以的，这是[我的代码](https://github.com/qq10137383/vue3-admin/blob/main/src/layout/components/AppMain.vue)
我确实不知道影响元... | 2022-01-13T01:45:41 | 2022-01-13T01:45:41 | {} | NONE |
vuejs | core | 1,011,878,711 | 5,250 | kalvenschraut | I see that issue, but my problem is more so with how the prop type is being inferred by the compiler.
According to your docs on the script setup page that I screenshotted
"If the type is referenced t... | 2022-01-13T07:45:56 | 2022-01-13T14:09:26 | {} | CONTRIBUTOR |
vuejs | core | 1,013,800,008 | 2,613 | lcoder | same error
```tsx
import { h, Teleport, defineAsyncComponent, FunctionalComponent, TeleportProps } from 'vue';
export const AsyncTeleport = defineAsyncComponent({
loader: () => new Promise((r) => {
const cp: FunctionalComponent<TeleportProps> = (props, ctx) => h(Teleport, props, ctx.slots);
cp.props =... | 2022-01-16T02:56:29 | 2022-01-16T02:56:29 | {} | NONE |
vuejs | core | 1,013,825,924 | 5,265 | yyx990803 | Please use the discord, stackoverflow or the forum for questions. | 2022-01-16T07:31:03 | 2022-01-16T07:31:03 | {} | MEMBER |
vuejs | core | 1,013,844,852 | 5,269 | posva | You need to use `Suspense` in the parent component. In other words, move the code you have in App.vue to a another vue file, import that component in App.vue and use it like
```vue
<Suspens><MyComp/></Suspense>
```
Please, next time consider using the [forum](http://forum.vuejs.org/), the [Discord server](https... | 2022-01-16T09:59:41 | 2022-01-16T09:59:41 | {} | MEMBER |
vuejs | core | 1,009,046,977 | 4,294 | nborko | Yes, I was probably too harsh, as the macros probably do work well for a good 95%+ of the people using the expected pattern. I was initially pretty frustrated when my meticulously developed type interfaces didn't work, and finally stumbled on this issue. I also didn't want to support two different coding paradigms in a... | 2022-01-10T16:22:41 | 2022-01-10T16:22:41 | {
"+1": 1
} | NONE |
vuejs | core | 1,011,629,693 | 5,217 | edison1105 | @AK47-dadada
传个简单的可以复现的 demo 吧。 | 2022-01-13T01:21:18 | 2022-01-13T01:21:18 | {} | MEMBER |
vuejs | core | 1,011,655,861 | 5,217 | qq10137383 | > > >  我是在这里展开的 但是没用...
> >
> >
> > 暂时不知道你这个是什么情况，我试了一下即使去掉transaction组件和你一样，我这个也是正常的。按原理来说只要提示组件的更新到上一级就可以的，这是[我的代码](https://github.com/qq10137383/vue3-admin/blob/main/src/layout/components/AppMain.vue)
... | 2022-01-13T01:48:50 | 2022-01-13T01:48:50 | {} | NONE |
vuejs | core | 1,012,160,278 | 4,542 | cobaltt7 | Does anyone know of any alternative solution for this? | 2022-01-13T13:57:35 | 2022-01-13T13:57:35 | {} | NONE |
vuejs | core | 1,013,525,977 | 5,228 | LinusBorg | I understand. We are moving a bit slower right now as the new docs are being polished for publishing, amongst other reasons. We will pick up speed soon. :) | 2022-01-14T22:50:30 | 2022-01-14T22:50:51 | {} | MEMBER |
vuejs | core | 1,013,592,358 | 5,263 | Justineo | Your `fn` is not returning a reactive object so Vue won't automatically unwrap the internal computed refs. You are seeing double quotes as it's the result of stringifying a ref object. | 2022-01-15T02:43:36 | 2022-01-15T02:43:36 | {} | MEMBER |
vuejs | core | 1,013,837,755 | 5,238 | yyx990803 | `animation-iteration-count` only works if the element stays in the DOM. Vue removes the element on `animationend` event, which fires after each iteration. Supporting this property is out of scope for Vue. | 2022-01-16T09:08:58 | 2022-01-16T09:08:58 | {} | MEMBER |
vuejs | core | 934,212,424 | 4,736 | posva | This behavior is expected (https://github.com/vuejs/rfcs/pull/154#issuecomment-614724480) so it should maybe be documented instead.
This is a duplicate of https://github.com/vuejs/vue-next/issues/3432, #4736, #4489.
Given https://github.com/vuejs/vue-next/issues/3432#issuecomment-812237075, this should go into a ... | 2021-10-05T09:03:12 | 2022-01-11T08:43:22 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,010,655,295 | 5,244 | EthanVn | > see #4993
Would vue development team consider that use file name as default component name in future when setup-SFC component's name is missing instead of using extra script tag to declare the definite name to keep the coding fluency of setup-SFC component? After all 'setup-SFC' component may be frequently cached ... | 2022-01-12T05:37:27 | 2022-01-12T05:44:03 | {
"+1": 1
} | NONE |
vuejs | core | 1,011,617,677 | 5,217 | qq10137383 | >
```
<router-view v-slot="{ Component }">
<transition name="fade-transform" mode="out-in">
<keep-alive :include="cachedViews">
<component :is="Component" />
</keep-alive>
</transition>
</router-view>
```
```
<script ... | 2022-01-13T01:09:51 | 2022-01-13T01:09:51 | {} | NONE |
vuejs | core | 1,011,816,302 | 5,217 | AK47-dadada | @yyx990803 尤大 这里有人骂人哦 | 2022-01-13T05:46:58 | 2022-01-13T05:46:58 | {} | NONE |
vuejs | core | 1,011,817,773 | 2,903 | dev-zhiou | As it turns out, upgrading the TS version didn't work
| 2022-01-13T05:50:20 | 2022-01-13T05:50:20 | {} | NONE |
vuejs | core | 1,011,998,095 | 5,253 | hcg1023 | > [example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmNvbnN0IHByb3BzID0gd2l0aERlZmF1bHRzKGRlZmluZVByb3BzPHtcbiAgZm4/OiAobmFtZTogc3RyaW5nKSA9PiB2b2lkXG59PigpLCB7XG4gIGZuOiAobmFtZTogc3RyaW5nKSA9PiB7XG4gICAgcmV0dXJuIG5hbWUudG9VcHBlckNhc2UoKVxuICB9XG59K... | 2022-01-13T10:24:51 | 2022-01-13T10:24:51 | {} | CONTRIBUTOR |
vuejs | core | 1,012,068,595 | 5,256 | meteor199 | 
| 2022-01-13T11:55:48 | 2022-01-13T11:55:48 | {} | NONE |
vuejs | core | 1,010,420,912 | 5,227 | lidlanca |
`JSON.parse(JSON.stringify(o))`
to quickly get a clone of simple data free from reactivity ( exclude Set, Map, Function, ,references/circular references, etc )
which for most use cases is fine.
| 2022-01-11T22:35:21 | 2022-01-11T22:35:21 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,011,767,751 | 5,217 | Codermar | How can you call yourself ak47? Are you trying to be cute or jus downright stupid?
> On Jan 12, 2022, at 7:40 PM, AK47-dadada ***@***.***> wrote:
>
>
> @qq10137383 搞了个线上demo居然没问题........................................................................................................................................... | 2022-01-13T03:51:27 | 2022-01-13T03:51:27 | {} | NONE |
vuejs | core | 1,011,769,112 | 5,001 | dev-zhiou | >
hello，you means install vetur can resolved this warning?
but i tried and unuseful | 2022-01-13T03:53:36 | 2022-01-13T03:53:36 | {} | NONE |
vuejs | core | 1,011,814,828 | 5,217 | AK47-dadada | > How can you call yourself ak47? Are you trying to be cute or jus downright stupid?
> […](#)
> On Jan 12, 2022, at 7:40 PM, AK47-dadada ***@***.***> wrote: @qq10137383 搞了个线上demo居然没问题........................................................................................................................................ | 2022-01-13T05:43:36 | 2022-01-13T05:43:36 | {} | NONE |
vuejs | core | 1,011,843,859 | 5,250 | LinusBorg | you have a typo:
```diff
- someObject: someObject | someObject[]
+ someObject: SomeObject | SomeObject[]
``` | 2022-01-13T06:46:46 | 2022-01-13T06:46:46 | {} | MEMBER |
vuejs | core | 1,011,989,317 | 5,253 | jacekkarczmarczyk | [example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmNvbnN0IHByb3BzID0gd2l0aERlZmF1bHRzKGRlZmluZVByb3BzPHtcbiAgZm4/OiAobmFtZTogc3RyaW5nKSA9PiB2b2lkXG59PigpLCB7XG4gIGZuOiAobmFtZTogc3RyaW5nKSA9PiB7XG4gICAgcmV0dXJuIG5hbWUudG9VcHBlckNhc2UoKVxuICB9XG59KVx... | 2022-01-13T10:14:07 | 2022-01-13T10:14:07 | {} | CONTRIBUTOR |
vuejs | core | 1,013,829,481 | 5,213 | yyx990803 | Force trigger the ref with `triggerRef()`: https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgdHJpZ2dlclJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgdGV4dCA9IHJlZignMycpXG5cbmZ1bmN0aW9uIG9uSW5wdXQoZXZlbnQpIHtcbiAgdGV4dC52YWx1ZSA9IGV2ZW50LmRhdGFcbiAgdHJpZ2dlclJlZih0ZXh0KVxufVxuPC9zY3JpcHQ+XG5cbjx0ZW1wbG... | 2022-01-16T08:03:33 | 2022-01-16T08:03:33 | {} | MEMBER |
vuejs | core | 1,010,587,414 | 5,244 | edison1105 | see https://github.com/vuejs/vue-next/issues/4993 | 2022-01-12T03:10:52 | 2022-01-12T03:10:52 | {} | MEMBER |
vuejs | core | 1,010,630,614 | 5,245 | ctforcp | `ref` 定义的变量在 `computed` 中要带在value ``
```
let user = ref('');
let name = computed(()=>{
return user.value;
})
```
我知道问题了。对不起，打扰了 | 2022-01-12T04:45:38 | 2022-01-12T04:45:38 | {} | NONE |
vuejs | core | 1,011,339,062 | 5,248 | HSchwichtenberg | Please have a look at https://codepen.io/hschwichtenberg/pen/jOGQvZK
This is the same code in Vue 2. But the y value is not printed.
| 2022-01-12T18:35:08 | 2022-01-12T18:35:08 | {} | NONE |
vuejs | core | 1,011,481,682 | 5,247 | LinusBorg | Workaround:
```html
<Suspense>
<template #default>
<component :is="$slots.default?.()[0]" />
</template>
<template #fallback>
<slot name="fallback"> Default Loading Message... </slot>
</template>
</Suspense>
``` | 2022-01-12T21:47:17 | 2022-01-12T21:47:58 | {} | MEMBER |
vuejs | core | 1,013,833,322 | 5,107 | yyx990803 | Vue's style merging is simple object property merging. There's no way for Vue to support merging logic of all possible CSS shorthands, and you should not expect it to work. As @lidlanca suggested, you'll have to either stick to explicit style properties, or write your own merging logic. | 2022-01-16T08:34:54 | 2022-01-16T08:34:54 | {} | MEMBER |
vuejs | core | 1,013,847,116 | 5,252 | posva | Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org). Maybe [there is already an existing bug report](https://github.com/vuejs/vue-next/issues?q=is%3Aiss... | 2022-01-16T10:13:32 | 2022-01-16T10:13:32 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,009,094,603 | 5,223 | murilolivorato | thanks @LinusBorg | 2022-01-10T16:42:56 | 2022-01-10T16:42:56 | {} | NONE |
vuejs | core | 1,011,429,224 | 5,243 | sqal | Is this really a fix or a breaking change? This change would break the [following example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IHsgcmVmIH0gZnJvbSAndnVlJ1xuIFx0aW1wb3J0IHsgdXNlTWFwcGVkSWRzIH0gZnJvbSAnLi9fLmpzJ1xuICBcbiAgbGV0IGlkID0gMFxuICBjb25zdCBpZHMgPSByZWYoW10pXG4gIGNvbnN0IGFkZCA9IC... | 2022-01-12T20:34:34 | 2022-01-12T20:34:34 | {} | CONTRIBUTOR |
vuejs | core | 1,011,628,417 | 5,217 | qq10137383 | >  我是在这里展开的 但是没用...
暂时不知道你这个是什么情况，我试了一下即使去掉transaction组件和你一样，我这个也是正常的。按原理来说只要提示组件的更新到上一级就可以的，这是[我的代码](https://github.com/qq10137383/vue3-admin/blob/main/src/layout/components/AppMain.vue)
| 2022-01-13T01:20:05 | 2022-01-13T01:20:05 | {} | NONE |
vuejs | core | 1,011,894,969 | 5,250 | LinusBorg | Ah, Thanks, that makes it clearer. Agree, this could be fixed. | 2022-01-13T08:10:14 | 2022-01-13T08:10:14 | {
"heart": 3
} | MEMBER |
vuejs | core | 1,013,620,087 | 5,262 | MuTsunTsai | @edison1105
I see; that was a little confusing. It also turns out that `isProd` is not related at all. The only setting that matters is `compilerOptions.comments` in this scenario. I wonder if this is documented anywhere?
| 2022-01-15T06:00:09 | 2022-01-15T06:00:09 | {} | NONE |
vuejs | core | 1,013,832,982 | 5,119 | yyx990803 | How React transforms JSX **is not a standard**. JSX itself has no runtime semantics, and it's up to frameworks to decide how to compile it. Vue does not aim to be compatible with how React decides to compile JSX. | 2022-01-16T08:32:12 | 2022-01-16T08:32:12 | {} | MEMBER |
vuejs | core | 1,013,846,673 | 5,204 | posva | [This is what you want to do](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2PlxuICAgIDxJbnB1dFNlbGVjdCB2LW1vZGVsPVwidmFsdWVcIj5cbiAgICAgIDxvcHRpb24gdmFsdWU9XCIxXCI+MTwvb3B0aW9uPlxuICAgICAgPG9wdGlvbiB2YWx1ZT1cIjJcIj4yPC9vcHRpb24+XG4gICAgPC9JbnB1dFNlbGVjdD5cblxuICAgIDxzZWxlY3Qgdi1tb2RlbD1cInZhbHVlXCI+XG4... | 2022-01-16T10:11:11 | 2022-01-16T10:11:11 | {} | MEMBER |
vuejs | core | 1,010,880,730 | 5,217 | AK47-dadada | >
我的还是不行啊... | 2022-01-12T10:16:22 | 2022-01-12T10:16:22 | {} | NONE |
vuejs | core | 1,011,782,065 | 4,590 | dev-zhiou | i update ts to 4.4.3, still has this warning,so bad!
| 2022-01-13T04:18:26 | 2022-01-13T04:18:26 | {
"eyes": 1
} | NONE |
vuejs | core | 1,012,922,945 | 5,259 | LinusBorg | That is indeed very weird, but - you should never have keys with the same name between data/setup/computed etc.
so this is a curious side effect that is not relevant when writing correct code.
Edit: the reason for the behaviour lies in the bindings analysis that the compiler does for optimization - you can see th... | 2022-01-14T08:48:20 | 2022-01-14T09:48:26 | {} | MEMBER |
vuejs | core | 1,013,830,927 | 5,194 | axelthat | Fixed https://github.com/vuejs/vue-next/commit/5ac703055fa83cb1e8a173bbd6a4d6c33707a3c3. You can close this PR. | 2022-01-16T08:13:51 | 2022-01-16T08:13:51 | {} | NONE |
vuejs | core | 1,011,022,187 | 5,244 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4993 | 2022-01-12T13:02:20 | 2022-01-12T13:02:20 | {} | MEMBER |
vuejs | core | 1,011,243,713 | 4,810 | CodingGorit | I hope setup will be added with "inheritAttrs: false" | 2022-01-12T16:44:38 | 2022-01-12T16:44:38 | {
"+1": 1
} | NONE |
vuejs | core | 1,011,653,447 | 5,217 | AK47-dadada | @edison1105 大佬你稍等，我想想办法给你个demo | 2022-01-13T01:46:12 | 2022-01-13T01:46:12 | {} | NONE |
vuejs | core | 1,013,828,745 | 5,200 | yyx990803 | closed via 78df8c78 | 2022-01-16T07:57:45 | 2022-01-16T07:57:45 | {} | MEMBER |
vuejs | core | 1,009,062,704 | 4,294 | LinusBorg | > `PropType<>` isn't exported, but `Prop<T, D>` is (which includes `PropType`),
`PropType` certainly *is* exported by `'vue'`, I use it daily. | 2022-01-10T16:29:09 | 2022-01-10T16:29:21 | {} | MEMBER |
vuejs | core | 1,011,873,691 | 5,248 | LinusBorg | > But I have the feeling that the difference between new Vue () and createApp () could also be an surprising issue for other developers and a documentation in v3.vuejs.org/guide/migration/introduction.html#breaking-changes would be helpful.
We would welcome a proposal in the docs repo.
Personally I would consider... | 2022-01-13T07:36:41 | 2022-01-13T07:36:41 | {} | MEMBER |
vuejs | core | 1,012,394,063 | 4,862 | lukeromanowicz | @posva please take a second look. This bug is open for some time and is still present | 2022-01-13T18:22:37 | 2022-01-13T18:22:37 | {} | NONE |
vuejs | core | 1,012,835,558 | 5,253 | LinusBorg | The mentioned fact that you need to use an arrow function or annotate `this` properly is documented here:
https://v3.vuejs.org/guide/typescript-support.html#annotating-props
But indeed, a method with `this: undefined` doesn't work work on `withDefaults()`. But it does with arrow functions. Not sure if this is a ... | 2022-01-14T07:12:39 | 2022-01-14T07:12:39 | {} | MEMBER |
vuejs | core | 1,013,608,478 | 5,262 | edison1105 | you should add `compilerOptions` as below:
```javascript
const result = sfc.compileTemplate({
id: "test",
source: "<div><!--test--></div>",
isProd: true,
// add this
compilerOptions:{
comments:false
}
});
``` | 2022-01-15T04:27:23 | 2022-01-15T04:27:23 | {} | MEMBER |
vuejs | core | 1,013,829,613 | 5,240 | yyx990803 | It's already fixed but thanks for the PR. | 2022-01-16T08:04:33 | 2022-01-16T08:04:33 | {} | MEMBER |
vuejs | core | 1,011,610,804 | 5,217 | AK47-dadada | 不行啊
`
<template>
<el-main>
<router-view v-slot="{ Component }">
<keep-alive :include="cacheViews">
<component :is="Component" />
</keep-alive>
</router-view>
</el-main>
</template>
`
----
`
<script>
import { defineComponent } from 'vue'
import { mapState } from 'vuex'
... | 2022-01-13T01:03:10 | 2022-01-13T01:05:00 | {} | NONE |
vuejs | core | 1,013,825,813 | 5,267 | yyx990803 | - The playground uses [sucrase](https://github.com/alangpierce/sucrase) for transpiling TS in browser, which does not support decorators.
- Vue class component is no longer recommended, so the playground has no plan in supporting it. | 2022-01-16T07:30:05 | 2022-01-16T07:30:05 | {} | MEMBER |
vuejs | core | 1,009,065,186 | 4,294 | nborko | > > `PropType<>` isn't exported, but `Prop<T, D>` is (which includes `PropType`),
>
> `PropType` certainly _is_ exported by `'vue'`, I use it daily.
Huh, so it is. I stand corrected. | 2022-01-10T16:30:12 | 2022-01-10T16:30:12 | {} | NONE |
vuejs | core | 1,011,769,821 | 5,217 | AK47-dadada | @edison1105 这里有人骂人嗷 | 2022-01-13T03:54:41 | 2022-01-13T03:54:41 | {} | NONE |
vuejs | core | 1,011,881,396 | 5,248 | HSchwichtenberg | >>Also, this seems to a notable difference between Options API and Composition API, because in following sample I don't get the updated y printed, because it is not a RefImp.
>Your example works fine for me
Oh... I see, that the `y` values are updated in the Vue SFC Playground. But `y` is **not updated in my loca... | 2022-01-13T07:50:39 | 2022-01-13T07:55:09 | {} | NONE |
vuejs | core | 1,013,516,865 | 5,228 | oswaldofreitas | yes, I have some .native listeners, not sure how many, but I'll definitely search all places and go with your suggestion, thanks again, and sorry for the coffee joke, it wasn't my intention to "buy" a position in the queue, but to say how important this fix is for me :) | 2022-01-14T22:30:03 | 2022-01-14T22:30:03 | {
"+1": 1
} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.