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 | 753,217,610 | 2,364 | FloppyNotFound | This seems to be a bug in Firefox itself, see https://stackoverflow.com/questions/39044803/syntaxerror-missing-in-const-declaration-firefox-50 and https://bugzilla.mozilla.org/show_bug.cgi?id=1101653 for further reference.
I'm currently experiencing the same issue while creating a Svelte 3.0 App with Rollup for KaiOS.... | 2020-12-31T22:20:31 | 2020-12-31T22:20:31 | {} | NONE |
vuejs | core | 753,344,901 | 2,925 | 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-01T17:06:44 | 2021-01-01T17:06:44 | {} | NONE |
vuejs | core | 753,583,422 | 2,926 | HcySunYang | We should avoid checking whether an element is SVG in `processElement`, which can avoid a lot of computational consumption. And again, I didn’t notice @edison1105 's PR because I’m coding, sorry... | 2021-01-03T08:14:25 | 2021-01-03T08:14:25 | {} | MEMBER |
vuejs | core | 752,065,706 | 2,909 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.52 KB (+0.03% 🔺) |
| runtime-dom.global.prod.js | 26.84 KB (+0.04% 🔺) |
| size-check.global.prod.js | 16.21 KB (+0.04% 🔺) | | 2020-12-29T12:56:14 | 2020-12-29T12:57:05 | {} | NONE |
vuejs | core | 752,398,745 | 2,779 | edison1105 | @LinusBorg
I agree, This problem may often be encountered. | 2020-12-30T10:01:51 | 2020-12-30T10:01:51 | {} | MEMBER |
vuejs | core | 752,807,640 | 2,918 | edison1105 | Duplicate of #2863 | 2020-12-31T01:09:21 | 2020-12-31T01:09:21 | {} | MEMBER |
vuejs | core | 752,813,392 | 2,834 | Mr14huashao | @edison1105，Hi，i find a problem.
The ``skip`` attribute is meaningless and becomes undefined during compilation.
```ts
if (job && !job.skip) //The skip is always undefined.
```
The button still responds properly after the skip is deleted.
```ts
export function invalidateJob(job: SchedulerJob) {
const i =... | 2020-12-31T01:45:17 | 2020-12-31T01:45:17 | {} | NONE |
vuejs | core | 752,898,243 | 2,910 | LinusBorg | That helps a bit but I still don't see how you are seeing a lot of these errors in your app caused by this. an reproduction from a real use case would help us understand what the actual issue and impact is. | 2020-12-31T09:12:07 | 2020-12-31T09:12:20 | {} | MEMBER |
vuejs | core | 754,649,336 | 2,944 | edison1105 | > it will be very complicated
yes, it's very complicated to determine which is the end tag in this case.
```javascript
function parseInterpolation(
context: ParserContext,
mode: TextModes
): InterpolationNode | undefined {
const [open, close] = context.options.delimiters
__TEST__ && assert(startsWit... | 2021-01-05T13:53:33 | 2021-01-05T13:53:33 | {} | MEMBER |
vuejs | core | 751,998,097 | 2,898 | wezter96 | @posva Well I can't really add the type if I want it to be a generic datatable.
Replacing any would render it completely useless since I want to be able to use it with any type of data.
Would prop type inheritance (prop inheriting the type from the component that sets the prop data) be imposible within Vue and have... | 2020-12-29T08:44:22 | 2020-12-29T08:44:22 | {} | NONE |
vuejs | core | 752,366,882 | 2,913 | LinusBorg | This is caused by having more than one copy of vue included in the app (from the different /node_modules/ in the federated pojects).
You have to configure your way so that only one copy is included.
Since you provided no reproduction, we can't really be more specific. | 2020-12-30T08:03:20 | 2020-12-30T08:03:20 | {
"+1": 5,
"-1": 2
} | MEMBER |
vuejs | core | 754,434,647 | 2,942 | 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-05T06:39:43 | 2021-01-05T06:39:43 | {} | NONE |
vuejs | core | 754,697,672 | 2,944 | HcySunYang | Ah, just use the backslash to escape.
https://vue-next-template-explorer.netlify.app/#%7B%22src%22%3A%22%20%20%3Cp%3E%7B%7B%20%24fm('%7BserverCount%2C%20plural%2C%20one%20%7BServer%7D%20other%20%7BServers%7D%5C%5C%7D')%20%7D%7D%3C%2Fp%3E%22%2C%22ssr%22%3Afalse%2C%22options%22%3A%7B%22mode%22%3A%22module%22%2C%22prefix... | 2021-01-05T15:14:09 | 2021-01-05T15:14:09 | {} | MEMBER |
vuejs | core | 754,873,256 | 2,944 | longlho | hmm I'm not sure I understand what you mean by `Interpolation braces are parsed in same way as browser parses <script> tag, basically it terminates on first occurrence of closing sequence.`, any DSL has a way of escaping syntax token so reserved tokens can be used. For HTML it's the HTML entities. Escaping is fine, the... | 2021-01-05T20:14:43 | 2021-01-05T20:14:43 | {} | NONE |
vuejs | core | 755,038,368 | 2,944 | znck | Contents of interpolation braces is JavaScript, providing escape sequence means custom syntax which would break JS tools and IDE.
This should be documented though. cc @vuejs/docs | 2021-01-06T02:37:23 | 2021-01-06T02:37:23 | {} | MEMBER |
vuejs | core | 755,045,085 | 2,944 | longlho | I think it'd be great if u guys can formalize a spec for vue template. I mean like EBNF-style spec rather than "everything inside {{ }} is a black box". I assume it can also be TypeScript/CoffeeScript in there?
Regarding breaking JS tools, as I mentioned, if u unescape before piping to JS parser (in the AST) it shou... | 2021-01-06T03:00:43 | 2021-01-06T03:06:11 | {} | NONE |
vuejs | core | 752,255,536 | 2,912 | posva | Tested on master and works
Duplicate of https://github.com/vuejs/vue-next/issues/2715 | 2020-12-29T21:59:59 | 2020-12-29T21:59:59 | {} | MEMBER |
vuejs | core | 752,356,698 | 2,915 | 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-30T07:18:47 | 2020-12-30T07:18:47 | {} | NONE |
vuejs | core | 753,788,049 | 2,935 | 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-04T06:38:14 | 2021-01-04T06:38:14 | {} | NONE |
vuejs | core | 754,708,145 | 2,944 | posva | I think what @HcySunYang said makes sense and escaping them inside strings is the way to go. Especially because it's only needed when two curly braces are together | 2021-01-05T15:30:31 | 2021-01-05T15:57:25 | {} | MEMBER |
vuejs | core | 754,845,606 | 2,944 | znck | Interpolation braces are parsed in same way as browser parses `<script>` tag, basically it terminates on first occurrence of closing sequence. For including `}}` in string use concatenation `'}'+'}'` and use block comment for other cases `}/**/}` (or consider extracting the expression as a method or computed property).... | 2021-01-05T19:22:12 | 2021-01-05T19:22:12 | {} | MEMBER |
vuejs | core | 752,034,953 | 2,905 | LinusBorg | This is effectively a question about how to annotate function arguments, there is nothing special to consider for Vue here. So this is neither a bug nor a feature request. At best, a topic for documentation over at the vuejs/docs-vext repo.
Please use chat.vuejs.org to ask for help. | 2020-12-29T10:57:36 | 2020-12-29T10:57:36 | {} | MEMBER |
vuejs | core | 752,980,088 | 2,910 | LinusBorg | You are missing an implementation detail:
https://jsfiddle.net/Linusborg/3tkae0jd/
With that flag, you don't get any more warnings. That's also why the render function works if you let Vue compile it itself, the way it's intended:
https://jsfiddle.net/Linusborg/5xL86wuz/ | 2020-12-31T14:52:46 | 2020-12-31T14:52:46 | {} | MEMBER |
vuejs | core | 753,576,906 | 2,926 | dsseng | It's caused by runtime bug, not compiler. Here's the reproduction with render functions:
https://codepen.io/sh7dm/pen/VwKXzbK | 2021-01-03T06:51:19 | 2021-01-03T06:51:19 | {} | CONTRIBUTOR |
vuejs | core | 753,901,190 | 2,230 | HcySunYang | I think this issue has been resolved and can be closed. | 2021-01-04T10:44:22 | 2021-01-04T10:44:22 | {} | MEMBER |
vuejs | core | 754,655,382 | 2,944 | longlho | Is there a way to escape? | 2021-01-05T14:04:20 | 2021-01-05T14:04:20 | {} | NONE |
vuejs | core | 754,724,775 | 2,944 | posva | Oh yeah, those are very different from the original ones with a string only | 2021-01-05T15:56:59 | 2021-01-05T15:57:21 | {} | MEMBER |
vuejs | core | 755,106,214 | 2,944 | znck | I started writing spec (https://github.com/vuejs/docs-next/pull/729), it follows HTML spec like format.
Yes, we can unescape in AST but it will break eslint, typescript, babel vetur (pretty much everything). Parsing of interpolation braces is designed same as `<script>` parsing of HTML (e.g. https://jsfiddle.net/z... | 2021-01-06T06:16:19 | 2021-01-06T06:16:19 | {
"+1": 2,
"heart": 1
} | MEMBER |
vuejs | core | 752,350,250 | 2,892 | edison1105 | ```javascript
const setScopeId = (
el: RendererElement,
scopeId: string | false | null,
vnode: VNode,
parentComponent: ComponentInternalInstance | null
) => {
if (scopeId) {
hostSetScopeId(el, scopeId)
}
if (parentComponent) {
const treeOwnerId = parentComponent.type... | 2020-12-30T06:52:30 | 2020-12-30T07:03:12 | {} | MEMBER |
vuejs | core | 745,802,349 | 2,830 | 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-16T06:44:13 | 2020-12-30T20:54:50 | {} | NONE |
vuejs | core | 752,823,397 | 2,834 | Mr14huashao | @edison1105
After the sourceMap test, I find that `job.skip` is always undefined.
In other words,``! job.skip is`` always true.
```ts
if (job && !job.skip)
```
The job cannot be determined. It is more reasonable to exclude the problem of the af95604 `queue[i] = null`.
Maybe we should deal with the queue a diffe... | 2020-12-31T02:47:29 | 2020-12-31T02:47:29 | {} | NONE |
vuejs | core | 753,606,676 | 2,897 | Polle87 | The problem here is the good old event.timestamp which is not always working right in CEF browsers.
https://github.com/vuejs/vue-next/blob/master/packages/runtime-dom/src/modules/events.ts
```
// line 113
const timeStamp = e.timeStamp || _getNow()
// changed to
const timeStamp = _getNow()
```
This solved the ... | 2021-01-03T12:02:09 | 2021-01-03T12:28:47 | {} | NONE |
vuejs | core | 753,624,700 | 2,917 | skirtles-code | I did something similar in some of my Vue 2 applications. I needed access to `this` and didn't want to add any extra overhead to components that didn't use the property. A getter on `Vue.prototype` worked perfectly.
So far I've only migrated one, very small application to Vue 3. I switched it to use a global mixin w... | 2021-01-03T14:20:52 | 2021-01-03T14:20:52 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 753,897,928 | 2,936 | LinusBorg | FYI I'm working on a small PR to the docs explaining that this option only affects runtime-compilated templates and requires configuration of its counterpart option in build tooling like `vue-loader` etc.
Still, this seems like a good idea for a runtime warning. | 2021-01-04T10:37:32 | 2021-01-04T10:37:32 | {} | MEMBER |
vuejs | core | 753,923,588 | 2,931 | danranVm | > Use a computed() property.
>
> ```js
> export default {
> name: "HelloWorld",
> setup(props, { slots }) {
> const withText = computed(() => {
> const text = getFirstValidNode(slots.default?.({ withText: true }));
> return !!(text && isValidElementNode(text));
> });
>
> return ... | 2021-01-04T11:31:58 | 2021-01-04T11:38:48 | {} | NONE |
vuejs | core | 754,698,994 | 2,944 | longlho | hmm that's not escaping, that's just making invalid syntax. I can do the same with `} }` (space). With escaping, the AST text node is not supposed to contain the escape character. | 2021-01-05T15:16:14 | 2021-01-05T15:16:14 | {} | NONE |
vuejs | core | 755,041,283 | 2,900 | znck | VueDX also needs this change. https://github.com/znck/vue-developer-experience/blob/master/packages/typescript-plugin-vue/src/features/completions/TemplateExpressionCompletionProvider.ts | 2021-01-06T02:47:18 | 2021-01-06T02:47:18 | {} | MEMBER |
vuejs | core | 752,008,618 | 2,903 | posva | Open the issue in English and with a valid reproduction: https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro | 2020-12-29T09:22:26 | 2020-12-29T09:22:26 | {} | MEMBER |
vuejs | core | 754,848,209 | 2,946 | 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-01-05T19:27:06 | 2021-01-05T19:27:06 | {} | CONTRIBUTOR |
vuejs | core | 667,441,177 | 1,745 | PingTouG | ‘saferGetter’ is ok, but muset use this? | 2020-08-01T00:51:02 | 2020-08-01T00:51:02 | {} | NONE |
vuejs | core | 669,857,721 | 1,799 | unbyte | > Same as #1490
That implementation introduces unnecessary impact of the runtime performance. But time loss caused by my implementation can be acceptable
I have run a simple test (node v12.18.0 on win10 using `console.time()`):
- the average time of my implementation is 0.007ms
- the average time of that implem... | 2020-08-06T10:53:01 | 2020-08-06T11:03:56 | {} | CONTRIBUTOR |
vuejs | core | 666,736,607 | 1,739 | yyx990803 | 1. Don't try to make your state deep-destructure-safe, it feels like unnecessary defensive programming. Destructure concerns should only happen at the root level of an object returned from a composition function.
2. Your first code sample actually doesn't work because you are replacing `dataRef.value` in the fetch c... | 2020-07-30T22:10:25 | 2020-07-30T22:10:25 | {} | MEMBER |
vuejs | core | 668,531,051 | 1,775 | posva | I'm realizing there are a few things I should change like adding a warning in dev mode | 2020-08-04T11:04:58 | 2020-08-04T11:04:58 | {
"+1": 1
} | MEMBER |
vuejs | core | 668,704,196 | 1,775 | yyx990803 | 👍 | 2020-08-04T16:42:54 | 2020-08-04T16:42:54 | {} | MEMBER |
vuejs | core | 669,785,302 | 1,796 | 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/7882?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 test... | 2020-08-06T08:18:54 | 2020-08-06T08:18:54 | {} | CONTRIBUTOR |
vuejs | core | 669,841,904 | 1,790 | qgates | @underfin thanks for clarifying. Seems a behavioural change from vue2, is it mentioned in the docs?
https://jsfiddle.net/e3t7sby2/ | 2020-08-06T10:15:11 | 2020-08-06T10:15:11 | {} | NONE |
vuejs | core | 669,917,008 | 1,799 | unbyte | I think it's a trade-off: either restrict usage, or lose some performance, or fail to keep things neat. There needs to be a decision to solve the problem. After all, there is no guarantee that no subtypes of collection used in a project or imported third-party libraries.
btw, I think solution like https://github.com/... | 2020-08-06T13:10:20 | 2020-08-06T13:11:32 | {} | CONTRIBUTOR |
vuejs | core | 670,956,570 | 1,810 | sqal | There's no longer `{ domProps: { innerHTML: '' } }` or any other nested values in vnode data structure, instead vnode now receives flat props object, so simply replace it with innerHTML
Related RFC - https://github.com/vuejs/rfcs/blob/master/active-rfcs/0008-render-function-api-change.md#flat-vnode-props-format
... | 2020-08-08T17:59:46 | 2020-08-08T18:09:22 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 668,507,546 | 1,773 | posva | No, they are removed when the component is destroyed | 2020-08-04T10:07:18 | 2020-08-04T10:07:18 | {} | MEMBER |
vuejs | core | 668,649,629 | 1,782 | posva | @sodatea do you have an idea where would be the fix for this one? Maybe in vue-loader? | 2020-08-04T15:02:06 | 2020-08-04T15:02:06 | {} | MEMBER |
vuejs | core | 669,620,077 | 1,790 | qgates | @posva sorry to chime in but I think the OP's point is that the render function could involve more significant changes than in the demo. I'm curious as to how optimised things are underneath ie. the render function is called but vue doesn't actually do anything since the template doesn't need updating.
Is a call to ... | 2020-08-06T00:53:41 | 2020-08-06T00:53:41 | {} | NONE |
vuejs | core | 669,766,779 | 1,793 | posva | Thank you but there is no need to change the parameter name | 2020-08-06T07:43:49 | 2020-08-06T07:43:49 | {
"confused": 1
} | MEMBER |
vuejs | core | 669,785,668 | 1,783 | dependabot-preview[bot] | Superseded by #1797. | 2020-08-06T08:19:38 | 2020-08-06T08:19:38 | {} | CONTRIBUTOR |
vuejs | core | 669,016,321 | 1,779 | caikan | > Maybe you can try `<script setup>`
>
> See [vuejs/rfcs#182](https://github.com/vuejs/rfcs/pull/182) and https://github.com/vuejs/rfcs/blob/sfc-improvements/active-rfcs/0000-sfc-script-setup.md
Thanks~ I feel that compared with the `<script setup>`, the advantages of my scheme are that it is easy to use, has ver... | 2020-08-05T06:54:18 | 2020-08-05T06:54:18 | {} | NONE |
vuejs | core | 669,936,498 | 1,745 | yyx990803 | Hmm, `slots` is not reactive though, so the computed is pointless...
Also, if you are trying to check for presence of a slot, you should do `!!$slots.default` in the template (don't call it) | 2020-08-06T13:46:30 | 2020-08-06T13:50:06 | {} | MEMBER |
vuejs | core | 670,977,196 | 1,813 | AjaiKN | @posva Thanks for your response!
I tried it on all of these browsers, and it's not working on any of them:
* Firefox 79.0; macOS 10.15.4
* Chrome 84.0.4147.105 (Official Build) (64-bit); macOS 10.15.4
* Safari 13.1; macOS 10.15.4
* Firefox 79.0; Windows 10
* Safari; iOS 13.6
I've been using the CodePen debug... | 2020-08-08T21:45:58 | 2020-08-08T21:50:13 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 668,523,393 | 1,228 | spikyjt | Surely `isolatedModules` is necessary? Whether transpiling TS with esbuild (i.e. Vite) or babel, it is a requirement. Therefore, we want to keep it on when running `tsc --noEmit` because we are supposed to be checking types, but compiling in the same manner as we would when building the app.
This error is happening ... | 2020-08-04T10:45:18 | 2020-08-04T10:46:34 | {
"+1": 5
} | NONE |
vuejs | core | 669,637,973 | 1,790 | underfin | See https://github.com/vuejs/vue-next/issues/1181#issuecomment-628969490 | 2020-08-06T02:00:12 | 2020-08-06T02:00:12 | {
"+1": 2
} | MEMBER |
vuejs | core | 670,063,822 | 1,803 | HerringtonDarkholme | This is caused by wrong setup of ast-explorer. It uses `compiler-core` instead of `compiler-dom`. So it fails to recognize `script` tag. | 2020-08-06T17:17:54 | 2020-08-06T17:17:54 | {} | MEMBER |
vuejs | core | 670,199,853 | 1,790 | skirtles-code | @posva @underfin
Much of the discussion on #1181 seems to be about `$attrs`, `style` and `class`.
The discussion of `props` starts with this comment from Evan:
> Why would a component declare a prop and then never use it?
I can think of several use cases for `props` that aren't used during *rendering*:
... | 2020-08-06T21:25:14 | 2020-08-06T21:25:14 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 670,437,694 | 1,802 | mofux | @posva Thanks for the response. I'm not sure we are talking about the same thing :) To illustrate what I mean I've created a small working example that overwrites the `app.component` function, so it provides a class that can be used to create, mount and destroy an instance of that component programatically (very simila... | 2020-08-07T09:59:16 | 2020-08-07T09:59:16 | {} | NONE |
vuejs | core | 670,975,430 | 1,813 | posva | It works on Chrome and Safari. What browser are you using? | 2020-08-08T21:25:32 | 2020-08-08T21:25:32 | {} | MEMBER |
vuejs | core | 667,245,061 | 1,752 | posva | You need to use the `v-slot` API. I added a note about it in the vue-router readme https://github.com/vuejs/vue-router-next | 2020-07-31T17:34:19 | 2020-07-31T17:34:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 669,036,015 | 1,779 | posva | This should be an RFC (in English to allow everybody to participate) and there is already https://github.com/vuejs/rfcs/pull/180, where you could propose alternatives | 2020-08-05T07:40:51 | 2020-08-05T07:40:51 | {} | MEMBER |
vuejs | core | 669,844,238 | 1,799 | Picknight | Same as #1490 | 2020-08-06T10:20:27 | 2020-08-06T10:20:27 | {} | CONTRIBUTOR |
vuejs | core | 670,250,940 | 1,803 | zouhangwithsweet | Thanks all of you | 2020-08-07T00:08:59 | 2020-08-07T00:08:59 | {} | CONTRIBUTOR |
vuejs | core | 670,293,759 | 1,155 | lxjwlt | not in runtime, compile to "props" by loader instead, is it better?
```javascript
export interface PropsType {
title: string;
}
let ShorterWay = defineComponent<PropsType>((props) => {
return () => (
<p>{props.title}</p>
)
})
// compile to
export interface PropsType {
title: string;
}
let... | 2020-08-07T02:58:49 | 2020-08-07T02:58:49 | {} | NONE |
vuejs | core | 667,660,385 | 1,758 | posva | Please open a new issue once you have the time to create a boiled down reproduction with no external dependencies. You should probably open an issue at Vue-select first (if they do support Vue 3 | 2020-08-02T11:12:09 | 2020-08-02T11:12:09 | {} | MEMBER |
vuejs | core | 669,494,493 | 1,790 | posva | > The actual performance impact will usually be small as no DOM changes should be required. It could add up though if lots of components update at once, maybe inside a list or grid component.
Have you done a benchmark to see the difference between `<child-component/>` (no prop) and `<child-component :value="id"/>`? | 2020-08-05T20:39:56 | 2020-08-05T20:39:56 | {} | MEMBER |
vuejs | core | 669,739,173 | 1,792 | posva | Open a new issue with a valid repro. Thank you | 2020-08-06T06:47:58 | 2020-08-06T06:47:58 | {} | MEMBER |
vuejs | core | 669,865,119 | 1,799 | Picknight | Can you please post the code for the performance test, I am just curious :) | 2020-08-06T11:12:06 | 2020-08-06T11:12:06 | {} | CONTRIBUTOR |
vuejs | core | 669,989,798 | 1,802 | mofux | @posva I'm afraid your solution doesn't offer the same functionality.
In your example you are creating a new **app instance** - but I want to create a new **component instance** of an existing app instance, so other registered app components and mixins can be used by the component instance that is created programat... | 2020-08-06T15:12:33 | 2020-08-06T15:12:33 | {} | NONE |
vuejs | core | 666,896,820 | 1,745 | underfin | I tracked for this and the blew is a mini-reproduction.Maybe we should internal provider a safer getter for `computed` and `customRef`?
``` js
<script src="./dist/vue.global.js"></script>
<div id="app"></div>
<script>
const {createApp, computed, setBlockTracking} = Vue
// this can fix this.
function safer... | 2020-07-31T03:40:28 | 2020-07-31T03:43:50 | {} | MEMBER |
vuejs | core | 667,167,679 | 1,747 | posva | As a workaround you can do use `@click="method()"` instead of `@click="method"` | 2020-07-31T15:04:22 | 2020-07-31T15:04:22 | {} | MEMBER |
vuejs | core | 669,092,139 | 1,782 | underfin | It caused by hoc component (`RouterView`) inherited scopeId and fallthrough scopeId attr to `Home`.I diffed the behavior v2 and v3.The v2 will generate attrs like this `data-v-469af010="" data-v-fae5bece="" data-v-7ba5bd90=""`.The v3 look like lost the behavior or be intention to throw away this.I am not sure that.
J... | 2020-08-05T09:37:57 | 2020-08-05T09:38:58 | {} | MEMBER |
vuejs | core | 670,957,668 | 1,811 | paulshen | Yep, but it still needs a VDOM and lifecycle pass. I'm not reporting this as a bug as I think it's reasonable if the answer is this optimization is delegated to the VDOM.
It seems possible to implement if you add some global state to track whether you're in the middle of derived data. | 2020-08-08T18:11:05 | 2020-08-08T18:11:05 | {} | NONE |
vuejs | core | 668,494,724 | 1,773 | posva | I don't think it makes sense from an API point of view because there is no intuitive way to provide a key to the `watch` object if it is a function. And to be able to rely on `this`, it cannot be an arrow function, it would have to be a regular function, making the syntax even more bothersome, or to pass `this` as the ... | 2020-08-04T09:39:09 | 2020-08-04T09:39:09 | {} | MEMBER |
vuejs | core | 668,535,512 | 1,773 | xPaw | > The same happens with this.$on when the instance is destroyed.
I never knew this either... Maybe it's intuitive, but I never expected Vue to actually keep track of my function calls to automatically turn off events.
Does this work the same way in vue 2 too? | 2020-08-04T11:15:46 | 2020-08-04T11:16:08 | {} | NONE |
vuejs | core | 669,890,534 | 1,799 | Picknight | I changed the number of for loops to `10000`, below are the results of several tests(environment: MacBook Pro 16-inch, Chrome 84.0.4147.105):
```
a: 4.263916015625ms
b: 3.35009765625ms
c: 0.240966796875ms
a: 2.878173828125ms
b: 3.525146484375ms
c: 0.202880859375ms
a: 4.864013671875ms
b: 3.117919921875ms
c... | 2020-08-06T12:13:51 | 2020-08-06T12:13:51 | {} | CONTRIBUTOR |
vuejs | core | 669,997,148 | 1,794 | unbyte | solved by https://github.com/vuejs/vue-next/commit/ed4381020fcea0494f19f11bebabd9108f2dafd7 | 2020-08-06T15:24:26 | 2020-08-06T15:24:26 | {
"laugh": 1
} | CONTRIBUTOR |
vuejs | core | 670,251,963 | 1,803 | zouhangwithsweet | > This is caused by wrong setup of ast-explorer. It uses `compiler-core` instead of `compiler-dom`. So it fails to recognize `script` tag.
I will try useing `parse` of `compiler-dom`. | 2020-08-07T00:12:40 | 2020-08-07T00:12:40 | {} | CONTRIBUTOR |
vuejs | core | 668,249,114 | 1,755 | yyx990803 | VNode props are never guaranteed to be normalized, this is not documented behavior. The normalization happens only when the component is receiving the props. | 2020-08-03T21:24:40 | 2020-08-03T21:24:40 | {} | MEMBER |
vuejs | core | 668,261,844 | 1,760 | yyx990803 | Thanks for the PR - however, I think it's better (and easier) to cache the invoker on the element by event name instead. See 1c967fc4 | 2020-08-03T21:57:58 | 2020-08-03T21:57:58 | {} | MEMBER |
vuejs | core | 668,498,581 | 1,773 | xPaw | > Where doing it with the created hook is straightforward and allows you to use the syntax already
Don't you need to keep track of the returned value by `$watch` to later on call it to unwatch when component gets destroyed? | 2020-08-04T09:47:26 | 2020-08-04T09:47:26 | {} | NONE |
vuejs | core | 668,978,270 | 1,228 | sapphi-red | FYI setting `skipLibCheck` to `true` will make the error not happening. (Of course we will not be able to catch library type definition errors.) | 2020-08-05T04:51:29 | 2020-08-05T04:51:29 | {} | CONTRIBUTOR |
vuejs | core | 669,272,194 | 1,772 | unbyte | Finally I understand what you mean. I'm so foolish.
But the items got from maps are not like this
```javascript
const reactiveTest = reactive(test)
const readonlyTest = readonly(reactiveTest)
```
Instead, they are more like this
```javascript
const reactiveTest = reactive(test)
const readonlyTest = readon... | 2020-08-05T15:50:22 | 2020-08-05T16:11:55 | {} | CONTRIBUTOR |
vuejs | core | 669,738,757 | 1,790 | posva | @underfin thanks, I knew we had the explanation of correctness somewhere | 2020-08-06T06:46:55 | 2020-08-06T06:46:55 | {} | MEMBER |
vuejs | core | 670,065,541 | 1,803 | posva | @zouhangwithsweet you should open an issue at https://github.com/fkling/astexplorer if the problem is there | 2020-08-06T17:20:52 | 2020-08-06T17:20:52 | {} | MEMBER |
vuejs | core | 667,042,711 | 1,712 | cliqer | I'm using `pug` with latest `vite` and `vue rc5`.
The error appears on child `v-if` even when `v-for` is not used.
edit: Nevermind, on my case I had a 3rd `v-if` that also had a `:key`.
Removed the key and the error is gone. | 2020-07-31T10:02:00 | 2020-07-31T10:09:29 | {} | NONE |
vuejs | core | 667,505,952 | 1,754 | posva | When reporting a bug please provide a minimal reproduction with one singe package.json and only the required packages to reproduce the problem.
For SSR, you might want to wait for documentation. Otherwise, you can give existing tests a look as well as other projects like https://github.com/pikax/zipe | 2020-08-01T09:55:20 | 2020-08-01T09:55:20 | {} | MEMBER |
vuejs | core | 667,719,212 | 1,761 | posva | This is expected, it's too late to listen to the `onMounted` anyway.
You should call the `useMousePosition` outside of `onMounted` | 2020-08-02T20:12:40 | 2020-08-02T20:12:40 | {} | MEMBER |
vuejs | core | 668,245,106 | 1,757 | yyx990803 | Thanks! | 2020-08-03T21:14:22 | 2020-08-03T21:14:22 | {} | MEMBER |
vuejs | core | 668,844,057 | 1,778 | posva | Please provide a boiled down reproduction when reporting a bug using something like JS fiddle, codepen or codesandbox
This is a whole project | 2020-08-04T21:55:12 | 2020-08-04T21:55:12 | {} | MEMBER |
vuejs | core | 669,035,122 | 1,782 | posva | Right. Do you know why does it not appear on the jsfiddle? | 2020-08-05T07:39:09 | 2020-08-05T07:39:09 | {} | MEMBER |
vuejs | core | 669,326,967 | 1,787 | yakobe | We also ran into this while prepping an upgrade. We need the `form` attribute to submit named forms. It seems vue doesn't recognize it as a [valid attribute](https://www.w3schools.com/tags/att_button_form.asp). | 2020-08-05T17:30:53 | 2020-08-05T17:30:53 | {} | NONE |
vuejs | core | 669,837,346 | 1,800 | posva | Do you mean adding a extra check at https://github.com/vuejs/vue-next/blob/master/packages/compiler-dom/src/transforms/vModel.ts#L64 to allow `type="select"` on a custom component? | 2020-08-06T10:04:36 | 2020-08-06T10:04:36 | {} | MEMBER |
vuejs | core | 669,984,158 | 1,802 | posva | You have to pass the props to `createApp`:
```js
Vue.createApp({
template: '<div>Hello {{name}}</div>',
props: ['name']
}, { name: 'Thomas' }).mount('#my-component-mountpoint')
``` | 2020-08-06T15:03:27 | 2020-08-06T15:03:27 | {} | MEMBER |
vuejs | core | 670,500,917 | 1,802 | mofux | > I think this belongs in the user land but maybe there is a lot of people using it and it worth adding a utility to Vue that can be tree shaken
Creating a tree-shakable utility for this sounds like a good idea. I don't currently have the time to drive the RFC process for this though. Anyway, I think the sample code... | 2020-08-07T12:51:50 | 2020-08-07T12:51:50 | {} | NONE |
vuejs | core | 666,858,998 | 1,739 | fxxjdedd | Thanks for the replay!
I did make some mistakes in using the API. It was stupid. But I've always wondered why it's easy for me to fall into a trap when using the composition API. My goal is to find a way to stop users from making such stupid mistakes.
It is true that if you follow: simply don't destructure. It will... | 2020-07-31T01:24:33 | 2020-07-31T01:27:02 | {} | NONE |
vuejs | core | 666,929,723 | 1,538 | qmhc | @yyx990803
but
will it is added in the official version? | 2020-07-31T05:23:13 | 2020-07-31T05:23:13 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.