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 | 760,367,772 | 3,015 | posva | The genearted code uses an arrow function. You should use `<component @my-event="(...args) => handleEvent('thing', ...args)" />`. I would say this should be documented | 2021-01-14T18:07:52 | 2021-01-14T18:07:52 | {
"+1": 9
} | MEMBER |
vuejs | core | 760,622,674 | 3,021 | HcySunYang | > The tsx component supports global id and name instead of props
If you treat `name` as `IntrinsicAttributes`, it means that all `IntrinsicElements` can use the `name` attribute, which is incorrect, the `name` attribute is valid only on the following elements: `<button>`, `<fieldset>`, `<form>`, `<iframe>`, `<input>... | 2021-01-15T03:32:39 | 2021-01-15T03:32:39 | {} | MEMBER |
vuejs | core | 760,795,655 | 3,022 | posva | yes, that's the link | 2021-01-15T10:00:51 | 2021-01-15T10:00:51 | {
"heart": 1
} | MEMBER |
vuejs | core | 761,548,417 | 3,029 | HcySunYang | You can use https://github.com/vuejs/jsx-next
And, I close this issue. If you think the type checking between h and jsx still bothers you (inconsistent behavior), then you can open a new issue about that. | 2021-01-16T11:32:06 | 2021-01-16T11:32:06 | {} | MEMBER |
vuejs | core | 761,557,878 | 3,031 | l0rn | Hm, i just double checked. I clicked the link in a non-logged in private window and it still shows correctly :thinking:
Maybe the permalink to the problematic line helps?
https://github.com/l0rn/inject-provide-types/blob/75743eb91230424db07f6dbfb4095a918c890da7/src/components/Marker.vue#L23 | 2021-01-16T12:44:15 | 2021-01-16T12:45:08 | {} | NONE |
vuejs | core | 761,801,210 | 3,035 | posva | Please read https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro to understand what we expect as a boiled down repro.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-01-17T12:04:59 | 2021-01-17T12:04:59 | {} | MEMBER |
vuejs | core | 762,723,177 | 3,008 | lijingfaatcumt | > If you don't create a boiled down repro showing the existing problem or provide test cases, this won't be able to go any further...
@posva isShallow is useful, please see https://github.com/vuejs/vue-next/pull/3052 , i use isShallow to separete reactive and shallowReactive | 2021-01-19T09:39:40 | 2021-01-19T09:39:40 | {} | NONE |
vuejs | core | 762,863,078 | 3,057 | posva | Please add your review at https://github.com/vuejs/vue-next/pull/2851 instead of copying and adding commits and communicate what you think is missing. That would really help us 🙂 | 2021-01-19T14:10:14 | 2021-01-19T14:10:14 | {} | MEMBER |
vuejs | core | 758,509,233 | 2,621 | HcySunYang | According to these specs:
- https://tc39.es/ecma262/#sec-object.prototype.hasownproperty
- https://tc39.es/ecma262/#sec-hasownproperty
1. Assert: Type(O) is Object.
2. Assert: IsPropertyKey(P) is true.
3. Let desc be ? `O.[[GetOwnProperty]](P)`.
4. If desc is undefined, return false.
5. Return true.
In ste... | 2021-01-12T08:58:17 | 2021-01-14T08:37:21 | {
"+1": 2
} | MEMBER |
vuejs | core | 760,362,496 | 3,016 | veaba | > If you have found a bug please provide a reproduction, if you have a code improvement proposal, please open a pull request
Hi, @posva： Sorry about that.
Can you help a little to explain the above phenomenon?
I'm not quite sure if the error I'm pointing out is correct.
If what I say is correct, I will initi... | 2021-01-14T17:58:45 | 2021-01-14T17:58:45 | {} | MEMBER |
vuejs | core | 760,392,903 | 3,017 | diwic | Thanks - if this is indeed intentional, may I ask that it should be clearly stated in the documentation?
(Fwiw, The documentation for [extends](https://v3.vuejs.org/api/options-composition.html#extends) mentions `Vue.extend` which is no longer available) | 2021-01-14T18:41:19 | 2021-01-14T18:42:06 | {} | NONE |
vuejs | core | 760,741,857 | 3,022 | posva | Thank you but this would be a breaking change on something that is working as intended. It won't be considered unless it's fixing an existing case without breaking others.
You might want to open an RFC in the rfcs repository instead to propose something new | 2021-01-15T08:16:25 | 2021-01-15T08:16:25 | {} | MEMBER |
vuejs | core | 761,710,754 | 3,033 | yesixuan | When we go back to the correct resource or resource error, we should clear the delay timer and timeout timer | 2021-01-17T01:23:50 | 2021-01-17T01:23:50 | {} | NONE |
vuejs | core | 762,038,198 | 3,041 | 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-18T07:15:49 | 2021-01-18T07:15:49 | {} | NONE |
vuejs | core | 762,075,884 | 3,044 | Kingbultsea | see #3045 | 2021-01-18T08:26:33 | 2021-01-18T08:26:33 | {
"+1": 4
} | CONTRIBUTOR |
vuejs | core | 762,571,253 | 3,046 | cc-max | After doing some verification, an error was reported in helloworld.vue, ‘The template root disallows'</slot>' elements ’ | 2021-01-19T03:03:13 | 2021-01-19T03:03:13 | {} | NONE |
vuejs | core | 762,629,253 | 3,054 | 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-19T06:24:15 | 2021-01-19T06:24:15 | {} | NONE |
vuejs | core | 762,661,872 | 3,055 | LinusBorg | $el returns a plain DOM element. What you see has nothing to do with Vue. The issue tracker is also not meant for posting questions about things that are unclear to you. it's for bugs.
Feel free to ask about Javascript and how the DOM works in an appropriate channel on chat.vuejs.org | 2021-01-19T07:42:17 | 2021-01-19T07:42:17 | {} | MEMBER |
vuejs | core | 762,878,778 | 3,056 | plehnen | It wasn't a question. I know that I have to call the slots.default() function. The problem is that in vue2 the value is "undefined" as expected when the body is empty, but in vue3 the value is filled, even if the body is just a `<b v-if="false">not visible at all</b>` code. And this makes it impossible to migrate such ... | 2021-01-19T14:33:36 | 2021-01-19T14:35:09 | {} | NONE |
vuejs | core | 763,384,646 | 3,062 | 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-20T07:00:02 | 2021-01-20T07:00:02 | {} | NONE |
vuejs | core | 763,384,766 | 3,063 | 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-20T07:00:18 | 2021-01-20T07:00:18 | {} | NONE |
vuejs | core | 760,226,005 | 3,010 | HcySunYang | This can be reproduced by (from @Justineo):
https://www.typescriptlang.org/play?#code/C4TwDgpgBA8mwGcA8AVAfFAvFA3gKCigBMBDYEgCgEoAuKFAbgKgFsJgALAeyITv0KEA2gGs6CYACcAlgDsA5gF061LBhKyQTQgF8oAMnodpCFOAio0THUzwAzAK6yAxsGldZUO7MsUu8OjhES1ooADcuaSJcHTx7WQoBYjJKKlxmQkl2B0lPJMFwkgAbBwg6AEYMqBtmHQAaZjZOHj50grsuLlV8wU4TADow4tLb... | 2021-01-14T14:20:08 | 2021-01-14T14:20:08 | {} | MEMBER |
vuejs | core | 761,560,662 | 3,031 | pikax | I think this is a request to get the type when using `inject` with Options API
```ts
defineComponent({
inject: [ 'myVar'],
mounted(){
this.myVar // doesn't exists
}
})
```
Ideally we would also be able to get the typing information, it would be cool to use the `InjectionKey<T>` for that
```ts
co... | 2021-01-16T13:07:36 | 2021-01-16T13:07:36 | {
"+1": 12,
"confused": 1
} | MEMBER |
vuejs | core | 762,128,371 | 3,034 | posva | Using a `number` would be easier to not depend on NodeJS types. A reproduction or failing test case is still necessary to move forward | 2021-01-18T09:51:04 | 2021-01-18T09:51:04 | {} | MEMBER |
vuejs | core | 762,608,983 | 2,851 | lijingfaatcumt | > @lijingfaatcumt What behavior would you in that case?
@LinusBorg in vue3, designing reactiveMap and readonlyMap is for cache the proxy version if the target has the proxy or the target is a proxy, but in you pr, the code below will cause the cache useless
```javascript
let proxy = reactive(origin)
let shallowPr... | 2021-01-19T05:23:42 | 2021-01-19T05:39:01 | {} | NONE |
vuejs | core | 762,803,850 | 2,851 | lijingfaatcumt | > Converted this back to a draft as there's both ongoing discussion about the approach itself by @jods4 and an edge case raised by @lijingfaatcumt that isn't covered yet.
@LinusBorg i have find the new way to solve the problem by https://github.com/vuejs/vue-next/pull/3052 ， it use 'isReadonly' and 'isShallow' prop... | 2021-01-19T12:14:32 | 2021-01-20T01:53:18 | {} | NONE |
vuejs | core | 760,278,489 | 3,012 | HcySunYang | Before you submit a PR, you should give a reproduction, because there may be a more appropriate solution. | 2021-01-14T15:42:04 | 2021-01-14T15:42:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 760,687,192 | 3,023 | 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-15T06:38:56 | 2021-01-15T06:38:56 | {} | NONE |
vuejs | core | 760,689,172 | 3,023 | 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/11767?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-01-15T06:43:36 | 2021-01-15T06:43:36 | {} | CONTRIBUTOR |
vuejs | core | 760,735,585 | 3,008 | posva | If you don't create a boiled down repro showing the existing problem or provide test cases, this won't be able to go any further... | 2021-01-15T08:12:24 | 2021-01-15T08:12:24 | {} | MEMBER |
vuejs | core | 761,027,465 | 3,026 | 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).
Bug reports must have a boiled down reproduction (https... | 2021-01-15T16:00:51 | 2021-01-15T16:00:51 | {} | MEMBER |
vuejs | core | 761,535,386 | 3,029 | HcySunYang | Vue denies unknown props by default, you can change this behavior through `ComponentCustomProps`:
```ts
declare module 'vue' {
interface ComponentCustomProps {
custom?: number
}
}
```
Check this file: https://github.com/vuejs/vue-next/blob/master/test-dts/componentTypeExtensions.test-d.tsx , you can... | 2021-01-16T09:43:00 | 2021-01-16T09:43:00 | {} | MEMBER |
vuejs | core | 761,539,519 | 3,029 | 07akioni | > https://github.com/vuejs/vue-next/blob/master/test-dts/componentTypeExtensions.test-d.tsx
I wonder why it works in raw `h` function but not in tsx. Could you please explain what does the transformation do? Thanks. @HcySunYang
Since `inheritAttrs` works by default, I think it is wired that DOM events props are ... | 2021-01-16T10:19:56 | 2021-01-16T10:27:37 | {} | CONTRIBUTOR |
vuejs | core | 761,547,609 | 3,029 | 07akioni | Thanks! And I find it's wired to implement `v-model` in tsx. To make props like `onUpdate:value` work, I need to write `<Comp {...{ 'onUpdate:value': null }} />`.
I think it make it hard to build a libr... | 2021-01-16T11:25:15 | 2021-01-16T11:33:23 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 762,111,846 | 2,791 | aethr | We ran into the same issue in our app where we're creating a validation helper similar to Vuelidate.
We define a `validations` option in a component when we want some data properties to be validated, and a global mixin will add this to a `computed` property (so that validation rules can rely on other data properties... | 2021-01-18T09:24:39 | 2021-01-18T09:24:39 | {
"+1": 1,
"eyes": 1
} | NONE |
vuejs | core | 762,665,248 | 3,052 | LinusBorg | You have a point here, but I don't think the solution is the best one.
Checking the WeakMap for an existing entry is a comparatively expensive OP, which is why it's been placed *after* the check of `ReactiveFlags.RAW` etc.
Will look further into it later. | 2021-01-19T07:49:59 | 2021-01-19T07:49:59 | {} | MEMBER |
vuejs | core | 762,861,234 | 3,056 | 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 have to check and call the function and lo... | 2021-01-19T14:07:24 | 2021-01-19T14:07:24 | {} | MEMBER |
vuejs | core | 762,959,902 | 3,050 | Xenoha |
Hello @HcySunYang , thanks for the reply. That was an easy error on my part trying to demonstrate the problem. Thanks for the fix. However, going through this exercise has made me realize that RC doesn't seem to be inside of the Teleport. See the below screenshot of my app instance that is being built from 'runtime-c... | 2021-01-19T16:30:16 | 2021-01-19T16:37:58 | {} | NONE |
vuejs | core | 759,988,517 | 2,993 | muelbr | > you can also define `click` as a component event by adding
>
> ```js
> export default {
> emits: ["click"],
> }
> ```
>
> With this, Vue will no longer add a native eventlistener for this event, and you can control it with `$emit`
This seems not working with web-components, e.g.
https://github.com/mat... | 2021-01-14T07:42:57 | 2021-01-14T07:45:45 | {} | NONE |
vuejs | core | 714,905,695 | 2,457 | edison1105 | incorrect reproduction link @0x30 | 2020-10-23T04:38:31 | 2020-10-23T04:38:31 | {} | MEMBER |
vuejs | core | 715,210,370 | 2,457 | 0x30 | may not need to provide a reproduction link.
Follow the steps below to see this problem
```
// @vue/cli 4.5.8
vue create demo
// choose vue 3 default
cd demo
npm run serve
// open url on ios 10 device
```
This is the [project](https://github.com/0x30/vue-next-issues-2457) and [recorded file
](https://gi... | 2020-10-23T09:08:49 | 2020-10-23T09:09:13 | {} | NONE |
vuejs | core | 708,587,802 | 2,380 | LinusBorg | a raw object is not reactive, and can't be observed (that's why you marked it raw, right?).
Strict mode just watches the state tree for changes to reactive objects, and then warns about them. changes to nonreactive objects can't be observed and consequently, can't be warned about.
Vuex should likely add an option... | 2020-10-14T18:39:28 | 2020-10-25T19:45:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 716,527,077 | 2,488 | posva | There is already another issue opened about events casing I think | 2020-10-26T12:54:49 | 2020-10-26T12:54:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 717,370,118 | 1,409 | LinusBorg | > const { useRouter } = await import('vue-router');
Why import the router asyncronously?
1. If the project uses `vue-router` in their app, it will already be synchronously imported in their `main.js` bundle.
2. If they don't have `vue-router` installed, this will throw an error
3. If they have `vue-router` ins... | 2020-10-27T16:36:53 | 2020-10-27T16:36:53 | {} | MEMBER |
vuejs | core | 717,646,429 | 2,493 | lixiaofa | I'd like to ask why this design is so designed that indexes can't be collected by dependency, but by using lastIndexOf, indexof and includes. Shouldn't readonly behave consistently | 2020-10-28T01:59:49 | 2020-10-28T01:59:49 | {} | NONE |
vuejs | core | 717,772,909 | 2,493 | LinusBorg | Please be more specific and provide an example. | 2020-10-28T08:16:08 | 2020-10-28T08:16:08 | {} | MEMBER |
vuejs | core | 717,820,961 | 2,503 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-28T09:50:38 | 2020-10-28T09:50:38 | {} | NONE |
vuejs | core | 718,092,367 | 2,508 | LinusBorg | The repo he links to is Vue 2. It rather seems he missed to actually pass the parent slot to the child scoped slot.
An actual repo in Vue 3 would help. | 2020-10-28T17:30:37 | 2020-10-28T17:31:49 | {} | MEMBER |
vuejs | core | 718,108,337 | 2,508 | pmisiejuk | Ups. My fault. I reproduced it in bigger app with vue 3. Here it's 2xx beacuse I used wrong Vue CLI option. Trust me it occurs the same in vue 3 - follow my commits. I spend whole day trying to archieve this. I don't have more time now to migrate.
Providing details component as a prop for recursive component is ok for... | 2020-10-28T17:57:41 | 2020-10-28T17:57:41 | {} | NONE |
vuejs | core | 716,193,308 | 2,484 | KaelWD | There's more `@vue/*` packages than that. | 2020-10-25T18:49:54 | 2020-10-25T18:49:54 | {} | CONTRIBUTOR |
vuejs | core | 716,499,859 | 2,488 | posva | It looks like a casing problem, using `<slot name="boolean" :hasBeenClicked="hasBeenClicked"></slot>
` works | 2020-10-26T11:55:54 | 2020-10-26T11:55:54 | {
"+1": 2
} | MEMBER |
vuejs | core | 717,404,609 | 1,409 | AlexandreBonaventure | @LinusBorg
> 2. If they don't have vue-router installed, this will throw an error
This is exactly what I want to avoid. static imports are not catchable.
The goal is to conditionally support vue-router. | 2020-10-27T17:31:04 | 2020-10-27T17:31:12 | {} | CONTRIBUTOR |
vuejs | core | 717,820,580 | 2,500 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-28T09:50:02 | 2020-10-28T09:50:02 | {} | NONE |
vuejs | core | 717,781,631 | 2,493 | lixiaofa | readonlyState.includes("a"); readonly(["a", "b", "c"]) Collected by dependency
readonlyState[0] readonly(["a", "b", "c"]) not be collected by dependency
Shouldn't readonly behave consistently | 2020-10-28T08:34:46 | 2020-10-28T10:34:25 | {} | NONE |
vuejs | core | 718,084,512 | 2,508 | KaelWD | Still seems like a bug to me, pretty sure you could do it in vue 2. | 2020-10-28T17:17:56 | 2020-10-28T17:17:56 | {} | CONTRIBUTOR |
vuejs | core | 715,516,145 | 2,473 | alperkay | > Please open the issue on the relevant repository like vue-class-component if this was already fixed in [vuejs/vue-cli#5974](https://github.com/vuejs/vue-cli/issues/5974)
You're totally right. I didn't realise that this was happening due to vue-class-component. I'll open the issue there. Thanks for noticing. | 2020-10-23T18:47:17 | 2020-10-23T18:47:17 | {} | NONE |
vuejs | core | 716,104,370 | 2,464 | pikax | This is caused because your `core.state.bricks` is not of type `Brick` but `Readonly<Brick>`
If you want to have the correct type you need to update to use `as PropType<DeepReadonly<Brick>>`
```ts
imp... | 2020-10-25T07:10:41 | 2020-10-25T07:13:02 | {} | MEMBER |
vuejs | core | 716,460,349 | 2,184 | IndexXuan | @yyx990803 @posva
our Lowcode tools uses templateRef to bind Model and UI, we don't use template`@click` directly.
also, rxjs use fromEvent https://github.com/antfu/vueuse/tree/master/packages/rxjs, while these only support native button element, prevent all vue UI librarys. sad.
We need these to implement useEve... | 2020-10-26T10:35:45 | 2020-10-26T10:35:45 | {} | NONE |
vuejs | core | 717,777,824 | 1,409 | LinusBorg | @icehaunter provide a ref synchronously and populate it with the data after the asyncs fetch operation has finished.
@somodevo if you need to fetch data before you initialize your app, then don't initialize your app before you got the data. Different problem then what this issue is about.
> This is exactly what... | 2020-10-28T08:26:29 | 2020-10-28T08:26:29 | {} | MEMBER |
vuejs | core | 717,819,670 | 2,489 | dependabot-preview[bot] | Superseded by #2503. | 2020-10-28T09:48:16 | 2020-10-28T09:48:16 | {} | CONTRIBUTOR |
vuejs | core | 718,166,076 | 2,512 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-28T19:41:52 | 2020-10-28T19:41:52 | {} | NONE |
vuejs | core | 718,205,549 | 1,249 | LinusBorg | I'll close this as there's no real traction and limited benefit. | 2020-10-28T20:59:43 | 2020-10-28T20:59:43 | {} | MEMBER |
vuejs | core | 718,206,591 | 1,356 | LinusBorg | @xiaoxiangmoe is this still relevant? There have been significant changes been done to `jsx.d.ts`, so can you please respond wether this issue is still actionable or can be closed?
Thanks! | 2020-10-28T21:01:46 | 2020-10-28T21:01:46 | {} | MEMBER |
vuejs | core | 714,905,140 | 2,448 | edison1105 | ```js
rollup -f cjs,esm-bundler
```
this is not supported with muitl output format in rollup-cli | 2020-10-23T04:36:46 | 2020-10-23T04:36:46 | {} | MEMBER |
vuejs | core | 715,701,257 | 2,477 | znck | It's common to omit protocol in assets. Can you add a test case for `//localhost`? | 2020-10-24T05:07:13 | 2020-10-24T05:07:13 | {} | MEMBER |
vuejs | core | 716,046,216 | 2,479 | posva | Closing as this is an expected difference between Vue 2 and Vue 3 | 2020-10-24T19:50:05 | 2020-10-24T19:50:05 | {} | MEMBER |
vuejs | core | 716,094,146 | 2,481 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-25T04:55:56 | 2020-10-25T04:55:56 | {} | NONE |
vuejs | core | 717,825,168 | 2,493 | LinusBorg | We only collect the minimal dependencies necessary.
1. in the first example, "a" could be anywhere in the array, so we have to collect the whole array as a dep.
2. in the second example, we only need 1 dep for the first index of the array, because that's all that's ever read from the array.
I'm not sure how to ... | 2020-10-28T09:58:24 | 2020-10-28T10:34:40 | {} | MEMBER |
vuejs | core | 716,029,074 | 2,477 | internettrans | @znck good catch - adding that test revealed a bug. I have pushed a new commit with the test and the corresponding fix. | 2020-10-24T17:38:08 | 2020-10-24T17:38:08 | {} | NONE |
vuejs | core | 716,201,318 | 2,215 | jmheretik | any news about how to properly nest suspense + keep alive + component with **async setup**? even though the PR linked above is already merged im still getting an error unless i use the old `3.0.0-rc.5` :-(
my setup:
```
<router-view v-slot="{ Component }">
<Suspense>
<keep-alive>
<component :is="Com... | 2020-10-25T19:47:11 | 2020-10-25T19:47:11 | {} | NONE |
vuejs | core | 717,779,139 | 2,493 | lixiaofa | setup() {
const readonlyState = readonly(["a", "b", "c"]);
effect(() => {
debugger;
readonlyState.includes("a");
});
},
so
readonly(["a", "b", "c"]) Collected by dependency
if
setup() {
const readonlyState = readonly(["a", "b", "c"]);
effect(() => {
debugger;
... | 2020-10-28T08:29:19 | 2020-10-28T08:29:19 | {} | NONE |
vuejs | core | 717,892,159 | 2,507 | mpricu | ok. And how I can access the global properties inside the setup()? | 2020-10-28T12:11:44 | 2020-10-28T12:11:44 | {} | NONE |
vuejs | core | 715,564,147 | 1,600 | nfplee | I already commented on a closed issue but just so it’s not ignored, please see my post over at stack overflow https://stackoverflow.com/questions/64432182/vue-3-removes-white-space-between-inline-block-elements which shows how this is a breaking change from v2 and how it affects the rendered output contrary to what’s b... | 2020-10-23T20:03:08 | 2020-10-24T23:06:50 | {} | NONE |
vuejs | core | 717,164,533 | 2,495 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.15 KB (-0.01% 🔽) |
| runtime-dom.global.prod.js | 26.43 KB (-0.01% 🔽) |
| size-check.global.prod.js | 15.95 KB (-0.02% 🔽) | | 2020-10-27T11:05:03 | 2020-10-27T11:05:03 | {} | NONE |
vuejs | core | 718,202,709 | 802 | LinusBorg | Judging from the convo in the PR, this issue can be closed. | 2020-10-28T20:54:07 | 2020-10-28T20:54:07 | {} | MEMBER |
vuejs | core | 715,470,661 | 2,093 | IlCallo | Small side effect of this: you can use an `await` to avoid a dependency to be tracked.
I had this situation where a `watchEffect` needed to use 3 reactive refs, but track only 2 of them.
`watch` shall be used in these cases, but leveraging this behaviour you can actually filter which dependency to track (eg. adding... | 2020-10-23T17:19:52 | 2020-10-23T17:21:21 | {
"+1": 3
} | NONE |
vuejs | core | 716,014,537 | 2,479 | Tzdy | @unbyte
```
const app = Vue.createApp({
data() {
return {
items: []
}
},
methods: {
addItem() {
let item = {
text: 'apple'
}
this.items.push(item)
... | 2020-10-24T17:17:04 | 2020-10-24T17:17:04 | {} | NONE |
vuejs | core | 716,380,576 | 2,474 | KaelWD | Ah yeah it's https://github.com/vuejs/vue/issues/8679 again, thanks. | 2020-10-26T08:01:32 | 2020-10-26T08:02:29 | {} | CONTRIBUTOR |
vuejs | core | 717,794,396 | 1,409 | icehaunter | @LinusBorg That is what I ended up doing. This approach, however, has a couple of drawbacks. Mainly - I cannot rely on `Suspense` to correctly display an application-wide loader while data required for the application is loading | 2020-10-28T09:01:10 | 2020-10-28T09:01:10 | {} | NONE |
vuejs | core | 717,815,423 | 1,409 | somodevo | @LinusBorg - Thanks I'll try that and see if/how I can decouple the Vue dependencies from the other initialisation logic. However, I wanted to do it in the Vue context because I wanted to use Suspense to show a loading screen in the meantime. That's why I think my case is related to this issue. | 2020-10-28T09:40:19 | 2020-10-28T09:40:19 | {} | NONE |
vuejs | core | 718,208,953 | 2,116 | LinusBorg | @yyx990803 I think we should keep the Vue 3 behavior as is. The Vue 2 behavior was out fo necessity. IU think with the old caveat out of the way, objects and arrays now behave the same - and both need a `deep: true` to have changes to their properties watched.
Artificially reverting to the Vue 2 behavior for arrays ... | 2020-10-28T21:06:36 | 2020-10-28T21:06:36 | {} | MEMBER |
vuejs | core | 718,301,437 | 2,493 | lixiaofa | Thank you for answering my questions | 2020-10-29T01:27:30 | 2020-10-29T01:27:30 | {} | NONE |
vuejs | core | 716,002,134 | 2,479 | unbyte | use `reactive`
https://codepen.io/unbyte/pen/xxOgQOE | 2020-10-24T17:06:26 | 2020-10-24T17:06:26 | {} | CONTRIBUTOR |
vuejs | core | 716,111,113 | 2,464 | d-corler | Works perfectly, thanks @pikax ! | 2020-10-25T08:24:01 | 2020-10-25T08:24:01 | {} | NONE |
vuejs | core | 716,335,024 | 2,474 | HcySunYang | Use arrow function instead, or explicitly add an annotation to `this`: `validator(this: void, val: string){ ... }` | 2020-10-26T06:29:42 | 2020-10-26T06:29:42 | {
"+1": 1,
"heart": 1,
"hooray": 4
} | MEMBER |
vuejs | core | 717,843,604 | 2,493 | LinusBorg | So thanks for being adamant here, I was wrong.
readonly on a plain value should of course not track. I usually use it on reactive values only and didn't think about it enough.
So the problem seems to be here:
https://github.com/vuejs/vue-next/blob/0e5a3c47a7398dfd0107fccf9b615772dd01aa74/packages/reactivity/sr... | 2020-10-28T10:32:45 | 2020-10-28T10:32:45 | {} | MEMBER |
vuejs | core | 715,558,535 | 2,476 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-23T19:52:09 | 2020-10-23T19:52:09 | {} | NONE |
vuejs | core | 716,189,303 | 2,484 | ScriptedAlchemy | You're not sharing vue
You need to share things that depend on a singleton, like vue - otherwise its loading two separate copies of vue | 2020-10-25T18:19:36 | 2020-10-25T18:19:36 | {} | NONE |
vuejs | core | 716,958,546 | 2,106 | skirtles-code | I've posted some suggestions to your forum post.
I'm not aware of anywhere that this is currently documented. It may well be something that is handled by the migration helper once that's available. | 2020-10-27T03:39:04 | 2020-10-27T03:39:04 | {} | CONTRIBUTOR |
vuejs | core | 717,821,372 | 2,505 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-28T09:51:23 | 2020-10-28T09:51:23 | {} | NONE |
vuejs | core | 717,834,771 | 2,493 | LinusBorg | Ah, *now* I get what you mean. I failed at reproducing it properly first with the snippet your provided.
Let's look into it, we might have an issue here. | 2020-10-28T10:16:14 | 2020-10-28T10:17:29 | {} | MEMBER |
vuejs | core | 718,108,828 | 2,508 | pmisiejuk | btw stackoverflow issue helped me https://stackoverflow.com/questions/64572235/is-possible-to-have-recurring-slots-in-vue | 2020-10-28T17:58:34 | 2020-10-28T17:58:34 | {} | NONE |
vuejs | core | 715,288,485 | 2,470 | posva | Thanks although I'm not sure there is much we can do here apart from manually patching the generated file and publishing a new patch.
A better fix would be to change the minifier behavior | 2020-10-23T11:37:25 | 2020-10-23T11:37:25 | {} | MEMBER |
vuejs | core | 717,816,285 | 1,409 | LinusBorg | @icehaunter I don't see why that would be the case? You're being a bit unspecific here, so I'm not sure how to answer. A real example would be helpful.
@somodevo same applies to you. | 2020-10-28T09:41:56 | 2020-10-28T09:42:28 | {
"+1": 2
} | MEMBER |
vuejs | core | 717,814,458 | 2,493 | LinusBorg | I'm still not sure what you are asking as your code doesn't contain any example of how different behaviour affects your use case.
However:
* in the first example, using `includes()` makes the whole array a dependency, as well as each index, as any index could be "a".
* in the second example, you access one speci... | 2020-10-28T09:38:23 | 2020-10-28T10:34:30 | {} | MEMBER |
vuejs | core | 717,856,431 | 2,493 | LinusBorg | Thanks for reporting, tracked it down and sent a PR.
Apologies for my initial stubborness. | 2020-10-28T10:58:48 | 2020-10-28T10:58:48 | {
"+1": 3
} | MEMBER |
vuejs | core | 718,033,888 | 2,508 | pmisiejuk | I found an workaround solution - detailsComponent passed as prop.
It's in updated repository.
I don't know why I needed to do it - version from first commit looks nicer.
But I'm also satisfied with actual.
I'm closing. Maybe there will be someone searching for 'recurring slot vue'.
Thank you | 2020-10-28T16:01:07 | 2020-10-28T16:01:07 | {} | NONE |
vuejs | core | 716,195,693 | 2,484 | yyx990803 | This is a webpack configuration question, not a Vue one. | 2020-10-25T19:05:43 | 2020-10-25T19:05:43 | {} | MEMBER |
vuejs | core | 717,816,905 | 1,409 | somodevo | Once I got it working or not I will share a fiddle/codesandbox. Thanks for taking the time 👍 | 2020-10-28T09:43:08 | 2020-10-28T09:43:08 | {} | NONE |
vuejs | core | 717,819,970 | 2,498 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.15 KB (0%) |
| runtime-dom.global.prod.js | 26.43 KB (0%) |
| size-check.global.prod.js | 15.95 KB (0%) | | 2020-10-28T09:48:46 | 2020-10-28T09:48:46 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.