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 | 998,870,021 | 5,147 | posva | This is actually because of how pug transforms the expression you give to it:
```pug
div
div(:title='row["item2"]') {{ row["item2"] }}
input(v-model='row["item2"]')
```
becomes
```html
<div>
<div :title="row["item2"]">{{ row["item2"] }}</div><input v-model="row["item2"]" />
<... | 2021-12-21T15:26:36 | 2021-12-21T15:26:36 | {} | MEMBER |
vuejs | core | 999,389,438 | 5,150 | posva | This is the browser setting it as by spec, you can only use numbers: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/li#attr-value | 2021-12-22T08:38:31 | 2021-12-22T08:38:45 | {} | MEMBER |
vuejs | core | 1,000,000,315 | 4,866 | yjj5855 | @651778286 不只有refs有问题 , 我在setup script 中 `const _bill = inject('bill')` , 在script 中 也获取不到.
都是开发环境正常, 发布环境undefined
不知道是不是vite的问题 我也提到vite了 https://github.com/vitejs/vite/issues/6244 | 2021-12-23T02:38:20 | 2021-12-23T06:53:56 | {} | NONE |
vuejs | core | 1,000,123,743 | 5,105 | Riant | @caozhong1996
> Note: it's very similar to #4339
Yes, there are so many developers need and talk about this feature, and it is strange there is no progress so far. and like what you said, it is smallest, this pr or even a half of this pr is enough.
> it seems that we can control cache via key now
Did you m... | 2021-12-23T08:16:43 | 2021-12-23T08:34:54 | {
"+1": 1
} | NONE |
vuejs | core | 1,000,209,347 | 5,156 | way2ex | > If you are not using TS, you can actually import the props/emits definitions and share them, because they are runtime objects. Vue doesn't need to process them in SFCs.
>
> When using TS-based declarations, currently it doesn't support importing external types/interfaces, but it's on the roadmap. I believe there i... | 2021-12-23T10:43:51 | 2021-12-23T10:43:51 | {} | NONE |
vuejs | core | 1,000,564,740 | 5,155 | edimitchel | Thank you for your anwser.
Here the line: https://github.com/vuejs/repl/blob/0c920ea68df0dda814ebf10b3747e43ade928cf7/src/output/srcdoc.html#L107
If someone find something to do.. | 2021-12-23T23:36:19 | 2021-12-23T23:36:19 | {} | NONE |
vuejs | core | 1,002,922,391 | 4,256 | wuliupo | It is very cool in Vue 3.1+ by `setup` script:
```vue
<template>
<div>{{title}}</div>
</template>
<script lang="ts" setup>
import { ref } from 'vue';
const title = ref('Hello World');
</script>
```
| 2021-12-30T08:24:45 | 2021-12-30T08:24:45 | {} | NONE |
vuejs | core | 1,000,609,478 | 5,105 | huangqian0310 | @caozhong1996
> it seems that we can control cache via key now
Current 3.2 In the 26 version, KeepAlive's exclude still does not support key. When it comes to the effective process of exclude, he will still match the routing name, or is it using other ways to make key control the cache of routing？
| 2021-12-24T02:08:54 | 2021-12-24T02:08:54 | {} | NONE |
vuejs | core | 1,000,836,047 | 5,073 | Chenshyboy | #5165, it can fix it, I add a test case to reappearance the situation
this problem is related to cache of keep-alive | 2021-12-24T13:16:20 | 2021-12-24T13:16:20 | {} | NONE |
vuejs | core | 1,000,980,923 | 5,170 | SunsetFeng | @caozhong1996 | 2021-12-25T06:26:39 | 2021-12-25T06:26:39 | {} | NONE |
vuejs | core | 1,001,169,099 | 5,169 | yjj5855 | Why the development environment can get properties, but not after packaging. And there is no prohibition in the documentation to use 2 ways at the same time. | 2021-12-26T12:19:57 | 2021-12-26T12:19:57 | {} | NONE |
vuejs | core | 1,002,250,967 | 5,179 | LinusBorg | https://v3.vuejs.org/api/sfc-script-setup.html#defineexpose | 2021-12-28T19:28:10 | 2021-12-28T19:28:10 | {} | MEMBER |
vuejs | core | 1,002,389,254 | 5,138 | dsonet | Is this bring better performance and lower the memory usage? | 2021-12-29T04:13:19 | 2021-12-29T04:13:19 | {} | CONTRIBUTOR |
vuejs | core | 1,002,966,470 | 5,186 | LinusBorg | That's expected. you *first* change `currentValue`, *then* the component re-renders, and *then* the destroy callback gets called.
If you need help in solving this differently: chat.vuejs.org | 2021-12-30T10:29:06 | 2021-12-30T10:29:06 | {} | MEMBER |
vuejs | core | 999,008,804 | 5,142 | ycw | > This was intentionally left out and discussed in the relevant RFCs
@posva It would be great if you provide a link to the relevant discussion/rfcs. | 2021-12-21T18:41:42 | 2021-12-21T18:41:42 | {} | NONE |
vuejs | core | 1,000,679,482 | 5,126 | zhangyuang | In addition, there must wrap teleport node in a div and the `to` props cannot be `body`
```js
import { defineComponent, Teleport } from 'vue'
export default defineComponent({
setup() {
const teleport = '#pop'
return () => (
<div>
<Teleport to={teleport}>
<div> yes </div>
... | 2021-12-24T06:28:45 | 2021-12-24T07:55:27 | {} | CONTRIBUTOR |
vuejs | core | 1,000,779,129 | 5,163 | Pentadome | @LinusBorg Okay this is really weird. Try removing the `: any` in the isCollapse validator and you will get the bug. | 2021-12-24T10:35:34 | 2021-12-24T10:36:00 | {} | CONTRIBUTOR |
vuejs | core | 1,000,785,440 | 5,163 | LinusBorg | I won't type out the whole example by hand again.
If annotating the parameter solves the issue maybe we should document that. | 2021-12-24T10:49:46 | 2021-12-24T10:49:46 | {} | MEMBER |
vuejs | core | 1,000,980,881 | 5,170 | SunsetFeng | I create a new project for testing. Created by CLI(version:4.5.15) with vue3 and typescript. Add a function name of doAction in App.vue. Here is the repo link [vue-test](https://github.com/SunsetFeng/vue-test.git). And this is my screenshot.
` instead and keep only one version of the component: the composition or the setup version.
You can still access the ref through `this.$refs.ref_form` though | 2021-12-26T09:35:14 | 2021-12-26T09:35:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,001,585,158 | 5,171 | builder555 | i'm still not sure why this bug report is marked as closed? was it fixed? | 2021-12-27T14:06:37 | 2021-12-27T14:06:37 | {} | NONE |
vuejs | core | 1,000,005,018 | 5,009 | candy-Tong | May I ask when to fix this problem？
Is it because my solution still has some problem and you need more time to think about it？
| 2021-12-23T02:53:34 | 2021-12-23T02:53:34 | {} | NONE |
vuejs | core | 1,000,424,804 | 5,163 | LinusBorg | Can't reproduce. Please follow the issue guidelines and provide a runnable reproduction.
Hint: As this issue is with our IDE, provide additional details about your exact IDE setup, most specifically the Vue plugin(s) you are using.
<img width="658" alt="Bildschirmfoto 2021-12-23 um 17 57 09" src="https://user-ima... | 2021-12-23T16:58:30 | 2021-12-23T16:58:30 | {} | MEMBER |
vuejs | core | 1,001,608,676 | 5,171 | builder555 | @caozhong1996 if you try installing sass from one of the predefined settings (no manual npm install steps), the same error happens. | 2021-12-27T15:05:05 | 2021-12-27T15:05:05 | {} | NONE |
vuejs | core | 1,001,881,161 | 5,131 | zhangenming | > You can only commit the file you intended to change and ignore the others.
What do you mean by others files?
So what am I supposed to do now
> The benefit brought by the PR should be worth the effort we put into reviewing it.
sorry
| 2021-12-28T05:47:08 | 2021-12-28T06:55:55 | {} | CONTRIBUTOR |
vuejs | core | 999,309,115 | 5,147 | Lsnsh | I found that my steps to reproduce cannot be reproduced normally because of the cache.
The first build will report an error, and the second build will not report an error.
I updated the **steps to reproduce**:
- <del>Edit `item2` in `src/components/Case1.vue`, then save the changes.</del>
- Uncomment `input(v... | 2021-12-22T06:01:33 | 2021-12-22T06:01:33 | {} | NONE |
vuejs | core | 999,645,871 | 5,151 | LinusBorg | This is a tricky one, feels like a definition gap. If we change the behavior now, we risk breaking existing code. We might still want to if we decide the proposed behavior was the originally intended one anyway.
For now, one could work around this like so:
```js
const count = ref(0);
watch(count, (value, oldV... | 2021-12-22T15:09:21 | 2021-12-22T15:09:21 | {} | MEMBER |
vuejs | core | 1,000,321,472 | 5,157 | 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).
—-
You should probably remove the key attribute from... | 2021-12-23T13:55:33 | 2021-12-23T13:55:33 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,001,168,747 | 5,168 | posva | Right, but that bar component shouldn’t go in the transition group, it should go in a transition and then it works | 2021-12-26T12:16:47 | 2021-12-26T12:16:47 | {} | MEMBER |
vuejs | core | 1,001,650,821 | 5,174 | gnuletik | Thanks @posva for the fast feedback!
I was able to create a wrapper like that :
```vue
<!-- SuspenseWrapper.vue -->
<template>
<div v-if="error">
{{ error }}
</div>
<suspense v-else>
<template #default>
<slot />
</template>
<template #fallback>
<LoadingIcon />
... | 2021-12-27T16:44:17 | 2021-12-27T17:08:48 | {} | NONE |
vuejs | core | 1,001,869,435 | 5,131 | Justineo | You can only commit the file you intended to change and ignore the others. The benefit brought by the PR should be worth the effort we put into reviewing it. | 2021-12-28T04:57:47 | 2021-12-28T06:55:48 | {} | MEMBER |
vuejs | core | 1,001,927,834 | 5,175 | pomeloneo | operation error 😂
close this pr
open the [pr](https://github.com/vuejs/vue-next/pull/5176) | 2021-12-28T08:07:59 | 2021-12-28T08:11:28 | {} | NONE |
vuejs | core | 998,710,153 | 5,146 | posva | You can use `getCurrentInstance()` to detect if you can call `onMounted()` and other composition api functions. Maybe you are putting things inside of the function returned in setup while they should be outside:
```js
setup() {
return () => {
const data = ref() // this should go up
// ... return jsx
... | 2021-12-21T11:41:22 | 2021-12-21T11:41:22 | {} | MEMBER |
vuejs | core | 1,001,035,700 | 5,171 | builder555 | @posva this _is_ a bug report | 2021-12-25T15:23:15 | 2021-12-25T15:23:15 | {} | NONE |
vuejs | core | 1,001,888,293 | 5,131 | zhangenming | > Current changes seems to be fine.
I didn't do anything changes, github bug??
| 2021-12-28T06:14:36 | 2021-12-28T06:56:18 | {} | CONTRIBUTOR |
vuejs | core | 1,002,130,316 | 5,178 | caozhong1996 | #5105 #4339
When the data is huge, it does really necessary, there are two linked PR.
当数据量巨大的时候，这确实很有必要，已经有两个相关的提交了
| 2021-12-28T14:24:47 | 2021-12-28T14:24:47 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,002,869,184 | 4,189 | osi-oswald | I second the request of @mVIII, to have a `customReactive` analog to `customRef` API. But as you said @posva, I guess going through an RFC is the right way. Since I already wrote my issue (over the last 2 hours until I found this issue... 🙈), I'll just post it here instead:
### What problem does this feature solve?... | 2021-12-30T04:30:47 | 2021-12-30T04:30:47 | {} | NONE |
vuejs | core | 1,002,947,715 | 5,184 | posva | Hello, make sure to always provide a reproduction that follows the instructions at https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro.
Open a new issue with a reproduction that follows those instructions if you manage to create a boiled down reproduction.
Remember to use the [forum](http://forum.vuejs.org... | 2021-12-30T09:38:12 | 2021-12-30T09:38:12 | {} | MEMBER |
vuejs | core | 1,019,484,133 | 5,301 | Oleksii14 | According to the changes in v3.2.26, maybe you may know what could cause this? `vue-tsc` didn't report any TS issues while using v.3.2.25 and after v3.2.26 is installed, I get those TS errors from `vue-tsc` | 2022-01-23T13:19:55 | 2022-01-23T13:19:55 | {} | NONE |
vuejs | core | 1,019,737,781 | 2,460 | flozero | I am not able to make simple custom event to work personally... if the prop is an object | 2022-01-24T05:34:31 | 2022-01-24T05:44:35 | {} | NONE |
vuejs | core | 1,020,544,017 | 5,319 | twickstrom | > Declare it as as prop `onDelete: Function`. You will be able to check for existence, and still use `emit('delete')`
>
> duplicate - #5220
Agreed, there are a few work arounds. However I feel that lacking a way to check what is an allowed emit, per the documentation, especially as it pertains to more complex exa... | 2022-01-24T21:03:36 | 2022-01-24T21:03:36 | {} | NONE |
vuejs | core | 1,022,479,064 | 4,566 | markhalliwell | > And on top, the migration guide explains that all Compat flags that need to be set in the compiler Options are prefixed with COMPILER_*
Yes, however, it is not explicit that _only_ the flags that are prefixed with `COMPILER_` will work in the build setup and not the other flags that are not prefixed with it. This ... | 2022-01-26T18:33:34 | 2022-01-26T18:33:34 | {
"+1": 3
} | NONE |
vuejs | core | 1,023,205,866 | 5,322 | LinusBorg | Seems we indeed have an inconsistency here. the code responsible for remoiving style properties relies on `null` being set for undefined values, which does happen when the style definition is wrapped in `normalizeStyle`.
```js
_createElementVNode("h1", {
style: _normalizeStyle({color: x.value })
}, " co... | 2022-01-27T13:22:48 | 2022-01-27T13:22:48 | {} | MEMBER |
vuejs | core | 1,021,393,430 | 4,314 | gnuletik | @jsbaguette, you can copy the `apiCustomElement.ts` file from my [PR](https://github.com/vuejs/core/pull/4404) if you need it.
You just need to replace an import in this file :
```diff
- import { hydrate, render } from '.'
+ import { hydrate, render } from '@vue/runtime-dom'
```
And install an extra dependen... | 2022-01-25T16:48:20 | 2022-01-27T13:42:04 | {
"rocket": 14
} | NONE |
vuejs | core | 1,023,317,277 | 5,031 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 35f59b3c2274711cdc0372a4e6258a37b4cd875e
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61f2b6e207303d000774e57f](https://app.netlify.com/sites/vuejs-coverage/deploys/61f2b6e207303d000774e57f)
😎 Browse th... | 2022-01-27T15:14:46 | 2022-01-27T15:20:50 | {} | NONE |
vuejs | core | 1,023,642,534 | 5,331 | LinusBorg | I'm not sure I understand the question. | 2022-01-27T21:11:38 | 2022-01-27T21:11:38 | {} | MEMBER |
vuejs | core | 1,019,740,621 | 2,343 | flozero | the .prop doesnt send the data on update...
EDIT: it work if I am spreading the object inside { ...myObj } that sounds like a non normal behavior in vue3 at least with reactive | 2022-01-24T05:42:27 | 2022-01-24T05:47:23 | {} | NONE |
vuejs | core | 1,020,126,769 | 5,313 | flozero | Thank you linus. But if I do that. For other framework like angular or react. They will have to install vue3 right ? Cause it will not work in this case if they don't. Same for vue2 project | 2022-01-24T13:56:55 | 2022-01-24T14:00:55 | {} | NONE |
vuejs | core | 1,020,199,804 | 5,314 | LinusBorg | Yes, I think so. React uses its own synthetic event system which, as far as I understand, doesn't work seamlessly with CustomEvents | 2022-01-24T15:09:04 | 2022-01-24T15:09:04 | {} | MEMBER |
vuejs | core | 1,020,405,150 | 5,301 | LinusBorg | Typing of these global properties by third party packages happens by augmenting the `CustomComponentProperties` interface, see for example vue-router [here](https://github.com/vuejs/router/blob/main/src/globalExtensions.ts#L48-L58)
But The changes between .25 and .26 don't affect this interface, so it's really hard ... | 2022-01-24T18:22:38 | 2022-01-24T18:22:38 | {} | MEMBER |
vuejs | core | 1,022,552,548 | 5,332 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 9bd848505a71f02d9ce0419722daaf0bf5422fc7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f1a7f4c12b8600077f2909](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f... | 2022-01-26T19:58:49 | 2022-01-26T20:00:26 | {} | NONE |
vuejs | core | 1,023,173,349 | 5,312 | Moonlight63 | After some further testing this behavior seems to be coming from the components definition file that is automatically generated as part of the vitesse template. This doesn't make it a vitesse specific issue as I was able to recreate the bug on a vue-cli project as well. It seems that when a vue file containing this pat... | 2022-01-27T12:50:02 | 2022-01-27T12:50:02 | {} | NONE |
vuejs | core | 1,023,188,492 | 5,322 | hit12369 | > This seems to be just how CSS variables work:
>
> ```js
> $0.style.setProperty('--color', undefined) // sets the string undefined
> ```
While it is true, setting it as undefined removes the property in vue 2.
vue2 example: https://jsfiddle.net/zb1x79m0/
Also it would ensure consistency with non variabl... | 2022-01-27T13:08:58 | 2022-01-27T13:22:43 | {} | NONE |
vuejs | core | 1,023,990,768 | 5,337 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: e87c843bf53f8aeeddec1b9f2a28ebe68f63cdea
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f3a906ded4920008dfcab7](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f... | 2022-01-28T08:27:55 | 2022-01-28T08:28:45 | {} | NONE |
vuejs | core | 1,019,483,093 | 5,165 | AlexDaniel | Found this PR because yes, indeed, HMR is broken if I add keep-alive on the router-view.
That's the error:
I haven't tried applying the fix proposed in this PR, but 🤞🏼 that it's about the same issue :... | 2022-01-23T13:14:25 | 2022-01-23T13:14:25 | {} | NONE |
vuejs | core | 1,019,647,896 | 5,311 | yyx990803 | `RendererOptions` is a type, not an API. | 2022-01-24T02:11:27 | 2022-01-24T02:11:27 | {} | MEMBER |
vuejs | core | 1,020,170,408 | 5,313 | flozero | Agree with you. For vue2 I am going to have an issue no ? how can I an make both working good ? | 2022-01-24T14:40:49 | 2022-01-24T14:40:49 | {} | NONE |
vuejs | core | 1,021,772,293 | 5,326 | ygj6 | I think it's a duplicate of #5280. | 2022-01-26T01:35:26 | 2022-01-26T01:35:26 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,024,435,483 | 5,331 | posva | Given how easy it is to create your own composable and how much of an edge case this is, I don't thin it should be added to vue core. It could maybe be in vueuse if there is enough interest in it though | 2022-01-28T17:17:05 | 2022-01-28T17:17:05 | {} | MEMBER |
vuejs | core | 1,024,436,898 | 5,335 | posva | I would say using `markRaw()` is expected: https://v3.vuejs.org/api/basic-reactivity.html#markraw | 2022-01-28T17:18:46 | 2022-01-28T17:18:46 | {} | MEMBER |
vuejs | core | 1,024,620,556 | 5,331 | Razi91 | Okay, I thought doing it in core would be better, but you are right, it's easy to implement manually, thanks @LinusBorg | 2022-01-28T20:42:17 | 2022-01-28T20:42:17 | {} | NONE |
vuejs | core | 1,020,751,826 | 5,180 | BrunoRicci | > My bad, you were right this was environmental. Turned out the event default was being prevented in the unhandledrejection listener with `event.preventDefault()`
>
> Sorry for the noise, will leave this up in case someone else stumbles upon a similar issue.
I'm facing the same issue and cannot seem to solve it... | 2022-01-25T02:38:54 | 2022-01-25T02:39:21 | {} | NONE |
vuejs | core | 1,021,513,186 | 5,328 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 6dff8a25a61243e0c26c258ddedfa65debb0228e
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61f04cc942474a000785555c](https://app.netlify.com/sites/vuejs-coverage/deploys/61f04cc942474a000785555c)
😎 Browse th... | 2022-01-25T19:03:40 | 2022-01-25T19:23:35 | {} | NONE |
vuejs | core | 1,021,948,067 | 813 | mkidsc1603 | This issue should be took a look again.
Now , It is like tol must define specific props & event (include common e.g. class、style、click ...)
Generally, some strange situation occured when I encapsulate other UI Framework component 😢 | 2022-01-26T07:53:11 | 2022-01-26T07:53:11 | {} | NONE |
vuejs | core | 1,019,797,672 | 5,313 | LinusBorg | Your issue here is that you have two local copies of vue in this repository:
* one in the main `/node_modules`, which will be detected for files from /src (or /dist)
* one in `/examples/vue3-playground/node_modules`, which will be detected for files from /examples/vue3-playground/src
Since Vue relies on a couple... | 2022-01-24T07:30:50 | 2022-01-24T07:30:50 | {} | MEMBER |
vuejs | core | 1,020,537,772 | 5,301 | Oleksii14 | Will try that. Thanks for your reply | 2022-01-24T20:54:57 | 2022-01-24T20:54:57 | {} | NONE |
vuejs | core | 1,023,246,148 | 5,322 | hit12369 | There's a problem even with `normalizeStyle` where initial render sets the property as `undefined` but any rerender correctly removes the property.
Playground link: [sfc.vuejs.org](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aDEgOnN0eWxlPVwieyctLWNvbG9yJzogeH1cIj5QYXJlbnQ8L2gxPlxuICA8YnV0dG9uIEBjbGlja... | 2022-01-27T14:06:36 | 2022-01-27T14:06:36 | {
"+1": 1
} | NONE |
vuejs | core | 1,024,241,640 | 5,182 | xxSkyy | Can it be merged? It's really essential problem with SSR | 2022-01-28T13:48:29 | 2022-01-28T13:48:29 | {} | NONE |
vuejs | core | 1,019,298,606 | 5,309 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 8bef1799965cd562020253a5cc071bcaa4f87aa2
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61ee88a0a702ba0007a2c4c6](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61e... | 2022-01-22T16:03:52 | 2022-01-24T11:09:18 | {} | NONE |
vuejs | core | 1,019,298,607 | 5,309 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 8bef1799965cd562020253a5cc071bcaa4f87aa2
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61ee88a06e9d6d00084b0964](https://app.netlify.com/sites/vue-sfc-playground/deploys/61ee88a06e9d6d00084b0964)
... | 2022-01-22T16:03:53 | 2022-01-24T11:10:34 | {} | NONE |
vuejs | core | 1,020,756,772 | 5,180 | BrunoRicci | > > My bad, you were right this was environmental. Turned out the event default was being prevented in the unhandledrejection listener with `event.preventDefault()`
> > Sorry for the noise, will leave this up in case someone else stumbles upon a similar issue.
>
> I'm facing the same issue and cannot seem to solve ... | 2022-01-25T02:50:14 | 2022-01-25T02:50:14 | {} | NONE |
vuejs | core | 1,021,844,389 | 5,329 | LinusBorg | ```ts
defineProps<{
num?: number
}>()
``` | 2022-01-26T04:11:39 | 2022-01-26T04:11:39 | {} | MEMBER |
vuejs | core | 1,022,367,656 | 5,301 | Oleksii14 | @LinusBorg @yyx990803 it turned out to be a problem with `pnpm`. We migrated to this package manager recently and we had no issues until now. When we update dependencies (not only Vue as it turned out
to be) to their newer versions, there appear the errors from `vue-tsc` while running the build command with Vite. I d... | 2022-01-26T16:26:54 | 2022-01-26T16:27:25 | {} | NONE |
vuejs | core | 1,022,552,556 | 5,332 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 9bd848505a71f02d9ce0419722daaf0bf5422fc7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61f1a7f40fa51d0008ece868](https://app.netlify.com/sites/vue-sfc-playground/deploys/61f1a7f40fa51d0008ece868)
... | 2022-01-26T19:58:50 | 2022-01-26T20:03:00 | {} | NONE |
vuejs | core | 1,022,552,543 | 5,332 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 9bd848505a71f02d9ce0419722daaf0bf5422fc7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61f1a7f4e7d802000787d7d9](https://app.netlify.com/sites/vuejs-coverage/deploys/61f1a7f4e7d802000787d7d9)
😎 Browse th... | 2022-01-26T19:58:49 | 2022-01-26T20:05:02 | {} | NONE |
vuejs | core | 1,022,844,775 | 5,320 | AaronBeaudoin | Hi all. This is a real weird one and I've tried to figure out the cause for this strange behavior but I've had pretty much no success. Would someone with more experience be willing to step in and take a look? Thanks! | 2022-01-27T04:47:07 | 2022-01-27T04:47:07 | {} | NONE |
vuejs | core | 1,023,948,137 | 1,033 | wadadanet | I deleted the `@storybook/testing-vue3": "^0.0.1` and the error stopped.
Removing `node_modules/@storybook/testing-vue3/` had the same effect. | 2022-01-28T07:16:45 | 2022-01-28T07:16:45 | {} | NONE |
vuejs | core | 1,019,481,718 | 5,301 | Oleksii14 | from v3.2.25. It seems that some type-related changes caused that. Unfortunately, I could not reproduce it within a new Vite project. All seems to work fine from scratch.
From the console in the current project, I can see that the errors are all about root Vue instance properties: $t, $route, etc | 2022-01-23T13:06:42 | 2022-01-23T13:18:13 | {} | NONE |
vuejs | core | 1,019,800,656 | 5,314 | LinusBorg | defineEmits works for for me when I do this:
```js
const emit = defineEmits(['customme'])
const handleClick = () => {
emit('customme', {
test: 'information'
})
}
```
![Kapture 2022-01-24 at 08 36 31](https://user-images.githubusercontent.com/1444526/150740712-49c24eb0-146b-4784-a19b-f20458e0241e.gi... | 2022-01-24T07:36:56 | 2022-01-24T07:36:56 | {} | MEMBER |
vuejs | core | 1,019,811,932 | 5,313 | LinusBorg | Ah, still the same reason: 2 copies of Vue. But the real culprit was that you didn't exclude vue from the web components bundle.
You need to externalize Vue so that in the consuming app, the same copy of Vue is used for the app and the Vue web component from your lib.
```js
build: {
lib: {
entry: pat... | 2022-01-24T07:56:36 | 2022-01-24T07:56:59 | {} | MEMBER |
vuejs | core | 1,021,367,264 | 5,325 | LinusBorg | We likely shouldn't expand the props validation API in this way as it brings a lot of complexity, in my opinion. this can be solved in user land. | 2022-01-25T16:24:18 | 2022-01-25T16:24:18 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,022,070,559 | 813 | SomeoneIsWorking | I'm changing my statement on this issue. There is no problem regarding the behavior. If you want to omit specific events you can use `inheritAttrs: false` combined with `v-bind="omit($attrs, 'onClick')` for example (`omit` is a lodash function here)
People struggling with it most likely don't know what they are doing ... | 2022-01-26T10:33:57 | 2022-01-26T10:33:57 | {} | NONE |
vuejs | core | 1,022,135,533 | 5,331 | LinusBorg | You can build that yourself in like 3 lines of code.
```js
const computedWithPrev = (cb) => {
let previous
return computed(() => previous = cb(previous))
}
```
Usage
```js
const count = ref(23);
const result = computedWithPrev((previous) => {
const digit = count.value % 10;
if (previous.digit == d... | 2022-01-26T12:03:37 | 2022-01-27T07:38:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,023,354,495 | 5,334 | LinusBorg | Hello @OrhanOzkercin
Thank your for your interest in this project.
However, your issue is a usage/support question, and the issue tracker is reserved exclusively for bug reports and feature requests (as outlined in our [Contributing Guide](https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md)).
We en... | 2022-01-27T15:46:44 | 2022-01-27T15:47:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,019,539,069 | 5,301 | Oleksii14 | @LinusBorg the code base is quite large and the amount of errors is huge - more than 1700 items. Maybe all of them are about `$t` function call and a few about `$route` reference. See the attached screenshot. | 2022-01-23T18:17:16 | 2022-01-23T18:17:16 | {} | NONE |
vuejs | core | 1,021,398,647 | 5,324 | adamdehaven | @LinusBorg thanks for the quick response!
> All extra arguments passed to `$emit()` after the event name will be forwarded to the listener. For example, with `$emit('foo', 1, 2, 3)` the listener function will receive three arguments.
~This appears to be missing from the live version of the docs 🤷🏼♂️ -- I've n... | 2022-01-25T16:53:44 | 2022-01-25T17:07:19 | {} | NONE |
vuejs | core | 1,021,513,192 | 5,328 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 6dff8a25a61243e0c26c258ddedfa65debb0228e
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61f04cc93b17010008fa3515](https://app.netlify.com/sites/vue-sfc-playground/deploys/61f04cc93b17010008fa3515)
... | 2022-01-25T19:03:40 | 2022-01-25T19:20:01 | {} | NONE |
vuejs | core | 1,021,837,299 | 5,252 | npmrun | M1,M2并没有被缓存，你在m2加一个输入框，输入一点东西，从A切换过去M2，输入框并没有东西，那个activated应该是M界面触发的,因为M被缓存了，如果把M去掉，就只会触发created了， 子路由也需要加keepalive才能被缓存 | 2022-01-26T03:54:37 | 2022-01-26T03:54:37 | {} | NONE |
vuejs | core | 1,019,970,973 | 4,294 | Shinigami92 | I'm now also affected by this issue and trying to workaround for 2 hours now without luck :slightly_frowning_face:
I want to extend a quasar QBtn like so
```ts
<script setup lang="ts">
import type { QBtnProps } from 'quasar';
defineProps<QBtnProps>();
</script>
<template lang="pug">
QBtn(
v-bind="$a... | 2022-01-24T10:58:26 | 2022-01-24T10:58:26 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 1,019,996,086 | 4,294 | Shinigami92 | > How about:
>
> ```js
> <script setup lang="ts">
> import { QBtn } from 'quasar';
>
> defineProps(QBtn.props);
> </script>
> ```
Sadly that doesn't help at all, due to `QBtn.props` is of type `any` | 2022-01-24T11:24:24 | 2022-01-24T11:24:24 | {} | CONTRIBUTOR |
vuejs | core | 1,020,167,502 | 5,313 | LinusBorg | Yes. Which, in my opinion isn't much of a problem. Rather can be an advantage if the consumers might choose to use another web component built on Vue 3 from another vendor.
If it is a problem though for you or your consumers tough, you could do 2 builds, one which includes Vue 3 and one which doesn't. | 2022-01-24T14:37:55 | 2022-01-24T14:38:04 | {} | MEMBER |
vuejs | core | 1,020,535,738 | 5,319 | sqal | Declare it as as prop `onDelete: Function`. You will be able to check for existence, and still use `emit('delete')`
duplicate - https://github.com/vuejs/core/issues/5220
[example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cblx0aW1wb3J0IEJhZGdlIGZyb20gJy4vQmFkZ2UudnVlJ1xuICBjb25zdCB3aW4gPSB3aW5kb3dc... | 2022-01-24T20:51:59 | 2022-01-24T21:03:14 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 1,020,640,617 | 5,319 | lidlanca | make your case in the RFC discussion, if it wasn't already made.
https://github.com/vuejs/rfcs/discussions/397
and don't hold your breath | 2022-01-24T23:08:26 | 2022-01-24T23:11:18 | {} | CONTRIBUTOR |
vuejs | core | 1,022,291,303 | 4,566 | markhalliwell | Thank you @LinusBorg! I have been trying to figure out why this wasn't working. The only thing I will add to the above solution is some more details around where to put `INSTANCE_LISTENERS`. I attempted to add this to `compilerOptions` in `vue.config.js` prior to finding this issue and it did not seem to work at all. I... | 2022-01-26T15:11:08 | 2022-01-26T15:11:08 | {} | NONE |
vuejs | core | 1,024,510,101 | 4,733 | mika76 | @posva this helper function does not work any more...
I would like to add my vote to the request of having a built in function which does this, or a dictionary on the slots object or something. Currently it's impossible to figure out exactly what is an empty slot and what isn't.
Hmm it seems like it's actually a ... | 2022-01-28T18:48:35 | 2022-01-28T19:00:52 | {} | NONE |
vuejs | core | 1,019,802,104 | 5,313 | LinusBorg | On second look I need to reopen, made a mistake and need to re-evaluate | 2022-01-24T07:39:41 | 2022-01-24T07:39:41 | {} | MEMBER |
vuejs | core | 1,019,980,439 | 4,294 | LinusBorg | How about:
```js
<script setup lang="ts">
import { QBtn } from 'quasar';
defineProps(QBtn.props);
</script>
``` | 2022-01-24T11:08:21 | 2022-01-24T11:08:21 | {} | MEMBER |
vuejs | core | 1,019,298,614 | 5,309 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 8bef1799965cd562020253a5cc071bcaa4f87aa2
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61ee88a0d784c600083c45ea](https://app.netlify.com/sites/vuejs-coverage/deploys/61ee88a0d784c600083c45ea)
😎 Browse th... | 2022-01-22T16:03:55 | 2022-01-24T11:14:22 | {} | NONE |
vuejs | core | 1,020,742,674 | 5,321 | ygj6 | This is because, in a reactive array, the value of the object will be set to reactive.
```ts
const store = {
test: ref('test'),
};
type Store = typeof store;
const initialValues = [store];
console.log('store: ',isReactive(store)) //false
const list = ref(initialValues);
console.log('ref([store]): ... | 2022-01-25T02:18:50 | 2022-01-25T02:18:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,022,276,645 | 5,331 | rgaudy | > If computed's getter returns an object, every time it's recalculated it will return a new object. It could be optimized if we would be able to get previously calculated value and in the case when nothing changes, we could just return the previous value without triggering watchers and other effects.
>
A problem w... | 2022-01-26T14:56:45 | 2022-01-26T14:56:45 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.