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,641,474,323 | 8,788 | Shyam-Chen | ```vue
<script lang="ts" setup>
import { ref } from 'vue';
const regularRef = ref();
const vFunc = { // v-func
mounted(el) {
// ...
}.
};
</script>
<template>
<h3 ref="regularRef" v-func>My title</h3>
</template
``` | 2023-07-19T06:10:05 | 2023-07-19T06:10:05 | {} | CONTRIBUTOR |
vuejs | core | 1,641,889,731 | 7,215 | fungaren | Hi, is this bug fixed now? | 2023-07-19T11:12:41 | 2023-07-19T11:12:41 | {} | NONE |
vuejs | core | 1,643,028,649 | 6,974 | edison1105 | > why closed this pr
Maybe it is too late to perform animation in the hydration phase. This is what you'll see
- element appearance -> page loaded
- element disappearance -> hydration start
- element reappearance
The correct way to do this is to perform the animation before the hydration. But vue doesn't have ... | 2023-07-20T02:53:23 | 2023-07-20T02:53:23 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,635,166,320 | 8,780 | zh-lx | > should be `width="200"` without `px`. see https://developer.mozilla.org/en-US/docs/Web/API/HTMLImageElement/width
I know this point, but why not preserve the attribute written by the user, instead, rewrite it to 0? Mdn did not say that when a value has units, it needs to be rewritten to `0`.
In standard html, ... | 2023-07-14T02:14:11 | 2023-07-14T02:43:43 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,639,532,622 | 8,790 | Mario34 | > It similer to #5363 Note: without `svg` it also has a memory leak
In fact, in my project, the Dom node can be reclaimed after the svg component is removed, so I have provided a reproduced example based on the fact. The issue mentioned in #5363 has been fixed, it should not be the same as the issue I described. | 2023-07-18T05:55:20 | 2023-07-18T05:55:20 | {
"+1": 1
} | NONE |
vuejs | core | 1,641,958,137 | 8,812 | edison1105 | duplicate of https://github.com/vuejs/core/issues/8612
see https://github.com/vuejs/core/issues/8612#issuecomment-1600030885 | 2023-07-19T12:02:30 | 2023-07-19T12:02:30 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,642,969,596 | 8,811 | so1ve | @Justineo I think `-foo-bar` is ok? | 2023-07-20T01:25:35 | 2023-07-20T01:25:35 | {} | MEMBER |
vuejs | core | 1,635,475,330 | 8,086 | matrosov2019 | @blur="triggerEventChange()" | 2023-07-14T08:12:20 | 2023-07-14T08:12:20 | {} | NONE |
vuejs | core | 1,636,604,747 | 8,086 | johnwc | > @blur="triggerEventChange()"
Change and blur event are not the same. | 2023-07-15T01:09:12 | 2023-07-15T01:09:12 | {
"+1": 1
} | NONE |
vuejs | core | 1,637,874,997 | 8,780 | zh-lx | > > For example, sometimes users may add an attribute to the dom that is not in the HTML specification and unify the dom with that attribute.
>
> That’s not the case here. Vue only sets bindings as properties if they exist on the element. Unknown attributes are always set as-is.
Yes, I just made an analogy of thi... | 2023-07-17T10:49:17 | 2023-07-17T10:49:43 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 1,639,831,934 | 5,198 | vercel[bot] | @edison1105 is attempting to deploy a commit to the **vuejs** Team on [Vercel](https://vercel.com).
A member of the Team first needs to [authorize it](https://vercel.com/git/authorize?team=vuejs&type=github&job=%7B%22headInfo%22%3A%7B%22sha%22%3A%22e6bcdb408d77d1a3b124111f47ae2ba65b90a29c%22%7D%2C%22id%22%3A%22QmVZM8q... | 2023-07-18T09:06:06 | 2023-07-18T09:06:06 | {} | NONE |
vuejs | core | 1,635,264,994 | 8,487 | dodgex | I tried to recreate the repro for a new issue as you suggested but now it seems to work in a blank vue project. No Idea what i did diffrent 2 days ago when testing it.
But what I found is that it somehow relates my `tsconfig.json`. When using my tsconfig in the blank project it fails; with the tsconfig(s) setup gene... | 2023-07-14T04:47:19 | 2023-07-14T04:47:19 | {} | NONE |
vuejs | core | 1,635,359,878 | 8,780 | zh-lx | > As the most used browser doesn't support this usage, I'd say there's no reason for developers to keep this usage in their application code. This should be fixed during development and not to be shipped to production. Maybe we can warn about this usage at dev time.
Firstly, contrary to what you said, most browsers ... | 2023-07-14T06:42:42 | 2023-07-14T06:45:33 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 1,636,235,356 | 6,420 | ivanmem | > As a workaround for now, I'm casting the return type of `toRefs` manually:
>
> ```ts
> const { prop1, prop2 } = toRefs(props) as Required<ReturnType<typeof toRefs<PropInterface>>>;
> ```
In this case, type is lost. | 2023-07-14T18:32:24 | 2023-07-14T18:32:24 | {} | NONE |
vuejs | core | 1,637,625,009 | 8,149 | WhereJuly | > ### Link to minimal reproduction
> https://codepen.io/leaverou/pen/MWPpEQg?editors=1011
> ### What is expected?
> 1 in Result pane
>
> ### Any additional comments?
> Apparently proxies break private class fields ([MDN](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Proxy#n... | 2023-07-17T08:48:14 | 2023-07-17T08:55:41 | {} | NONE |
vuejs | core | 1,639,662,836 | 8,776 | sxzz | I think it's not relate to Vue core | 2023-07-18T07:33:09 | 2023-07-18T07:33:09 | {} | MEMBER |
vuejs | core | 1,642,414,435 | 8,811 | so1ve | That's definitely a bug. In that case, we have to convert `FooBar` to `-foo-bar`, which is not vue's shared hyphenate utility's desired output. We will use a custom hyphenate function in volar side. Fix for this issue will be available at vuejs/language-tools#3424 | 2023-07-19T16:39:58 | 2023-07-19T16:39:58 | {} | MEMBER |
vuejs | core | 1,643,042,931 | 6,974 | baiwusanyu-c | > > why closed this pr
>
> Maybe it is too late to perform animation in the hydration phase. This is what you'll see
>
> * element appearance -> page loaded
> * element disappearance -> hydration start
> * element reappearance
>
> The correct way to do this is to perform the animation before the hydration. B... | 2023-07-20T03:18:13 | 2023-07-20T03:18:13 | {} | MEMBER |
vuejs | core | 1,643,761,099 | 5,036 | cmath10 | Hello, @LinusBorg! Are there any updates? | 2023-07-20T11:33:22 | 2023-07-20T11:33:22 | {} | NONE |
vuejs | core | 1,643,900,531 | 8,817 | yangliguo7 | ```
Vue.createApp({
setup() {
function test(){
params.value.x++;
}
const params = Vue.ref({ x: 1 })
const label = Vue.computed(() => {
const originalArgs =Vue.toRaw(Vue.unref(params))
const storeKey = JSON.stringify(originalArgs)
return storeKey ... | 2023-07-20T13:10:36 | 2023-07-20T13:10:36 | {} | CONTRIBUTOR |
vuejs | core | 1,644,594,821 | 5,657 | volk234 | Same issue in nuxt 3.6.5 and vue 3.3.4.
It happens in production build only. | 2023-07-20T20:56:52 | 2023-07-20T20:56:52 | {
"+1": 8
} | NONE |
vuejs | core | 1,636,503,876 | 7,286 | 719media | Would love to have this PR get traction again! Thanks for making this PR! | 2023-07-14T22:16:05 | 2023-07-14T22:16:05 | {} | NONE |
vuejs | core | 1,637,271,375 | 8,790 | Mario34 | Memory leaks have been bothering us for a long time, and we finally found the cause | 2023-07-17T01:39:21 | 2023-07-17T01:39:21 | {
"+1": 1
} | NONE |
vuejs | core | 1,639,547,812 | 8,149 | WhereJuly | @LeaVerou True, my workaround requires coupling with Vue. For code assumed to work along with Vue it is fine, though for code trying to be Vue-agnostic this is the problem. Could be probably solved by some Vue-aware adapter object nearby the original object to still keep properties private. Though this approach applica... | 2023-07-18T06:05:48 | 2023-07-18T06:06:54 | {} | NONE |
vuejs | core | 1,641,508,085 | 8,788 | klausXR | > ```
> <script lang="ts" setup>
> import { ref } from 'vue';
>
> const regularRef = ref();
>
> const vFunc = { // v-func
> mounted(el) {
> // ...
> }.
> };
> </script>
>
> <template>
> <h3 ref="regularRef" v-func>My title</h3>
> </template
> ```
Thank you for that example. Unfortunately... | 2023-07-19T06:43:29 | 2023-07-19T06:43:29 | {} | NONE |
vuejs | core | 1,641,565,329 | 8,808 | chenweiyi | > ```ts
> 'update:modelValue': (value: string) => typeof value === 'string',
> ```
Yeah, this code solve the warning. But I actualy want to solve another question. I have added a picture to the question, please take a look and help me again. | 2023-07-19T07:30:45 | 2023-07-19T07:30:45 | {} | NONE |
vuejs | core | 1,635,145,475 | 8,522 | edison1105 | @SuleymanQ
this should work:
```typescript
declare const ConfigDefaults: {
colors: ColorDefaults
}
export type ConfigProps = typeof ConfigDefaults
const props = defineProps<Partial<ConfigProps>>()
``` | 2023-07-14T01:49:59 | 2023-07-14T01:49:59 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,635,381,604 | 8,780 | Justineo | > Firstly, contrary to what you said, most browsers support this usage, and in fact, I don't know which browser does not support this usage.
I deleted my comment as I misremembered it from our last discussion about this in #7658. In most cases Vue tries to set properties if they exist. Shall we keep all invalid attr... | 2023-07-14T07:03:28 | 2023-07-14T07:05:21 | {} | MEMBER |
vuejs | core | 1,640,996,557 | 6,229 | naaadz | > The correct solution is: you need to split the files that don't contain scss variables and the files that contain scss variables, and introduce the files that contain scss variables in additionalData, so that they won't be introduced repeatedly and the scss variables can be used in each component.
Where do you put... | 2023-07-18T21:10:19 | 2023-07-18T22:29:00 | {} | NONE |
vuejs | core | 1,641,485,214 | 8,808 | Shyam-Chen | ```ts
'update:modelValue': (value: string) => typeof value === 'string',
``` | 2023-07-19T06:20:21 | 2023-07-19T06:20:21 | {} | CONTRIBUTOR |
vuejs | core | 1,642,408,842 | 8,811 | browsnet | ```vue
<Comp :foo-bar="`hello`"/>
```
is equal to
```vue
<Comp :fooBar="`hello`"/>
```
is not equal to
```vue
<Comp :FooBar="`hello`"/>
```
In the implementation of Vue, the key of props is only determined for equality using `camelize(key)`, so `fooBar` and `FooBar` can coexist and represent two different p... | 2023-07-19T16:35:35 | 2023-07-19T16:35:35 | {} | CONTRIBUTOR |
vuejs | core | 1,643,785,123 | 8,819 | yangliguo7 | ```
/**
* v-for object
*/
export function renderList<T>(
source: T,
renderItem: <K extends keyof T>(
value: T[K],
key: K,
index: number
) => VNodeChild
): VNodeChild[]
```
const testObject: { [k: string]: string } = {
key1: 'value2',
key2: 'value2'
}
type k = keyof typeof tes... | 2023-07-20T11:52:01 | 2023-07-20T11:52:01 | {} | CONTRIBUTOR |
vuejs | core | 1,635,332,369 | 8,779 | epreston | I've submitted option 3 for your review.
This updates the sfc-playground package with the missing `"type": "module"`, explicitly declares the dependency used by the private vite.config.ts, and updates the dependency to match the base package. | 2023-07-14T06:14:15 | 2023-07-14T06:14:15 | {} | NONE |
vuejs | core | 1,641,274,700 | 8,794 | Shyam-Chen | ```diff
- const readOnlyMessage = readonly(msg);
+ const readOnlyMessage = msg.value;
```
```ts
import { toRaw } from 'vue';
structuredClone(toRaw(items));
```
```vue
<script type="ts" setup>
import { reactive, readonly, watchEffect } from 'vue';
const original = reactive({ count: 0 });
const copy =... | 2023-07-19T02:05:30 | 2023-07-19T02:09:36 | {} | CONTRIBUTOR |
vuejs | core | 1,640,681,224 | 8,804 | Andrioden | Related: https://stackoverflow.com/questions/55926550/vue-array-prop-jsdoc-typescript-error-in-vs-code-type-arrayconstructor-is-mis (does not work) | 2023-07-18T17:44:23 | 2023-07-19T10:22:30 | {} | NONE |
vuejs | core | 1,643,489,555 | 8,817 | edison1105 | Please provide a runnable minimal reproduction. | 2023-07-20T08:20:36 | 2023-07-20T08:20:36 | {} | MEMBER |
vuejs | core | 1,640,209,155 | 6,435 | rivatove | **My use case:**
I want to create a JSON-LD script tag with metadata. I want to use data passed to a component as props.
No workaround is available for this AFAIK. | 2023-07-18T13:14:33 | 2023-07-18T13:14:33 | {} | NONE |
vuejs | core | 1,640,542,152 | 8,576 | matthew-dean | At the very least, can there be changes to the Vite / Webpack plugins to fix this behavior for the `defineProps` macro and correctly reflect TypeScript types in the runtime (and in Volar), if the Vue team does not want to create a breaking change?
Something like:
```ts
vue({
script: {
accurateTypes: true
... | 2023-07-18T16:20:34 | 2023-07-18T16:20:34 | {
"+1": 6,
"rocket": 2
} | NONE |
vuejs | core | 1,602,035,017 | 8,105 | kikuchan | https://github.com/vuejs/core/blob/d2c3d8b70b2df6e16f053a7ac58e6b04e7b2078f/packages/runtime-core/src/components/Suspense.ts#L497-L520
The issue happens when `activeBranch` is truthy, and regardless of whether `delayEnter` is true or not.
And, I think the `anchor` re-selection in the `if (activeBranch)` block needs... | 2023-06-22T05:32:11 | 2023-06-22T05:32:11 | {
"eyes": 1
} | NONE |
vuejs | core | 1,606,172,257 | 5,724 | sfreytag | My code with this issue runs fine. I think it might be a tooling problem. JetBrains discusses it here:
https://youtrack.jetbrains.com/issue/WEB-60065/Vue3-dynamic-component-type-mismatch-errors-when-using-component-ref-as-is-prop-value
And Vue language tools for VSCode here:
https://github.com/vuejs/language-t... | 2023-06-25T17:24:59 | 2023-06-25T17:25:12 | {} | NONE |
vuejs | core | 1,608,663,150 | 8,641 | kikuchan | It also fixes https://github.com/nuxt/nuxt/issues/13350 btw | 2023-06-27T02:55:36 | 2023-06-27T02:55:36 | {} | NONE |
vuejs | core | 1,608,954,642 | 8,615 | so1ve | You shouldn't use generics and argument together | 2023-06-27T07:33:27 | 2023-06-27T07:33:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,609,221,225 | 8,654 | auvred | This regex is also used for css var names escaping, but the dash is allowed symbol there. I'm not sure if I properly handled this case. Maybe we should use two different regular expressions: one for type-only props names and another one for css var names? | 2023-06-27T10:23:05 | 2023-06-27T10:23:05 | {} | CONTRIBUTOR |
vuejs | core | 1,614,556,489 | 8,036 | artmakarov | If you make a shallow copy of the array, this will work as a [workaround ](https://play.vuejs.org/#eNqNUk1vGjEQ/SsjX7IodKmUGyFR0yQHemhQ0lvdw2bXgMF4XX9QENr/3vF4d4E2jSok1h7PvHkz7x3YnTH5Ngg2ZhNXWmk8OOGDueVabkxtPdwvpapgbusNcJaP6BorOLuGPukAVsyHUNYbE7yooEkFF5h3cd1nPb2uROmPWOmerxxicQ0IV9baIQNfeAE3PVyWDeDmFg5cc58ytoUKMaNFoIKcg... | 2023-06-30T12:04:29 | 2023-06-30T12:04:29 | {} | NONE |
vuejs | core | 1,602,483,690 | 8,509 | ivanmem | duplicate? [github.com/vuejs/core/issues/5603](https://github.com/vuejs/core/issues/5603) | 2023-06-22T11:35:27 | 2023-06-22T11:35:43 | {} | NONE |
vuejs | core | 1,602,709,302 | 8,617 | nick-korolev | You are absolutely right. It looks like I dived too deep, but I didn't notice the obvious reason | 2023-06-22T14:09:09 | 2023-06-22T14:09:09 | {} | NONE |
vuejs | core | 1,606,507,712 | 5,724 | juzser | @so1ve That's right, volar supports dynamic components type-checking now so I guess it no longer occurs.
But I'm not sure 100%, I've not tested. | 2023-06-26T02:42:42 | 2023-06-26T02:42:42 | {
"heart": 1
} | NONE |
vuejs | core | 1,606,791,293 | 8,640 | baiwusanyu-c | Can you provide more information, I did not reproduce your problem. [see](https://play.vuejs.org/#eNp9Uj2P2zAM/SuEFt8BgTPcFrgF2uKGdmgPbbeqg2Ezqa6yJFBSLoXh/15StpMA9zFJ5HuPeiI5qg8h1MeMaqea2JEJCSKmHMC27vBOqxS1eq+dGYKnBJ/8EGBPfoCq3kog0kq7ZjtrmclBwiHYNiFHAE3RpH8BuVrMXYdRSjZFzoxme6arDT/Xebc3h/oxeseeRimhVcdcY5G+hWS8Y/0OCiJYa6... | 2023-06-26T06:49:27 | 2023-06-26T06:49:27 | {} | MEMBER |
vuejs | core | 1,609,227,393 | 8,658 | slothvips | for the unification of programming style,`getSequence` is a utility function,should be placed under the shared package | 2023-06-27T10:27:43 | 2023-06-27T10:27:43 | {} | NONE |
vuejs | core | 1,610,140,292 | 8,083 | aayler | greetings!
would really appreciate a confirmation:
does this feature support import via `alias` in vite, ie, `@`?
when we use something like `import { PageSlug } from '@/types/audio.interface';` vite generates:
```[commonjs] [@vue/compiler-sfc] Failed to resolve import source "@/types/audio.interface".```
wh... | 2023-06-27T20:04:28 | 2023-06-27T20:04:28 | {
"eyes": 2
} | NONE |
vuejs | core | 1,612,894,789 | 8,676 | LinusBorg | Ah. Thanks for the follow-up, I now see I misunderstood your description. Seems indeed like an adge case worth looking into. | 2023-06-29T11:00:09 | 2023-06-29T11:00:09 | {} | MEMBER |
vuejs | core | 1,602,558,265 | 8,592 | sxzz | @zqran No, if there's any reference not inside of `withDefaults`, then we can just hoist the variable (`const` only). | 2023-06-22T12:33:50 | 2023-06-22T12:33:50 | {} | MEMBER |
vuejs | core | 1,603,734,155 | 8,629 | GiantAxeWhy | This enhancement would involve modifying the compiler's parsing and transformation logic to recognize and handle the <!-- --> comment syntax when encountered within template expressions. The comments would be treated as non-evaluating content, allowing them to coexist with the actual expressions and be ignored during t... | 2023-06-23T06:17:21 | 2023-06-23T06:17:21 | {} | NONE |
vuejs | core | 1,608,952,805 | 8,648 | so1ve | Your data fetching function is throwing an error =.= | 2023-06-27T07:32:03 | 2023-06-27T07:32:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,609,268,216 | 8,523 | Mosharush | I found also easy reproduce with this:
https://codesandbox.io/s/clever-elion-x4lwnh?file=/src/components/AppCard.vue | 2023-06-27T10:56:15 | 2023-06-27T10:56:15 | {} | NONE |
vuejs | core | 1,610,868,760 | 8,618 | wenfangdu | @Shyam-Chen This issue has nothing to do with `pug`, and the optional root `<template>` should be enabled only when the templating language is html. | 2023-06-28T06:52:28 | 2023-06-28T06:52:28 | {} | NONE |
vuejs | core | 1,612,388,627 | 8,105 | kikuchan | I'm trying to explain what's going on under the hood.
For this issue, there are 2 cases:
1. In **this** case, the `activeBranch` is still in the `hiddenContainer` (I don't know if this is a valid state).
Then, `move` tries to move the `pendingBranch` where the `activeBranch` is, and it fails because the `anchor`... | 2023-06-29T03:41:55 | 2023-06-29T03:41:55 | {
"+1": 3,
"eyes": 2
} | NONE |
vuejs | core | 1,603,647,969 | 8,627 | johnsoncodehk | Related to https://github.com/vuejs/repl/pull/107 | 2023-06-23T03:56:50 | 2023-06-23T03:56:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,609,110,135 | 8,646 | abczhangshasha | @liting-yes 好的
当时git打不开就先放这了
| 2023-06-27T09:15:42 | 2023-06-27T09:15:42 | {} | NONE |
vuejs | core | 1,610,752,390 | 8,667 | baiwusanyu-c | cc @sxzz 👀 | 2023-06-28T05:16:06 | 2023-06-28T05:16:06 | {} | MEMBER |
vuejs | core | 1,613,996,242 | 8,668 | Alfred-Skyblue | TBR | 2023-06-30T01:37:58 | 2023-06-30T01:37:58 | {} | MEMBER |
vuejs | core | 1,601,978,347 | 8,569 | sxzz | Could you please try it again with upgrading VScode extension Volar, TS, and Vue to the latest version? If the problem stills, please provide a minimum reproduction. | 2023-06-22T03:59:32 | 2023-06-22T03:59:32 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,434,848,652 | 7,499 | yangwao | Hey, how is this standing? I've heard [nuxt-speedkit](https://github.com/GrabarzUndPartner/nuxt-speedkit/issues/542) would need it and then [kodadot/nft-gallery](https://github.com/kodadot/nft-gallery/) is happy to use it 😁 | 2023-02-17T16:02:03 | 2023-06-24T07:39:26 | {
"+1": 7
} | NONE |
vuejs | core | 1,607,140,015 | 8,643 | baiwusanyu-c | https://github.com/vuejs/core/issues/8465 duplicate question
cc @edison1105 | 2023-06-26T10:07:22 | 2023-06-26T10:07:22 | {
"+1": 1,
"heart": 1
} | MEMBER |
vuejs | core | 1,608,578,359 | 8,640 | Shyam-Chen | Duplicate of #8152 | 2023-06-27T01:43:39 | 2023-06-27T01:44:58 | {} | CONTRIBUTOR |
vuejs | core | 1,608,697,007 | 8,640 | toplyb | oh~, i thought that with a validator there would be type hints, so forgot to define the type of TypeScript, thx 🌷 | 2023-06-27T03:16:07 | 2023-06-27T03:16:07 | {} | NONE |
vuejs | core | 1,609,576,887 | 8,604 | so1ve | Hmmm, maybe u r right! 😂 | 2023-06-27T14:03:49 | 2023-06-27T14:03:49 | {} | MEMBER |
vuejs | core | 1,610,806,493 | 8,618 | Shyam-Chen | - https://github.com/vitejs/vite/issues/17#issuecomment-638847357
- [@volar/vue-language-plugin-pug](https://github.com/vuejs/language-tools/tree/master/packages/vue-language-plugin-pug) | 2023-06-28T06:10:40 | 2023-06-28T07:10:30 | {} | CONTRIBUTOR |
vuejs | core | 1,611,111,490 | 8,670 | Rusinas | Also, locally my problem was that I've tried to put in that global ref the return value of window.getSelection() and ironically it returns the same object every time (window.getSelection() === window.getSelection()), which I didn't consider initially, so my solution was to just ```globalState.value = { ...window.getSel... | 2023-06-28T09:52:40 | 2023-06-28T09:53:15 | {} | NONE |
vuejs | core | 1,602,691,161 | 8,592 | zqran | @sxzz
There are two different cases depending on the operation:
1. `get`
2. `set`
For the `set` case, as long as the value is modified it cannot be hoisted (explicitly).
For the `get` case, the following scenarios are possible:
- `const` (explicitly)
```ts
// hoist
const defaults = { baz: false }
co... | 2023-06-22T13:58:55 | 2023-06-22T13:58:55 | {} | CONTRIBUTOR |
vuejs | core | 1,603,906,616 | 8,592 | sxzz | @zqran Cause exported variable is top level and always inited once, but in `<script setup>` (without this feature), it's inited every time. We must ensure there's no side effect if we hoist inner variable to the top level. | 2023-06-23T08:15:51 | 2023-06-23T08:15:51 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,607,917,693 | 7,677 | mrleblanc101 | @LinusBorg @yyx990803
Sorry to ping again, but any idea when this could get merged ? I would be sad to have to wait another 2 years like we did between 3.2 and 3.3
| 2023-06-26T17:28:19 | 2023-06-26T17:28:19 | {} | NONE |
vuejs | core | 1,609,205,990 | 5,783 | Zelig880 | Hi guys, I just wanted to know that I was going to raise this precise bug.
During Unit Test development we have started to encounter this issue after upgrading from 3.2.27 to 3.2.37. The change that breaks the test is the one highlighted above.
In the previous implementation `this.effects.forEach(e => e.stop())` ... | 2023-06-27T10:12:15 | 2023-06-27T10:12:15 | {
"+1": 1
} | NONE |
vuejs | core | 1,606,806,698 | 6,169 | WORMSS | I see this is still not merged for some reason.. I was coming to see if there is anything I can do to help move this along? | 2023-06-26T06:53:05 | 2023-06-26T06:53:05 | {} | NONE |
vuejs | core | 1,607,848,768 | 8,647 | shengxinjing | https://deploy-preview-8649--vue-sfc-playground.netlify.app/#eNp9U01vozAQ/StTXwJSRA699UtqVzl0D+1qmz2t9+DCENyFMWsbkmyU/96xCbSR2koc8Js34/cew17ctm3WdyguxJXLrW49OPRdeyNJN62xHvZgUeVe9wgHKK1pYMb8mSRJuSHnwVea1nA90ZL9IR1rPOt9hXADT+iT37HnT8o8ST1aXe4YvvfY/CL9r0NC5xLunQ/D00tYLGBVacdnazYutI1I2REPNwRxjsbAUR50CYpA80hgkqpZQ7EDTaCCqDm... | 2023-06-26T16:46:07 | 2023-06-26T16:46:07 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 1,609,113,981 | 8,646 | abczhangshasha | 已解决，和playground上Import Map自动引的vue冲突了，构造了两个实例 | 2023-06-27T09:18:26 | 2023-06-27T09:18:26 | {} | NONE |
vuejs | core | 1,609,258,093 | 5,151 | shengxinjing | [preview](https://deploy-preview-8655--vue-sfc-playground.netlify.app/#eNp9U01v2zAM/SucLnbQIBnaW5YE64oessM2bMNOujg27aqVJUOikxSB//so2c5HUfRgQ+J7JN+jpKO4b5rZrkWxEEufO9UQeKS2WUuj6sY6giM4LKewzyh/gg5KZ2tIOCORRprcGk+Q29YQrAIx/Tz5EoBITyMwhXSX6RanYHXxb1iZjeGgKjLCCazWcJQGYD6HEkObvW11AVuEPNMaC6brV7gFUjX6QFTlUBPWcDvpk4HbU+sMtwfow... | 2023-06-27T10:48:17 | 2023-06-27T10:49:39 | {} | CONTRIBUTOR |
vuejs | core | 1,609,308,979 | 7,835 | davision | Just encounter this bug myself.
```html
<teleport
:disabled="!appState.leftAside"
to="#main-action"
>
<CreateButton />
</teleport>
```
When toggling the boolean leftAside state, the teleported code dissapears. | 2023-06-27T11:24:21 | 2023-06-27T11:24:21 | {} | NONE |
vuejs | core | 1,610,880,600 | 8,565 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c1c87e919c29d0e1b15a5df095d6b3db793f5da5 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2023-06-28T07:03:31 | 2023-06-28T07:03:31 | {} | NONE |
vuejs | core | 1,611,084,141 | 8,670 | Rusinas | Crap, the solution was simple:
=>
But it seems it depends the way I declare my watcher depends on the way I update the ref.
... | 2023-06-28T09:34:32 | 2023-06-28T09:34:32 | {} | NONE |
vuejs | core | 1,616,085,239 | 8,682 | auvred | It seems to be related to https://github.com/vuejs/language-tools/issues/3340
`Transition` component is functional, I guess that this is what causes the error
https://github.com/vuejs/core/blob/3127c4113e6ff381cd8f79a445655f759e08372a/packages/runtime-dom/src/components/Transition.ts#L45-L48 | 2023-07-01T20:11:50 | 2023-07-01T20:11:50 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,607,082,590 | 8,633 | recallwei | Caused by Volar? | 2023-06-26T09:34:49 | 2023-06-26T09:34:49 | {} | NONE |
vuejs | core | 1,608,757,231 | 8,656 | franck-lynn | I modified this, it woks
```vue
<script setup lang="ts">
import { h, useSlots } from "vue"
defineSlots<{
default: (props: { msg: string }) => string
footer: (props: { title: string }) => string
}>()
const MySlots = () => {
const slots = useSlots()
return h("div", null, [slots.default?.({ msg: "the... | 2023-06-27T04:00:38 | 2023-06-27T04:00:38 | {} | NONE |
vuejs | core | 1,608,930,644 | 8,655 | slothvips | 官方不是都已经禁用`undefined`了吗?
是不是意味着 `undefined`推荐用`void`替代 | 2023-06-27T07:15:55 | 2023-06-27T07:15:55 | {
"laugh": 3
} | NONE |
vuejs | core | 1,601,975,727 | 8,618 | sxzz | Not available for now. It's just a thought. | 2023-06-22T03:54:32 | 2023-06-22T03:54:32 | {} | MEMBER |
vuejs | core | 1,603,680,482 | 8,373 | johnsoncodehk | Please track for https://github.com/vuejs/language-tools/issues/3206 | 2023-06-23T04:58:57 | 2023-06-23T04:58:57 | {} | MEMBER |
vuejs | core | 1,604,404,565 | 8,592 | zqran | Thank you for your explanation, I will modify it according to the above content. | 2023-06-23T14:58:53 | 2023-06-23T14:58:53 | {} | CONTRIBUTOR |
vuejs | core | 1,607,142,114 | 8,633 | recallwei | It also cannot pass `vue-tsc` type check. Does `vue-tsc` also belong to `language-tools`? | 2023-06-26T10:08:25 | 2023-06-26T10:08:25 | {
"+1": 1
} | NONE |
vuejs | core | 1,608,971,863 | 6,158 | danielmiksavmlyr | It is June 2023, Vue version 3.3.4 and the issue is still not resolved nor commented. @yyx990803 I know, that this feature was not officially documented, but it was working in Vue 2.x version. Could you please share your thought on that? | 2023-06-27T07:46:53 | 2023-06-27T07:46:53 | {} | NONE |
vuejs | core | 1,610,927,703 | 8,669 | Justineo | See discussions at https://github.com/vuejs/core/pull/7475#pullrequestreview-1239791970
Using `==` with `null` is intentional and [consistent across the codebase](https://github.com/search?q=repo%3Avuejs%2Fcore+%22+%3D%3D+%22&type=code). Thank you. | 2023-06-28T07:43:32 | 2023-06-28T07:43:32 | {} | MEMBER |
vuejs | core | 1,612,565,857 | 7,506 | getlistman | The same issue still exists with vue@3.3.4.
https://codesandbox.io/s/vue-router-playground-forked-ptdmt6?file=/package.json | 2023-06-29T07:39:39 | 2023-06-29T07:39:39 | {} | NONE |
vuejs | core | 1,602,519,669 | 8,466 | ghost | Yes, all events declared with enum are marked as "Not declared" in Vue's browser extension.
Additionally, if you have a parent component that emits same event as it's child component, event callback on parent will be executed twice due to `inheritAttrs: true` default behavior | 2023-06-22T12:04:40 | 2023-06-22T12:04:40 | {} | NONE |
vuejs | core | 1,606,315,215 | 5,724 | so1ve | I think this problem no longer exists because volar supports type-checking dynamic components now.
@juzser @qinlinwang Could you please confirm? | 2023-06-25T23:18:17 | 2023-06-25T23:18:17 | {} | MEMBER |
vuejs | core | 1,607,396,376 | 8,646 | litingyes | 给个建议：别用百度网盘，至少把 node_modules 删了😂 | 2023-06-26T12:47:18 | 2023-06-26T12:47:18 | {} | NONE |
vuejs | core | 1,609,638,685 | 8,659 | so1ve | Pleased read the docs | 2023-06-27T14:36:14 | 2023-06-27T14:36:14 | {} | MEMBER |
vuejs | core | 1,609,954,494 | 8,105 | kikuchan | I've posted a PR (based on another idea), and I've noticed that the same pattern causes the same error, btw.
For example, following lines cause a HMR issue. (failed to reload a page sometimes)
https://github.com/vuejs/core/blob/9f8e98af891f456cc8cc9019a31704e5534d1f08/packages/runtime-core/src/renderer.ts#L374-L375... | 2023-06-27T17:38:42 | 2023-06-27T17:38:42 | {
"eyes": 1
} | NONE |
vuejs | core | 1,610,880,331 | 8,565 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c1c87e919c29d0e1b15a5df095d6b3db793f5da5 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2023-06-28T07:03:17 | 2023-06-28T07:03:17 | {} | NONE |
vuejs | core | 1,612,021,281 | 6,347 | AlexandreBonaventure | Any way I can help in order to speed up the resolution of this ticket ? It's very crippling for our application and the linked MR is now stale for almost a year. | 2023-06-28T19:58:05 | 2023-06-28T19:58:05 | {} | CONTRIBUTOR |
vuejs | core | 1,614,378,635 | 7,343 | jackchoumine | > 这个问题现在有没有解决方式，我的项目也出现了？
Have you worked it out? I met this issue today. | 2023-06-30T09:18:18 | 2023-06-30T09:18:18 | {
"+1": 2
} | NONE |
vuejs | core | 1,615,849,256 | 8,682 | WXperia | use transition-group | 2023-07-01T10:58:30 | 2023-07-01T10:58:30 | {
"laugh": 2
} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.