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
903,094,199
4,408
posva
We can't read your mind 😄 , can you talk to us to explain what you want?
2021-08-21T10:11:03
2021-08-21T10:11:03
{}
MEMBER
vuejs
core
903,682,973
4,403
Fiona-SUN
@LinusBorg Thanks for you helping! I agree with this. Indeedly, a function has additional properties should be function extension. - but it is undeniable that convenient methods are more popular with people.
2021-08-23T11:31:18
2021-08-23T11:31:18
{}
NONE
vuejs
core
903,716,102
4,420
posva
This is expected because you modified manually the style of the element instead of using a reactive value: ```js document.getElementById('text1').style.display="block" ``` Vue cannot be aware of this change and sets the display to none as specified in the template. --- Remember to use the [forum](http:/...
2021-08-23T12:22:52
2021-08-23T12:22:52
{}
MEMBER
vuejs
core
904,301,749
4,427
zhangenming
Another problem, thanks now the Package lint field : `"lint": "eslint --ext .ts packages/*/src/**.ts",` Why only src, should __tests__ be included?: `"lint": "eslint --ext .ts packages/*/{src,__tests__}/**.ts",`
2021-08-24T03:55:41
2021-08-24T03:55:41
{}
CONTRIBUTOR
vuejs
core
904,404,401
4,428
LinusBorg
Strictly speaking this is not really a bug as the custom element does what it's supposed to do: it emits the component event as a custom event. The problem is that v-model listens for `input` but the custom element emits an `update:modelValue` event. However we should discuss how we can better support this common us...
2021-08-24T07:44:47
2021-08-24T07:46:04
{}
MEMBER
vuejs
core
904,986,458
2,349
Miguelklappes
+100 for this
2021-08-24T21:23:07
2021-08-24T21:23:07
{ "+1": 5 }
NONE
vuejs
core
905,151,890
4,424
nVitius
@yyx990803 Thanks for the review. I made the requested changes.
2021-08-25T03:23:23
2021-08-25T03:23:23
{}
NONE
vuejs
core
905,268,880
4,435
posva
This is expected and has been discussed already: SFC compiled with 3.2.x are compatible with ^3.2x (3.2, 3.3, 3.4, etc). Use peerdependencies to make the minimum required version to be ^3.2.0 It would be otherwise impossible to bring improvements to templates (and sometimes even some bug fixes)
2021-08-25T07:51:30
2021-08-25T07:51:30
{}
MEMBER
vuejs
core
905,336,112
4,437
edison1105
see https://v3.vuejs.org/guide/migration/custom-elements-interop.html#_3-x-syntax your should config `isCustomElement`
2021-08-25T09:27:35
2021-08-25T09:27:35
{}
MEMBER
vuejs
core
905,968,747
4,430
webfansplz
@uinio Reason: https://github.com/vuejs/vue-next/issues/4288#issuecomment-895723947
2021-08-26T00:36:01
2021-08-26T00:36:01
{}
MEMBER
vuejs
core
906,203,278
4,450
laineus
See also this PR: https://github.com/vuejs/vue-next/pull/4447
2021-08-26T08:27:54
2021-08-26T08:27:54
{}
CONTRIBUTOR
vuejs
core
903,214,093
4,410
webfansplz
i can't reproduced it , can you provide a mini repo ?
2021-08-22T05:03:31
2021-08-22T05:03:31
{}
MEMBER
vuejs
core
904,105,010
4,423
posva
Maybe a duplicate of https://github.com/vuejs/vue-next/issues/4294 as it seems that you can import what is exported in [other files](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuPC90ZW1wbGF0ZT5cblxuPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbiAgZXhwb3J0IGludGVyZmFjZSBIZWxsb1dvcmxkUHJvcHMge1xuICBtc2c6IHN0cmluZ1xufVxu...
2021-08-23T20:35:12
2021-08-23T20:35:12
{}
MEMBER
vuejs
core
904,337,879
4,422
qq974969638
I think there is a solution. Due to my limited technical ability, I don't know if this repair will cause other problems. Here I only provide my suggestions for your reference, thank you. The original function: `function toValidAssetId(name, type) {` ` return `_${type}_${name.replace(/[^\w]/g, '_')}`;` `}` ...
2021-08-24T05:39:30
2021-08-24T05:39:30
{}
NONE
vuejs
core
904,456,489
4,428
LinusBorg
On second thought, I'm inclined to rate this as a bug. There's a few different aspects to this, the thing to discuss is wethe we want to support v-model on a custom element at all. We currently support it on distinct native input elements only (and components, but we are dealing with a custom DOM element here). If w...
2021-08-24T08:56:57
2021-08-24T08:57:16
{ "+1": 2 }
MEMBER
vuejs
core
905,430,683
3,798
Zclhlmgqzc
> Thanks, maybe the second option might be better (but just a preference) Thanks for your review
2021-08-25T11:52:49
2021-08-25T11:52:49
{}
CONTRIBUTOR
vuejs
core
906,175,098
4,444
Liwoj
My bad, completely overlooked the change of transition classes from `v-enter` to `v-enter-from`. Closing...
2021-08-26T07:46:53
2021-08-26T07:46:53
{}
NONE
vuejs
core
902,684,663
4,400
LinusBorg
the return value of the new computed that you introduced is still a plain array (`computed` doesn't "reactive-fy" its return values, never has). Which will not be unwrapped.
2021-08-20T13:14:31
2021-08-20T13:17:04
{}
MEMBER
vuejs
core
903,345,671
3,989
andylizi
This is actually unrelated to `compat`. As far as I can tell, it happens whenever there's a `<slot>` wrapped in `<transition>`. Here's my reproduction using only `vue@3.2.4`: https://codesandbox.io/s/9mo46?file=/src/App.vue
2021-08-22T23:15:42
2021-08-22T23:15:42
{ "+1": 2 }
CONTRIBUTOR
vuejs
core
904,349,737
4,426
HcySunYang
It’s not a good practice to get slots manually, for this scenario, you can use provide & inject to achieve the goal: https://codesandbox.io/s/billowing-hooks-k8x0n?file=/src/components/VueButton.vue
2021-08-24T06:07:06
2021-08-24T06:07:06
{ "+1": 1, "hooray": 2 }
MEMBER
vuejs
core
905,143,953
4,433
sxzz
Another problem: ```ts import { ref } from 'vue'; let ref1 = $(ref()); // any let ref2 = $ref(); // { // [RefMarker]?: any; // } ref1 = 'hello world'; ref2 = 'hello world'; // 类型“"hello world"”与类型“{ [RefMarker]?: any; }”不具有相同的属性。ts(2559) console.log(ref1, ref2); ```
2021-08-25T03:06:42
2021-08-25T03:06:42
{}
MEMBER
vuejs
core
905,300,994
4,436
posva
Deleting your lock and running `yarn`/`npm i` should fix this issue. Another possible solution is removing all the vue (vue, `@vue/*`) dependencies and add them again. Not sure why this is happening but this is how I fixed it in my projects.
2021-08-25T08:37:48
2021-08-25T08:37:48
{}
MEMBER
vuejs
core
905,867,909
4,445
LinusBorg
That's because of the computed property and a common misunderstanding about how they work. I'm having a blog post about that topic ready, just don't know yet where to post it. The gist of it is: computed properties are evaluated when they are read. So the return value is only known when they are read. before that...
2021-08-25T20:56:42
2021-08-25T20:56:42
{ "+1": 1 }
MEMBER
vuejs
core
905,904,721
4,443
tochoromero
This is the error I get. By reading the source code you can see how it is failing. <img width="599" alt="Screen Shot 2021-08-25 at 4 59 18 PM" src="https://user-images.githubusercontent.com/4211135/130870106-22cb4325-3cfe-4c36-afb4-369c71dc304c.png">
2021-08-25T21:59:35
2021-08-25T22:00:01
{ "+1": 4 }
NONE
vuejs
core
903,247,542
4,412
ghost
I got the issue solved by upgrading the typescript to 4.3.5. I guess there might be some recent changes in Vue which might have changed for the older typescript.
2021-08-22T10:34:48
2021-08-22T10:34:48
{}
NONE
vuejs
core
903,566,630
4,403
smileqwe
I think this behavior should be fixed, because the official versions of vue2 and vue3 do not have this problem, which will lead to differences in the perception of migrated users
2021-08-23T08:46:25
2021-08-23T08:46:25
{ "+1": 1 }
NONE
vuejs
core
904,378,216
4,423
Nisgrak
It give another error, I create a branch for the example, moving the export in the `<script setup>` tag ![image](https://user-images.githubusercontent.com/19597708/130571994-cc001600-97a8-4abe-b4e0-e9b389a3391b.png)
2021-08-24T07:04:39
2021-08-24T07:04:39
{}
NONE
vuejs
core
905,418,615
3,798
pikax
Thanks, maybe the second option might be better (but just a preference)
2021-08-25T11:32:35
2021-08-25T11:32:35
{}
MEMBER
vuejs
core
903,385,852
4,414
linjiahao962889027
> 你这个问题比较简单,Vue 3 的 render function 不再有 `on` 属性了,请仔细查看文档:https://v3.vuejs.org/guide/render-function.html#v-on OK,这个问题解决了,但或许你们需要更新一下你们文档中的搜索功能,当我在搜索框中搜索h函数的时候并没有这么详细的信息。
2021-08-23T02:00:03
2021-08-23T02:00:03
{}
NONE
vuejs
core
903,602,077
4,418
LinusBorg
it's still the same object returned from the watcher's first argument, so it's correct that its not triggering. You might be looking for the `deep: true` option on that watcher.
2021-08-23T09:33:07
2021-08-23T09:33:07
{}
MEMBER
vuejs
core
903,653,416
4,403
LinusBorg
It is a bug, but it's an edge case, really. it only affects you if you pass a function that also has additional properties on it (which is not something people do quite often). A plain function *without additional properties on it* will work just fine.
2021-08-23T10:44:16
2021-08-23T10:44:41
{}
MEMBER
vuejs
core
903,681,410
4,417
posva
@LinusBorg I think he's referring to https://v3.vuejs.org/guide/class-and-style.html#auto-prefixing. For example [this version works](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IGNsYXNzPVwicm93XCI+XG4gICAgPGRpdiBjbGFzcz1cImxhcmdlXCI+XG4gICAgICBMYXJnZVxuICAgIDwvZGl2PlxuICAgIDxkaXYgY2xhc3M9XCJzbWF...
2021-08-23T11:28:38
2021-08-23T11:28:38
{}
MEMBER
vuejs
core
903,685,675
4,417
LinusBorg
Oh. I was honestly unaware we do this in Vue 3. Apologies ^^
2021-08-23T11:35:54
2021-08-23T11:35:54
{}
MEMBER
vuejs
core
904,464,437
4,423
Nisgrak
It seems if I add this to the bottom of the `<script>` tag works, but cant use the interface to declare the prosp inside `<script setup>`, it's need to exist inside the setup, but there can't be exported, strange... ```js export default defineComponent({}); ``` I created the branch `workaround` in the repo with t...
2021-08-24T09:07:42
2021-08-24T09:11:30
{}
NONE
vuejs
core
903,093,931
4,307
baronkoko
@pikax yes, the project had typescript version 4.1.6, from vue create. Аfter updating typescript to the latest version everything works. Thank you very much
2021-08-21T10:08:32
2021-08-21T10:08:32
{ "+1": 2 }
NONE
vuejs
core
903,509,799
4,415
LinusBorg
From the docs: > `updated`: called after the containing component's VNode and the VNodes of its children have updated. When a component updates, the whole render function is run again, and in this re-run, directive hooks are ran again.
2021-08-23T07:20:31
2021-08-23T07:20:31
{}
MEMBER
vuejs
core
905,198,084
4,429
edison1105
@qq974969638 I think it's a very very very very edge case.
2021-08-25T05:36:30
2021-08-25T05:36:30
{ "+1": 1 }
MEMBER
vuejs
core
905,902,079
4,443
posva
A boiled down repro or a test case would be necessary for this to move forward
2021-08-25T21:53:49
2021-08-25T21:53:49
{}
MEMBER
vuejs
core
906,139,207
4,433
ghost
because 'vue-next/packages/vue/package.json' files not includes 'ref-macros.d.ts', so npm store not have this file
2021-08-26T06:43:55
2021-08-26T06:43:55
{}
NONE
vuejs
core
948,663,920
2,457
onemantooo
Is there any workaround for this? Got same problem.
2021-10-21T14:17:12
2021-10-21T14:17:12
{}
NONE
vuejs
core
950,355,803
4,844
LinusBorg
> What about this example? if use reactive object, computed not recalculate `useDataLvl1` returns a reactive object - which will unwrap the message ref. So when you spread this reactive object into a new one in `useDataLvl2`, the new object doesn't get the message ref, only its value at that time. Also: expected.
2021-10-24T16:41:39
2021-10-24T16:41:39
{}
MEMBER
vuejs
core
952,812,254
4,864
criticalsoft
{ "version": "0.2.0", "configurations": [ { "name": "Launch", // "type": "chrome", // "type": "firefox", "type": "pwa-chrome", // "type": "pwa-node", "request": "launch", "url": "http://localhost:8080/", ...
2021-10-27T11:13:40
2021-10-27T11:15:34
{}
NONE
vuejs
core
952,860,799
4,864
LinusBorg
You're welcome to think what you want. All I can say is: I am not *that* well versed with the debugger in VSCode. I sometimes use it to debug in jest tests, but haven't used it with a Vue & vite app yet in the form that you seem to do/want. So I was asking for help with a setup that allows me to reliably reproduc...
2021-10-27T12:11:47
2021-10-27T12:12:36
{ "-1": 1, "heart": 2 }
MEMBER
vuejs
core
951,508,674
4,849
Edge00
@Justineo Thanks for your explanation. I have a little question. According to the specification. Is the design of `v-slots:[slotsName]` follows specification by [Empty attribute syntax](https://html.spec.whatwg.org/multipage/syntax.html#attributes-2) ?
2021-10-26T02:49:02
2021-10-26T02:49:02
{}
NONE
vuejs
core
952,304,196
4,860
LinusBorg
JSX needs a build step one way or another.
2021-10-26T20:36:25
2021-10-26T20:36:25
{}
MEMBER
vuejs
core
952,345,859
4,860
criticalsoft
We Should Load Babel Directlly In The Browser First. And Then Translate Vue JSX Code In The RunTime. Some People Don't Really Need Build Step Actually.
2021-10-26T21:34:23
2021-10-26T21:37:48
{}
NONE
vuejs
core
952,637,404
4,861
posva
You probably figured it out but, as a workaround, pass a new function each time.
2021-10-27T07:56:30
2021-10-27T07:56:30
{}
MEMBER
vuejs
core
952,825,881
4,864
LinusBorg
and do you want to debug the running app at :8080 (Launch)? or rather :3000 (which `dev` command runs on) ? or 5050 (which `serve` runs on)? or the "pwa-node" one (Attach)? Really, please just create a repository that has a command we can run to do exactly what you do. Then you don't have to explain everything and w...
2021-10-27T11:30:50
2021-10-27T11:30:56
{}
MEMBER
vuejs
core
948,215,806
4,667
cyfung1031
> > 这是因为 style 被 parse 成了对象,为的是处理 auto-prefixing。直接写 `background: #18191c url('http://abc.bcd.com/efg.jpeg');` 就可以避免了。 > > 我也是这样处理的,但这样合理么 之前也有人問過類似的問題(好似是Form Input), Evan You也是類似的答法 簡單來說, 在現時的設計下, 同一vue component下的東西, 裡面的state一改, 所有都會跟著改 你能做的就是盡量把靜態不變的抽出成獨立元件 不同vue component之間就不會有這樣的問題
2021-10-21T03:05:57
2021-10-21T03:05:57
{}
NONE
vuejs
core
949,423,924
4,834
Bigfish8
😂Sorry, I Did not notice that you have already committed for this issue. It is my PR #4835. The difference is treatment for mixin url.
2021-10-22T08:57:19
2021-10-22T08:57:19
{ "+1": 1 }
CONTRIBUTOR
vuejs
core
950,332,096
4,844
Fl0pZz
> This behaviour is correct. You pass a non-reactive object, and unwrapping only happens for reactive objects. What about this example? if use reactive object, computed not recalculate https://codesandbox.io/s/laughing-zhukovsky-17qpf?file=/src/App.vue
2021-10-24T14:10:45
2021-10-24T14:10:45
{}
NONE
vuejs
core
950,301,343
4,679
psi-4ward
Looks like I stumbled over this too with VuePress v2. What makes me headaches - it does work on some builds and sometimes not but didnt change any packages. Just rebuild the page. EDIT: I've disabled webpack file-cache and the problem seems gone
2021-10-24T10:46:46
2021-10-24T20:42:51
{}
NONE
vuejs
core
950,733,789
4,845
posva
This behavior seems inconsistent with `v-if`, which can be used as a temporary workaround
2021-10-25T09:46:22
2021-10-25T09:46:22
{}
MEMBER
vuejs
core
950,777,869
4,851
noook
Closing this, I can't reproduce anymore, there was probably something wrong in what I did, I do have the expected behavior now.
2021-10-25T10:33:39
2021-10-25T10:33:39
{}
NONE
vuejs
core
951,514,617
4,849
Justineo
Yes, `v-slots:[slotsName]` is an attribute name.
2021-10-26T03:03:51
2021-10-26T03:03:51
{ "+1": 1 }
MEMBER
vuejs
core
952,353,296
4,860
LinusBorg
Well you can load babel into the browser today. We don't see a big enough use case for this to do any work in that direction, though.
2021-10-26T21:47:45
2021-10-26T21:47:45
{}
MEMBER
vuejs
core
952,905,818
4,864
criticalsoft
Yeah, I Want To Use Visual Studio Code To Debug Vue File. Make It Happen !! It's So Simple To Describe The Problem, It's Basic Feature And It's Broken. And It's Nothing About My Vue Code. Why So Many UnNecessary Request And Words Here ??
2021-10-27T13:03:33
2021-10-27T14:11:13
{}
NONE
vuejs
core
949,356,470
4,830
ShroXd
A component in `<Transition>` should have a root tag so that it can be animated. If you change the comment to `<div>Hello World</div>`, you will see the correct warning message. So maybe we have two works : 1. Fix the error catch when component inside <Transition> don't have a root node and have a comment 2. We do...
2021-10-22T07:18:44
2021-10-22T11:08:25
{}
CONTRIBUTOR
vuejs
core
950,116,812
906
CharlesOkwuagwu
Removed all comments, leave transitions still do not work on components.
2021-10-23T08:29:03
2021-10-23T08:29:03
{}
NONE
vuejs
core
950,640,921
4,847
posva
Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js).
2021-10-25T08:08:37
2021-10-25T08:08:37
{}
MEMBER
vuejs
core
952,809,543
4,864
criticalsoft
This Is Why I Want Live Coding. https://github.com/vuejs/vue-next/issues/4860
2021-10-27T11:10:32
2021-10-27T11:10:32
{}
NONE
vuejs
core
953,016,135
4,841
ManL-T
Yes, I just had to use a v-if. Thank you for your help :-)
2021-10-27T14:59:25
2021-10-27T14:59:25
{}
NONE
vuejs
core
948,297,605
4,827
LinusBorg
This is in principle the same issue as #4294 I'll close this as a duplicate.
2021-10-21T06:27:32
2021-10-21T06:27:32
{}
MEMBER
vuejs
core
948,336,865
838
Eyran
> > 那可以用什么方式替代呢? > > 你可以先一次如何使用emit,我再学习问尤大... https://vueuse.org/core/useVModel/ 我想要的是在父类中使用子组件的方法,emit应该只能在子组件调用父类的方法并传参;
2021-10-21T07:32:26
2021-10-21T07:32:26
{}
NONE
vuejs
core
948,545,904
4,784
zhaozhongyu
> style Yeah i know this, but we are talking about why the code behaves differently when written in different ways, right?
2021-10-21T12:05:23
2021-10-21T12:05:23
{}
NONE
vuejs
core
950,334,550
4,844
Fl0pZz
> This behaviour is correct. You pass a non-reactive object, and unwrapping only happens for reactive objects. In repl `msgWrapper` not reactive, but `msgWrapper.msg` - ref: `<other :msg="msgWrapper.msg" />`
2021-10-24T14:26:22
2021-10-24T14:26:32
{}
NONE
vuejs
core
950,384,482
4,846
LinusBorg
Your project lockfile likely has Vue version locked at 3.1.*, while some component (from an npm package) requires Vue 3.2 (`createElement is only available in Vue 3.2 onwards). Remove the lockfile & packagea and reinstall. If you still have problems, asl for help on chat.vuejs.org.
2021-10-24T19:52:18
2021-10-24T19:52:18
{}
MEMBER
vuejs
core
950,678,441
4,845
ygj6
Please refer to: https://v3.vuejs.org/guide/conditional.html#v-if-vs-v-show
2021-10-25T08:48:11
2021-10-25T08:48:11
{}
MEMBER
vuejs
core
950,726,187
4,848
posva
Use the camelCase version `v-model:msgTest` as a workaround (will not work in HTML templates, e.g. outside vue files) It also looks like the modifiers are being passed as attributes (kebab or camel case): ```htm <div id="app" data-v-app=""><h1>testtttt</h1><h2 msgtestmodifiers="[object Object]">beforetestttttaft...
2021-10-25T09:37:55
2021-10-25T09:40:03
{}
MEMBER
vuejs
core
950,991,986
3,478
posva
For anybody interested in this feature, you should upvote the necessary feature in TypeScript: https://github.com/microsoft/TypeScript/issues/43826
2021-10-25T14:33:29
2021-10-25T14:33:29
{}
MEMBER
vuejs
core
951,935,112
4,858
LinusBorg
posva I've reopened as I misinterpreted the issue, it's about todo's length, not the array itself. i wanna take a second look and close it if it's still not a bug.
2021-10-26T13:23:30
2021-10-26T13:23:30
{ "+1": 2 }
MEMBER
vuejs
core
952,722,190
4,861
LinusBorg
Are we sure this is a bug and was not a design decision?
2021-10-27T09:27:24
2021-10-27T09:27:24
{ "-1": 1 }
MEMBER
vuejs
core
948,382,579
4,828
vue-bot
Hello, thank you for taking time filling this issue! However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic...
2021-10-21T08:32:05
2021-10-21T08:32:05
{}
CONTRIBUTOR
vuejs
core
949,588,082
4,836
posva
This is a nice start but comments should follow https://tsdoc.org/ and use `@example`, `@param` and other directives. I also think adding full examples for all the methods is too much and won't be as practical when hovering definitions. It would be better to keep a short explanation about the functions with links to...
2021-10-22T12:31:53
2021-10-22T12:31:53
{}
MEMBER
vuejs
core
949,600,506
4,836
defaude
If we start adding `@param` tags - what about internal stuff like e.g. `computed`'s `debugOptions` param? And: you're leaning towards having a dedicated, exhaustive documentation in vue-docs and a shorter, more brief version in the in-line docs, right?
2021-10-22T12:48:44
2021-10-22T12:48:44
{}
CONTRIBUTOR
vuejs
core
949,878,561
4,789
flanagankp
@LinusBorg any new thoughts on this?
2021-10-22T18:41:42
2021-10-22T18:41:42
{}
NONE
vuejs
core
950,294,994
4,842
LinusBorg
Duplicate of #4841
2021-10-24T09:58:23
2021-10-24T09:58:23
{}
MEMBER
vuejs
core
951,373,509
4,853
posva
When you say _there is evidence_, people expect you to provide it as well. Have you faced performance issues due to CSS in the Vue applications you develop? Most of the things (if not all) you mention can already be achieved. Some of the ideas you mentioned are interesting but they go beyond vue scope (e.g. contain)
2021-10-25T22:13:20
2021-10-25T22:15:13
{}
MEMBER
vuejs
core
951,827,448
4,855
posva
Thanks but this doesn't look like the real fix. Can you follow https://new-issue.vuejs.org/?repo=vuejs/vue-next and create an issue with a boiled down repro first?
2021-10-26T11:08:30
2021-10-26T11:08:30
{}
MEMBER
vuejs
core
952,723,574
4,861
posva
I'm honestly not sure and I also think it could be a design decision 😬
2021-10-27T09:28:58
2021-10-27T09:28:58
{ "-1": 1 }
MEMBER
vuejs
core
952,987,893
4,866
posva
This is not a valid reproduction but I noticed in your code you should use `markRaw()` in your components if you pass to them to reactive functions like ref or computed; ```js import _HomeView from './HomeView.vue' const HomeView = markRaw(_HomeView) const currentTabComponent = computed(() => { switch (cur...
2021-10-27T14:29:01
2021-10-27T14:29:01
{ "+1": 1, "eyes": 1 }
MEMBER
vuejs
core
947,729,618
4,686
msimpson
@LinusBorg I'd also document the need to hoist `beforeUpdate` or employ some generic slot wrapper in nested situations. For example, the following will not work as the `@vnode-before-update` listener in `app` only reaches down one level. **slot-a** ``` <template> <slot/> </template> ``` **slot-b** ...
2021-10-20T14:34:58
2021-10-22T19:12:54
{}
NONE
vuejs
core
950,227,723
3,989
209
No progress on the problem? I have bug with vue3 and element-plus dropdown. Slot on transition too.
2021-10-23T22:44:06
2021-10-23T22:44:06
{}
NONE
vuejs
core
950,295,281
4,841
LinusBorg
This is expected behaviour as `thread` will be undefined directly after mount, until data has been fetched and the component has updated. Please use chat.vujes.org to ask for help with this, it's one of the most common patterns to use with Vue and remote data.
2021-10-24T10:00:36
2021-10-24T10:00:36
{ "+1": 1 }
MEMBER
vuejs
core
950,249,405
4,783
languanghao
Not work, get `open = ''` ``` withDefaults(defineProps<{ open?: bool }>(), { open: false, }) ``` Work fine, get `open=false` ``` defineProps({ open: { type: Boolean, default: false, } }) ``` Both of these codes works fine in v3.2.19
2021-10-24T02:33:40
2021-10-24T02:42:20
{}
NONE
vuejs
core
952,965,247
4,865
sqal
```vue <span>{{ count + 1 }}</span> ```
2021-10-27T14:05:00
2021-10-27T14:05:00
{}
CONTRIBUTOR
vuejs
core
948,022,426
4,784
furryablack
I guess you can try type like ` fullStyle: "'display: none'" ` The case we use the bind signature - :style instead of a html attr style => it should be the 'string' i.e. "'string'"
2021-10-20T20:44:17
2021-10-20T20:44:32
{}
NONE
vuejs
core
948,252,007
3,930
Traeric
我也遇到这个问题 在rollup.config.js中加上external: ['vue']就好了 因为原始项目中用到了vue但是打包时没有把vue打包上 因此需要引用新项目里面的vue才能正常工作
2021-10-21T04:40:05
2021-10-21T04:40:05
{}
NONE
vuejs
core
949,051,750
4,832
defaude
PR will come tomorrow as it's too late now 😅
2021-10-21T22:33:28
2021-10-21T22:33:28
{}
CONTRIBUTOR
vuejs
core
949,633,919
1,527
eldair
What about adding special variable (like $event in listeners) so that the function doesn't have to be written inline in these cases?
2021-10-22T13:29:58
2021-10-22T13:29:58
{}
NONE
vuejs
core
949,980,101
4,836
defaude
I've shortened the doc blocks a bit and sprinkled some tsdoc goodness, as well. Did not add `@returns`, though, as this basically just repeats the first sentence (in a way). For the dev-only params like `debugOptions`: I've added an empty `@param` tag and this looks nice in intelliJ (doesn't show up at all). But ...
2021-10-22T21:53:45
2021-10-22T21:53:45
{}
CONTRIBUTOR
vuejs
core
952,778,479
4,863
LinusBorg
Please follow Issue Requirements.
2021-10-27T10:32:50
2021-10-27T10:32:50
{}
MEMBER
vuejs
core
952,836,158
4,861
wellrus
At first glance, it looks like vue can't work correctly when using a function reference. For example: two components share a common function. Or, for example, inside one component, one function is used in two different hooks. The reason is in the function: injectHook. Since the __weh function is reused. Using the...
2021-10-27T11:42:08
2021-10-27T11:42:08
{ "+1": 2 }
NONE
vuejs
core
952,844,943
4,864
criticalsoft
Don't Force Every One To Create Repo For Every Bug Report. This Issue Doesn't Need To Do That.
2021-10-27T11:53:00
2021-10-27T12:27:19
{}
NONE
vuejs
core
953,441,517
4,867
caozhong1996
It does make sense if I'm not an obsessive😂
2021-10-28T02:07:31
2021-10-28T02:07:31
{ "laugh": 1 }
CONTRIBUTOR
vuejs
core
948,877,357
2,457
onemantooo
BTW Looks like code from !*** ./node_modules/@vue/reactivity/dist/reactivity.esm-bundler.js ***! isn't minified at all, so i'm not sure this is about Terser. @HcySunYang
2021-10-21T18:08:18
2021-10-21T18:08:18
{}
NONE
vuejs
core
949,465,691
4,831
posva
I would say the bug here is the event listeners not being removed while the element is leaving rather than the ref being unset because the element already fired its unmounted event while it's leaving. Having the ref unset is actually consistent because if the element is leaving it's supposed not to be there anymore (e....
2021-10-22T09:49:27
2021-10-22T09:49:27
{}
MEMBER
vuejs
core
950,332,173
4,843
LinusBorg
You could also make sure to access the dep (`refs.name.value`) before using `await`, i.e. by assigning it's value to a local variable.
2021-10-24T14:11:19
2021-10-24T14:11:19
{ "+1": 1 }
MEMBER
vuejs
core
950,474,676
4,847
Dedicatus546
in `<script>` `import { AddCurrency } from './component/AddCurrency.vue'` -> `import AddCurrency from './views/AddCurrency.vue'`, because you create it in 'views/AddCurrency.vue' and you should use `import AddCurrency ...` instead of `import { AddCurrency } ...` and the `AddCurrency` component can work. it see...
2021-10-25T02:35:47
2021-10-25T06:00:28
{}
NONE
vuejs
core
951,654,874
4,854
posva
Works fine on Firefox 94.
2021-10-26T07:51:35
2021-10-26T07:51:35
{ "+1": 1 }
MEMBER