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 | 881,703,151 | 3,921 | yyx990803 | FWIW this should still be considered a bug in `thread-loader` so I opened an issue there: https://github.com/webpack-contrib/thread-loader/issues/123 | 2021-07-16T20:34:34 | 2021-07-16T20:34:34 | {} | MEMBER |
vuejs | core | 881,860,832 | 4,140 | xGuangsPBD | > your reproduction link is broken.
https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IHYtZm9yPVwiKHJvdyx5KSBpbiBsaXN0XCI+XG4gICAgPGRpdj5cbiAgICAgIC0tLSByb3cge3t5fX1cbiAgICA8L2Rpdj5cbiAgICA8ZGl2IHYtZm9yPVwiKG51bSx4KSBpbiByb3dcIiBAY2xpY2s9XCJoYW5kbGVDbGljayh4LHkpXCI+XG4gICAgICB7e251bX19XG4gICAgPC9kaXY+XG... | 2021-07-17T08:53:54 | 2021-07-17T08:53:54 | {} | NONE |
vuejs | core | 883,389,201 | 4,152 | yyx990803 | They are different by design:
- The `E` argument of `FunctionalComponent` is the **shape of the runtime `emits` option**. i.e. the type should match what you would write as the value of the `emits` option:
```ts
emits: {
eventName: (payload: string) => { /* validation logic */ }
}
```
- The ar... | 2021-07-20T13:23:13 | 2021-07-20T13:23:13 | {} | MEMBER |
vuejs | core | 883,585,911 | 4,156 | yyx990803 | See 2bdee50a | 2021-07-20T17:59:00 | 2021-07-20T17:59:00 | {} | MEMBER |
vuejs | core | 883,694,103 | 4,152 | andylix | A thing that I just notice, `defineEmits`'s argument is a callable with a void return, and even if you change it to a number or string, the way that you would use emit is still treating it as a void return function. Why isn't tuple considered for typing emit's parameters instead of a callable type? The purpose of this ... | 2021-07-20T20:40:37 | 2021-07-20T21:41:43 | {} | NONE |
vuejs | core | 884,013,876 | 4,161 | posva | `attrs` is not reactive but it should be usable in the template. I think this is a bug but I'm not completely sure | 2021-07-21T08:53:08 | 2021-07-21T08:53:08 | {} | MEMBER |
vuejs | core | 884,085,398 | 4,164 | posva | Not sure if it makes sense to pass component slots that are supposed to render at different places and use a `v-if`/`v-else` which expects them to be together.
As a workaround, you can use a `v-if` instead of the `v-else` | 2021-07-21T10:36:56 | 2021-07-21T10:36:56 | {} | MEMBER |
vuejs | core | 880,979,611 | 3,392 | kospl | Yes, there is a reason. I'm running dev version of Vue because I want to
see any issues while, you know, developing. But, result I need is complied
template for, you know, production, so I got this issue when I can't have
it without comments, which I would say frustrating.
From other point, I found work around by rese... | 2021-07-15T20:07:36 | 2021-07-15T20:07:36 | {} | NONE |
vuejs | core | 881,000,956 | 2,817 | yyx990803 | Closing as IMO the overhead isn't worth it as the original issue isn't technically a bug has obvious workarounds. | 2021-07-15T20:44:27 | 2021-07-15T20:44:27 | {} | MEMBER |
vuejs | core | 882,664,697 | 4,144 | webfansplz | > If a timeout callback has already triggered, calling `clearTimeout` on that handle will simply be a noop. So clearing the handle when the callback is triggered doesn't actually affect the behavior in anyway... or am I missing something?
That‘s right. but maybe it can clears the memory usage of the timer😂 | 2021-07-19T15:58:46 | 2021-07-19T15:58:46 | {} | MEMBER |
vuejs | core | 882,865,001 | 3,918 | yyx990803 | Don't change what is intentional and working. The helpers are used to reduce bundle size because `addEventListener` calls are long and cannot be minified. | 2021-07-19T21:15:21 | 2021-07-19T21:15:53 | {} | MEMBER |
vuejs | core | 883,394,341 | 3,887 | yyx990803 | Thanks for the PR, `sfc-playground` should be ignored by default. See 3ff94fac | 2021-07-20T13:30:17 | 2021-07-20T13:30:17 | {} | MEMBER |
vuejs | core | 884,097,580 | 4,165 | posva | I'm seeing now deferredComputed relies on `effect.computed`, so this is not the right fix. @yyx990803 what about any of these:
- making `computed` an enum or string instead of boolean to differentiate computed from deferred computed
- Exposing a method called `isComputed` that can rely on the internal class with in... | 2021-07-21T10:57:25 | 2021-07-21T14:15:23 | {} | MEMBER |
vuejs | core | 881,063,310 | 2,016 | yyx990803 | Wondering if this is still relevant as there seems to be no one else raising similar needs. I'm removing this from 3.2 for now since I think we may have better consistency exposing `isSSR` and `isHydrating` via global callable methods, as part of 3.3 (which will focus on SSR). | 2021-07-15T23:02:09 | 2021-07-15T23:02:09 | {} | MEMBER |
vuejs | core | 881,492,309 | 4,131 | yyx990803 | You can just loop through the slot nodes and check if they are all comment nodes:
```js
import { Comment } from 'vue'
const isEffectiveSlot = vnodes => vnodes.some(vnode => vnode.type !== Comment)
``` | 2021-07-16T14:28:38 | 2021-07-16T14:28:38 | {} | MEMBER |
vuejs | core | 881,503,116 | 4,133 | yyx990803 | Attrs are non-reactive and can only be used in render functions. They are not a replacement of props. If you want to watch it reactively you need to use props. | 2021-07-16T14:44:33 | 2021-07-16T14:44:33 | {
"+1": 1
} | MEMBER |
vuejs | core | 881,572,077 | 3,894 | yyx990803 | Fixed via 6ed23f6 (will be out in 3.2) | 2021-07-16T16:29:56 | 2021-07-16T16:29:56 | {} | MEMBER |
vuejs | core | 881,937,319 | 1,679 | philibe | @guilhermemart
TLDR: It seems since Vue 3.1 old delimiter is deprecated and I was not able to have this option inlined in the source. My goal is to use Vue 3 with Flask. I've set up `options.compilerOptions` in `vue.config.js`.
I copy my answer also on S.O. : [How to change delimiters in Vue.js? ](https://stacko... | 2021-07-17T18:06:04 | 2021-07-17T18:49:05 | {
"+1": 2
} | NONE |
vuejs | core | 882,607,670 | 4,139 | yyx990803 | This fix is unsafe because it will skip `normlaizeStyle` for bindings like `:style="x"` or `:style="getStyle()"`.
The better fix is for `normalizeStyle` to return the string as-is.
See a8c3a8ad and 47ba33e2 | 2021-07-19T14:45:03 | 2021-07-19T14:45:03 | {} | MEMBER |
vuejs | core | 882,617,168 | 4,139 | edison1105 | > This fix is unsafe because it will skip `normlaizeStyle` for bindings like `:style="x"` or `:style="getStyle()"`.
>
> The better fix is for `normalizeStyle` to return the string as-is.
>
> See [a8c3a8a](https://github.com/vuejs/vue-next/commit/a8c3a8ad61b16a31f6754066838440a59ee9db8b) and [47ba33e](https://gith... | 2021-07-19T14:57:27 | 2021-07-19T14:57:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 882,768,330 | 4,010 | DV8FromTheWorld | As a note, I'd be happy to PR a solution to this issue, however, given the fact that the internals of the patch system are built intentionally with reverse-order patching for optimization I've not touched the code yet as it isn't clear how the project might want to address this.
Any thoughts or guidance here would b... | 2021-07-19T18:33:18 | 2021-07-19T18:33:18 | {} | CONTRIBUTOR |
vuejs | core | 883,182,711 | 3,814 | edison1105 | > Thanks for the PR, apparently this got fixed at [3056e9b](https://github.com/vuejs/vue-next/commit/3056e9b3dcb1ab0bd18227c6fa7bf283f98f6ef6)
@posva yes. I believe Evan closed the wrong PR 😓. see https://github.com/vuejs/vue-next/pull/3957#issuecomment-882882869.
Could you reopen my PR https://github.com/vuejs/vu... | 2021-07-20T07:57:25 | 2021-07-20T07:57:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 884,269,648 | 4,159 | pipe01 | Turns out it was something unrelated causing the problem, as always. Thank you for your great work. | 2021-07-21T15:13:16 | 2021-07-21T15:13:16 | {} | NONE |
vuejs | core | 884,405,034 | 4,164 | yyx990803 | This is wrong usage. You can't mix default slot and named slot container in the same `v-if/v-else` branch... this should throw a compiler error.
Use explicit `<template #default v-if="...">` as shown by @lidlanca's 2nd snippet. | 2021-07-21T18:34:51 | 2021-07-21T18:34:51 | {} | MEMBER |
vuejs | core | 881,315,283 | 4,127 | LinusBorg | Indeed. I wasn't even aware of that and would rate this an unintended side effect of the implementation ... :/ | 2021-07-16T09:37:53 | 2021-07-16T09:37:53 | {} | MEMBER |
vuejs | core | 881,837,468 | 4,136 | lidlanca | `return this.message` | 2021-07-17T06:02:58 | 2021-07-17T06:02:58 | {} | CONTRIBUTOR |
vuejs | core | 882,580,118 | 4,130 | yyx990803 | AFAIK `<portal>` isn't formally part of the spec yet. | 2021-07-19T14:09:57 | 2021-07-19T14:09:57 | {} | MEMBER |
vuejs | core | 883,726,167 | 4,157 | yyx990803 | It seems the computed change introduces too many edge cases and is too risky so I reverted it to the old behavior :/ | 2021-07-20T21:40:31 | 2021-07-20T21:40:31 | {} | MEMBER |
vuejs | core | 884,140,050 | 4,161 | edison1105 | without teleport also has same problem, see [playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8cD5cbiAgICBDaGlsZCBjb21wb25lbnQgdXBkYXRlcyBicmVhayB3aGVuIHVzaW5nIGEgVHJhbnNpdGlvbiBjb21wb25lbnQgaW5zaWRlIGEgVGVsZXBvcnQgY29tcG9uZW50IHdpdGggaW5oZXJpdEF0dHJzIHNldCB0byBmYWxzZS5cbiAgICA8YnI+XG4gICAgPGJyPlxu... | 2021-07-21T12:09:58 | 2021-07-21T12:09:58 | {} | MEMBER |
vuejs | core | 881,298,994 | 4,127 | LinusBorg | example: As soon as you have a composition lifecylce hook that depends on `this`, you will have a hard time extarcting that into a clean and reusable composition function, because that function now depends on some unknown property on the `this` of the component(s) it might be used in:
```js
function useMyFeature() ... | 2021-07-16T09:12:02 | 2021-07-16T09:13:46 | {} | MEMBER |
vuejs | core | 881,566,299 | 4,010 | DV8FromTheWorld | The problem originates from the fact that `patchKeyedChildren` iterates in reverse-order
https://github.com/vuejs/vue-next/blob/ba89ca9ecafe86292e3adf751671ed5e9ca6e928/packages/runtime-core/src/renderer.ts#L2049-L2051
This means that any `setRef` calls that occur in `patch` that rely on the `v-for : key` iteration... | 2021-07-16T16:20:21 | 2021-07-16T16:20:21 | {} | CONTRIBUTOR |
vuejs | core | 881,868,026 | 4,140 | edison1105 | I think it's not a bug. see https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IHYtZm9yPVwiKHJvdyx5KSBpbiBsaXN0XCIgOmtleT1cInlcIj5cbiAgICA8ZGl2PlxuICAgICAgLS0tIHJvdyB7e3l9fVxuICAgIDwvZGl2PlxuICAgIDxkaXYgdi1mb3I9XCIobnVtLHgpIGluIHJvd1wiIEBjbGljaz1cImhhbmRsZUNsaWNrKHgseSlcIj5cbiAgICAgIHt7bnVtfX1cbiAgICA8L2Rpd... | 2021-07-17T09:36:19 | 2021-07-17T09:52:22 | {} | MEMBER |
vuejs | core | 882,610,573 | 4,144 | webfansplz | > This doesn't seem to change anything.
Proactively clear the timer when callback is triggered .( handle=null ) | 2021-07-19T14:48:50 | 2021-07-19T14:48:50 | {} | MEMBER |
vuejs | core | 881,490,244 | 4,132 | posva | Your repro is far from minimal. Please open a new issue if you manage to reproduce it down with only Vue (no ui libs, no router, not ta, no tests, etc) and with a boiled down component. Usually this should kind of error should be reproducible with the SFC playground.
You can always use the chat to ask questions | 2021-07-16T14:25:46 | 2021-07-16T14:25:46 | {} | MEMBER |
vuejs | core | 881,594,094 | 4,010 | DV8FromTheWorld | You may be able to work around this problem via passing the intended index of the ref to your `handleItemRef` and using it to set the ref into the array instead of relying on `.push(ref)`.
The follow example highlights how this could be implemented
```vue
<template>
<ul>
<li
v-for="(item, idx) of i... | 2021-07-16T17:09:08 | 2021-07-16T17:13:54 | {
"+1": 5
} | CONTRIBUTOR |
vuejs | core | 883,941,826 | 4,163 | posva | There are already open pull requests for this | 2021-07-21T06:58:00 | 2021-07-21T06:58:00 | {} | MEMBER |
vuejs | core | 884,188,261 | 2,303 | modifMX | 我想你也是被 vue-router 欺骗的吧。
```
// 1. Define route components.
// These can be imported from other files
const Home = { template: '<div>Home</div>' }
const About = { template: '<div>About</div>' }
// 2. Define some routes
// Each route should map to a component.
// We'll talk about nested routes later.
const ro... | 2021-07-21T13:25:37 | 2021-07-21T13:25:37 | {} | NONE |
vuejs | core | 884,349,006 | 4,164 | lidlanca | The following seem like a sensible use case
```js
<template>
<comp>
<span v-if="condition">{{value}}</span>
<template #error v-else>
missing value
</template>
this will show in default slot regardless of condition
</comp>
</template>
```
which works using explicit default named template:
``... | 2021-07-21T17:07:17 | 2021-07-21T17:10:04 | {} | CONTRIBUTOR |
vuejs | core | 884,484,117 | 2,353 | yyx990803 | See ff0c8103 - while the changes proposed in this PR are technically correct, they introduce a bit too much overhead / complexity for a very finite special case. I decided to just special case `value` directly in `runtime-core`. | 2021-07-21T20:39:22 | 2021-07-21T20:39:22 | {
"hooray": 1
} | MEMBER |
vuejs | core | 830,728,309 | 3,716 | A-Babin | > Change the code as below, it will works fine
Apparently not in Chrome 89, Edge 90, or Safari 14. Using `enter-active, leave-active`, if the transition switches state while it's already mid-transition, it will jump to the start of the next transition, instead of continuing from where it was when the transition stat... | 2021-05-02T02:18:42 | 2021-05-02T03:20:51 | {} | NONE |
vuejs | core | 831,101,263 | 3,719 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js).
---
You are likely missing an `import { getPost }` f... | 2021-05-03T08:14:05 | 2021-05-03T08:15:22 | {} | MEMBER |
vuejs | core | 834,066,244 | 3,718 | Amour1688 | ```ts
import { CSSProperties } from 'vue'
type StyleValue = string | CSSProperties | Array<StyleValue>;
export interface AProps {
style?: StyleValue
}
```
I want type definition of style to have same type definition with `HTMLAttributes['style']` | 2021-05-07T04:56:15 | 2021-05-07T04:56:15 | {} | MEMBER |
vuejs | core | 834,613,109 | 3,741 | posva | > I'm not sure why the SFC Playground link is so massive, but here is the same code in a GitHub repo:
It's because it contais the whole code in the URL 😉 | 2021-05-07T16:45:25 | 2021-05-07T16:45:25 | {
"laugh": 1
} | MEMBER |
vuejs | core | 834,832,927 | 1,600 | yyx990803 | This PR has been cherry picked into working branch via dee3d6ab. Thanks! | 2021-05-07T22:44:18 | 2021-05-07T22:44:18 | {
"hooray": 8,
"rocket": 4
} | MEMBER |
vuejs | core | 835,566,953 | 3,288 | logaretm | This did break prop pass detection that I was relying on as reported in https://github.com/logaretm/vee-validate/pull/3294
As a workaround I had introduced a symbol as a default value to detect when the user didn't pass the prop:
```ts
export const EMPTY_VALUE = Symbol('Default empty value');
``
```js
{
... | 2021-05-08T23:16:14 | 2021-05-08T23:16:14 | {} | NONE |
vuejs | core | 837,836,783 | 3,756 | mofipp | > A workaround, use a `span` tag to wrap the `{{ number }}`:
>
> ```
> <div v-loading="loading"><span>{{ number }}</span></div>
> ```
Thanks for your reply and look forward to fixing it. | 2021-05-11T05:19:59 | 2021-05-11T05:19:59 | {} | NONE |
vuejs | core | 830,549,041 | 3,702 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.75 KB (0%) |
| runtime-dom.global.prod.js | 27.62 KB (0%) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-05-01T05:36:01 | 2021-05-01T05:36:01 | {} | NONE |
vuejs | core | 830,722,902 | 3,716 | edison1105 | Custom classes are not controlled by Transition, Not just class binding any other property will result in the same error. e.g: `style="color:#000"`
Change the code as below, it will works fine.
```javascript
<transition v-bind="$props">
<slot></slot>
</transition>
```
and
```diff
.fade-inout {
tra... | 2021-05-02T01:54:53 | 2021-05-02T02:00:08 | {} | MEMBER |
vuejs | core | 831,762,981 | 3,721 | HomyeeKing | the component should wrap with `<Suspense>`? I don't remember need to do that😕
maybe I developed w/ tsx before | 2021-05-04T08:15:21 | 2021-05-04T08:15:21 | {} | CONTRIBUTOR |
vuejs | core | 834,159,792 | 3,738 | Hozeee | Meanwhile i found, using :keY instead of :key is working, but it doesn't feel a good solution, just a hack (as i see the isReservedProps is by default not lowercase the attribute). | 2021-05-07T08:12:14 | 2021-05-07T08:12:14 | {} | NONE |
vuejs | core | 830,550,382 | 3,711 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.75 KB (0%) |
| runtime-dom.global.prod.js | 27.62 KB (0%) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-05-01T05:39:37 | 2021-05-01T05:39:37 | {} | NONE |
vuejs | core | 835,162,713 | 3,740 | HcySunYang | > I found another bug on current VariableDeclaration string removal implementation.
@Sociosarbis Now this PR can fix that. | 2021-05-08T07:11:13 | 2021-05-08T07:11:13 | {} | MEMBER |
vuejs | core | 835,734,860 | 2,020 | pikax | > I found out this thread in the process of migrating my project from Vue 2 to Vue 3. In Vue 2, I've used `Vue` type for passing around a component as a param but now that `CreateComponentPublicInstance` isn't exported as a type (returning type of `defineComponent()`), I can no longer do the same. As a workaround, I'm ... | 2021-05-09T07:59:54 | 2021-05-09T07:59:54 | {} | MEMBER |
vuejs | core | 836,640,717 | 3,752 | yanbowe | 这样写的话当我emit('show', '1', 18) 时可以触发事件
但是会有如下两个错误
vetur 会报错Expected 2 arguments, but got 3
控制台也会输出Component emitted event "show" but it is neither declared in the emits option nor as an "onShow" prop.
| 2021-05-10T12:32:20 | 2021-05-10T12:32:20 | {} | NONE |
vuejs | core | 830,540,260 | 1,157 | mdbetancourt | @yyx990803 i have this issue too, but looks like only happens when you are inside of a template (when you're using slots) | 2021-05-01T05:09:43 | 2021-05-01T05:11:00 | {
"+1": 1
} | NONE |
vuejs | core | 830,550,365 | 3,712 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.75 KB (0%) |
| runtime-dom.global.prod.js | 27.62 KB (0%) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-05-01T05:39:34 | 2021-05-01T05:39:34 | {} | NONE |
vuejs | core | 831,237,275 | 3,716 | posva | As @edison1105 said, you need to pass the `class` to the element, not the transition. Maybe the problem comes from somewhere else.
> it will jump to the start of the next transition, instead of continuing from where it was when the transition state was changed.
That is expected and the from classes are set when e... | 2021-05-03T12:48:50 | 2021-05-03T12:48:50 | {} | MEMBER |
vuejs | core | 833,231,112 | 1,927 | zq0904 | Is there an easy way to handle global components?
The custom component MyCustom uses a large number of global components, which cannot be resolved when I render using the h function.
Am I going to change the whole MyCustom to H function rendering?
```ts
// MyCustom.vue template
<div>
<el-xxxA /> // Globally r... | 2021-05-06T05:15:38 | 2021-05-06T06:10:16 | {} | NONE |
vuejs | core | 833,259,962 | 3,066 | HcySunYang | @Kingbultsea Could you please resolve the conflict? | 2021-05-06T06:21:47 | 2021-05-06T06:21:47 | {
"eyes": 1
} | MEMBER |
vuejs | core | 834,236,645 | 3,738 | Sociosarbis | What about `data-key` or `key-prop` ? | 2021-05-07T10:09:27 | 2021-05-07T10:09:27 | {} | NONE |
vuejs | core | 834,333,381 | 3,738 | LinusBorg | I'd think you can write a custom directive to set that key attribute as a workaround.
```vue
<template>
<div v-key="keyValue">
Check out this element's attributes
</div>
</template>
<script>
export default {
data: () => ({
keyValue: 'A'
}),
directives: {
key: {
mounted(el, ... | 2021-05-07T12:30:31 | 2021-05-07T14:39:00 | {
"+1": 7
} | MEMBER |
vuejs | core | 835,223,272 | 3,744 | soc221b | Thanks for your quick reply 👍 .
IMHO, if we have something like `in` operator or `getOwnProperty` method to distinguish that whether one prop is passed with `undefined` or just not be passed, then this will not introduce a breaking change I thought (but there may have another practical reasons I didn't know/underst... | 2021-05-08T08:56:47 | 2021-05-08T08:56:47 | {} | NONE |
vuejs | core | 836,214,185 | 3,668 | lidlanca | gist integration, allow creation or edits/patch of a gist from the playground.
<img src="https://user-images.githubusercontent.com/8693091/117611574-b9951080-b131-11eb-85f4-0430abc92df8.png" width=250/>
<img src="https://user-images.githubusercontent.com/8693091/117611709-fc56e880-b131-11eb-9324-2a761e99c374.... | 2021-05-10T05:53:42 | 2021-05-10T05:53:42 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 830,549,584 | 3,708 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.75 KB (0%) |
| runtime-dom.global.prod.js | 27.62 KB (0%) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-05-01T05:37:27 | 2021-05-01T05:37:27 | {} | NONE |
vuejs | core | 830,812,625 | 3,717 | edison1105 | as a workaround:
```javascript
const content = shallowRef()
```
or
```javascript
content.value = Vue.markRaw(options)
``` | 2021-05-02T13:49:52 | 2021-05-02T15:48:34 | {} | MEMBER |
vuejs | core | 836,547,527 | 3,478 | ercmage | It seems `shallowReactive` fixes my problem | 2021-05-10T10:52:36 | 2021-05-10T10:52:36 | {} | NONE |
vuejs | core | 837,165,889 | 3,596 | nfplee | It seems the order of the attributes is important. See the following:
https://jsfiddle.net/xm270v6y/
Therefore my new conclusion is that it should throw a warning if `:value` is used with `v-model` or `:value` is used after a `value` attribute (but not before).
There is a similar issue when using `v-text` and... | 2021-05-10T19:07:08 | 2021-05-11T08:05:05 | {} | NONE |
vuejs | core | 830,209,121 | 3,693 | pikax | Can you please don't override the `defineComponent` generics
You shouldn't be doing `defineComponent<ComponentPropsOption<.....>, ...>` because that's not supported and not intended to be used.
Also please, if you are defining the default please do not use `default()` since that infers the current `this`, but def... | 2021-04-30T16:23:22 | 2021-04-30T16:23:22 | {} | MEMBER |
vuejs | core | 830,256,636 | 3,701 | posva | You need to pass the data object if you manually call `$slots.default({ value: 'jsqy' })`. That's why you see an error: it's the template of `<tsub>` trying to read `data.value` | 2021-04-30T17:45:44 | 2021-04-30T17:45:44 | {} | MEMBER |
vuejs | core | 830,424,264 | 906 | mduey | I have the same issue as stuta. Same Pug template that swaps components. Works fine with no mode declared or with 'in-out' declared. If mode="out-in" is declared, it returns nothing. I am not using Vite. Using vue-cli 4.5.0. | 2021-04-30T22:02:56 | 2021-04-30T22:02:56 | {
"+1": 2,
"eyes": 1
} | NONE |
vuejs | core | 830,609,418 | 2,027 | jinxinkai | > > vue3 中，这个是devtools 6.0.0 beta 2打印的，我把devtools关闭，这个waring就消失了
>
> 请问怎么关闭 vue-devtools （vue3）
> 我也遇到了同样的警告信息，页面直接卡死无响应
set devtools in “when u click the extension” mode | 2021-05-01T10:33:39 | 2021-05-01T10:33:39 | {} | NONE |
vuejs | core | 837,688,711 | 3,747 | HcySunYang | This can be specified on the user side, e.g. https://github.com/vuejs/vue-next/blob/master/packages/runtime-test/src/index.ts#L16-L17 | 2021-05-11T02:52:05 | 2021-05-11T02:52:05 | {} | MEMBER |
vuejs | core | 830,550,860 | 3,705 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/13557?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your tes... | 2021-05-01T05:41:06 | 2021-05-01T05:41:06 | {} | CONTRIBUTOR |
vuejs | core | 830,551,399 | 3,706 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/13560?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your tes... | 2021-05-01T05:42:42 | 2021-05-01T05:42:42 | {} | CONTRIBUTOR |
vuejs | core | 830,656,096 | 3,701 | yunbookf | @posva
I'm so sorry, because I'm not sure yet, and I've looked through the documents several times in detail to confirm it to you again.
If it's not v-slot data, then there won't be any problems.
I've revised the example, click the second button: [https://codepen.io/jsqy/pen/dyNBNjR](https://codepen.io/jsqy/pen... | 2021-05-01T16:13:43 | 2021-05-03T11:39:53 | {} | NONE |
vuejs | core | 831,414,536 | 3,716 | A-Babin | > you need to pass the `class` to the element, not the transition.
@posva Yeah, that's exactly what I was trying to avoid having to do in the first place. If I want a reusable set of enter/leave transition components and don't want them to be ugly in Chrome, Edge, and Safari if they change state too quickly, I'd hav... | 2021-05-03T17:34:25 | 2021-05-03T17:34:25 | {} | NONE |
vuejs | core | 831,481,553 | 3,668 | lidlanca | loading from a github gist:
https://sfc-vue3.netlify.app/#/gist/c25471df90da7174730a2794f23a3bd9
| 2021-05-03T19:30:22 | 2021-05-03T19:30:22 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 833,930,082 | 3,737 | dependabot[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it. | 2021-05-06T22:59:13 | 2021-05-06T22:59:13 | {} | CONTRIBUTOR |
vuejs | core | 835,065,005 | 2,353 | HcySunYang | @unbyte There is a conflict again, can you please resolve the conflict again 🤣 | 2021-05-08T03:58:52 | 2021-05-08T03:58:52 | {} | MEMBER |
vuejs | core | 830,119,964 | 2,513 | tungquach | > The "solution" we are using in production is to manually modify a vue file and disable this ( runtime-dom.esm-bundler.js in our case ), however, I do not recommend doing so as other problems may appear.
>
> The changes we've made:
> https://gist.github.com/zauan/a3488a9feb799242df607c983de9c5b7
>
> We have thi... | 2021-04-30T14:06:21 | 2021-05-01T00:23:49 | {} | NONE |
vuejs | core | 830,549,387 | 3,706 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.75 KB (0%) |
| runtime-dom.global.prod.js | 27.62 KB (0%) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-05-01T05:36:52 | 2021-05-01T05:36:52 | {} | NONE |
vuejs | core | 830,550,705 | 3,713 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.75 KB (0%) |
| runtime-dom.global.prod.js | 27.62 KB (0%) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-05-01T05:40:36 | 2021-05-01T05:40:36 | {} | NONE |
vuejs | core | 830,674,321 | 3,668 | lidlanca | allow browser built in search to find code that is not in the editor viewport. ( remove limit of search only of visible part )
<img width=300 src="https://user-images.githubusercontent.com/8693091/116791504-cc9c4680-aa88-11eb-82df-064e31c91be9.png" />
| 2021-05-01T18:24:32 | 2021-05-01T18:24:32 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 833,927,060 | 3,711 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it. | 2021-05-06T22:52:42 | 2021-05-06T22:52:42 | {} | CONTRIBUTOR |
vuejs | core | 835,207,644 | 3,744 | posva | Passing undefined is the same as not passing a value to a prop and this is intended for practical reasons. Pass `null` instead if you want to signify an empty value for the prop. This would be a breaking change so it won't happen. | 2021-05-08T08:28:51 | 2021-05-08T08:28:51 | {} | MEMBER |
vuejs | core | 835,870,860 | 2,020 | binhonglee | > > I found out this thread in the process of migrating my project from Vue 2 to Vue 3. In Vue 2, I've used `Vue` type for passing around a component as a param but now that `CreateComponentPublicInstance` isn't exported as a type (returning type of `defineComponent()`), I can no longer do the same. As a workaround, I'... | 2021-05-09T19:35:09 | 2021-05-09T19:36:40 | {} | NONE |
vuejs | core | 836,092,280 | 3,749 | HcySunYang | This is expected, the [option 1](https://v3.vuejs.org/guide/migration/inline-template-attribute.html#option-1-use-script-tag) is used in scenarios where there is no build tool. So you should use the [option 2](https://v3.vuejs.org/guide/migration/inline-template-attribute.html#option-2-default-slot), refactor to the de... | 2021-05-10T02:48:03 | 2021-05-10T02:48:03 | {} | MEMBER |
vuejs | core | 836,493,797 | 3,752 | HcySunYang | ```js
const emit = defineEmit<((e: 'close', id: number) => void) | ((e: 'show', name: string, age: number) => void)>()
emit('close', 1)
emit('show', '1', 18)
``` | 2021-05-10T09:57:02 | 2021-05-10T09:57:02 | {} | MEMBER |
vuejs | core | 836,613,072 | 3,752 | HcySunYang | ~~const emit = defineEmit<(e: 'close', id: number) => void | ((e: 'show', name: string, age: number) => void)>()~~
| 2021-05-10T12:03:36 | 2021-05-10T14:58:20 | {} | MEMBER |
vuejs | core | 830,549,342 | 3,705 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.75 KB (0%) |
| runtime-dom.global.prod.js | 27.62 KB (0%) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-05-01T05:36:45 | 2021-05-01T05:36:45 | {} | NONE |
vuejs | core | 830,550,641 | 3,714 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.75 KB (0%) |
| runtime-dom.global.prod.js | 27.62 KB (0%) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-05-01T05:40:24 | 2021-05-01T05:40:24 | {} | NONE |
vuejs | core | 830,552,612 | 3,710 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/13563?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your tes... | 2021-05-01T05:46:13 | 2021-05-01T05:46:13 | {} | CONTRIBUTOR |
vuejs | core | 831,378,334 | 3,720 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-05-03T16:30:27 | 2021-05-03T16:30:27 | {} | CONTRIBUTOR |
vuejs | core | 833,927,637 | 3,729 | dependabot[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it. | 2021-05-06T22:53:53 | 2021-05-06T22:53:53 | {} | CONTRIBUTOR |
vuejs | core | 835,484,510 | 3,743 | LinusBorg | This happens because the call from within the constructor still has the original object as `this`, not the reactive proxy.
I don't really see a way around that. | 2021-05-08T19:35:20 | 2021-05-08T19:35:20 | {} | MEMBER |
vuejs | core | 836,086,282 | 3,748 | HcySunYang | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). | 2021-05-10T02:38:29 | 2021-05-10T02:38:29 | {} | MEMBER |
vuejs | core | 830,614,194 | 3,715 | Norserium | Actually, it's the same issue. My fault. Closed. | 2021-05-01T11:08:08 | 2021-05-01T11:08:08 | {} | NONE |
vuejs | core | 832,790,128 | 3,725 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 41.77 KB (+0.05% 🔺) |
| runtime-dom.global.prod.js | 27.63 KB (+0.06% 🔺) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-05-05T15:35:46 | 2021-05-05T15:35:46 | {} | NONE |
vuejs | core | 833,927,544 | 3,728 | dependabot[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it. | 2021-05-06T22:53:41 | 2021-05-06T22:53:41 | {} | CONTRIBUTOR |
vuejs | core | 835,802,036 | 3,743 | yyx990803 | This is a known limitation of Proxy-based reactivity, because Vue 3 no longer mutates the original object.
Another workaround is to always call async initialization code outside of the class:
```js
this.object = new ObjectWithAsync();
this.object.doSomethingAsync();
```
At the framework level this will be a... | 2021-05-09T12:54:40 | 2021-05-09T12:54:53 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.