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,432,664,126 | 7,729 | baiwusanyu-c | #7731 | 2023-02-16T07:55:48 | 2023-02-16T07:55:48 | {} | MEMBER |
vuejs | core | 1,436,449,683 | 7,710 | KaelWD | `expose()` isn't type safe.
I wasn't aware expose allowed prefixed keys, is there a reason setup return is treated differently? | 2023-02-20T07:04:25 | 2023-02-20T07:04:25 | {} | CONTRIBUTOR |
vuejs | core | 1,437,391,542 | 2,513 | miainchambers | Has anybody come across this issue with Vue 3 using the Options API? Any idea if it's been resolved yet at all? | 2023-02-20T18:08:40 | 2023-02-20T18:08:40 | {} | NONE |
vuejs | core | 1,439,063,374 | 6,736 | aadamcik | Hey @DamianGlowala , is there any reason why this isn't merged yet? Thank you! | 2023-02-21T20:39:14 | 2023-02-21T20:39:14 | {
"eyes": 4
} | NONE |
vuejs | core | 1,440,657,541 | 7,750 | sxzz | /ecosystem-ci run | 2023-02-22T19:15:37 | 2023-02-22T19:15:37 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,440,658,292 | 7,745 | sxzz | /ecosystem-ci run | 2023-02-22T19:16:14 | 2023-02-22T19:16:14 | {} | MEMBER |
vuejs | core | 1,435,468,794 | 5,525 | liulinboyi | > nothing is working and gives me headache omg. The value of ref, no matter what i do (skip unwrap, binding with function and push), is a proxy and I can't access anything. When i try to access with myArray.value[0], it gives undefined
>
>  and *all of them* should emit the same event, then yes: you would have to add an event binding on each of those 20 components.
Just like you would do if you had all of these 20 components directly ... | 2023-02-21T11:05:15 | 2023-02-21T11:12:02 | {} | MEMBER |
vuejs | core | 1,438,427,571 | 7,761 | yyx990803 | What is the point of this? The original uses 7 chars which is consistent with the GitHub short format. | 2023-02-21T12:50:46 | 2023-02-21T12:50:46 | {} | MEMBER |
vuejs | core | 1,439,930,421 | 3,671 | cbkhwx | +1 | 2023-02-22T12:21:13 | 2023-02-22T12:21:13 | {} | NONE |
vuejs | core | 1,433,101,590 | 7,733 | DrPhil | Here are two testcases that can be added to `server-renderer/__tests__/render.spec.ts`. (Not entirely sure that these test-cases are correct, or that this is the right place to put them. I trust the reproducing example more!)
```
// #7733
test('reset current instance after error in data', async () => {... | 2023-02-16T13:38:18 | 2023-02-16T13:59:25 | {} | CONTRIBUTOR |
vuejs | core | 1,434,178,843 | 7,736 | LinusBorg | `smooth-dnd` re-orders the HTML elements that Vue controls, so when Vue re-renders, the elements are not in the place Vue thinks they are, messing up its patch phase.
A quick look at that lib's [Vue 2 integraation](https://github.com/kutlugsahin/vue-smooth-dnd/blob/c9595fe11ee08ac2f56850037334b4eb6ece90f0/src/Contai... | 2023-02-17T06:58:10 | 2023-02-17T06:58:10 | {} | MEMBER |
vuejs | core | 1,434,301,139 | 7,742 | Justineo | 文档相关的问题请提到 [vuejs-translations](https://github.com/vuejs-translations/docs-zh-cn)。另外这个问题见 [vuejs-translations/docs-zh-cn#646](https://github.com/vuejs-translations/docs-zh-cn/issues/646)。 | 2023-02-17T08:37:52 | 2023-02-17T08:37:52 | {} | MEMBER |
vuejs | core | 1,436,557,581 | 7,710 | KaelWD | Fair enough, I don't use `this` anymore so I forgot that was a thing. It doesn't actually appear to use `_` though apart from `this._` for ComponentInternalInstance, and #4570 only mentions `this._` not any value starting with `_`.
Would changing the check from `key[0] === '_' || key[0] === '$'` to `key === '_' || k... | 2023-02-20T08:44:48 | 2023-02-20T08:44:48 | {} | CONTRIBUTOR |
vuejs | core | 1,439,021,821 | 7,755 | LinusBorg | Not really, no. | 2023-02-21T20:00:26 | 2023-02-21T20:00:26 | {} | MEMBER |
vuejs | core | 1,432,376,951 | 7,726 | Masa-Shin | I see now thanks @Justineo, but I think [this flag and its description](https://v3-migration.vuejs.org/migration-build.html#:~:text=No%20longer%20removes%20attribute%20if%20binding%20value%20is%20boolean%20false) may be somewhat misleading. In fact, the ATTR_FALSE_VALUE flags appeared even for boolean attributes. | 2023-02-16T02:18:20 | 2023-02-16T04:58:35 | {} | CONTRIBUTOR |
vuejs | core | 1,434,266,148 | 7,568 | nawbc | @yyx990803 cc
| 2023-02-17T08:01:19 | 2023-02-17T08:01:19 | {} | NONE |
vuejs | core | 1,435,972,509 | 7,755 | LinusBorg | Slots have a very different purpose. passing properties (or event listeners) to slots enables the parent component to decide where to place those.
See: https://vuejs.org/guide/components/slots.html#scoped-slots
So I'm not sure what the purpose of this request is, what kind of problem it solves. I read the linked ... | 2023-02-19T12:13:06 | 2023-02-19T12:15:02 | {} | MEMBER |
vuejs | core | 1,435,977,669 | 7,755 | olfek | so my use case looks something like this
`Dialog` component **which has show/hide logic** :
```
<div>
<slot></slot>
</div>
```
and then
```
<Dialog>
<SomeDialogContents /> <-- responsible for telling parent to "hide" when finished
</Dialog>
```
at the moment, I have implemented it like thi... | 2023-02-19T12:36:51 | 2023-02-19T12:36:51 | {} | NONE |
vuejs | core | 1,436,386,236 | 7,759 | baiwusanyu-c | This may be a compiler bug | 2023-02-20T06:09:52 | 2023-02-20T06:09:52 | {} | MEMBER |
vuejs | core | 1,436,568,348 | 7,761 | JayFate | @sxzz Do you have a minute to review this PR ? THX | 2023-02-20T08:54:26 | 2023-02-20T08:54:26 | {} | CONTRIBUTOR |
vuejs | core | 1,436,637,861 | 7,755 | Justineo | I believe @LinusBorg's [solution above](https://github.com/vuejs/core/issues/7755#issuecomment-1435980513
) is a more solid pattern for a parent component to expose logic to its slot content (not only in Vue 3 but also in Vue 2).
| 2023-02-20T09:41:07 | 2023-02-20T09:41:07 | {} | MEMBER |
vuejs | core | 1,436,680,188 | 7,754 | AlexVagrant | I think this is a `ref` bug. the following code may be used to solve this bug.
@LinusBorg
```js
if (value || (!value && vnode.transition && !vnode.transition.persisted)) {
// #1789: for non-null values, set them after render
// null values means this is unmount and it should not overwrite anothe... | 2023-02-20T10:10:06 | 2023-02-20T10:11:16 | {} | CONTRIBUTOR |
vuejs | core | 1,438,474,082 | 4,384 | skirtles-code | The code for the scheduler has undergone some significant changes since this PR was opened. From what I can tell, the most important parts of this PR apply to code that no longer exists.
@gdh51 Do you think this can be closed now? Or is there some part of it that is still relevant to the current version of the sched... | 2023-02-21T13:15:40 | 2023-02-21T13:15:40 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,439,645,751 | 6,736 | DamianGlowala | From the message I received from @antfu, this PR needs feedback from the core team. There isn't any timescale for having this merged at the moment.
For Nuxt users: if this PR takes longer than expected, it might be patched directly in Nuxt at some point. | 2023-02-22T08:55:21 | 2023-02-22T08:55:21 | {
"+1": 14
} | CONTRIBUTOR |
vuejs | core | 1,439,736,130 | 7,755 | olfek | This is a valid feature request and this issue should have been kept open to host any future discussion and to highlight areas for improvement. Thank you for the display of courtesy. I'm moving to Angular. Bye. | 2023-02-22T10:01:11 | 2023-02-22T10:01:11 | {} | NONE |
vuejs | core | 1,440,655,699 | 7,776 | sxzz | /ecosystem-ci run | 2023-02-22T19:14:04 | 2023-02-22T19:14:04 | {} | MEMBER |
vuejs | core | 1,440,656,085 | 7,776 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4246152343)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4246152343/jobs/7382596501) | :white_check_mark: success |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/42461523... | 2023-02-22T19:14:26 | 2023-02-22T19:21:39 | {} | CONTRIBUTOR |
vuejs | core | 1,432,733,676 | 7,729 | LinusBorg | Hm, I took another look. I think acutally, our types are fine. The problem is with the types of `fluent-vue`:
https://github.com/fluent-vue/fluent-vue/blob/fdc1fbcd45053415c55c86b2885534bed26451c6/src/types/typesCompat.ts#L26
```ts
export type InstallFunction<TOptions> = (vue: unknown, options: TOptions) => void... | 2023-02-16T08:56:08 | 2023-02-16T08:57:10 | {} | MEMBER |
vuejs | core | 1,434,177,276 | 4,662 | HaloElite | > This would get very messy if you have a design system in place that re-uses components.
That's true. But it's working for small components included once or twice on your page.
Apart from this I don't see a way to deal with this problem, tho. | 2023-02-17T06:55:54 | 2023-02-17T06:56:02 | {} | NONE |
vuejs | core | 1,434,456,259 | 7,010 | Stephan-MC | got the same issue too and using v:3,2,45 | 2023-02-17T10:42:44 | 2023-02-17T10:42:44 | {} | NONE |
vuejs | core | 1,435,313,915 | 5,764 | DrJume | Doesn't the eslint parser use the vue parser internally? So it could be still the issue I described above, where the compiled output doesn't remove the TS syntax. | 2023-02-17T21:47:49 | 2023-02-17T21:47:49 | {} | CONTRIBUTOR |
vuejs | core | 1,437,646,620 | 7,764 | J-Sek | Oh... am I see, we are expected to concatenate `passive` with `onWheel`.
If only I read the docs more carefully :) | 2023-02-20T22:56:20 | 2023-02-20T22:56:20 | {} | NONE |
vuejs | core | 1,439,795,312 | 7,755 | olfek | > Why can I say that confidently? Because we have discussed and decided against features related to "event bubbling" multiple times in the past. It's something we don't want in the API ...
Ok, so you don't want event bubbling, I understand this.
But I'm certain that the intelligent people working on Vue such as y... | 2023-02-22T10:40:22 | 2023-02-22T10:40:22 | {} | NONE |
vuejs | core | 1,564,145,978 | 5,657 | frosk1 | should this error due to the massive unresolved issues be opened again?
Opened again? | 2023-05-26T10:07:42 | 2023-07-24T15:03:07 | {
"+1": 9
} | NONE |
vuejs | core | 1,649,338,127 | 8,837 | marfalkov | @FreekVR
That v-for would be `v-for="(name, _)`, and the error is gone.
[stackblitz](https://stackblitz.com/edit/github-u4xmkj-ngscuy?file=src%2Fcomponents%2FExtend.vue) | 2023-07-25T08:10:57 | 2023-07-25T08:10:57 | {
"eyes": 1,
"heart": 1
} | NONE |
vuejs | core | 1,650,912,714 | 8,845 | Justineo | Vue template follows HTML syntax so `&` inside your template is already decoded into `&` in your JavaScript code. You can see this from the compiled output:
```js
return (_ctx, _cache) => {
return (_openBlock(), _createElementBlock(_Fragment, null, [
_createElementVNode("p", null, _toDisplayString(msg.v... | 2023-07-26T03:15:22 | 2023-07-26T03:15:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,651,081,852 | 8,847 | jacekkarczmarczyk | > According to the documentation, this watch in Child.vue should be deep by default
It should not be deep, which part of the documentation are you referring to? | 2023-07-26T06:51:06 | 2023-07-26T06:51:06 | {} | CONTRIBUTOR |
vuejs | core | 1,653,044,828 | 8,849 | Bernankez | Sorry my bad, I didn't pass filename on `parse(code, {filename:''})`, so `compileScript` cannot resolve the right file path. Thanks for reply :) | 2023-07-27T07:20:58 | 2023-07-27T07:20:58 | {} | NONE |
vuejs | core | 1,653,062,310 | 8,855 | 1zumii | part of this issue is the same as #8604
| 2023-07-27T07:35:09 | 2023-07-27T07:35:09 | {} | NONE |
vuejs | core | 1,653,895,675 | 8,861 | liulinboyi | @jc840031139
## Reason
首先`watchEffect`会立即执行回调,执行时机是`Vue`组件更新之前被调用,在子组件`test1Child`修改`testValRef`的值,`testValRef`发生改变,会立即触发父组件`test1`组件的更新(在父组件`test1`中使用了`testValRef`,所以会更新),父组件`test1`组件更新时先执行`setup`,执行`setup`时,`watchEffect`会立即执行回调,触发父组件`test1`组件的更新,此时`updateQueue`一直在增加,并没有真正执行组件渲染,来消费`update`。此时`updateQueue`增加至最大值`RE... | 2023-07-27T15:52:40 | 2023-07-28T02:57:59 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,655,436,051 | 8,860 | LinusBorg | I'd call this behavior expected as its the same as in templates:
* Top-level refs are unwrapped
* refs nested in `reactive()` objects are unwrapped
* refs nested in plain objects are *not* unwrapped (your case is this)
Changing this now would also ve a breaking change | 2023-07-28T10:12:40 | 2023-07-28T10:12:40 | {} | MEMBER |
vuejs | core | 1,656,091,730 | 8,862 | josh-eebz | Thanks for the feedback | 2023-07-28T17:39:58 | 2023-07-28T17:39:58 | {} | NONE |
vuejs | core | 1,656,117,874 | 8,865 | jacekkarczmarczyk | If you need a result from the handler then use `defineProps` instead of `defineEmits`
> And why do we have in defineEmits return type if emits always return void?
You don't need to, you can use the syntax that doesn't require providing a return type (see Vue docs for details) | 2023-07-28T18:03:29 | 2023-07-28T18:03:29 | {} | CONTRIBUTOR |
vuejs | core | 1,645,651,202 | 7,794 | edison1105 | It's been fixed since v3.3 | 2023-07-21T14:08:39 | 2023-07-21T14:08:39 | {} | MEMBER |
vuejs | core | 1,651,780,881 | 8,836 | edison1105 | 跟 vue-core 没关系。先去 unplugin-auto-import 的仓库提一个 issue 吧。 | 2023-07-26T13:12:59 | 2023-07-26T13:12:59 | {} | MEMBER |
vuejs | core | 1,654,836,039 | 8,862 | baiwusanyu-c | I don't think this is a bug. From the compilation results, `auto-import` only imports related components during compilation, while `DynamicComponent` obtains components from the parameters of the render function. The difference between the two leads to different usage methods, especially In the `option api`, you need t... | 2023-07-28T01:20:15 | 2023-07-28T01:20:49 | {} | MEMBER |
vuejs | core | 1,655,734,156 | 8,858 | andrewbrennanfr | After some more debugging - seems that the method `hasDefaultExport` in `vuejs/vue` is the one that's broken for this case & the one in `vuejs/core` is working.
https://github.com/vuejs/vue/blob/main/packages/compiler-sfc/src/rewriteDefault.ts#L91-L93
This regex change [here](https://github.com/vuejs/core/pull/5937... | 2023-07-28T13:55:12 | 2023-07-28T13:55:40 | {} | NONE |
vuejs | core | 1,657,368,858 | 8,872 | edison1105 | this is by design. [see docs](https://vuejs.org/guide/extras/web-components.html#building-custom-elements-with-vue)
 | 2023-07-31T01:37:54 | 2023-07-31T01:37:54 | {} | MEMBER |
vuejs | core | 1,657,441,517 | 8,872 | GuoJikun | Is there any meaning in this design? | 2023-07-31T03:20:47 | 2023-07-31T03:20:47 | {} | NONE |
vuejs | core | 1,646,791,706 | 8,826 | Shyam-Chen | https://vuejs.org/guide/extras/web-components.html
```ts
// vite.config.js
import vue from '@vitejs/plugin-vue'
export default {
plugins: [
vue({
template: {
compilerOptions: {
// treat all tags with a dash as custom elements
isCustomElement: (tag) => tag.includes('... | 2023-07-23T09:25:42 | 2023-07-23T09:25:42 | {} | CONTRIBUTOR |
vuejs | core | 1,651,191,445 | 8,662 | Vanilagy | This is a problem, and it has caused identity issues in my software. Don't see a reason why the proxy behavior for these two structures should diverge to the outside | 2023-07-26T08:09:00 | 2023-07-26T08:09:00 | {} | NONE |
vuejs | core | 1,651,301,172 | 4,309 | woldtwerk | I think the whole custom element api should get a look at. There are a lot of painpoints.
E.g.:
- nested styles
- access to the constructor
- access to the host element
- access to the shadowroot
- prefer constructed stylesheets over style tags
- allow attachElementInternals
- better support for defineExpose/d... | 2023-07-26T09:08:08 | 2023-07-26T09:08:08 | {
"+1": 2
} | NONE |
vuejs | core | 1,653,199,230 | 8,811 | rocifier | Kind of a side question, but isn't it a bit weird that Vue is converting TitleCase props to start with a dash: "-title-case", when <component -title-case="foo" /> isn't really valid as a custom html tag? | 2023-07-27T09:02:15 | 2023-07-27T09:02:15 | {} | NONE |
vuejs | core | 1,653,636,522 | 5,007 | codethief | I suggest we reopen this issue. Vue happily compiles unscoped `<style lang="scss">…</style>` containing `v-bind(my-variable)` and it's completely non-obvious that `my-variable` will not be available when the styles affect HTML elements outside the component's DOM subtree. If v-bind variables are used in *unscoped* styl... | 2023-07-27T13:31:32 | 2023-07-28T14:33:04 | {} | NONE |
vuejs | core | 1,657,352,180 | 8,354 | edison1105 | @yangzl96 I can't reproduce the problem you described. [see demo](https://play.vuejs.org/#eNp9Uk1v2zAM/SuCLraBzAHaW5oWW4se1sM2bDsUmHbwHMZRI1OCProAgf97KclOHbSoDrZEPpLvkTzyL8bUzwH4iq9da6XxzIEP5kag7I22nt0G7zU+Mra1umdFvcyG4krgNmDrpUamdFdWR4GtRqcV1PFdXFwUlcBB4HqZM1NOenjojWo80Iux9ZT9swfn75Rs99eCU7jgN8659VjskcDr5SmSL7h3VGsru/... | 2023-07-31T01:16:40 | 2023-07-31T01:16:40 | {} | MEMBER |
vuejs | core | 1,644,900,486 | 8,817 | yangliguo7 | try to delete `toRaw`
https://play.vuejs.org/#eNqNUstO5DAQ/BXLFzJilIjlNpuJdrLisKwEq2Vvaw4h6QSDY1t+DEFR/p22wzwkHuISxV1VrerqHulG63Trga5obmvDtSMWnNcFk7zXyjgyklr12jtolsRAu/QSv2QirVE9OUHpCZNMtl7WjitJasHrx9I7p+QmWYxMEqIrU/U23VbCQzqcnn5ncvpIU76j+c/oHaO3a3L27fxVymStpHWvNLIOzpJxWJ1NiwPYVK5CaGc/SRbrIjafYWV4x2UlNqbDDnGsZO6HPX... | 2023-07-21T02:28:45 | 2023-07-21T02:28:45 | {
"+1": 1,
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 1,645,033,967 | 7,723 | rudolfbyker | What does "on hold" mean? Do you need anything else from my side? | 2023-07-21T06:12:19 | 2023-07-21T06:12:19 | {
"+1": 1
} | NONE |
vuejs | core | 1,656,112,329 | 8,865 | uktamka | > Id argue that you are then no longer wmittinf an event, really. Emittinf an event means the child is not concerned with what happens with the emitted value.
>
> If your component does depwnd on the return value, defining that as a prop is fine and the way to go.
What if I have a lot of paragraphs in the child c... | 2023-07-28T17:59:06 | 2023-07-28T17:59:06 | {} | NONE |
vuejs | core | 1,657,226,605 | 8,780 | your-brain404 | I've just encountered that strange behaviour. I wish vuejs/core team member would handle that issue. | 2023-07-30T17:32:32 | 2023-07-30T17:32:32 | {} | NONE |
vuejs | core | 1,646,655,259 | 5,952 | michaelpumo | I can't believe it's been 1 year + 2 months since this PR was created and it's still not merged? This is a pretty major bug and the kind of bug that can break applications without realising it. Is this normal? It would be great if we can get this merged in and sorted once and for all. Thanks. | 2023-07-22T19:25:31 | 2023-07-22T19:25:31 | {
"+1": 12
} | NONE |
vuejs | core | 1,646,814,297 | 8,826 | GuoJikun | > https://vuejs.org/guide/extras/web-components.html
>
> ```ts
> // vite.config.js
> import vue from '@vitejs/plugin-vue'
>
> export default {
> plugins: [
> vue({
> template: {
> compilerOptions: {
> // treat all tags with a dash as custom elements
> isCustomElemen... | 2023-07-23T11:23:59 | 2023-07-23T11:23:59 | {} | NONE |
vuejs | core | 1,647,462,808 | 8,348 | ColinLQ | @yyx990803 Using naive-ui will still give you an error:
- "naive-ui": "^2.34.4",
- "vue": "^3.3.4",
```
import type { UploadProps } from 'naive-ui';
export interface Props extends UploadProps {
id?: number;
}
defineProps<Props>();
```
https://stackblitz.com/edit/vitejs-vite-2ewfux?file=src%2Fcompon... | 2023-07-24T08:33:51 | 2023-07-24T08:42:50 | {
"+1": 1
} | NONE |
vuejs | core | 1,651,094,808 | 8,847 | jacekkarczmarczyk | Yes, see https://github.com/vuejs/core/blob/main/packages/runtime-core/src/apiWatch.ts#L208
It may be confusing indeed, if ref's value is an object then the value is a reactive object, probably wording in docs could be improved | 2023-07-26T07:01:56 | 2023-07-26T07:03:59 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,653,256,309 | 1,136 | yuhenabc | you can use global Vue + self write vue.amd.js
global Vue:
```html
<!-- development -->
<script src="https://unpkg.com/vue@3.3.4/dist/vue.runtime.global.js"></script>
<!-- production -->
<script src="https://unpkg.com/vue@3.3.4/dist/vue.runtime.global.prod.js"></script>
```
vue.amd.js:
```js
/* eslint... | 2023-07-27T09:35:45 | 2023-07-27T09:38:03 | {} | NONE |
vuejs | core | 1,644,936,626 | 8,817 | mnm1001 | >
That is works!
Is this because JSON.stringify called all the "params" propety by recursion? | 2023-07-21T03:34:06 | 2023-07-21T03:34:06 | {} | NONE |
vuejs | core | 1,647,040,116 | 8,826 | GuoJikun | Sorry, I had a problem with the previous example, take a look at the following example.
https://stackblitz.com/edit/vitejs-vite-zm8kzw?file=src%2FApp.vue
| 2023-07-24T00:56:01 | 2023-07-24T00:59:18 | {} | NONE |
vuejs | core | 1,648,912,057 | 8,831 | Shyam-Chen | #8373 | 2023-07-25T02:35:55 | 2023-07-25T02:35:55 | {} | CONTRIBUTOR |
vuejs | core | 1,649,305,290 | 6,715 | MehranTaheri | This works for me :
```
<component :is="component" tag="div">
....
....
</component>
const mounted = ref(false);
const component = computed(() => (mounted.value ? TransitionGroup : 'div'));
onMounted(() => {
mounted.value = true;
}); | 2023-07-25T07:46:45 | 2023-07-25T07:48:57 | {
"+1": 3
} | NONE |
vuejs | core | 1,649,549,205 | 2,027 | Dorianslavov | Currently migrating nuxt 2 project to nuxt 3 and I started getting this error as well. What I've noticed is that it doesn't happen because of something specific, but rather because of some other errors happening. For example in my case since we wanted to still use vuex in nuxt 3, I was using `mapActions` but had the wr... | 2023-07-25T10:22:12 | 2023-07-25T10:22:12 | {} | NONE |
vuejs | core | 1,650,899,181 | 8,838 | Atlas-lili | > 使用`import { toRaw } from 'vue';`和`[toRaw(data)]`?
```
<li v-memo="[toRaw(data)]">{{ data.time }}</li>
```
I updated it to the demo. This doesn't seem to work. | 2023-07-26T02:57:17 | 2023-07-26T02:57:17 | {} | NONE |
vuejs | core | 1,651,120,336 | 8,836 | oulong6 | unplugin-auto-import 这个插件并不适合自动导入组件,然后在模板中使用。在模板中使用时,会被解析成_resolveComponent("UiAuto.ButtonA"),这是去获取注册的组件,但UiAuto.ButtonA并没注册,所以会失败。 | 2023-07-26T07:19:39 | 2023-07-26T07:19:39 | {} | NONE |
vuejs | core | 1,653,067,358 | 8,853 | yangliguo7 | ```
<script setup lang="ts">
import { ref, reactive, Directive, DirectiveBinding } from "vue";
const flag = ref(false);
const vHasShow: Directive = (el, binding) => { console.log(el.value, binding.value); };
const list = ref([1, 2, 3]);
const change = () => { list.value = [4, 5, 6]; };
</script>
```
The ... | 2023-07-27T07:39:04 | 2023-07-27T07:39:59 | {} | CONTRIBUTOR |
vuejs | core | 1,657,110,289 | 8,873 | so1ve | Did some benchmarks and here is the result:
```
hoisted x 1,613,160 ops/sec ±1.61% (90 runs sampled)
non-hoisted x 1,574,592 ops/sec ±0.83% (94 runs sampled)
```
Small improvements 😅 | 2023-07-30T11:08:01 | 2023-07-30T11:08:01 | {} | MEMBER |
vuejs | core | 1,649,639,440 | 8,457 | vaban-ru | 
Same issue here | 2023-07-25T11:18:37 | 2023-07-25T11:18:37 | {
"+1": 14,
"confused": 2
} | NONE |
vuejs | core | 1,650,830,188 | 8,838 | Shyam-Chen | Use `import { toRaw } from 'vue';` and `[toRaw(data)]`? | 2023-07-26T01:31:34 | 2023-07-26T01:31:34 | {} | CONTRIBUTOR |
vuejs | core | 1,653,801,571 | 8,861 | jc840031139 | 如果改成watchPostEffect 也不会出现无限循环的错误 但我想知道这是为什么 | 2023-07-27T15:01:05 | 2023-07-27T15:01:05 | {} | NONE |
vuejs | core | 1,653,992,579 | 8,863 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | e3b9f45fb63c7b74e787ab4344c603dd8d4fbf3a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-07-27T16:52:46 | 2023-07-27T16:52:46 | {} | NONE |
vuejs | core | 1,656,136,745 | 8,865 | uktamka | > If you need a result from the handler then use `defineProps` instead of `defineEmits`
>
> > And why do we have in defineEmits return type if emits always return void?
>
> You don't need to, you can use the syntax that doesn't require providing a return type (see Vue docs for details)
Yes, but we can specify ... | 2023-07-28T18:15:52 | 2023-07-28T18:15:52 | {} | NONE |
vuejs | core | 1,657,130,783 | 8,873 | baiwusanyu-c | tql!Ray! | 2023-07-30T12:45:12 | 2023-07-30T12:45:12 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,651,767,083 | 8,849 | edison1105 | duplicate of https://github.com/vuejs/core/issues/8775
It will be fixed via https://github.com/vuejs/core/pull/8671/files, But https://github.com/vuejs/core/issues/8775 describes that it only happens on Windows, Could you test if #8775 will fix your problem as well? | 2023-07-26T13:05:04 | 2023-07-26T13:10:09 | {} | MEMBER |
vuejs | core | 1,653,008,493 | 8,853 | pythonliuwei-root | my App.vue code is <template>
<div>
<button v-has-show="list" @click="change">change</button>
</div>
</template>
<script setup lang="ts">
import { ref, reactive, Directive, DirectiveBinding } from "vue";
const flag = ref(false);
const vHasShow: Directive = (el, binding) => {
console.log(el.value, b... | 2023-07-27T06:48:53 | 2023-07-27T06:48:53 | {} | NONE |
vuejs | core | 1,653,038,440 | 6,829 | Heniker | Wouldn't it make sense to have some way to define directive target on multi-root components? Since `v-bind="$attrs"` already works fine in such cases for everything besides directives. | 2023-07-27T07:15:46 | 2023-07-27T07:15:46 | {} | NONE |
vuejs | core | 1,653,073,863 | 8,854 | Shyam-Chen | ```vue
<script setup>
function click() {
window.alert('ouch');
}
</script>
<template>
<button
@click="
click();
click();
"
>
Click Me
</button>
</template>
``` | 2023-07-27T07:43:47 | 2023-07-27T08:11:57 | {} | CONTRIBUTOR |
vuejs | core | 1,653,112,551 | 8,854 | ateirney | @Shyam-Chen I am aware that adding semicolons will make it work.
I came across this when looking to port a vue2-based application to vue-3 that uses prettier formatting without semicolons.
An example formatting via prettier can be seen in this [prettier-playground](https://prettier.io/playground/#N4Igxg9gdgLgprEA... | 2023-07-27T08:10:03 | 2023-07-27T08:35:39 | {} | NONE |
vuejs | core | 1,653,286,947 | 4,980 | guohuihot | [unplugin-vue-macros](https://vue-macros.sxzz.moe/macros/define-render.html)
defineRender ^_^
I hope the official can support it | 2023-07-27T09:54:37 | 2023-07-27T09:55:46 | {
"+1": 1,
"hooray": 1
} | NONE |
vuejs | core | 1,653,806,047 | 8,842 | pleek91 | @Shyam-Chen There are a few key differences between computed and getters which are outlined quite well in https://github.com/vuejs/core/pull/7997. Both methods you've suggested are possible and useful. However they are functionally and performantly differently than being able to pass a getter that is then normalized in... | 2023-07-27T15:02:41 | 2023-07-27T15:02:41 | {} | NONE |
vuejs | core | 1,655,457,120 | 8,866 | LinusBorg | ou might be missing that refs are unwrapped in the template?
count2' value is unitially undefined, bzr you try to read a property on it. That will necessarily lead to an error. | 2023-07-28T10:31:08 | 2023-07-28T10:31:08 | {} | MEMBER |
vuejs | core | 1,656,788,704 | 6,745 | tsboh | I fixed this error by changing the **place of the _v-if_**
The transition worked when 'isOpen' became true. The error occurred when 'isOpen' became false.
After changing the place of the _v-if_ from:
```
<TransitionGroup name="pos-items-list"
enter-active-class="transition duration-100 ease-out"
enter-f... | 2023-07-29T16:54:07 | 2023-07-29T16:54:07 | {} | NONE |
vuejs | core | 1,645,187,985 | 5,477 | paul-thebaud | Hello @yyx990803 @LinusBorg, I'm here again for a reminder (sorry).
Could you please inspect this issue? Looks like the work is done, only a review is required.
This will fix or avoid major issues with some frameworks passing attributes as camel case strings.
Thank you. | 2023-07-21T08:12:05 | 2023-07-21T08:12:05 | {
"eyes": 6
} | NONE |
vuejs | core | 1,646,875,012 | 8,826 | baiwusanyu-c | https://stackblitz.com/edit/vitejs-vite-gtl19y?file=src%2FApp.vue
My local works fine | 2023-07-23T15:53:11 | 2023-07-23T15:54:00 | {} | MEMBER |
vuejs | core | 1,650,927,121 | 8,842 | Shyam-Chen | ```html
<DateLabel :value="dateGetter()" />
``` | 2023-07-26T03:35:54 | 2023-07-26T03:35:54 | {} | CONTRIBUTOR |
vuejs | core | 1,651,512,530 | 8,733 | yangliguo7 | The second function ( `console.log("Rerender App");` ) execution is because `unmount ` was executed during `patch`.
u can set a unique key to avoid it .
https://play.vuejs.org/#eNqVVU1z0zAQ/StClzgzic20nExaCp0c4ACdwi3qwbU3iVpZMpLshvH4v7OS7MQJhI8eamv3+e2nXlr6vqripgaa0oXJNa8sEZncXDFqDaPXTPKyUtqSlmxnpIA1l3Cr0CRB2hnR... | 2023-07-26T10:30:50 | 2023-07-26T10:33:08 | {} | CONTRIBUTOR |
vuejs | core | 1,653,051,792 | 8,613 | yangliguo7 | As we know. template converted to dom need `compiler -> render -> patch-> dom `
check the compiler code
```
function render(_ctx, _cache, $props, $setup, $data, $options) {
return (_openBlock(), _createElementBlock(_Fragment, null, [
_createTextVNode(_toDisplayString(_ctx.count) + " ", 1 /* TEXT */),
... | 2023-07-27T07:26:52 | 2023-07-27T07:27:14 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,653,135,495 | 8,627 | rocifier | cannot reproduce anymore, was fixed by the above PR. please close this issue. | 2023-07-27T08:24:29 | 2023-07-27T08:24:29 | {} | NONE |
vuejs | core | 1,653,992,379 | 8,863 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | e3b9f45fb63c7b74e787ab4344c603dd8d4fbf3a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-07-27T16:52:37 | 2023-07-27T16:52:37 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.