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,100,502,075 | 5,725 | Justineo | Can you explain how this change has improved the code? | 2022-04-16T01:43:02 | 2022-04-16T01:43:02 | {} | MEMBER |
vuejs | core | 1,100,734,369 | 5,730 | LinusBorg | I'm not sure what you mean when you say:
> since all props are passed when you do not use defineComponent
I suspect you mix this up with functional components which are a different thing. | 2022-04-16T18:59:24 | 2022-04-16T18:59:57 | {} | MEMBER |
vuejs | core | 1,063,622,536 | 5,557 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | bc06f4acc19498e638efbeeaaf2189bb059da8d2 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-03-10T03:41:27 | 2022-04-18T07:01:44 | {} | NONE |
vuejs | core | 1,099,191,212 | 5,716 | posva | Don't use `this` in the template and [follow the warning of using `$data` for properties that start with `_`](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdD5cbmV4cG9ydCBkZWZhdWx0IHtcbiAgZGF0YSgpIHtcbiAgICByZXR1cm4ge1xuICAgICAgJG1zZzogJ3N0YXJ0IHdpdGggJCcsXG4gICAgICBfbXNnOiAnc3RhcnQgd2l0aCBfJ1xuICAgIH1cbiAgfVxufVxuPC9... | 2022-04-14T13:32:35 | 2022-04-14T13:32:35 | {} | MEMBER |
vuejs | core | 1,099,900,152 | 5,720 | edison1105 | > > This scenario should use `effect` instead
>
> Why should it? There is nothing in computed values documentation (that i know of) that suggests the current behaviour is expected. That effect example happens to work, but it looks like doing manually what computed values were designed to do for you.
sorry, I misr... | 2022-04-15T06:51:23 | 2022-04-15T07:37:57 | {} | MEMBER |
vuejs | core | 1,100,084,808 | 5,723 | LinusBorg | That's not that straightforward. a CustomEvent isn't a drop-in replacement for an HTMLEvent, it has a different interface. | 2022-04-15T12:47:06 | 2022-04-15T12:47:17 | {} | MEMBER |
vuejs | core | 1,101,077,895 | 4,385 | Trinovantes | After digging around webpack's internals, I was able to create a plugin that generates a manifest and runtime code to find the current request's critical assets. It doesn't have any of the limitations from my initial hack and seems to work well for my Vue 3 SSR apps
https://www.npmjs.com/package/vue-ssr-assets-plugi... | 2022-04-18T04:18:30 | 2022-04-18T04:18:30 | {
"heart": 2
} | NONE |
vuejs | core | 1,102,584,657 | 5,752 | yyx990803 | This is great. Let's add some tests for it | 2022-04-19T12:29:13 | 2022-04-19T12:29:13 | {} | MEMBER |
vuejs | core | 1,094,286,147 | 5,695 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 931f0b8a6b594faae0394e8618b93ddfa1918b25 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-10T14:25:34 | 2022-04-14T16:27:58 | {} | NONE |
vuejs | core | 1,100,293,506 | 5,492 | gravelfox | FYI #5417 did not fix this issue, however [ckeditor5-vue](https://github.com/ckeditor/ckeditor5-vue) has fixed with a [workaround](https://github.com/ckeditor/ckeditor5-vue/issues/203). | 2022-04-15T18:57:49 | 2022-04-15T19:37:56 | {} | NONE |
vuejs | core | 1,100,750,064 | 5,734 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8d4508f15e05dcde69f5893b2406750fb5bd4c85 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-16T20:29:30 | 2022-04-16T21:33:43 | {} | NONE |
vuejs | core | 1,100,832,099 | 5,737 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 39271fffa2b6649277e58f0fcb6d3b52af8400b1 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-17T08:37:22 | 2022-04-17T08:42:51 | {} | NONE |
vuejs | core | 1,100,903,360 | 5,739 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | b3f27c6391a0994f35cb53b4afcda44518731289 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-17T15:40:26 | 2022-04-17T15:42:28 | {} | NONE |
vuejs | core | 1,101,048,909 | 5,743 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ccfef3fd30b5fcb3e368dc3bd281f000937fc889 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-18T03:09:18 | 2022-04-18T03:10:12 | {} | NONE |
vuejs | core | 1,101,093,827 | 5,745 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 4e74afe0c01f4569fda77d87e9b98d4e40aa91d9 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-18T04:55:00 | 2022-04-18T04:55:46 | {} | NONE |
vuejs | core | 1,101,631,134 | 5,741 | lidlanca | Likely duplicate of
https://github.com/vuejs/core/issues/5655 | 2022-04-18T18:23:35 | 2022-04-18T18:23:35 | {} | CONTRIBUTOR |
vuejs | core | 1,102,266,044 | 5,752 | sxzz | If this feature is acceptable, I will add a Unit Test for it later. | 2022-04-19T08:16:20 | 2022-04-19T08:16:20 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,099,144,888 | 5,707 | SvenSchoene | I wonder if this is related to this, or something like this: https://github.com/vuejs/core/issues/5655#issuecomment-1086613873 | 2022-04-14T12:41:15 | 2022-04-14T12:41:15 | {} | NONE |
vuejs | core | 1,099,278,148 | 5,720 | Frizi | > This scenario should use `effect` instead
Why should it? There is nothing in computed values documentation (that i know of) that suggests the current behaviour is expected. That effect example happens to work, but it looks like doing manually what computed values were designed to do for you. | 2022-04-14T15:01:59 | 2022-04-14T15:02:26 | {} | NONE |
vuejs | core | 1,099,665,188 | 5,720 | LinusBorg | This only seems to happen when the change happens synchronously after the watcher has been defined. Doing the count increment in `onMounted` gets the desired result:
[SFC Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IGNvbXB1dGVkLCByZWFjdGl2ZSwgcmVmLCB3YXRjaCwgb25Nb3VudGVkIH0gZnJ... | 2022-04-14T22:02:16 | 2022-04-14T22:02:16 | {} | MEMBER |
vuejs | core | 1,100,322,451 | 5,729 | dsonet | This seems harder to read. | 2022-04-15T19:43:54 | 2022-04-15T19:43:54 | {} | CONTRIBUTOR |
vuejs | core | 1,100,478,615 | 5,729 | edison1105 | do you think this change improve the performance？ | 2022-04-16T00:11:24 | 2022-04-16T00:11:53 | {} | MEMBER |
vuejs | core | 1,100,702,129 | 5,730 | westbrma | @LinusBorg since all props are passed when you do not use defineComponent it seems like it should also work that way for consistency when using defineComponent. | 2022-04-16T16:33:02 | 2022-04-16T16:33:02 | {} | NONE |
vuejs | core | 1,101,048,915 | 5,743 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | ccfef3fd30b5fcb3e368dc3bd281f000937fc889 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-18T03:09:19 | 2022-04-18T03:16:21 | {} | NONE |
vuejs | core | 1,101,147,697 | 5,500 | ygj6 | @posva I have tested, PR https://github.com/vuejs/core/pull/5268 can not solve this issue, so it's not a duplicate. | 2022-04-18T06:46:14 | 2022-04-18T06:46:14 | {} | MEMBER |
vuejs | core | 1,102,383,269 | 5,742 | posva | Can't you build this with customRefs already though? | 2022-04-19T09:29:46 | 2022-04-19T09:29:46 | {} | MEMBER |
vuejs | core | 1,099,193,607 | 5,719 | 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). | 2022-04-14T13:35:11 | 2022-04-14T13:35:11 | {} | MEMBER |
vuejs | core | 1,100,658,427 | 5,731 | LinusBorg | edit: I misread your issue. reopened | 2022-04-16T13:02:05 | 2022-04-16T13:13:39 | {} | MEMBER |
vuejs | core | 1,100,750,073 | 5,734 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8d4508f15e05dcde69f5893b2406750fb5bd4c85 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-16T20:29:33 | 2022-04-16T21:27:20 | {} | NONE |
vuejs | core | 1,101,148,970 | 5,680 | npmrun | 是的，加了nextTick不报错了。如果是去掉transition也不报错 | 2022-04-18T06:48:16 | 2022-04-18T06:48:16 | {} | NONE |
vuejs | core | 1,102,355,977 | 5,751 | posva | Your key always change. You might want to use
```vue
<router-view v-slot="{ Component, route }">
<transition mode="out-in" name="fade">
<keep-alive :include="cachedViewsDeep">
<component :is="Component" :key="route.name || route.path" />
</keep-alive>
</transition>
... | 2022-04-19T09:11:12 | 2022-04-19T09:11:12 | {} | MEMBER |
vuejs | core | 1,102,373,562 | 5,744 | posva | Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org). | 2022-04-19T09:23:02 | 2022-04-19T09:23:02 | {} | MEMBER |
vuejs | core | 1,102,519,207 | 5,753 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 5644e2ca54266fcf0054b5f3a63ba5bead3e0cd6 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-04-19T11:16:35 | 2022-04-19T11:20:58 | {} | NONE |
vuejs | core | 1,098,984,194 | 5,708 | yyx990803 | Thanks for the PR, however it only gets rid of the warning and doesn't fix the transition behavior for #5675. See 62eba631 | 2022-04-14T10:07:24 | 2022-04-14T10:07:24 | {} | MEMBER |
vuejs | core | 1,099,878,603 | 5,722 | Linhongbin-1111 | oh, it's my problem. Thanks for your reply. | 2022-04-15T06:02:33 | 2022-04-15T06:02:33 | {} | NONE |
vuejs | core | 1,100,903,362 | 5,739 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | b3f27c6391a0994f35cb53b4afcda44518731289 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-17T15:40:26 | 2022-04-17T15:41:19 | {} | NONE |
vuejs | core | 1,100,903,361 | 5,739 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | b3f27c6391a0994f35cb53b4afcda44518731289 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-04-17T15:40:26 | 2022-04-17T15:43:20 | {} | NONE |
vuejs | core | 1,101,659,232 | 5,741 | asialiugf | yes
| 2022-04-18T18:55:17 | 2022-04-18T18:55:17 | {} | NONE |
vuejs | core | 1,042,642,396 | 5,439 | lidlanca | a workaround that does not alter the output html
wrap string expression in `()`
```html
<template>
<pre data-type="js"><code v-html="('<span>show-it </span>')"></code></pre>
</template>
```
This will force it not to get statically hoisted.
`data-*` attribute, only "expedited" the static h... | 2022-02-17T07:16:19 | 2022-02-17T07:17:54 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 1,035,111,121 | 5,400 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 01c669470afa1ba02b9d61dc6560ce53a4e2e19f
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620e114b8b07cf0008fcd651](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-10T16:14:37 | 2022-02-17T09:12:38 | {} | NONE |
vuejs | core | 1,044,055,280 | 5,449 | LinusBorg | 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. | 2022-02-18T07:26:40 | 2022-02-18T07:26:53 | {
"heart": 1,
"rocket": 1
} | MEMBER |
vuejs | core | 1,044,717,155 | 5,453 | LinusBorg | > 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?
I see that I didn't make myself clear, sorry for that. So, let's restart and ignore my previous, confusing examples for a second.
I was tryi... | 2022-02-18T15:38:14 | 2022-02-18T15:51:53 | {} | MEMBER |
vuejs | core | 1,044,957,367 | 5,447 | lidlanca | note that PR https://github.com/vuejs/core/pull/5118
seem to fix both #5116 and #5447(this issue) | 2022-02-18T18:17:22 | 2022-02-18T18:17:22 | {
"+1": 1,
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 1,045,114,907 | 5,453 | lidlanca | when I said confusing I meant visually conflicting/similar.
for example names that are just slightly different (ex capital letter)
which is especially a problem where template have case insensitivity and more hidden logic.
BottomSheet
bottomSheet
HelloWorld
helloWorld
qButton
QButton
related
h... | 2022-02-18T20:07:15 | 2022-02-18T20:07:15 | {} | CONTRIBUTOR |
vuejs | core | 1,041,214,293 | 5,401 | LinusBorg | @rictic thanks!
So here's the recommendation:
In Vue, one can define custom directives (like that internal ones, i.e. `v-on`) to wrap imperative DOM operations in a declarative way. These custom directives can be declared locally in each component or registered globally in an app to be available in all child com... | 2022-02-16T07:59:57 | 2022-02-16T08:01:47 | {} | MEMBER |
vuejs | core | 1,041,360,826 | 4,662 | dezmound | > > 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 injecte... | 2022-02-16T10:53:46 | 2022-02-16T10:55:34 | {} | NONE |
vuejs | core | 1,041,924,586 | 5,438 | LinusBorg | `obj` needs to be a ref | 2022-02-16T17:43:40 | 2022-02-16T17:43:40 | {} | MEMBER |
vuejs | core | 1,042,599,620 | 5,439 | clxho | +1 | 2022-02-17T05:52:45 | 2022-02-17T05:52:45 | {} | NONE |
vuejs | core | 1,042,748,314 | 5,442 | ehsan-shv | I found it and solved based on [documents](https://vuejs.org/api/options-misc.html#inheritattrs):
```
export default {
inheritAttrs: false,
}
``` | 2022-02-17T09:35:16 | 2022-02-17T09:35:16 | {} | NONE |
vuejs | core | 1,043,214,402 | 3,102 | iliubinskii | For anyone interested I found the following solution:
I use GlobalComponentConstructor type from Quasar framework:
```vue
// Quasar type
type GlobalComponentConstructor<Props = {}, Slots = {}> = {
new (): {
$props: PublicProps & Props
$slots: Slots
}
}
interface MyComponentProps<T> {
// D... | 2022-02-17T17:24:43 | 2022-02-17T17:24:43 | {
"+1": 4
} | NONE |
vuejs | core | 1,042,811,844 | 5,445 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 1801f74b3cedf2f99a27fc21b106e6b264f25121
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620f03186ce64a0007f272c2](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-17T10:44:28 | 2022-02-18T02:24:06 | {} | NONE |
vuejs | core | 1,044,030,287 | 5,449 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: cef81241239c0befcf3b65f95cd9db8f2ef5b04c
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620f58508544e100073a5a80](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-18T07:02:36 | 2022-02-18T08:27:41 | {} | NONE |
vuejs | core | 1,044,247,071 | 4,339 | 0x30 | ABOUT这个,有没有计划上线啊... BROTHER. [狗头]
 | 2022-02-18T09:56:07 | 2022-02-18T09:56:07 | {} | NONE |
vuejs | core | 1,044,479,822 | 5,446 | LinusBorg | > The sense is that multiple root elements may use classes:
Our perspective is that it's not a good idea to break separation of concerns/responsibilities in this way, so we don't go out of our way to support it.
> But I can't achieve this neither with :deep pseudo class nor without it:
Yes, :deep doesn't work ... | 2022-02-18T12:52:53 | 2022-02-18T12:52:53 | {} | MEMBER |
vuejs | core | 1,044,736,037 | 2,855 | Yendric | This bug still occurs when using the latest version of vue. | 2022-02-18T15:51:11 | 2022-02-18T15:51:11 | {} | NONE |
vuejs | core | 1,046,036,794 | 5,446 | Rolanddoda | @LinusBorg thank you for the detailed explanation. Make sense to me now why this is a limitation. *Have a nice weekend* | 2022-02-19T14:59:48 | 2022-02-19T14:59:48 | {} | NONE |
vuejs | core | 1,044,768,710 | 5,453 | Rolanddoda | @LinusBorg thank you for the detailed explanation.
While I know why technically this fails and your explanation gives me a better understanding, I still think that this is a bug or at least should get improved. *Sorry, I might be the only one who thinks that.*
If the dev has a component imported locally, I don't ... | 2022-02-18T16:11:05 | 2022-02-18T16:11:05 | {} | NONE |
vuejs | core | 1,045,989,887 | 5,457 | LinusBorg | > here is no way get a genuine `<template>` tag to conditionally render.
That's incorrect. You can of course nest two template elements to achieve what you wanted to do with one.
```html
<template v-if="condition"> <!-- this one will disappear as it only carries the conditional -->
<template v-custom> <!-- this... | 2022-02-19T10:51:08 | 2022-02-19T10:51:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,046,023,554 | 5,459 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 90d2ddd608b9195b908222cf4ae02df20884fe5d
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/621102bd295abc0008fe6b61](https://app.netlify.com/sites/vue-next-template-explorer/deploys/621... | 2022-02-19T13:55:57 | 2022-02-19T14:47:26 | {} | NONE |
vuejs | core | 1,046,182,117 | 5,456 | Rolanddoda | @Hongbusi if you don't use the SFC playground but you instead use [Stackblitz demo here](https://stackblitz.com/edit/vitejs-vite-znrxck?file=src%2FApp.vue&terminal=dev) you will see that the Vue instance is correctly displayed:
 please. | 2022-02-18T08:01:30 | 2022-02-18T08:01:30 | {} | MEMBER |
vuejs | core | 1,044,167,742 | 5,184 | WangQingye | > I have the same issue, only in production env, cant find the reason
After stucking on this problem two days. Finally solved it, although i dont konw the real reason.
I have tried changing v-if to v-show, not works.
And changed my template slot to div, not works.
And then i found a strange thing is that when i ... | 2022-02-18T08:56:03 | 2022-02-18T08:59:17 | {} | NONE |
vuejs | core | 1,045,057,328 | 5,453 | Rolanddoda | > if you want to use confusing names for components and variables, you can do that
@lidlanca I am not using confusing names. If you have read my comments, I said that in my original code I have a global component named `BottomSheet` and I have a variable `bottomSheet` which is a ref. And that's when I got the error.... | 2022-02-18T19:24:46 | 2022-02-18T19:24:46 | {} | NONE |
vuejs | core | 1,045,339,214 | 5,453 | posva | Closing as this is working as intended as it's also the first line in docs: https://vuejs.org/api/sfc-script-setup.html#using-components
> Values in the scope of <script setup> can also be used directly as custom component tag names: | 2022-02-18T23:25:27 | 2022-02-18T23:25:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,046,022,591 | 5,456 | Hongbusi | > I can only reproduce it in SFC Playground.😵
You can try it in the project where I found this problem.
[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#L4... | 2022-02-19T13:49:58 | 2022-02-19T13:49:58 | {} | NONE |
vuejs | core | 1,046,026,085 | 5,456 | posva | You might not be able to console log inside the SFC playground but the variable is set, as @lidlanca pointed out.
The problem comes https://github.com/vuejs/repl/blob/main/src/output/srcdoc.html#L134. Maybe it's worth doing a try-catch there. You should open a PR @Hongbusi | 2022-02-19T14:10:11 | 2022-02-19T14:10:11 | {} | MEMBER |
vuejs | core | 1,045,981,223 | 5,458 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: f06426333c2f0a1a3524acd9906dad7e2c859700
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/621216212e54bb0007637b85](https://app.netlify.com/sites/vue-next-template-explorer/deploys/621... | 2022-02-19T09:58:12 | 2022-02-20T10:22:21 | {} | NONE |
vuejs | core | 1,042,629,938 | 5,401 | LinusBorg | @rictic That's indeed something to consider. However I'm worrried that it's similarity to `v-on` would make it an easy point of confusion, and given that it's only real purpose is to work around a limitation in the handling of custom events, I'd be a bit hesitant to make it a new API on the same level as `v-on`. Howeve... | 2022-02-17T06:54:33 | 2022-02-17T06:54:44 | {} | MEMBER |
vuejs | core | 1,043,515,253 | 5,446 | iliubinskii | > That doesn't make too much sense for a multi-root component
The sense is that multiple root elements may use classes:
And I may need to apply styles to these classes.
But I can't achieve this neit... | 2022-02-17T22:04:29 | 2022-02-17T22:04:29 | {
"+1": 2
} | NONE |
vuejs | core | 1,042,811,847 | 5,445 | netlify[bot] | ❌ Deploy Preview for *vuejs-coverage* failed.
🔨 Explore the source changes: 1801f74b3cedf2f99a27fc21b106e6b264f25121
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620f03182225080008722b8d](https://app.netlify.com/sites/vuejs-coverage/deploys/620f03182225080008722b8d)
| 2022-02-17T10:44:28 | 2022-02-18T02:25:17 | {} | NONE |
vuejs | core | 1,044,146,285 | 5,451 | neoech | but vm.error is a reactive object. | 2022-02-18T08:40:35 | 2022-02-18T08:40:35 | {} | NONE |
vuejs | core | 1,044,701,963 | 5,390 | Rolanddoda | @LinusBorg so if `App.vue` has a single root element we will end up having 2 container elements and there is no way to have just one?
Thanks for the links you referenced, but I can't really understand how can I have only one root element and that being from `App.vue` | 2022-02-18T15:27:24 | 2022-02-18T15:27:24 | {} | NONE |
vuejs | core | 1,044,932,439 | 5,118 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 6305830542a9d9f58419d610bed3f70dde3df5a8
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620fdedb1a797e0007fd3abc](https://app.netlify.com/sites/vuejs-coverage/deploys/620fdedb1a797e0007fd3abc)
😎 Browse th... | 2022-02-18T18:01:05 | 2022-02-18T18:06:45 | {} | NONE |
vuejs | core | 1,045,973,230 | 5,118 | lidlanca | > Look at this example:[vue-sfc-playground](https://deploy-preview-5118--vue-sfc-playground.netlify.app/#eyJBcHAudnVlIjoiPHNjcmlwdCA+XG4gIGltcG9ydCB7IHJlZiwgb25Nb3VudGVkIH0gZnJvbSAndnVlJ1xuICBcbiAgZXhwb3J0IGRlZmF1bHQge1xuICAgIHNldHVwKCl7XG4gICAgICBjb25zdCBsaXN0ID0gcmVmKFsxLCAyLCAzXSlcbiAgICAgIGxldCBpdGVtUmVmcyA9IHJlZih... | 2022-02-19T09:07:29 | 2022-02-19T09:07:54 | {} | CONTRIBUTOR |
vuejs | core | 1,045,986,977 | 5,457 | entegyopensource | Ok, so a `<template>` with a `v-if` is handled specially by Vue, and there is no way get a genuine `<template>` tag to conditionally render.
Thank you. This explains the results of my tests, however it does break my expectations of the framework. | 2022-02-19T10:33:11 | 2022-02-19T10:33:37 | {} | NONE |
vuejs | core | 1,046,023,557 | 5,459 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 90d2ddd608b9195b908222cf4ae02df20884fe5d
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/621102bd1c82870009586c81](https://app.netlify.com/sites/vuejs-coverage/deploys/621102bd1c82870009586c81)
😎 Browse th... | 2022-02-19T13:55:58 | 2022-02-19T14:53:57 | {} | NONE |
vuejs | core | 1,046,176,096 | 5,456 | Rolanddoda | @Hongbusi I re-created your demo in Stackblitz and it works fine. [See it here](https://stackblitz.com/edit/vitejs-vite-znrxck?file=src%2FApp.vue&terminal=dev)
So yeah the issue happens only in SFC playground | 2022-02-20T07:01:01 | 2022-02-20T07:01:01 | {} | NONE |
vuejs | core | 1,042,539,441 | 5,401 | rictic | That works well.
Given its small size, what do you think about adding the event directive into Vue by default, just so that it's a pattern that components can rely on existing, and that is more likely to be findable? | 2022-02-17T03:33:40 | 2022-02-17T03:33:40 | {} | NONE |
vuejs | core | 1,042,729,869 | 5,184 | martijn10kb | @posva Please reopen this issue and look into it. We are all stuck on this issue.. | 2022-02-17T09:15:37 | 2022-02-17T09:15:37 | {
"+1": 5
} | NONE |
vuejs | core | 1,044,121,589 | 3,258 | nandi95 | Happy birthday to this PR 🎉 🎉 🎈
It's already one year old, can't believe how fast time flies. 🥺🥺
😅 | 2022-02-18T08:18:08 | 2022-02-18T08:18:08 | {
"laugh": 3
} | CONTRIBUTOR |
vuejs | core | 1,044,554,306 | 2,562 | guogangj | Is there any further news on this issue? | 2022-02-18T13:49:16 | 2022-02-18T13:49:16 | {} | NONE |
vuejs | core | 1,046,021,789 | 5,456 | Hongbusi | > you are getting it, you just can't console.log the object.
>
> try for example `console.log(componentRef.value.$)` or `console.log(componentRef.value.$.ctx)`
This method can access the subcomponent instance, but there are no subcomponent-related methods. | 2022-02-19T13:45:04 | 2022-02-19T13:45:04 | {} | NONE |
vuejs | core | 1,046,204,523 | 5,456 | Hongbusi | Thank you. @lidlanca | 2022-02-20T10:11:35 | 2022-02-20T10:11:35 | {} | NONE |
vuejs | core | 1,043,823,589 | 5,448 | likeswinds | #5447 | 2022-02-18T03:29:56 | 2022-02-18T03:29:56 | {} | NONE |
vuejs | core | 1,044,932,436 | 5,118 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 6305830542a9d9f58419d610bed3f70dde3df5a8
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620fdedbf1b6ed00086b6336](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-18T18:01:04 | 2022-02-18T18:02:13 | {} | NONE |
vuejs | core | 1,045,966,800 | 5,456 | lidlanca | you are getting it, you just can't console.log the object.
try for example
`console.log(componentRef.value.$)`
or
`console.log(componentRef.value.$.ctx)` | 2022-02-19T08:26:51 | 2022-02-19T08:30:02 | {
"+1": 1,
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 1,046,035,809 | 5,446 | LinusBorg | There's a difference between a bug and a limitation of a design/solution/feature, wether that limitation is for technical reasons or intentionally put in place.
### `:deep()`
`:deep(.some-class-name)` was explicitly designed to produce a selector like: `[data-v-3478937439] .some-class-name`.
That means, this d... | 2022-02-19T14:54:18 | 2022-02-19T14:55:33 | {} | MEMBER |
vuejs | core | 1,046,182,402 | 5,456 | Hongbusi | @Rolanddoda The screenshot just now is the result of my local printout. | 2022-02-20T07:49:15 | 2022-02-20T07:49:15 | {} | NONE |
vuejs | core | 1,046,202,236 | 5,393 | NickBelhomme | I have this too in version 3.2.31
No interface available. I do not agree that it is a "feature" or a "nice to have"
| 2022-02-20T09:59:08 | 2022-02-20T09:59:08 | {} | NONE |
vuejs | core | 1,035,111,098 | 5,400 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 01c669470afa1ba02b9d61dc6560ce53a4e2e19f
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/620e114b91ec3d00074fed82](https://app.netlify.com/sites/vue-sfc-playground/deploys/620e114b91ec3d00074fed82)
... | 2022-02-10T16:14:36 | 2022-02-17T09:14:15 | {} | NONE |
vuejs | core | 1,044,125,599 | 5,451 | LinusBorg | This is expected as you logged a raw Ref, which will run its value through JSON.stringify()
You want to red the ref's value:
```
{{ vm.error.value }}
```
The value is not unwrapped because vm is not a reactive object. | 2022-02-18T08:21:34 | 2022-02-18T08:22:02 | {} | MEMBER |
vuejs | core | 1,044,151,543 | 5,451 | LinusBorg | It's a ref.
vm is not a reactive object, so its contents will not be unwrapped in the template.
So reading vm.error gives you the ref, not "aaa" | 2022-02-18T08:45:01 | 2022-02-18T08:45:39 | {} | MEMBER |
vuejs | core | 1,044,783,386 | 5,390 | Rolanddoda | Thank you @LinusBorg | 2022-02-18T16:21:39 | 2022-02-18T16:21:39 | {} | NONE |
vuejs | core | 1,045,926,566 | 5,456 | ygj6 | I can only reproduce it in SFC Playground.:dizzy_face:
| 2022-02-19T07:13:43 | 2022-02-19T07:13:43 | {} | MEMBER |
vuejs | core | 1,045,974,751 | 5,118 | ygj6 | > > Look at this example:[vue-sfc-playground](https://deploy-preview-5118--vue-sfc-playground.netlify.app/#eyJBcHAudnVlIjoiPHNjcmlwdCA+XG4gIGltcG9ydCB7IHJlZiwgb25Nb3VudGVkIH0gZnJvbSAndnVlJ1xuICBcbiAgZXhwb3J0IGRlZmF1bHQge1xuICAgIHNldHVwKCl7XG4gICAgICBjb25zdCBsaXN0ID0gcmVmKFsxLCAyLCAzXSlcbiAgICAgIGxldCBpdGVtUmVmcyA9IHJlZ... | 2022-02-19T09:16:57 | 2022-02-19T09:16:57 | {} | MEMBER |
vuejs | core | 1,045,992,172 | 5,458 | LinusBorg | > we usually don't have test for internal stuff, since the createBlock would be generated by the compiler
That wasn't relevant when we didn't really offer typechecking for the template/generated render function, but now with Volar and vue-tsc we effectively do, and the issue addressed by this PR is a result of that... | 2022-02-19T11:04:56 | 2022-02-19T11:04:56 | {} | MEMBER |
vuejs | core | 1,041,363,908 | 2,143 | ghost | > >
> >
> > `[Vue warn]: <Suspense> slots expect a single root node. `
>
> Fixed:
>
> ```
> <router-view v-slot="{ Component }">
> <suspense>
> <div>
> <component :is="Component" />
> </div>
> </suspense>
> </router-view>
> ```
I've added keep-alive and it's not work... | 2022-02-16T10:57:42 | 2022-02-16T10:57:42 | {
"eyes": 2
} | NONE |
vuejs | core | 1,041,474,838 | 5,430 | posva | This is what petite vue seems to solve. If not, please open an RFC in the rfcs repo | 2022-02-16T13:08:51 | 2022-02-16T13:08:51 | {} | MEMBER |
vuejs | core | 1,042,749,735 | 4,344 | tangjiahui-cn | > > > Hi,
> > > I am building a library with vue3 and vite, when i use the library if i use slot i got same issue, i tried the solutions in this thread but i can not fix the issue.
> > > error: `Uncaught TypeError: Cannot read properties of null (reading 'isCE')`
> > > My vite config.js:
> > > ```
> > > import vue... | 2022-02-17T09:36:54 | 2022-02-17T09:36:54 | {} | NONE |
vuejs | core | 1,043,172,471 | 3,102 | pikax | We need to use classes to solve this, classes are not planned to be supported.
Another way to do this (hacky overhead), would be doing something like:
```ts
import { Component, defineComponent } from 'vue'
function genericFunction<G extends { new(): { $props: P } }, P, T extends Component>(f: () => T, c: G): ... | 2022-02-17T16:46:21 | 2022-02-17T16:46:21 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.