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 | 908,697,312 | 4,385 | OskarLebuda | @yyx990803 I see u have been added a label `feat:ssr`. Can you explain how it's even possible no one thought about it during the implementation? This is a base feature of SSR implementation. If someone had more then basic sample code then cannot move to vue3 while this "feature" will not be done. I think this should b... | 2021-08-30T21:08:03 | 2021-08-30T21:43:02 | {} | NONE |
vuejs | core | 909,825,737 | 2,860 | ckvv | @mseele @bjkippax
We can support tree-shaking by compiling it into multiple files. like this <https://github.com/ckpack/v-ui-template>,
And here is a pack I wrote with it <https://github.com/ckpack/vue-color> | 2021-09-01T02:48:35 | 2021-09-01T02:48:35 | {} | NONE |
vuejs | core | 910,240,348 | 4,480 | Bigfish8 | > I can't find difference between them.
```
import type { DefaultFunc } from './service';
interface Props {
fetchData?: DefaultFunc
}
```
This is because In the condition, sfc-compiler can not generate the right type,see [code](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmlt... | 2021-09-01T12:33:46 | 2021-09-01T12:34:10 | {} | CONTRIBUTOR |
vuejs | core | 910,733,414 | 4,393 | yyx990803 | While this is a good improvement, I took another look at #4370 and feels there's a bit more to the original issue. Specifically for a prop declared as `type: String`, we probably should not attempt to parse it into a number at all. For example, if the original usage was something like `<my-el phone="123456789">`, it sh... | 2021-09-01T20:47:34 | 2021-09-01T20:47:34 | {} | MEMBER |
vuejs | core | 911,124,402 | 2,250 | salazarr-js | I know this is old and pretty closed, but trying to made something like a `props` factory function to generate reusable props between components, I found quite dificult to return the right type.
My function is pretty simple
```typescript
export function getIconDefaultProps() {
return {
width: {
type... | 2021-09-02T03:49:48 | 2021-09-02T04:21:51 | {} | NONE |
vuejs | core | 906,270,287 | 4,446 | sxzz | It still can't transform with spaces.
```
let msg = $ref < string > ('Hello World!')
``` | 2021-08-26T10:06:43 | 2021-08-26T10:06:43 | {} | MEMBER |
vuejs | core | 907,668,920 | 4,464 | ozergul | I thank you so much @sqal. | 2021-08-28T18:25:05 | 2021-08-28T18:25:05 | {} | NONE |
vuejs | core | 909,850,059 | 4,478 | ghost | @posva - i guess we did not search well enough on the issue. We found the solution for the issue at https://github.com/vuejs/vue-next/issues/4344. Thanks for the time. | 2021-09-01T03:42:55 | 2021-09-01T03:42:55 | {
"+1": 1
} | NONE |
vuejs | core | 911,297,296 | 4,393 | posva | Yeah, I thought about it too. I have two questions then:
- Should I just look if the props is an object and if it exists and it's either not Number or not `{ type: Number }`, skip the `parseNumber()` call.
- Should I still call `parseNumber()` for non existant props? | 2021-09-02T07:12:21 | 2021-09-02T07:12:21 | {} | MEMBER |
vuejs | core | 906,954,871 | 3,692 | ruchenshanghai | will this [issue](https://github.com/vuejs/vue-next/issues/4016) be solved by this PR?
if so, why don't we merge this PR ? | 2021-08-27T06:17:37 | 2021-08-27T06:17:37 | {} | NONE |
vuejs | core | 907,066,612 | 4,455 | LongJinCen | Here is a reproducible [demo](https://github.com/LongJinCen/Vue3-TS-error) with readme.md attached。please check @ygj6
| 2021-08-27T09:33:43 | 2021-08-27T09:33:43 | {} | NONE |
vuejs | core | 907,262,639 | 4,433 | modularcoder | @orziz yes, same for me, seems the
```
/// <reference types="vue/ref-macros" />
```
in env.d.ts doesn't fix TS errors | 2021-08-27T14:54:11 | 2021-08-27T14:54:11 | {} | NONE |
vuejs | core | 907,453,803 | 3,842 | doutatsu | Bumping this up -> Can't migrate to Vue 3 due to this issue | 2021-08-27T20:18:22 | 2021-08-27T20:18:30 | {
"+1": 2
} | NONE |
vuejs | core | 907,866,863 | 4,462 | dsonet | > https://2x.antdv.com/components/slider/#components-slider-demo-basic
> 
> like this. we have a tooltip when click slider bar. when i click other point, tootip will hide, then show again.
Which the toolti... | 2021-08-29T20:27:57 | 2021-08-29T20:27:57 | {} | CONTRIBUTOR |
vuejs | core | 909,388,688 | 4,394 | matt-filion | Bump. | 2021-08-31T16:23:45 | 2021-08-31T17:13:31 | {} | NONE |
vuejs | core | 907,912,734 | 4,462 | tangjinzhou |
> Which the tooltip should not hide when you keep clicking /moving on other points.
@dsonet
It doesn’t matter, whether it’s hidden or not, it’s reasonable. I’m just giving a scenario | 2021-08-30T00:30:59 | 2021-08-30T00:30:59 | {} | CONTRIBUTOR |
vuejs | core | 908,396,980 | 4,469 | posva | `defineEmits()` is a macro, it needs to be able to statically analyze what is passed to it in order to know what to generate, so it doesn't seem reasonable to be used that way as it doesn't get called in reality, even less with a generic `T` that is never given any type.
Maybe you are looking for this: https://githu... | 2021-08-30T14:36:14 | 2021-08-30T14:36:14 | {} | MEMBER |
vuejs | core | 908,862,699 | 4,477 | yuxino | 
currently not supported | 2021-08-31T03:12:40 | 2021-08-31T03:12:40 | {} | NONE |
vuejs | core | 909,242,941 | 2,860 | bjkippax | > Any progress in this topic? Sadly this is a showstopper to move our private libraries to vue 3, too.
Agreed. It’s causing our organisation problems too. | 2021-08-31T13:34:02 | 2021-08-31T13:34:02 | {} | NONE |
vuejs | core | 910,038,307 | 4,480 | LinusBorg | Ok could test it. Types don't like it.
As a temporary workaround you can typecast it like so:
```ts
const props = withDefaults(defineProps<Props>(), {
fetchData: (() => defaultFunc) as unknown as DefaultFunc
});
``` | 2021-09-01T08:00:57 | 2021-09-01T08:13:49 | {} | MEMBER |
vuejs | core | 910,854,575 | 4,489 | posva | You need to remove the prop from custom text input so it doesn't treat it as a v-model value and automatically handle the emit too (similar to having the emit defined https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aDE+e3sgbXNnIH19PC9oMT5cbiAgPGN1c3RvbS10ZXh0LWlucHV0IHYtbW9kZWw9XCJtc2dcIiAvPlxuPC90ZW1wbGF0ZT... | 2021-09-01T22:46:37 | 2021-09-01T22:46:37 | {} | MEMBER |
vuejs | core | 906,502,902 | 4,453 | LongJinCen | > Your types are different: the one with the interface make the props required while the one with the js object make them optional:
>
> ```js
> defineProps({
> hintMsg: { type: String, required: true },
> iconName: String
> })
> ```
>
> Remember to use the [forum](http://forum.vuejs.org/) or the [Discord... | 2021-08-26T15:15:44 | 2021-08-27T03:59:04 | {} | NONE |
vuejs | core | 906,993,892 | 4,455 | ygj6 | Could you describe the error in more detail? | 2021-08-27T07:34:40 | 2021-08-27T07:34:40 | {} | MEMBER |
vuejs | core | 907,604,495 | 4,463 | sqal | There's no Card component in your repository. My guess is you're incorrectly importing Card component, maybe you have a misconfigured `@` alias. Add `console.log(Card)` to see if it's exported component or undefined
[reproduction](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IENhcmQgfSBmcm9... | 2021-08-28T10:06:59 | 2021-08-28T10:07:31 | {} | CONTRIBUTOR |
vuejs | core | 908,924,239 | 4,424 | nVitius | @Justineo I spent some time in the SFC playground today, trying to get a reproduction working (not working?).
I could not replicate the issue on there. From what I could tell, the compiled JS I got in the playground was the same as the JS I saw in the library that had the issue. Not really sure what to make of this.
... | 2021-08-31T05:59:38 | 2021-08-31T05:59:38 | {} | NONE |
vuejs | core | 911,073,505 | 4,433 | orziz | updated to v3.2.7, but this issues is still not fixed. | 2021-09-02T02:49:51 | 2021-09-02T02:49:51 | {
"+1": 1
} | NONE |
vuejs | core | 906,232,234 | 4,447 | laineus | @posva
I have added one case into existing test. https://github.com/vuejs/vue-next/pull/4447/commits/88ecea92ee070e6283c0f0a25efb1073e8512922
It will not be passed on master, and will be passed on this PR.
I figured it's not need cases for all options, so I didn't. | 2021-08-26T09:09:29 | 2021-08-26T09:09:29 | {} | CONTRIBUTOR |
vuejs | core | 908,079,198 | 4,466 | ygj6 | I tried the [demo](https://github.com/LongJinCen/Vue3-TS-error) provided in #4455, and it still fails to compile after incorporating this `PR`.
```
ERROR in D:\workspace\vue-next\Vue3-TS-error\src\App.vue.ts
7:2-7
[tsl] ERROR in D:\workspace\vue-next\Vue3-TS-error\src\App.vue.ts(7,3)
TS2769: No overload mat... | 2021-08-30T06:50:23 | 2021-08-30T06:50:23 | {} | MEMBER |
vuejs | core | 908,208,079 | 4,466 | webfansplz | @ygj6
Sry, I misunderstood the meaning of the issue.
The reason maybe is that the option type of defineComponent is not overloaded correctly after compiled. | 2021-08-30T09:56:35 | 2021-08-30T12:38:10 | {} | MEMBER |
vuejs | core | 909,101,003 | 4,309 | pawel-marciniak | Is there any plan to fix this? Because for now I will need to get back to Vue 2.x. Regarding my above error - I'm using TypeScript and I have the same error when I'm using one <script setup> tag but without `lang="ts"`, so it seems to me that using two <script> tags along with TypeScript results in error. | 2021-08-31T10:18:16 | 2021-08-31T10:22:06 | {} | NONE |
vuejs | core | 910,723,945 | 4,486 | dependabot[bot] | OK, I won't notify you about sass again, unless you re-open this PR or update it yourself. 😢 | 2021-09-01T20:38:31 | 2021-09-01T20:38:31 | {} | CONTRIBUTOR |
vuejs | core | 911,479,159 | 4,216 | cexbrayat | Now that #4472 landed, this PR is rebased on master and ready to review.
The fix is intended to unblock the migration of the ecosystem to jest 27, but it also fixes a more general issue with updating proxies via `Object.defineProperty`. | 2021-09-02T09:57:38 | 2021-09-02T09:57:38 | {} | MEMBER |
vuejs | core | 906,916,831 | 3,930 | wuyongzhi | > @qmhc 我刚刚解决了这个问题，我修改了两个地方。1.rollup.config 中增加 resolve: { dedupe: ['vue'] } （这个是从vite，尤大回复别人的一个问题） 2.把vue从dependencies 改为 devDependencies 。不知道是哪个起作用了，但是确实解决了
我遇到了相同的问题，在 vite.config.ts 中增加 `resolve: { dedupe: ['vue'] }` 这个配置解决了，感谢！ | 2021-08-27T04:28:20 | 2021-08-27T04:28:20 | {
"+1": 6
} | NONE |
vuejs | core | 908,415,809 | 4,468 | 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).
Maybe you need to use `markRaw()` (look it up in documentation) | 2021-08-30T15:00:29 | 2021-08-30T15:00:29 | {} | MEMBER |
vuejs | core | 908,989,892 | 4,468 | ygj6 | Here when you get rid of whitespaces, the `fragment` node that wraps the `v-for` will also be deleted.
```
//exposed methods
set: function (el, lmddOptions) {
if (!el.lmdd) {
clean(el); //get rid of whitespaces <---------------
el.lmdd = true;
el.lmddOptions = assignOptio... | 2021-08-31T07:53:45 | 2021-08-31T07:53:45 | {
"heart": 1
} | MEMBER |
vuejs | core | 910,105,174 | 4,480 | HoPGoldy | And strangely, when I used the import `DefaultFunc` type in props interafce, default function was executed.
```typescript
import type { DefaultFunc } from './service';
interface Props {
fetchData?: DefaultFunc
}
// props.fetchData print "result" on console
```
But when I replaced `DefaultFunc` with ty... | 2021-09-01T09:27:25 | 2021-09-01T09:27:25 | {} | NONE |
vuejs | core | 911,447,835 | 4,482 | pikax | @yyx990803 fixed the issues with `h` the reason why it wasn't accepting an arbitrary `onXXX` was because the `onXXX` was having a type of `undefined` instead of `function`
I used `catch(e :any)` because the option `useUnknownInCatchVariables` was failing the `api-extractor` on `test-dts`.
What's missing now is f... | 2021-09-02T09:27:05 | 2021-09-02T09:27:05 | {} | MEMBER |
vuejs | core | 908,368,620 | 4,466 | LongJinCen | By the way, I have another problem, I want to make a prop to be required at runtime, So I'm write interface like this
```javascript
interface Props {
value: number
}
```
when `npm run build` , But it still failed, reporting an error
```javascript
[tsl] ERROR in /Users/bytedance/code/webpack5-ts-vue3/src/App.... | 2021-08-30T14:02:02 | 2021-08-30T14:14:35 | {} | NONE |
vuejs | core | 910,809,758 | 4,482 | yyx990803 | Ok the `h` type inference issue is that now if the `defineComponent` call doesn't explicitly declare `emits` option, then `h` won't accept arbitrary `onXXX` handlers. Should be related to the emits to handler props inference PR (#3926) - /cc @Amour1688 | 2021-09-01T21:56:19 | 2021-09-01T21:56:19 | {} | MEMBER |
vuejs | core | 911,852,308 | 2,015 | kaizenseed | Is there an accepted best practices approach to this issue that's different from the solution provided in https://stackoverflow.com/a/63665828/1764728? | 2021-09-02T16:20:03 | 2021-09-02T16:20:03 | {} | NONE |
vuejs | core | 913,353,215 | 4,525 | edison1105 | cause by https://github.com/vuejs/vue-next/pull/4518/files#diff-dbacb533411ec164eec5335d9310a44a911751dafc3f72c6879a6cdaf795be93R115 | 2021-09-06T05:23:57 | 2021-09-06T05:23:57 | {} | MEMBER |
vuejs | core | 913,432,259 | 4,527 | LongJinCen | > You are not giving the ref a type:
>
> ```ts
> const hint = ref<HTMLElement | undefined>()
> ```
That's not the problem. I looked at the type definition for `_createElementBlock`:
```javascript
// the props's type definition is not correct, The result is that ref is of type any
export declare function create... | 2021-09-06T07:58:32 | 2021-09-06T08:06:06 | {} | NONE |
vuejs | core | 913,961,778 | 4,423 | ygj6 |
It works fine in vite project, or ignores the type check can also work normally.
```
// @ts-ignore
import HelloWorld, { HelloWorldProps } from './components/HelloWorld.vue';
``` | 2021-09-07T03:23:06 | 2021-09-07T03:23:06 | {} | MEMBER |
vuejs | core | 915,087,905 | 3,577 | XMBLDB | same question. vue:3.2.10 @vue/compiler-sfc:3.2.10 | 2021-09-08T09:46:07 | 2021-09-08T09:46:16 | {
"+1": 1
} | NONE |
vuejs | core | 915,125,679 | 4,535 | 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).
---
This is related to rxjs not vue... | 2021-09-08T10:43:59 | 2021-09-08T10:43:59 | {} | MEMBER |
vuejs | core | 916,551,017 | 4,512 | oooplz | ~~Why do the feat still no be merged to master branch.~~
My apologies for the ask. I am using ``vue-next`` to develop a lib. And i have one component should be creating some child components. So i thought the ``extends`` keyword was helpful for me.
But @yyx990803 has said that `` the workaround is to prefer writ... | 2021-09-10T01:01:44 | 2021-09-10T01:27:10 | {} | NONE |
vuejs | core | 912,892,434 | 4,515 | ygj6 | > @aphex这是#4503的副本吗？
> /cc @ygj6
yes:stuck_out_tongue: | 2021-09-04T02:24:42 | 2021-09-04T02:24:42 | {} | MEMBER |
vuejs | core | 912,992,327 | 4,523 | posva | Issues are for bug reports and feature requests only. | 2021-09-04T15:31:33 | 2021-09-04T15:31:33 | {} | MEMBER |
vuejs | core | 912,997,481 | 4,501 | yyx990803 | There is no point in using MobX in Vue because the two systems are redundant. | 2021-09-04T16:05:36 | 2021-09-04T16:05:36 | {} | MEMBER |
vuejs | core | 913,550,607 | 4,423 | edison1105 | @henribru
yes, It still has the issue.
It's my fault. My PR has not fixed this issue but improve the `defineProps`.
I misunderstood it. This is about using the exported interface in another file.
the error info is changed.
![image](https://user-images.githubusercontent.com/3705199/132208359-d7ed6661-0dcd-4f9e-8... | 2021-09-06T10:50:42 | 2021-09-07T00:39:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 916,240,563 | 4,424 | nVitius | @yyx990803 Thanks for the help with diagnosing this. When you create the patch for that, will you link to it here? I'm interested in seeing where that happens. Thanks! | 2021-09-09T16:12:02 | 2021-09-09T16:12:02 | {} | NONE |
vuejs | core | 911,765,553 | 4,497 | StarHosea | I modified the demo, please see again.
```
bind style, attrs.style is string:
attrs.style is color:red;
fixed style, attrs.style is object:
attrs.style is { "color": "red" }
```
[demo link](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdD5cbiAgaW1wb3J0IENvbXAgZnJvbSAnLi9Db21wLnZ1ZSdcbmV4cG9ydCBkZWZhdW... | 2021-09-02T14:46:05 | 2021-09-03T01:10:43 | {} | NONE |
vuejs | core | 912,214,424 | 4,500 | oooplz | We can using SFC to implement that.
```vue
<template>
<component
v-bind:is="`h${$props.level}`"
v-bind="$attrs"
/>
</template>
<script>
export default {
inheritAttrs: false, // HIGHTLINE
props: ['level']
}
</script>
``` | 2021-09-03T02:55:37 | 2021-09-03T02:55:37 | {} | NONE |
vuejs | core | 913,150,007 | 4,524 | edison1105 | already fixed via 815bfcffae7a9f04ee996367a731e6e072af6bd2, not release yet. | 2021-09-05T12:55:26 | 2021-09-05T12:55:26 | {} | MEMBER |
vuejs | core | 913,282,246 | 4,516 | agileago | > I think an easy improvement is allowing a plugin function to return a "cleanup" callback.
yes. perfect design | 2021-09-06T02:00:54 | 2021-09-06T02:00:54 | {} | NONE |
vuejs | core | 916,254,990 | 4,545 | yyx990803 | Please reduce the reproduction to a smaller scope - ideally using https://sfc.vuejs.org. | 2021-09-09T16:30:42 | 2021-09-09T16:30:50 | {} | MEMBER |
vuejs | core | 916,733,829 | 4,550 | posva | There is no guarantee in the order components get unmounted/mounted/updated as there are different optimizations that can happen so you should definitely not rely on it. | 2021-09-10T08:36:20 | 2021-09-10T08:36:20 | {} | MEMBER |
vuejs | core | 912,999,348 | 4,501 | Justineo | I think OP is trying to reuse state management logic across apps built with both Vue and React. | 2021-09-04T16:18:05 | 2021-09-04T16:18:05 | {} | MEMBER |
vuejs | core | 913,425,924 | 4,527 | posva | You are not giving the ref a type:
```ts
const hint = ref<HTMLElement | undefined>()
``` | 2021-09-06T07:48:28 | 2021-09-06T07:48:28 | {} | MEMBER |
vuejs | core | 913,559,887 | 4,528 | Justineo | Your reproduction seems to be incorrect.
```vue
<script>
export default {
created () {
const asyncFunction = Object.getPrototypeOf(async function () { })
console.log(asyncFunction.constructor)
}
}
</script>
```
See [here](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdD5cbmV4cG9ydCBkZWZhdWx0... | 2021-09-06T11:05:43 | 2021-09-06T11:05:43 | {} | MEMBER |
vuejs | core | 914,289,091 | 4,394 | akibrk | Folders aren't the big issue, it's the path to the files. | 2021-09-07T13:04:22 | 2021-09-07T13:04:22 | {} | NONE |
vuejs | core | 911,697,093 | 4,496 | yyx990803 | See d7f1b771 - `vue/ref-macros.d.ts` should be manually referenced to avoid polluting globals. | 2021-09-02T13:41:20 | 2021-09-02T13:41:20 | {} | MEMBER |
vuejs | core | 912,172,633 | 4,491 | maorunjie-2019 | 
确实是vue3～～～ | 2021-09-03T01:06:32 | 2021-09-03T01:08:22 | {} | NONE |
vuejs | core | 914,129,417 | 4,533 | posva | it's `:global(.slide-menu-popover .el-menu)`. Check https://github.com/vuejs/vue-next/blob/master/packages/compiler-sfc/__tests__/compileStyle.spec.ts#L117.
Please, next time consider using the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.co... | 2021-09-07T09:06:15 | 2021-09-07T09:06:15 | {} | MEMBER |
vuejs | core | 916,129,466 | 4,543 | posva | When using suspense, it requires a single root node. So your view components must also follow that rule. | 2021-09-09T14:04:42 | 2021-09-09T14:04:42 | {} | MEMBER |
vuejs | core | 916,678,075 | 4,550 | missile-xuan | 语言表述的而不太清楚 可以项目拉下来看下 | 2021-09-10T07:00:57 | 2021-09-10T07:00:57 | {} | NONE |
vuejs | core | 916,682,709 | 629 | sh-mokong | @superkkmax
app.vue
```
<template>
<div id="app"></div>
</template>
<script>
import {createApp, onMounted} from 'vue';
import PlusMinus from '@/components/PlusMinus';
export default{
name: 'App',
components: {
},
props: {},
setup() {
onMounted(() => {
createApp(PlusMinus,{c... | 2021-09-10T07:09:17 | 2021-09-10T07:09:17 | {} | NONE |
vuejs | core | 914,431,255 | 4,432 | yyx990803 | After taking another look, I believe the runtime changes are not necessary when the compiler already outputs condensed class names, so I refactored to remove unnecessary abstractions. | 2021-09-07T16:00:55 | 2021-09-07T16:00:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 915,199,127 | 4,330 | philippevezina | Ohh great! Thanks! | 2021-09-08T12:34:10 | 2021-09-08T12:34:10 | {} | NONE |
vuejs | core | 908,821,994 | 4,294 | dwanl | 我也遇到了这个坑 | 2021-08-31T01:22:47 | 2021-09-10T11:00:44 | {} | NONE |
vuejs | core | 912,247,335 | 4,505 | code-farmer-i | I tried to compile the Sfc file into a ts file through compiler-sfc. After the compilation was completed, I found a syntax error in the ts file.
Sfc
<img width="400" src="https://user-images.githubusercontent.com/15082905/131950440-16c5f282-4e78-4a89-86d8-785dc5d74336.png">
Compile to ts
<img width="400" src=... | 2021-09-03T04:31:12 | 2021-09-03T04:31:12 | {} | NONE |
vuejs | core | 912,890,486 | 4,513 | edison1105 | Could you add a test case? | 2021-09-04T02:09:22 | 2021-09-04T02:09:22 | {} | MEMBER |
vuejs | core | 912,891,987 | 4,515 | edison1105 | @aphex is this a duplicate of https://github.com/vuejs/vue-next/pull/4503 ?
/cc @ygj6 | 2021-09-04T02:21:07 | 2021-09-04T02:21:07 | {} | MEMBER |
vuejs | core | 914,444,331 | 4,424 | yyx990803 | I was able to reproduce this: [link](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgbXNnID0gJ2hlbGxvJ1xuY29uc3QgcyA9IHJlZih7fSlcbjwvc2NyaXB0PlxuXG48dGVtcGxhdGU+XG4gIDxidXR0b24gQGNsaWNrPVwicyA9IG51bGxcIj5yZW1vdmU8L2J1dHRvbj5cbiAgPGlucHV0IHYtbW9kZWw9XCJtc2dcIiB2... | 2021-09-07T16:18:12 | 2021-09-07T16:18:12 | {
"hooray": 1
} | MEMBER |
vuejs | core | 915,623,380 | 4,537 | yyx990803 | That would bloat the production bundle by a LOT. I think what we should probably do is include an error code to message reference in the docs, which can be auto-generated.
For now you can refer to the [non-minified code](https://unpkg.com/browse/vue@3.2.10/dist/vue.esm-browser.js) (search for "errorMessages") | 2021-09-08T22:46:18 | 2021-09-08T22:46:18 | {
"+1": 2
} | MEMBER |
vuejs | core | 916,138,629 | 2,603 | cexbrayat | It used to warn but was removed (in this commit https://github.com/vuejs/vue-next/pull/2099/files#diff-56930a63772d2e89f19432918b9d6ed851ede4159b0d32404e0c1d8c159fec99L1241)
PR #3657 should fix it when merged | 2021-09-09T14:14:35 | 2021-09-09T14:14:35 | {} | MEMBER |
vuejs | core | 916,246,954 | 4,544 | yyx990803 | Sorry but this is way out of scope and not something we are supposed to fix for you. | 2021-09-09T16:19:37 | 2021-09-09T16:19:37 | {} | MEMBER |
vuejs | core | 912,235,940 | 4,478 | ghost | For anyone who has similar issues to what we had. The root cause seems to be we are including our component library with npm link: locally in the main application. Adding the following two lines to vue.config.js fixed the issue.
`config.resolve.symlinks(false)
config.resolve.alias.set( 'vue', path.resolve('./node... | 2021-09-03T03:59:30 | 2021-09-03T04:00:59 | {
"+1": 2
} | NONE |
vuejs | core | 912,245,512 | 4,504 | leboeuf | > and there's no need to do so.
@Justineo This was a contrived example, but my actual use case is a dynamically generated form. I have a list of async components:
```
// ComponentsList.js:
import { defineAsyncComponent } from 'vue'
export default {
CheckBox: defineAsyncComponent(() => import('./CheckBox... | 2021-09-03T04:25:21 | 2021-09-03T04:25:21 | {
"+1": 2
} | NONE |
vuejs | core | 912,608,462 | 4,409 | kaokei | @posva
I am also interested in this issue.
I know there were two `computed` in vue. One is inside `@vue/reactivity` and another one is inside `@vue/runtime-core`.
With the help of `EffectScope`, there is only one `computed` inside `@vue/reactivity` now.
So I am curious if there is a way to move `watch` to `... | 2021-09-03T15:07:27 | 2021-09-03T15:08:25 | {} | NONE |
vuejs | core | 913,231,053 | 4,516 | yyx990803 | There's currently no API to do this. For now wrapping the app's `unmount` function would probably be the cleanest way to do it. | 2021-09-05T21:32:51 | 2021-09-05T21:32:51 | {} | MEMBER |
vuejs | core | 914,294,558 | 4,370 | akibrk | Any update on this? | 2021-09-07T13:11:51 | 2021-09-07T13:11:51 | {} | NONE |
vuejs | core | 915,768,728 | 4,538 | yzx9 | See [here](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0040-script-setup.md#automatic-name-inference)
```ts
<script>
export default {
name: 'componentName'
}
</script>
<script setup>
// script setup logic
</script>
```
| 2021-09-09T05:12:10 | 2021-09-09T05:12:10 | {
"+1": 1,
"-1": 1
} | NONE |
vuejs | core | 916,058,446 | 4,543 | linbuxiao | When I add another parent element to `<Suspense>` like this, the error disappears and I would like to know why:
```html
<suspense>
<div> <------ parent element fix the error.
<router-view></router-view>
</div>
</suspense>
``` | 2021-09-09T12:45:30 | 2021-09-09T12:45:30 | {} | NONE |
vuejs | core | 916,586,997 | 4,547 | tjk | If I disable the server render, the patching works fine. Otherwise, the vnodes under `thead` have `null` `el`. | 2021-09-10T02:41:46 | 2021-09-10T02:41:46 | {} | CONTRIBUTOR |
vuejs | core | 916,724,284 | 4,550 | missile-xuan | Look at this
看看这个
I modified it
[SFC](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG5cbmNvbnN0IGFyciA9IHJlZihbeyBrZXk6IDAgfSwgeyBrZXk6IDEgfV0pXG5cblxuZnVuY3Rpb24gbG9nKGkpIHtcbiAgY29uc29sZS5sb2coJ2NyZWF0ZWQnLCBpKVxufVxuICBzZX... | 2021-09-10T08:21:11 | 2021-09-10T08:21:11 | {} | NONE |
vuejs | core | 912,239,341 | 4,504 | Justineo | It is expected. Without the `components` option you don't have a chance to give the component a local name (string) and there's no need to do so. | 2021-09-03T04:08:11 | 2021-09-03T04:08:11 | {} | MEMBER |
vuejs | core | 912,288,836 | 4,505 | LinusBorg | Semicolons are valid in Type declarations (even though not commonly used in my experience), so this should be rated as a bug | 2021-09-03T06:21:39 | 2021-09-03T06:21:39 | {
"+1": 3
} | MEMBER |
vuejs | core | 912,826,135 | 4,394 | tayyab-developer | You have to create these folders by yourself. | 2021-09-03T21:42:41 | 2021-09-03T21:42:41 | {} | NONE |
vuejs | core | 913,251,595 | 3,870 | lijialiang | I have a question in the process of using it, can I avoid hydrate and only render the renderToString output? | 2021-09-06T00:04:51 | 2021-09-06T00:04:51 | {} | NONE |
vuejs | core | 913,542,979 | 4,423 | henribru | @edison1105 I did update both dependencies, actually.
If Nisgrak's repo no longer reproduces the issue I can attempt to make another one later today | 2021-09-06T10:37:01 | 2021-09-06T10:37:01 | {} | NONE |
vuejs | core | 915,052,807 | 4,427 | zhangenming | > This affects a number of `async setup()` test cases where they are intentionally `async` without using `await`.
maybe...so what to do next...
just close this pr? or Do some modifications...
| 2021-09-08T09:02:16 | 2021-09-08T09:02:16 | {} | CONTRIBUTOR |
vuejs | core | 916,254,433 | 4,541 | yyx990803 | Thanks for the PR, but in fact with a dynamic key the key node can be any expression type. See more complete fix in a6e5f82d | 2021-09-09T16:29:50 | 2021-09-09T16:29:50 | {} | MEMBER |
vuejs | core | 916,817,865 | 4,548 | qmhc | @Bigfish8 Thanks for your reply.
```vue
<script setup lang="ts">
type Props = {
color: 'blue' | 'red' | 'purple'
}
const props = defineProps<Props>()
</script>
```
After parse then got the following:
![image](https://user-images.githubusercontent.com/40221744/132843525-cdff32de-686f-4e2b-85d7-2d2c9c... | 2021-09-10T11:00:34 | 2021-09-10T11:00:55 | {
"+1": 1
} | NONE |
vuejs | core | 916,888,388 | 4,552 | posva | cc @johnsoncodehk I suppose | 2021-09-10T13:04:22 | 2021-09-10T13:04:22 | {
"eyes": 1
} | MEMBER |
vuejs | core | 912,557,415 | 4,510 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4505 | 2021-09-03T13:53:41 | 2021-09-03T13:53:41 | {} | MEMBER |
vuejs | core | 912,627,569 | 4,344 | ghost | Using the npm link is the primary reason as the host application would try to use the vue from the linked library. Add these two lines to the vue.config.js of the host application.
```
chainWebpack(config) {
config.resolve.symlinks(false)
config.resolve.alias.set( 'vue', path.resolve('./node_modules/vue... | 2021-09-03T15:36:28 | 2021-09-03T15:36:28 | {
"+1": 20,
"hooray": 6,
"rocket": 2
} | NONE |
vuejs | core | 912,981,499 | 4,521 | LinusBorg | that's because you're not keying the list elements, and also don't react to the props change of the `element` prop (you initially copy it to `localIndex`, subsequent props changes will stay without effect).
https://v3.vuejs.org/guide/list.html#maintaining-state | 2021-09-04T14:14:20 | 2021-09-04T14:24:19 | {} | MEMBER |
vuejs | core | 913,538,339 | 4,423 | edison1105 | @henribru you should update `@vue/compiler-sfc` to '3.2.9' | 2021-09-06T10:29:35 | 2021-09-06T10:29:35 | {} | MEMBER |
vuejs | core | 913,823,794 | 3,630 | yyx990803 | While this results in shorter URLs, lzutf8 seems pretty heavy for this purpose (35kb minified). I don't think the long URLs cause any intrinsic problems so it doesn't seem to be worth it. | 2021-09-06T19:29:40 | 2021-09-06T19:29:40 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.