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 | 2,105,662,387 | 10,909 | LinusBorg | I'm not 100% sure that I understand the question, so:
If you are asking why the type of the `list` ref can't be inferred from the props definition in the child, then I think you have a misunderstanding about how inference works in TS.
Here's a TS-only example with a simple function:
https://www.typescriptlang.... | 2024-05-11T10:08:57 | 2024-05-11T10:08:57 | {} | MEMBER |
vuejs | core | 2,105,673,823 | 10,882 | NonSpicyBurrito | > Very interesting. But I find it strange that folks actually use 'key' to bind to key. 🤔
Yeah `v-for="key in keys"` would be quite rare and is served as simply a minimal reproduction.
A more realistic example would be something where you already have to generate unique keys for a list of objects to iterate throug... | 2024-05-11T10:49:03 | 2024-05-11T10:49:03 | {
"+1": 1
} | NONE |
vuejs | core | 2,107,328,144 | 10,928 | johnsoncodehk | It's type issue from `@vue/runtime-dom`, [the type of `onToggle`](https://github.com/vuejs/core/blob/b2b5f57c2c945edd0eebc1b545ec1b7568e51484/packages/runtime-dom/src/jsx.ts#L409) should be `(payload: MouseEvent) => void` instead of `MouseEvent`.
@LinusBorg could you transfer this issue? | 2024-05-13T08:24:07 | 2024-05-13T08:24:58 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,107,843,299 | 10,933 | Shyam-Chen | `0 && 'foo'` -> `0`
<img width="815" alt="image" src="https://github.com/vuejs/core/assets/13535256/8964bae1-0cc9-4e4e-8344-a6763847135f">
---
這是預期的，你應該用這個：
```tsx
{!!(yourConditionalStatement) && 'foo'}
```
| 2024-05-13T14:50:09 | 2024-05-13T15:07:51 | {} | CONTRIBUTOR |
vuejs | core | 2,107,983,885 | 10,925 | haoqunjiang | /ecosystem-ci run | 2024-05-13T15:23:33 | 2024-05-13T15:23:33 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,108,581,453 | 10,870 | ekkotest | > Can't reproduce from your repro link. (I built the project locally with Vite)
> https://stackblitz.com/edit/vitejs-vite-dxqht5?file=src%2FApp.vue,src%2Fcomponents%2Ftest.svg,package.json,src%2Fmain.js&terminal=dev
I updated the code, and you can try it again, comment almost any other code, and the bug won't rec... | 2024-05-13T18:56:10 | 2024-05-13T18:56:10 | {} | NONE |
vuejs | core | 2,109,551,521 | 10,936 | truthtenfold | > vue webcomponents里面不要使用vue组件吧，样式隔离了，vue组件可以使用vue webcomponetns
如果都用webcomponent的话，就会导致这种组件太多了，就会注册过多的webcomponent,而且会导致provide无法传值下去，书写上也会有较大的脑力负担。
我只是想创建一个webcomponent,用于开发跨技术栈的sdk,把组件和业务都内聚进去。内部用到的组件没有开放的必要性 | 2024-05-14T08:11:30 | 2024-05-14T08:11:30 | {} | NONE |
vuejs | core | 2,100,184,610 | 10,844 | haoqunjiang | > Am I correct in thinking this also could have a follow up to allow TrustedHTML objects to be passed to v-html? Or is that automatically handled?
This is automatically handled as this test case shows: https://github.com/vuejs/core/pull/10844/files#diff-5329e45cfbe289d331762479cc76fe38b6657526dc2a9e2cd6f4729baa6b3e4... | 2024-05-08T09:42:57 | 2024-05-08T09:42:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,101,474,946 | 10,890 | screendriver | Duplicate of https://github.com/vuejs/core/pull/10889 ? | 2024-05-08T21:08:51 | 2024-05-08T21:08:51 | {} | NONE |
vuejs | core | 2,101,595,576 | 10,813 | seattlewayne | I can't speak for the other folks, but updating to Vue v3.4.27 fixed this issue for me. | 2024-05-08T22:19:12 | 2024-05-08T22:19:12 | {} | NONE |
vuejs | core | 2,102,094,012 | 10,880 | kRaviteja7 | Try this it's working,
This issue file is not presented in the project?
import { ref, defineComponent, SetupContext } from 'vue';
export default defineComponent(
<T extends string | number>(props: { msg: T; list: T[] }, context: SetupContext) => {
const count = ref(0);
console.log(props, context)... | 2024-05-09T07:15:48 | 2024-05-09T07:15:48 | {} | NONE |
vuejs | core | 2,106,577,354 | 10,925 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-13T03:42:33 | 2024-05-13T03:42:33 | {} | NONE |
vuejs | core | 2,109,537,248 | 10,936 | yanyunwu | vue webcomponents里面不要使用vue组件吧，样式隔离了，vue组件可以使用vue webcomponetns | 2024-05-14T08:04:10 | 2024-05-14T08:04:10 | {} | NONE |
vuejs | core | 2,097,046,181 | 10,786 | yyx990803 | Thanks for the PR - looks like the root cause of this is the types of `actual` and `expected` are too lax and thus we didn't catch the case where `el.getAttribute('style')` could possibly be `null`. I fixed it with a test in f2c1412e4. | 2024-05-06T22:39:39 | 2024-05-06T22:39:39 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,101,677,878 | 10,886 | skirtles-code | I believe the `trim` modifier has the same problem. Modifiers also seem to be ignored for `type="checkbox"`.
It seems relatively easy to work around this problem. I wonder whether it's worth the extra bytes to support it. That said, if it isn't supported that should probably be documented somewhere. | 2024-05-08T23:53:25 | 2024-05-08T23:53:25 | {} | CONTRIBUTOR |
vuejs | core | 2,102,003,392 | 10,813 | zhangwannihao | me too , updating to Vue v3.4.27 fixed this issue for me. | 2024-05-09T06:06:04 | 2024-05-09T06:06:04 | {} | NONE |
vuejs | core | 2,105,660,581 | 10,910 | LinusBorg | This is all expected behavior | 2024-05-11T10:02:45 | 2024-05-11T10:02:45 | {} | MEMBER |
vuejs | core | 2,105,929,459 | 10,913 | jh-leong | 1. When executing `this.store.registers.push(cmp);`, since `registers` is a `reactive` array, `cmp` will be automatically proxied by `reactive`.
2. Accessing a key of a `reactive` object triggers the proxy's get. In the get logic, `unRef` operation is performed if `isRef(res) === true`. The source code location is a... | 2024-05-11T15:15:51 | 2024-05-11T15:18:05 | {} | MEMBER |
vuejs | core | 2,106,082,689 | 10,813 | edison1105 | @nongtan7898
Thanks for your reproduction but it seems not related to this issue.
You should initialize the DataTable after the data is rendered.
```diff
watch(
() => store._getData,
async () => {
+ await nextTick();
await $("#myTable").DataTable();
}
);
```
---
@seattlewayne @zhangwannihao
... | 2024-05-12T01:32:55 | 2024-05-12T01:32:55 | {} | MEMBER |
vuejs | core | 2,106,577,898 | 10,926 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-13T03:43:09 | 2024-05-13T03:43:09 | {} | NONE |
vuejs | core | 2,097,396,897 | 10,863 | littlezo | > Does this have any real impact on usage?
Yes, for the lifecycle, there is encapsulation. When external hook functions are called internally, the internal context is passed to the incoming hook function, which can result in the inability to obtain the corresponding context on the correct path | 2024-05-07T03:54:42 | 2024-05-07T03:54:42 | {} | NONE |
vuejs | core | 2,098,905,069 | 10,869 | skirtles-code | Is it possible to include test cases for this fix? | 2024-05-07T16:57:44 | 2024-05-07T16:57:44 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,099,334,672 | 10,870 | daniluk4000 | All right this one of weirdest bugs I have experienced.
This is perfectly valid code. Placed inside scoped slot if this matters on few levels deep.
 | 34.5 kB (**+14 B**) | 31.1 kB (**+26 B**) |
... | 2024-05-10T04:15:42 | 2024-05-10T04:45:09 | {} | NONE |
vuejs | core | 2,103,950,439 | 10,900 | jh-leong | Since there has been a previous discussion on issue #2669 regarding a similar topic, and considering the reply from a member [here](https://github.com/vuejs/core/issues/2669#issuecomment-747433501), it seems like the fix in pr would introduce a breaking change.
Therefore, I have temporarily closed it. | 2024-05-10T06:25:53 | 2024-05-10T06:25:53 | {} | MEMBER |
vuejs | core | 2,104,129,560 | 10,898 | dten | Thanks. I do note the other discussion is not about deep being used though. | 2024-05-10T07:59:19 | 2024-05-10T07:59:19 | {} | NONE |
vuejs | core | 2,105,445,386 | 10,882 | neneodonkor | @quiteeasy Very interesting. But I find it strange that folks actually use 'key' to bind to key. 🤔 | 2024-05-11T01:58:24 | 2024-05-11T01:58:24 | {
"+1": 1
} | NONE |
vuejs | core | 2,097,093,979 | 10,873 | yyx990803 | I don't think there is a fix for this, since it's impossible to infer the type passed to `expose` in the return type of `defineComponent` in TypeScript.
The workaround is exporting your expose type as a separate interface:
```tsx
import { defineComponent } from 'vue';
export inteface Exposed {
getClipDataU... | 2024-05-06T23:31:55 | 2024-05-06T23:31:55 | {} | MEMBER |
vuejs | core | 2,097,271,396 | 10,873 | Flame-00 | > 我认为这个问题没有解决办法，因为无法推断TypeScript`expose`的返回类型中传递的类型。`defineComponent`
>
> 解决方法是将公开类型导出为单独的接口：
>
> ```tsx
> import { defineComponent } from 'vue';
>
> export inteface Exposed {
> getClipDataURL: number
> }
>
> export default defineComponent((_, { expose }) => {
> expose({
> getClipDataURL: 1,
>... | 2024-05-07T02:10:46 | 2024-05-07T02:10:46 | {} | NONE |
vuejs | core | 2,098,551,351 | 10,870 | damms005 | > tldr;
> Add `v-if` to the parent of where things are blowing up for you
I have a monkey-patch that works for me.
[In my case](https://github.com/damms005/devdb-vscode/issues/59), in [call to `insertBefore`](https://github.com/vuejs/core/blob/461946175df95932986cbd7b07bb9598ab3318cd/packages/runtime-dom/src/nod... | 2024-05-07T14:32:21 | 2024-05-07T14:32:21 | {} | NONE |
vuejs | core | 2,099,547,202 | 10,887 | Justineo | It’s how JavaScript works and not related to Vue. | 2024-05-08T01:09:38 | 2024-05-08T01:09:38 | {} | MEMBER |
vuejs | core | 2,103,983,668 | 10,898 | jh-leong | As a workaround, you can manually retrieve the `scopeId` of the parent component for binding:
```ts
const useScopeId = () => {
const { scopeId } = getCurrentInstance()?.vnode || {};
return scopeId ? { [scopeId]: '' } : null;
};
```
Refer to [playground](https://play.vuejs.org/#eNqdU9tu00AQ/ZXRviSRiiMBEpL... | 2024-05-10T06:49:50 | 2024-05-10T06:49:50 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,104,022,029 | 10,901 | warmthsea | Is this the design? | 2024-05-10T07:04:31 | 2024-05-10T07:04:31 | {} | NONE |
vuejs | core | 2,101,813,588 | 10,886 | YiMo1 | > I believe the `trim` modifier has the same problem. Modifiers also seem to be ignored for `type="checkbox"`.
>
> It seems relatively easy to work around this problem. I wonder whether it's worth the extra bytes to support it. That said, if it isn't supported that should probably be documented somewhere.
Yes, in... | 2024-05-09T02:24:30 | 2024-05-09T02:24:30 | {} | NONE |
vuejs | core | 2,103,913,359 | 10,900 | jh-leong | > ## scope css still doesn’t take effect
>  在 3.2 及以下版本中，defineProps() 的泛型类型参数仅限于类型文字或对本地接口的引用。 这个限制在... | 2024-02-28T10:50:41 | 2024-02-28T10:50:41 | {} | NONE |
vuejs | core | 1,970,622,996 | 10,171 | pikax | @PurpleTape do you mind explaining this better, the code you provided, the issue only happens in typescript and the behaviour is what I would expect, do you mind providing more info, bear in mind on the template the type errors and runtime errors are two different things, if you declare the properties to be required in... | 2024-02-29T08:13:45 | 2024-02-29T08:13:45 | {} | MEMBER |
vuejs | core | 1,970,936,771 | 10,431 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8095141631)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8075503619) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-02-29T11:29:29 | 2024-02-29T11:29:29 | {} | CONTRIBUTOR |
vuejs | core | 1,973,396,150 | 10,425 | el-j | Hi, yes so indeed it's not about define slots and use them in the component. Its about useing the component and know the possible slot names or generically put in/fill all possible slots.
Sorry if i was not clear on that.
If i import a component i can get slmething like
`component.props` but cannot get `componen... | 2024-03-01T15:33:15 | 2024-03-01T15:33:15 | {} | NONE |
vuejs | core | 1,978,187,942 | 10,455 | catpigdog | @LinusBorg Do you also think this is a bug? | 2024-03-05T08:16:57 | 2024-03-05T08:16:57 | {} | NONE |
vuejs | core | 1,980,161,082 | 10,460 | Shyam-Chen | Unable to reproduce the issue.
```sh
$ pnpm dlx degit fastify/fastify-vite/starters/vue-base my-vue-app
$ cd my-vue-app
$ pnpm i
$ pnpm dev
```
```js
import { h } from 'vue';
export default function Test1(props, context) {
return h('div', {}, ['12']);
}
```
```js
import { h } from 'vue';
expo... | 2024-03-06T06:17:17 | 2024-03-06T06:25:26 | {} | CONTRIBUTOR |
vuejs | core | 1,968,124,763 | 9,313 | cicada-ah | @edison1105 还是有遗漏场景
https://deploy-preview-9313--vue-sfc-playground.netlify.app/#eNqdU11r2zAU/SuaNogDmc3YnjIndCt92GAfrIW9+MW1rx21smSkKzcQ8t97JSGnKaUPfTDI9xwdnft14N/GMZ8c8DUvEYZR1gjbSjFWtmJiot1UHGvTA1Y8hAlINDZ9FB3h7+xOP/w39ThTiHS5E7JNDE8IgYqzC9R9L8HrhgOFiqRcnDsoyAKdzsL0axsjRmSyVr1XsaRgAd1IqBhGbZAdmFa/tFMI7YoZ6NiRdUYPbE... | 2024-02-28T03:19:51 | 2024-02-28T03:19:51 | {} | NONE |
vuejs | core | 1,968,638,762 | 8,952 | ThejanNim | Hi guys, Any update here? @sxzz if you can please follow up on this issue. | 2024-02-28T10:05:36 | 2024-02-28T10:07:52 | {} | NONE |
vuejs | core | 1,969,253,018 | 10,376 | pikax | This looks to be a dupe of https://github.com/vuejs/core/issues/9649 | 2024-02-28T15:38:50 | 2024-02-28T15:39:00 | {} | MEMBER |
vuejs | core | 1,970,537,444 | 10,429 | Doctor-wu | This didn't help, can you provide a minimal reproduction? | 2024-02-29T07:09:46 | 2024-02-29T07:09:46 | {} | MEMBER |
vuejs | core | 1,971,922,889 | 9,556 | sadeghbarati | @pikax Hey!
Please check the Svelte type helpers `ComponentProps`, and `ComponentType` in this source
https://github.com/wobsoriano/svelte-sonner/blob/main/src/lib/types.ts#L30C2-L31C51
What is the equivalent of this source with your Vue type helpers?
Thanks and sorry for tag :pray: | 2024-02-29T20:40:57 | 2024-02-29T20:40:57 | {} | NONE |
vuejs | core | 1,972,696,287 | 10,367 | OnlyWick | I notice that the reactivity system change, does this mean that `minor` will replace the current version? @sxzz | 2024-03-01T07:57:12 | 2024-03-01T07:57:12 | {} | CONTRIBUTOR |
vuejs | core | 1,973,237,871 | 6,761 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.5 kB (**+27 B**) | 34.4 kB (**+33 B**) | 31 kB (**+42 B**) |
... | 2024-03-01T13:48:49 | 2024-03-01T13:48:49 | {} | NONE |
vuejs | core | 1,964,679,190 | 10,203 | goodwan | logic is quite simple:
* I have a function that takes a generic `Map<string, K>`, i.e. `calcSomeMagicNumber<K>(m: Map<string, K>): number`
* I want to pass a reactive map (i.e. from pinia getter) into it
ideally I would like to pass it "as is" like I did before. it is not possible since 3.3.10 as @yangxiuxiu1115 k... | 2024-02-26T17:14:07 | 2024-03-03T08:35:43 | {} | NONE |
vuejs | core | 1,976,034,204 | 10,452 | haoqunjiang | https://github.com/vuejs/vue/issues/9008#issuecomment-434645103
https://github.com/vuejs/vue/issues/9160#issuecomment-445184426
Vue.js 不保证在浏览器翻译插件下正常工作。 | 2024-03-04T08:48:56 | 2024-03-04T08:48:56 | {} | MEMBER |
vuejs | core | 1,978,183,455 | 10,455 | LinusBorg | that's not a solution to the issue ... | 2024-03-05T08:14:16 | 2024-03-05T08:14:16 | {} | MEMBER |
vuejs | core | 1,980,299,642 | 10,464 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8168744828)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8167159696) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-03-06T08:09:58 | 2024-03-06T08:09:58 | {} | CONTRIBUTOR |
vuejs | core | 1,968,221,950 | 10,410 | haoqunjiang | I don't see any objective benefits to the end users.
Such large refactoring also obscures the git blame history.
So I think the trouble outweighs the potential benefits. Therefore I'm not going to merge it.
Thanks for the effort, though. | 2024-02-28T04:47:14 | 2024-02-28T04:47:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,970,654,224 | 10,429 | LinusBorg | So the problem was a dependency that is not for Vue 3? Then we don't have a bug. Closing this. | 2024-02-29T08:34:57 | 2024-02-29T08:34:57 | {} | MEMBER |
vuejs | core | 1,970,952,697 | 10,425 | pikax | @el-j can you provide more information
Seems to be working to me [playground](https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBAbzgEwKYDNgDtUGUA2EMAznAL5zpQQhwDkAbgK6p0BQbAxhFsfMYRJwAvCgzY8g4gB4kAQwBccABQBKYQD44crAE8yGtUA)
```ts
import { defineSlots } from 'vue'
const slots = defineSlots<{ a: () => any }... | 2024-02-29T11:38:53 | 2024-02-29T11:38:53 | {} | MEMBER |
vuejs | core | 1,132,567,584 | 5,964 | yoyo837 | > Yes, I think so. But the template in the original repro is invalid IMO (see [comment](https://github.com/vuejs/core/issues/5964#issuecomment-1132521964)). I recommend creating a new issue with _valid_ markup that generates the error.
I've updated it https://stackblitz.com/edit/vue3-forwarding-slots-qmswhv?file=src... | 2022-05-20T07:22:05 | 2024-02-29T13:01:15 | {} | NONE |
vuejs | core | 1,973,282,154 | 6,715 | jonaskuske | > For me it not only happens with v-if child, but also when you have a slot in a reusable transition component (as mentioned in this closed issue #6922):
>
> [sfc.vuejs.org/#__SSR__eNp9kctqwzAQRX9FaJNNLEFbKBg1pHTRH+hSGz+mjRrrwUh2KcH/3pGTJk4M2c3cOeiO7hz4awhi6IGXXMUGTUgsQurDRjtjg8fE3rwN7BO9ZSshc5PxlXZKHnkiqUlgQ1cloI4x... | 2024-03-01T14:15:37 | 2024-03-01T14:15:37 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 1,980,176,419 | 10,460 | cc-hearts | I used a template created by vite to reproduce the issue. [repo](https://github.com/cc-hearts/vue-issues.git)
(I'm using the `createSSRApp` API. )
Here's the rendering.
 | 34.5 kB (**+121 B**) | 31.1 kB (**+13... | 2023-09-28T13:49:19 | 2024-02-29T07:03:04 | {} | NONE |
vuejs | core | 1,970,721,281 | 10,431 | baiwusanyu-c | /ecosystem-ci run | 2024-02-29T09:17:07 | 2024-02-29T09:17:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,970,730,850 | 10,419 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8093653136)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8075503619) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-02-29T09:22:50 | 2024-02-29T09:22:50 | {} | CONTRIBUTOR |
vuejs | core | 1,969,261,982 | 6,745 | Tobiaqs | It seems I'm still encountering this issue, even in Vue 3.4.x
This is my workaround (works with Vite). It disables transitions in dev. In prod everything works...
```vue
// FixedTransitionGroup.vue
//
// Usage:
// <FixedTransitionGroup
// enter-active-class="transform ease-out duration-300 transition"
//... | 2024-02-28T15:43:03 | 2024-02-29T13:49:29 | {} | NONE |
vuejs | core | 1,972,650,332 | 10,367 | sxzz | The reactivity system is changed a lot, and related PR is merged into `minor` branch.
Could you please change the target branch of your PR to `minor` branch instead of `main`, then resolve conflicts. | 2024-03-01T07:21:10 | 2024-03-01T07:21:10 | {} | MEMBER |
vuejs | core | 1,980,288,884 | 10,464 | baiwusanyu-c | /ecosystem-ci run | 2024-03-06T08:02:30 | 2024-03-06T08:02:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,969,454,210 | 10,370 | hrubysi | @pikax
I replicated desired behavior using a function in file `example.ts` in this [Playgournd](https://play.vuejs.org/#eNqFVMGO2kAM/RUrF0BCoXT30pSlaisO28N21aJeCKqyiUOHJpNoZkJBKP9ej4eEEKXbAyjjZ888288+ex/L0j9U6AXeQsdKlAY0mqqELJK7h9AzOvSWoRR5WSgDn4u8hFQVOYz8mT3Y0FEoQ2lOJcJKGmFO8ADnUAKIJABZ5S+o3tujjHIMQBsl5I4MtY2KC6kN... | 2024-02-28T17:08:30 | 2024-02-28T17:08:30 | {} | NONE |
vuejs | core | 1,971,752,164 | 4,668 | Sceat | Kinda reviving this each year but it is still an issue which defeats the point of graying out unused variables. | 2024-02-29T18:48:42 | 2024-02-29T18:48:42 | {} | NONE |
vuejs | core | 1,972,977,647 | 10,425 | LinusBorg | If I had to guess, OP wants a way to read the available slot names from a component definition at runtime or something like that?
Not sure though ... | 2024-03-01T10:59:40 | 2024-03-01T10:59:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,970,724,127 | 5,964 | EDM115 | indeed, there was an oversight in my eslint config
thanks, this was driving me insane :) | 2024-02-29T09:18:47 | 2024-02-29T09:18:47 | {} | NONE |
vuejs | core | 1,972,868,070 | 10,438 | BlackCrowxyz | ```js
if (a.value | b.value) {}
``` | 2024-03-01T09:53:20 | 2024-03-01T09:54:20 | {} | NONE |
vuejs | core | 1,974,913,771 | 10,445 | walpolea | After some extra digging, I believe this is also the same issue reported here: https://github.com/vuejs/core/issues/9033
Which seems to have an open PR for a possible fix: https://github.com/vuejs/core/pull/9083 | 2024-03-02T21:27:21 | 2024-03-02T21:27:21 | {} | NONE |
vuejs | core | 1,977,802,274 | 10,455 | Shyam-Chen | ```diff
+ delete array[0]
watchSyncEffect(() => {
console.log(array.hasOwnProperty(0))
})
- delete array[0]
```
Or
```diff
- watchSyncEffect
+ watchPostEffect
``` | 2024-03-05T01:52:07 | 2024-03-05T08:27:30 | {} | CONTRIBUTOR |
vuejs | core | 1,968,072,192 | 9,313 | edison1105 | /ecosystem-ci run | 2024-02-28T02:24:57 | 2024-02-28T02:24:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,968,073,004 | 10,416 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8074326328)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8043911204) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/807... | 2024-02-28T02:25:54 | 2024-02-28T02:25:54 | {} | CONTRIBUTOR |
vuejs | core | 1,970,534,294 | 10,429 | huluobotx | sorry, it's not my use defineComponent, it's in @element-plus/icons-vue@2.3.1
```
/*! Element Plus Icons Vue v2.3.1 */
// unplugin-vue:/home/runner/work/element-plus-icons/element-plus-icons/packages/vue/src/components/add-location.vue?vue&type=script&setup=true&lang.ts
import { defineComponent as _defineCompon... | 2024-02-29T07:07:03 | 2024-02-29T07:07:03 | {} | NONE |
vuejs | core | 1,970,737,348 | 10,431 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8093676103)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8075503619) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-02-29T09:26:33 | 2024-02-29T09:26:33 | {} | CONTRIBUTOR |
vuejs | core | 1,970,819,474 | 10,431 | baiwusanyu-c | /ecosystem-ci run | 2024-02-29T10:15:34 | 2024-02-29T10:15:34 | {
"+1": 1,
"heart": 1
} | MEMBER |
vuejs | core | 1,971,222,857 | 10,428 | aqordeon | ahh my bad, you're correct, native css didn't supports darken. I just followed a tutorial I found and didn't notice the SCSS thing. Now I use ```
background-color: v-bind('`color-mix(in srgb, ${bgColor} 80%, black)`');``` and it work as I expected. Thanks for remind me. | 2024-02-29T14:09:00 | 2024-02-29T14:09:00 | {} | NONE |
vuejs | core | 1,961,040,355 | 10,383 | Shyam-Chen | Give `@fastify/vite` a try, referencing the example at [`@fastify/vue`](https://github.com/fastify/fastify-vite/tree/dev/starters/vue-base).
```sh
$ pnpm dlx degit fastify/fastify-vite/starters/vue-base vue-fastify-ssr
$ cd vue-fastify-ssr
$ pnpm install
$ pnpm build
$ pnpm start
``` | 2024-02-23T10:02:30 | 2024-03-01T09:57:34 | {} | CONTRIBUTOR |
vuejs | core | 1,972,974,935 | 10,438 | LinusBorg | While I understand that this can be confusing, it's technically working as expected. When the first condition evaluates to `false`, the code in the second condition won't be run by Javascript, so Vue can't collect `b` as a dependency of the effect.
Another way to accommodate for this would be to read both values bef... | 2024-03-01T10:57:55 | 2024-03-01T10:58:13 | {} | MEMBER |
vuejs | core | 1,973,470,754 | 9,866 | EmilyRagan | @elizatlawy looks like 3.3.13, according to the [change log](https://github.com/vuejs/core/blob/main/changelogs/CHANGELOG-3.3.md#3313-2023-12-19) | 2024-03-01T16:14:32 | 2024-03-01T16:14:32 | {} | NONE |
vuejs | core | 1,978,189,649 | 10,455 | LinusBorg | Probably, yes. | 2024-03-05T08:18:00 | 2024-03-05T08:18:00 | {} | MEMBER |
vuejs | core | 1,968,055,022 | 10,416 | edison1105 | /ecosystem-ci run | 2024-02-28T02:04:50 | 2024-02-28T02:04:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,968,063,338 | 10,416 | Doctor-wu | The quasar one seems to be a glitch, could you help to rerun it? @edison1105 | 2024-02-28T02:14:20 | 2024-02-28T02:14:20 | {} | MEMBER |
vuejs | core | 1,970,683,140 | 5,964 | EDM115 | any update on this ?
I have this code part of a Vue 3 migration :
```vue
<template>
<v-card
rounded="0"
:loading="loading"
>
<v-card-title>
Exécutions
</v-card-title>
<v-list class="py-0">
<template v-if="runs">
<template v-for="run in runs.results">
... | 2024-02-29T08:53:44 | 2024-02-29T08:53:44 | {} | NONE |
vuejs | core | 1,132,541,774 | 5,964 | yoyo837 | > Not sure about the `key` issue. I'm wondering if `<template>`'s `key` is supposed to be automatically applied to `<slot>` children. Nothing in the [docs](https://vuejs.org/guide/essentials/list.html#maintaining-state-with-key) suggests the `key` should be manually/explicitly moved to the children, so it might be a Vu... | 2022-05-20T06:57:28 | 2024-02-29T09:14:08 | {} | NONE |
vuejs | core | 1,970,717,289 | 10,392 | baiwusanyu-c | /ecosystem-ci run | 2024-02-29T09:14:36 | 2024-02-29T09:14:36 | {} | MEMBER |
vuejs | core | 1,979,919,944 | 10,457 | Doctor-wu | The e2e one seems like an accident | 2024-03-06T01:33:39 | 2024-03-06T01:33:39 | {} | MEMBER |
vuejs | core | 1,968,445,672 | 10,418 | ChuTingzj | > > https://vuejs.org/guide/typescript/composition-api#typing-component-props
>
> 并没用，示例里是个interface, 而我这里是个class, 就是识别不出来
我好像没复现3.2、3.4都试过了，也有可能是IDE的问题 | 2024-02-28T08:15:04 | 2024-02-28T08:15:04 | {} | NONE |
vuejs | core | 1,968,685,866 | 10,418 | 52javascript | > > > https://vuejs.org/guide/typescript/composition-api#typing-component-props
> >
> >
> > 并没用，示例里是个interface, 而我这里是个class, 就是识别不出来
>
> 官方是这么说的
>
> 语法限制[](https://cn.vuejs.org/guide/typescript/composition-api.html#syntax-limitations) 在 3.2 及以下版本中，defineProps() 的泛型类型参数仅限于类型文字或对本地接口的引用。 这个限制在 3.3 中得到了解决。最新版本... | 2024-02-28T10:30:39 | 2024-02-28T10:30:39 | {} | NONE |
vuejs | core | 1,965,703,031 | 10,416 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 90.5 kB (**+14 B**) | 34.4 kB (**+3 B**) | 31.1 kB (**+13 B**) |
| v... | 2024-02-27T03:03:10 | 2024-02-28T11:03:54 | {} | NONE |
vuejs | core | 1,969,283,956 | 10,370 | pikax | This seems to be a typescript issue rather than a vue issue, `modelValue` does not have the correct type, which causes typescript to not infer it correctly, see the example [playground](https://www.typescriptlang.org/play?#code/FAFwngDgpgBAcgewJIDsBmUBOAeAKgPhgF4YBtXAXXJigA8QoUATAZxgEMUwYB+GABhgAuGCigA3LBQDcwYEygBjADbt... | 2024-02-28T15:53:14 | 2024-02-28T15:53:14 | {} | MEMBER |
vuejs | core | 1,970,700,962 | 5,964 | LinusBorg | @EDM115 That's not related to this issue.
Your problem is that your eslint config has two rules active that are incompatible.
The first error is from the Vue 3 rule:
https://eslint.vuejs.org/rules/no-v-for-template-key-on-child.html#vue-no-v-for-template-key-on-child
The second error is from the Vue 2 rule:
... | 2024-02-29T09:04:57 | 2024-02-29T09:04:57 | {} | MEMBER |
vuejs | core | 1,970,718,574 | 10,419 | baiwusanyu-c | /ecosystem-ci run | 2024-02-29T09:15:26 | 2024-02-29T09:15:26 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,972,655,280 | 10,367 | sxzz | I’ve changed it for you. Only one thing you have to be done is rebasing your branch for resolving conflicts and push it directly. | 2024-03-01T07:23:14 | 2024-03-01T07:23:14 | {} | MEMBER |
vuejs | core | 1,975,567,408 | 10,397 | moushicheng | Hello yyx, I read your pr in detail, thx your this amazing work!
But because of my stupidity, I don't quite understand why double-linked lists improve memory efficiency
i guess use double-linked lists ,It makes it easier to implement certain functions, but what else does it mean , can you give me some.
Can you give... | 2024-03-04T02:59:25 | 2024-03-04T02:59:25 | {} | CONTRIBUTOR |
vuejs | core | 1,978,345,670 | 10,457 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.5 kB | 34.4 kB | 31 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-03-05T09:44:27 | 2024-03-05T09:44:27 | {} | NONE |
vuejs | core | 1,968,055,331 | 10,417 | edison1105 | /ecosystem-ci run | 2024-02-28T02:05:10 | 2024-02-28T02:05:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,968,066,916 | 10,416 | Justineo | /ecosystem-ci run | 2024-02-28T02:18:36 | 2024-02-28T02:18:36 | {
"+1": 2,
"heart": 2
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.