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,758,095,301 | 9,379 | haoqunjiang | I think the pinia failure isn't relevant; its main branch's CI has been failing since just a few hours ago: https://github.com/vuejs/pinia/actions/runs/6483605215/job/17605582340 | 2023-10-11T16:47:02 | 2023-10-11T16:47:02 | {} | MEMBER |
vuejs | core | 1,759,545,715 | 9,387 | sxzz | Closing this since the minimum compatibility of browsers is ES2015. | 2023-10-12T12:45:23 | 2023-10-12T12:45:23 | {} | MEMBER |
vuejs | core | 1,761,319,648 | 9,392 | pikax | @edison1105 I don't think the solution is good enough, from what I could gather this is caused by the [renderer.ts](https://github.com/vuejs/core/blob/main/packages/runtime-core/src/renderer.ts#L2095)
Basically the `unmount` is being called multiple times on the `vnode`, I wonder if we could replace the condition on... | 2023-10-13T10:56:02 | 2023-10-13T10:56:02 | {} | MEMBER |
vuejs | core | 1,761,448,394 | 9,392 | edison1105 | @pikax
That's a great idea. I changed the solution. | 2023-10-13T12:37:20 | 2023-10-13T12:37:20 | {} | MEMBER |
vuejs | core | 1,762,516,240 | 7,963 | sxzz | Currently we cannot use generic + typed emits or slots (in other words only `props` can) due to limitation of TS | 2023-10-14T03:01:47 | 2023-10-14T03:01:47 | {} | MEMBER |
vuejs | core | 1,763,405,352 | 5,912 | binary-signal | @johnsoncodehk wow amazing work!!! | 2023-10-15T14:23:38 | 2023-10-15T14:23:38 | {} | NONE |
vuejs | core | 1,761,118,161 | 9,397 | mu-yu | Vue2 works fine as expected, vue3 with dev mode works fine, too.
**This issue is only occured in vue3 after build.** | 2023-10-13T08:24:26 | 2023-10-13T08:26:35 | {} | NONE |
vuejs | core | 1,764,728,198 | 9,413 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 85.9 kB (**+38 B**) | 32.7 kB (**+4 B**) | 29.5 kB (**+6 B**) |
| v... | 2023-10-16T15:21:09 | 2023-10-16T15:34:10 | {} | NONE |
vuejs | core | 1,761,498,372 | 9,396 | LinusBorg | these classes are not meant to stay on the element. they are added for one frame at the end, and removed right after the transition finishes. So this works as intended.
> `v-enter-to`: Ending state for enter. Added one frame after the element is inserted (at the same time v-enter-from is removed), removed when the t... | 2023-10-13T13:11:45 | 2023-10-13T13:12:01 | {} | MEMBER |
vuejs | core | 1,764,126,756 | 9,381 | pikax | I believe this is caused by the language service not by vue core
/cc @johnsoncodehk | 2023-10-16T09:57:06 | 2023-10-16T09:57:06 | {} | MEMBER |
vuejs | core | 1,757,595,825 | 4,809 | posva | This can already be achieved with `app.runWithContext(() => inject('key'))` so maybe it's not needed anymore | 2023-10-11T12:37:57 | 2023-10-11T12:37:57 | {} | MEMBER |
vuejs | core | 1,761,581,808 | 5,920 | sebastianvitterso | I ran into the same issue today, the issue has to do with protected properties on classes used inside `reactive`:
```vue
<script setup lang="ts">
import { reactive } from 'vue'
class Person {
constructor(public name: string){}
protected species = "HUMAN"
}
const names = [ "Jim", "Pam" ]
const people = ... | 2023-10-13T14:06:06 | 2023-10-13T14:10:56 | {} | NONE |
vuejs | core | 1,761,625,166 | 9,343 | OBe95 | @pikax I just pushed some tests, let me know if you think of others | 2023-10-13T14:34:05 | 2023-10-13T14:34:05 | {} | NONE |
vuejs | core | 1,761,647,990 | 9,314 | sxzz | Duplicate of #8904 | 2023-10-13T14:49:21 | 2023-10-13T14:49:21 | {} | MEMBER |
vuejs | core | 1,761,926,047 | 9,134 | pikax | The error is not present but the behaviour is incorrect:
[playground](https://deploy-preview-9134--vue-sfc-playground.netlify.app/#eNqtVE2PmzAQ/SsjLslKBKJGlSqapE2qPbSHttrNkYsLA/Eu2Mg2bKIo/71jOwsoaStV2pvn6817MwOnYNM0UddikARLnSneGNBo2madCl43Uhk4QY4FF/hFki1QmBD2IQg8mB3PnkPQe1ZV8uUBCzhDoWQNE8KbfExFJoU20NdtYHUNNT2lAkChyFEl... | 2023-10-13T17:42:57 | 2023-10-13T17:42:57 | {} | MEMBER |
vuejs | core | 1,763,576,789 | 9,407 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 85.9 kB | 32.6 kB | 29.5 kB |
| vue.global.prod.js | 132 kB | 49.3 kB | 44.4 kB |
### Usages
| Name | Size |... | 2023-10-16T01:08:50 | 2023-10-16T01:08:50 | {} | NONE |
vuejs | core | 1,758,093,632 | 9,379 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/6485437949)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/6478163140) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2023-10-11T16:45:51 | 2023-10-11T16:45:51 | {} | CONTRIBUTOR |
vuejs | core | 1,759,669,301 | 9,388 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 85.9 kB (**+14 B**) | 32.7 kB (**+19 B**) | 29.5 kB (**+19 B**) |
... | 2023-10-12T14:00:02 | 2023-10-12T20:34:03 | {} | NONE |
vuejs | core | 1,760,344,466 | 5,844 | pikax | Just to give an update on this, I've created a PR https://github.com/vuejs/core/pull/9388 aimed to fix this
https://github.com/vuejs/core/assets/4620458/6f81918c-f4ab-407e-be33-ec818fd96aad
It's working, but since this is touching Suspense, I would expect more scrutiny while reviewing, because it can be very easy... | 2023-10-12T20:47:58 | 2023-10-12T20:47:58 | {
"eyes": 3,
"heart": 11,
"hooray": 2
} | MEMBER |
vuejs | core | 1,761,160,760 | 8,376 | KaelWD | Minimal reproduction:
```ts
import type {
ComponentPropsOptions,
ComputedOptions,
MethodOptions,
ComponentOptionsMixin,
EmitsOptions,
SlotsType,
ComponentOptionsWithObjectProps,
DefineComponent,
ComponentInjectOptions,
} from 'vue'
// overload 4 from vue: object format with object pro... | 2023-10-13T08:55:47 | 2023-10-13T09:00:31 | {} | CONTRIBUTOR |
vuejs | core | 1,761,412,003 | 9,328 | pikax | @antfu can you add a test pls | 2023-10-13T12:10:07 | 2023-10-13T12:10:07 | {} | MEMBER |
vuejs | core | 1,761,506,879 | 9,380 | LinusBorg | Shouldn't the compiler be able to recognize this as a stable slot instead of falling back on `/* DYNAMIC */`?
This appears to me like a compiler issue, not a reactivity issue.
| 2023-10-13T13:18:02 | 2023-10-13T13:20:06 | {} | MEMBER |
vuejs | core | 1,763,590,902 | 9,396 | cess123456 | 
| 2023-10-16T01:29:34 | 2023-10-16T01:29:34 | {} | NONE |
vuejs | core | 1,764,379,233 | 9,139 | vvkk77 | Hi @sxzz , When are you planning to release the new version of Vue 3.4. It's great that you are resolving container exposure in custom elements. My team heavily depends on custom elements. | 2023-10-16T12:34:38 | 2023-10-16T12:34:38 | {
"+1": 4,
"eyes": 4,
"hooray": 1,
"rocket": 2
} | NONE |
vuejs | core | 1,757,083,728 | 9,375 | kaine0923 | duplicate of #9071 | 2023-10-11T08:10:38 | 2023-10-11T08:10:38 | {} | CONTRIBUTOR |
vuejs | core | 1,757,300,733 | 9,369 | RodrigoProjects | @sadeghbarati the problem here is not the mismatch (the same happened at this issue and it got closed early https://github.com/nuxt/nuxt/issues/23590), it's the fact the error of a mismatch is not shown if we use an Async Component vs an inline import.
Thanks anyways! :) | 2023-10-11T09:55:59 | 2023-10-11T09:55:59 | {
"+1": 1,
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 1,758,072,789 | 9,379 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 85.9 kB | 32.6 kB | 29.5 kB |
| vue.global.prod.js | 132 kB | 49.3 kB | 44.4 kB |
### Usages
| Name | Size |... | 2023-10-11T16:31:41 | 2023-10-11T16:31:41 | {} | NONE |
vuejs | core | 1,758,871,399 | 9,071 | yangtoude | @edison1105 is this bug fixed？ | 2023-10-12T03:54:15 | 2023-10-12T03:54:15 | {} | NONE |
vuejs | core | 1,759,286,358 | 9,071 | edison1105 | @yangtoude Not yet. the PR is still open. | 2023-10-12T09:46:50 | 2023-10-12T09:46:50 | {} | MEMBER |
vuejs | core | 1,761,176,047 | 8,376 | KaelWD | Looks like we might be able to work around this by defining an intermediary type:
```ts
type ExtendDefineComponent<
Props = {},
RawBindings = {},
D = {},
C extends ComputedOptions = {},
M extends MethodOptions = {},
Mixin extends ComponentOptionsMixin = ComponentOptionsMixin,
Extends extends Comp... | 2023-10-13T09:06:57 | 2023-10-13T09:06:57 | {} | CONTRIBUTOR |
vuejs | core | 1,761,641,250 | 5,920 | sebastianvitterso | I can add: I think this is because `UnwrapRefSimple<T>` depends on the `keyof` operator, which [according to this comment in the TS repo](https://github.com/microsoft/TypeScript/issues/50668#issuecomment-1239139886) "intentionally does not include non-public members".
So it might not be something that we can get ar... | 2023-10-13T14:45:03 | 2023-10-14T10:10:53 | {} | NONE |
vuejs | core | 1,757,045,543 | 9,370 | edison1105 | @Disservin Yes, The root cause is the same. | 2023-10-11T07:49:27 | 2023-10-11T07:49:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,757,707,716 | 9,372 | stafyniaksacha | > Maybe worth comparing to #8530.
I've changed the behavior when having ref/reactive in input, now it converts to `shallowRef`. I also implemented `toShallowRef({ nested: { foo: 1 }}, 'nested')` to match `toRef`.
Furthermore, I also took care about `isShallow(toShallowRef(..))` via `__v_isShallow` internal flag
... | 2023-10-11T13:31:21 | 2023-10-11T13:31:21 | {} | NONE |
vuejs | core | 1,760,711,421 | 9,386 | edison1105 | /cc @so1ve | 2023-10-13T03:36:47 | 2023-10-13T03:36:47 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,763,357,187 | 9,328 | antfu | > @antfu can you add a test pls
I'd love to, but we didn't even have any tests for devtools. It might be better to delegate that to another PR. | 2023-10-15T11:14:53 | 2023-10-15T11:14:53 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,764,570,196 | 9,257 | trudbot | Generics cannot be used in the way you are doing; in your code, the T is treated as a concrete type.
```
type Props<T> = {
color?: T;
}
withDefaults(
defineProps<Props<Color>>(),
{
color: Color.RED,
}
);
``` | 2023-10-16T14:11:27 | 2023-10-16T14:11:27 | {} | NONE |
vuejs | core | 1,764,839,970 | 9,336 | davidmatter | @pikax thanks, rolled back the import ordering | 2023-10-16T16:22:11 | 2023-10-16T16:22:11 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 1,764,985,036 | 9,329 | haoqunjiang | It's been two weeks now. So, I'm closing this issue.
If you encounter similar issues again and can follow up with more information, please open a new issue with a reference to this one. | 2023-10-16T17:51:44 | 2023-10-16T17:51:44 | {} | MEMBER |
vuejs | core | 1,451,372,289 | 4,906 | emrysctl | > > > 像这样声明一个组件，props 是默认为浏览器原生标签的 props。道具无法获取名称和年龄...😟这似乎与预期的行为不一致，也许我误解了？
> >
> >
> > 我认为你应该定义道具。
> > ```js
> > interface TestProps {
> > name: string;
> > age?: number;
> > }
> >
> > export const Test = defineComponent<TestProps>(function Test(props) {
> > return () => {
> > return <div>{p... | 2023-03-02T06:38:57 | 2023-03-02T06:38:57 | {} | NONE |
vuejs | core | 1,455,128,195 | 7,830 | zhangenming | 这里应该有个优化点, 不知道是否有必要实现
考虑``` ret[i] = renderItem(source[i], i, void 0, cached && cached[i]);```
是不是可以改成```ret[i] = renderItem(source, i, void 0, cached && cached[i]);```
或者其他形式
目的是为了减少不必要的source[i]访问
当cache命中的时候
source[i]是没有必要求值的
这样可以减少大部分proxy带来的消耗
我这个场景下 额外的成本还是挺高的 如下图
这里的renderList里的get成本都是source[i]带来的... | 2023-03-05T15:48:19 | 2023-03-05T16:38:54 | {} | CONTRIBUTOR |
vuejs | core | 1,455,490,967 | 7,834 | baiwusanyu-c | 
https://vuejs.org/api/built-in-special-elements.html#slot
As the document says, attributes other than `name` will be passed as props of scoped slots when applied to slots, so it is urgent to bind `ref` in t... | 2023-03-06T05:44:46 | 2023-03-06T05:44:46 | {} | MEMBER |
vuejs | core | 1,456,164,323 | 7,836 | sxzz | I pushed a commit to fix unit tests. Please don't forget to pull before committing | 2023-03-06T13:46:56 | 2023-03-06T13:46:56 | {} | MEMBER |
vuejs | core | 1,457,346,566 | 7,699 | puppet-666 | 
@DavidAwing
After looking at the compiled result, the comment node is also a case of vnode, so there is no problem with `useSlots().default` being true. But I still think this performance makes me confu... | 2023-03-07T01:35:10 | 2023-03-07T01:35:10 | {} | NONE |
vuejs | core | 1,457,920,344 | 7,817 | I-love-learn |
> 如果子组件只有一个跟节点且在没有设置 `inheritAttrs: false` 的情况下，传递给子组件的属性会自动应用到这个根节点上。
ok thanks
| 2023-03-07T10:24:33 | 2023-03-07T10:24:33 | {} | NONE |
vuejs | core | 1,453,013,321 | 7,817 | baiwusanyu-c | If the component does not define `props`, then all the properties on the template will be inherited by the elements rendered by the component, including the compiled attribute `onUpdate:modelValue` of `v-model`, which makes there are two `onUpdate:modelValue` events on the input element, I am not sure if this is a bug,... | 2023-03-03T05:54:31 | 2023-03-03T06:12:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,455,321,168 | 7,831 | edison1105 | 我在sfc playground中试了，并没有导致浏览器卡死。你得提供一个简单的demo，我们才能排查问题所在。 | 2023-03-06T02:10:06 | 2023-03-06T02:10:06 | {} | MEMBER |
vuejs | core | 1,455,387,796 | 3,045 | sxzz | Implemented via 9fda9411ec92dc703288b229106116dd0f16e5e7 | 2023-03-06T03:32:34 | 2023-03-06T03:32:34 | {} | MEMBER |
vuejs | core | 1,457,360,748 | 7,699 | puppet-666 | 
One more question is: since the comment node vnode is created, why is this comment not mounted when viewing dom? | 2023-03-07T01:45:53 | 2023-03-07T01:45:53 | {} | NONE |
vuejs | core | 1,457,636,266 | 7,840 | asuishi | slot.default is a function ,so Boolean(slot.default) always be true
interface ComponentPublicInstance {
$slots: { [name: string]: Slot }
}
type Slot = (...args: any[]) => VNode[] | 2023-03-07T06:51:58 | 2023-03-07T06:51:58 | {} | NONE |
vuejs | core | 1,457,710,569 | 7,836 | sto3psl | @sxzz I added the guard for missing `MathMLElement`s and normalized the type in `app.mount`. I didn't find other public APIs, do you know of any? After checking the Vue docs, the 2nd and 3rd argument to [`app.mount`](https://vuejs.org/api/application.html#app-mount) aren't even documented (which is fine in my opinion). | 2023-03-07T07:54:51 | 2023-03-07T07:54:51 | {} | CONTRIBUTOR |
vuejs | core | 1,458,097,136 | 4,356 | larryval | Hi DBTK1990,
my Discord userName : \_larry\_
As I said, my entire app is attached to a shadowRoot tag, as shown in the simplified code below, I just added your code by replacing `vueService.CurrentApp` by the instance of my application `app`.
VueDevtools works in this config (Pinia ok, cool!), but there is somet... | 2023-03-07T12:35:19 | 2023-03-07T12:35:19 | {} | NONE |
vuejs | core | 1,450,147,234 | 7,808 | LinusBorg | I can't really reproduce any leak. My experience:
1. In a prod build, memory always drops back to <10MB for me on the Home route, once I finished switching back & forth
2. In dev, Memory always drops back to ~67MB (size of one component), no matter the route I stop on. It seems the previous component is being cache... | 2023-03-01T13:21:52 | 2023-03-01T13:21:52 | {} | MEMBER |
vuejs | core | 1,451,459,048 | 2,497 | panstromek | I bumped into this, too. Some nicer error would be appreciated, because it was just one of many breakages I was dealing with during migration, so it took some time to find out what is the cause. Currently there's no indication of what to look for when you see this error.
Note that if the element is inside a transiti... | 2023-03-02T08:10:02 | 2023-03-02T08:10:02 | {} | NONE |
vuejs | core | 1,454,783,801 | 7,821 | yangxiuxiu1115 | Maybe it's intentional. I found this comment in the source code.
https://github.com/vuejs/core/blob/98f1934811d8c8774cd01d18fa36ea3ec68a0a54/packages/runtime-core/src/components/Teleport.ts#L243 | 2023-03-04T15:51:37 | 2023-03-04T15:51:37 | {} | CONTRIBUTOR |
vuejs | core | 1,455,385,401 | 7,834 | baiwusanyu-c | As far as I know, the `ref` attribute only seems to be supported on normal `dom` elements as well as on components🤔 | 2023-03-06T03:27:38 | 2023-03-06T03:28:22 | {} | MEMBER |
vuejs | core | 1,455,693,253 | 7,832 | LinusBorg | We would have to ask Evan what the exact use case here is. the line about "Vetur and TSX" (we not have Volar as the default IDE extension) sounds like this type is overload is being used by tooling when converting Vue SFCs into a TSX-like representation for TSC support. I could be wrong though.
At the runtime level,... | 2023-03-06T08:25:25 | 2023-03-06T08:29:18 | {} | MEMBER |
vuejs | core | 1,457,655,844 | 7,839 | LinusBorg | That's likely because you use unplugin-vue-components, which will add import statements for any component it finds in src/components.
you end up with two paths to the component:
1. The direct import addded by the plugin
2. The indirect import from the barrel entry in /components/index, which you use for the compon... | 2023-03-07T07:04:07 | 2023-03-07T07:04:07 | {} | MEMBER |
vuejs | core | 1,452,895,456 | 6,222 | yiaokan | 如果你使用vue3.2x的版本还有相同的问题，使用的是官网推荐的router-view > keep-alive > suspense > component ，那你可以尝试下下面这个模板，个人通过几台电脑测试了一下是可以跑得通的。
| 2023-03-03T03:12:10 | 2023-03-03T03:14:10 | {} | NONE |
vuejs | core | 1,453,068,114 | 7,817 | yangxiuxiu1115 | I think it may be a bug. I found this comment in the source code.
https://github.com/vuejs/core/blob/98f1934811d8c8774cd01d18fa36ea3ec68a0a54/packages/runtime-core/src/componentRenderUtils.ts#L141-L144
| 2023-03-03T06:59:22 | 2023-03-03T06:59:22 | {} | CONTRIBUTOR |
vuejs | core | 1,454,664,993 | 4,733 | lehni | Here my version of `hasSlotContent()`, along with other useful helpers. I found it a bit easier to understand what's actually happening when structured this way:
```js
import { Comment } from 'vue'
export function hasSlotContent(slot, props = {}) {
return !isSlotEmpty(slot, props)
}
export function isSlo... | 2023-03-04T08:34:53 | 2023-03-04T08:35:12 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,454,940,985 | 7,819 | skirtles-code | Wouldn't this change break valid uses of attribute inheritance to pass along `v-model` to components?
* [Current `main` - works](https://sfc.vuejs.org/#eNqFkc1OwzAQhF9lsZDaSk18j1JEi7hz4oI5pMmGpo1/ZDvhEOXdWSdRA6WUm9cz/nY927GtMXHbIEtY6nJbGQ8OfWMehKqk0dZDBxZL6KG0WsKCrIuz9HSo6mI7KTEfy0Aji1C5Vs5Dm9WwCYhlmdUOV0KlfGxELajwK... | 2023-03-05T00:47:38 | 2023-03-05T00:47:38 | {} | CONTRIBUTOR |
vuejs | core | 1,455,114,103 | 7,820 | baiwusanyu-c | > > Oh, we need to use the MathML namespace like we use SVG namespace for SVG elements. That will be a bigger change than initially expected.
>
> @LinusBorg This is exactly right. I just checked the code and made it work with MathML.
>
> <img alt="Working MathML rendered by Vue 3" width="948" src="https://user-im... | 2023-03-05T14:54:12 | 2023-03-05T14:54:12 | {} | MEMBER |
vuejs | core | 1,455,875,289 | 7,817 | I-love-learn | @baiwusanyu-c But I still have a question,this disappears when I use msgown in the child component,this issue arises again when I remove the use of msgown from the child component template，Look at this example：
https://sfc.vuejs.org/#eNqVkU1OwzAQha8y8iYgNbZKWVUuKmLDDdh4U5ppG4h/ZE9aUJS7M05L1QaBxCrOvJn37Pk68RiC3Lco5kKn... | 2023-03-06T10:30:17 | 2023-03-06T10:30:17 | {} | NONE |
vuejs | core | 1,452,080,648 | 4,662 | SavkaTaras | Hello @yyx990803 @LinusBorg ,
I hope you are doing well.
Do you by any chance have any update on this?
Thank you so much,
Taras | 2023-03-02T15:43:22 | 2023-03-02T15:43:22 | {
"+1": 10
} | NONE |
vuejs | core | 1,452,973,117 | 7,816 | zhangenming | ```js
const r = ref(0)
watch(r, () => console.log('1'))
watchEffect(() => {
r.value
console.log('2')
})
watch(r, () => console.log('3'))
watchEffect(() => {
r.value
console.log('4')
})
r.value = 1
```
now the rersult is 4-3-2-1
Why not let ... | 2023-03-03T04:57:35 | 2023-03-03T04:57:35 | {} | CONTRIBUTOR |
vuejs | core | 1,453,170,939 | 7,818 | wenfangdu | @LinusBorg Could [StrictUnion](https://stackoverflow.com/a/65805753/7881859) help? | 2023-03-03T08:42:48 | 2023-03-03T08:42:48 | {} | NONE |
vuejs | core | 1,450,154,948 | 7,805 | yangxiuxiu1115 | #7810 Sorry, this pr does not solve this problem perfectly. I have to rethink the solution.So I closed it, I'm sorry. | 2023-03-01T13:27:50 | 2023-03-01T13:27:50 | {} | CONTRIBUTOR |
vuejs | core | 1,453,009,642 | 7,817 | I-love-learn | @baiwusanyu-c thank you 谢谢你 我第一次用issue 不会贴代码链接。I will not post code link the first time I mention errors. Thank you for your help | 2023-03-03T05:48:46 | 2023-03-03T05:48:46 | {
"+1": 1
} | NONE |
vuejs | core | 1,454,016,159 | 6,950 | justinwinslow | Any update on this? Or a workaround? | 2023-03-03T19:23:25 | 2023-03-03T19:23:25 | {} | NONE |
vuejs | core | 1,455,396,648 | 7,834 | yangxiuxiu1115 | @lyric-zemin You can use cloneVNode and withDirectives to realize your functions. I also think it can support the use of ref on slot, which is very useful in component encapsulation。 | 2023-03-06T03:48:35 | 2023-03-06T03:48:35 | {} | CONTRIBUTOR |
vuejs | core | 1,456,143,187 | 7,836 | sto3psl | Not sure why `ci / unit-test` fails. It works fine for me locally and the tests pass. | 2023-03-06T13:31:24 | 2023-03-06T13:31:24 | {} | CONTRIBUTOR |
vuejs | core | 1,457,326,562 | 7,699 | puppet-666 | I have the same question. | 2023-03-07T01:21:14 | 2023-03-07T01:21:14 | {} | NONE |
vuejs | core | 1,457,331,586 | 7,699 | puppet-666 | > I think you can find why `useSlots().default` is a function from this line:https://github.com/vuejs/core/blob/main/packages/runtime-core/src/componentSlots.ts#L130. I hope that can help you.
I think the problem is not whether `useSlots().default` is a function, but whether the comment node can be judged in slot by... | 2023-03-07T01:26:03 | 2023-03-07T01:48:16 | {} | NONE |
vuejs | core | 1,451,406,766 | 7,812 | yangxiuxiu1115 | Yes, your issue is effective. I mean that the following situation does not need to be dealt with.
As you said, the following situation is not the same as yours.
```
<script setup>
import { ref } from 'vue'
console.log('test')
const props = defineProps(['item'])
(function(){})()
</script>
``` | 2023-03-02T07:22:32 | 2023-03-02T07:24:57 | {
"+1": 1,
"rocket": 1
} | CONTRIBUTOR |
vuejs | core | 1,453,232,908 | 7,820 | LinusBorg | There's two layers to this:
1. Vue needs to add these new tags to the list of known elements, now that they have become supported amongst all major browsers.
2. Even without 1. though, I would expect for the MathML to properly render as all of the elements seem to be added to the DOM just as you would expect them t... | 2023-03-03T09:31:53 | 2023-03-03T09:38:53 | {} | MEMBER |
vuejs | core | 1,453,297,175 | 4,566 | hokkaido | @LinusBorg Stupid question, but if I have a project where I set compatConfig globally to Mode: 2 and then import a vanilla vue 3 component library (external npm dependency), does this force those components to run in Mode: 2 if they don't specifically declare a compatConfig with Mode: 3 themselves? | 2023-03-03T10:20:54 | 2023-03-03T10:21:03 | {} | NONE |
vuejs | core | 1,453,627,964 | 4,566 | LinusBorg | Yes. So to leave them in Vue 3 more you would have to add that config to those components. Can be done at runtime. | 2023-03-03T14:38:48 | 2023-03-03T14:38:48 | {} | MEMBER |
vuejs | core | 1,454,984,497 | 5,584 | activeDannyA | > I had a similar issue recently, the workaround I went with was creating a computed with a get and set. Passing the get to model and having the set emit the update.
>
> ```js
> const value = computed({
> get() {
> return props.modelValue;
> },
> set(value) {
> emit("update:modelValue", value);
... | 2023-03-05T04:07:54 | 2023-03-05T04:07:54 | {} | NONE |
vuejs | core | 1,455,098,213 | 7,817 | baiwusanyu-c | I closed the pr because I thought it over and thought it was expected
1. `InheritAttrs: false` is not set, so some attributes will be inherited by subcomponents to dom by default
2. From the source code pointed out by @RicardoErii, it can be seen that the corresponding props need to be explicitly set in the component... | 2023-03-05T13:52:07 | 2023-03-05T13:58:54 | {} | MEMBER |
vuejs | core | 1,455,279,004 | 7,831 | edison1105 | please provide a minimal reproduction.I did not reproduce the issue you mentioned. [see](https://sfc.vuejs.org/#eNp9UMtqw0AM/BVVFycQe+nVOIHe+ge97MW15cTB+0C76xYW/3tlJw2lhcKyaDSjQaOML95XcyKssQkdjz6etB2NdxwhA9MACwzsDBQiKrSlz43qaWjTFLO2AIFi8rv9VgN0zoYIJpzhuI7vileaJgdvjqf+qdjfRCwjbCGL7DAku6xd+eQ16rGFgEjGT20kQQDN5fmU82a9LI0S... | 2023-03-06T01:02:42 | 2023-03-06T01:02:42 | {} | MEMBER |
vuejs | core | 1,457,428,870 | 7,840 | puppet-666 | 
| 2023-03-07T02:56:29 | 2023-03-07T02:56:29 | {} | NONE |
vuejs | core | 1,453,041,412 | 7,818 | edison1105 | you should:
```typescript
// 👇
const a2: A = reactive<A>({
a: 'a',
b: '', // 👈 thrown
})
``` | 2023-03-03T06:24:33 | 2023-03-03T06:24:33 | {} | MEMBER |
vuejs | core | 1,455,149,549 | 7,832 | LinusBorg | In Vue, props *always* require runtime config. So what you are trying to do is not supported.
In `script setup` we support what you want in a way, with `defineProps`, which is a compiler hint that can take a generic type and the compiler generates the runtime props config from it.
| 2023-03-05T17:14:47 | 2023-03-05T17:15:04 | {} | MEMBER |
vuejs | core | 1,455,296,825 | 7,831 | bozaigao | @edison1105 项目开发过程中遇到的，用vite构建后运行到指定页面浏览器会卡死然后崩溃！后来发现这个页面中setup里导出了不存在的函数，这里我觉得vuejs应该可以优化，毕竟浏览器直接卡死崩溃这种体验太不好了 | 2023-03-06T01:34:08 | 2023-03-06T01:34:08 | {} | NONE |
vuejs | core | 1,455,323,802 | 7,831 | bozaigao | @edison1105 稍后有时间了我弄一个demo放上面 | 2023-03-06T02:13:14 | 2023-03-06T02:13:14 | {} | NONE |
vuejs | core | 1,453,051,207 | 7,817 | I-love-learn | Yes, the problem went away when I added props
| 2023-03-03T06:38:15 | 2023-03-03T06:38:15 | {} | NONE |
vuejs | core | 1,453,061,381 | 7,818 | wenfangdu | > reactive will automatically infer its type based on the incoming object
@baiwusanyu-c I simplified the object for minimal repro, the actual object is fairly complex. | 2023-03-03T06:51:25 | 2023-03-03T06:51:25 | {} | NONE |
vuejs | core | 1,454,661,049 | 3,258 | nandi95 | @yyx990803 @HcySunYang @pikax
Can we get any movement on this? | 2023-03-04T08:12:18 | 2023-03-04T08:12:18 | {} | CONTRIBUTOR |
vuejs | core | 1,455,888,613 | 7,615 | Jevon617 | It's a vite bug, and I have reported this bug to vite and provided a pr for this, [look this way](https://github.com/vitejs/vite-plugin-vue/pull/123). | 2023-03-06T10:39:22 | 2023-03-06T10:39:22 | {} | NONE |
vuejs | core | 1,456,038,427 | 7,832 | rdhelms | @LinusBorg Thanks for the RFC link - that does actually look like exactly what would help here.
I think the TS experience with the Options API would be hugely improved if users could type Props and Emits without the runtime validation. | 2023-03-06T12:22:25 | 2023-03-06T12:22:25 | {
"+1": 2
} | NONE |
vuejs | core | 1,455,655,624 | 7,803 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4341188335)
| suite | result |
|-------|--------|
| [naive-ui](https://github.com/vuejs/ecosystem-ci/actions/runs/4341188335/jobs/7580485791) | :x: failure |
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4341188335/jobs/7580... | 2023-03-06T08:03:15 | 2023-03-06T13:30:08 | {} | CONTRIBUTOR |
vuejs | core | 1,456,188,801 | 4,356 | DBTK1990 | yes it is but you dont need all of it to do it,
you can just emit the event with the current app
do you have discord?
you can use this event with the vue app
devtools.emit('app:init', vueService.CurrentApp, version, {
Fragment,
Text,
Comment,
Static
});
... | 2023-03-06T14:00:20 | 2023-03-06T14:04:29 | {} | NONE |
vuejs | core | 1,457,861,864 | 7,842 | LinusBorg | That's expected. When a component re-renders, *all* of the template is re-rendered into a new virtual DOM representation which will then be diffed. That includes all slots, as they are part of the component's template. | 2023-03-07T09:46:17 | 2023-03-07T09:46:17 | {} | MEMBER |
vuejs | core | 1,451,959,615 | 7,814 | Skuallpa | @LinusBorg OK I see. Thanks for your help! | 2023-03-02T14:30:56 | 2023-03-02T14:30:56 | {} | NONE |
vuejs | core | 1,452,708,851 | 5,401 | edimitchel | As for now, the website https://custom-elements-everywhere.com is still showing Vue as 91% web component compliant.
I raise a PR to solve that: https://github.com/webcomponents/custom-elements-everywhere/pull/2074 | 2023-03-02T23:16:09 | 2023-03-02T23:16:09 | {} | NONE |
vuejs | core | 1,452,985,900 | 7,816 | skirtles-code | I believe this is the problem reported in issue #7576.
I think the fix in #7748 is more accurate than the fix suggested here. | 2023-03-03T05:12:53 | 2023-03-03T05:12:53 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,453,064,431 | 7,818 | wenfangdu | > you should:
>
> ```ts
> // 👇
> const a2: A = reactive<A>({
> a: 'a',
> b: '', // 👈 thrown
> })
> ```
@edison1105 This usage is [officially discouraged](https://vuejs.org/guide/typescript/composition-api.html#typing-reactive).
 waiting approval. Is there anyone can look into it? @zhangzhonghe Any luck with getting the PR reviewed and released? Thanks.
I'm experiencing the same thing. And ... | 2023-03-06T02:03:44 | 2023-03-06T02:05:36 | {} | NONE |
vuejs | core | 1,455,388,734 | 7,834 | lyric-zemin | @baiwusanyu-c But support `template` and `component` | 2023-03-06T03:34:23 | 2023-03-06T03:34:23 | {} | NONE |
vuejs | core | 1,457,402,305 | 7,817 | edison1105 | > 我有个问题： 当我在子组件的template模板中 通过h1标签中使用msgown时， 这个问题就消失了， 不再出现父组件中msg也改变的问题，当我删掉h1标签中使用msgown时，这个问题就又出现了，这是什么原因呢？
如果子组件只有一个跟节点且在没有设置 `inheritAttrs: false` 的情况下，传递给子组件的属性会自动应用到这个根节点上。 | 2023-03-07T02:24:20 | 2023-03-07T02:24:20 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.