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 | 701,543,032 | 2,283 | LinusBorg | yes, inside the fullscreen view that you can pop open. | 2020-09-30T17:46:34 | 2020-10-01T08:07:29 | {} | MEMBER |
vuejs | core | 702,733,500 | 2,278 | shadowings-zy | @posva @LinusBorg
Hello, I have added warnings for in-DOM template, and doing camelCasing in the compiler in the newest PR.
All tests were passed.
Let us review it. | 2020-10-02T13:26:57 | 2020-10-02T13:26:57 | {} | CONTRIBUTOR |
vuejs | core | 700,599,746 | 2,252 | posva | As a workaround, you can use `:value="2"` | 2020-09-29T09:58:56 | 2020-09-29T09:58:56 | {} | MEMBER |
vuejs | core | 700,969,446 | 2,251 | fotijr | I found the library causing the bug and opened an issue with [clean-css](https://github.com/jakubpawlowicz/clean-css/issues/1126). I didn't realize Vue doesn't do any CSS parsing, thanks for the info. I should have started with Vite, since that's what wired up clean-css. | 2020-09-29T20:31:04 | 2020-09-29T20:31:04 | {} | NONE |
vuejs | core | 701,480,439 | 2,282 | LinusBorg | We should keep it compatible though, seems like an easy fix. | 2020-09-30T15:53:01 | 2020-09-30T15:53:01 | {} | MEMBER |
vuejs | core | 699,892,517 | 2,249 | posva | I think the only one expected to work on a render function should be `onTestedEvent`.
We should probably also warn [like in Vue 2](https://jsfiddle.net/posva/wsr78d2w/) for in-DOM templates | 2020-09-28T09:27:55 | 2020-09-30T16:18:46 | {
"+1": 2
} | MEMBER |
vuejs | core | 702,478,507 | 2,215 | yeikiu | In case it helps, sticking to `vue@3.0.0-rc.5` version under yarn.lock fixed all my issues with Suspense and router-views. You need to install dependencies with `yarn --frozen-lock-file`.
```
vue@^3.0.0-0:
version "3.0.0-rc.5"
resolved "https://registry.yarnpkg.com/vue/-/vue-3.0.0-rc.5.tgz#973175d45a892b3bd2... | 2020-10-02T01:24:17 | 2020-10-02T01:25:22 | {} | NONE |
vuejs | core | 703,093,136 | 2,293 | KaelWD | > as long as the parent component updated, the child component will render again
That sounds like v2 behaviour if you used `$attrs` in the child. | 2020-10-03T12:06:06 | 2020-10-03T12:06:06 | {} | CONTRIBUTOR |
vuejs | core | 701,053,050 | 2,204 | dependabot-preview[bot] | Superseded by #2275. | 2020-09-29T23:51:00 | 2020-09-29T23:51:00 | {} | CONTRIBUTOR |
vuejs | core | 701,349,305 | 2,280 | LinusBorg | I'm not too sure that this is a good idea, because this only works if the object with the `is` property is defined directly in the template.
If the object is actually defined in the component (which, in my experience, is the rule rather than the exception), and passed into the template with a variable, then this st... | 2020-09-30T12:09:56 | 2020-09-30T12:12:02 | {
"+1": 1
} | MEMBER |
vuejs | core | 701,478,542 | 2,282 | posva | I'm surprised it works on Vue 2. You should use an arrow function to keep the context or even use the promise syntax. I thought the callback syntax wouldn't be supported anymore | 2020-09-30T15:49:49 | 2020-09-30T15:49:49 | {} | MEMBER |
vuejs | core | 702,992,946 | 2,283 | MayaRainer | I just encountered this too. It seems to happen for every `ref` on elements inside of a child component's `slot`. | 2020-10-02T23:03:10 | 2020-10-02T23:03:10 | {
"+1": 1
} | NONE |
vuejs | core | 703,101,263 | 2,170 | kleinfreund | I now understand @LinusBorg’s investigation and think I can provide a fix for this. If that’s alright, I’d like to submit a pull request for this. | 2020-10-03T13:09:50 | 2020-10-03T13:09:50 | {} | CONTRIBUTOR |
vuejs | core | 700,530,239 | 2,258 | watonyweng | I executed `yarn dev` and got information in the console `Uncaught SyntaxError: The requested module '/@modules/@babel/parser/lib/index.js' does not provide an export named 'parse'` | 2020-09-29T08:15:13 | 2020-09-29T08:15:13 | {} | NONE |
vuejs | core | 700,549,376 | 629 | seanlandsman | @LinusBorg I've literally just implemented that :-)
```
componentDefinition = defineComponent({ extends: defineComponent({ ...component }), data: () => ({params: params}), created: function() { componentInstance = this.$root }});
createApp(componentDefinition).mount(container);
```
This works well (with a fe... | 2020-09-29T08:46:21 | 2020-09-29T08:48:05 | {
"+1": 4
} | NONE |
vuejs | core | 700,580,162 | 2,261 | LinusBorg | Yeah, The second proposal about clearing the Set might still be worth looking into, it seems to me.
Not necessarily as a bugfix for this rather than an optimization.
> This is a tiny change, and will automatically cleanup stale computeds from the deps instead of holding on to them forever.
Tiny change but nee... | 2020-09-29T09:21:53 | 2020-09-29T09:22:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 700,590,478 | 2,261 | basvanmeurs | Added a PR. Tests are all passing as expected.
I verified with the original example that, after clicking the 'updateRef' button, the computeds and instances are indeed dereferenced. | 2020-09-29T09:40:39 | 2020-09-29T09:40:39 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 701,143,460 | 2,249 | shadowings-zy | > I think the only one expected to work on a render function should be `onTestedEvent`
I am agree with you, and I think `onTest-Event` worked is weird. So I fixed it in PR #2278 | 2020-09-30T04:02:33 | 2020-09-30T04:02:33 | {} | CONTRIBUTOR |
vuejs | core | 701,214,264 | 2,277 | edison1105 | > > modify your code:
> > `emits: ['myclick']`
> > and
> > `emit('myclick', e)`
> > worked.
>
> Because `Props` can support the camelCased & kebab-case.
>
> `props:{ showContent: String }`
> `emits: ['myClick']`
> `emit('myClick', e)`
> and
> `:show-content="xxx"`
> `@my-click="xx"`
>
> It would be gr... | 2020-09-30T07:29:21 | 2020-09-30T07:29:58 | {} | MEMBER |
vuejs | core | 701,955,784 | 777 | antoniandre | I just found out it has to be wrapped with `defineAsyncComponent` as per the migration guide: https://v3.vuejs.org/guide/migration/async-components.html#overview
This page also says so: https://v3.vuejs.org/guide/component-dynamic-async.html#async-components. 👍
I must have accessed an old doc, or missed it. 😅 | 2020-10-01T07:47:17 | 2020-10-01T07:47:17 | {
"+1": 17,
"eyes": 1,
"heart": 1,
"hooray": 2
} | NONE |
vuejs | core | 701,118,841 | 2,270 | rhengles | I guess we're meant to use `@vue/compiler-dom`. We need documentation on this. | 2020-09-30T02:22:18 | 2020-09-30T02:22:18 | {} | NONE |
vuejs | core | 701,222,013 | 2,277 | xuliangzhan | > > > modify your code:
> > > `emits: ['myclick']`
> > > and
> > > `emit('myclick', e)`
> > > worked.
> >
> >
> > Because `Props` can support the camelCased & kebab-case.
> > `props:{ showContent: String }`
> > `emits: ['myClick']`
> > `emit('myClick', e)`
> > and
> > `:show-content="xxx"`
> > `@my-click... | 2020-09-30T07:44:51 | 2020-09-30T07:44:51 | {} | NONE |
vuejs | core | 701,255,358 | 2,277 | shadowings-zy | It seems not a bug, but a feature. See `setFullProps` function in `packages/runtime-core/src/componentProps.ts` file.
```js
function setFullProps(
instance: ComponentInternalInstance,
rawProps: Data | null,
props: Data,
attrs: Data
) {
const [options, needCastKeys] = instance.propsOptions
if (raw... | 2020-09-30T08:49:50 | 2020-09-30T08:49:50 | {} | CONTRIBUTOR |
vuejs | core | 701,275,062 | 2,272 | LinusBorg | The property *might* exist if during runtime, defaultSlot[1] is actually a component vnode that *did* receive content for the default slot.
As that's not guaranteed, you will need to typecast it yourself. | 2020-09-30T09:27:04 | 2020-09-30T12:12:59 | {} | MEMBER |
vuejs | core | 701,445,871 | 2,281 | LinusBorg | Because you changed it?
You did both a reactive change (`this.count++`) and a nonreactive change (`this. nonReactiveCount++`) in one method call.
The reactive change caused a re-render of the component, and during that re-render, the new values for *both* properties are being used.
That works just like Vue 2. | 2020-09-30T14:57:49 | 2020-09-30T14:58:41 | {
"+1": 1,
"eyes": 1
} | MEMBER |
vuejs | core | 701,442,584 | 2,281 | RobbinBaauw | Actually, I think the `methods` way updates the `setupState` because `methods` are bound to the public instance proxy. Hence assignments are actually proxied and the original `setupState` object is updated. Note that this doesn't trigger the rerender, updating the `ref` takes care of that, this only explains why the up... | 2020-09-30T14:52:26 | 2020-09-30T15:03:11 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 701,987,085 | 2,278 | LinusBorg | I think this will break in-browser templates:
```html
<the-component v-on:test-event="handler">
```
results in this render function:
```javascript
return (_openBlock(), _createBlock(_component_Mycomponent, { "onTest-event": _ctx.handler }, null, 8 /* PROPS */, ["onTest-event"]))
```
[Example in template... | 2020-10-01T08:45:19 | 2020-10-01T08:45:19 | {
"+1": 2
} | MEMBER |
vuejs | core | 703,070,267 | 2,281 | RobbinBaauw | ^ I was just going to write that. Try
```js
let nonReactiveCount = {
x: 0
};
const incrementNonReactive = () => {
nonReactiveCount.x++;
};
```
and upon rerender because of the ref change it will actually update in the view (this is what I was trying to explain before but it wasn't v... | 2020-10-03T08:45:41 | 2020-10-03T08:45:41 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 703,146,644 | 2,293 | skirtles-code | If I'm reading it right, `shouldUpdateComponent` will return `true` if there are any directives present on the VNode:
https://github.com/vuejs/vue-next/blob/1abcb2cf61ec16807cae11cfe56acefab19487a1/packages/runtime-core/src/componentRenderUtils.ts#L306
So any 'custom' directive would cause the same problem. | 2020-10-03T18:37:07 | 2020-10-03T18:37:07 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 701,482,480 | 2,282 | shaan1974 | Thanks guys with arrow function it's working ;) | 2020-09-30T15:56:17 | 2020-09-30T15:56:17 | {} | NONE |
vuejs | core | 703,065,565 | 2,293 | posva | This is expected, it did update. It wouldn't trigger with **nested** components though | 2020-10-03T08:06:21 | 2020-10-03T08:06:21 | {} | MEMBER |
vuejs | core | 703,075,993 | 2,293 | posva | It's true the behavior is [different from Vue 2](https://jsfiddle.net/z8w0u5b2/) and I'm not even sure it makes sense for it to call the `updated` hook | 2020-10-03T09:32:26 | 2020-10-03T09:32:26 | {} | MEMBER |
vuejs | core | 703,085,801 | 2,294 | 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). | 2020-10-03T11:02:29 | 2020-10-03T11:02:29 | {} | MEMBER |
vuejs | core | 700,524,067 | 2,261 | edison1105 | see https://github.com/vuejs/rfcs/pull/212#issuecomment-695842658 | 2020-09-29T08:03:19 | 2020-09-29T08:06:46 | {} | MEMBER |
vuejs | core | 700,702,421 | 2,264 | haoqunjiang | @jacekkarczmarczyk In the translated docs, the phrase is presented in Chinese as "组合式 API", which, IMO, can be considered as the official translation for the term. | 2020-09-29T13:27:30 | 2020-09-29T13:27:30 | {} | MEMBER |
vuejs | core | 701,782,000 | 2,037 | rocky-191 | 统一以往的slot-scope和具名插槽，如果需要用到slot-scope的话，后面跟上slotProps,即写成 #test="slotProps就可以了。更方便了，牛逼 | 2020-10-01T02:44:28 | 2020-10-01T02:44:28 | {} | NONE |
vuejs | core | 701,966,746 | 2,278 | posva | Can you add dev warning like in vue 2 (https://github.com/vuejs/vue-next/issues/2249#issuecomment-699892517) | 2020-10-01T08:07:16 | 2020-10-01T08:07:16 | {} | MEMBER |
vuejs | core | 701,543,212 | 2,283 | 07akioni | > yes, inside the fullscreen view that you can pop open.
Great, thanks. | 2020-09-30T17:46:57 | 2020-10-01T08:07:34 | {} | CONTRIBUTOR |
vuejs | core | 701,536,873 | 2,283 | LinusBorg | doesn't happen when using actual `ref()`s for the template refs:
https://codesandbox.io/s/vue-ref-bug-issue-2283-jrdvs
I assume it's caused in part by the slot optimizations - when App.vue re-renders, $refs is cleared:
https://github.com/vuejs/vue-next/blob/5d825f318f1c3467dd530e43b09040d9f8793cce/packages/run... | 2020-09-30T17:34:42 | 2020-10-01T08:37:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 748,643,067 | 2,853 | posva | The existing type is correct | 2020-12-20T18:25:40 | 2020-12-20T18:25:40 | {} | MEMBER |
vuejs | core | 749,371,692 | 2,861 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-22T06:34:20 | 2020-12-22T06:34:20 | {} | NONE |
vuejs | core | 749,997,222 | 2,866 | shlroland | > > > Could you try my project: https://github.com/Alanscut/vue-next-emit
> > > and even I introduced it with cnd package, it still work well: https://github.com/Alanscut/vue-next-emit/blob/master/html/index.html
> > > in the console, your will see '### handler has been triggered.'
> >
> >
> > i am wirting a UI ... | 2020-12-23T08:04:17 | 2020-12-23T08:04:17 | {} | NONE |
vuejs | core | 751,223,258 | 2,882 | lgz5689 | @underfin why this array default cannot set [] , only set [0],[{}] and more ?
because this array render `el-option` ? | 2020-12-25T09:52:18 | 2020-12-25T09:52:18 | {} | NONE |
vuejs | core | 751,654,126 | 2,895 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-28T09:48:53 | 2020-12-28T09:48:53 | {} | NONE |
vuejs | core | 751,779,242 | 2,896 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2892 | 2020-12-28T16:38:55 | 2020-12-28T16:38:55 | {} | MEMBER |
vuejs | core | 748,568,266 | 2,852 | gkweb | 
| 2020-12-20T06:03:38 | 2020-12-20T06:03:38 | {} | NONE |
vuejs | core | 748,643,416 | 2,853 | yustnip | Ok, thanks for the confirmation | 2020-12-20T18:28:35 | 2020-12-20T18:28:35 | {} | NONE |
vuejs | core | 750,796,564 | 2,874 | peter50216 | `((e: 'foo' | 'bar') => void) & ((e: 'baz', id: number) => void)` also works for TypeScript, but vue compiler reject this too. | 2020-12-24T08:01:32 | 2020-12-24T08:01:32 | {} | NONE |
vuejs | core | 750,911,646 | 2,736 | posva | I'm actually not sure. The best is to make it consistent with Vue 2 | 2020-12-24T15:31:25 | 2020-12-24T15:31:25 | {} | MEMBER |
vuejs | core | 751,461,210 | 2,889 | edison1105 | I'm think the best is to make it consistent with Vue 2.
https://github.com/vuejs/vue/blob/dev/src/core/util/options.js#L172
BTW, your code not handled `globalMixins` | 2020-12-27T12:20:26 | 2020-12-27T12:24:03 | {} | MEMBER |
vuejs | core | 751,467,287 | 2,889 | tabjy | > ...make it consistent with Vue 2
Thank you for pointing the direction. I'll take a deeper look!
> BTW, your code not handled globalMixins
No, it doesn't, and it doesn't handle mixins with a mixin either. By no means that was a proper fix. :joy: | 2020-12-27T13:21:20 | 2020-12-27T13:21:20 | {} | NONE |
vuejs | core | 751,655,965 | 2,893 | Jokcy | Yeah, if only edge case like this will face this issue, maybe a doc is enough. Can we find a way to warning when people manually manipulating slots content in render functions? | 2020-12-28T09:55:13 | 2020-12-28T10:03:21 | {} | CONTRIBUTOR |
vuejs | core | 750,024,898 | 2,668 | posva | @Alanscut This is a typing issue, you need to add code inside `setup` to show the TS error | 2020-12-23T09:07:33 | 2020-12-23T09:07:44 | {} | MEMBER |
vuejs | core | 751,335,030 | 2,886 | edison1105 | When opening bug reports make sure to follow https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro | 2020-12-26T08:32:25 | 2020-12-26T08:32:25 | {} | MEMBER |
vuejs | core | 751,627,700 | 2,893 | LinusBorg | The cause is that the slots for each `<A>` are indeed stable and don't need updating, but Vue is re-using the same instance of `A` for efficiency when you toggle between the two vnodes.
Not sure we can fix this at the compiler level without de-optimizing the usually justified use-cases of keeping slots stable.
It... | 2020-12-28T08:18:49 | 2020-12-28T08:18:49 | {} | MEMBER |
vuejs | core | 751,964,419 | 2,807 | softboy99 | i have same problem | 2020-12-29T06:28:37 | 2020-12-29T06:28:37 | {} | NONE |
vuejs | core | 748,568,185 | 2,852 | gkweb | Same issue with rollup out of the box. Config info below:
```
"dependencies": {
"vue": "^3.0.0"
},
"devDependencies": {
"@types/jest": "^24.0.19",
"@typescript-eslint/eslint-plugin": "^2.33.0",
"@typescript-eslint/parser": "^2.33.0",
"@vue/compiler-sfc": "^3.0.4",
"@vue/eslint... | 2020-12-20T06:02:14 | 2020-12-20T06:02:14 | {} | NONE |
vuejs | core | 750,186,314 | 2,668 | Alanscut | > @Alanscut This is a typing issue, you need to add code inside `setup` to show the TS error
Thanks! | 2020-12-23T11:34:27 | 2020-12-23T11:34:49 | {} | CONTRIBUTOR |
vuejs | core | 750,905,223 | 2,736 | edison1105 | @posva
I am working on this, should we also handle error in `renderToString` function ? | 2020-12-24T15:01:34 | 2020-12-24T15:01:34 | {
"hooray": 1
} | MEMBER |
vuejs | core | 751,199,373 | 2,882 | lgz5689 | >
>
> > You overwirte the value at here https://gitee.com/liguangzheng777/school/blob/master/src/views/student/add.vue#L97
>
> in 97 overwirte console error:Uncaught (in promise) TypeError: oldChildren is null
> I attempt shield https://gitee.com/liguangzheng777/school/blob/master/src/views/student/add.vue#L26 ... | 2020-12-25T07:42:26 | 2020-12-25T07:42:26 | {} | NONE |
vuejs | core | 751,212,410 | 2,880 | posva | Read what I sent you on the other issue you opened with the same invalid reproduction | 2020-12-25T08:52:48 | 2020-12-25T08:52:48 | {} | MEMBER |
vuejs | core | 751,649,226 | 2,779 | LinusBorg | We should probably amend the Vue core docs for `app.config.isCustomElement` and explain that:
1. This check only runs for templates compiled at runtime.
2. a similar option can be configured for templates compiled during build:
- vue-loader & rollup-plugin-vue (through their `compilerOptions`)
- vue's jsx bab... | 2020-12-28T09:32:08 | 2020-12-28T09:32:08 | {} | MEMBER |
vuejs | core | 751,901,229 | 2,899 | daniel-jonathan | Okay, thank you! For anyone who stumbles upon this, I added to my script tag **type='module'** and all works now. | 2020-12-29T00:06:18 | 2020-12-29T00:06:57 | {} | NONE |
vuejs | core | 748,901,981 | 2,654 | LinusBorg | @posva can you take another look here? | 2020-12-21T10:35:09 | 2020-12-21T10:35:09 | {} | MEMBER |
vuejs | core | 748,945,653 | 1,925 | kabforks | Hello! IE11 build was supposed to have some attention in Q4. Do you guys have any news to share? :) | 2020-12-21T12:19:22 | 2020-12-21T12:19:22 | {
"+1": 13,
"eyes": 2
} | NONE |
vuejs | core | 749,504,447 | 2,863 | lovetingyuan | > As a workaround you can specify the component options object instead of its name:
>
> ```js
> setup() {
> return {
> view: MyTest,
> }
> },
> ```
thanks, it works | 2020-12-22T11:56:02 | 2020-12-22T11:56:02 | {} | NONE |
vuejs | core | 751,368,242 | 2,887 | HomyeeKing | use `ref` | 2020-12-26T15:47:46 | 2020-12-26T15:47:46 | {} | CONTRIBUTOR |
vuejs | core | 751,448,167 | 2,889 | edison1105 | The logic for processing `mixin serverPrefetch` should be written here:
https://github.com/vuejs/vue-next/blob/8ac2241b22/packages/runtime-core/src/componentOptions.ts#L438
| 2020-12-27T10:06:27 | 2020-12-27T10:06:27 | {} | MEMBER |
vuejs | core | 748,958,910 | 2,849 | LinusBorg | I thought about this a bit more, and I think this solution is good for this individual issue, but there are more readonly properties out there that could fail like this.
Example: #2766
I think the core reason is that the last line of `shouldSetAsProp` only checks for the existance of the key, but not wether it ha... | 2020-12-21T12:53:47 | 2020-12-21T12:54:55 | {} | MEMBER |
vuejs | core | 749,549,796 | 2,864 | posva | This should go as an RFC: https://github.com/vuejs/rfcs | 2020-12-22T13:51:27 | 2020-12-22T13:51:27 | {} | MEMBER |
vuejs | core | 749,914,234 | 2,866 | shlroland | > @shlroland Maybe this is a bug of codesandbox, if you create an project with vue-cli, then it will trigger the handler. I have met this issue ever before.
but in my loccal project(dont use vue cli), this bug is exist | 2020-12-23T03:52:13 | 2020-12-23T03:52:13 | {} | NONE |
vuejs | core | 749,950,869 | 2,866 | shlroland | > Could you try my project: https://github.com/Alanscut/vue-next-emit
> and even I introduced it with cnd package, it still work well: https://github.com/Alanscut/vue-next-emit/blob/master/html/index.html
>
> in the console, your will see '### handler has been triggered.'
i am wirting a UI library `rol-ui` for v... | 2020-12-23T05:53:01 | 2020-12-23T05:53:01 | {} | NONE |
vuejs | core | 751,271,960 | 2,870 | leaon4 | Thank you, you're right.
Because of your suggestion, I reconsidered four situations of Teleport's props, , and then found more.
`
h(teleport, props, h('div'))
`
1. props = {to: null, disabled: false} // illegal
2. props = {to: null, disabled: true} // need to check target
3. props = {to: target, disabled: false}... | 2020-12-25T17:03:17 | 2020-12-25T17:03:17 | {} | CONTRIBUTOR |
vuejs | core | 751,748,247 | 2,668 | vandelpavel | ~I had the same problem and the workaround worked for me but i'm still interested on why that happen.~
Just saw related issue #2676
| 2020-12-28T15:21:57 | 2020-12-28T15:25:45 | {} | NONE |
vuejs | core | 748,642,510 | 2,853 | yustnip | @posva I'm very sorry for the uncompleted reproduction (saving error, fixed now). But I need to ensure. The case looks like a good candidate for the enhancement.
According with DirectiveBinding arg can't be boolean (packages/runtime-core/src/directives.ts).
```
export interface DirectiveBinding<V = any> {
ins... | 2020-12-20T18:21:30 | 2020-12-20T18:21:30 | {} | NONE |
vuejs | core | 748,907,196 | 2,857 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2020-12-21T10:47:12 | 2020-12-21T10:49:40 | {} | NONE |
vuejs | core | 748,908,944 | 2,650 | posva | Agree, it's usually only one change per year (if any since there is _present_ in the year), not worth automating | 2020-12-21T10:51:30 | 2020-12-21T10:52:12 | {} | MEMBER |
vuejs | core | 749,482,436 | 2,862 | posva | Hello, this is too much for a reproduction: it should be boiled down as explained at https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro (e.g. simplified components, no store, no router). You can also use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask for help boiling it d... | 2020-12-22T10:58:56 | 2020-12-22T10:58:56 | {} | MEMBER |
vuejs | core | 749,518,888 | 2,094 | LinusBorg | Oh, I missed that. Will link issue and PR for better tracking now.
Thanks! | 2020-12-22T12:34:38 | 2020-12-22T12:34:38 | {} | MEMBER |
vuejs | core | 749,968,711 | 2,866 | Wizard67 | > > Could you try my project: https://github.com/Alanscut/vue-next-emit
> > and even I introduced it with cnd package, it still work well: https://github.com/Alanscut/vue-next-emit/blob/master/html/index.html
> > in the console, your will see '### handler has been triggered.'
>
> i am wirting a UI library `rol-ui`... | 2020-12-23T06:40:28 | 2020-12-23T06:40:28 | {} | NONE |
vuejs | core | 751,242,529 | 2,883 | posva | It needs to be a reactive source: https://v3.vuejs.org/api/refs-api.html#toref
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2020-12-25T12:25:47 | 2020-12-25T12:25:47 | {} | MEMBER |
vuejs | core | 751,264,707 | 2,871 | leaon4 | Thank you for your suggestion, it is much better. | 2020-12-25T15:42:45 | 2020-12-25T15:42:45 | {} | CONTRIBUTOR |
vuejs | core | 751,338,193 | 2,885 | LinusBorg | Please provide an actual reproduction. Your issue is with electron, so the reproduction needs to be a repository with a project that actually uses electron.
Please open a new issue when you have a proper reproduction that we can check out.
In the meantime, you can also try and find help at chat.vuejs.org | 2020-12-26T09:25:00 | 2020-12-26T09:25:00 | {} | MEMBER |
vuejs | core | 751,448,738 | 1,925 | slide222 | Do you know when we will have ie11 support ? | 2020-12-27T10:12:07 | 2020-12-27T10:12:07 | {} | NONE |
vuejs | core | 748,963,935 | 963 | LinusBorg | Think we can close this as concensus is that this hits a limitation in TS, and we have a good workaround with annotating the return value | 2020-12-21T13:06:21 | 2020-12-21T13:06:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 750,811,880 | 2,877 | posva | It's maybe what @edison1105 said but you shouldn't manually modify the slots in an instance.
Also you should read https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro | 2020-12-24T08:54:13 | 2020-12-24T08:54:13 | {} | MEMBER |
vuejs | core | 751,634,293 | 2,893 | Jokcy | > The cause is that the slots for each `<A>` are indeed stable and don't need updating, but Vue is re-using the same instance of `A` for efficiency when you toggle between the two vnodes.
>
> Not sure we can fix this at the compiler level without de-optimizing the usually justified use-cases of keeping slots stable.... | 2020-12-28T08:42:13 | 2020-12-28T08:42:13 | {} | CONTRIBUTOR |
vuejs | core | 751,946,553 | 2,843 | edison1105 | @lijingfaatcumt
Insert code like this in markdown.
It will enhance the readability of the code
| 2020-12-29T04:58:09 | 2020-12-29T04:58:09 | {} | MEMBER |
vuejs | core | 751,965,318 | 2,889 | tabjy | @edison1105 I don't know the workflow here. I was under the impression submitting it after someone from @vuejs confirms it to be a bug and assigns me to it, but you're right. I might as well submit it now. Worst case they can just close it if it's a wontfix.
Thank you! | 2020-12-29T06:32:26 | 2020-12-29T06:32:26 | {} | NONE |
vuejs | core | 748,570,960 | 2,852 | gkweb | @mazaiting - I've resolved this issue by setting the `NODE_ENV`.
`NODE_ENV=production npx rollup -c` - For example removes this error.
| 2020-12-20T06:46:39 | 2020-12-20T06:46:39 | {
"+1": 1
} | NONE |
vuejs | core | 749,517,048 | 2,094 | wonderful-panda | @LinusBorg PR is already opened.
https://github.com/vuejs/vue-next/pull/2179 | 2020-12-22T12:29:49 | 2020-12-22T12:29:49 | {} | CONTRIBUTOR |
vuejs | core | 751,198,075 | 2,882 | underfin | You overwirte the value at here https://gitee.com/liguangzheng777/school/blob/master/src/views/student/add.vue#L97 | 2020-12-25T07:35:02 | 2020-12-25T07:35:02 | {} | MEMBER |
vuejs | core | 751,647,385 | 2,893 | LinusBorg | Well I'm saying that at least I personally don't see how, as the problem you are facing here is not detectable by static analysis during compilation.
So the only way I can see would be to never optimize slots in this way, which is too high a price to solve such an edge case, in my opinion.
Maybe a better route ... | 2020-12-28T09:26:08 | 2020-12-28T09:27:40 | {} | MEMBER |
vuejs | core | 748,583,865 | 2,852 | posva | Read and follow https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro
The error might be a miss configuration on a template. In that case open the issue on the template repo | 2020-12-20T09:28:46 | 2020-12-20T09:28:46 | {
"hooray": 1
} | MEMBER |
vuejs | core | 748,999,450 | 2,855 | LinusBorg | `createBlock()` accepts the following types as its first argument:
```ts
export type VNodeTypes =
| string
| VNode
| Component
| typeof Text
| typeof Static
| typeof Comment
| typeof Fragment
| typeof TeleportImpl
| typeof SuspenseImpl
```
Those `*Impl` types ares used internally only... | 2020-12-21T14:24:27 | 2020-12-21T14:24:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 751,341,250 | 2,884 | LinusBorg | there's a console error message:
> Vue warn]: Invalid VNode type: Symbol(Fragment) (symbol)
> at <TextField>
That's a good indicator that the issue is fro having two distinct copies of vue included in the bundle (from the two `node_modules` folders.
Vue has to be properly externalized and it has to be mad... | 2020-12-26T10:12:02 | 2020-12-26T10:12:02 | {} | MEMBER |
vuejs | core | 751,380,617 | 2,887 | xtoolkit | >
>
> use `ref`
try with ref: [sandbox](https://codesandbox.io/s/lucid-blackwell-e4jc5?file=/src/components/ComposationApi.vue)
but again not work! why? | 2020-12-26T18:01:47 | 2020-12-26T18:01:47 | {} | NONE |
vuejs | core | 751,393,297 | 2,887 | LinusBorg | Please use chat.vuejs.org for questions and help, and read the docs on how to use refs. This is not a bug, and Github issues are reserved for bug reports. | 2020-12-26T20:31:34 | 2020-12-26T20:40:51 | {} | MEMBER |
vuejs | core | 751,432,205 | 2,870 | underfin | Good work :) | 2020-12-27T06:29:25 | 2020-12-27T06:29:25 | {} | MEMBER |
vuejs | core | 751,593,532 | 2,894 | 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... | 2020-12-28T06:17:35 | 2020-12-28T06:17:35 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.