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,404,786,730 | 7,579 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8436b015ea4c88babbf2870e7eaa829729e9238b |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-26T10:07:49 | 2023-01-26T14:01:04 | {} | NONE |
vuejs | core | 1,384,431,197 | 7,355 | funkyvisions | @LinusBorg and @grpdream I think this bit me again today in a different way. I'm seeing my watch function getting called for ~~an inactive~~ **a disposed** child of a keep-alive component. I put onActivated and onDeactivated handlers that set a flag in the component that has the watch and I see the watch getting call... | 2023-01-16T18:40:42 | 2023-01-16T19:06:52 | {} | NONE |
vuejs | core | 1,384,857,921 | 6,434 | ddmy | 我也遇到了这个问题，我自己封装了一个vue组件上传到了npm，当在项目中引入时也会有类似的警告，导致加载组件挂载不成功。 我调试vite打包后的`dist`目录文件，发现`setup`方法内的 `onMounted`方法并未执行。
| 2023-01-17T05:37:40 | 2023-01-17T05:37:55 | {} | NONE |
vuejs | core | 1,385,793,660 | 5,996 | rhues | Still waiting for the fix to be merged. | 2023-01-17T17:42:56 | 2023-01-17T17:42:56 | {} | NONE |
vuejs | core | 1,399,155,158 | 7,560 | sxzz | It's not necessary to add emojis, and we use PRESENT instead of a particular year. | 2023-01-21T02:32:12 | 2023-01-21T02:32:12 | {} | MEMBER |
vuejs | core | 1,381,701,932 | 5,153 | renatodeleao | I'm getting the issue on a very complex `table` component.
As for the workarounds, my components have an indented/formatted structure and only removing **all whitespace between components** makes it work, which is a no-go because the component becomes impossible to read/maintain by humans.
What is causing the iss... | 2023-01-13T11:16:55 | 2023-01-13T11:54:42 | {} | NONE |
vuejs | core | 1,382,836,660 | 7,458 | LeaVerou | Thank you for the lengthy explanation, I now understand the rationale much better.
> First off, technically, the root object is special, it represents the component instance itself. while it's a proxy, it's not a reactive data proxy - instead the proxy's job is to provide the template access to the different proper... | 2023-01-14T16:09:22 | 2023-01-14T16:09:40 | {
"+1": 1
} | NONE |
vuejs | core | 1,384,343,752 | 3,914 | renatodeleao | @posva any suggestion to get some traction on this idea? I've used [`rfcs` repo "discussions" tab](https://github.com/vuejs/rfcs/discussions/480), but had zero engagement, so either:
1. I didn't explain the problem properly — very likely (😅)
1. people just learned to live with the limitation, gave up, and added thei... | 2023-01-16T17:11:41 | 2023-01-16T17:11:41 | {} | NONE |
vuejs | core | 1,400,265,019 | 1,825 | justDabuK | I just encountered a similar problem. I just found that issue and see that it is closed, but I didn't see any explanation on how this is solved now. Did I oversee anything? 🤔
In order to give some context to my "similar" problem, I want to dynamically use `.lazy`. Or to frame it in a better way, I want to pass dow... | 2023-01-23T12:28:46 | 2023-01-23T12:28:46 | {} | NONE |
vuejs | core | 1,404,679,538 | 7,153 | sxzz | Unfortunately, Reactivity Transform has been dropped officially now, so I closed this issue/PR. If you want to keep using it, please consider the community version [Vue Macros](https://vue-macros.sxzz.moe/features/reactivity-transform.html). | 2023-01-26T08:20:53 | 2023-01-26T08:20:53 | {} | MEMBER |
vuejs | core | 1,405,173,505 | 7,582 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 674b21d3f6333725ee7079e2b3f6f1d2ae232c84 |
|<span aria-hidden="true">🔍</span> Latest deploy l... | 2023-01-26T15:22:53 | 2023-01-26T15:22:53 | {} | NONE |
vuejs | core | 1,383,165,380 | 7,534 | sxzz | https://sfc.vuejs.org/#eNpNj01uAjEMha8SedVKMNlPUaXeoVI32dDBKYMSO7KTUgnN3esMCNj593vvXeCjlOG3IYyw00nmUt8DxUZTnZlcfHl1l0DOCdYm5AIcMSXeuDNLOgR4C7QEwr/CUt0B476l2p9svvN33A3s1CDF+jmv959H/MI0cUYXhbPBB29dYUKq6h/r7m/VemLCBq6Ybd6X4aRMlmC1Gm4LDTBezffZihh7gFqLjt5rnDr3pAPLj7dqkEZ1NjXUvP0WPiuKgQN0hKVcYPkHRRRqbg== | 2023-01-15T14:29:24 | 2023-01-15T14:29:24 | {} | MEMBER |
vuejs | core | 1,383,561,289 | 7,535 | baiwusanyu-c | Maybe it's a problem with a misspelled word
wdyt? @LinusBorg | 2023-01-16T06:40:15 | 2023-01-16T06:40:15 | {} | MEMBER |
vuejs | core | 1,384,438,895 | 7,355 | LinusBorg | That's actually expected. Components are kept alive - so their reactive defects still works like normal, they are not "asleep" or anything. Just out of the DOM while deactivated.
It's left to you to customize this with the help of the(de)activated hooks | 2023-01-16T18:52:38 | 2023-01-16T18:52:38 | {} | MEMBER |
vuejs | core | 1,035,999,092 | 5,406 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: f1a6a3226001887033c05f20af98e390f6a94274
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620625b77502d40007195c7e](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-11T09:03:29 | 2023-01-19T16:04:22 | {} | NONE |
vuejs | core | 1,116,845,135 | 5,856 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | af488c26764b97133e785cfc2a7ad708c61ffb67 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-05-04T01:08:05 | 2023-01-19T17:03:47 | {} | NONE |
vuejs | core | 1,304,715,489 | 7,028 | edison1105 | duplicate of nuxt/nuxt.js#14586 | 2022-11-06T05:00:27 | 2023-01-19T17:48:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,398,872,133 | 7,515 | LinusBorg | Here: https://vuejs.org/api/sfc-css-features.html#child-component-root-elements | 2023-01-20T20:05:25 | 2023-01-20T20:05:25 | {} | MEMBER |
vuejs | core | 1,102,658,374 | 5,754 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | e182bbcc755c252b26de78e36581ac4a09af3b4d |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-04-19T13:29:17 | 2023-01-23T14:11:12 | {} | NONE |
vuejs | core | 1,404,326,257 | 4,836 | defaude | A belated merry christmas and happy new year to everyone 😘 I've updated the PR so it can be merged again. | 2023-01-25T22:48:55 | 2023-01-25T22:48:55 | {} | CONTRIBUTOR |
vuejs | core | 1,404,682,953 | 5,100 | sxzz | Unfortunately, Reactivity Transform has been dropped officially now, so I closed this issue/PR. If you want to keep using it, please consider the community version [Vue Macros](https://vue-macros.sxzz.moe/features/reactivity-transform.html).
---
This PR has been merged to Vue Macros https://github.com/sxzz/unplug... | 2023-01-26T08:24:55 | 2023-01-26T08:24:55 | {} | MEMBER |
vuejs | core | 1,368,192,797 | 4,294 | atmosphr | For Nuxt3 users, I got it to work with the following setup:
1. Install the `vite-plugin-vue-type-imports` plugin:
```
npm install --save-dev vite-plugin-vue-type-imports
```
2. In `nuxt.config.ts`, add the plugin to the `modules` field:
```ts
export default defineNuxtConfig({
// ...
modules: [
... | 2022-12-31T09:47:52 | 2023-01-14T08:43:16 | {
"+1": 6,
"heart": 4
} | NONE |
vuejs | core | 1,382,866,596 | 7,515 | abitwhy | @LinusBorg Sorry for missing that doc.
> the parent can style the child root element
I think the above design violates the following principle:
> its CSS will apply to elements of the current component only.
In fact, the current behavior has made a [mess](https://sfc.vuejs.org/#eNq1VN1u2jAUfhXL1cQmNQkpIBWPI... | 2023-01-14T17:37:27 | 2023-01-15T01:44:18 | {
"+1": 1
} | NONE |
vuejs | core | 1,170,143,734 | 6,201 | LinusBorg | 🤦🏻♂️thanks | 2022-06-29T15:43:11 | 2023-01-19T17:37:50 | {} | MEMBER |
vuejs | core | 1,398,190,090 | 7,561 | LinusBorg | You are recreating a new object for `style` on every re-render of the parent, and the parent re-renders on each change of count.
This is expected in Vue 3, where applying fallthrough attributes is left to the child instead of being done by the parent. | 2023-01-20T10:27:04 | 2023-01-20T10:27:04 | {} | MEMBER |
vuejs | core | 1,400,973,871 | 7,572 | LinusBorg | This should likely be addressed in the Volar repo, not here.
https://github.com/johnsoncodehk/volar | 2023-01-23T21:02:40 | 2023-01-23T21:02:58 | {} | MEMBER |
vuejs | core | 1,402,345,263 | 7,575 | LinusBorg | This is documented behavior.
<img width="739" alt="Bildschirmfoto 2023-01-24 um 18 46 01" src="https://user-images.githubusercontent.com/1444526/214368741-95e16f26-7568-4543-8ea3-fd6b89c3ee43.png">
https://vuejs.org/api/reactivity-core.html#reactive | 2023-01-24T17:46:56 | 2023-01-24T17:46:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,384,451,534 | 7,355 | funkyvisions | @LinusBorg I'll try to work up an example. Thanks. | 2023-01-16T19:07:25 | 2023-01-16T19:07:25 | {} | NONE |
vuejs | core | 1,384,709,113 | 6,043 | edison1105 | It's probably resolved by https://github.com/vuejs/devtools/commit/60aeed218badfed81b7e7957ebd0c0b521de4cfa
**It's NOT released yet.** | 2023-01-17T00:59:44 | 2023-01-17T00:59:44 | {} | MEMBER |
vuejs | core | 1,386,010,434 | 7,510 | funkyvisions | I've applied this patch locally and it seems to address my initial issue. | 2023-01-17T20:28:23 | 2023-01-17T20:28:23 | {} | NONE |
vuejs | core | 1,401,153,492 | 7,572 | johnsoncodehk | Please track https://github.com/johnsoncodehk/volar/issues/2308. | 2023-01-23T23:36:18 | 2023-01-23T23:36:18 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,403,826,906 | 7,502 | ThornWalli | What is the current status here? | 2023-01-25T15:47:53 | 2023-01-25T15:47:53 | {} | NONE |
vuejs | core | 1,404,679,399 | 7,150 | sxzz | Unfortunately, Reactivity Transform has been dropped officially now, so I closed this issue/PR. If you want to keep using it, please consider the community version [Vue Macros](https://vue-macros.sxzz.moe/features/reactivity-transform.html). | 2023-01-26T08:20:44 | 2023-01-26T08:20:44 | {} | MEMBER |
vuejs | core | 1,404,684,530 | 6,349 | sxzz | Unfortunately, Reactivity Transform has been dropped officially now, so I closed this issue/PR. If you want to keep using it, please consider the community version [Vue Macros](https://vue-macros.sxzz.moe/features/reactivity-transform.html).
---
This PR has been merged to Vue Macros https://github.com/sxzz/unplug... | 2023-01-26T08:26:51 | 2023-01-26T08:26:51 | {} | MEMBER |
vuejs | core | 1,382,682,519 | 7,158 | jaytonic | Hi,
Any chance that someone could validate this PR? It would really be helpfull :) It is really a pain that the HMR is not updating the page when developing with such libraries. | 2023-01-14T07:30:26 | 2023-01-14T07:31:10 | {
"+1": 2
} | NONE |
vuejs | core | 1,369,844,738 | 7,457 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | bb7ed25caf5abb845cb82e515a7b022c7e6589e1 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2023-01-03T14:40:54 | 2023-01-18T02:31:53 | {} | NONE |
vuejs | core | 1,113,482,221 | 5,817 | Hebilicious | @liulinboyi Thanks for the quick fix 🙏
I used the same class to illustrate the bug visually, but it happened to me in a totally different scenario :D | 2022-04-29T16:04:06 | 2023-01-19T17:08:12 | {} | NONE |
vuejs | core | 1,112,079,795 | 5,817 | liulinboyi | > ### Version
> 3.2.25
>
> ### Reproduction link
> [stackblitz.com](https://stackblitz.com/edit/github-qwk9ei)
>
> ### Steps to reproduce
> Create a component with a scoped style (parent) Create a regular component with a template tag (children) Create a functional component that uses `h` (children)
>
> The... | 2022-04-28T11:14:21 | 2023-01-19T17:08:12 | {} | MEMBER |
vuejs | core | 1,481,654,542 | 7,841 | sxzz | You can try `ToRefs` type and code below
```ts
type PartialRef<O, K extends keyof O> = ToRefs<Pick<O, K>> & Omit<O, K>
```
https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBDAnmApnA3nAKhASigMwGcAaOfAuAXzgKghDgHIA3AVxSYChRJYM4KAB6oAxjCzIUAeUo06DZsLEwAtElTcuGtNIBGAKzgBeDFzi0IEAFxwiMKMAB2Ac3NwneQradsQelCguKi5tK... | 2023-03-23T18:02:03 | 2023-03-23T18:02:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,456,122,978 | 7,836 | sxzz | /ecosystem-ci run | 2023-03-06T13:19:56 | 2023-03-23T18:04:56 | {} | MEMBER |
vuejs | core | 1,280,012,301 | 6,891 | sxzz | It's by design I think. If you need TypeScript support then install it by yourself.
---
You can enable `skipLibCheck` in tsconfig | 2022-10-16T17:13:49 | 2023-03-29T07:04:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,484,988,382 | 7,737 | haoqunjiang | Thanks, I've read HTML documentation on MDN in more depth and realized that `input`'s `value` only has a few possible types, so `any` is too permissive.
Nevertheless, it's another topic and should have a dedicated issue. (Though I doubt it'll change in the current major version, as it's a breaking change in types.) | 2023-03-27T11:37:56 | 2023-03-27T11:37:56 | {} | MEMBER |
vuejs | core | 1,486,644,166 | 7,737 | Pryscy | Thank you for your feedback :)
It would be cleaner on the input side to be less permissive. However, as you said, the change is a breaking change, and it won't happen right away. It's a bit annoying to have something out of sync between the input and the textarea.
I was hoping to persuade you to change the textare... | 2023-03-28T10:56:27 | 2023-03-28T10:56:27 | {} | NONE |
vuejs | core | 1,488,127,178 | 7,979 | haoqunjiang | /ecosystem-ci run vuetify | 2023-03-29T08:06:49 | 2023-03-29T08:06:49 | {} | MEMBER |
vuejs | core | 1,488,390,927 | 7,836 | sxzz | @sto3psl Yes I think so! | 2023-03-29T11:05:02 | 2023-03-29T11:05:02 | {
"hooray": 2
} | MEMBER |
vuejs | core | 1,486,470,749 | 7,511 | yyx990803 | fix in https://github.com/vuejs/core/commit/2e074a70091e76359e930e733785100cd7dc66ed was incorrect. | 2023-03-28T08:55:46 | 2023-03-28T08:55:46 | {} | MEMBER |
vuejs | core | 1,486,840,705 | 7,969 | baiwusanyu-c | It seems that you want to be able to define a verification function when the v-model is updated. If the data verification fails, it will not be updated.
In my opinion, v-model on the native dom does not seem to have this ability, you can do a high-level component package to achieve your needs (https://vuejs.org/guide/... | 2023-03-28T12:58:02 | 2023-03-28T12:58:02 | {} | MEMBER |
vuejs | core | 1,487,901,579 | 7,975 | privatenumber | Allowing a way to use native `<template>` makes sense and is cool, but the DX is quite unintuitive. I think most users would assume `<template>` to be a special Vue.js element.
Are there real use-cases for native `<template>` in Vue.js? Seems like there wouldn't/shouldn't be, given a major point of adopting Vue.js i... | 2023-03-29T03:41:09 | 2023-03-29T03:41:09 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,490,299,546 | 7,982 | pikax | > One more question - what about dynamic slot names?
Yes
This would be possible:
```ts
interface MyAwesomeType {
title: string;
age: number;
}
const slots = defineSlots<{
[name in `col.${keyof MyAwesomeType}`]?: { item: MyAwesomeType, index: number };
}>()
slots['col.age']
slots['col.ti... | 2023-03-30T13:23:56 | 2023-03-30T13:23:56 | {
"+1": 8
} | MEMBER |
vuejs | core | 1,481,668,626 | 7,836 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4503798855)
| suite | result |
|-------|--------|
| [naive-ui](https://github.com/vuejs/ecosystem-ci/actions/runs/4503798855/jobs/7927464560) | :x: failure |
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4503798855/jobs/7927... | 2023-03-23T18:06:01 | 2023-03-23T18:12:34 | {} | CONTRIBUTOR |
vuejs | core | 1,483,927,675 | 7,218 | xieyuheng | @edison1105
I found that I can use component to do the following:
`components/Scope.vue`:
```vue
<script setup lang="ts">
import { reactive } from 'vue'
defineProps<{ scope: any }>()
</script>
<template>
<slot :scope="reactive(scope)" />
</template>
```
`Example.vue`:
```vue
<Scope :scope... | 2023-03-25T21:37:38 | 2023-03-25T21:59:40 | {
"eyes": 2,
"rocket": 1
} | NONE |
vuejs | core | 1,484,860,212 | 7,921 | Jevon617 | The reason is that, during the first mount, the `loading` changed in the `onMounted` hook, triggering `patch`. Vue only processed the dynamic node `span`, while for the static node `h1`, because its `parentComponent` (`SomeSlotComponent` in the demo) is a component from a JavaScript file, vite-plugin-vue does not add `... | 2023-03-27T10:04:08 | 2023-03-27T10:04:08 | {
"confused": 1
} | NONE |
vuejs | core | 1,485,653,558 | 7,836 | sto3psl | @sxzz @sodatea is there a chance that this change might land in Vue 3.3? | 2023-03-27T18:25:27 | 2023-03-27T18:25:27 | {} | CONTRIBUTOR |
vuejs | core | 1,486,160,323 | 7,068 | yyx990803 | @sxzz did you end up re-creating https://github.com/vitejs/vite/pull/10888 for https://github.com/vitejs/vite-plugin-vue? | 2023-03-28T03:44:25 | 2023-03-28T03:44:25 | {} | MEMBER |
vuejs | core | 1,486,501,910 | 7,548 | yyx990803 | This is still a compiler issue - union / intersection types containing unknown types were not handled correctly. In the case of #7511 it should have generated `null` due to the type of the `Enum` not inferable (which we technically can fix, but is a separate issue).
see 5fb406e3 | 2023-03-28T09:17:01 | 2023-03-28T09:17:09 | {} | MEMBER |
vuejs | core | 1,486,600,557 | 7,548 | sxzz | @yyx990803 But we introduced a breaking change now.
[Demo](https://sfc.vuejs.org/#eNqFUUFOwzAQ/MrKl4LUxBIgIUWhKuIDHODmS9psSmi9a9lOKxTyd9ZpqdoiUd9mZmfHmu3Vs3P5tkNVqDIsfesiBIydg01FqyejYjBqZqi1jn2EF7YOGs8WJrlOIFknhkq998qkgIjWbaqIgkBeObq0oFIfJTVV+52ZrVz+GZjkB30ymIMgwQWMTOIkJ2GjPmJ0odC6I7de5Uu2ei6a9h3F1mJWs53f53f5w6Ou2xB... | 2023-03-28T10:24:24 | 2023-03-28T10:24:24 | {} | MEMBER |
vuejs | core | 1,488,127,746 | 7,979 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4551688337)
| suite | result |
|-------|--------|
| [vuetify](https://github.com/vuejs/ecosystem-ci/actions/runs/4551688337/jobs/8026071865) | :white_check_mark: success |
| 2023-03-29T08:07:14 | 2023-03-29T08:13:49 | {} | CONTRIBUTOR |
vuejs | core | 1,490,232,828 | 7,982 | sxzz | @pikax I agree with you. We should have a better DX about slots, but I think we need more discussions about it and we likely need to add runtime code. So maybe in another PR? | 2023-03-30T12:39:58 | 2023-03-30T12:39:58 | {} | MEMBER |
vuejs | core | 1,490,266,527 | 7,982 | jacekkarczmarczyk | Would it be possible to type-check missing slots or would it rather be a task for eslint or other tools? | 2023-03-30T13:02:27 | 2023-03-30T13:02:27 | {} | CONTRIBUTOR |
vuejs | core | 1,482,469,181 | 7,939 | edison1105 | see https://github.com/vuejs/core/pull/3450#issue-835751911
another PR https://github.com/vuejs/core/pull/6508 | 2023-03-24T09:04:20 | 2023-03-24T09:05:44 | {} | MEMBER |
vuejs | core | 1,486,635,530 | 7,457 | baiwusanyu-c | I'm turning it into a draft for now, to fix he has to recognize both inputs from the compiler and fix this at runtime, I think it's a lot of cost and not worth the cost
@sodatea | 2023-03-28T10:49:43 | 2023-03-28T10:49:43 | {} | MEMBER |
vuejs | core | 1,488,252,966 | 7,979 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4552400256)
| suite | result |
|-------|--------|
| [naive-ui](https://github.com/vuejs/ecosystem-ci/actions/runs/4552400256/jobs/8027688798) | :x: failure |
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4552400256/jobs/8027... | 2023-03-29T09:26:06 | 2023-03-29T09:35:42 | {} | CONTRIBUTOR |
vuejs | core | 1,490,340,512 | 7,968 | Azurox | I believe this is linked to #4404 and #4314 . It would be nice if this was merged, currently the only way to bypass it is a "fix" that breaks slots | 2023-03-30T13:49:47 | 2023-03-30T13:49:47 | {} | NONE |
vuejs | core | 1,481,667,960 | 7,836 | sxzz | /ecosystem-ci run | 2023-03-23T18:05:39 | 2023-03-23T18:05:39 | {} | MEMBER |
vuejs | core | 1,483,603,862 | 7,083 | johnsoncodehk | > Also, can we use something like
>
> ```ts
> /** @jsxImportSource @vue/jsx */
> ```
This works. I think users should be required to explicitly specify it in tsconfig compilerOptions instead of implicitly adding it automatically in virtual code.
The PR seems to have issues with `"jsxImportSource": "@vue/jsx"... | 2023-03-24T23:53:57 | 2023-03-24T23:53:57 | {} | MEMBER |
vuejs | core | 1,483,962,308 | 7,956 | FreezeNow | I find this in vue 3 document, but when i remove mode="out-in", it work. Why? This behaves as if the docs are outdated.
tell a joke: it is a feature not a bug. | 2023-03-26T01:04:19 | 2023-03-26T02:40:38 | {} | NONE |
vuejs | core | 1,484,101,225 | 7,959 | leopiccionia | Keys should be handled; they're passed as part of the second argument of `h`.
See example in docs: https://vuejs.org/guide/extras/render-function.html#v-for | 2023-03-26T13:43:39 | 2023-03-26T14:11:02 | {} | CONTRIBUTOR |
vuejs | core | 1,488,265,355 | 7,979 | yyx990803 | /ecosystem-ci run | 2023-03-29T09:35:07 | 2023-03-29T09:35:07 | {} | MEMBER |
vuejs | core | 1,490,116,714 | 7,982 | sxzz | @pikax Thanks for your review. I've changed the style of the definition.
But I think it should be
```ts
expectType<undefined | ((param: { foo: string; bar: number }) => VNode[])>(
slots.default
)
```
because if the parent component didn't pass the slot, the slot is undefined. And if the parent component d... | 2023-03-30T11:11:02 | 2023-03-30T11:30:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,481,761,631 | 7,836 | sto3psl | Seems like Nuxt doesn't like the bundle size increase and naive-ui seems unrelated(?) | 2023-03-23T19:17:04 | 2023-03-23T19:17:04 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,482,213,309 | 7,841 | GodAraden | > You can try `ToRefs` type and code below
>
> ```ts
> type PartialRef<O, K extends keyof O> = ToRefs<Pick<O, K>> & Omit<O, K>
> ```
>
> https://www.typescriptlang.org/play?#code/JYWwDg9gTgLgBDAnmApnA3nAKhASigMwGcAaOfAuAXzgKghDgHIA3AVxSYChRJYM4KAB6oAxjCzIUAeUo06DZsLEwAtElTcuGtNIBGAKzgBeDFzi0IEAFxwiMKMAB2Ac3Nwne... | 2023-03-24T03:57:04 | 2023-03-24T03:57:04 | {} | NONE |
vuejs | core | 1,483,836,746 | 7,953 | trandaison | @LinusBorg I want to get the component name and the component path for a custom composable. I found that the `$options` contains `__name` and `__file` property. | 2023-03-25T14:23:31 | 2023-03-25T14:23:31 | {} | NONE |
vuejs | core | 1,488,339,900 | 7,979 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4552949445)
| suite | result |
|-------|--------|
| [naive-ui](https://github.com/vuejs/ecosystem-ci/actions/runs/4552949445/jobs/8028926111) | :x: failure |
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4552949445/jobs/8028... | 2023-03-29T10:28:05 | 2023-03-29T10:43:44 | {} | CONTRIBUTOR |
vuejs | core | 1,490,084,302 | 7,991 | LinusBorg | `@vue/reactivity` low-level `effect()` is synchronous unless you provide a scheduler.
You want to be using `watchEffect` from the `vue` package | 2023-03-30T10:45:09 | 2023-03-30T10:45:19 | {} | MEMBER |
vuejs | core | 1,483,995,275 | 6,690 | tachibana-shin | >
> @tachibana-shin
>
> I found that I can define a component to do the following (not as ideal as a proper `v-scope`).
>
> `components/Scope.vue`:
>
> ```
> <script setup lang="ts">
> import { reactive } from 'vue'
>
> defineProps<{ scope: any }>()
> </script>
>
> <template>
> <slot :scope... | 2023-03-26T04:53:44 | 2023-03-26T04:53:44 | {} | NONE |
vuejs | core | 1,484,075,677 | 5,318 | phil294 | > Does any of you have at least a suggestion?
instead of `Object.defineProperty`, I solved this problem with `markRaw` as hinted above - not sure why it doesn't work for you. In my case, I changed my pinia getter from
```js
{
...,
children: [...],
parent: parent
}
```
to
```js
{
...,
static: ma... | 2023-03-26T12:02:47 | 2023-03-26T12:02:47 | {} | NONE |
vuejs | core | 1,486,084,160 | 7,276 | yxchai | > @yxchai I have a workaround but very specific to my project and that might not work for you, or not be what you need, If you're still interested in it lemme know.
Thanks for the reply, @dbssman, I was able to work out a way in my project specifically. So, all good here. | 2023-03-28T01:38:40 | 2023-03-28T01:38:40 | {
"heart": 1
} | NONE |
vuejs | core | 1,487,987,815 | 7,979 | haoqunjiang | /ecosystem-ci run | 2023-03-29T05:55:51 | 2023-03-29T06:49:00 | {} | MEMBER |
vuejs | core | 1,487,994,306 | 7,979 | haoqunjiang | /ecosystem-ci run | 2023-03-29T06:03:24 | 2023-03-29T08:07:05 | {} | MEMBER |
vuejs | core | 1,490,116,506 | 7,991 | skirtles-code | The `[...b]` and `b.push()` inside the effect will be registering different dependencies on `b`. Both of these are being triggered by the external `b.push()`, so they each trigger the effect. The scheduler handles the deduplication when using `watchEffect`, but if you use `effect` directly you will get the same effect ... | 2023-03-30T11:10:52 | 2023-03-30T11:10:52 | {} | CONTRIBUTOR |
vuejs | core | 1,482,373,630 | 7,719 | Tanglongwen | Agree！
In vue2，users can get all registered events functions from parent by `_events`. But now I have to declare v-bind="attrs" in parent component, for that child component can get access to events name called onXXX. It makes complex to use component | 2023-03-24T07:32:59 | 2023-03-24T07:32:59 | {} | NONE |
vuejs | core | 1,482,166,781 | 5,085 | morlay | @yyx990803 `react-jsx` just make a way to let us to define any jsx not just react
Once vue provider exports `vue/jsx-runtime` and `vue/jsx-dev-runtime`,
We could easy to make use to use vue jsx with current build tools `typescript/esbuild/swc`, not only `babel`.
Just with options `"jsx": "react-jsx"` and `"jsxImp... | 2023-03-24T02:32:08 | 2023-03-24T07:44:15 | {} | NONE |
vuejs | core | 1,486,310,108 | 7,968 | yanyunwu | can you help me? | 2023-03-28T06:51:09 | 2023-03-28T06:51:09 | {
"confused": 2
} | NONE |
vuejs | core | 1,487,503,328 | 7,973 | sxzz | Will fix soon. | 2023-03-28T19:46:41 | 2023-03-28T19:46:41 | {} | MEMBER |
vuejs | core | 1,487,812,853 | 7,975 | Justineo | It’s by design in Vue 3: https://vuejs.org/api/built-in-special-elements.html#template | 2023-03-29T01:19:46 | 2023-03-29T01:19:46 | {} | MEMBER |
vuejs | core | 1,488,516,177 | 7,949 | yyx990803 | I should've looked at ecosystem CI results before merging 😅 | 2023-03-29T12:32:03 | 2023-03-29T14:06:14 | {} | MEMBER |
vuejs | core | 1,484,085,999 | 7,958 | remcohaszing | It’s awesome to see Vue adding support for the JSX automatic runtime! :tada:
I spotted some bugs though. #7959 explains and resolves them. | 2023-03-26T12:44:55 | 2023-03-26T12:44:55 | {} | CONTRIBUTOR |
vuejs | core | 1,484,886,875 | 7,737 | Pryscy | But the react jsx type for input is more restricted too :
value?: string | ReadonlyArray<string> | number | undefined;
https://github.com/DefinitelyTyped/DefinitelyTyped/blob/1510fcc8ca198002a13660cac2eafc2786165ce1/types/react/index.d.ts#LL2256C13-L2256C13
For Vue, on input, we have "any" with no restriction,... | 2023-03-27T10:19:26 | 2023-03-27T10:19:26 | {} | NONE |
vuejs | core | 1,486,222,126 | 7,365 | sxzz | ? | 2023-03-28T05:05:42 | 2023-03-28T05:05:42 | {} | MEMBER |
vuejs | core | 1,490,263,459 | 7,982 | pikax | I don't have a strong opinion on either be done on this or another PR, what I think is a bit odd the syntax be very similar to `defineProps`
```ts
const props = defineProps<{
a?: string; // explicit optional
b: string;
}>();
expectType<number | undefined>(prop.a)
expectType<number>(prop.b)
const slot... | 2023-03-30T13:00:17 | 2023-03-30T13:01:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,481,637,251 | 7,851 | sxzz | Supported already 53e3533b75adc32f979adde34bde3b581e48084b | 2023-03-23T17:53:09 | 2023-03-23T17:53:19 | {} | MEMBER |
vuejs | core | 1,482,177,888 | 5,119 | morlay | @yyx990803 Could we re-open this? It is important for developer use vue-jsx without babel.
`react-jsx` now is standard interface to pass JSX `tag` `key`, and `props` ( includes `children` )
`jsx(type, props: { children, ...otherProps }, key)` for single child
`jsxs(type, props: { children, ...otherProps }, key)`... | 2023-03-24T02:51:58 | 2023-03-24T02:51:58 | {} | NONE |
vuejs | core | 1,483,236,540 | 6,951 | linspw | It still doesn't work | 2023-03-24T18:24:23 | 2023-03-24T18:24:23 | {} | NONE |
vuejs | core | 1,483,788,452 | 7,953 | LinusBorg | There's no public API for this. what's your use case? | 2023-03-25T10:26:26 | 2023-03-25T10:26:26 | {} | MEMBER |
vuejs | core | 1,483,797,909 | 7,953 | sxzz | ```vue
<script setup>
import { getCurrentInstance } from 'vue'
const i = getCurrentInstance()
console.log(i.proxy.$options)
</script>
```
> **Warning**: It's not a public API, and could be changed anytime. Use at your risk. | 2023-03-25T11:15:32 | 2023-03-26T19:26:42 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,425,694,990 | 5,752 | haoqunjiang | /ecosystem-ci run | 2023-02-10T11:45:56 | 2023-03-28T00:43:34 | {} | MEMBER |
vuejs | core | 1,486,094,279 | 7,687 | yyx990803 | Moved to `type: "module"` so cjs is no longer needed. | 2023-03-28T01:56:00 | 2023-03-28T01:56:00 | {} | MEMBER |
vuejs | core | 1,486,161,121 | 7,068 | sxzz | @yyx990803 No, I haven't done it yet. | 2023-03-28T03:46:09 | 2023-03-28T03:46:09 | {} | MEMBER |
vuejs | core | 1,490,269,680 | 7,982 | pikax | > Would it be possible to type-check missing slots or would it rather be a task for eslint or other tools?
It would be possible to do typechecking, altho not sure how Volar is currently doing (with JSX) but if used `h`, is possible to typecheck it to see if is passed.
/cc @johnsoncodehk | 2023-03-30T13:04:34 | 2023-03-30T13:04:34 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,481,669,253 | 7,949 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4503802129)
| suite | result |
|-------|--------|
| [naive-ui](https://github.com/vuejs/ecosystem-ci/actions/runs/4503802129/jobs/7927650282) | :x: failure |
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4503802129/jobs/7927... | 2023-03-23T18:06:20 | 2023-03-23T18:23:32 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.