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,225,964,467 | 6,540 | LinusBorg | 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+n7gNe7Y2O9WSLVjht660AbwMtV0JXSprXIAGnNxDC3tnFEwwddJfvRhlUzzjdCAlvBZ6a... | 2022-08-24T16:33:13 | 2022-08-24T16:33:13 | {} | MEMBER |
vuejs | core | 1,227,289,934 | 6,532 | LinusBorg | That's because in your example you are essentially casting all 4 objects to be of type `Prop`. They don't have their own explicit type that could clash with your `: Props` annotation.
I think what happens in this issue is more like this (pseudocode, and a bit backwards):
```tsx
interface PropsExtractedFromParent... | 2022-08-25T13:50:07 | 2022-08-25T13:52:31 | {} | MEMBER |
vuejs | core | 1,227,325,411 | 6,504 | cokuna-pavelkosolapov | Yes, I could capture all undesirable attribute in that way. But still, I think this behaviour is not correct. | 2022-08-25T14:18:03 | 2022-08-25T14:18:03 | {} | NONE |
vuejs | core | 1,227,932,130 | 6,222 | ZSSXL | same error | 2022-08-26T01:49:52 | 2022-08-26T01:49:52 | {} | NONE |
vuejs | core | 1,220,198,592 | 5,165 | boundless-qi | I find that this problem does not occur when using the option API. Only when using the setup API will the hot update fail! | 2022-08-19T03:18:03 | 2022-08-19T03:18:03 | {
"+1": 1
} | NONE |
vuejs | core | 1,221,663,334 | 6,515 | EmmyMay | Definitely has to do something with `<renderer></renderer>` component because using an ordinary `>div></div>` does not throw off errors
| 2022-08-22T00:46:29 | 2022-08-22T00:46:29 | {} | NONE |
vuejs | core | 1,221,907,654 | 6,517 | LinusBorg | The first point is also a duplicate of #5655 | 2022-08-22T06:32:56 | 2022-08-22T06:32:56 | {} | MEMBER |
vuejs | core | 1,224,124,582 | 6,536 | MAXLZ1 | This is not required in template. You can compile constant.js in SFC Playground.
No this: https://sfc.vuejs.org/#eNqNUl1r20AQ/CuL8pAWIl2apCaobqAESt9b0hdBOEsr3SX3xe3JJhj/9+5JcuK2UPp2O6uZndHuvvgSQrUdsaiLNbVRhwSEaQx3jRMCfihNQEnGhBES2mBkQmBsJO0GeBgRruF3Hnz/ek8T+V5h+wx+TKBSClQLwXOeqPJxEDJoQX1bztRyolYqWXN2ijRO2+Bjgm9ojP/p... | 2022-08-23T14:04:11 | 2022-08-23T14:04:11 | {} | NONE |
vuejs | core | 1,219,816,046 | 5,767 | tintin10q | For me the solution by @MilkoEmanuilov worked. But it updates much slower than before. | 2022-08-18T18:42:27 | 2022-08-18T19:11:49 | {} | NONE |
vuejs | core | 1,221,614,235 | 6,518 | LinusBorg | Serup runs before data. There is no way to access Options API properties in setup. This is intended and documented. | 2022-08-21T20:20:27 | 2022-08-21T20:20:27 | {} | MEMBER |
vuejs | core | 1,221,664,575 | 6,515 | EmmyMay | Also, in the browser elements, those components are not being rendered. `#app should have child elements no?`
| 2022-08-22T00:49:53 | 2022-08-22T00:49:53 | {} | NONE |
vuejs | core | 1,223,451,648 | 6,387 | EmmyMay | Firstly, you cannot translate an inline-element
Secondly taking away the body element styling does not affect the animation when I tried it. | 2022-08-23T02:33:56 | 2022-08-23T02:33:56 | {} | NONE |
vuejs | core | 1,223,698,565 | 6,532 | LinusBorg | For now, just use `?:` in the prop type to make the prop optional. Also allows for rhe prop to be undefined.
```ts
const props = defineProps<{
modelValue?: number
}>();
```
| 2022-08-23T07:58:31 | 2022-08-23T07:58:31 | {} | MEMBER |
vuejs | core | 1,225,574,283 | 6,309 | einavk | Hi,
I'm having similar issue - custom elements who repeat themselves - the first one is ok and rest are broken. Also - only happens on global.prod.min and not on dev env.
However, in my case, it is not related to v-for at all.
I noticed that the "broken" custom elements are my "static" elements, and not those who ha... | 2022-08-24T11:09:45 | 2022-08-24T11:29:12 | {} | NONE |
vuejs | core | 1,227,226,602 | 4,960 | fiftin | > This is inherent to the language, in your scenario, using a Promise is the right approach, even inside of `setup()`:
>
> ```js
> async setup() {
> data.value = await stuff()
> return { data }
> }
> ```
>
> is different from
>
> ```js
> setup() {
> stuff().then(d = > data.value = d)
> return {... | 2022-08-25T13:00:29 | 2022-08-25T13:01:16 | {
"+1": 9
} | NONE |
vuejs | core | 1,217,241,819 | 6,391 | 719media | Just leaving a follow up note that the same problem/behavior happens in safari desktop/mobile for a template like:
```
<img
:srcset="https://domain.com/image.jpg?w=200 200w, https://domain.com/image.jpg?w=100 100w"
sizes="50px"
>
```
What happens is, Safari eagerly loads the srcset before the `sizes` att... | 2022-08-16T22:39:59 | 2022-08-16T22:42:23 | {
"+1": 1
} | NONE |
vuejs | core | 1,219,215,750 | 3,936 | Daniel-Musunza | i've got the same problem can i get some help
**1st err**
**my app.vue**
**my productCard.vue... | 2022-08-18T08:57:36 | 2022-08-18T08:57:36 | {} | NONE |
vuejs | core | 1,221,527,294 | 2,513 | Hyperblaster | @lidlanca thanks so much! This helped me solve my issue. Adding the script into the head (before vue is initialised) seemed to do the trick. I tried all kinds of things in `onMounted` hooks and nothing seemed to work.
Hopefully this can be merged and fixed in core soon | 2022-08-21T11:32:23 | 2022-08-21T11:32:23 | {
"+1": 1
} | NONE |
vuejs | core | 1,221,619,702 | 6,518 | LinusBorg | Please suggest improvements to the docs in the docs repository, we are open to contributions.
It might indeed to be helpful to mention the requirement for `defineComponent()` for Typescript users in the migration docs.
Besides that, I mention again: The methods work *at runtime*, `defineComponent()`is only necess... | 2022-08-21T20:57:54 | 2022-08-21T20:58:19 | {} | MEMBER |
vuejs | core | 1,225,042,564 | 4,294 | alex-dow | > I found some hack. Currently, it works for me. Just wrap imported type with `Omit`.
>
> ```
> <script setup lang="ts">
> import { Button as AButton, ButtonProps } from "ant-design-vue";
> interface Props extends Omit<ButtonProps, ""> {}
>
> const props = defineProps<Props>();
> </script>
>
> <templ... | 2022-08-24T00:58:09 | 2022-08-24T00:58:09 | {
"eyes": 4
} | NONE |
vuejs | core | 1,227,121,731 | 6,532 | 2-5 | I get the errors both in VS Code with Volar when the file is open and when running `npx vue-tsc -noEmit` in the terminal in a `vite` based project.
I tried your changes, I still get type errors.
Volar:
```
Type '{ modelValue: number | undefined; }' is not assignable to type
'Omit<Readonly<ExtractPropTypes<_... | 2022-08-25T11:16:23 | 2022-08-25T11:16:39 | {} | NONE |
vuejs | core | 1,217,493,373 | 6,222 | boundless-qi | same error！ | 2022-08-17T05:54:19 | 2022-08-17T05:54:19 | {} | NONE |
vuejs | core | 1,218,578,928 | 2,855 | glspdotnet | > Additionaly, if I remove the leading div, I get a Vue Warning: "Extraneous non-props attributes (name) were passed to component but could not be automatically inherited because component renders fragment or text root nodes. " (which probably makes sense, but still, maybe it helps)
I can't speak to the dev/prod bui... | 2022-08-17T22:56:25 | 2022-08-17T22:56:25 | {} | NONE |
vuejs | core | 1,221,123,738 | 2,513 | Hyperblaster | Really struggling with this one. None of the workarounds above seem to work reliably and @semiaddict 's pull request has been sitting there unmerged for over 6 months.
Is there any updates? | 2022-08-19T22:02:55 | 2022-08-19T22:02:55 | {} | NONE |
vuejs | core | 1,221,614,677 | 6,517 | LinusBorg | Yes, const variables cannot be changed in Javascript. No, this is not a bug. Is part of the language | 2022-08-21T20:23:21 | 2022-08-21T20:23:31 | {} | MEMBER |
vuejs | core | 1,221,668,675 | 6,504 | EmmyMay | Hello, you are getting this prop error because `:a="343"` is a number not a string. To make it a string, that would be `:a="'343'"`
| 2022-08-22T01:00:03 | 2022-08-22T01:00:03 | {} | NONE |
vuejs | core | 1,221,670,877 | 6,504 | EmmyMay | Are you claiming there should be a change in how vue works or something? Because it makes sense that the grandparent value takes precedence because that is what is RENDERED on screen. I can't seem to find what is wrong with this code apart from the prop error | 2022-08-22T01:05:01 | 2022-08-22T01:05:01 | {} | NONE |
vuejs | core | 1,221,715,850 | 6,499 | EmmyMay | @LinusBorg hi. I am looking into making a PR for this. Would you say the fix for this lies in the `const forAliasRE = /([\s\S]*?)\s+(?:in|of)\s+([\s\S]*)/` regex? | 2022-08-22T02:22:33 | 2022-08-22T02:22:33 | {} | NONE |
vuejs | core | 1,221,761,600 | 6,517 | zhangenming | 104 edge on win... | 2022-08-22T03:39:12 | 2022-08-22T03:39:12 | {} | CONTRIBUTOR |
vuejs | core | 1,221,894,285 | 6,526 | LinusBorg | No, warnings for problems will not be optional. Not catching this error is a bad idea. | 2022-08-22T06:19:11 | 2022-08-22T06:19:11 | {} | MEMBER |
vuejs | core | 1,218,531,005 | 5,836 | RoosDev | Yes I'm agree with you.
I would like to animate a component (like a modal) but inside the component I use a teleport ... so the transition doesn t work.
For me it look's like :
`<transition>
<ModalWindow>
</transition>`
and in the component ModalWindow :
`<Template>
<teleport to=".myWonderfullDiv... | 2022-08-17T22:00:25 | 2022-08-17T22:00:25 | {} | NONE |
vuejs | core | 1,219,079,158 | 6,467 | moushicheng |
> this seems not to fix #6463. see [demo with your deploy preview](https://deploy-preview-6467--vue-sfc-playground.netlify.app/#eNqlVMuK2zAU/ZWLNuNAZKVQppBxAmE2hW4KU+jGGze+blRsSUiy0zD436uHHSsz09lMNtF9nXPPsexnclAqH3okW1JY7FRbWdyXAqCo+bAHAH920VNvFAoTayHj63MwhV+xbWXBXlS+IapDy4dlNqQfOwUD5c2uJNw8neRZlASYp5x+CQR7jZHSFOxm... | 2022-08-18T06:14:55 | 2022-08-18T10:46:22 | {} | CONTRIBUTOR |
vuejs | core | 1,221,940,028 | 6,525 | jambonn | @LinusBorg Thank you. If possible, can you suggest me how to replace createVNode and render? | 2022-08-22T07:08:10 | 2022-08-22T07:08:10 | {} | NONE |
vuejs | core | 1,224,522,423 | 5,584 | mileusna | My fist Vue project, everything is working fine and then after "npm run build" I ran into this bug, what a bad luck! And here I am after lots of googling. Yes, moving everything from `<script setup>` to `<script>` solves the problem, thank you for that.
Fairly simple code for this view. I have just removed login pro... | 2022-08-23T18:14:21 | 2022-08-23T18:16:37 | {} | NONE |
vuejs | core | 1,225,976,671 | 6,540 | OrbisK | > 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+n7gNe7Y2O9WSLVjht660AbwMtV0JXSprXIAGnNxDC3tnFEwwddJfvRhlUzz... | 2022-08-24T16:44:27 | 2022-08-24T17:53:14 | {} | CONTRIBUTOR |
vuejs | core | 1,226,878,505 | 4,294 | myesn | Many thanks to Evan You and the rest of the community for developing and maintaining Vue, but I'm sorry I have to comment because this issue has been around for a year and I don't mean to rush you to fix it, I just want to know if there's a temporary solution, thanks again for your efforts. | 2022-08-25T07:24:47 | 2022-08-25T07:24:47 | {} | NONE |
vuejs | core | 1,226,893,076 | 6,532 | LinusBorg | When and where exactly is that error being raised? Do you also get an error in VSCode/your IDE?
As an experiment, try this please:
```ts
const props = defineProps<{
modelValue?: number | undefined
'onUpdate:modelValue'?: undefined | (value: number | undefined) => any
}>
```
and *don't* use `defineEmits(... | 2022-08-25T07:39:31 | 2022-08-25T07:54:45 | {} | MEMBER |
vuejs | core | 1,227,177,895 | 6,532 | LinusBorg | Okay, so I can kinda reproduce this, but a full repro from your side in a github repo would be apprechiated to make sure we are looking at the same things.
I have:
* `exactOptionalPropertyTypes: true` in my tsconfig
* Typescript 4.6 in my project i'm testing with. (yes, not latest)
* latest Volar / `vue-tsc` (0... | 2022-08-25T12:15:16 | 2022-08-25T12:20:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,367,403,067 | 1,050 | Ronan-bkg | For others genius like us, I had the same issue :
`[Vue warn]: Missing ref owner context. ref cannot be used on hoisted vnodes. A vnode with ref must be created inside the render function.`
It was because **i had two different versions of Vue in node_module**.
( monorepo with multiple package.json with differe... | 2022-12-29T15:16:21 | 2022-12-29T15:19:02 | {
"+1": 2
} | NONE |
vuejs | core | 1,368,037,316 | 7,437 | LinusBorg | > i think it is important than a framework have same behavior in both mode, both stop the browser or both stop in max count
* the max count check has a negative performance impact, so it's active only in dev.
* and it's in dev because the warning we can give this way is much more helpful than a context-free `max st... | 2022-12-30T18:08:53 | 2022-12-30T22:50:37 | {} | MEMBER |
vuejs | core | 1,368,191,510 | 7,437 | sxzz | @Inori-Lover 🤔 Hmmm it makes sense.
I think we should change the warning to an error too and it's a serious error to be fixed by developers. | 2022-12-31T09:35:14 | 2022-12-31T09:35:14 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,368,201,805 | 7,441 | LinusBorg | Hi there.
It would be very helpful if you could explain what you are actually trying to achieve. I have a hard time understanding that from the code example. Also, if the example can't be run in the SFC playground, please provide a repository instead where it does run.
But it *seems* like you want to replace a te... | 2022-12-31T11:12:56 | 2022-12-31T11:12:56 | {} | MEMBER |
vuejs | core | 1,368,618,924 | 7,437 | smallnine9 | so, maybe we need to replace the 'warn' with throwing an error? But I want to know how to test changes in prod mode? Since the SFC also running in dev mode | 2023-01-02T02:55:37 | 2023-01-02T02:55:37 | {} | CONTRIBUTOR |
vuejs | core | 1,369,087,062 | 7,449 | LinusBorg | "runnable reproduction" means source code i can run. Either on sfc.vuejs.org or in a github repo or similar. | 2023-01-02T16:49:12 | 2023-01-02T16:49:12 | {} | MEMBER |
vuejs | core | 1,369,471,147 | 7,280 | SailSpring | I tried. In this case,<keep alive>will not cache the page, and page1 and page2 will be remounted every time. | 2023-01-03T07:48:12 | 2023-01-03T07:48:12 | {} | NONE |
vuejs | core | 1,369,505,755 | 7,425 | yurj26 | > LGTM
When will this PR be merged? | 2023-01-03T08:40:36 | 2023-01-03T08:40:36 | {} | CONTRIBUTOR |
vuejs | core | 1,369,708,034 | 7,450 | caveofjulian | But why did this behavior change from Vue version 3.2.25 to 3.2.45? Normally, it would pick up that change. I find it confusing and I get into problems where upgrading one package leads to issues in another package. I wonder what exactly changed about the reactivity but couldn't find it in the logs. | 2023-01-03T12:22:13 | 2023-01-03T12:22:13 | {} | NONE |
vuejs | core | 1,366,403,325 | 3,102 | hymair | I just want to mention this video which outlines (and solves for React) this exact issue - https://www.youtube.com/watch?v=hBk4nV7q6-w | 2022-12-28T06:26:53 | 2022-12-28T06:26:53 | {
"+1": 1,
"-1": 2
} | NONE |
vuejs | core | 1,366,423,495 | 7,423 | sxzz | @mnixry I fixed that. | 2022-12-28T07:11:47 | 2022-12-28T07:11:47 | {} | MEMBER |
vuejs | core | 1,367,104,266 | 7,176 | sxzz | @hydrati Sure | 2022-12-29T06:42:41 | 2022-12-29T06:42:41 | {} | MEMBER |
vuejs | core | 1,367,374,293 | 7,428 | zhangzhonghe | > [Demo](https://deploy-preview-7428--vue-sfc-playground.netlify.app/#eNqdkM1OxDAMhF/F+FKQSCsQEqjqrsSNN+CSS2nd3aL8WEnaVVXl3XG7iAPHvWVm8nksr/jOXM4TYY1N7MLICSKliY/ajZZ9SLCCxkCDRmgjyAMyDMFbKIQqtGuqKyaAiJtGaNd5FxPYeILDlt8XH2SMh08fTH9XPPxvSWTZtIlEATTnp+O67nDOTSVqd0fHU4JZWd+TOWiUXKNETfVH4yNeF1S25fI7eidXWDda/wZRYw27s3my7aY1nl... | 2022-12-29T14:37:10 | 2022-12-29T14:38:10 | {} | MEMBER |
vuejs | core | 1,367,652,939 | 7,173 | enkot | My point in this proposal is more about cleaner component look without the repetitive lang=“ts” in each file. For sure, most of devs use snippets and this is even not a problem, it’s just “don’t repeat it” feature if you have 100% TS codebase. | 2022-12-30T00:17:58 | 2022-12-30T00:19:12 | {
"+1": 4
} | NONE |
vuejs | core | 1,368,411,139 | 7,199 | LinusBorg | Thanks! | 2023-01-01T10:44:23 | 2023-01-01T10:44:23 | {
"heart": 1,
"rocket": 1
} | MEMBER |
vuejs | core | 1,368,412,533 | 7,176 | LinusBorg | I have my a doubts about this change - not about what it does (I think it makes sense), but when to introduce it.
It feels like a breaking change that would have to wait for Vue 4. Even if it's not to be considered a breaking change, it should only be introduced in a minor release, not a patch version.
For one, ... | 2023-01-01T10:57:05 | 2023-01-01T11:15:57 | {
"+1": 5
} | MEMBER |
vuejs | core | 1,369,536,844 | 7,453 | LinusBorg | Expected behaviour.
1. The variables Data in the normal script block are **shared** between both instances of the component
2. Each component only re-renders when one of its **own** reactive dependencies changes (`a`).
3. But when you bring in the `another` ref, this ref is now a **shared** reactive dependency of **... | 2023-01-03T09:14:01 | 2023-01-03T09:14:20 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,370,404,758 | 3,452 | rudyxu1102 | https://github.com/vuejs/rfcs/pull/477
cc @agileago @axelthat | 2023-01-04T02:01:15 | 2023-01-04T02:01:15 | {} | CONTRIBUTOR |
vuejs | core | 1,367,330,963 | 7,428 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | dbf987e26ad0dac3ad13b1b628a0b86574980f84 |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-12-29T13:43:07 | 2022-12-29T13:43:07 | {} | NONE |
vuejs | core | 1,367,977,192 | 7,437 | sxzz | ```diff
+++ watch(() => state.value.deep, () => {
--- watch(() => [state.value.deep], () => {
```
or check the new value and old value yourself
It will avoid recursive updates. | 2022-12-30T15:40:36 | 2022-12-30T15:40:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,367,979,812 | 7,437 | Inori-Lover | > ```diff
> +++ watch(() => state.value.deep, () => {
> --- watch(() => [state.value.deep], () => {
> ```
>
> or check the new value and old value yourself
>
> It will avoid recursive updates.
i am not interested in how to fix this code; if i write the logic, data update will not appera in watch cb but in e... | 2022-12-30T15:47:25 | 2022-12-30T15:47:25 | {} | NONE |
vuejs | core | 1,368,204,973 | 7,441 | sj7112 | idea is to build a shell comp, the parent passes all the data/functions/template to it. Just like functional comp, but it can change the template.
The same issue as I said before, why VUE doesn't allow us to modify the template? I'm thinking to raise a discussion late on. | 2022-12-31T11:44:34 | 2022-12-31T11:44:50 | {} | NONE |
vuejs | core | 1,368,399,283 | 7,199 | g1eny0ung | @sxzz @pikax Since I have a vue image library that depends on this PR for updates, I would like to ask if this PR can be merged. Thanks a lot for taking the time to help with the review. | 2023-01-01T09:43:00 | 2023-01-01T09:43:00 | {} | CONTRIBUTOR |
vuejs | core | 1,369,080,676 | 7,448 | michelvermeulen | Sorry, I actually commented out the focus in the SFC. It's back on.
What I do is play around with the buttons/esc to go back and forth, and randomly force GC in the Chrome console.
This is what I start with, and end up with after playing for a minute:
Fresh state
 (Volar) v1.0.9.
>
> My component looks like this:
>
> ```ts
> function myExposedMethod() {
> console.log("test");
> }
>
> defineExpose({
> myExposedMethod,
> });
> ```
>
> and I have a ref in the parent component like this:
>
> ```ts
... | 2022-12-29T06:01:57 | 2022-12-29T06:02:47 | {
"+1": 2
} | NONE |
vuejs | core | 1,367,194,377 | 7,427 | zhangzhonghe | This does not seem to be a bug of Vue, as the ``rerender`` and ``reload`` functions of HMR are not executed after changing the file.
Could you open an issue in Vite and preferably provide a **minimal** reproduction without other third-party dependencies?
I'll close this for now. If you have any new problems on vu... | 2022-12-29T09:44:51 | 2022-12-29T09:44:51 | {} | MEMBER |
vuejs | core | 1,320,678,126 | 7,176 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | eaa323cb10f74548e2021119d51dfa8df70eb78a |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-11-19T00:01:42 | 2022-12-29T12:14:17 | {} | NONE |
vuejs | core | 1,368,189,308 | 7,437 | sxzz | Actually, warnings are not to be ignored in Vue. | 2022-12-31T09:13:44 | 2022-12-31T09:13:44 | {} | MEMBER |
vuejs | core | 1,368,190,347 | 7,437 | Inori-Lover | @sxzz i know vue team has warning me/us in console to friendly reminder me modify my code, but catch an error then change it to a warn is not a good practice, right? it make wrong code "work".
and we can not expect all dever open dev tool all the time | 2022-12-31T09:24:25 | 2022-12-31T09:24:25 | {
"+1": 3
} | NONE |
vuejs | core | 1,368,204,588 | 7,441 | sj7112 | https://stackblitz.com/edit/vitejs-vite-yus79e?file=src%2FApp.vue,src%2Fviews%2FrenderVnode.ts | 2022-12-31T11:40:59 | 2022-12-31T11:40:59 | {} | NONE |
vuejs | core | 1,369,482,006 | 7,392 | eddeisling | @edison1105 I was wrong and my problem is not relative to this issue.
https://sfc.vuejs.org/#eNp9Uc1O80AMfBVrL7RSk9X3wyWkERw5I3HKpSQuXcj+yOukoCo8O96E0gISh6qxx+OZHR/UTQj50KMqVBkbMoEhIvehqh2AscETwwEItytovA09YwsjbMlbuBDaRRpLv8a7yGB9ix2s0/yCqcfl1Qkb7hryXUIPMtc72VTAArslrCvALhd1gW8d+3uD+8USRiGXejYldqRgtKHbME7mytYMMGQzrSq1... | 2023-01-03T08:06:25 | 2023-01-03T08:06:25 | {} | NONE |
vuejs | core | 1,369,683,076 | 7,450 | zhangzhonghe | ```js
const rows = computed(() => {
console.log("triggered!");
return store.state.rows;
});
```
The above ```computed``` dependencies ```store.state.rows```, so you need to change the ```store.state.rows``` to trigger the ```computed``` rerun. But it is no code to change the ```store.state.row``` i... | 2023-01-03T11:54:10 | 2023-01-03T11:58:00 | {} | MEMBER |
vuejs | core | 1,366,603,377 | 7,424 | zhaozhongyu | 确定了, 只要在tsconfig.json中包含了includes就会有问题
```
"include": [
"src/**/*.ts",
"src/**/*.d.ts",
"src/**/*.vue"
],
``` | 2022-12-28T12:06:53 | 2022-12-28T12:06:53 | {} | NONE |
vuejs | core | 1,367,313,928 | 2,084 | yuntian001 | > 三年又三年
以有对应实现：源代码：https://github.com/meadmin-cn/meadmin-template/tree/main/src/components/meKeepAlive
对应文档：https://meadmin-cn.github.io/meadmin-template-doc/components/core/meKeepAlive.html | 2022-12-29T13:18:27 | 2022-12-29T13:18:27 | {} | NONE |
vuejs | core | 1,367,332,063 | 7,428 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | dbf987e26ad0dac3ad13b1b628a0b86574980f84 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-29T13:45:09 | 2022-12-29T13:45:09 | {} | NONE |
vuejs | core | 1,367,388,130 | 7,392 | eddeisling | The same happens with a checkbox. Value is set after control is added to the dom which triggers transition animations. | 2022-12-29T14:56:58 | 2022-12-29T14:56:58 | {
"+1": 2
} | NONE |
vuejs | core | 1,368,188,674 | 7,437 | Inori-Lover | @LinusBorg problem is same wrong code, vue "work" in dev mode but not in prod mode.
may be vue team can consider thrown error in dev mode too? | 2022-12-31T09:07:10 | 2022-12-31T09:07:23 | {} | NONE |
vuejs | core | 1,366,417,608 | 7,423 | mnixry | It actually reverts #6778, :(
wait for a minute, i will made a PR for this | 2022-12-28T07:01:56 | 2022-12-28T07:04:31 | {} | NONE |
vuejs | core | 1,367,251,878 | 7,430 | LinusBorg | This is not a fix for a bug, see comment in the linked issue. | 2022-12-29T11:22:39 | 2022-12-29T11:22:39 | {} | MEMBER |
vuejs | core | 1,369,075,906 | 7,448 | LinusBorg | I compared two heap snapshots on the provided reproduction and can't really spot anything extraordinary. Would you be able to provide a bit more guidance on where and how you see the leaked components and listeners? | 2023-01-02T16:26:15 | 2023-01-02T16:26:15 | {} | MEMBER |
vuejs | core | 1,369,081,821 | 7,448 | michelvermeulen | Not a major overhead but when you work with lots of lines and an app that stays in for a long time you end up with a large chunk of memory leaking. | 2023-01-02T16:38:28 | 2023-01-02T16:38:28 | {} | NONE |
vuejs | core | 1,369,082,826 | 7,449 | caveofjulian | https://6hrrjp.csb.app/ | 2023-01-02T16:40:31 | 2023-01-02T16:40:31 | {} | NONE |
vuejs | core | 1,370,254,063 | 7,459 | MoishyS | we should make this clear in the docs, that for custom attribute will only get removed if its set to null | 2023-01-03T21:43:46 | 2023-01-03T21:43:46 | {} | NONE |
vuejs | core | 1,368,653,290 | 5,423 | rudyxu1102 | https://github.com/vuejs/rfcs/pull/477
cc @bosens-China | 2023-01-02T04:38:46 | 2023-01-04T02:01:53 | {} | CONTRIBUTOR |
vuejs | core | 1,366,966,367 | 7,417 | LinusBorg | Ah ses, this was a bug that was fixed in 3.2.45. See:
https://github.com/vuejs/core/issues/5655 (commit https://github.com/vuejs/core/commit/f73925d76a76ee259749b8b48cb68895f539a00f)
| 2022-12-28T22:47:56 | 2022-12-28T22:48:26 | {} | MEMBER |
vuejs | core | 1,367,201,441 | 7,425 | yurj26 | > LGTM
thanks | 2022-12-29T09:58:16 | 2022-12-29T09:58:16 | {} | CONTRIBUTOR |
vuejs | core | 1,367,222,702 | 7,429 | sxzz | You should use `ref` for a primitive value
https://sfc.vuejs.org/#eNp9kMtuwjAQRX9lNBtaidiij00aKvof3tBkKGnxQ/YkLKL8e8dJKwWQ8M73js8ZecCPEFTfEZZoXMVkw2nP9G4cyKlaFzqGvrC+odPW4PkoZU/RIGiZqfTigVxTHdvAkIi7MCEMtzb4yDBEOoxwiN7CSmyrmV97lxj+obAFmXrYbB7fMnqGTWDANc6gwu6D+k7eyb7DZPgrksESpiRnosh3g0fmkEqtOxd+vlTtrd5Jp2PnZDMqGm93z+pJv... | 2022-12-29T10:32:10 | 2022-12-29T10:32:10 | {} | MEMBER |
vuejs | core | 1,367,277,817 | 7,429 | baohangxing | the primitive value here is just a example
**see this =>**
to reassign an array with v-model, like
[this example](https://sfc.vuejs.org/#eNp9U0tv2zAM/iuELnYAP7DXxUuKDjsPu+0S5eDabOPMekCS3Q2B/3spOXKdtKgPlkRS/D7yo87sh9bFOCCrGJdbh0L3tcM7LoG+bTNYp0TeKKGVROlgzIVqsd9x9nykuBENZ1BS+LZc3aWjbUynHVh0gw7ZuOsoiXFwBoN147oRY... | 2022-12-29T12:13:02 | 2022-12-29T12:13:02 | {
"eyes": 1
} | NONE |
vuejs | core | 1,367,291,734 | 7,429 | LinusBorg | Again: for that, we need to use a `ref()` | 2022-12-29T12:39:14 | 2022-12-29T12:39:14 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,367,940,705 | 7,436 | perelin | Grrrr, seems I need to wait for nextTick(). This SO answer helped https://stackoverflow.com/questions/49031373/ref-array-inside-refs-undefine-inside-mounted | 2022-12-30T14:11:56 | 2022-12-30T14:11:56 | {} | NONE |
vuejs | core | 1,368,468,367 | 4,339 | danyadev | Looking forward to this feature | 2023-01-01T15:23:02 | 2023-01-01T15:23:02 | {} | CONTRIBUTOR |
vuejs | core | 1,367,286,946 | 7,173 | johnsoncodehk | Thank you for your proposal, but I hope avoid adding this feature, I think it makes sense to add lang explicitly.
- This feature needs to be followed by all downstream tools, we should try our best to avoid this, because if some IDE can't support it, we can't control this. Volar is easy to support for IntelliSense, ... | 2022-12-29T12:29:45 | 2022-12-29T12:29:45 | {
"+1": 3,
"-1": 1,
"eyes": 5
} | MEMBER |
vuejs | core | 1,367,434,961 | 5,897 | Michael-E-Rose | So, it would be
Vue.js developers. (2014). Vue.js -- The Progressive JavaScript Framework v3.0. [Online]. Available https://vuejs.org/guide/introduction.html, access on: 29 December 2022
or what?
Would be good to have some guidance by the developers here. | 2022-12-29T16:07:35 | 2022-12-29T16:07:35 | {
"+1": 2
} | NONE |
vuejs | core | 1,368,417,927 | 7,176 | hydrati |
> For one, today some libraries choose to publish raw .vue files, which works particularly well if they re already written in plain JS and CSS. Those might break if the consuming app has set the default script lang to ts.
Maybe I need to add an "scope" option to keep the compatibility for those libraries.
> Furtherm... | 2023-01-01T11:10:57 | 2023-01-01T11:10:57 | {} | NONE |
vuejs | core | 1,368,454,858 | 7,437 | sxzz | Sure, if you would like | 2023-01-01T14:13:20 | 2023-01-01T14:13:20 | {} | MEMBER |
vuejs | core | 1,368,813,713 | 7,285 | atonemi | @zhangzhonghe I love you | 2023-01-02T10:24:48 | 2023-01-02T10:24:48 | {} | NONE |
vuejs | core | 1,369,304,357 | 7,392 | edison1105 | @edikdeisling
Could you provide a minimal reproduction? | 2023-01-03T01:08:32 | 2023-01-03T01:08:32 | {} | MEMBER |
vuejs | core | 1,369,598,288 | 7,450 | caveofjulian | @zhangzhonghe thanks, yes I suspected that it could also have to do with ag-grid. However, this worked before the Vue update. What I find strange is that Ag-Grid updates it correctly, the Vue plugin shows that it gets in the store successfully. Therefore, it's strange that the computed property does not execute. What c... | 2023-01-03T10:19:14 | 2023-01-03T10:19:14 | {} | NONE |
vuejs | core | 1,369,724,977 | 7,455 | LinusBorg | 1. This seems to be about Vue CLI, so it's the wrong repository.
2. Vue CLI is in maintenance mode, so no further features will be added.
3. you can already edit the title in public/index.html.. For vite based projects, that's also possible.
4. Your tone does not warrant any further interaction. Good luck. | 2023-01-03T12:42:48 | 2023-01-03T12:46:53 | {} | MEMBER |
vuejs | core | 1,370,162,261 | 7,458 | LinusBorg | Here's an example: https://codepen.io/LinusBorg/pen/qByabaV | 2023-01-03T19:48:37 | 2023-01-03T19:48:37 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.