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,578,444,371 | 8,506 | sxzz | @Alfred-Skyblue
We need to call `catch` method to handle errors.
https://github.com/vuejs/core/blob/a95e612b252ae59eaf56e0b8ddba66948d4ac20e/packages/runtime-core/src/apiSetupHelpers.ts#L516
https://github.com/vuejs/core/blob/a95e612b252ae59eaf56e0b8ddba66948d4ac20e/packages/runtime-core/src/errorHandling.ts#L8... | 2023-06-06T10:50:01 | 2023-06-06T10:50:37 | {} | MEMBER |
vuejs | core | 1,578,504,537 | 8,484 | 1020847665 | but
`console.log("change state.obj", state.obj, isReactive(state.obj));`
isReactive function console.log is true | 2023-06-06T11:12:54 | 2023-06-06T11:12:54 | {} | NONE |
vuejs | core | 1,579,295,422 | 8,482 | justin-schroeder | Pretty sure this is a duplicate of #8468 | 2023-06-06T18:59:38 | 2023-06-06T18:59:38 | {
"+1": 1
} | NONE |
vuejs | core | 1,564,625,185 | 8,419 | yyx990803 | Declaring the emits only removes it from `attrs`. Non-declared events can still be triggered. This is expected behavior. | 2023-05-26T16:16:23 | 2023-05-26T16:16:23 | {} | MEMBER |
vuejs | core | 1,564,639,006 | 8,399 | yyx990803 | With all due respect, here's exactly what I suggest: if you are using Composition API, then follow the recommended best practice. My opinion is that the concept of "inheritance" is inherently incompatible with the Composition mindset. If you want to **reuse** logic in Composition API, reuse them as composables. One pat... | 2023-05-26T16:28:06 | 2023-05-26T16:28:06 | {} | MEMBER |
vuejs | core | 1,570,113,511 | 8,462 | Justineo | Duplicate of #6553 | 2023-05-31T12:16:57 | 2023-05-31T12:16:57 | {} | MEMBER |
vuejs | core | 1,578,175,609 | 8,492 | baiwusanyu-c | duplicate question https://github.com/vuejs/core/issues/6347 | 2023-06-06T08:28:18 | 2023-06-06T08:28:18 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,578,490,345 | 8,479 | LinusBorg | `Nested` is a functional component. as such, its contained elements will *not* receive the scoped styling from its parent, except for the root element. In that regard, functional components work just like normal components: only the (single) root element will inherit scoped styles from the parent. | 2023-06-06T11:07:06 | 2023-06-06T11:07:06 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,568,253,310 | 8,454 | oswaldofreitas | nevermind, it was my bad | 2023-05-30T11:17:55 | 2023-05-30T11:17:55 | {} | NONE |
vuejs | core | 1,569,577,011 | 7,268 | TNGD-YQ | For whom may concern, the issue patched in v3.3.4
see https://github.com/vuejs/core/commit/91f1c62e6384a8b09f90e7e43b8d347901e529a0 | 2023-05-31T06:35:15 | 2023-05-31T06:35:15 | {
"hooray": 1
} | NONE |
vuejs | core | 1,570,631,765 | 8,459 | yyx990803 | This is expected behavior in Vue 3 (which is intentionally different from Vue 2). `v-if` branches **always remounts** because they are considered branches with different keys at the root. Keys on nested elements won't affect the behavior. | 2023-05-31T17:30:42 | 2023-05-31T17:30:42 | {} | MEMBER |
vuejs | core | 1,571,186,015 | 8,468 | edison1105 | <s>should be
```ts
// props.ts
type Text = { text: string }
type Number = { number: number }
```
</s>
sorry, I misread. | 2023-06-01T01:23:14 | 2023-06-01T02:07:54 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,576,034,672 | 8,301 | lmiller1990 | I don't think we've tried vue-jest with Vue 3.3 yet. We should add some tests in that code base and see if there's any bugs or issues.
It sounds like this isn't an issue in Vue core, though - perhaps we should move the issue to vue-jest? | 2023-06-05T04:46:28 | 2023-06-05T04:46:28 | {} | MEMBER |
vuejs | core | 1,566,583,260 | 8,416 | haoqunjiang | Unfortunately, this is a public export. Therefore renaming it is a breaking change.
It's already causing ecosystem-ci failures: https://github.com/vuejs/ecosystem-ci/actions/runs/5108624282
IMO, the best we can do in the current major version is to deprecate it. | 2023-05-29T05:44:42 | 2023-05-29T08:22:40 | {} | MEMBER |
vuejs | core | 1,574,869,986 | 8,479 | shaileshnighojkar | @davidleger95 According to me it is working fine.
To check this I have simplified your example
Link: [Simplified Version](https://play.vuejs.org/#eNp9kM9ugzAMxl/FyoUiFXLoTrRF3QvsCXJpiTvYyB8lgW2qePc5gU6ok3oIxP7s3+f4xl6tLccBWcUOvnGdDbXQ0ClrXIAbtDDB1RkFGdVkQpMGjdE+wBv6gBKOsMnhWEO7yWQ3Ztt4sfTLdNKzPN/PXfidkBKv56EndMyBQ... | 2023-06-03T11:16:30 | 2023-06-03T11:16:30 | {
"+1": 1
} | NONE |
vuejs | core | 1,566,120,808 | 8,444 | NikhilVerma | From what I can see this happens because we use
```js
hostInsert(fragmentStartAnchor, container, anchor)
hostInsert(fragmentEndAnchor, container, anchor)
```
I see why we need those anchors and I am unable to think of a better solution at the moment. My current "fix" is like so:
```vue
<template>
<div v-... | 2023-05-28T12:26:26 | 2023-05-29T03:50:52 | {} | NONE |
vuejs | core | 1,567,171,678 | 8,364 | tragid | @yyx990803 Hi, when is it planned to make 3.3.5 release with this bug fix? | 2023-05-29T13:57:38 | 2023-05-29T13:57:38 | {} | NONE |
vuejs | core | 1,567,484,788 | 8,450 | Killea | You could try to find the $parent and then call the method in the parent. You also could use provide/inject to pass the value if it's a deeply nested component. | 2023-05-29T20:17:52 | 2023-05-29T20:18:44 | {} | NONE |
vuejs | core | 1,568,032,820 | 7,942 | baiwusanyu-c | ~Using uid as ceStyleId will cause duplication of style tags when components are reused~ | 2023-05-30T08:52:22 | 2023-05-31T02:46:57 | {} | MEMBER |
vuejs | core | 1,571,191,347 | 8,468 | justin-schroeder | 🤔 no, that's not the intended props. I did in fact mean the discriminated union that was provided. | 2023-06-01T01:30:36 | 2023-06-01T01:30:36 | {} | NONE |
vuejs | core | 1,578,925,934 | 8,501 | LinusBorg | I think my previous reply is pretty much in sync with your understanding | 2023-06-06T14:57:13 | 2023-06-06T14:57:13 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,575,442,091 | 6,978 | misutime | Months have passed, but there has been no progress.
The same issue still persists. I don't understand why such an obvious issue has not been fixed yet. | 2023-06-04T07:24:15 | 2023-06-04T07:24:15 | {
"+1": 1
} | NONE |
vuejs | core | 1,576,670,006 | 8,373 | sadovsf | To be more specific. ReturnType works for typing but resulting type is missing exposed functions | 2023-06-05T12:10:02 | 2023-06-05T12:10:02 | {} | NONE |
vuejs | core | 1,579,663,687 | 8,482 | edison1105 | @justin-schroeder They're not exactly the same. | 2023-06-07T00:47:31 | 2023-06-07T00:47:31 | {} | MEMBER |
vuejs | core | 1,566,128,457 | 5,165 | INSIinc | still getting this error on ^3.3.4 | 2023-05-28T12:50:28 | 2023-05-28T12:50:28 | {} | NONE |
vuejs | core | 1,566,780,475 | 8,450 | Alfred-Skyblue | Normally, after the instance of the component is destroyed, it should be garbage collected, so the emit event cannot be monitored, but if you manually destroy the map instance, you can choose not to destroy it, and you can use EventBus to trigger, it It is unreasonable behavior to listen to events and let destroyed com... | 2023-05-29T08:51:36 | 2023-05-29T08:51:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,570,108,340 | 7,502 | ThornWalli | @baiwusanyu-c Thanks to the PR 🙂
Now this PR is almost half a year old, not really feel like waiting until this reaches its first year of life 😉
Seems to be only minimal changes and slowly the excitement rises.
Could you also alternatively use a workaround here for now without this PR?
Is that possible? | 2023-05-31T12:15:12 | 2023-05-31T12:15:12 | {} | NONE |
vuejs | core | 1,571,149,840 | 7,268 | godxiaoji | Can this change be merged into version 3.2.x. The current version and accompanying tools (such as vite) no longer support Windows 7 (Node <13). Not very friendly to developers who cannot upgrade their systems (such as work computers). | 2023-06-01T00:47:13 | 2023-06-01T00:47:13 | {} | CONTRIBUTOR |
vuejs | core | 1,571,195,816 | 8,459 | Alfred-Skyblue | Vue tries to reuse nodes with the same key and tag under the same parent element as much as possible. However, since the template is not a real node, your v-if and v-else are under the same parent element. You can use different keys to render them or use different parent elements to render them.
```vue
<template ... | 2023-06-01T01:37:23 | 2023-06-01T01:37:23 | {} | MEMBER |
vuejs | core | 1,572,528,781 | 4,662 | lucasantunes-ciandt | > > > > Since this problem has caused me some troubles, and I don’t know when the official vue will fix it, as a temporary solution, I made my PR into a vite plugin and injected the code through compilation to temporarily solve this problem problem, but for more complex scenarios still need testing, if you happen to ne... | 2023-06-01T17:52:32 | 2023-06-01T17:54:27 | {} | NONE |
vuejs | core | 1,576,259,030 | 8,491 | LinusBorg | `reactive()` does not manipulate the original data inot a proxy. | 2023-06-05T07:50:45 | 2023-06-05T07:50:55 | {} | MEMBER |
vuejs | core | 1,576,531,298 | 8,501 | LinusBorg | In my understanding values being stored "as-is" means they are left untouched.
So when you set as a value on the map with a reactive proxy, that would stay a reactive proxy - and that reactive proxy *would* unwrap nested refs. just like it does for `foo1`, which *is* stored as the reactive proxy in the map.
The ... | 2023-06-05T10:24:22 | 2023-06-05T10:27:23 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,579,138,153 | 4,309 | alexlyul | Hello! Any news on this PR? | 2023-06-06T17:00:06 | 2023-06-06T17:00:06 | {} | NONE |
vuejs | core | 1,564,628,246 | 8,441 | yyx990803 | You should **not** be manipulating the DOM structure that is controlled by Vue. Errors are expected if you do that. | 2023-05-26T16:18:46 | 2023-05-26T16:18:46 | {} | MEMBER |
vuejs | core | 1,567,332,158 | 8,412 | szulcus | I have the same problem, when I use `HTMLInputElement` / `InputHTMLAttributes`:
```ts
import { InputHTMLAttributes } from 'vue';
interface Props extends Pick<Partial<InputHTMLAttributes>, 'min' | 'max'> {
value: number;
}
```
Workaround with `/* vue-ignore */` comment works for me:
```ts
import { InputHTMLA... | 2023-05-29T16:33:47 | 2023-05-29T16:33:47 | {
"+1": 5
} | NONE |
vuejs | core | 1,567,986,834 | 8,140 | simonbuerger | > I get this error (only during build) when importing a type with relative path eg:
>
> ```
> '../types/myfile' ❌
> ```
>
> when I use project root import, it resolves without errors
>
> ```
> '@/types/myfile' ✅
> ```
>
> I should note that this error arises when I import a file to use in `defineProps<M... | 2023-05-30T08:22:50 | 2023-05-30T08:22:50 | {} | NONE |
vuejs | core | 1,577,843,668 | 8,444 | yyx990803 | This is necessary for Vue to manage the fragments. "Fixing" this would require a massive refactor, and to be honest I do not believe it can be justified by "breaking XPath selectors". This sounds **very** specific to the way the test is written. You can assert text by getting `.textContent` of the parent element instea... | 2023-06-06T03:28:45 | 2023-06-06T03:28:45 | {
"-1": 3
} | MEMBER |
vuejs | core | 1,660,404,184 | 5,007 | codethief | @LinusBorg No, this is indeed not a bug, as you say. But what @olemarius posted was a feature request, so this seems very much in line with what you're saying? :)
(I agree with your assessment of the race condition risk, though. In my case, I have a single top-level "layout" component which interacts with the outsid... | 2023-08-01T14:05:42 | 2023-08-01T14:07:44 | {} | NONE |
vuejs | core | 1,661,418,956 | 8,880 | Shyam-Chen | The usage of `slot` in Web Components is as follows `slot="label"`. | 2023-08-02T03:04:30 | 2023-08-02T03:07:30 | {} | CONTRIBUTOR |
vuejs | core | 1,661,436,289 | 8,880 | GuoJikun | > > > > > > The usage of `slot` in Web Components is as follows `slot="label"`.
> > > > >
> > > > >
> > > > > > 用法错了，在 web component 中只能使用 `slot="label"` 这种形式。 这是文档 https://cn.vuejs.org/guide/extras/web-components.html#building-custom-elements-with-vue
> > > > >
> > > > >
> > > > > <img alt="image" width="519... | 2023-08-02T03:30:29 | 2023-08-02T03:30:29 | {} | NONE |
vuejs | core | 1,665,972,294 | 4,710 | tsol | Nope. No reply. I need "dev" to fail when typescript errors because of a collegue who needs to be forced to learn typescript! | 2023-08-04T17:45:09 | 2023-08-04T17:45:09 | {} | NONE |
vuejs | core | 1,666,541,526 | 8,781 | zh-lx | >
I have known this standard, but in most browsers, it can be rendered normally when set `24px` with unit. So my main point is that when user give an invalid value, vue should keep the invalid value and let browser to handle the invalid value, rather than rewrite it to `0` in vue. | 2023-08-05T16:01:43 | 2023-08-05T16:01:43 | {} | CONTRIBUTOR |
vuejs | core | 1,666,544,797 | 8,904 | TheDutchCoder | `price` is already reactive, you probably shouldn't make them refs. Specifically this part seems relevant (https://vuejs.org/guide/essentials/reactivity-fundamentals.html#reactive-proxy-vs-original-1):
> This rule applies to nested objects as well. Due to deep reactivity, nested objects inside a reactive object are ... | 2023-08-05T16:17:13 | 2023-08-05T16:17:13 | {} | NONE |
vuejs | core | 1,670,971,735 | 6,347 | pkrzyszko | Please, fix it as soon as possible.
It causes a huge memory leak in my application. | 2023-08-09T09:20:17 | 2023-08-09T09:20:17 | {} | NONE |
vuejs | core | 1,671,409,881 | 8,929 | doutatsu | Watching this 🙏🏻 Thanks for opening a PR so quickly! Hopefully it gets approved soon | 2023-08-09T14:11:54 | 2023-08-09T14:11:54 | {} | NONE |
vuejs | core | 1,662,403,144 | 8,903 | LinusBorg | It's not mentoned in the `Transition` docs because it's part of `TranstitionGroup` (which you are using), particularly to provide an class to attach `move` styles to. like other transition classes, the default name starts with `v-` , unless you give your transition a specfic `name`.
https://vuejs.org/guide/built-in... | 2023-08-02T15:18:03 | 2023-08-02T15:18:03 | {} | MEMBER |
vuejs | core | 1,668,349,578 | 8,857 | Eternal-Rise | I believe, it will be fixed with https://github.com/vuejs/core/pull/8748 | 2023-08-07T17:58:50 | 2023-08-07T17:58:50 | {} | NONE |
vuejs | core | 1,670,952,874 | 8,940 | gucovip | > According to [the spec](https://262.ecma-international.org/14.0/#prod-IdentifierName), the accurate regexp for identifiers (disregarding unicode escape sequences) should be
>
> ```ts
> /^[$_\p{IDS}][$\p{IDC}\u200c\u200d]*/u
> ```
>
> But this may have browser compatibility issues so we may need a simplified v... | 2023-08-09T09:07:21 | 2023-08-09T09:07:21 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,671,157,607 | 1,228 | AnnaMadsenKnowit | These enums also result in an issue with the `verbatimModuleSyntax` compiler option.
Error message with `yarn build`:
```
node_modules/@vue/reactivity/dist/reactivity.d.ts:295:15 - error TS2748: Cannot access ambient const enums when 'verbatimModuleSyntax' is enabled.
295 readonly [ReactiveFlags.IS_READONL... | 2023-08-09T11:33:20 | 2023-08-09T11:33:20 | {} | NONE |
vuejs | core | 1,657,926,459 | 8,871 | edison1105 | This is not what Vue should do.
It's 2023, and developers should always include `<!DOCTYPE html>` declaration to ensure the document parses according to the specification. | 2023-07-31T08:40:47 | 2023-07-31T08:40:47 | {} | MEMBER |
vuejs | core | 1,658,476,450 | 6,463 | Rigo-m | > On 3.3, this can be resolved by using a nested `<Suspense suspensible>`:
>
> https://play.vuejs.org/#eNp9VLFu2zAQ/ZUDl8iALaZIuyiyESNLgS4FUqALF8U612wlkiApuUGgfw9FihZtJxkE8e7x3r17pPRKtkrlfYekIKXFVjWVxQ0TAGXN+w0AjGsXPXVGoTAB85kRj8EUfsemkSU9Rzz6A1FtG97P9ScoMoMJC/7cIPQrvl8zws3TQR4FI2dlzPrCx1YB3UwCE0J6pTUC1ypSsReFESpp4k... | 2023-07-31T14:25:23 | 2023-07-31T14:25:23 | {} | NONE |
vuejs | core | 1,661,537,766 | 8,880 | felbry | > ```diff
> - <slot v-if="isRenderSlot" name="label"></slot>
> - <template v-else>我是默认label</template>
> + <span v-if="isRenderSlot"><slot name="label"></slot></span>
> + <span v-else>我是默认label</span>
> ```
>
> The usage of `slot` in Web Components is as follows:
>
> ```
> <span v-if="isRenderSlot"><slot na... | 2023-08-02T05:54:57 | 2023-08-02T05:54:57 | {} | NONE |
vuejs | core | 1,665,077,969 | 8,804 | rocifier | Hmm the problem is that native javascript doesn't support this either. Outside of linting what would you expect that using one of the suggested implementations would actually do? Also your second point is essentially a use-case of linting/parsing. For example when would type validation be done? | 2023-08-04T06:25:49 | 2023-08-04T06:28:41 | {} | NONE |
vuejs | core | 1,666,774,714 | 8,916 | steffanhalv | Sorry my mistake, I got it to work.
Here is a working example using options API:
https://play.vuejs.org/#eNqNU01v2zAM/SuaLm6Bxjp0JyMbsg09bBi2Ydtt3sG1mESJRAkSnQQI8t8ryXHiph8oYMAiH/nER4p7/sm5ctMBr/iUwDjdEHyskbHpF2ucRUAS0Z6KERjN0HrlKJ5VDPLETsFs7q1hRSmSJxEXNcIux0iYN50mtk/07ZAQKrYfpR9uEmqAllYmKFmMabtQeHU9mIw1GjxdFd+Tn22... | 2023-08-06T08:34:58 | 2023-08-06T08:35:11 | {} | NONE |
vuejs | core | 1,668,800,200 | 8,908 | baiwusanyu-c | I don't think this is a bug. Maybe you need to provide more information. In the repo you provided, when the data is not returned, accessing a non-existing attribute results in an error. I don't think it's Vue's problem that wrong coding causes vue to report errors and warnings 🤔
````
<template>
<div class="pokemo... | 2023-08-08T02:03:43 | 2023-08-08T02:03:43 | {} | MEMBER |
vuejs | core | 1,661,430,382 | 8,880 | felbry | > > > The usage of `slot` in Web Components is as follows `slot="label"`.
> >
> >
> > > 用法错了，在 web component 中只能使用 `slot="label"` 这种形式。 这是文档 https://cn.vuejs.org/guide/extras/web-components.html#building-custom-elements-with-vue
> >
> >
> > <img alt="image" width="519" src="https://user-images.githubuserconte... | 2023-08-02T03:22:19 | 2023-08-02T03:22:19 | {} | NONE |
vuejs | core | 1,661,440,340 | 8,880 | GuoJikun | 兄弟，在组件内部有什么好的方式在宿主元素( host)上 添加属性和方法吗？
例如：在 `form-item.ce.vue` 中对 `wc-form-item` 添加一个方法 | 2023-08-02T03:37:59 | 2023-08-02T03:37:59 | {} | NONE |
vuejs | core | 1,666,457,579 | 8,914 | mhxy13867806343 | 好的 | 2023-08-05T09:51:00 | 2023-08-05T09:51:00 | {} | NONE |
vuejs | core | 1,666,468,530 | 8,915 | remiconnesson | Hey in this reply https://github.com/tailwindlabs/tailwindcss/issues/11024#issuecomment-1513283412 there's a link to repro that doesn't use tailwindcss at all.
Link:
https://play.vuejs.org/#eNqtU8FSwjAQ/ZVMTjgD5cCtVmfU4aAHddRjLrVZIZAmmWQDOAz/bhIoLYo4znDb7tv39u1ru6Y3xmQLDzSnBUJtZIlwzRQhBReLVGxLUsnSuStGl7Y0BiyjO/AbXE... | 2023-08-05T10:42:43 | 2023-08-05T10:43:39 | {
"+1": 1
} | NONE |
vuejs | core | 1,668,801,096 | 8,908 | baiwusanyu-c | If there are deep-level object properties in the template, the properties should be initialized in data | 2023-08-08T02:05:06 | 2023-08-08T02:05:06 | {} | MEMBER |
vuejs | core | 1,669,868,156 | 8,917 | sxzz | Yes, sorry! The correct issue is #6891. | 2023-08-08T15:46:32 | 2023-08-08T15:46:32 | {} | MEMBER |
vuejs | core | 1,670,852,107 | 8,066 | posva | Related to https://github.com/vuejs/core/issues/4516 | 2023-08-09T07:57:41 | 2023-08-09T07:57:41 | {} | MEMBER |
vuejs | core | 1,662,191,364 | 8,682 | VytenisSidabras | Faced this issue when updating an existing project to a Typescript setup so can add a few additional details:
- This error is not related to `v-for` as you get it without using them.
- `TransitionProps` does not inherit `key` prop, so it throws TS error that for the moment can be ignored with `@vue-ignore`
- Transit... | 2023-08-02T13:13:35 | 2023-08-02T13:13:35 | {} | NONE |
vuejs | core | 1,663,619,891 | 7,708 | qian-kong | > > `include="A,B"` A and B should be string, You're passing objects. see [playground](https://sfc.vuejs.org/#eNq1U01r20AQ/SvDXtSCrYW2UBBKsaRjbyW3bg+ONJHVrHaX3ZHTYvzfMysljmSHkEMCNmjnvZk3nwdROJfuBxSZyEPtO0cQkAb3QxlFXe+sJyjg1tselEhlEblKzMDyGSwvwOoZrC7AA4TdVmt7/wtv4TgxEyYlygBoJKht7+BqxvqUFMlnZXI5ZRpzNDlh7/SWkF8A+U9EV+huj5... | 2023-08-03T09:27:04 | 2023-08-03T09:27:04 | {} | NONE |
vuejs | core | 1,669,669,971 | 8,917 | sxzz | Closing this due to duplicated of #6891 | 2023-08-08T13:55:35 | 2023-08-08T15:46:43 | {} | MEMBER |
vuejs | core | 1,641,783,100 | 8,811 | Justineo | ~~It seems that `FooBar` is converted to `-foo-bar`.~~
https://github.com/vuejs/core/blob/a3dddd62059f4a7a762046c1e7f01485b96e737d/packages/shared/src/general.ts#L110-L112 | 2023-07-19T09:54:14 | 2023-07-31T12:04:00 | {} | MEMBER |
vuejs | core | 1,659,453,185 | 8,830 | felbry | 哎 快点合并吧 这个问题严重阻塞开发进度了 | 2023-08-01T02:03:49 | 2023-08-01T02:03:49 | {} | NONE |
vuejs | core | 1,659,897,142 | 5,007 | u12206050 | Came across the same issue today. Was wondering why v-bind styles weren't applied globally. In my case I have theme colors that change on a page component, and that I want modals and popups to respect, however since they are rendered outside of the page component even though I use `:global` the theme variables apply bu... | 2023-08-01T09:08:34 | 2023-08-01T09:08:34 | {} | NONE |
vuejs | core | 1,661,421,536 | 8,880 | GuoJikun | 用法错了，在 web component 中只能使用 `slot="label"` 这种形式。
这是文档 https://cn.vuejs.org/guide/extras/web-components.html#building-custom-elements-with-vue | 2023-08-02T03:08:34 | 2023-08-02T03:10:05 | {} | NONE |
vuejs | core | 1,661,450,819 | 8,880 | GuoJikun |
> `getCurrentInstance()`可以获取当前组件的实例，它有一个`ctx`上下文属性，`ctx`有`$el`属性直接指向了template模板的根元素，如果template有多个一级节点，`$el`指向的是个text。有个这个元素就可以通过`getCurrentInstance().ctx.$el..parentNode.host`访问host对象了
>
> 感觉好多不方便的点 最近开始调研lit了 至少目前看比vue开发体验舒服点
确实很不方便；
`defineExpose` 的 pr 都半年了还没合并(使用 `defineExpose` 的导出的可以直接在 `host` 上使用 )还没合并；
... | 2023-08-02T03:54:31 | 2023-08-02T03:56:35 | {} | NONE |
vuejs | core | 1,664,822,586 | 8,908 | edison1105 | Please provide a runnable reproduction | 2023-08-04T00:52:12 | 2023-08-04T00:52:12 | {} | MEMBER |
vuejs | core | 1,666,538,352 | 8,781 | TheDutchCoder | Setting `24px` as an attribute is not valid HTML: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/img
> The intrinsic height of the image, in pixels. Must be an integer without a unit
So I think if anything, it should be parsed as an integer, not blindly propagated with invalid values? | 2023-08-05T15:46:36 | 2023-08-05T15:49:57 | {} | NONE |
vuejs | core | 1,667,067,970 | 8,904 | TheDutchCoder | @Teiiiiiio I don't think so?
Anyway, I think this is just normal behaviour. I personally never use `reactive`, `ref` is so much easier imo.
https://play.vuejs.org/#eNqtVU1T2zAQ/SuLLnGKkxS4ZZL0g+FApwWGMsMBcXCcdRDYkkcf4SPj/96VhJOUYVLokFOkfat9+/RWXrJvdd1fOGRDNjK5FrUFg9bVUGZyPubMGs4mXIqqVtrCEjRmuRULTDUWqTDn7RJyVdXO4gwa... | 2023-08-07T01:50:44 | 2023-08-07T01:50:44 | {} | NONE |
vuejs | core | 1,667,652,286 | 8,927 | LinusBorg | `<SlottedComponent>` is in the template of `App.vue`. Therefore, it's receiving App's scoped style attribute, just like any normal element in `App.vue` - regardless of wether you put that into another component's slot, or not.
So this is working as designed - the quoted docs apply to this scenario. We may revisit th... | 2023-08-07T11:06:07 | 2023-08-07T11:06:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,660,033,806 | 8,842 | LinusBorg | > Props basically have the type MaybeRef because you can bind either a static value or a ref
This may be a misunderstanding. You cannot pass a ref, props do not have a `MaybeRef` type. The ref will be unwrapped in the parent's render function before passing it to the child component (when using templates). What happ... | 2023-08-01T10:29:49 | 2023-08-08T07:19:20 | {} | MEMBER |
vuejs | core | 1,670,618,069 | 8,939 | dongwa | 
The bug may be caused by the cache of Chinese characters. | 2023-08-09T04:01:55 | 2023-08-09T04:01:55 | {
"+1": 1
} | NONE |
vuejs | core | 1,671,749,503 | 8,801 | posva | 1. I think yes, I don't see why this should be in runtime-dom instead of core
2. I'm not sure but I don't think it matters | 2023-08-09T16:23:31 | 2023-08-09T16:23:31 | {} | MEMBER |
vuejs | core | 1,659,953,489 | 8,388 | dianligegege | > #5846
太震惊了，我之前使用这个“bug”编写组件，可以直接给组件传值jsx函数，非常方便 | 2023-08-01T09:41:34 | 2023-08-01T09:41:34 | {} | NONE |
vuejs | core | 1,664,484,805 | 6,018 | SinBirb | This isn't really an edge-case. There should be a warning somewhere in the docs, that you should not use `watch` with `flush: sync`, or `computedEager` for large arrays.
And that `splice()`, `shift()`, etc. are not atomic operations with Vue.
The JSBench example here is 10 million *times* slower with Proxy, on m... | 2023-08-03T19:03:21 | 2023-08-03T19:05:33 | {} | NONE |
vuejs | core | 1,665,494,448 | 8,908 | Ceagah2 |
Sorry.
You can run this project, and just open the console.
https://github.com/Ceagah2/vuejs-playground/tree/main/cli
| 2023-08-04T11:57:58 | 2023-08-04T11:57:58 | {} | NONE |
vuejs | core | 1,665,656,807 | 8,303 | stafyniaksacha | > I catch it.
>
> In any vue 3.3.2 project. Add file
>
> ```ts
> // file: run-vite.mts
> import * as vite from 'vite'
>
> const root = process.cwd()
>
> async function main() {
> const viteDevServer = await vite.createServer({
> root,
> logLevel: 'info',
> server: {
> ... | 2023-08-04T13:59:50 | 2023-08-04T13:59:50 | {} | NONE |
vuejs | core | 1,666,125,665 | 4,400 | theoephraim | @m0dch3n @LinusBorg - I just ran into this as well. Was definitely unexpected.
Seems worth reopening for this specific case of function calls? | 2023-08-04T20:15:06 | 2023-08-04T20:15:06 | {} | NONE |
vuejs | core | 1,668,263,289 | 8,857 | censujiang | same question | 2023-08-07T17:00:34 | 2023-08-07T17:00:34 | {} | NONE |
vuejs | core | 1,669,662,602 | 8,917 | sxzz | Try to add `skipLibCheck` option in `tsconfig.json` | 2023-08-08T13:51:30 | 2023-08-08T13:51:30 | {} | MEMBER |
vuejs | core | 1,658,097,352 | 6,483 | reitowo | Guys, any update on this?
@yyx990803 It seems multiple same issues happens nowadays, and it is not a rare case, can you reevaluate this issue? | 2023-07-31T10:28:05 | 2023-07-31T14:41:49 | {
"eyes": 1
} | NONE |
vuejs | core | 1,659,406,151 | 8,871 | toyknight | If it is not omitted then the inspector will tell you it is an invalid value, so you know what's wrong. If it is omitted then people will likely wonder that something else goes wrong (I didn't see this omitting behavior mentioned in the doc?).
Guess I will just close this as WAI for future reference then. | 2023-08-01T00:55:00 | 2023-08-01T00:55:00 | {} | NONE |
vuejs | core | 1,660,537,270 | 5,952 | joseehilton147 | 1 year and 3 months and counting, what's is stopping this from being merged? | 2023-08-01T15:17:08 | 2023-08-01T15:17:08 | {
"+1": 11
} | NONE |
vuejs | core | 1,661,385,364 | 8,836 | Justineo | 导入 Vue 组件请用 https://github.com/antfu/unplugin-vue-components | 2023-08-02T02:15:58 | 2023-08-02T02:15:58 | {} | MEMBER |
vuejs | core | 1,670,609,861 | 8,937 | F1462900874 | 
| 2023-08-09T03:47:49 | 2023-08-09T03:47:49 | {} | NONE |
vuejs | core | 1,671,738,566 | 8,801 | Mini-ghost | Thank you for your feedback. I have a couple of questions I would like to confirm:
1. In #4619, the implementation of adding `app.onUnmount` functionality is located in `runtime-core/src/apiCreateApp.ts` instead of `runtime-dom/src/index.ts`. I'm not sure if this PR should follow this approach.
2. Currently, Vue ... | 2023-08-09T16:16:42 | 2023-08-09T16:16:42 | {} | CONTRIBUTOR |
vuejs | core | 1,659,970,750 | 5,007 | LinusBorg | This is not a bug.
> The actual value will be compiled into a hashed CSS custom property, so the CSS is still static. **The custom property will be applied to the component's root element via inline styles** and reactively updated if the source value changes.
https://vuejs.org/api/sfc-css-features.html#v-bind-in-... | 2023-08-01T09:52:10 | 2023-08-01T09:52:39 | {} | MEMBER |
vuejs | core | 1,659,975,440 | 8,877 | LinusBorg | When a reactive Effect triggers a re-render, the *the whole template* is updated with *all current data* - wether or not that data itself is reactive, doesn't matter.
So yes, this is intentional, it's how updates in virtualDOM-based view libraries, such as Vue and React, work. | 2023-08-01T09:55:08 | 2023-08-01T09:55:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,660,008,504 | 8,794 | AndreiSoroka | > const readOnlyMessage = msg.value;
@Shyam-Chen my purpose is to make both reactive and readonly property
For example:
```ts
// not working, but expected
defineProperties<{
message: string,
}>()
// working, but overhead for each property
defineProperties<{
message: Readonly<string>,
}>()
``` | 2023-08-01T10:14:54 | 2023-08-01T10:14:54 | {} | NONE |
vuejs | core | 1,655,460,775 | 8,865 | LinusBorg | Id argue that you are then no longer emitting an event, really. Emitting an event means the child is not concerned with what happens with the emitted value.
If your component does depends on the return value, defining that as a prop is fine and the way to go. | 2023-07-28T10:33:54 | 2023-08-01T12:38:07 | {} | MEMBER |
vuejs | core | 1,662,878,315 | 906 | MaxiBorrajo | In my case, as it happened to others, removing the comments fixes the problems with the out-in mode. | 2023-08-02T19:47:57 | 2023-08-02T19:47:57 | {} | NONE |
vuejs | core | 1,669,883,975 | 8,842 | pleek91 | @LinusBorg thanks for the detailed response. That totally makes sense. I guess I'm suggesting that when the template is converted into a render function to use `toValue` rather than `unwref`. But you're right that would break things.
I was thinking about this from a pure types perspective where currently if you're ... | 2023-08-08T15:56:46 | 2023-08-08T15:56:46 | {} | NONE |
vuejs | core | 1,657,858,090 | 7,301 | dwin0 | @zhangzhonghe Thanks for providing a fix for this problem. Do you know when it will be merged? | 2023-07-31T07:53:51 | 2023-07-31T07:53:51 | {} | NONE |
vuejs | core | 1,658,512,119 | 6,491 | reitowo | Thanks for the PR, any updates on this? | 2023-07-31T14:43:13 | 2023-07-31T14:43:13 | {} | NONE |
vuejs | core | 1,659,041,088 | 3,378 | rockisch | Sorry for a bit of necro, but I feel like both reasons cited for the closing of this ticket (and the previous one as well) don't make a lot of sense.
1. **The empty string is what the browser provides**: This was also cited in the previous ticket, but that has nothing to do with the requested feature. The browser al... | 2023-07-31T19:52:53 | 2023-07-31T19:52:53 | {
"+1": 1
} | NONE |
vuejs | core | 1,667,253,035 | 6,540 | hdy1023 | > > your `defineExpose`call in Comp.vue is incorrect. `defineExpose()`expects an object, not a ref.
> > Consequently your accessing in the parent was also wrong.
> > https://sfc.vuejs.org/#eNqFk01PwzAMhv+KlcuGtDUqiMvUDSHElQPnXPaRsU7Nh5J0IFX979hp1rWDwa1x7Nd+n7gNe7Y2O9WSLVjht660AbwMtV0JXSprXIAGnNxDC3tnFEwwddJfvRhlUzzjd... | 2023-08-07T06:20:09 | 2023-08-07T06:20:09 | {
"-1": 1
} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.