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,405,553,457
7,581
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 0fbc19f2d034a3a50f5c9114ae58bf8f06cf241d | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-26T19:54:34
2023-01-26T20:04:08
{}
NONE
vuejs
core
1,405,597,322
7,584
liuseen-l
I submitted the same PR a few times before, but I happened to encounter that vue/core are migrating from jest to vitest, pr had a lot of problems, and I am now resubmitting to vitest's version
2023-01-26T20:16:22
2023-01-26T20:16:22
{}
CONTRIBUTOR
vuejs
core
1,407,586,710
6,926
edison1105
@earlAchromatic > For instance, if I am prerendering and then want to lazily hydrate some components but still have the css vars initially bound so styles show up. Lazily hydrate is not supported by vue-core, Maybe you have to wait until Q2. The final implementation is uncertain and may not be the same as Astro. N...
2023-01-29T07:30:10
2023-01-29T07:30:10
{}
MEMBER
vuejs
core
1,407,766,505
7,583
liuseen-l
@sxzz
2023-01-29T20:51:24
2023-01-29T20:51:24
{}
CONTRIBUTOR
vuejs
core
1,409,948,290
7,606
posva
hmm, maybe something after cd7c887b755810aedf83f3d458cb956d5b147f6f broke this then? because it fails on the latest commit on the main branch
2023-01-31T08:22:42
2023-01-31T08:22:42
{}
MEMBER
vuejs
core
1,412,092,034
7,576
edison1105
The root cause is: the `findInsertionIndex` function returns the same index when job.id is equal, resulting in a misordering of the jobs in the queue. https://github.com/vuejs/core/blob/957722c4185ea87aabc711f6f8997e528dd3ba1b/packages/runtime-core/src/apiWatch.ts#L362 this resulted in the same jobId
2023-02-01T13:51:07
2023-02-01T13:51:07
{ "+1": 1 }
MEMBER
vuejs
core
1,413,264,146
7,578
edison1105
see https://github.com/vuejs/core/issues/574 I feel the docs should be updated. @LinusBorg WDYT
2023-02-02T07:23:32
2023-02-02T07:24:17
{}
MEMBER
vuejs
core
1,406,019,594
5,525
liulinboyi
> I experienced this issue yesterday in the newest Vue version. Only in Vite build not in Vite dev. > > With the wrapper it worked in both. So this issue is still relevant? Can you provide a minimum reproduction? Thanks.
2023-01-27T04:52:12
2023-01-27T04:52:12
{}
MEMBER
vuejs
core
1,407,062,601
7,590
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | ca3c029250c2d09f365baf090f5cb4afe39294d8 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-27T20:53:02
2023-01-27T20:53:02
{}
NONE
vuejs
core
1,407,389,566
7,594
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 2e6ac016927a5b98373e2272e329a96ce84b8432 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-28T12:32:57
2023-01-28T12:32:57
{}
NONE
vuejs
core
1,405,297,576
7,326
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 66e84f81976f3841777d514c7955d31d47f732e2 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-26T16:48:57
2023-01-29T19:54:49
{}
NONE
vuejs
core
1,407,882,204
7,458
LeaVerou
@LinusBorg Just figured I'd post an update, since both polls have now closed. [Twitter poll](https://twitter.com/LeaVerou/status/1614281677014016003): <img width="598" alt="image" src="https://user-images.githubusercontent.com/175836/215372123-188c5150-5128-4a1b-ad4b-30af233fd336.png"> Note that the ratio of ...
2023-01-30T02:08:25
2023-01-30T02:08:25
{}
NONE
vuejs
core
1,410,595,101
7,611
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 87567ec858ef243fae739c85077d908274180e3a | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-31T15:32:58
2023-01-31T16:01:07
{}
NONE
vuejs
core
1,411,734,149
7,617
haoqunjiang
/ecosystem-ci run
2023-02-01T09:28:52
2023-02-01T09:28:52
{}
MEMBER
vuejs
core
1,411,859,712
7,590
pi0
Thanks for quick feedback @yyx990803 > since currentInstance isn't the only global singleton that the Vue runtime relies on. Some other examples include the reactivity tracking maps and built-in VNode type symbols like Text or Fragment. Indeed. But at least in Nuxt projects, currentInstance and SSR instance were...
2023-02-01T10:53:40
2023-02-01T10:53:40
{}
NONE
vuejs
core
1,413,080,732
7,116
yyx990803
@godxiaoji Thank you very much for the PR - @sxzz came up with a better alternative in #7619 that retains the ability to jump to definition on props properties, but we really appreciate your contribution!
2023-02-02T02:58:54
2023-02-02T02:58:54
{}
MEMBER
vuejs
core
1,413,345,633
7,606
posva
Now I see that the import maps were version-fixed and had the wrong version of Vue 🥲
2023-02-02T08:41:34
2023-02-02T08:41:34
{}
MEMBER
vuejs
core
1,407,418,585
6,745
jonaskuske
@locki13freja What does the template of `PostItem` look like?
2023-01-28T15:12:06
2023-01-28T15:12:06
{}
CONTRIBUTOR
vuejs
core
1,407,424,053
7,329
MichaelDeBoey
@ice1000 Unfortunately it's reversed 😢 https://github.com/remorses/esbuild-plugins/issues/28#issuecomment-1406309742
2023-01-28T15:36:50
2023-01-28T15:36:50
{ "eyes": 3 }
NONE
vuejs
core
1,410,086,824
7,601
AlexVagrant
https://github.com/vuejs/core/blob/7d0c63ff4361e59e820441a24bf4fb2a93335a1e/packages/runtime-dom/src/directives/vModel.ts#L251 getCheckboxValue define _typeValue and _falseValue type is `_trueValue?: any _falseValue?: any` https://github.com/vuejs/core/blob/c6eb3ccccee8e43e7aafcbc3c9ededecc565fdf0/packages/runtim...
2023-01-31T10:09:56
2023-01-31T10:09:56
{}
CONTRIBUTOR
vuejs
core
1,411,780,012
7,184
Evertvdw
Can this be merged?
2023-02-01T09:58:43
2023-02-01T09:58:43
{}
NONE
vuejs
core
1,313,218,348
7,113
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 446498a55de9421f637f176bf9f199d8f11bf0de | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2022-11-14T07:39:05
2023-01-26T17:10:45
{}
NONE
vuejs
core
1,405,331,359
7,398
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | be7830141b390200772ceb71b47a51d5e743d4e5 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-26T17:12:53
2023-01-26T17:12:53
{}
NONE
vuejs
core
1,405,332,414
7,365
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 7b32568e28ff4b7f271c34e694e40cda98011340 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-26T17:13:40
2023-01-26T17:13:40
{}
NONE
vuejs
core
1,405,539,617
7,583
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 0cb451f5056f3e1e7c1a15edf6b00a6aa0decfc7 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-26T19:47:58
2023-01-30T06:44:39
{}
NONE
vuejs
core
1,408,322,133
7,048
sxzz
@klausXR `Awaited` I provided is not the same as the TypeScript built-in one.
2023-01-30T10:04:27
2023-01-30T10:04:27
{}
MEMBER
vuejs
core
1,413,192,950
7,623
yyx990803
fixed via 4b703665 (out in 3.2.47)
2023-02-02T05:55:32
2023-02-02T05:55:32
{ "rocket": 1 }
MEMBER
vuejs
core
1,408,822,983
7,606
posva
Trasfered from pinia and updated the reproduction. This is similar to https://github.com/vuejs/core/issues/7319 but not exactly the same. Use a regular `watch()` as a workaround.
2023-01-30T15:25:00
2023-01-30T15:26:25
{}
MEMBER
vuejs
core
1,411,422,270
7,613
edison1105
duplicate of https://github.com/vuejs/core/issues/6483
2023-02-01T03:50:23
2023-02-01T03:50:23
{}
MEMBER
vuejs
core
1,411,737,604
5,996
yyx990803
The original problematic code is no longer present after https://github.com/vuejs/core/commit/78c199d6dbe8931520b75d8bfe0d49366a06922a which was released in 3.2.38, so the issue should no longer be relevant.
2023-02-01T09:31:21
2023-02-01T09:31:21
{}
MEMBER
vuejs
core
1,412,486,201
7,620
MisterGoodcat
Hi Thorsten, thanks for the fast response. I can understand this, but I'm still curious why this works when both computed properties are used side by side, and also why it works for multiple instances of the same (directly manipulated) property in different places. I updated your sample with another missing ".value"...
2023-02-01T17:57:15
2023-02-01T18:07:02
{}
NONE
vuejs
core
1,412,539,455
7,614
yurivish
Thank you for the great explanation, @skirtles-code. The issue you linked containing explanations of problems with reactivity is also very useful. I think my mistake here was actually in not understanding how props are passed – I knew that that triggering a ref without changing its value would cause re-evaluation on...
2023-02-01T18:38:32
2023-02-01T18:42:12
{}
NONE
vuejs
core
1,102,164,505
5,752
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 02081e08004a02c758526862e6ab3794e9707f42 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2022-04-19T06:59:46
2023-01-26T17:14:57
{}
NONE
vuejs
core
1,405,339,492
7,394
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 522d6bccd3e615e5914d16eb2f11b223fc03afa8 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-26T17:19:15
2023-01-26T17:19:15
{}
NONE
vuejs
core
1,406,010,847
7,586
ccmetz
@code-ManL appreciate the comment! I know that type casting will make the error go away but was mostly curious if this is something that can be addressed in a future version of Vue. After doing some more digging, I stumbled across #2981 and it appears that it would be pretty difficult.
2023-01-27T04:37:16
2023-01-27T04:37:16
{}
NONE
vuejs
core
1,412,550,373
7,620
LinusBorg
I'm not sure what Im supposed to look for in that second example. Generally said: * Vue tracks property reads, and re-reruns effects (i.e.: rendering) when those properties are being set. * Each component tracks its own reactive dependencies * In your example, the first two child components components only tra...
2023-02-01T18:48:02
2023-02-01T18:49:22
{}
MEMBER
vuejs
core
1,384,938,093
7,548
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed. | Name | Link | |---------------------------------|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | 182c253e08faf0b0d475d7e38929f6a0d9fc9e74 | |<span aria-hidden="true">🔍</span> Latest deploy log | https:/...
2023-01-17T07:24:18
2023-01-26T17:20:36
{}
NONE
vuejs
core
1,406,007,412
7,586
liuseen-l
You can try using type assertions, like this testFunc(customArray.value as CustomClass[]);
2023-01-27T04:31:46
2023-01-27T04:31:46
{}
CONTRIBUTOR
vuejs
core
1,527,171,196
7,871
KaygNas
> The prefix 'on' is considered an event. It is not recommended to use the 'on' prefix as a boolean attribute. Maybe some warning print on console would be better? Developer could be hinted by the warning and realize where the problem are when they stuck into this situation.
2023-04-28T08:16:41
2023-04-28T08:16:41
{}
NONE
vuejs
core
1,519,185,979
5,525
Seanitzel
Also spent a bit of time on this, the way it works for me: ```vue <script setup> const items = ['i1', 'i2', 'i3']; const elRefs = reactive([]); function updateRefs(el, index) { elRefs[index] = el; } </script> <template> <div> <div v-for="item, index in items" :key="index" :ref="(e...
2023-04-23T22:46:35
2023-04-28T14:50:31
{}
NONE
vuejs
core
1,505,136,397
4,294
ahl-asg
I am having a hard time reconciling that I cannot import interfaces for defineProps. When I can do this as a workaround. `interface props extends InterfaceProps {}` Why can i not directly use the imported type?
2023-04-12T11:52:23
2023-04-29T11:39:40
{ "+1": 1 }
NONE
vuejs
core
1,529,483,413
6,610
s3fs
Hello @LinusBorg @yyx990803, Could you please evaluate this PR and see if this could be a valid fix for #4662 issue? Thanks a lot!
2023-05-01T08:32:27
2023-05-01T08:32:27
{ "+1": 1 }
NONE
vuejs
core
1,537,668,454
6,819
mrchar
I realy need this feature, is this feature likely to be merged? when will it be available?
2023-05-08T03:01:18
2023-05-08T03:01:18
{}
NONE
vuejs
core
1,537,694,784
8,247
yyx990803
This is not a Vue issue and should be reported to [Vite](https://github.com/vitejs/vite) instead, also make sure to provide a proper reproduction by creating a GitHub repository with your code.
2023-05-08T03:43:51
2023-05-08T03:44:01
{}
MEMBER
vuejs
core
1,537,836,153
8,252
haoqunjiang
/ecosystem-ci run
2023-05-08T06:42:24
2023-05-08T06:42:24
{}
MEMBER
vuejs
core
1,527,046,858
7,804
yyx990803
This should have been resolved in 3.3 beta and latest Volar already.
2023-04-28T06:17:53
2023-04-28T06:17:53
{ "+1": 1 }
MEMBER
vuejs
core
1,531,358,450
6,913
edison1105
a workaround see https://github.com/vuejs/core/issues/8203#issuecomment-1531347186
2023-05-02T12:09:10
2023-05-02T12:09:10
{}
MEMBER
vuejs
core
1,527,096,997
8,171
StepanMynarik
@yyx990803 Running ```vue-tsc --noEmit``` gives no errors. Errors happen right after running ```npx vite```, so it is as @johnsoncodehk says. **Full error description:** `Error: Failed to scan for dependencies from entries: E:/Downloads/Test/vue-project/index.html X [ERROR] Unexpected "," script...
2023-04-28T07:09:41
2023-05-04T06:50:20
{}
NONE
vuejs
core
1,536,081,861
8,235
xflyyxfl
> 你可以不用vmodel跟watch,绑定value跟@input来判断,或者@change然后逻辑赋值吧 也不是不可以,但是这样肯定是比直接任何地方一个v-model绑定要麻烦。 而且,我这样使用是有什么‘不合理’/‘违反xx原则’/‘故意挠痛点’之类的问题吗 有空了我去扒下原码,看下为什么这样
2023-05-05T10:57:51
2023-05-05T10:57:51
{}
NONE
vuejs
core
1,536,092,609
4,733
rdunk
@mika76 What is your definition of "with text in it"? It checks for empty text nodes, i.e. when the node is of type Text but the node doesn't actually contain content.
2023-05-05T11:07:14
2023-05-05T11:07:14
{}
NONE
vuejs
core
1,537,435,695
8,247
xiaohongju
> Please provide a project that can reproduce the problem so that the problem can be located How can I present my code?At github
2023-05-07T12:57:08
2023-05-07T12:57:08
{}
NONE
vuejs
core
1,524,088,041
7,942
johnp
Works similarly well as https://github.com/vuejs/core/pull/6610 and solves https://github.com/vuejs/core/issues/4662. (~~requires enabling custom element mode in vite-plugin-vue; works for build and HMR~~) With this PR, under some circumstances, the style tags are duplicated, see for example: - https://stackblitz...
2023-04-26T21:50:41
2023-05-07T20:36:08
{}
NONE
vuejs
core
1,529,030,477
8,186
nined9
> > 你应该是将props弄成响应式 而不是里面的值弄成响应式 > > ``` > > <template> > > <component :is="Comp" v-bind="props" /> > > </template> > > > > <script setup> > > import { onMounted, ref, computed, defineComponent } from 'vue' > > import Comp from './Comp.vue' > > > > const tmp = ref(true) > > const props = computed(()=>{...
2023-04-30T13:50:27
2023-04-30T13:50:27
{}
NONE
vuejs
core
1,533,569,061
8,083
brolnickij
@yyx990803 should we expect this feature in `vue@2.7`? thank you!
2023-05-03T19:16:16
2023-05-03T19:19:34
{ "eyes": 3 }
NONE
vuejs
core
1,535,958,971
4,733
rdunk
> BTW I find `asArray()` generally useful and would allow it any argument types, nut just VNodes Been using these helpers for a couple of weeks, updated my comment to add another check in `isVNodeEmpty` for empty text nodes that I've found useful. Also updated `asArray` for flexibility as you suggested @lehni.
2023-05-05T09:07:26
2023-05-05T09:07:26
{}
NONE
vuejs
core
1,536,068,042
8,235
xflyyxfl
> 你想实时监听就别用lazy呗 我是在正式项目使用中遇到的问题,不使用lazy可能导致逻辑问题。 比如我有个参数输入范围是10-100,用户想输入52,但是在他输第一个5的时候就触发的watch,那么对他的输入检测不合法,强行进行修改。就会导致用户无法输入他想要的值。
2023-05-05T10:44:01
2023-05-05T10:44:01
{}
NONE
vuejs
core
1,537,066,733
8,240
baiwusanyu-c
`{ immediate: true, deep: true }` 这会导致组件进入时直接运行一次回调,在回调中你修改了监听的对象这会导致回调再次触发造成崩溃,我不认为这是一个好的或者说是一个规范的用法 `{ immediate: true, deep: true }` This will cause a callback to be run directly when the component enters. In the callback, you modify the listening object, which will cause the callback to trigger again and cause a c...
2023-05-06T06:31:02
2023-05-06T06:31:12
{}
MEMBER
vuejs
core
1,527,181,355
8,177
Shyam-Chen
```vue <script lang="ts" setup> const modelValue = defineModel<string>({ default: '' }); </script> <template> <input v-model="modelValue" /> </template> ``` ```vue <script lang="ts" setup> import { ref } from 'vue'; import TextField from '~/components/TextField.vue'; const val = ref(''); </script...
2023-04-28T08:25:51
2023-04-28T08:37:30
{}
CONTRIBUTOR
vuejs
core
1,527,322,737
8,186
Dlouxgit
> 你应该是将props弄成响应式 而不是里面的值弄成响应式 > > ``` > <template> > <component :is="Comp" v-bind="props" /> > </template> > > <script setup> > import { onMounted, ref, computed, defineComponent } from 'vue' > import Comp from './Comp.vue' > > const tmp = ref(true) > const props = computed(()=>{ > return { > ...
2023-04-28T10:10:44
2023-04-28T10:10:44
{}
NONE
vuejs
core
1,527,761,072
8,194
LinusBorg
This is known and wont' be supported before 3.3 (currently in beta)
2023-04-28T15:50:17
2023-04-28T15:50:17
{}
MEMBER
vuejs
core
1,527,766,116
7,871
LinusBorg
> > The prefix 'on' is considered an event. It is not recommended to use the 'on' prefix as a boolean attribute. > > I appreciate that but this is not obvious from the docs and it is something that is difficult to change in large applications when moving from Vue 2 to Vue 3. You're right in that docs would profit...
2023-04-28T15:54:53
2023-04-28T15:55:52
{}
MEMBER
vuejs
core
1,530,784,487
8,179
yyx990803
This is not something we will consider, because it makes the markup no longer syntactically valid HTML.
2023-05-02T02:30:02
2023-05-02T02:30:02
{}
MEMBER
vuejs
core
1,531,432,044
8,203
nined9
> duplicate of #6913 as a workaround > > ```js > const icon = computed(() => { > setBlockTracking(-1) > const res = h(BackTopIcon) > setBlockTracking(1) > return res > }); > ``` 好的,感谢确认! 这里为了保持向前兼容,setBlockTracking方法就必须保持public了,直到有新的api来处理这种情况 想问下这块有没有计划进行优化,以提供更简便的实现...
2023-05-02T12:58:10
2023-05-02T12:58:10
{}
NONE
vuejs
core
1,536,055,953
8,235
wsw2000
看你的例子,你使用了v-model.lazy, 只有在按回车或者输入框失去聚焦后才会触发watch的
2023-05-05T10:32:07
2023-05-05T10:32:07
{}
NONE
vuejs
core
1,537,065,425
8,240
Cqqgyh
> 在您提供的复制项目中,我没有找到任何可以触发更改的地方,因此无法定位问题。请提供更多有效信息`part2RightTextList` en:You don't need to trigger it intentionally, or you can write any trigger you like. If the code contains a **watch** command and is configured with **{immediate: true, deep: true}**, and you execute **vite build**, followed by **vite preview**, a...
2023-05-06T06:23:34
2023-05-06T06:23:34
{}
NONE
vuejs
core
1,537,067,429
8,240
Cqqgyh
> `{ immediate: true, deep: true }` 这会导致组件进入时直接运行一次回调,在回调中你修改了监听的对象这会导致回调再次触发造成崩溃,我不认为这是一个好的或者说是一个规范的用法 `{ immediate: true, deep: true }` This will cause a callback to be run directly when the component enters. In the callback, you modify the listening object, which will cause the callback to trigger again and cause a ...
2023-05-06T06:35:08
2023-05-06T06:35:08
{}
NONE
vuejs
core
1,526,948,204
8,180
qmhc
Now I using `customRef` to imrpove this: ```ts import { customRef } from 'vue' const triggerSet = new Set<() => void>() function manualRef<T>(value: T) { return customRef<T>((track, trigger) => { let origin = value const update = () => { if (value !== origin) { origin = value ...
2023-04-28T03:54:49
2023-04-28T03:56:01
{}
NONE
vuejs
core
1,531,256,715
6,463
theguriev
Same issue on my side :(
2023-05-02T10:45:16
2023-05-02T10:45:16
{}
NONE
vuejs
core
1,512,876,503
4,733
rdunk
TS version of @lehni's helpers in case it's useful for anyone else: ```ts import { Comment, Text, type Slot, type VNode } from 'vue'; export function hasSlotContent(slot: Slot | undefined | null, props: any = {}) { return !isSlotEmpty(slot, props); } export function isSlotEmpty(slot: Slot | undefined | nu...
2023-04-18T10:59:35
2023-05-05T09:04:51
{ "+1": 4, "heart": 3 }
NONE
vuejs
core
1,527,686,394
5,525
Seanitzel
@madsh93 Oops my bad, messed up the rewrite from my code to the comment lol Edited my comment, should be clear now :)
2023-04-28T14:51:18
2023-04-28T14:51:38
{}
NONE
vuejs
core
1,528,999,441
8,197
LinusBorg
#7329
2023-04-30T11:16:12
2023-04-30T11:16:12
{ "+1": 1 }
MEMBER
vuejs
core
1,530,776,347
8,207
yyx990803
This is expected behavior - `ssrPrefetch` is bound to the component lifecycle, and they only get called when the component is rendered by its parent. It has to work that way because `ssrPrefetch` has access to the component's props - and props can only be resolved when the parent is rendered. Note this is not something...
2023-05-02T02:19:09
2023-05-02T02:19:09
{}
MEMBER
vuejs
core
1,533,114,613
8,218
VividLemon
> Is it possible to use this `.join(' ')`? For a simple string[], yes, but not with objects no
2023-05-03T14:20:07
2023-05-03T14:20:07
{}
NONE
vuejs
core
1,533,219,730
2,775
benjsmyth
I had this problem for objects that I was injecting into my component. For anyone having problems with typing injected data, the solution is to [use the Composition API](https://vuejs.org/guide/typescript/composition-api.html#typing-provide-inject) instead.
2023-05-03T15:13:00
2023-05-03T15:13:38
{}
NONE
vuejs
core
1,535,941,199
4,344
lisilinhart
For me the error disappeared when I installed the dependency in the root project with `npm` instead of `yarn`. I also setup the lib similar to this vite configuration (https://github.com/ferryanggriawan/vue3-plugin-boilerplate/blob/master/vite.config.ts) and tried all the things recommended on this thread, but really ...
2023-05-05T08:55:25
2023-05-05T08:55:25
{}
NONE
vuejs
core
1,535,961,073
8,171
yyx990803
This error is upstream in Vite core - I've created a fix PR at https://github.com/vitejs/vite/pull/13101 Closing this one to track in Vite instead.
2023-05-05T09:08:59
2023-05-05T09:08:59
{}
MEMBER
vuejs
core
1,536,331,141
8,235
xflyyxfl
我在官方源码里面已经找到原因了,但是对于官方尤大这样的选择仍然不太清楚,可能是基于某些需求下的考量: 当某个input用lazy绑定的响应式在变化时,用户如果刚好也在编辑这个输入,那么变化的数据为了不影响用户的编辑,不会主动更新这个值到输入框; 好处是上面的这种情况,以用户输入体验为主。坏处就是当开发者想主动更新时就会发生问题。 示例代码仍然在https://codepen.io/xflyyxfl-the-typescripter/pen/poxpwKK?editors=1010 ///// I have found the reason in the official source code, but i...
2023-05-05T14:17:08
2023-05-05T14:17:08
{}
NONE
vuejs
core
1,537,029,621
7,942
netlify[bot]
### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed. | Name | Link | |:-:|------------------------| |<span aria-hidden="true">🔨</span> Latest commit | eedf48f675ec10883e357b1a89efd8cb899cfb2f | |<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s...
2023-05-06T03:14:48
2023-05-06T03:14:48
{}
NONE
vuejs
core
1,274,538,097
4,662
leokolezhuk
+1 Urgently need this too!
2022-10-11T11:31:12
2023-04-28T03:26:19
{}
NONE
vuejs
core
1,529,355,811
7,677
mrleblanc101
@LinusBorg @yyx990803 How are pending PR reviewed/managed ? Any chance that this will get merged with 3.3 ?
2023-05-01T05:10:21
2023-05-01T05:10:21
{}
NONE
vuejs
core
1,532,863,278
8,214
leonardorafael
Hi @LinusBorg Retuning a number as string, is not a good practice and may cause some side effects: 1) Changing type at runtime is not a good practice (and breaks the Typescript type previously defined) 2) If you have to calculate, all calculated values will be string, it's like a virus 3) If you have to send ...
2023-05-03T11:25:27
2023-05-03T12:48:25
{}
NONE
vuejs
core
1,536,065,242
8,235
wsw2000
你想实时监听就别用lazy呗
2023-05-05T10:41:53
2023-05-05T10:41:53
{}
NONE
vuejs
core
1,536,077,091
8,235
wsw2000
你可以不用vmodel跟watch,绑定value跟@Input来判断,或者@change然后逻辑赋值吧
2023-05-05T10:52:54
2023-05-05T10:52:54
{}
NONE
vuejs
core
1,537,768,592
8,178
icarusgk
It has already been discussed before [in this PR](https://github.com/vuejs/vue/pull/2877). See [Evan's comment](https://github.com/vuejs/vue/pull/2877#issuecomment-226618510) on it. 👀 I do like the idea, and a lot of the community has proposed the same idea over the years at least 10 times `(See the PR for referenc...
2023-05-08T05:18:40
2023-05-08T05:23:53
{ "+1": 4 }
NONE
vuejs
core
1,532,684,657
8,216
Shyam-Chen
You can use the `vue/no-mutating-props` rule in ESLint.
2023-05-03T09:06:20
2023-05-03T09:07:13
{}
CONTRIBUTOR
vuejs
core
1,532,692,380
8,218
Shyam-Chen
Is it possible to use this `.join(' ')`?
2023-05-03T09:11:36
2023-05-03T09:11:36
{}
CONTRIBUTOR
vuejs
core
1,536,645,829
8,178
AntonyZ89
You can use `v-bind` ```vue <Component v-bind="{ data }" /> ```
2023-05-05T18:52:50
2023-05-05T18:52:50
{ "+1": 2 }
NONE
vuejs
core
1,302,635,692
4,662
ucjonathan
+10 Urgently need this too!
2022-11-03T20:36:29
2023-04-28T03:26:26
{}
NONE
vuejs
core
1,532,485,534
8,219
gme-gpl
## 我建议直接禁止二者应用在同一级中, 因为这会造成一定的认知歧义 (I don't think using both directives on the same level is a good idea, as it creates some cognitive ambiguity) ### 针对第一种情况, 你可以写成 (For the first situation, you can write) ```vue <div v-for="(value, key, index) in list.map(item => item.value.size === 20)"></div> ``` ### 针对第二种情...
2023-05-03T05:59:18
2023-05-03T05:59:18
{}
NONE
vuejs
core
1,532,604,223
8,216
edison1105
The warning should also be displayed in development mode
2023-05-03T08:00:47
2023-05-03T08:00:47
{ "hooray": 1 }
MEMBER
vuejs
core
1,535,569,282
8,228
Mini-ghost
This seems to be an inconsistency issue that arose to address #8201, which I didn't notice. Perhaps this issue should be closed.
2023-05-05T00:57:01
2023-05-05T00:57:01
{}
CONTRIBUTOR
vuejs
core
1,535,873,667
8,228
yyx990803
This should be considered intended behavior - the previous `provide()` types were not strict enough and allowing incompatible types to be provided. After the change it is now correctly catching type errors that should be fixed. In your case, you are indicating that you are providing a `WritableComputedRef` but actua...
2023-05-05T07:53:46
2023-05-05T07:53:46
{ "heart": 1 }
MEMBER
vuejs
core
1,536,965,963
8,234
btea
It seems to have been duplicated with #8211..
2023-05-06T01:31:50
2023-05-06T01:31:50
{}
CONTRIBUTOR
vuejs
core
1,537,419,470
8,247
baiwusanyu-c
Please provide a project that can reproduce the problem so that the problem can be located
2023-05-07T11:44:07
2023-05-07T11:44:07
{}
MEMBER
vuejs
core
1,537,435,350
8,247
xiaohongju
> @xiaohongju i think you should just externalize `fsevents` in your vite config ` optimizeDeps: { exclude: ['fsevents'], },` thanks,I have already tried,but The problem is still unresolved
2023-05-07T12:55:48
2023-05-07T12:55:48
{}
NONE
vuejs
core
1,537,618,550
7,268
godxiaoji
May I ask when this PR will be merged? This compatibility issue may have a significant impact on the business.
2023-05-08T01:33:25
2023-05-08T01:33:25
{ "+1": 2, "eyes": 1 }
CONTRIBUTOR
vuejs
core
1,527,047,461
8,171
yyx990803
This seems to be a regression in Volar when paired with 3.2.x - /cc @johnsoncodehk
2023-04-28T06:18:46
2023-04-28T06:18:46
{}
MEMBER
vuejs
core
1,527,057,338
8,172
yyx990803
This is not a bug. When you wrap the return type with `reactive`, the properties are unwrapped and are no longer refs. The type error you are seeing is expected behavior.
2023-04-28T06:31:04
2023-04-28T06:31:04
{}
MEMBER
vuejs
core
1,533,986,214
8,152
asasugar
> ```ts > interface Props { > propF?: 'success' | 'warning' | 'danger'; > } > ``` verifying simple types is okay, but more complex verifications should not be enough
2023-05-04T02:13:02
2023-05-04T02:13:02
{}
NONE
vuejs
core
1,534,127,504
8,171
jd-solanki
I guess this is related to reported issue: https://github.com/vitejs/vite-plugin-vue/issues/162
2023-05-04T05:50:36
2023-05-04T05:50:36
{}
NONE