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 | 1,207,421,468 | 6,420 | Waujito | >
> `toRef()` works as expected. The prop is possibly undefined, so the generated ref possibly contains and `undefined` value: `Ref<string | undefined>`. The propblem is only with `toRefs()`
>
I agree. But, I think, the main topic of this issue is that it is impossible to separate `Ref<string>` from `Ref<undefi... | 2022-08-07T14:31:20 | 2022-08-07T14:31:45 | {} | NONE |
vuejs | core | 1,207,479,140 | 6,420 | Waujito | Okey and thank you for your time | 2022-08-07T20:23:16 | 2022-08-07T20:26:27 | {} | NONE |
vuejs | core | 1,212,528,614 | 5,481 | pleek91 | I'm having a similar issue. According to the docs components can be recursive. But appears to be an issue when the recursion is circular. A -> B -> A vs A -> A -> A
https://vuejs.org/api/sfc-script-setup.html#recursive-components
Seems to build fine in my case. But VSCode shows lots of typescript problems. | 2022-08-11T21:46:48 | 2022-08-11T21:48:35 | {
"eyes": 1
} | NONE |
vuejs | core | 1,214,131,514 | 6,468 | JerryWu1234 | 
| 2022-08-13T10:06:11 | 2022-08-13T10:06:11 | {} | NONE |
vuejs | core | 1,214,146,599 | 6,469 | BobLuursema | > You are using application.id but in your application object there is no such property, maybe you should use application.pk
I know, read the "additional comments" in my post, the rabbit hole is a bit deeper ;-) | 2022-08-13T12:08:20 | 2022-08-13T12:10:15 | {} | NONE |
vuejs | core | 1,207,463,787 | 6,420 | Waujito | > @pikax you sure? I think what OP tries to do here would require casting or a new ref.
>
> They are checking for .value to not be nullish, but that will _not_ make the _existing_ `Ref<string | undefined>` ref into `Ref<string>`, as it could be set to undefined later again. Object ins TS can never change their origi... | 2022-08-07T18:43:55 | 2022-08-07T20:26:17 | {} | NONE |
vuejs | core | 1,208,105,064 | 5,513 | joshistoast | bump | 2022-08-08T13:07:00 | 2022-08-08T13:56:12 | {} | NONE |
vuejs | core | 1,210,429,035 | 6,437 | LinusBorg | To me this is expected behaviour. script setup makes all top-level variables available in the template. That would take precedence over this Options API data option.
Sidenote: Mixing the options API with script setup is **absolutely no recommended, and was not an intended use case that we had in mind or seriously te... | 2022-08-10T09:45:09 | 2022-08-10T09:46:29 | {} | MEMBER |
vuejs | core | 1,211,634,635 | 6,448 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a98109752d4ff569d838854a676d722669baa215 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-08-11T07:20:08 | 2022-08-11T07:20:08 | {} | NONE |
vuejs | core | 1,216,012,556 | 6,478 | kaitian996 | 我上传了一个最小可复现仓库，问题在App.vue中已记录
[地址在这里](https://github.com/suanzi-yi/vue_6478) | 2022-08-16T00:27:58 | 2022-08-16T00:28:21 | {} | NONE |
vuejs | core | 1,207,452,598 | 6,420 | LinusBorg | Yeah thats what i meant, basically. | 2022-08-07T17:36:53 | 2022-08-07T20:26:12 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,207,476,606 | 6,420 | LinusBorg | well, then create a computed property that returns the default string if the optional prop is undefined. that then will also always be a string. One way or another *you* have to deal with the fact that *your* prop can be undefined in *your* code.
Please use the discord community or the repo discussions to ask for fu... | 2022-08-07T20:08:28 | 2022-08-07T20:26:21 | {} | MEMBER |
vuejs | core | 1,208,648,338 | 6,427 | dtyler7 | This was previously reported as https://github.com/vuejs/core/issues/4780 but was closed as not a bug. | 2022-08-08T21:49:33 | 2022-08-08T21:49:33 | {} | NONE |
vuejs | core | 1,213,274,971 | 3,842 | RobyCigar | idk, this pug indentation thing works on webpack, but not with vite, so i should remove the indent manually, I wonder how webpack team solve this issue | 2022-08-12T16:04:50 | 2022-08-12T16:05:28 | {} | NONE |
vuejs | core | 1,214,732,625 | 6,448 | KaelWD | It already works at runtime, the types just need to be changed. `{}` would work for any object instead of having a special case just for String. | 2022-08-15T08:06:43 | 2022-08-15T08:06:43 | {} | CONTRIBUTOR |
vuejs | core | 1,216,479,946 | 4,294 | Shinigami92 | > I found some hack. Currently, it works for me. Just wrap imported type with `Omit`.
>
> ```
> <script setup lang="ts">
> import { Button as AButton, ButtonProps } from "ant-design-vue";
> interface Props extends Omit<ButtonProps, ""> {}
>
> const props = defineProps<Props>();
> </script>
>
> <templ... | 2022-08-16T10:58:54 | 2022-08-16T10:58:54 | {
"laugh": 2
} | CONTRIBUTOR |
vuejs | core | 1,213,837,791 | 6,466 | alamhubb | The text in slots.default()[0].children does not contain newlines
I want to get text that contains newlines, how do I manipulate $slots | 2022-08-13T06:38:34 | 2022-08-13T06:38:34 | {} | NONE |
vuejs | core | 1,207,425,133 | 6,421 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 43065b51032cf22c6cd4c9c274113a42ba561b9c |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-08-07T14:52:13 | 2022-08-07T14:52:13 | {} | NONE |
vuejs | core | 1,207,866,761 | 5,165 | KID-joker | The first `reload` didn't trigger the `onDeactivated`. | 2022-08-08T09:11:01 | 2022-08-08T09:11:01 | {} | NONE |
vuejs | core | 1,210,419,160 | 6,441 | LinusBorg | your likely undelying problem is that you don't annotate the computed property's return type, which is required when using Options API & TS.
https://vuejs.org/guide/typescript/options-api.html#typing-computed-properties
Can'T 100% verify as I can't run the reproduction right now, but I'm willing to bet that it's ... | 2022-08-10T09:37:08 | 2022-08-10T09:38:26 | {} | MEMBER |
vuejs | core | 1,214,146,307 | 6,469 | v1ctorw1ll1an | You are using application.id but in your application object there is no such property, maybe you should use application.pk
<br>
<br>
<img width="1423" alt="Screen Shot 2022-08-13 at 09 05 48" src="https://user-images.githubusercontent.com/47677499/184493320-9f7620fa-ab8c-423b-8f12-32aa58563711.png">
| 2022-08-13T12:06:04 | 2022-08-13T12:06:50 | {} | NONE |
vuejs | core | 1,214,150,886 | 6,468 | LinusBorg | your repo works fine nlon your vercel deployment and also when copied to the SFC playground. The screenshots shows an error from a component that can't be found in the provided reproduction. (HeaderTool.vue)
Can't reproduce the problem. | 2022-08-13T12:42:10 | 2022-08-14T08:03:10 | {} | MEMBER |
vuejs | core | 1,207,426,930 | 6,420 | Waujito | Ok thank you | 2022-08-07T15:02:45 | 2022-08-07T20:25:54 | {} | NONE |
vuejs | core | 1,207,452,482 | 6,420 | pikax | @LinusBorg I believe that's typescript type narrowing, it makes sense if you think about, because the `ref` **can** be undefined, even if you check if `.value` is `undefined` nothing prevents to be changed afterwards:
```ts
declare const r : Ref<string | undefined>
const refString = r.value ? r : ref(''); // the ... | 2022-08-07T17:35:51 | 2022-08-07T20:26:08 | {} | MEMBER |
vuejs | core | 1,207,947,648 | 6,205 | vilbergs | In case someone else runs into this, I noticed that I had some element refs that were wrapped in template strings ` `` `, which caused the same error. So making the following changes to my refs solved the problem:
```diff
- <div :ref="`annotationLayer`" />
+ <div ref="annotationLayer" />
```
For fun i tried pa... | 2022-08-08T10:31:10 | 2022-08-08T10:31:55 | {
"+1": 3
} | NONE |
vuejs | core | 1,210,439,919 | 6,441 | davidgiga1993 | > your likely undelying problem is that you don't annotate the computed property's return type, which is required when using Options API & TS.
>
> https://vuejs.org/guide/typescript/options-api.html#typing-computed-properties
>
> Can'T 100% verify as I can't run the reproduction right now, but I'm willing to bet ... | 2022-08-10T09:55:02 | 2022-08-10T09:55:21 | {} | NONE |
vuejs | core | 1,212,252,923 | 6,449 | deathlynocturnal | Nevermind, `timeout` doesn't work, tried with:
`<Suspense timeout="5000">`
and
`<Suspense :timeout="5000">` | 2022-08-11T17:01:51 | 2022-08-11T17:01:51 | {} | NONE |
vuejs | core | 1,212,786,129 | 6,453 | PYPARA | ```vue
<script setup>
// This starter template is using Vue 3 <script setup> SFCs
// Check out https://vuejs.org/api/sfc-script-setup.html#script-setup
import { ref, nextTick } from 'vue';
const alive = ref(true);
function reload() {
alive.value = false;
nextTick(() => {
alive.value = true;
});
}... | 2022-08-12T06:49:50 | 2022-08-12T06:49:50 | {} | NONE |
vuejs | core | 1,209,041,095 | 6,430 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 3270c686282204db799a9aecba32f7e83ba0b364 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-08-09T07:55:47 | 2022-08-13T03:27:32 | {} | NONE |
vuejs | core | 1,207,287,836 | 6,417 | LinusBorg | That's expected behavior.
> Note that if you destructure the props object, the destructured variables will lose reactivity. It is therefore recommended to always access props in the form of props.xxx.
https://vuejs.org/api/composition-api-setup.html#accessing-props
You can use toRef() to get a reactive single... | 2022-08-06T21:50:49 | 2022-08-06T21:50:49 | {} | MEMBER |
vuejs | core | 1,207,389,823 | 6,417 | LinusBorg | Hard to debug a screenshot. Would assume it's just a type level inconstency with toRefs and an optional prop.
You could open separate issue for this.
toRef() will not have this problem. | 2022-08-07T11:44:47 | 2022-08-07T11:44:47 | {} | MEMBER |
vuejs | core | 1,209,303,843 | 6,433 | tbh-nine | I experience the same issue in my app, even though the documentation clearly states that component emitted events do not bubble: https://vuejs.org/guide/components/events.html#emitting-and-listening-to-events.
Looks like a bug. | 2022-08-09T12:14:47 | 2022-08-09T12:15:20 | {} | NONE |
vuejs | core | 1,209,478,524 | 6,434 | mgsod | > 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 likely need to move the alert to an `onMounte... | 2022-08-09T14:46:44 | 2022-08-09T14:47:42 | {} | NONE |
vuejs | core | 1,210,164,799 | 6,437 | sunxi1997 | 
| 2022-08-10T05:05:53 | 2022-08-10T05:05:53 | {} | NONE |
vuejs | core | 1,211,459,963 | 6,442 | edison1105 | 
It will add a new text Node after press enter. Vue only patch **the focused text Node** when blur. That's why the textContent is incorrent. | 2022-08-11T01:21:44 | 2022-08-11T01:21:44 | {} | MEMBER |
vuejs | core | 1,211,633,458 | 6,448 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a98109752d4ff569d838854a676d722669baa215 |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-08-11T07:18:30 | 2022-08-11T07:18:30 | {} | NONE |
vuejs | core | 1,213,836,190 | 6,466 | alamhubb | 
| 2022-08-13T06:37:32 | 2022-08-13T06:37:32 | {} | NONE |
vuejs | core | 1,216,485,660 | 4,294 | vdseregin | > > I found some hack. Currently, it works for me. Just wrap imported type with `Omit`.
> > ```
> > <script setup lang="ts">
> > import { Button as AButton, ButtonProps } from "ant-design-vue";
> > interface Props extends Omit<ButtonProps, ""> {}
> >
> > const props = defineProps<Props>();
> > </script>
... | 2022-08-16T11:05:25 | 2022-08-16T11:05:25 | {} | NONE |
vuejs | core | 1,280,009,838 | 6,892 | LinusBorg | You are free to qrap thr return value of the computed in `readonly()`. By default, they are muatable. | 2022-10-16T17:02:53 | 2022-10-16T17:02:53 | {
"+1": 1,
"eyes": 1
} | MEMBER |
vuejs | core | 1,280,763,683 | 6,896 | zhangzhonghe | @davidfarah2003 You can use a div as the root element in the component.
[Example.](https://stackblitz.com/edit/vitejs-vite-vp8anr?file=src%2Fviews%2FGraphs.vue,src%2Fviews%2FAllData.vue) | 2022-10-17T12:14:44 | 2022-10-17T12:14:44 | {} | MEMBER |
vuejs | core | 1,281,741,008 | 6,902 | baiwusanyu-c | I didn't make any changes, why does this unit test sometimes fail to run and sometimes pass @yyx990803 😂
![image](https://user-images.githubusercontent.com/32354856/196323115-6f612f32-e6bb-4bf6-90ef-a101... | 2022-10-18T02:43:27 | 2022-10-18T02:57:46 | {} | MEMBER |
vuejs | core | 1,281,748,700 | 5,047 | chuanqiangTsang | same problem，Is there any solution? | 2022-10-18T02:58:08 | 2022-10-18T02:58:08 | {} | NONE |
vuejs | core | 1,285,625,556 | 6,918 | LinusBorg | In Vue 3, all event listeners passed to a component which are not declared in that component's `emits`, will be applied as native event listeners to the root element.
https://vuejs.org/guide/components/attrs.html#v-on-listener-inheritance
In Vue 2, you could create the same issue by adding the `.native`listener:
... | 2022-10-20T14:15:48 | 2022-10-20T14:22:06 | {} | MEMBER |
vuejs | core | 1,284,250,692 | 6,913 | zhangzhonghe | More simplified [reproduction](https://sfc.vuejs.org/#eNp9Uj1vwjAQ/SsnLwRBYlhTQKq6dEIdkLp4geRSguIP2U4Yovz3nk1CEZVYEt/d87t399yzd2OyrkWWs40rbG08OPSt2QlVS6Othx4sVjBAZbWEGUFn99KHlmbMZzwEgYnKQhVaOQ+qlbAN15P1/C2kifpQS9StT5I5bHcBkXXHpsXFYgnr1WoVcBt+U0IaKPAoTXP0SBHAJrbM6dpWMPoKBpwKG35HsSW7qUvl0WQXpxWN1oe7Yiw4wXKImZAjxSEW7Oy9cT... | 2022-10-19T16:06:35 | 2022-10-21T04:16:19 | {} | MEMBER |
vuejs | core | 1,287,668,610 | 4,605 | Rusinas | Any updades on this? :( | 2022-10-22T07:53:28 | 2022-10-22T07:53:38 | {} | NONE |
vuejs | core | 1,288,113,242 | 5,952 | BenjaminOddou | 👀 | 2022-10-23T13:27:00 | 2022-10-23T13:27:00 | {} | NONE |
vuejs | core | 1,290,035,788 | 6,943 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 36df192c2d0333a98113259fbbb215f7a783f931 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-10-25T06:11:37 | 2022-10-25T06:11:37 | {} | NONE |
vuejs | core | 1,278,853,328 | 6,883 | w1ndy | > Consider this example:
>
> ```ts
> const msg = $ref('test')
> $$([msg]) // It really should be `Ref<string>[]`
> ```
>
> Why escape a normal variable for you demo?
It's a common case in props destructuring:
```
const { msg } = defineProps<{ msg: string[] }>()
useSomeHook($$(msg)); // type check fails a... | 2022-10-14T11:01:14 | 2022-10-14T11:01:14 | {} | NONE |
vuejs | core | 1,279,778,242 | 6,863 | Rolanddoda | Interesting! I always go for creating a child component when I see repetition and while reading the problem I intuitively thought of solving it that way.
But having multiple templates in order to reuse them inside a SFC looks amazing. I am thinking that this way of doing it, wouldn't require a new instance to be cre... | 2022-10-15T16:29:47 | 2022-10-15T16:29:47 | {
"+1": 3
} | NONE |
vuejs | core | 1,279,821,910 | 6,865 | znck | What is use case of `v-if="true"`? | 2022-10-15T19:52:10 | 2022-10-15T19:52:10 | {} | MEMBER |
vuejs | core | 1,280,791,993 | 6,895 | AngryChocobo | @defaude So how can I skip this question? I am stucked. 😂 | 2022-10-17T12:37:30 | 2022-10-17T12:37:49 | {} | NONE |
vuejs | core | 1,283,433,084 | 2,015 | jd-solanki | I think we should have [vue-safe-teleport](https://github.com/Akryum/vue-safe-teleport) built-in.
[Johnson Chu](https://twitter.com/johnsoncodehk) tweet [reply](https://twitter.com/johnsoncodehk/status/1582347036598628354). | 2022-10-19T05:02:34 | 2022-10-19T05:02:39 | {
"+1": 1
} | NONE |
vuejs | core | 1,285,942,445 | 6,919 | sxzz | I don't think this change is necessary. I mean `maxConcurrency` is pretty useful. It may have better performance in some special cases, and I'm not sure. The PR requires other team members for reviewing. | 2022-10-20T18:01:44 | 2022-10-20T18:01:44 | {} | MEMBER |
vuejs | core | 1,286,562,253 | 6,899 | LinusBorg | Comment by sodatea in the PR: [15 hours ago](https://github.com/vuejs/core/pull/6855#issuecomment-1285844958)
> FYI the issue has been fixed in [@types/node v18.11.1+](https://github.com/DefinitelyTyped/DefinitelyTyped/pull/62782) so you don't have to wait for this PR to be merged to update your @types/node version. | 2022-10-21T07:21:27 | 2022-10-21T07:21:37 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,289,357,428 | 6,940 | ysy945 | This is because the order of 'props' compiled from' interfaces' in different orders is also different. If you put 'foo' on it, you will first process the 'foo' attribute and put it into 'props', and then process' bar'. At this time, 'foo' attribute can be read from 'props', so' true 'is displayed. If 'foo' is placed be... | 2022-10-24T17:26:52 | 2022-10-24T17:26:52 | {} | CONTRIBUTOR |
vuejs | core | 1,279,475,530 | 6,855 | johnsoncodehk | @acidjazz We may need cautious to check if the change leads to some regressions, so please be patient. :)
Downgrading `@types/node` to `18.8.0` for now is fine. | 2022-10-14T21:15:18 | 2022-10-14T21:15:18 | {
"+1": 11
} | MEMBER |
vuejs | core | 1,279,894,830 | 6,865 | SuzumiyaHaku | v-if="true" doesn't make sense in any real apps. But green hand, maybe will write such code during development， ignore is just to reduce one question. | 2022-10-16T05:21:42 | 2022-10-16T05:21:42 | {} | NONE |
vuejs | core | 1,280,843,939 | 2,907 | andoniabedul | > I'm having exactly this problem, but in the server side... Once createSSRApp(App, fetchedData) for each request, it 's keeping me in memory the fetchedData.
>
> App.js
>
> ```
> import { createSSRApp } from 'vue';
> import App from '../src/App.vue';
> import PageStore from '../src/store/Brands.js';
> import... | 2022-10-17T13:15:51 | 2022-10-17T13:15:51 | {} | NONE |
vuejs | core | 1,288,149,929 | 6,933 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 1a408b0fb5a8507e54eb725b8a551714cf29e29e |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-10-23T16:32:43 | 2022-10-23T16:32:43 | {} | NONE |
vuejs | core | 863,600,581 | 3,969 | tony19 | @posva Oh, I missed those PRs. However, they appear to be outdated, as they no longer compile. Plus, I believe they'll introduce a breaking change for users. I'll comment in a moment. | 2021-06-17T22:22:07 | 2022-10-23T18:47:03 | {} | CONTRIBUTOR |
vuejs | core | 1,280,802,139 | 6,895 | AngryChocobo | @LinusBorg Thanks. It works.
```html
<script lang="ts" setup>
defineProps<{ somePatch: string }>();
</script>
``` | 2022-10-17T12:45:19 | 2022-10-17T12:45:19 | {} | NONE |
vuejs | core | 1,281,029,403 | 6,899 | sxzz | Related PR #6855 | 2022-10-17T15:13:00 | 2022-10-17T15:13:00 | {} | MEMBER |
vuejs | core | 1,283,323,256 | 6,910 | alamhubb | I thought about it again, why there are different views on defineProps and defineEmits, because defineProps defines objects, while defineEmits defines strings, and strings are used when using them, although there are also intelligent prompts.
But I still think it would be better if you can directly provide emit and ... | 2022-10-19T02:39:46 | 2022-10-19T02:39:46 | {} | NONE |
vuejs | core | 1,283,649,719 | 6,909 | posva | Avoid manual dom manipulation, use `v-bind` as described in docs.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://chat.vuejs.org/) to ask questions! | 2022-10-19T08:46:52 | 2022-10-19T08:46:52 | {} | MEMBER |
vuejs | core | 1,285,930,779 | 4,552 | victorz | > I am running into a similar issue with custom css properties, I believe this is related.
>
> 
Also running into this problem. Can't declare/manipulate CSS variables with an attribute binding. | 2022-10-20T17:50:29 | 2022-10-20T17:50:29 | {} | NONE |
vuejs | core | 1,286,038,163 | 6,920 | LinusBorg | PRs welcome. Closing the issue though for passive-aggressive language. Not interested in interacting on that level. | 2022-10-20T19:30:37 | 2022-10-20T19:30:37 | {} | MEMBER |
vuejs | core | 1,278,938,691 | 6,884 | Evertt | Okay, my bad. I had made a mistake in the `<template>` which meant that the nextButton would never be shown anyway. Even then I still find it weird that it did not get recomputed, but maybe that's part of Vue's magic, that it won't recompute a value if it somehow "knows" that it wouldn't change the UI anyway.
As soo... | 2022-10-14T12:26:14 | 2022-10-14T12:26:14 | {} | NONE |
vuejs | core | 1,279,938,521 | 6,888 | LinusBorg | You are interfering yourself by using global query Selectors like `document.getElementById('uploadIcon')`, which will always match the first element found - the one in the first component. | 2022-10-16T10:14:53 | 2022-10-16T10:14:53 | {} | MEMBER |
vuejs | core | 1,280,751,681 | 6,895 | edison1105 | https://github.com/vuejs/core/blob/9617dd4b2abc07a5dc40de6e5b759e851b4d0da1/packages/runtime-dom/src/apiCustomElement.ts#L219
We should also check the `props` is not `undefined`
PR welcome. | 2022-10-17T12:05:01 | 2022-10-17T12:05:01 | {} | MEMBER |
vuejs | core | 1,283,607,532 | 6,910 | LinusBorg | In normal (non-script-setup) components you need to use the [`emits:` option](https://vuejs.org/api/options-state.html#emits) to declare which events will be emitted by the component.
This is important to that Vue can differentiate component event listeners from the parent from native event listeners, as the latter ... | 2022-10-19T08:13:34 | 2022-10-19T08:13:34 | {} | MEMBER |
vuejs | core | 1,286,539,909 | 6,919 | JayFate | > I don't think this change is necessary. I mean `maxConcurrency` is pretty useful. It may have better performance in some special cases, and I'm not sure. The PR requires other team members for reviewing.
I think `maxConcurrency` is unnecessary. I made build comparisons on 4 different computers(include windows, lin... | 2022-10-21T06:58:19 | 2022-10-21T06:58:19 | {} | CONTRIBUTOR |
vuejs | core | 1,287,121,406 | 6,260 | ml1nk | Same problem here on the current version 3.2.41. Is it related to #6347 and hopefully fixed with #6529?
| 2022-10-21T15:27:11 | 2022-10-21T15:27:11 | {
"+1": 5
} | NONE |
vuejs | core | 1,287,668,155 | 6,924 | LinusBorg | duplicate of #4605 | 2022-10-22T07:50:30 | 2022-10-22T07:50:30 | {
"confused": 1
} | MEMBER |
vuejs | core | 1,290,133,574 | 6,948 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 1d25db4b731f9192e25db3afa7ced32a70cc2d2b |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-10-25T07:48:05 | 2022-10-25T07:57:35 | {} | NONE |
vuejs | core | 1,290,230,686 | 6,222 | paul-xia | vue@3.2.41，same error:
| 2022-10-25T09:07:29 | 2022-10-25T09:07:29 | {} | NONE |
vuejs | core | 1,280,413,004 | 6,851 | oliverzy | OK, strictly speaking, it's an undocumented internal api change since 3.2.40.
Let's see how can we proceed with this. One of our internal component library relies on this behavior, currently we have to lock the vue version to 3.2.39 for quick fix. | 2022-10-17T07:30:12 | 2022-10-17T07:30:12 | {} | NONE |
vuejs | core | 1,282,366,003 | 5,401 | skirtles-code | I believe this was fixed in 3.2.38 via <https://github.com/vuejs/core/commit/0739f8909a0e56ae0fa760f233dfb8c113c9bde2>.
**Update:** Running the original reproduction against the latest Vue still shows the reported problem. However, I believe that's because `isCustomElement` is not set correctly, which is also why it... | 2022-10-18T13:12:58 | 2022-10-18T21:40:08 | {} | CONTRIBUTOR |
vuejs | core | 1,283,896,008 | 6,254 | lvjiaxuan | Still exist?
Should I close it? | 2022-10-19T11:57:59 | 2022-10-19T11:57:59 | {} | NONE |
vuejs | core | 1,285,678,727 | 6,919 | JayFate | > Could you please explain why did you make this PR and improve what? 🤔 I'm a bit confused.
The target of this PR is to simplify `scripts/build.js`, to make it more readable.
While, Artifacts of `scripts/build.js` of this PR is same to `origin/main` branch.
Time spent of build process doesn't change too.
*... | 2022-10-20T14:49:00 | 2022-10-20T14:49:00 | {} | CONTRIBUTOR |
vuejs | core | 1,288,097,091 | 4,609 | edison1105 | @Rusinas
We're working on this. please be patient. | 2022-10-23T12:04:53 | 2022-10-23T12:04:53 | {
"hooray": 2
} | MEMBER |
vuejs | core | 1,288,150,155 | 6,933 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 1a408b0fb5a8507e54eb725b8a551714cf29e29e |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-10-23T16:34:06 | 2022-10-23T16:34:06 | {} | NONE |
vuejs | core | 1,281,763,844 | 5,047 | chuanqiangTsang | fixed just now。
if you are using vite, set as follow:
resolve.dedupe: ['vue', 'locally-linked packages']
[https://github.com/vuejs/core/issues/5455](https://github.com/vuejs/core/issues/5455) | 2022-10-18T03:25:42 | 2022-10-18T03:25:42 | {} | NONE |
vuejs | core | 1,283,343,425 | 6,910 | alamhubb | I feel that defineEmits is more of a programming normative limitation. It is useful for complex components, but it is a bit redundant for simple components. If I have only a few lines of code in a component and only one emit, I need to declare it. It seems a bit redundant if you can only use it. If you provide an emit ... | 2022-10-19T03:00:48 | 2022-10-19T03:00:48 | {} | NONE |
vuejs | core | 1,283,360,599 | 6,910 | alamhubb | ```
const useEmit = defineEmits([])
export default function emit(event, ...args) {
useEmit(event, ...args)
}
``` | 2022-10-19T03:19:28 | 2022-10-19T03:19:28 | {} | NONE |
vuejs | core | 1,285,844,958 | 6,855 | haoqunjiang | FYI the issue has been fixed in `@types/node` v18.11.1+ https://github.com/DefinitelyTyped/DefinitelyTyped/pull/62782
so you don't have to wait for this PR to be merged to update your `@types/node` version. | 2022-10-20T16:32:11 | 2022-10-20T16:32:11 | {
"+1": 6
} | MEMBER |
vuejs | core | 1,286,541,347 | 6,919 | sxzz | /cc @antfu | 2022-10-21T07:00:00 | 2022-10-21T07:00:00 | {} | MEMBER |
vuejs | core | 1,272,443,597 | 3,969 | tony19 | @posva I agree, and the current code already allows that 😄 | 2022-10-09T03:12:05 | 2022-10-23T18:47:58 | {} | CONTRIBUTOR |
vuejs | core | 1,289,208,225 | 6,935 | posva | Please open a new issue with a valid reproduction using [the playground](https://sfc.vuejs.org/#eNo9j71uwzAMhF+F5eIWqCV0NZQA3foGXbikjpw40B9EOR0EvXspp8imu9N9OFb8TEndN4sTGp7zmgqwLVs6Ulh9irlAhWwXaLDk6GGQrwMFCnMMXMDzBQ49fx2+rHMRvmN255fhjYLRD5yARBTrkzsVKwrAXD+Ote7l1owWtbtrSFuB++jj2boDoeSEEhn9bOM7PlaN/pTUjWOQ3bW36T9gwgl2p3uy... | 2022-10-24T15:26:03 | 2022-10-24T15:26:03 | {} | MEMBER |
vuejs | core | 1,280,427,432 | 4,745 | serialine | vue2 fixed: v2.7.11
https://github.com/vuejs/vue/releases/tag/v2.7.11
https://github.com/vuejs/vue/commit/2f335b2f9d09b962f40e38740826d444e4fff073 | 2022-10-17T07:43:19 | 2022-10-17T07:45:21 | {
"hooray": 3
} | NONE |
vuejs | core | 1,282,530,122 | 5,584 | nicoszerman | This problem is happening to me too. I jumped into the source code and found that modifying the produced code like this fixes the problem:
_PRODUCED CODE_
`"onUpdate:modelValue": _cache[2] || (_cache[2] = ($event) => isRef(draftMessage) ? draftMessage.value = $event : null)`
_FIXED PRODUCED CODE_
`"onUpdate:mod... | 2022-10-18T14:56:47 | 2022-10-18T15:00:28 | {} | NONE |
vuejs | core | 1,283,769,182 | 4,942 | telion2 | I have a similar Issue.
@mmrpm the repro you provided doesn't work anymore (throws Errors)
@edison1105 This is a workaround inside of vuejs core, correct? => not a workaround that one can use in a normal Vue Project, correct?
| 2022-10-19T10:18:04 | 2022-10-19T10:18:50 | {} | NONE |
vuejs | core | 1,288,073,384 | 4,609 | Rusinas | @edison1105 any updates? This problem is stopping my work :( | 2022-10-23T10:04:38 | 2022-10-23T10:04:38 | {} | NONE |
vuejs | core | 1,288,125,280 | 6,855 | iBobik | @sodatea I have 18.11.3 but the error is there. | 2022-10-23T14:25:21 | 2022-10-23T14:25:21 | {} | NONE |
vuejs | core | 1,272,195,187 | 3,969 | tony19 | @antfu Done. Thanks! | 2022-10-08T01:58:14 | 2022-10-23T18:47:20 | {} | CONTRIBUTOR |
vuejs | core | 1,280,087,509 | 6,893 | fenilli | This is the same as #4294 | 2022-10-16T23:21:40 | 2022-10-16T23:21:40 | {} | NONE |
vuejs | core | 1,282,082,122 | 6,610 | stevenkuster | It would be great if this PR got some attention. It would fix a lot of issues for us. | 2022-10-18T09:21:04 | 2022-10-18T09:21:04 | {
"+1": 5
} | NONE |
vuejs | core | 1,290,051,135 | 6,944 | baiwusanyu-c | nice！ | 2022-10-25T06:33:24 | 2022-10-25T06:33:24 | {
"laugh": 1
} | MEMBER |
vuejs | core | 1,280,756,361 | 6,896 | edison1105 | close as duplicate. | 2022-10-17T12:08:47 | 2022-10-17T12:08:47 | {} | MEMBER |
vuejs | core | 1,284,467,476 | 5,401 | LinusBorg | Just checked this and yes, the changed mentioned by @skirtle addresses this issue, though only the related issues in the docs repo were mentjoned in the commit message as this one was already closed at that point.
So this issue is now solved. | 2022-10-19T19:20:43 | 2022-10-19T19:20:43 | {} | MEMBER |
vuejs | core | 1,279,383,480 | 6,879 | wellrus | not a bug
read about + workaround here https://github.com/vuejs/vue/issues/9200 | 2022-10-14T19:34:17 | 2022-10-14T19:34:51 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.