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 | 939,212,510 | 4,299 | zhangshichun | 同样的问题；
发现当同时满足以下三种情况时，可能出现一个vue3的bug:
1. 使用setup标签写法
2. 在模板中给某标签定义了ref属性，如：`<div ref="root" />`
3. 在<script setup> 中没有定义 const root = ref(xxx);
这个问题最讨厌的一点，就是本地开发环境ok，打包后才异常；
| 2021-10-09T03:00:46 | 2021-10-09T22:37:47 | {} | NONE |
vuejs | core | 939,597,516 | 4,779 | edison1105 | did you enable [__VUE_PROD_DEVTOOLS__](https://github.com/vuejs/vue-next/tree/master/packages/vue#bundler-build-feature-flags)? | 2021-10-11T01:15:10 | 2021-10-11T01:15:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 939,627,565 | 4,781 | yyx990803 | Thanks, but I think `watch` should align with Options API and be configured mainly via options.
In addition, `immediate` watch is a rare use case - in most cases you should use `watchEffect` instead of an immediate watcher. | 2021-10-11T02:28:03 | 2021-10-11T02:28:03 | {} | MEMBER |
vuejs | core | 939,632,717 | 4,779 | ygj6 | @StarHosea I used the version you provided to create a demo project, but it did not reproduce.
```
vue 3.2.12
vueDevtools: v6.0.0-beta.19
vite: 2.5.10
@vitejs/plugin-vue: 1.9.0
```
| 2021-10-11T02:44:37 | 2021-10-11T02:44:37 | {} | MEMBER |
vuejs | core | 939,972,146 | 4,247 | Bigfish8 | @cyfung1031 there is difference between `mergeProps` function call with `{...propsA, propsB}`.See [code](https://github.com/vuejs/vue-next/blob/master/packages/runtime-core/src/vnode.ts#L780).
BTW, this PR indeed not a good solution. | 2021-10-11T12:10:13 | 2021-10-11T12:10:13 | {} | CONTRIBUTOR |
vuejs | core | 940,122,834 | 3,102 | oswaldofreitas | Is there any other place I can follow discussions/progress about this one? | 2021-10-11T15:16:35 | 2021-10-11T15:16:35 | {
"eyes": 7
} | NONE |
vuejs | core | 938,878,602 | 4,757 | ElMassimo | Works like a charm in `3.2.20`, thanks! | 2021-10-08T17:07:43 | 2021-10-08T17:07:43 | {} | NONE |
vuejs | core | 939,216,613 | 4,767 | edison1105 | see https://v3.vuejs.org/guide/migration/custom-directives.html#overview
| 2021-10-09T03:32:20 | 2021-10-09T03:32:20 | {
"+1": 1
} | MEMBER |
vuejs | core | 940,712,409 | 4,786 | Chandler-Zhu | I added `const box1 = ref(null) ` and still get the same result, [here](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgYm94MSA9IHJlZihudWxsKSAgLy9qdXN0IGFkZGVkXG5jb25zdCBtc2cgPSByZWYoJ0hlbGxvIFdvcmxkIScpXG5jb25zdCBtZXNzYWdlcyA9IHJlZihbXG4gICAgICAgIHsgYm9keTog... | 2021-10-12T06:43:29 | 2021-10-12T06:46:24 | {} | NONE |
vuejs | core | 942,081,858 | 3,648 | haoziqaq | 谢谢～ | 2021-10-13T08:57:25 | 2021-10-13T08:57:25 | {} | NONE |
vuejs | core | 942,266,827 | 3,813 | hedefalk | @posva, @yyx990803
A general follow-up question. Can I somehow detect these things build-time? I got bitten of this since this typechecks and emits fine but the string is a number runtime:
```
<script setup lang="ts">
import { computed } from '@vue/reactivity';
const props = defineProps<{ modelValue: stri... | 2021-10-13T12:44:57 | 2021-10-13T12:46:10 | {} | NONE |
vuejs | core | 938,207,463 | 4,757 | ElMassimo | @yyx990803 Confirmed that this is a regression, it was working in [`3.2.10`](https://github.com/ElMassimo/vite-vue-router-hmr-repro/tree/3.2.10?rgh-link-date=2021-10-07T22%3A22%3A36Z). | 2021-10-07T22:46:21 | 2021-10-07T22:46:57 | {} | NONE |
vuejs | core | 938,535,538 | 4,764 | posva | There is no error | 2021-10-08T10:35:09 | 2021-10-08T10:35:09 | {} | MEMBER |
vuejs | core | 938,547,330 | 2,513 | AurelieV | For information, this is how we temporaly fix it for our usecase (App which load components inside iframe)
iframe.onload = () => {
performance.now = iframe.contentWindow.performance.now
}
Tested only on Chrome, this is a way to resynchronise the timestamps used by Vue | 2021-10-08T10:56:12 | 2021-10-08T10:56:12 | {} | NONE |
vuejs | core | 938,570,924 | 4,764 | edison1105 | ```javascript
<script setup>import { ref } from 'vue' // this line will cause an error
const props=defineProps({
foo:String
})
const msg = ref('Hello World!')
</script>
<template>
<h1>{{ msg }}</h1>
<input v-model="msg">
</template>
``` | 2021-10-08T11:35:52 | 2021-10-08T11:35:52 | {} | MEMBER |
vuejs | core | 939,469,281 | 4,774 | posva | Open an RFC on the rfcs repo.
BTW it should be a standalone function instead of a function attached to app for tree shaking reasons | 2021-10-10T11:57:01 | 2021-10-10T11:57:01 | {} | MEMBER |
vuejs | core | 939,556,956 | 4,780 | martinbean | @posva Pretty sure being unable to compile with what looks like perfectly-valid Vue code is a bug. Feel free to explain how this _isn’t_ a bug, though… | 2021-10-10T21:38:03 | 2021-10-10T21:38:03 | {} | NONE |
vuejs | core | 941,322,425 | 4,622 | catrope | In other words, it fails even without using comments anywhere. Just the text node in between the two `<p>` tags is enough to cause this failure. | 2021-10-12T19:13:00 | 2021-10-12T19:13:00 | {} | CONTRIBUTOR |
vuejs | core | 939,162,385 | 4,765 | edison1105 | > Why is this closed?
this is not correct.🤦♂️ | 2021-10-08T23:16:21 | 2021-10-08T23:16:21 | {} | MEMBER |
vuejs | core | 939,259,976 | 4,768 | edison1105 | caused by https://github.com/vuejs/vue-next/commit/d53451583684c37bda7d30bff912216e1a58126f | 2021-10-09T08:55:49 | 2021-10-09T08:56:00 | {
"+1": 2
} | MEMBER |
vuejs | core | 939,366,638 | 4,771 | yyx990803 | 1. 内部的运行时行为定义是非常明确的：任何 shallow 的 ref 或者 object 都会中断 unwrapping
2. 类型定义也应该是明确的，你所举出的例子和 #4732 都属于类型的 bug (fixed by https://github.com/vuejs/vue-next/commit/20a361541cc5faffa82cbf3f2d49639a97b3b678)
3. 虽然文档也确实可以改善，但这本质上不是文档的问题，只是单纯的类型没写对。 | 2021-10-09T21:51:25 | 2021-10-09T21:51:59 | {} | MEMBER |
vuejs | core | 939,904,564 | 4,776 | lgd8981289 | 多谢，我当时忽略了警告 | 2021-10-11T10:36:48 | 2021-10-11T10:36:48 | {} | NONE |
vuejs | core | 940,717,077 | 4,786 | Chandler-Zhu | According to the offical doc, `nextTick` is a global api method, why do I still have to do the import if it is global ? | 2021-10-12T06:51:58 | 2021-10-12T06:51:58 | {
"eyes": 1
} | NONE |
vuejs | core | 938,536,198 | 4,763 | posva | This is expected, you need to put the mergeProps inside a computed | 2021-10-08T10:36:15 | 2021-10-08T10:36:15 | {
"heart": 1
} | MEMBER |
vuejs | core | 939,286,088 | 4,769 | zhaozhongyu | 我修改了codepen实例, 您可以直接在示例上测试不同情况 | 2021-10-09T12:04:09 | 2021-10-09T12:04:09 | {} | NONE |
vuejs | core | 939,475,480 | 4,776 | edison1105 | 你需要提供一个最小可以复现的demo，否则是没办法帮你解决问题的。
像是vue-router-next的问题。注意看开发环境是否有警告。
| 2021-10-10T12:40:21 | 2021-10-10T12:48:45 | {} | MEMBER |
vuejs | core | 939,986,316 | 4,784 | zhaozhongyu | I found a testcase in `vShow.spec.ts` name `the value of 'display' set by v-show should not be overwritten by the style attribute when updated`, So the issue https://github.com/vuejs/vue-next/issues/4768 is not a bug, it is designed like this.
or we can fix it simply like https://github.com/iBelieveLove/vue-next/com... | 2021-10-11T12:30:13 | 2021-10-11T12:30:13 | {} | NONE |
vuejs | core | 940,709,118 | 4,786 | ygj6 | [You need to expose the box1 variable](https://v3.vuejs.org/guide/composition-api-template-refs.html#template-refs)
```vue
<script setup>
import { ref, nextTick } from 'vue'
const msg = ref('Hello World!')
const box1 = ref(null) // <------- Look here.
const messages = ref([
{ body: "Message... | 2021-10-12T06:37:06 | 2021-10-12T06:37:06 | {} | MEMBER |
vuejs | core | 941,113,282 | 4,783 | paraboul | Same issue here. Looks like a regression in production build. This broke us just recently (all our boolean props values suddenly evaluate to false).
edit: @LinusBorg I confirm, this is a regression in 3.2.20. I'd mark this as important 🙏 | 2021-10-12T15:20:10 | 2021-10-12T17:45:46 | {
"heart": 4
} | CONTRIBUTOR |
vuejs | core | 937,958,928 | 4,739 | julie777 | Understood. | 2021-10-07T16:28:04 | 2021-10-07T16:28:04 | {} | NONE |
vuejs | core | 938,433,722 | 4,760 | wensc1996 | > Open the issue in vant repository first.
Yes, I have been opened.https://github.com/youzan/vant/issues/9487 | 2021-10-08T08:05:56 | 2021-10-08T08:05:56 | {} | NONE |
vuejs | core | 938,437,524 | 4,760 | posva | Then please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org). | 2021-10-08T08:11:23 | 2021-10-08T08:11:23 | {} | MEMBER |
vuejs | core | 938,590,625 | 4,764 | posva | Thanks @edison1105
It's weird the error didn't show when I opened the repro 🤔 | 2021-10-08T12:08:43 | 2021-10-08T12:08:43 | {} | MEMBER |
vuejs | core | 939,488,870 | 4,777 | edison1105 | should be
```javascript
const emits = defineEmits(['update:value']);
``` | 2021-10-10T14:07:59 | 2021-10-10T14:07:59 | {
"+1": 3,
"laugh": 1
} | MEMBER |
vuejs | core | 940,853,931 | 4,738 | kad-tijhuo | @yyx990803 Thank you for looking into this issue so quickly. Unfortunately the setTimeout fix doesn't seem to work. With Vue 3.2.20 memory still isn't released properly, even after waiting for a longer period than is set in setTimeout.
Both screenshots were after switching from a 123 page pdf to a 12 page pdf, waiti... | 2021-10-12T09:55:25 | 2021-10-12T09:55:25 | {} | NONE |
vuejs | core | 940,908,726 | 4,491 | wlx200510 | typescript version should be upper then 4.0.0, ~3.9.9 will break. | 2021-10-12T11:11:17 | 2021-10-12T11:11:17 | {} | NONE |
vuejs | core | 940,715,221 | 4,786 | ygj6 | > I added const box1 = ref(null) and still get the same result, here
You also need to import nextTick from 'vue'
```vue
<script setup>
import { ref, nextTick } from 'vue' // <------- Look here.
const msg = ref('Hello World!')
const box1 = ref(null) // <------- Look here.
const messages =... | 2021-10-12T06:48:37 | 2021-10-12T07:05:16 | {} | MEMBER |
vuejs | core | 941,299,167 | 4,621 | catrope | I think this issue was closed incorrectly: my example doesn't involve a `<transition>` (which, you're right, can't have multiple children), it involves a `<transition-group>` (which can have multiple children, and is designed for that exact purpose) | 2021-10-12T18:58:44 | 2021-10-12T18:58:44 | {} | CONTRIBUTOR |
vuejs | core | 941,982,939 | 2,903 | leehave | > ### Version
> 3.0.4
>
> ### Reproduction link
> https://codepen.io/autumn-one/pen/dypJKXq?editors=0010
>
> ### Steps to reproduce
> ## 构建工具为 @vue/cli4.5.9
> ## 注入自定义属性如下
> ```js
> app.config.globalProperties.api = api; // 向所有组件注入 api 对象
> ```
>
> 注入之后是不能在组件中使用的，因为 ts 类型的原因，组件实例是没有 api 的声明的，所以需要额外声明
>... | 2021-10-13T06:57:48 | 2021-10-13T06:57:48 | {} | NONE |
vuejs | core | 967,144,593 | 4,933 | edison1105 | the root cause is: `instance.update` is not run.
| 2021-11-12T14:08:51 | 2021-11-13T01:12:46 | {} | MEMBER |
vuejs | core | 969,625,519 | 4,294 | languanghao | I also find a workaround, just use `defineProps(ComplexType)` instead of `defineProps<ComplexType>`. Even the `ComplexType` is imported from other file, it works fine. | 2021-11-16T01:34:09 | 2021-11-16T01:34:09 | {
"+1": 1,
"-1": 81,
"confused": 6,
"eyes": 6
} | NONE |
vuejs | core | 972,626,928 | 4,960 | mrts | Alright, let me just point out that there are at least two other recent questions in similar vein in Stack Overflow, so this is seems to be confusing developers:
1. https://stackoverflow.com/questions/69903520/vue-export-import-async-await-stops
2. https://stackoverflow.com/questions/64117116/how-can-i-use-async-aw... | 2021-11-18T08:06:16 | 2021-11-18T08:06:16 | {
"+1": 2
} | NONE |
vuejs | core | 972,788,717 | 4,960 | LinusBorg | Top level awai compiles to `async setup()` and that requires `Suspense`. All of this is documented here, and would be apparent to users if we had something like #2603. So this is a question of DX that we have to solve first and foremost.
Top-Level await is not a simple thing to support because what will be rendered... | 2021-11-18T11:41:27 | 2021-11-18T11:42:03 | {} | MEMBER |
vuejs | core | 968,206,321 | 3,489 | wen-haoming | > ```ts
> import { parse, transform } from '@vue/compiler-dom'
>
> const ast = parse(...)
>
> transform(ast, {
> nodeTransforms: [...]
> })
> ```
>
> Please read the [source type definitions](https://github.com/vuejs/vue-next/blob/master/packages/compiler-core/src/options.ts) for transform options usage.... | 2021-11-14T04:54:38 | 2021-11-14T04:54:38 | {} | NONE |
vuejs | core | 974,189,542 | 4,973 | posva | In this scenario you need to use a [post watcher](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IGlkPVwiYXBwXCI+XG4gICAgPHNsaWRlciA6bWF4VmFsdWU9XCJtYXhcIiAvPlxuICAgIDxidXR0b24gQGNsaWNrPVwiY2xpY2tlZFwiPlNldCBNYXg8L2J1dHRvbj5cbiAgPC9kaXY+XG48L3RlbXBsYXRlPlxuXG48c2NyaXB0PlxuaW1wb3J0IFNsaWRlciBmcm9tIFwiLi9... | 2021-11-19T15:52:11 | 2021-11-19T15:52:11 | {
"heart": 1
} | MEMBER |
vuejs | core | 974,898,679 | 4,817 | DoubleJ-G | I am also noticing something similar also happen with the fragment comments
```
- Client vnode: div
- Server rendered DOM: <!--[--> (start of fragment)
```
Nothing actually seems to be mismatched besides these comments. From what I can tell they are used for v-for and <slot>, possibly also for components with... | 2021-11-21T21:26:36 | 2021-11-21T21:26:36 | {} | NONE |
vuejs | core | 970,190,828 | 4,953 | LinusBorg | You are generating types for a module called "index", which doesn't exist. That happens because you specifically compile a named input file. look at your generated types:
```ts
// ....
declare module "index" {
export { default as Component } from "components/Component.vue";
}
```
You need to run (vue-... | 2021-11-16T11:44:19 | 2021-11-16T11:44:19 | {
"hooray": 1
} | MEMBER |
vuejs | core | 972,750,555 | 4,965 | 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-11-18T10:48:03 | 2021-11-18T10:48:03 | {} | MEMBER |
vuejs | core | 973,936,128 | 4,970 | egoist | @knightly-bot build this
| 2021-11-19T10:14:50 | 2021-11-19T10:14:50 | {
"+1": 1
} | NONE |
vuejs | core | 966,776,245 | 4,933 | edison1105 | as a workaround add a key to transition:
```javascript
<transition :key="key" name="fade" mode="out-in">
<component :is="Component" :key="key" />
</transition>
``` | 2021-11-12T02:46:27 | 2021-11-12T02:46:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 970,108,311 | 4,952 | LinusBorg | Additionally, this would be a breaking change, which we won't do. | 2021-11-16T09:59:47 | 2021-11-16T09:59:47 | {} | MEMBER |
vuejs | core | 974,574,778 | 4,977 | ygj6 | https://github.com/vuejs/vue-next/issues/2431#issuecomment-712286152 You can put them on the same line
```html
<a class="btn btn-secondary" href="/Registro">Back</a> <input type="submit" value="Safe" class="btn btn-primary"/>
``` | 2021-11-20T02:05:31 | 2021-11-20T02:05:31 | {
"+1": 1
} | MEMBER |
vuejs | core | 974,808,694 | 4,980 | LinusBorg | The fact that it works is a unwanted side-effect of a difference in the dev-behaviour required for debuggability / HMR.
We should find some way to warn about this though - the first thing coming to mind would be to throw an error for SFCs using script setup that don't use a <template>. | 2021-11-21T12:29:05 | 2021-11-21T12:43:51 | {} | MEMBER |
vuejs | core | 967,092,981 | 4,936 | sxzz | Yes, I can indeed modify props type to solve this problem.
However, this is a bit counter-intuitive, I think Vue should automatically unwrap for props. Just like `reactive` will automatically unwrap. | 2021-11-12T12:45:41 | 2021-11-12T12:45:41 | {} | MEMBER |
vuejs | core | 968,426,296 | 4,943 | yyx990803 | This is definitely not the right fix - also, Vue SSR really isn't resigned for rendering the HTML layout, you should render the layout yourself. | 2021-11-15T01:20:28 | 2021-11-15T01:20:28 | {
"+1": 2,
"heart": 1
} | MEMBER |
vuejs | core | 968,431,800 | 4,883 | yyx990803 | > should I open separate issue or just put the link to repro here?
Please comment here with updated repo.
Re duplicated attributes: again, if the compiler mistakenly injects the same scopeID twice, it's a scope ID bug. If you manually author duplicated attributes in a template, it is always a mistake (because the... | 2021-11-15T01:34:50 | 2021-11-15T01:35:27 | {} | MEMBER |
vuejs | core | 968,648,200 | 4,946 | posva | Related to https://github.com/vuejs/vue-next/issues/2598 | 2021-11-15T08:29:57 | 2021-11-15T08:29:57 | {} | MEMBER |
vuejs | core | 968,676,395 | 4,939 | liulei92 | you can fix it in "https://github.com/vuejs/vue-next/issues/4654" | 2021-11-15T09:05:37 | 2021-11-15T09:05:37 | {} | NONE |
vuejs | core | 970,110,650 | 4,952 | xflyyxfl | > `@event="(...args) => fn(custom_par, ...args)"`
yes, that will work, But a bit not straightforward | 2021-11-16T10:02:28 | 2021-11-16T10:02:28 | {} | NONE |
vuejs | core | 971,543,102 | 4,121 | xanf | @yyx990803 @posva
While working on migration of bootstrap-vue to @vue/compat I believe I was able to extract minimal possible example:
```js
import Vue from "@vue/compat";
const App = {
compatConfig: {
MODE: 3,
COMPONENT_V_MODEL: true,
RENDER_FUNCTION: true
},
render(h) {
return h... | 2021-11-17T12:41:59 | 2021-11-17T13:26:36 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 973,822,702 | 3,251 | HcySunYang | ~~Now it seems that this is the expected behavior.~~
Sorry, this seems to need to be fixed... | 2021-11-19T07:29:14 | 2021-11-19T07:35:11 | {} | MEMBER |
vuejs | core | 974,659,455 | 2,695 | LinusBorg | Closing this as we don't see any way to improve this. | 2021-11-20T14:42:01 | 2021-11-20T14:42:01 | {} | MEMBER |
vuejs | core | 925,700,765 | 4,566 | cyfung1031 | Is it just the problem in codesandbox.io?
It performs correctly in [SFC Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2PlxuICAgIFZ1ZSBMb2dvXG4gICAgPEhlbGxvV29ybGQgQGNsaWNrPVwib25DbGlja1wiIC8+XG4gIDwvZGl2PlxuPC90ZW1wbGF0ZT5cblxuPHNjcmlwdD5cbmltcG9ydCBIZWxsb1dvcmxkIGZyb20gXCIuL0hlbGxvV29ybGQu... | 2021-09-23T10:48:03 | 2021-11-20T16:04:11 | {} | NONE |
vuejs | core | 974,994,086 | 4,947 | caozhong1996 | It does address this problem, but it removed the '--ci' option. I believe it's good idea to explicitly tell Jest it is running in a CI environment, Jest will handle snapshots more strictly.😀
| 2021-11-22T01:33:14 | 2021-11-22T01:33:14 | {} | CONTRIBUTOR |
vuejs | core | 966,737,952 | 4,933 | dodododooo | also when component have no template and render function | 2021-11-12T01:10:07 | 2021-11-12T01:10:07 | {} | NONE |
vuejs | core | 966,908,848 | 4,939 | posva | Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org). | 2021-11-12T08:16:42 | 2021-11-12T08:16:42 | {} | MEMBER |
vuejs | core | 971,116,775 | 4,817 | mekery | same problem. | 2021-11-17T02:28:28 | 2021-11-17T11:58:34 | {} | NONE |
vuejs | core | 972,684,733 | 4,921 | LinusBorg | I'll close this as I don't see any arguments for a breaking change on the horizon. | 2021-11-18T09:25:43 | 2021-11-18T09:25:43 | {} | MEMBER |
vuejs | core | 972,871,973 | 4,967 | posva | ~~The script setup should always go after the regular script.~~ This is irrelevant in this scenario as there shouldn't be a `computed` option used when using script setup anyway.
Also, when using script setup, I recommend you to use the regular script **only** for things that cannot be done within the script setup. | 2021-11-18T13:36:10 | 2021-11-18T13:37:11 | {} | MEMBER |
vuejs | core | 973,724,222 | 3,251 | egoist | Can we get this merged 👀 | 2021-11-19T04:25:31 | 2021-11-19T04:25:31 | {} | NONE |
vuejs | core | 926,067,911 | 4,566 | SupertigerDev | > > I fixed my issue by adding INSTANCE_LISTENERS: false as suggested
>
> I recommend you to use vite2 to build your vue3 apps. Vite2 don't need to config these options and everything works the same way as official docs.
>
> https://v3.vuejs.org/guide/installation.html#vite
I'm using the migration build of vue... | 2021-09-23T18:49:41 | 2021-11-20T16:02:36 | {} | NONE |
vuejs | core | 975,017,603 | 4,975 | ygj6 |
> When I use `@vue/compiler-sfc` to parse a component's ast, I found it can't parse `v-pre` to props. Any other directives can be found in the AST parsing results of the corresponding attributes. So it's on purpose or it's a bug?
https://github.com/vuejs/vue-next/blob/61720231b48dc57eeda8930eae11b5a03d9210a3/packa... | 2021-11-22T02:34:42 | 2021-11-22T02:34:42 | {} | MEMBER |
vuejs | core | 966,769,557 | 4,814 | yyx990803 | This is indeed a breaking change.
- Is the `.cjs` rename necessary?
- `.mjs` files are really a Node-only construct, so it doesn't make sense to rename `esm-browser` files as well.
- Since we do not have conditional `exports` declared for `@vue/*` packages, you will need to import these `.mjs` files via deep impor... | 2021-11-12T02:28:11 | 2021-11-12T02:28:11 | {} | MEMBER |
vuejs | core | 966,779,252 | 4,937 | wxsms | > You should commit the correct user value. eg:
>
> ```js
> onMounted(() => {
> store.commit('setUser', { name: 'username', roles: [] });
> });
> ```
@ygj6 this is not the point, bad codes happends. The point is, it behave differently in development and production. which made the problem not being able to s... | 2021-11-12T02:55:04 | 2021-11-12T03:07:39 | {} | MEMBER |
vuejs | core | 966,939,052 | 4,940 | LinusBorg | 1. Your issue is missing the required runnable reproduction.
2. Using webassembly is unrelated to Vue core, it's a question of configuring your build system. Of you are using Vue CLI (which I can't tell as you didn't provide a reproduction), you should open an issue in that project's repository - after you asked for h... | 2021-11-12T09:07:42 | 2021-11-12T09:07:42 | {} | MEMBER |
vuejs | core | 972,691,285 | 4,954 | JSteitz | More info:
This only happens if I use `<script setup>`.
Using `defineComponent` with `setup()` does work. | 2021-11-18T09:33:39 | 2021-11-18T09:33:39 | {} | NONE |
vuejs | core | 974,456,894 | 4,874 | trusktr | Ah, thanks, I will try this out when I circle back to it. | 2021-11-19T20:45:57 | 2021-11-19T20:45:57 | {} | NONE |
vuejs | core | 974,650,459 | 4,947 | LinusBorg | Tests running fine for me ... I think another recent change already fixed this? | 2021-11-20T13:27:41 | 2021-11-20T13:28:39 | {} | MEMBER |
vuejs | core | 966,778,228 | 4,937 | ygj6 | You should commit the correct user value. eg:
```js
onMounted(() => {
store.commit('setUser', { name: 'username', roles: [] });
});
``` | 2021-11-12T02:52:10 | 2021-11-12T02:52:10 | {} | MEMBER |
vuejs | core | 967,276,005 | 4,662 | raffobaffo | @lucasantunes-ciandt Nice find 👍 ! Still this block is not part of the PR, because this actually make sense to have it in a separate module that is loaded just when custom elements are needed. In my case I have a components library and I want to have 2 exports, one to be consumed by Vue applications and one for brows... | 2021-11-12T17:09:05 | 2021-11-12T17:09:05 | {} | NONE |
vuejs | core | 968,246,115 | 3,489 | yyx990803 | Yes, please read the source code. | 2021-11-14T08:24:29 | 2021-11-14T08:24:29 | {} | MEMBER |
vuejs | core | 969,011,756 | 2,989 | dpschen | If someone needs this: I was able to create a hacky work-around for this:
https://github.com/dpschen/vue3-directive-script-setup
You have to use custom hooks, so they are not the normal vue ones as mentioned by LinusBorg. | 2021-11-15T15:16:06 | 2021-11-15T15:16:06 | {} | NONE |
vuejs | core | 969,028,781 | 4,948 | dpschen | @posva: Thanks, I created [a discussion](https://github.com/vuejs/rfcs/discussions/414)
I was aware of the rfcs but was confused by the wording in the [issue helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next&type=feature-request):
> The issue list is reserved exclusively for bug reports and feature request... | 2021-11-15T15:33:00 | 2021-11-15T15:33:00 | {} | NONE |
vuejs | core | 970,106,638 | 4,952 | jacekkarczmarczyk | `@event="(...args) => fn(custom_par, ...args)"` | 2021-11-16T09:57:42 | 2021-11-16T09:57:42 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 970,163,490 | 4,954 | LinusBorg | If you have a compile error, please provide a reproduction that actually demonstrates this.
the SFC playground doesn't work for this type of reproduction, obviously. | 2021-11-16T11:07:31 | 2021-11-16T11:07:31 | {} | MEMBER |
vuejs | core | 959,008,724 | 4,874 | LinusBorg | Just for the record what you can quite easily do for now is use a wrapper component like this:
```js
import { h, reactive } from 'vue'
import App from './App.vue'
const props = reactive({ whatever })
const app = createApp({
render: () => h(App, props)
})
app.mount('#app')
```
When you now mutate `... | 2021-11-03T12:58:41 | 2021-11-18T07:07:54 | {
"+1": 19,
"heart": 12
} | MEMBER |
vuejs | core | 972,594,344 | 4,874 | LinusBorg | Sorry for confusing you - I simply forgot to wrap it in `reactive()`. Fixed my previous post. | 2021-11-18T07:08:15 | 2021-11-18T07:08:15 | {} | MEMBER |
vuejs | core | 973,284,001 | 4,968 | LinusBorg | `@babel/parser` supports this new syntax since `7.16`, our lockfile has it locked at `7.15.8` right now. Hopefully bumping this dep is all it takes? | 2021-11-18T21:25:15 | 2021-11-18T21:26:28 | {} | MEMBER |
vuejs | core | 973,994,495 | 4,971 | posva | I think you are right, it makes sense for `toRaw()` to not have nested | 2021-11-19T11:32:30 | 2021-11-19T11:32:30 | {} | MEMBER |
vuejs | core | 974,711,321 | 4,950 | kadiryazici | @yuwu9145 What about custom components that use `$props` ? | 2021-11-20T21:06:16 | 2021-11-20T21:06:16 | {} | CONTRIBUTOR |
vuejs | core | 970,182,494 | 4,954 | JSteitz | Here is a minimal repo: https://github.com/JSteitz/bug_vue_next_template_refs | 2021-11-16T11:32:58 | 2021-11-16T11:32:58 | {} | NONE |
vuejs | core | 971,463,936 | 4,956 | LinusBorg | It happens because
1. We *first* set the options textContent before the value property
https://github.com/vuejs/vue-next/blob/f454dd62ab689b348902b01f849ca5347e91ffae/packages/runtime-core/src/renderer.ts#L655
2. then, when attempting to set the value prop, we compare the new, incoming value to the existing o... | 2021-11-17T10:58:37 | 2021-11-17T11:36:21 | {} | MEMBER |
vuejs | core | 972,144,507 | 4,960 | posva | No because they are just different and valid behaviors. What is interesting is to have https://github.com/vuejs/vue-next/issues/2603 | 2021-11-17T22:18:41 | 2021-11-17T22:18:41 | {} | MEMBER |
vuejs | core | 972,882,839 | 4,967 | apeschar | Okay, but does it really make sense for this to work in the dev server, but not in a production built? Isn't that confusing? | 2021-11-18T13:50:10 | 2021-11-18T13:50:10 | {} | NONE |
vuejs | core | 973,838,912 | 4,969 | Bigfish8 | you should use `const bold = computed(() => msg.value.length>=10)` here. | 2021-11-19T07:52:00 | 2021-11-19T07:52:00 | {} | CONTRIBUTOR |
vuejs | core | 973,969,634 | 4,971 | LinusBorg | I'd say that this is expected. the raw source object for the first store does contain a proxy as its `nested` property because you defined it that way.
Would you expect `toRaw()` to somehow unwrap that? that would alter the source object. | 2021-11-19T10:53:34 | 2021-11-19T10:53:34 | {} | MEMBER |
vuejs | core | 970,188,585 | 4,817 | ovidiuc | I'm having the same problem, using Quasar framework. The component rendered by `<router-view>` server side is wrapped in a `<!--[--> <!--]-->` that the client is not expecting. | 2021-11-16T11:41:37 | 2021-11-16T11:41:37 | {} | NONE |
vuejs | core | 972,646,911 | 4,963 | 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-11-18T08:36:42 | 2021-11-18T08:36:42 | {} | MEMBER |
vuejs | core | 973,593,497 | 2,027 | davevasquez | > 
>
> Even in the store when I save my current form ( vue component as form) it gives me this...And in the production it removes it so I can't go further
I'm encoutering a similar issue when dispatching ... | 2021-11-19T00:43:50 | 2021-11-19T02:40:03 | {
"+1": 1
} | NONE |
vuejs | core | 973,698,850 | 4,951 | ygj6 | This PR could also solve the problem of the inline function mode of non-asynchronous components in the link: [sfc.vuejs.org](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuPGJ1dHRvbiBAY2xpY2s9XCJzaG93QXRUb3A9IXNob3dBdFRvcFwiPlRvZ2dsZTwvYnV0dG9uPlxuICA8ZGl2IHYtaWY9J3Nob3dBdFRvcCc+XG4gICAgPCEtLSBjbGljayBhbmQgcHJp... | 2021-11-19T03:26:03 | 2021-11-19T03:26:03 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.