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,045,984,380 | 5,387 | pikax | > Is there any risk this might cause type errors in current usage in specific scenarios? In that case we might postpone this to 3.3.
The scenarios I can think of are if ppl are declaring wrong `refs`:
```ts
const comp = ref<ComponentPublicInstance | undefined>() // the correct type should have `null` too!
const d... | 2022-02-19T10:16:14 | 2022-02-19T10:16:14 | {} | MEMBER |
vuejs | core | 1,045,981,219 | 5,458 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: f06426333c2f0a1a3524acd9906dad7e2c859700
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/621216212e54bb0007637b87](https://app.netlify.com/sites/vue-sfc-playground/deploys/621216212e54bb0007637b87)
... | 2022-02-19T09:58:11 | 2022-02-20T10:24:05 | {} | NONE |
vuejs | core | 1,043,984,724 | 5,447 | LinusBorg | > [#1166 (comment)](https://github.com/vuejs/core/issues/1166#issuecomment-626859012)
That's no longer true. It is supported | 2022-02-18T06:24:44 | 2022-02-18T06:24:44 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,044,030,316 | 5,449 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: cef81241239c0befcf3b65f95cd9db8f2ef5b04c
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620f585068ece40008337d48](https://app.netlify.com/sites/vuejs-coverage/deploys/620f585068ece40008337d48)
😎 Browse th... | 2022-02-18T07:02:38 | 2022-02-18T08:32:21 | {} | NONE |
vuejs | core | 1,045,970,167 | 5,118 | ygj6 | ~Look at this example:[vue-sfc-playground](https://deploy-preview-5118--vue-sfc-playground.netlify.app/#eyJBcHAudnVlIjoiPHNjcmlwdCA+XG4gIGltcG9ydCB7IHJlZiwgb25Nb3VudGVkIH0gZnJvbSAndnVlJ1xuICBcbiAgZXhwb3J0IGRlZmF1bHQge1xuICAgIHNldHVwKCl7XG4gICAgICBjb25zdCBsaXN0ID0gcmVmKFsxLCAyLCAzXSlcbiAgICAgIGxldCBpdGVtUmVmcyA9IHJlZihu... | 2022-02-19T08:49:29 | 2022-02-19T09:18:45 | {} | MEMBER |
vuejs | core | 1,045,983,447 | 5,387 | LinusBorg | Hey @pikax,
This is looking good!
Is there any risk this might cause type errors in current usage in specific scenarios? In that case we might postpone this to 3.3.
If it's fully backwardds-compatible, we an merge it in a patch. I'd assume it is, since people were forced to typecast previously anyways, right? | 2022-02-19T10:10:32 | 2022-02-19T10:10:32 | {} | MEMBER |
vuejs | core | 1,046,175,080 | 5,456 | Hongbusi | The code in the SFC playground is just a simple implementation.
The real find is in this place [https://github.com/Hongbusi/vue-element-admin/blob/master/src/views/login/components/login-panel.vue#L40](https://github.com/Hongbusi/vue-element-admin/blob/master/src/views/login/components/login-panel.vue#L40). @posva
... | 2022-02-20T06:49:49 | 2022-02-20T06:49:49 | {} | NONE |
vuejs | core | 1,046,181,654 | 5,456 | Hongbusi | When I click on the button, the output is this. And I can't access the methods defined inside the childComponent properly.
Is there something wrong with the way I'm using it? [See it here](https://sfc.v... | 2022-02-20T07:42:51 | 2022-02-20T07:42:51 | {} | NONE |
vuejs | core | 1,041,280,859 | 4,662 | claudiomedina | > As a workaround I've created component, which tracks Mutation in `document.head ` and inline style tags (must includes comment `/* VueCustomElementChildren */`) into shadow dom in dev mode, for production it inlines link for stylesheets:
@dezmound, wont that make other Vue custom elements' styles get injected into... | 2022-02-16T09:22:14 | 2022-02-16T09:22:14 | {} | NONE |
vuejs | core | 1,035,111,128 | 5,400 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 01c669470afa1ba02b9d61dc6560ce53a4e2e19f
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620e114bb274ec0007029a76](https://app.netlify.com/sites/vuejs-coverage/deploys/620e114bb274ec0007029a76)
😎 Browse th... | 2022-02-10T16:14:38 | 2022-02-17T09:17:33 | {} | NONE |
vuejs | core | 1,043,348,111 | 5,446 | LinusBorg | It's by design, in my view.
The scoped data property is only inherited onto single root nodes because the intended use case is to add layout styles for that root node.
That doesn't make too much sense for a multi-root component.l, and could in fact have unintended side effects when the number of root nodes change... | 2022-02-17T19:40:35 | 2022-02-17T19:40:35 | {} | MEMBER |
vuejs | core | 1,042,811,846 | 5,445 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 1801f74b3cedf2f99a27fc21b106e6b264f25121
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/620f0318cd4ece0007927485](https://app.netlify.com/sites/vue-sfc-playground/deploys/620f0318cd4ece0007927485)
... | 2022-02-17T10:44:28 | 2022-02-18T02:25:45 | {} | NONE |
vuejs | core | 1,044,158,667 | 5,451 | neoech | thank you,i got it | 2022-02-18T08:50:05 | 2022-02-18T08:50:05 | {} | NONE |
vuejs | core | 1,044,932,443 | 5,118 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 6305830542a9d9f58419d610bed3f70dde3df5a8
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/620fdedb0e828000084c248d](https://app.netlify.com/sites/vue-sfc-playground/deploys/620fdedb0e828000084c248d)
... | 2022-02-18T18:01:05 | 2022-02-18T18:04:51 | {} | NONE |
vuejs | core | 1,045,981,443 | 5,458 | LinusBorg | @pikax could you have a look at this? Also, any idea where to test this? I didn't find any other test-dts tests for these compiler-helpers like createBlock() so not sure where to put them/how to do them. | 2022-02-19T09:59:38 | 2022-02-19T09:59:38 | {} | MEMBER |
vuejs | core | 1,045,985,102 | 5,458 | pikax | > @pikax could you have a look at this? Also, any idea where to test this? I didn't find any other test-dts tests for these compiler-helpers like createBlock() so not sure where to put them/how to do them.
It looks good to me, we usually don't have test for internal stuff, since the `createBlock` would be generated ... | 2022-02-19T10:21:00 | 2022-02-19T10:21:00 | {} | MEMBER |
vuejs | core | 1,046,202,453 | 5,393 | NickBelhomme | @nborko how could you work around the problem with
`const emit: Emits = rawEmit`
as that still needs the Emits type which does not exist...
Thanks in advance. | 2022-02-20T10:00:45 | 2022-02-20T10:00:45 | {} | NONE |
vuejs | core | 1,044,063,455 | 5,449 | ygj6 | > suggestion: replace commit message with: "ensure v-for works with template refs in script setup during dev"
>
> That makes for a more descriptive entry in the changelog later.
:smiley: Okay, I will add some testcases later. | 2022-02-18T07:35:00 | 2022-02-18T07:35:00 | {} | MEMBER |
vuejs | core | 1,044,673,900 | 5,453 | Rolanddoda | @LinusBorg thanks for taking the time to look at this.
First, I don't know why you are complicating stuff by putting `components` option and Options API. Also, your code doesn't make sense. How can you put `ref` in the `components`?
```js
export default {
components: {
qRadio: ref('')
}
}
```
As ... | 2022-02-18T15:08:31 | 2022-02-18T15:08:31 | {} | NONE |
vuejs | core | 1,044,945,301 | 5,455 | arpowers | Thanks, I didn't know about the Vite "dedupe" option (although it still
wont work for me since we are using ES builds)...
I would still recommend an improvement to the error message; as these types
of issues are tough to debug.
On Fri, Feb 18, 2022 at 10:50 AM Thorsten Lünborg ***@***.***>
wrote:
> Closed #5455 <htt... | 2022-02-18T18:09:16 | 2022-02-18T18:09:16 | {} | NONE |
vuejs | core | 1,044,987,437 | 5,453 | lidlanca | its not rare, you just need to be aware, that when you use `<script setup>`
you get all the magic that comes with it.
if you want to use confusing names for components and variables, you can do that
just make sure they are not case conflicting when vue try to resolve them.
This will not conflict
```js
con... | 2022-02-18T18:39:55 | 2022-02-18T18:39:55 | {} | CONTRIBUTOR |
vuejs | core | 1,041,206,880 | 5,401 | rictic | Sent over a docs PR, but if there's an ergonomic to support arbitrary event names, we could instead update the custom-elements-everywhere test for this feature: https://github.com/webcomponents/custom-elements-everywhere/blob/221ea4744373f34112331949c0d85d4b45e41d69/libraries/vue/src/components.js#L157-L163 | 2022-02-16T07:48:45 | 2022-02-16T07:48:45 | {} | NONE |
vuejs | core | 1,042,663,732 | 5,184 | WangQingye | I have the same issue, only in production env, cant find the reason | 2022-02-17T07:51:24 | 2022-02-17T07:51:24 | {
"+1": 5
} | NONE |
vuejs | core | 1,045,976,776 | 5,457 | LinusBorg | `<template>` elements with `v-if`on them are not rendered as actual elements, they serve as virtual wrappers to use a one `v-if` on a group of elements.
Since they are not rendered as elements, you can't use directives on them. | 2022-02-19T09:28:58 | 2022-02-19T09:28:58 | {} | MEMBER |
vuejs | core | 1,042,610,099 | 5,440 | caozhong1996 | Duplicate of #5218， see [RFC](https://github.com/vuejs/rfcs/discussions/430) | 2022-02-17T06:14:54 | 2022-02-17T06:14:54 | {} | CONTRIBUTOR |
vuejs | core | 1,042,903,334 | 5,441 | LinusBorg | > React also supports the use of self-closing tags in dom templates
To the best of my knowledge, React doesn't support any kind of templates (only JSX), so I don'T know what you refer to here.
Try adding a self-closing tag to an HTML document and open it in a browser, then check devtools. it will be turned into ... | 2022-02-17T12:33:20 | 2022-02-17T12:33:20 | {} | MEMBER |
vuejs | core | 1,044,030,297 | 5,449 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: cef81241239c0befcf3b65f95cd9db8f2ef5b04c
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/620f5850ac06560007e4dafb](https://app.netlify.com/sites/vue-sfc-playground/deploys/620f5850ac06560007e4dafb)
... | 2022-02-18T07:02:37 | 2022-02-18T08:29:09 | {} | NONE |
vuejs | core | 1,044,914,036 | 5,455 | LinusBorg | This sounds more like the common identity hazard arising when linking a package locally.
Vue relies on singletons in a couple of places, like the effects scheduler, so this is not really limited to SSR.
The proper solution is to make sure in your build tooling that all imports of Vue point to a single physical pa... | 2022-02-18T17:50:21 | 2022-02-18T17:50:21 | {} | MEMBER |
vuejs | core | 1,043,971,358 | 5,447 | ygj6 | ~~https://github.com/vuejs/core/issues/1166#issuecomment-626859012~~ | 2022-02-18T06:10:03 | 2022-02-19T01:45:42 | {} | MEMBER |
vuejs | core | 1,046,027,981 | 5,446 | Rolanddoda | @LinusBorg from the comments is a bit unclear if you answered or understood this issue with multi-root components so I am going to give it a try to ask again because in my view this is a bug.
### Component with multi-root nodes cannot be styled from parent with `:deep()` selector
[See the demo on Stackblitz](http... | 2022-02-19T14:21:13 | 2022-02-19T14:21:13 | {
"+1": 1
} | NONE |
vuejs | core | 1,046,186,452 | 5,456 | Hongbusi | When a method exists in a child component, it is not accessible via ref in the parent component.
Child component:
``` js
<script setup>
const action = () => {
console.log('action')
}
</script>
```
Parent component:
``` js
<script setup>
const handleClick = () => {
componentRef.value.action() // err... | 2022-02-20T08:20:44 | 2022-02-20T08:20:44 | {} | NONE |
vuejs | core | 1,044,418,115 | 5,453 | LinusBorg | This is working as intended. in script setup, you no longer need to register a component explicitly, rather you can just us a component that you imported - or created in place - by adding an element of the same name as the variable to the template.
And similarly to how "normal" script works, this is expected to over... | 2022-02-18T12:04:10 | 2022-02-18T12:04:48 | {} | MEMBER |
vuejs | core | 1,044,950,788 | 5,118 | lidlanca | also fixes: #5447
[sfc playground preview #5447 repro](https://deploy-preview-5118--vue-sfc-playground.netlify.app/#eyJBcHAudnVlIjoiPHNjcmlwdCA+XG4gIGltcG9ydCB7IHJlZiwgb25Nb3VudGVkIH0gZnJvbSAndnVlJ1xuICBcbiAgZXhwb3J0IGRlZmF1bHQge1xuICAgIHNldHVwKCl7XG4gICAgICBjb25zdCBsaXN0ID0gcmVmKFsxLCAyLCAzXSlcbiAgICAgIGxldCBpdGVtU... | 2022-02-18T18:12:56 | 2022-02-18T18:55:54 | {} | CONTRIBUTOR |
vuejs | core | 1,046,023,555 | 5,459 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 90d2ddd608b9195b908222cf4ae02df20884fe5d
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/621102bd295abc0008fe6b5d](https://app.netlify.com/sites/vue-sfc-playground/deploys/621102bd295abc0008fe6b5d)
... | 2022-02-19T13:55:57 | 2022-02-19T14:49:05 | {} | NONE |
vuejs | core | 1,041,201,050 | 5,401 | LinusBorg | Sure, PRs are welcome.
However, consider that we don't prevent you from listening to this event - you can add the event listener with a small custom directive, as mentioned - it's just not supported via `v-on` as it collides with Vue's own event name semantics. | 2022-02-16T07:41:33 | 2022-02-16T07:43:30 | {} | MEMBER |
vuejs | core | 1,044,742,440 | 5,390 | LinusBorg | You can try mounting to body, if that helps. But likely not a good idea as it will replace the content
I can accept that you can't understand it but that's what it is. | 2022-02-18T15:55:15 | 2022-02-18T15:55:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,045,126,240 | 2,855 | LinusBorg | Also indicated by the fact that the issue is still open, yes. | 2022-02-18T20:17:44 | 2022-02-18T20:17:44 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,046,197,624 | 5,456 | lidlanca | https://vuejs.org/api/sfc-script-setup.html#defineexpose | 2022-02-20T09:27:31 | 2022-02-20T09:27:31 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,088,347,914 | 5,667 | lloydjatkinson | Accidentally opened twice please look at #5666 | 2022-04-05T07:16:15 | 2022-04-05T07:16:15 | {} | NONE |
vuejs | core | 1,088,372,682 | 5,575 | posva | @qq15725 do you have a failing test case so we can add it? | 2022-04-05T07:45:51 | 2022-04-05T07:45:51 | {} | MEMBER |
vuejs | core | 1,090,234,751 | 5,672 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 98f5750f5798c388501376d7b366b863f0c37dac |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-06T12:53:51 | 2022-04-06T12:54:36 | {} | NONE |
vuejs | core | 1,090,319,335 | 5,657 | javastation | > @javastation When remove the outer div, the error seems gone [sfc playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICAgIDxkaXYgY2xhc3M9XCJwLTVcIj5cbiAgICAgIDxpbnB1dCB2LW1vZGVsPVwidG9nZ2xlXCIgdHlwZT1cImNoZWNrYm94XCIgLz5cbiAgICAgIDxkaXYgdi1pZj1cIiF0b2dnbGVcIj5lcnJvcjwvZGl2PlxuICAgICAgPG0tdGFibGUgdi1pZ... | 2022-04-06T14:10:39 | 2022-04-06T14:10:39 | {} | CONTRIBUTOR |
vuejs | core | 1,092,117,719 | 1,005 | softwareCobbler | Hello, I think this error message could be improved to also say something like "you may not have intended to have this listener fallthrough; consider `inheritAttrs: false`" | 2022-04-07T19:23:52 | 2022-04-07T19:23:52 | {} | NONE |
vuejs | core | 1,092,336,947 | 5,683 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 5900f1055e2d951b02a1f4c1baf29c8f8ffb834d |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-08T00:57:12 | 2022-04-08T00:57:55 | {} | NONE |
vuejs | core | 1,092,336,950 | 5,683 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 5900f1055e2d951b02a1f4c1baf29c8f8ffb834d |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-08T00:57:12 | 2022-04-08T01:02:18 | {} | NONE |
vuejs | core | 1,092,533,809 | 5,679 | LinusBorg | Thanks for checking this PR! :)
> But what about unmounted components handling events?
That should not be an issue as child components are unmounted *before* the parent.
> Shouldn't event listeners be removed between the beforeUnmount and unmounted lifecycle phases?
Event listeners are part of the vnode p... | 2022-04-08T07:21:07 | 2022-04-08T08:51:20 | {} | MEMBER |
vuejs | core | 1,088,461,987 | 5,669 | posva | See https://github.com/vuejs/core/pull/5575#issuecomment-1088461788 | 2022-04-05T09:12:27 | 2022-04-05T09:12:27 | {} | MEMBER |
vuejs | core | 1,088,593,897 | 5,668 | Mister-Hope | Anyway, I found this useful, may help others if you are building a "middleware“ which do not have access to app, nor can not control component registing.
```ts
import { camelize, getCurrentInstance } from "vue";
export const isComponentRegistered = (name: string): boolean => {
const instance = getCurrentInsta... | 2022-04-05T11:33:03 | 2022-04-05T11:33:03 | {
"+1": 1
} | NONE |
vuejs | core | 1,089,969,877 | 5,670 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 83b463b83300ad4fbc013cdbdf3f0e11e8314628 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-06T08:08:38 | 2022-04-06T08:09:22 | {} | NONE |
vuejs | core | 1,091,164,125 | 5,678 | LinusBorg | duplicate #5673 | 2022-04-07T07:16:44 | 2022-04-07T07:16:44 | {} | MEMBER |
vuejs | core | 1,091,623,193 | 5,673 | AimForNaN | @posva The [documentation](https://vuejs.org/api/sfc-script-setup.html#usage-alongside-normal-script) says it is possible to mix both APIs within the same component. | 2022-04-07T11:31:19 | 2022-04-07T11:31:19 | {} | NONE |
vuejs | core | 1,087,484,888 | 5,663 | LinusBorg | The examples rely on dynamic imports - not supported by your build target. (we won't make those examples compatible with older browsers, we expect developers to have access to an evergreen browser to read the docs).
But that only applies to the examples on the docs website. Vue core itself does *not* rely on those A... | 2022-04-04T12:19:15 | 2022-04-04T13:02:12 | {} | MEMBER |
vuejs | core | 1,087,782,904 | 5,575 | qq15725 | Maybe it would be better to just change these two positions.
```ts
constructor(detached = false) {
// 👇🏻 this line
this.parent = activeEffectScope
if (!detached && activeEffectScope) {
this.index =
(activeEffectScope.scopes || (activeEffectScope.scopes = [])).push(
this... | 2022-04-04T16:46:31 | 2022-04-04T16:46:31 | {} | NONE |
vuejs | core | 1,090,013,443 | 5,657 | kikyous | @javastation When remove the outer div, the error seems gone [sfc playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICAgIDxkaXYgY2xhc3M9XCJwLTVcIj5cbiAgICAgIDxpbnB1dCB2LW1vZGVsPVwidG9nZ2xlXCIgdHlwZT1cImNoZWNrYm94XCIgLz5cbiAgICAgIDxkaXYgdi1pZj1cIiF0b2dnbGVcIj5lcnJvcjwvZGl2PlxuICAgICAgPG0tdGFibGUgdi1pZ... | 2022-04-06T08:46:23 | 2022-04-06T08:46:23 | {} | NONE |
vuejs | core | 1,091,132,517 | 5,679 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ca327e035eccc1f4ef100bc0cf5173c5ec18897e |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-07T06:34:54 | 2022-04-07T06:37:00 | {} | NONE |
vuejs | core | 1,091,430,702 | 5,657 | kikyous | @javastation I don't understand why add a outer div will cause this error. | 2022-04-07T09:36:09 | 2022-04-07T09:36:09 | {} | NONE |
vuejs | core | 1,092,330,680 | 5,678 | AimForNaN | @LinusBorg After much experimentation, I managed to find out the real source of the problem. There was nothing wrong with the UMD build. What was happening was Vite does not seem to be able to handle imports whose folders contain their own `node_modules` folder. In other words, say I have the following directory struct... | 2022-04-08T00:42:10 | 2022-04-08T00:44:36 | {
"heart": 1
} | NONE |
vuejs | core | 1,092,374,278 | 5,661 | sallen450 | * https://github.com/vuejs/core/issues/5317
* https://github.com/vuejs/core/issues/1235 | 2022-04-08T02:13:46 | 2022-04-08T02:16:05 | {} | NONE |
vuejs | core | 1,092,467,258 | 5,678 | LinusBorg | Sounds pretty much like another perspective on the issue I described: there's a second node_modules with a second "vue" package that gets included.
happ you found your solution. | 2022-04-08T05:55:16 | 2022-04-08T05:55:16 | {} | MEMBER |
vuejs | core | 1,092,846,596 | 5,687 | hcg1023 | @LinusBorg Ok, looking forward to your reply, I will do this based on your reply | 2022-04-08T13:13:48 | 2022-04-08T13:13:48 | {} | CONTRIBUTOR |
vuejs | core | 1,088,235,056 | 5,108 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 60e88fa934787357855dae3f04d3d892a7cd3f18 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-05T03:41:38 | 2022-04-05T03:46:42 | {} | NONE |
vuejs | core | 1,088,448,035 | 5,669 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a901c60a1ee61fae820e78e76d04a6f545090345 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-05T08:59:39 | 2022-04-05T09:05:26 | {} | NONE |
vuejs | core | 1,089,969,939 | 5,670 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 83b463b83300ad4fbc013cdbdf3f0e11e8314628 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-06T08:08:43 | 2022-04-06T08:13:48 | {} | NONE |
vuejs | core | 1,091,420,916 | 5,661 | posva | You cannot mount an app within an app, use a component instead or make sure you manually add an element that [isn't handled by Vue](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IGNyZWF0ZUFwcCwgcmVmLCBjb21wdXRlZCwgaCwgb25Nb3VudGVkLCBzaGFsbG93UmVmIH0gZnJvbSBcInZ1ZVwiO1xuaW1wb3J0IEZyYWdtZW50Q2hpb... | 2022-04-07T09:27:20 | 2022-04-07T09:27:20 | {} | MEMBER |
vuejs | core | 1,091,457,641 | 5,640 | edison1105 | @LeslieZhang 你先别用模板字符串，应该是没问题的。有空了我查一下原因。 | 2022-04-07T09:56:45 | 2022-04-07T09:56:45 | {} | MEMBER |
vuejs | core | 1,091,637,117 | 5,677 | LinusBorg | Duplicate: #5280, solved after #5281 is merged and published | 2022-04-07T11:46:37 | 2022-04-07T13:54:37 | {} | MEMBER |
vuejs | core | 1,092,681,868 | 5,686 | LinusBorg | providing the template ref from the parent to the slot as a slot prop would be another alternative.
Further support can be provided by the community on chat.vuejs.org | 2022-04-08T09:48:34 | 2022-04-08T09:48:34 | {} | MEMBER |
vuejs | core | 1,087,142,137 | 5,662 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | e66e4d26afc19696b02be93dae1e8629e3b8a1e9 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-04T05:49:45 | 2022-04-04T05:54:19 | {} | NONE |
vuejs | core | 1,087,652,733 | 5,665 | LinusBorg | duplicate of #5651 | 2022-04-04T14:48:31 | 2022-04-04T14:48:31 | {} | MEMBER |
vuejs | core | 1,091,114,936 | 5,678 | LinusBorg | That's not related to the UMD Build.
It's currently not supported to access state that was defined in `script setup` in Options API at runtime, because the render function gets inlined into the generated setup function and is returned from it - there's no returned state for options API to access:
```js
export de... | 2022-04-07T06:06:20 | 2022-04-07T06:06:20 | {} | MEMBER |
vuejs | core | 1,091,393,541 | 5,676 | posva | Duplicate of https://github.com/vuejs/core/issues/5640 | 2022-04-07T09:12:12 | 2022-04-07T09:12:12 | {} | MEMBER |
vuejs | core | 1,091,743,076 | 5,661 | sallen450 | @posva Thanks for your reply. I know it is the best practice not to mount an app within an app. Maybe the sfc [reproduction link](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IGNyZWF0ZUFwcCwgcmVmLCBjb21wdXRlZCwgaCwgb25Nb3VudGVkIH0gZnJvbSBcInZ1ZVwiO1xuaW1wb3J0IEZyYWdtZW50Q2hpbGQgZnJvbSAnLi9GcmF... | 2022-04-07T13:31:55 | 2022-04-07T13:59:47 | {} | NONE |
vuejs | core | 1,091,819,310 | 5,679 | bbotto-pdga | Apologies if I am misunderstanding this change, @LinusBorg, but at a glance it doesn't look like it entirely fixes the problem I reported. It looks like this prevents a component from emitting events after it's been unmounted. But what about unmounted components _handling_ events? Shouldn't event listeners be remove... | 2022-04-07T14:35:32 | 2022-04-07T14:35:32 | {} | NONE |
vuejs | core | 1,092,467,692 | 5,678 | LinusBorg | Tip: https://vitejs.dev/config/#resolve-dedupe could also help. | 2022-04-08T05:56:16 | 2022-04-08T05:56:16 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,087,208,282 | 5,661 | sallen450 | ## Demo with x6 library:
### Reproduction link
https://stackblitz.com/edit/vitejs-vite-nghwu9?file=README.md
### Steps to reproduce
1. click the button
### What is expected?
Remove all the two custom nodes
### What is actually happening?
Only remove one node | 2022-04-04T07:25:21 | 2022-04-04T07:32:40 | {} | NONE |
vuejs | core | 1,087,799,020 | 4,294 | Codebreaker101 | Just in case anyone needs @LinusBorg example without `type-fest` lib:
``` ts
import { ExtractPropTypes, ExtractDefaultPropTypes } from 'vue';
type Omit<T, K> = Pick<T, Exclude<keyof T, K>>;
type PartialBy<T, K> = Omit<T, K> & Partial<T>;
type Writeable<T> = { -readonly [P in keyof T]: T[P] };
export type Ty... | 2022-04-04T17:04:02 | 2022-04-04T17:04:02 | {
"+1": 3
} | NONE |
vuejs | core | 1,088,448,024 | 5,669 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a901c60a1ee61fae820e78e76d04a6f545090345 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-05T08:59:38 | 2022-04-05T09:00:24 | {} | NONE |
vuejs | core | 1,088,461,788 | 5,575 | posva | Thanks. You don't call `off` on an effectScope, you call `stop()` (https://vuejs.org/api/reactivity-advanced.html#effectscope) so that will never happen in a real scenario. | 2022-04-05T09:12:16 | 2022-04-05T09:12:16 | {} | MEMBER |
vuejs | core | 1,091,488,952 | 5,673 | Bodokh | Then why does this work on dev and not build... Sounds like a bug to me but ok. | 2022-04-07T10:10:48 | 2022-04-07T10:10:48 | {
"+1": 2
} | NONE |
vuejs | core | 1,092,864,385 | 5,687 | hcg1023 | 
I saw this in the documentation and felt like it didn't work when it was precompiled | 2022-04-08T13:32:04 | 2022-04-08T13:32:04 | {} | CONTRIBUTOR |
vuejs | core | 1,092,938,910 | 5,685 | posva | Duplicate of https://github.com/vuejs/core/issues/994 | 2022-04-08T14:45:31 | 2022-04-08T14:45:31 | {} | MEMBER |
vuejs | core | 1,087,773,723 | 5,575 | qq15725 | `off()` is the same problem. | 2022-04-04T16:36:11 | 2022-04-04T16:36:11 | {} | NONE |
vuejs | core | 1,088,466,572 | 5,668 | posva | You can implement `getApp()` in userland with the inject/provide api:
```ts
app.provide('app', app)
function getApp() {
return inject('app')
}
```
Then you can call `app.component('ComponentName')`.
If you are registering global components, you usually already have access to the app since you need to ... | 2022-04-05T09:16:58 | 2022-04-05T09:16:58 | {} | MEMBER |
vuejs | core | 1,090,970,890 | 5,268 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 2615a4633d098d36417b41dd66b7f91fc2ec6000 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-07T00:57:10 | 2022-04-07T01:12:48 | {} | NONE |
vuejs | core | 1,092,931,169 | 5,688 | posva | While this feature could be added, I don't think it makes sense to have a `v-bind()` in an external CSS as the origin of the variable would be confusing and implicit. | 2022-04-08T14:37:06 | 2022-04-08T14:37:06 | {} | MEMBER |
vuejs | core | 1,089,972,854 | 5,657 | javastation | the error of slot function execution affects block tracking,as a workaround,add `setBlockTracking(1)` in catch. | 2022-04-06T08:11:13 | 2022-04-06T08:11:13 | {} | CONTRIBUTOR |
vuejs | core | 1,090,097,399 | 5,671 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 1dcfd06bd442fe987968a51c9ef106a5984d9956 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-06T10:14:34 | 2022-04-06T10:15:14 | {} | NONE |
vuejs | core | 1,090,234,784 | 5,672 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 98f5750f5798c388501376d7b366b863f0c37dac |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-06T12:53:54 | 2022-04-06T12:56:29 | {} | NONE |
vuejs | core | 1,090,234,752 | 5,672 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 98f5750f5798c388501376d7b366b863f0c37dac |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-06T12:53:51 | 2022-04-06T13:00:25 | {} | NONE |
vuejs | core | 1,091,663,846 | 5,678 | LinusBorg | I got the same error on my local machine (about defineComponent).
The line you point to is independent of the kind of build format, but:
What this rather sounds like is that you bundled Vue into this UMD build.
Which will break your app, that uses its own copy of Vue, and lead to things like `getCurrentInstance()` b... | 2022-04-07T12:17:33 | 2022-04-07T12:20:20 | {} | MEMBER |
vuejs | core | 1,091,881,821 | 5,661 | posva | You are not supposed to manually manipulate the HTML that is handled by Vue either. You just need to move the html clear after the unmount [like this](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IGNyZWF0ZUFwcCwgcmVmLCBjb21wdXRlZCwgaCwgb25Nb3VudGVkLCBzaGFsbG93UmVmIH0gZnJvbSBcInZ1ZVwiO1xuaW1wb3... | 2022-04-07T15:30:14 | 2022-04-07T15:30:14 | {} | MEMBER |
vuejs | core | 1,092,701,903 | 5,687 | hcg1023 | I wish I could fix this, but I found several places to fix this, such as patchProp,patchDOMProp, or VueElement's _resolveDef method, and I need a good suggestion | 2022-04-08T10:12:03 | 2022-04-08T10:12:03 | {} | CONTRIBUTOR |
vuejs | core | 1,092,709,490 | 5,657 | javastation | > @javastation I don't understand why add a outer div will cause this error.
```mermaid
flowchart TB
subgraph A[showTable change]
direction LR
2(patch root vnode)-->3(root.el=preRoot.el):::red-->4(dynamicChildren!=null)-->|true|5(patch dynamicChildren,mount table using oldEl.parentNode)-->6(end:secondDiv.e... | 2022-04-08T10:20:30 | 2022-04-08T10:40:04 | {} | CONTRIBUTOR |
vuejs | core | 1,088,235,058 | 5,108 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 60e88fa934787357855dae3f04d3d892a7cd3f18 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-05T03:41:38 | 2022-04-05T03:43:47 | {} | NONE |
vuejs | core | 1,092,655,141 | 5,686 | edison1105 | here is a workaround. see [sfc](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCBQYXJlbnQgZnJvbSBcIi4vcGFyZW50LnZ1ZVwiO1xuaW1wb3J0IENoaWxkIGZyb20gXCIuL2NoaWxkLnZ1ZVwiO1xuXG4gIGltcG9ydCB7IHByb3ZpZGUscmVmIH0gZnJvbSAndnVlJ1xuICBjb25zdCBlbCA9IHJlZihudWxsKVxuICBwcm92aWRlKCdjaGlsZCcsZWwpXG48L3NjcmlwdD5cb... | 2022-04-08T09:32:06 | 2022-04-08T09:32:33 | {} | MEMBER |
vuejs | core | 1,092,811,674 | 5,687 | hcg1023 | @LinusBorg Actually, WHAT I mean is that I want to develop and fix this problem by myself. I think it is most appropriate to modify it in the method resolveDef. I wonder if you can assign this task to me? | 2022-04-08T12:32:00 | 2022-04-08T12:32:00 | {} | CONTRIBUTOR |
vuejs | core | 1,092,960,313 | 5,679 | bbotto-pdga | Thanks, @LinusBorg, for helping with this issue.
> This is because defineCustomElement replaces the original emit function so it can instead emit a CustomEvent.
>
> I forgot to apply the fix to that part of the codebase as well, will fix that!
I'll take your word for it on this one--I don't know enough about t... | 2022-04-08T14:59:51 | 2022-04-08T14:59:51 | {} | NONE |
vuejs | core | 1,089,969,863 | 5,670 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 83b463b83300ad4fbc013cdbdf3f0e11e8314628 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-06T08:08:38 | 2022-04-06T08:10:46 | {} | NONE |
vuejs | core | 1,090,815,696 | 5,182 | weikinhuang | we are also encountering this issue | 2022-04-06T21:15:53 | 2022-04-06T21:15:53 | {} | NONE |
vuejs | core | 1,091,069,595 | 5,676 | edison1105 | related #5640 | 2022-04-07T04:33:29 | 2022-04-07T04:33:29 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.