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 | 770,212,621 | 3,127 | edison1105 | - | 2021-01-30T13:28:03 | 2021-01-30T13:29:12 | {} | MEMBER |
vuejs | core | 770,301,926 | 3,131 | eli-crow | For the moment, I'm working around the problem by "cloning-and-owning" the source code for TransitionGroup. Simply changing top to bottom; and left to right does exactly what I needed it to do. | 2021-01-31T00:14:04 | 2021-01-31T00:14:04 | {} | NONE |
vuejs | core | 770,373,953 | 3,135 | HcySunYang | You should test in incognito mode in order to eliminate the interference of browser extensions. In addition, you should also click the **collect garbage** button every time you take a snapshot. And finally, I did some tests and found no memory leaks | 2021-01-31T12:22:34 | 2021-01-31T12:22:34 | {} | MEMBER |
vuejs | core | 770,451,387 | 3,131 | posva | do you have a boiled down repro to illustrate the bug? Are you changing the origin of the translation after the element is added? | 2021-01-31T21:09:56 | 2021-01-31T21:09:56 | {} | MEMBER |
vuejs | core | 770,486,988 | 3,110 | Akryum | Thank you for your PR! :+1: | 2021-02-01T00:44:32 | 2021-02-01T00:44:32 | {} | MEMBER |
vuejs | core | 770,719,916 | 3,025 | LinusBorg | @evan as this might be an expensive change, can you take a look for cost/benefit? | 2021-02-01T09:40:14 | 2021-02-01T09:40:14 | {} | MEMBER |
vuejs | core | 771,940,915 | 3,151 | davy-tw | If `$`- prefix is not allowed in exports from `setup()`, I think `$style` should also be banned and we may need to update the documents. 🤔
(Like what `vue-router` does: with composition API, we use `router` instead of `this.$router`) | 2021-02-02T20:04:18 | 2021-02-02T20:04:18 | {} | NONE |
vuejs | core | 769,787,436 | 3,121 | ghost | Yes, this is what I expected. Probably not possible without explicitly specifying slots in the child template? | 2021-01-29T12:52:27 | 2021-01-29T12:52:27 | {} | NONE |
vuejs | core | 770,735,815 | 2,621 | HcySunYang | Except for the solution given by this PR, I can't think of a better way. | 2021-02-01T10:05:09 | 2021-02-01T10:05:09 | {} | MEMBER |
vuejs | core | 770,908,403 | 3,102 | 07akioni | > #3049
I know vue can do a runtime validation. What I need is to make different prop got connected by generic. For example you can create a select component with props:
```
{
value: string | string[]
onChange: (value: string) => void | (value: string[]) => void
}
```
But if I do this there would be a l... | 2021-02-01T14:44:19 | 2021-02-01T14:44:27 | {
"+1": 3,
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 771,690,535 | 3,122 | kiroushi | Yeah, it immediately clicked as soon as I checked CI outcome. Sorry for the hassle.
Would it make sense to expose a prop utility to get typings from a parent’s scope perspective, like HcySunYang mentioned? | 2021-02-02T14:53:46 | 2021-02-02T14:53:46 | {} | NONE |
vuejs | core | 769,760,534 | 3,121 | HcySunYang | Hey, is this what you want? https://codepen.io/hcysunyang/pen/GRNRWJB | 2021-01-29T11:52:39 | 2021-01-29T11:52:39 | {} | MEMBER |
vuejs | core | 771,047,227 | 3,143 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2291 | 2021-02-01T18:07:25 | 2021-02-01T18:07:25 | {} | MEMBER |
vuejs | core | 769,170,415 | 3,117 | HcySunYang | import it from vue:
```ts
import { InputHTMLAttributes } from 'vue
``` | 2021-01-28T15:37:43 | 2021-01-28T15:37:43 | {} | MEMBER |
vuejs | core | 770,693,046 | 3,048 | LinusBorg | @pikax Can you have another look at this? Isue reminds me of similar issues with had with refs in compoisition api and Vue 3 beta/rc.
Just to double-check. | 2021-02-01T09:00:25 | 2021-02-01T09:00:25 | {} | MEMBER |
vuejs | core | 771,564,789 | 3,149 | posva | They are not empty, they are printed as empty. BTW, you should inject outside of `onMounted()`
---
Please, next time consider using the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js) for questions first. But feel free t... | 2021-02-02T11:18:21 | 2021-02-02T11:18:21 | {} | MEMBER |
vuejs | core | 768,907,093 | 3,113 | posva | What are you trying to optimize exactly? | 2021-01-28T09:03:57 | 2021-01-28T09:03:57 | {} | MEMBER |
vuejs | core | 769,119,581 | 3,117 | HcySunYang | You can use `$attrs` to passthrough, for example, https://codepen.io/hcysunyang/pen/abBoRpQ, also check out https://v3.vuejs.org/guide/component-attrs.html#attribute-inheritance | 2021-01-28T14:43:10 | 2021-01-28T14:43:10 | {} | MEMBER |
vuejs | core | 770,229,152 | 3,128 | HcySunYang | Which version of Typescript are you using? You should use Typescript 4.0+ | 2021-01-30T15:28:47 | 2021-01-30T15:28:47 | {} | MEMBER |
vuejs | core | 770,828,394 | 3,003 | LinusBorg | I think we should consider this a `fix:`, not a `feat:`. I don't think we ever meant for collections to act as fully reactive when wrapped in a `shallowReactive`, so this implements the behavior that was originally intended.
Opinions?
If we agree on that, the commit message has to be changed to reflect properly i... | 2021-02-01T12:42:06 | 2021-02-01T12:42:46 | {} | MEMBER |
vuejs | core | 770,889,322 | 3,003 | LinusBorg | Think so, yes. | 2021-02-01T14:16:56 | 2021-02-01T14:16:56 | {} | MEMBER |
vuejs | core | 771,391,696 | 3,144 | 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%) | | 2021-02-02T06:12:22 | 2021-02-02T06:12:22 | {} | NONE |
vuejs | core | 771,391,992 | 3,146 | 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%) | | 2021-02-02T06:13:03 | 2021-02-02T06:13:03 | {} | NONE |
vuejs | core | 771,481,669 | 3,147 | LinusBorg | A minimal reproduction doesn't mean "a single page". It means "the minimum amount of code necessary to demonstrate the problem".
A compete app with vuex, icons, a complete 3rd party framework (elements-plus) it definitely *not* the minimum amount of code necessary here.
Please try to narrow down your problem. You... | 2021-02-02T09:04:05 | 2021-02-02T09:04:45 | {} | MEMBER |
vuejs | core | 769,603,740 | 3,120 | 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%) | | 2021-01-29T06:19:19 | 2021-01-29T06:19:19 | {} | NONE |
vuejs | core | 770,617,565 | 3,140 | 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%) | | 2021-02-01T06:51:57 | 2021-02-01T07:01:52 | {} | NONE |
vuejs | core | 744,225,423 | 2,811 | 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-14T07:12:16 | 2021-01-29T06:23:54 | {} | NONE |
vuejs | core | 769,638,324 | 2,841 | devmount | @recamshak Didn't know about that syntax, it's working, thanks! | 2021-01-29T07:43:55 | 2021-01-29T07:43:55 | {} | NONE |
vuejs | core | 770,239,322 | 1,409 | mcrio | > @AlexandreBonaventure I guess @icehaunter and my use case is more closely to #1826 which got closed as a duplicate of this issue. However, I'll provide an example as mentioned earlier when I continue working on evaluating Vue for our SPA rewrite.
I think @somodevo has a valid point here. If not related to this iss... | 2021-01-30T16:26:20 | 2021-01-30T16:26:20 | {
"+1": 1
} | NONE |
vuejs | core | 770,273,825 | 2,860 | mgdodge | Not surprisingly, [vite.js libarary mode](https://vitejs.dev/guide/build.html#library-mode) output, though minified, still suffers from this. Thinking this should get a bump in priority, since more prominent tooling/documentation is now promoting libarary builds which will suffer from this. | 2021-01-30T20:10:13 | 2021-01-30T20:10:13 | {
"+1": 9
} | NONE |
vuejs | core | 770,395,083 | 3,126 | sapphi-red | It seems this is same with #2362 . | 2021-01-31T14:57:31 | 2021-01-31T14:57:31 | {} | CONTRIBUTOR |
vuejs | core | 770,407,227 | 3,130 | susnux | @HcySunYang Tank you, it works!
Is that intended and I missed it in the docs or is this an issue? | 2021-01-31T16:19:44 | 2021-01-31T16:19:44 | {} | NONE |
vuejs | core | 770,617,192 | 3,137 | 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%) | | 2021-02-01T06:51:13 | 2021-02-01T06:51:13 | {} | NONE |
vuejs | core | 771,393,368 | 3,146 | 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/12012?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-02-02T06:16:10 | 2021-02-02T06:16:10 | {} | CONTRIBUTOR |
vuejs | core | 771,453,657 | 3,143 | rashfael | Thanks, the workaround in #2291 is working. | 2021-02-02T08:15:41 | 2021-02-02T08:15:41 | {} | NONE |
vuejs | core | 772,053,329 | 3,131 | eli-crow | @posva Exactly. But defining "stay where it was" is dependent on which direction gravity is pointing.
I'll see if I have some time to submit an RFC this week. | 2021-02-02T22:28:47 | 2021-02-02T22:28:47 | {} | NONE |
vuejs | core | 768,889,226 | 3,090 | LinusBorg | Noteworthy is that this is only looking at the initial render. Efficiency of updates is another, arguably maybe more important thing for performance.
Also, on the upside, this shows how mouch more efficient Vue 3 is memory-wise. In these measurements, memory consumption is cut in half compared to Vue 2. | 2021-01-28T08:33:12 | 2021-01-28T08:33:12 | {} | MEMBER |
vuejs | core | 770,764,342 | 2,788 | pikax | What is this supposed to fix? Can you provide a fail/fixed test? | 2021-02-01T10:50:59 | 2021-02-01T10:50:59 | {} | MEMBER |
vuejs | core | 771,391,862 | 3,145 | 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%) | | 2021-02-02T06:12:44 | 2021-02-02T06:12:44 | {} | NONE |
vuejs | core | 796,712,926 | 727 | frandiox | @takechihorn You can follow this issue to find an example of `vite-ssr` with Suspense: https://github.com/frandiox/vite-ssr/issues/8 | 2021-03-11T12:50:29 | 2021-03-11T12:50:29 | {} | NONE |
vuejs | core | 797,274,166 | 2,457 | MaybeQHL | @edison1105 Has the problem been solved?I opened it blank in iOS10 + | 2021-03-12T06:43:15 | 2021-03-12T06:43:15 | {} | NONE |
vuejs | core | 799,985,265 | 3,429 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.89 KB (0%) |
| runtime-dom.global.prod.js | 27.16 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-16T06:17:15 | 2021-03-16T06:17:15 | {} | NONE |
vuejs | core | 800,484,925 | 2,600 | industral | > Unless you can provide a reproduction it's very difficult to help you
here I created simple reproducible example https://github.com/industral/vue-symbol-issue
| 2021-03-16T17:59:34 | 2021-03-16T17:59:34 | {} | NONE |
vuejs | core | 796,577,954 | 3,408 | posva | Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-03-11T08:56:39 | 2021-03-11T08:56:39 | {} | MEMBER |
vuejs | core | 797,228,272 | 2,457 | edison1105 | ping @HcySunYang | 2021-03-12T04:36:05 | 2021-03-12T04:36:05 | {} | MEMBER |
vuejs | core | 799,364,296 | 2,627 | 0x1af2aec8f957 | Incorrect type description of TS loader when exporting, reference configuration:
```typescript
// @workDir/typings.d.ts
/* declare module '*.vue' { // NOTE: 非ts-loader
// const value: WebpackContent;
import Vue from 'vue';
export default Vue;
} */
declare module '*.vue' { // NOTE: ts-loader
... | 2021-03-15T12:01:53 | 2021-03-15T12:03:19 | {
"+1": 33
} | NONE |
vuejs | core | 799,763,026 | 3,425 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2603 | 2021-03-15T21:25:40 | 2021-03-15T21:25:40 | {} | MEMBER |
vuejs | core | 799,779,807 | 3,424 | LinusBorg | duplicate of #3024 | 2021-03-15T21:53:32 | 2021-03-15T21:53:32 | {} | MEMBER |
vuejs | core | 800,453,013 | 3,433 | LinusBorg | This is not realated to Vue, but to Vite. Open an issue there. | 2021-03-16T17:16:37 | 2021-03-16T17:16:37 | {} | MEMBER |
vuejs | core | 800,502,621 | 2,600 | skirtles-code | @industral In `index.js`, change this:
```js
import {createApp} from 'vue/dist/vue.esm-browser.js';
```
to this:
```js
import {createApp} from 'vue';
```
Then in `webpack.config.js`, get rid of your existing `resolve` section and replace it with this:
```js
resolve: {
alias: {
vue$: 'vue/dis... | 2021-03-16T18:25:13 | 2021-03-16T18:25:13 | {
"+1": 2,
"heart": 1,
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 797,184,293 | 2,457 | huanggm | @edison1105 @yyx990803 Can we reopen and fix this issue? | 2021-03-12T02:12:17 | 2021-03-12T02:12:17 | {} | NONE |
vuejs | core | 797,473,496 | 3,413 | LinusBorg | ```js
return h("div", { ref: 'elRef' }, "ok");
``` | 2021-03-12T12:57:28 | 2021-03-12T12:57:28 | {} | MEMBER |
vuejs | core | 800,608,949 | 2,279 | UnderTheMoonspell | This problem lost me an entire afternoon. I was trying the same in the vue 2 codepen for the same feature and it was working, so it ended up being a really frustrating day.
It might help someone who will have the same problem in the future:
Because I was iterating an array (json schema to generate inputs) and cal... | 2021-03-16T21:12:01 | 2021-03-16T21:12:01 | {
"+1": 1
} | NONE |
vuejs | core | 795,405,478 | 3,405 | posva | Find the name of the key and use the kebab version of it: https://v3.vuejs.org/guide/migration/keycode-modifiers.html#_3-x-syntax. Note `contextmenu` is an event on its own: `@contextmenu="..."`
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questio... | 2021-03-10T13:21:15 | 2021-03-10T13:21:15 | {} | MEMBER |
vuejs | core | 797,260,756 | 3,410 | edison1105 | > According to Terser's docs, `safari10: true` already indicates `mangle: { safari10: true }`, unless there's a bug on Terser's side.
Yes, I look into the code and find that.
https://github.com/terser/terser/blob/master/lib/minify.js#L103
this line will merge `safari10: true` to `mangle` and `format` | 2021-03-12T06:11:10 | 2021-03-12T06:12:31 | {} | MEMBER |
vuejs | core | 797,309,541 | 2,874 | Blackfaded | With an interface I also gen a compiler Error:
```ts
interface Emit {
(e: 'delete', id: string): void;
(e: 'duplicate', id: string): void;
(e: 'start', id: string): void;
}
const emit = defineEmit<Emit>();
```
```bash
Syntax Error: TypeError: Cannot read property 'content' of null
```
, also this https://github.com/vuejs/vue-next/issues/1518 | 2021-03-12T15:20:33 | 2021-03-12T15:26:56 | {
"+1": 3
} | MEMBER |
vuejs | core | 798,086,505 | 3,415 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/issues/3038 | 2021-03-13T10:11:09 | 2021-03-13T10:11:09 | {} | MEMBER |
vuejs | core | 799,419,078 | 2,457 | huanggm | Could anyone fix this issue? I desire to do something. But I don't have a clue. | 2021-03-15T13:28:19 | 2021-03-15T13:28:19 | {
"+1": 3
} | NONE |
vuejs | core | 799,562,713 | 3,423 | kospl | @LinusBorg this was working with Vue 2 without an issue. While updating to Vue 3 it happened to not save array data correctly. I am not aware for exact reason, this might be too deep to investigate for me personally.
From provided demo it's easy to scope the issue to Vue / Proxy and Chrome storage API, but I am not ... | 2021-03-15T16:34:04 | 2021-03-15T16:34:04 | {} | NONE |
vuejs | core | 799,714,289 | 2,807 | Valter4o | Left async setup without awaiting anything inside and my components didn't appear at all. It would be nice to have at least a warning about the async setup or error. | 2021-03-15T20:03:36 | 2021-03-15T20:11:55 | {} | NONE |
vuejs | core | 795,219,102 | 3,399 | HcySunYang | `GlobalComponents` and `GlobalDirectives`? | 2021-03-10T10:33:34 | 2021-03-10T10:33:34 | {} | MEMBER |
vuejs | core | 795,387,791 | 2,457 | huanggm | It seems that the bug has not been fixed. 😢
iOS version: 10.2
**Steps to reproduce**
vue-cli (@vue/cli 4.5.11) create demo
choose Default (Vue 3 Preview) ([Vue 3] babel, eslint)
And I have changed vue@3.0.0 to vue@3.0.7
<img width="605" alt="8D4E79A9-F1E0-4CAA-84DD-5D5E15D7140C" src="https://user-ima... | 2021-03-10T13:08:01 | 2021-03-10T13:08:01 | {} | NONE |
vuejs | core | 796,489,711 | 3,404 | HcySunYang | Indeed, but strictly speaking it is different from #2768 #2829, but very similar. The reason is that the update of the child component causes the parent component's `renderEffect` to be enqueued (the child component registers its own reactivity data to the parent component through the injected callback function, then t... | 2021-03-11T06:17:20 | 2021-03-11T06:40:31 | {} | MEMBER |
vuejs | core | 796,504,737 | 3,399 | johnsoncodehk | > `GlobalComponents` and `GlobalDirectives`?
Look good, but inconsistent...
```ts
declare module 'vue' {
interface ComponentCustomOptions { }
interface ComponentCustomProperties { }
interface GlobalComponents { }
interface GlobalDirectives { }
}
``` | 2021-03-11T06:47:40 | 2021-03-11T06:47:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 796,552,444 | 3,407 | 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-03-11T08:11:24 | 2021-03-11T08:11:24 | {} | CONTRIBUTOR |
vuejs | core | 797,246,195 | 2,457 | edison1105 | > I just checked the code of terser [terser/terser@`master`/lib/minify.js](https://github.com/terser/terser/blob/master/lib/minify.js), seems yes. @edison1105 can you make a PR? That way we can provide a nightly build for @huanggm to testing.
got it | 2021-03-12T05:32:45 | 2021-03-12T05:32:45 | {} | MEMBER |
vuejs | core | 797,432,209 | 3,412 | LinusBorg | you should be using `@vue/compiler-sfc` to compile Single File Components. Is there a specific reason you want to use the core compiler? | 2021-03-12T11:30:18 | 2021-03-12T11:30:18 | {} | MEMBER |
vuejs | core | 797,555,011 | 2,633 | HcySunYang | [This PR](https://github.com/vuejs/vue-next/pull/3079) provides the checking for duplicate keys | 2021-03-12T15:16:39 | 2021-03-12T15:16:39 | {} | MEMBER |
vuejs | core | 796,457,679 | 3,404 | edison1105 | same as #2768 #2829
caused by https://github.com/vuejs/vue-next/pull/2567
| 2021-03-11T05:08:37 | 2021-03-11T05:08:37 | {} | MEMBER |
vuejs | core | 796,570,757 | 3,408 | LinusBorg | ```ts
//main.ts
declare module '@vue/runtime-core' {
interface ComponentCustomProperties {
$http:any,
}
}
```
Do not put it into `.d.ts` | 2021-03-11T08:44:17 | 2021-03-11T08:44:27 | {} | MEMBER |
vuejs | core | 796,591,389 | 3,399 | pikax | > Look good, but inconsistent...
It looks inconsistent but they mean different things
- **ComponentCustomOptions** : Component custom options when you `defineComponent`, eg: `onBeforeRouteUpdate`
- **ComponentCustomProperties** : Custom `vm` properties available on the `componentInstance`, eg: `$router`
- **Glob... | 2021-03-11T09:17:47 | 2021-03-11T09:17:47 | {
"+1": 12
} | MEMBER |
vuejs | core | 797,238,433 | 2,457 | HcySunYang | I just checked the code of terser https://github.com/terser/terser/blob/master/lib/minify.js, seems yes. @edison1105 can you make a PR? That way we can provide a nightly build for @huanggm to testing. | 2021-03-12T05:10:09 | 2021-03-12T05:10:09 | {} | MEMBER |
vuejs | core | 798,090,111 | 3,416 | HcySunYang | Thanks for this PR, but please see https://github.com/vuejs/vue-next/pull/3040 | 2021-03-13T10:12:49 | 2021-03-13T10:12:49 | {} | MEMBER |
vuejs | core | 798,880,255 | 3,417 | LinusBorg | Please open an issue in their repo, or open a new issue here if you can reproduce the problem without involving 3rd party frameworks. | 2021-03-14T10:04:42 | 2021-03-14T10:04:42 | {} | MEMBER |
vuejs | core | 800,377,674 | 3,431 | 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-03-16T15:46:03 | 2021-03-16T15:46:03 | {} | CONTRIBUTOR |
vuejs | core | 800,406,805 | 2,600 | industral | Looks like it doesn't have anything with two copies with vue. Checked with `BundleAnalyzerPlugin`, it's only 1 copy. Also tried your solution - the same.
I found that issue appears when using `v-for`, in that case it fails with Symbol(Fragment), and using just text without wrapped into tag - it will fail with Symbol(... | 2021-03-16T16:22:13 | 2021-03-16T16:22:56 | {} | NONE |
vuejs | core | 795,822,404 | 2,540 | effset | Thanks ! That's the solution ! :) | 2021-03-10T17:55:32 | 2021-03-10T17:55:32 | {
"hooray": 1
} | NONE |
vuejs | core | 796,502,984 | 3,249 | LinusBorg | We can optimize this for vue's own APIs, but that happens for *any* import, and it does so by design.
in `<script setup>`, the template is treated more like an inline render function - everything that's available in `setup` is available in the render function / template - which includes all imports, and that can eve... | 2021-03-11T06:44:03 | 2021-03-11T06:44:03 | {
"+1": 2
} | MEMBER |
vuejs | core | 797,256,085 | 2,457 | edison1105 | It seems not necessary 😆

| 2021-03-12T05:59:44 | 2021-03-12T06:09:05 | {} | MEMBER |
vuejs | core | 797,470,452 | 3,413 | LinusBorg | The stuff you return from setup is not part of `$props`, it becomes part of `this`.
For further support please use the discord community at chat.vuejs.org | 2021-03-12T12:50:56 | 2021-03-12T12:50:56 | {} | MEMBER |
vuejs | core | 798,937,674 | 3,188 | gaborfeher | Sorry, I seem to have responded to a deleted comment. | 2021-03-14T16:35:49 | 2021-03-14T16:35:49 | {} | NONE |
vuejs | core | 799,160,652 | 3,420 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.89 KB (0%) |
| runtime-dom.global.prod.js | 27.16 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-15T06:46:47 | 2021-03-15T06:46:47 | {} | NONE |
vuejs | core | 799,369,986 | 3,025 | JshGrn | I don't suppose anyone has looked at this any further? | 2021-03-15T12:11:07 | 2021-03-15T12:11:07 | {} | NONE |
vuejs | core | 799,781,727 | 3,424 | LinusBorg | > it doesn't look like it is in a hurry to be merged in
opening another issue for it won't make it happen any quicker on its own ;) We just have a full plate and need to prioritize
Good you have a workaround now, though. | 2021-03-15T21:57:41 | 2021-03-15T21:58:08 | {} | MEMBER |
vuejs | core | 799,782,392 | 3,424 | JshGrn | > > it doesn't look like it is in a hurry to be merged in
>
> opening another issue for it won't make it happen any quicker on its own ;) We just have a full plate and need to prioritize
>
> Good you have a workaround now, though.
Completely understandable, thank you | 2021-03-15T21:59:20 | 2021-03-15T21:59:20 | {} | NONE |
vuejs | core | 799,828,205 | 3,418 | bazuka5801 | @posva I was trying to use codepen, codesandbox, I dont understand these instruments, sorry, but it is really don't working from docs, who is writing doc page with "v-for + article"? | 2021-03-15T23:27:01 | 2021-03-15T23:27:01 | {} | NONE |
vuejs | core | 800,468,853 | 3,432 | plehnen | But according to the docs (https://v3.vuejs.org/guide/migration/emits-option.html#_3-x-behavior) "emits will now be included in the component's `$attrs`, which by default will be bound to the component's root node".
For me it is difficult to understand why documenting emits will affect what's inside `$attrs`. And as... | 2021-03-16T17:37:34 | 2021-03-16T17:40:29 | {
"+1": 1
} | NONE |
vuejs | core | 800,576,399 | 3,432 | LinusBorg | > But according to the docs (v3.vuejs.org/guide/migration/emits-option.html#_3-x-behavior) "emits will now be included in the component's $attrs, which by default will be bound to the component's root node".
You seem to have misread (emphasis mine):
> This is especially important because of the removal of the .na... | 2021-03-16T20:21:37 | 2021-03-16T21:16:38 | {} | MEMBER |
vuejs | core | 800,646,965 | 3,432 | plehnen | Got it. Thanks a lot for explaining!
In my "real" situation I only pass it down to the child. So it is actually not a big deal for me.
I just assumed it would be best practice to add it to the `emits`, as the docs says: "It is highly recommended that you document **all of the events** emitted by each of your compon... | 2021-03-16T22:10:38 | 2021-03-16T22:10:38 | {} | NONE |
vuejs | core | 796,597,496 | 3,408 | zhaoxm2016 | @posva @LinusBorg | 2021-03-11T09:27:17 | 2021-03-11T09:27:17 | {} | NONE |
vuejs | core | 797,359,118 | 2,064 | mikecmpbll | anyone got any clues how to resolve this with webpack? experiencing the same thing. | 2021-03-12T09:25:27 | 2021-03-12T09:25:27 | {} | NONE |
vuejs | core | 798,947,008 | 3,188 | LinusBorg | Yes, it was merged after 3.0.7 and will be part of 3.0.8 | 2021-03-14T17:36:27 | 2021-03-14T17:36:27 | {} | MEMBER |
vuejs | core | 799,047,862 | 3,409 | HcySunYang | Thanks | 2021-03-15T02:28:58 | 2021-03-15T02:28:58 | {
"laugh": 1
} | MEMBER |
vuejs | core | 799,783,045 | 3,423 | LinusBorg | `toRaw()` can give you the non-proxy original data, you should probably save that to storage instead.
```js
chrome.storage.local.set({ error_info: Vue.toRaw(this.error_info) }, function(){
```
Might be worth documenting. | 2021-03-15T22:00:36 | 2021-03-15T22:00:36 | {
"hooray": 2
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.