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 | 974,574,329 | 4,977 | ygj6 | duplicate of #2431 | 2021-11-20T02:03:07 | 2021-11-20T02:03:07 | {} | MEMBER |
vuejs | core | 968,315,192 | 4,339 | nandongdong | Looking forward to this feature. | 2021-11-14T15:43:52 | 2021-11-14T15:43:52 | {
"+1": 1
} | NONE |
vuejs | core | 968,334,393 | 4,944 | scottbedard | Closing, looks like a duplicate of https://github.com/vuejs/vue-next/issues/4783 and I expect will be fixed with the next patch release. | 2021-11-14T17:40:13 | 2021-11-14T17:40:13 | {} | CONTRIBUTOR |
vuejs | core | 971,384,192 | 4,955 | posva | Thanks but this wouldn't work for library custom components like RouterView or RouterLink in vue router. It would also be great to add a d-ts test to check for externally added components | 2021-11-17T09:15:18 | 2021-11-17T09:15:18 | {
"+1": 1
} | MEMBER |
vuejs | core | 972,040,550 | 4,955 | yuwu9145 | d-ts test has been added, without changes in this pull request, it will fail | 2021-11-17T21:15:22 | 2021-11-17T21:15:22 | {} | CONTRIBUTOR |
vuejs | core | 974,634,304 | 4,874 | LinusBorg | You can make it even shorter when using a functional component:
https://stackblitz.com/edit/vue-tv16yo?file=src%2Fmain.js | 2021-11-20T11:16:30 | 2021-11-20T11:16:30 | {
"heart": 1
} | MEMBER |
vuejs | core | 974,970,983 | 4,980 | wxsms | Okay. I see. thank you! | 2021-11-22T00:56:23 | 2021-11-22T00:56:23 | {} | MEMBER |
vuejs | core | 969,049,444 | 4,887 | batuotasis | any progress on this? | 2021-11-15T15:53:53 | 2021-11-15T15:53:53 | {} | NONE |
vuejs | core | 969,706,485 | 4,887 | yyx990803 | To check TS in `<script setup>`, you currently have to use `vue-tsc` in a separate process.
The CLI setup uses `ts-loader`, which handles Vue type checking support, but AFAIK it doesn't support `<script setup>` atm.
For the future, we no longer recommend type-checking as part of the bundler pipeline because it ha... | 2021-11-16T02:30:11 | 2021-11-16T02:30:11 | {} | MEMBER |
vuejs | core | 972,116,850 | 4,960 | mrts | Alright, but can we make the developer experience better in some other way? Should using `Promise.then()` be documented as the recommended solution to this common problem? | 2021-11-17T22:00:29 | 2021-11-17T22:00:29 | {} | NONE |
vuejs | core | 972,111,330 | 4,960 | posva | This is inherent to the language, in your scenario, using a Promise is the right approach, even inside of `setup()`:
```js
async setup() {
data.value = await stuff()
return { data }
}
```
is different from
```js
setup() {
stuff().then(d = > data.value = d)
return { data }
}
```
Magically ... | 2021-11-17T21:56:49 | 2021-11-17T22:17:47 | {} | MEMBER |
vuejs | core | 925,702,475 | 4,566 | cyfung1031 | > You need to use the `.native` modifier.
He is using vue3 not vue2. | 2021-09-23T10:51:09 | 2021-11-20T16:04:01 | {} | NONE |
vuejs | core | 974,803,334 | 4,981 | edison1105 | see https://github.com/vuejs/vue-next/pull/408 | 2021-11-21T11:59:02 | 2021-11-21T11:59:38 | {} | MEMBER |
vuejs | core | 966,737,031 | 4,930 | languanghao | @LinusBorg Thank you for your reply.
Sometimes call `expose()` before any top level `await` calls will make code logic strange as I replied before. The exposed fuction invkoe var which defined in setup is very normal.
Consider `exposed` function need invoke a var which created by an async function, then we only h... | 2021-11-12T01:07:40 | 2021-11-12T01:07:40 | {} | NONE |
vuejs | core | 967,088,400 | 4,936 | LinusBorg | I don't see a problem. If you correctly type your props like this, there's no problem:
```ts
type Foo = { bar: string };
```
reactive data is unwrapped, so the interface of the object it returns does not contain `Ref` - why do you want to use it, then? | 2021-11-12T12:41:18 | 2021-11-12T12:44:20 | {} | MEMBER |
vuejs | core | 967,102,602 | 4,936 | sxzz | I see. Thank you very much. | 2021-11-12T13:02:15 | 2021-11-12T13:02:15 | {} | MEMBER |
vuejs | core | 968,182,152 | 4,942 | edison1105 | as a workaround
```javascript
<teleport to="body">
<span key="1">
This text is teleported and will be duplicated.
</span>
</teleport>
```
maybe should force bail out of optimize mode
![image](https://user-images.githubusercontent.com/3705199/141663348-c158c2ec-d93c-41a0-a... | 2021-11-14T00:43:46 | 2021-11-14T11:09:47 | {} | MEMBER |
vuejs | core | 968,977,183 | 4,949 | posva | You need to run https://github.com/vuejs/vue-next/blob/master/package.json#L25 first | 2021-11-15T14:41:23 | 2021-11-15T14:41:23 | {} | MEMBER |
vuejs | core | 970,861,525 | 4,294 | cdvillard | Despite a fairly similar setup to @phasetri's issue, I'm finding that the properties of the interface I'm trying to import resolve as `attrs` instead of `props`, which breaks what I see as expected and predictable functionality.
Control example:
```vue
<script setup lang="ts">
interface IThingie {
serial: str... | 2021-11-16T23:46:05 | 2021-11-16T23:52:47 | {
"+1": 64,
"eyes": 2,
"rocket": 1
} | NONE |
vuejs | core | 972,608,245 | 593 | wisetc | vue2 in nuxt, 为何调用根结点的 `vm.$destroy()` 方法只能销毁vm, 却不能从DOM中移除mount 的DOM? | 2021-11-18T07:33:47 | 2021-11-18T07:33:47 | {} | NONE |
vuejs | core | 973,149,198 | 4,968 | posva | Until this is supported, use `import type { Ref } from 'vue'` | 2021-11-18T18:37:36 | 2021-11-18T18:37:36 | {} | MEMBER |
vuejs | core | 973,655,912 | 4,339 | huangqian0310 | 大概在之后哪个版本可以正式用上他呢 | 2021-11-19T01:56:00 | 2021-11-19T01:56:00 | {
"+1": 4
} | NONE |
vuejs | core | 973,666,091 | 4,963 | guaijie | > 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).
Isn't this a feature request.
I put all my suggestio... | 2021-11-19T02:18:47 | 2021-11-19T02:18:47 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 973,841,145 | 3,238 | HcySunYang | Raise a new PR to fix this. | 2021-11-19T07:56:05 | 2021-11-19T07:56:05 | {} | MEMBER |
vuejs | core | 973,992,132 | 4,971 | posva | I would expect to both `reactive({ nested })` and `reactive({}).nested = nested` to work the same way with `nested = reactive({})` 🤔
I can do `toRaw(store).nested = nested` though but [it won't be observed](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgcmVhY3RpdmUsIHRvUmF3LCBpc1JlY... | 2021-11-19T11:28:25 | 2021-11-19T11:31:21 | {} | MEMBER |
vuejs | core | 974,898,014 | 4,980 | LinusBorg | It's not really meant to be used with render functions, and most of the advantages of `script setup` are already a given when using a render function in a normal Component
* no need to return all those properties from setup, everything's already in the closure
* no need to register components
all you are left wi... | 2021-11-21T21:21:12 | 2021-11-21T21:22:31 | {} | MEMBER |
vuejs | core | 967,073,027 | 4,936 | sxzz | How about using `UnwrapRef` to wrap `props` to avoid this problem? Then, we can get correct type. | 2021-11-12T12:25:54 | 2021-11-12T12:25:54 | {} | MEMBER |
vuejs | core | 967,097,508 | 4,936 | LinusBorg | The whole point of `reactive()` unwrapping nested refs (insofar as types are concerned) is so you can have a type like `{ bar: string}` and don't need a type of `{bar: Ref<string>}`
Your component clearly expects a prop called `foo` containing an object with an interface of `{bar: string}`, because you expect that ... | 2021-11-12T12:52:50 | 2021-11-12T14:15:22 | {} | MEMBER |
vuejs | core | 970,141,226 | 4,952 | xflyyxfl | > Additionally, this would be a breaking change, which we won't do.
Did you really think of this, I have change the vue.global.js as I thought while all goes well as far. My applycation contains about 254 Vue instances .(with elementPlus). just change one line code here:
```
exp = createCompoundExpression([
... | 2021-11-16T10:39:08 | 2021-11-16T10:39:08 | {} | NONE |
vuejs | core | 925,704,276 | 4,566 | cyfung1031 | > 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 | 2021-09-23T10:54:10 | 2021-11-20T16:02:49 | {} | NONE |
vuejs | core | 974,732,773 | 4,950 | yuwu9145 | > @yuwu9145 What about custom components that use `$props` ?
based on my testing, custom component type still works. I also think ultimately it should be user's responsibility of making sure their custom component type serve as legitimate `Component`
![image](https://user-images.githubusercontent.com/5698884/1427... | 2021-11-21T00:35:37 | 2021-11-21T01:27:01 | {} | CONTRIBUTOR |
vuejs | core | 966,908,470 | 4,937 | posva | as @ygj6 pointed out, you need to provide valid values. Your code is throwing an error in development mode and it should not be overlooked. In production mode some optimizations take place for better performance and **if you let errors pass through during development** you cannot expect your application to work normall... | 2021-11-12T08:15:57 | 2021-11-12T08:15:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 966,919,360 | 4,939 | zhaozhongyu | > 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).
So, how can i create a demo in https://sfc.vuejs.org/ and import vue-class-component?
see: ... | 2021-11-12T08:35:02 | 2021-11-12T08:35:47 | {} | NONE |
vuejs | core | 967,771,555 | 4,662 | lucasantunes-ciandt | @raffobaffo Exactly! In our case we're using Vue inside a CMS, so we'll be only exporting custom elements to use within it instead of creating a Vue app, so we'll definitely keep that part because we need some external styles and even scripts from the CMS to be injected into the elements. | 2021-11-13T03:27:30 | 2021-11-13T03:27:30 | {
"+1": 1
} | NONE |
vuejs | core | 969,067,726 | 4,946 | TatsuyaYamamoto | @posva Thank you for your comment.
I understood that `toNumber()` has a migration concern.
What do you think of the idea of defining `toNumber()` in [apiCustomElement.ts](https://github.com/vuejs/vue-next/blob/master/packages/runtime-dom/src/apiCustomElement.ts) to improve the behavior of parsing without worrying ... | 2021-11-15T16:11:48 | 2021-11-15T16:11:48 | {} | NONE |
vuejs | core | 925,719,634 | 4,566 | LinusBorg | Vite has nothing to do with this question. | 2021-09-23T11:18:06 | 2021-11-20T16:02:42 | {} | MEMBER |
vuejs | core | 925,702,035 | 4,566 | cyfung1031 | > Oh, but in the documents, it says to remove all .natives? confused
> https://v3.vuejs.org/guide/migration/v-on-native-modifier-removed.html#_2-x-syntax
> I also get this huge error in my real project to actually remove .native.
> ![image](https://user-images.githubusercontent.com/8193841/132996027-da19adcb-095d-41... | 2021-09-23T10:50:26 | 2021-11-20T16:03:52 | {} | NONE |
vuejs | core | 968,977,956 | 4,948 | posva | Please open a discussion or PR in the vuejs/rfcs repository for this. | 2021-11-15T14:42:12 | 2021-11-15T14:42:12 | {
"+1": 1
} | MEMBER |
vuejs | core | 974,823,639 | 4,980 | wxsms | Thanks. It may not be a proper space to ask for, but is there any way to use render function with script-setup though? It seems not mentioned from document. | 2021-11-21T14:05:00 | 2021-11-21T14:18:38 | {
"+1": 3
} | MEMBER |
vuejs | core | 755,250,639 | 2,944 | glen-84 | > I assume it can also be TypeScript/CoffeeScript in there?
As far as I know (and I could be wrong), it's limited to JavaScript.
---
> So, can we close this now as we don't see a way to effienctly detect this?
HTML likely avoids attempting to parse the contents of script elements, because it could be any la... | 2021-01-06T11:38:41 | 2021-01-06T11:38:41 | {} | NONE |
vuejs | core | 756,693,277 | 2,969 | posva | It looks like emitting events or hooking into the equivalent of `@hook:created` or similar would also work | 2021-01-08T10:58:55 | 2021-01-08T10:58:55 | {} | MEMBER |
vuejs | core | 757,185,176 | 2,972 | LinusBorg | The issue isn't really the reactivity of the array, as the child does correctly update hwne the array is changed - can be verified by loggind to console in `onUpdated()`.
Rather, the generated render function is buggy - it adds a patch flag that seems to make the child component skip the update of that node, even th... | 2021-01-09T13:24:40 | 2021-01-09T13:24:40 | {} | MEMBER |
vuejs | core | 757,453,934 | 2,944 | jods4 | That's rather bad and closing doesn't feel like the right thing to do to me.
AFAIK:
- expressions in template can _only_ be JS, no other language allowed.
- `compiler-sfc` already embeds a JS parser, namely Babel.
So when encountering a `{{` interpolation marker, why not parse a JS expression starting on next c... | 2021-01-10T10:41:21 | 2021-01-10T10:41:21 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 757,459,276 | 2,981 | LinusBorg | This is a pretty bad caveat stemming from a combination of things:
This is a limitation in Typescript, when using private properties in classes the Unwrapping that reactivity is doing:
- For TS, the private `baz` property is part of the `Foo` type,even though it's private.
- When `Foo` is being unwrapped, the re... | 2021-01-10T11:21:02 | 2021-01-11T09:00:58 | {
"+1": 9
} | MEMBER |
vuejs | core | 758,617,667 | 2,993 | edison1105 | see https://github.com/vuejs/vue-next/issues/2966 | 2021-01-12T12:15:04 | 2021-01-12T12:15:04 | {
"+1": 1
} | MEMBER |
vuejs | core | 759,172,678 | 2,995 | HcySunYang | Use `h` to wrap it:
```js
function Button() {
return h(defineComponent({
render() {
return h('div', 'test');
},
}))
}
```
Or:
```js
const MyComp = defineComponent({
render() {
return h('div', 'test');
},
})
function Button() {
return <MyComp />
}
``` | 2021-01-13T03:02:31 | 2021-01-13T03:02:31 | {
"+1": 3,
"-1": 3
} | MEMBER |
vuejs | core | 755,159,194 | 2,952 | HcySunYang | the reactive means that it will collect effects as dependencies, the readonly means that its value cannot be modified. When reading a readonly data, it can still collect effects, in this scenario, it is both reactive and readonly.
Consider this:
```js
const a = reactive({ foo: 1 })
const b = readonly(a)
effe... | 2021-01-06T08:27:33 | 2021-01-06T08:27:33 | {
"+1": 2
} | MEMBER |
vuejs | core | 756,052,007 | 2,929 | posva | I think it's good but I'm not sure, that's why I didn't review it 😅
It looks a bit weird to pass isSVG as a parameter because it might not be the only kind of element needing a specific check, but this could also be refactored in the future with an enum if multiple types checks are needed | 2021-01-07T11:12:48 | 2021-01-07T11:12:48 | {} | MEMBER |
vuejs | core | 756,282,834 | 2,964 | LinusBorg | That has to be solved in Webstorm, not the vue runtime.
You can see how Vetur does it for VSCode - The developers of Webstorm would have to provide some similar config options:
https://vuejs.github.io/vetur/guide/global-components.html#example | 2021-01-07T18:04:38 | 2021-01-07T18:04:38 | {} | MEMBER |
vuejs | core | 757,156,668 | 1,790 | nandin-borjigin | @posva Please tell me if I should create a new issue instead of commenting here.
---
I'm facing same problem and wondering if this usecase justifies this optimization:
## Goal:
To have an `Async` component that accepts an async value and uses `Suspense` to handle that value properly.
## Typical usage
```
... | 2021-01-09T12:53:47 | 2021-01-09T13:17:55 | {} | NONE |
vuejs | core | 757,418,411 | 2,973 | HcySunYang | The `compileScript` has already thrown an error for this:
| 2021-01-10T05:16:29 | 2021-01-10T05:16:29 | {} | MEMBER |
vuejs | core | 757,518,492 | 2,380 | jods4 | I wonder how that would work.
By essence `markRaw` means: don't put this into a proxy, so I don't see how it would be able to intercept everything that's put into it to mark it as well? | 2021-01-10T18:09:28 | 2021-01-10T18:09:28 | {} | CONTRIBUTOR |
vuejs | core | 757,730,082 | 2,986 | posva | You are passing the refs directly to `logIn` instead of the values:
```js
const onLogIn = () => {
logIn(username.value, password.value)
}
```
| 2021-01-11T08:42:20 | 2021-01-11T08:42:20 | {} | MEMBER |
vuejs | core | 758,440,562 | 2,991 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-12T06:37:29 | 2021-01-12T06:37:29 | {} | NONE |
vuejs | core | 758,412,684 | 2,843 | lijingfaatcumt | > PR submitted, happy to get reviews.
@LinusBorg in you code of pr, i found some improve, i think should modify below
```javascript
export function reactive(target: object) {
return createReactiveObject(
target,
false,
mutableHandlers,
mutableCollectionHandlers,
reactiveMap
)
}
f... | 2021-01-12T05:29:16 | 2021-01-12T06:59:20 | {} | NONE |
vuejs | core | 759,391,098 | 2,999 | 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-01-13T11:34:55 | 2021-01-13T11:34:55 | {} | MEMBER |
vuejs | core | 755,918,122 | 2,959 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-07T06:35:45 | 2021-01-07T06:35:45 | {} | NONE |
vuejs | core | 757,519,865 | 2,380 | jods4 | BTW I'm not sure what is the exact use case here.
The built-in `deep` watch means: when anything reactive in that state graph, at any level, changes, then run the watch again.
If you want something more specialized, e.g. maybe just 1 or 2 level deep, or to any other arbitrary condition (e.g. the object is marked as... | 2021-01-10T18:17:40 | 2021-01-10T18:17:40 | {} | CONTRIBUTOR |
vuejs | core | 757,635,587 | 2,710 | Adeelasd | any update? | 2021-01-11T05:42:01 | 2021-01-11T05:42:01 | {} | NONE |
vuejs | core | 759,239,604 | 2,997 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-13T06:36:50 | 2021-01-13T06:36:50 | {} | NONE |
vuejs | core | 755,188,957 | 2,951 | LinusBorg | The use of that piece of code is explained in the comment directly above it. | 2021-01-06T09:31:03 | 2021-01-06T09:31:03 | {} | MEMBER |
vuejs | core | 755,202,418 | 2,929 | LinusBorg | @posva can this be approved now? | 2021-01-06T09:57:13 | 2021-01-06T09:57:13 | {} | MEMBER |
vuejs | core | 755,203,060 | 2,909 | LinusBorg | @Akryum Tagged you for a review as that hook is for devtools. I think it's safe to remove it here. Agree? | 2021-01-06T09:58:23 | 2021-01-06T09:58:23 | {} | MEMBER |
vuejs | core | 755,950,599 | 2,961 | jw-foss | True, it's the same issue. | 2021-01-07T07:55:21 | 2021-01-07T07:55:21 | {} | NONE |
vuejs | core | 756,992,166 | 2,116 | WesleyKapow | `[...array]` approach is working for me. I'd suggest adding a note about this in the docs. It was definitely not obvious that watching an array does not watch adds/removes. | 2021-01-08T20:51:04 | 2021-01-08T20:51:04 | {
"+1": 3
} | NONE |
vuejs | core | 757,329,264 | 2,972 | HcySunYang | ```js
"bindings": {
"VueNext": "setup-const",
"ref": "setup-const",
"reactive": "setup-const",
"provide": "setup-const",
"watchEffect": "setup-const",
"cars": "setup-const",
"pens": "setup-const",
"receivedData": "setup-const", // Caused by here
"receiveHandler": "setup-con... | 2021-01-09T16:17:49 | 2021-01-09T16:17:49 | {
"+1": 2
} | MEMBER |
vuejs | core | 758,624,289 | 2,993 | chemist-repo | This will lead to more time consuming migration. And it doesn't look normal.
`inheritAttrs: false` - this really works, but it partially solves the problem, I may want to keep which attributes and rename which other. | 2021-01-12T12:28:32 | 2021-01-12T12:28:32 | {} | NONE |
vuejs | core | 758,727,605 | 2,944 | jods4 | > 3.x compatible tools are using the same parser, so they can offer some options for this. (vite, rollup-plugin-vue, vue-loader already have this).
I guess and they're all build tools using `compiler-sfc`.
I was rather thinking of Vetur / IDE support.
And of course I guess this isn't supported either by JIT temp... | 2021-01-12T15:21:27 | 2021-01-12T15:21:27 | {} | CONTRIBUTOR |
vuejs | core | 759,322,943 | 2,998 | edison1105 | maybe you can use color name instead hex-color: https://developer.mozilla.org/en-US/docs/Web/CSS/color_value | 2021-01-13T09:28:40 | 2021-01-13T09:28:40 | {
"+1": 2
} | MEMBER |
vuejs | core | 759,335,689 | 2,999 | edison1105 | I think this is not relate to `vue` or `vue-router`.
you should find out which plugin cause that. | 2021-01-13T09:51:28 | 2021-01-13T09:52:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 756,589,342 | 2,967 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.51 KB (0%) |
| runtime-dom.global.prod.js | 26.83 KB (0%) |
| size-check.global.prod.js | 16.21 KB (0%) | | 2021-01-08T07:04:22 | 2021-01-08T07:04:22 | {} | NONE |
vuejs | core | 757,932,592 | 2,973 | jods4 | Quick heads-up: I can confirm my real project still goes in an infinite loop in Vite when I change the correct `definEmit` for this bad guy:
```ts
const emits = defineEmit<{ showRevision(e: 'showRevision', sha: string): void }>();
```
As that doesn't seem to be sufficient I'll try to work out a repro if I have th... | 2021-01-11T12:52:25 | 2021-01-11T12:52:25 | {} | CONTRIBUTOR |
vuejs | core | 758,619,947 | 2,993 | Mr14huashao | The child-component contains a click event,
The parent-component transfers a click event to the child component.
Two responses are correct.
One is the event of the parent-component,
and the other is the child-component invokes the parent-component method and prints 'test-click'.
``<button @click="$emit('click', ... | 2021-01-12T12:19:24 | 2021-01-12T12:19:24 | {} | NONE |
vuejs | core | 759,239,199 | 2,996 | LinusBorg | Use chat.vuejs.org for questions please. | 2021-01-13T06:35:53 | 2021-01-13T06:35:53 | {} | MEMBER |
vuejs | core | 755,213,530 | 2,944 | LinusBorg | So, can we close this now as we don't see a way to effienctly detect this? | 2021-01-06T10:18:14 | 2021-01-06T10:18:14 | {} | MEMBER |
vuejs | core | 755,949,185 | 2,961 | edison1105 | I think it's dumplicate of #2757 | 2021-01-07T07:52:05 | 2021-01-07T07:52:05 | {} | MEMBER |
vuejs | core | 755,997,902 | 2,961 | posva | Duplicate of #2757 | 2021-01-07T09:30:47 | 2021-01-07T09:30:47 | {} | MEMBER |
vuejs | core | 756,485,750 | 2,957 | lijingfaatcumt | > If you are submitting a fix, can you add a test that failed before and now passes?
no, originally i want to mention a bug, but this is not a bug,so the bug i mentioned is closed | 2021-01-08T01:18:34 | 2021-01-08T01:19:09 | {} | NONE |
vuejs | core | 757,304,756 | 2,293 | cobalamin | It took me a long time to figure out that this is what was killing performance in my app.
I am rendering ~3000 custom components (each rendering one SVG element) via `v-for` and had a `v-show` directive on the same elements that rendered via `v-for`. Clearly having that `v-show` leads the check (which @skirtles-code... | 2021-01-09T15:17:45 | 2021-01-09T19:11:33 | {} | NONE |
vuejs | core | 757,657,848 | 2,710 | knightly-bot | <!--KNIGHTLY-BUILD-ENABLED-->
[](https://github.com/knightlyjs/knightly)
🌒 Knightly build enabled, release every night at 00:00 UTC <sup>(skip if no change)</sup>
📦 [npm package](https://www.npmjs.com/package/@knightly/vue/v/p... | 2021-01-11T06:45:36 | 2021-01-11T06:45:36 | {
"hooray": 1
} | NONE |
vuejs | core | 758,625,862 | 2,944 | jods4 | OK, I understand why you don't want to include an extra 60K gzip of `@babel/parser` just for this edge case.
You could if you wanted, still take advantage of the parser in AOT but that creates discrepancies between the two modes for things that are rare edge cases.
You could make the parser opt-in in JIT, but that'... | 2021-01-12T12:31:59 | 2021-01-12T12:33:42 | {} | CONTRIBUTOR |
vuejs | core | 756,609,533 | 2,966 | gitHber | > See https://v3.vuejs.org/guide/component-attrs.html#attribute-inheritance
Thanks for reply, That would be great, We don't have to duplicate redeclare props from other component | 2021-01-08T07:58:13 | 2021-01-08T07:58:13 | {} | NONE |
vuejs | core | 757,742,361 | 2,973 | posva | Closing in favor of https://github.com/vuejs/vue-next/issues/2983 since this one has no reproduction | 2021-01-11T08:51:13 | 2021-01-11T08:51:13 | {} | MEMBER |
vuejs | core | 758,613,767 | 2,944 | jods4 | Slight out of topic digression, please skip if you're here for the `}}`
> compiler allows additional plugins for JS expression parsing, so you can use any language supported by @babel/parser (TypeScript and Flow are supported).
How does it work exactly?
- The expression itself isn't parsed, but is copied verbati... | 2021-01-12T12:07:07 | 2021-01-12T12:07:07 | {} | CONTRIBUTOR |
vuejs | core | 755,212,956 | 2,639 | LinusBorg | @znck this PR ha aged a bit. is it still vaild? Should we let some of the jsx maintainers have a look? | 2021-01-06T10:16:57 | 2021-01-06T10:16:57 | {} | MEMBER |
vuejs | core | 755,215,688 | 2,949 | LinusBorg | This is expected behaviour. As the store effectively gets created within `setup`, all of the watchers and effects are bound to that instance. When that instance gets destroyed, the effects get cleaned up.
We intend to ship a new feature to solve this usecase, which would also be required for Vuex 5 - you can read up... | 2021-01-06T10:22:34 | 2021-01-06T10:22:34 | {} | MEMBER |
vuejs | core | 755,265,682 | 2,116 | LinusBorg | @yyx990803 I would propose to close this and leave the behaviour as is. WDYT? | 2021-01-06T12:13:56 | 2021-01-06T12:13:56 | {} | MEMBER |
vuejs | core | 755,934,616 | 2,961 | jw-foss | BTW:
Worked in `3.0.3` after `3.0.4` it's broken. | 2021-01-07T07:17:20 | 2021-01-07T07:17:20 | {} | NONE |
vuejs | core | 757,372,176 | 2,977 | LinusBorg | I don't speak Spanish, but that github repo doesn't use a transition-group anywhere. | 2021-01-09T21:47:37 | 2021-01-09T21:47:37 | {} | MEMBER |
vuejs | core | 757,455,130 | 2,973 | jods4 | I tried to create a minimal repro and indeed, I observed the same error as @HcySunYang. I guess I'll have to find out why in my real project it goes into an infinite loop.
Just commenting out the bad `defineEmit` fixes it but there must be something else required to trigger the bug.
I'll post here if I find out what... | 2021-01-10T10:49:00 | 2021-01-10T10:49:00 | {} | CONTRIBUTOR |
vuejs | core | 757,642,127 | 2,710 | ghost | > any update?
https://github.com/vitejs/vite works with PostCSS 8 (alternative to `@vue/cli`) | 2021-01-11T06:01:53 | 2021-01-11T06:01:53 | {
"eyes": 2
} | NONE |
vuejs | core | 755,194,867 | 2,954 | LinusBorg | Please provide a reproduction. | 2021-01-06T09:42:44 | 2021-01-06T09:42:44 | {} | MEMBER |
vuejs | core | 755,816,085 | 2,956 | lijingfaatcumt | i think the code above i mentinoned is useless, because in function createReactiveObject will solve the situation that if trying to observe a readonly proxy, return the readonly version, becasuse in createReactiveObject , except readonly() on a reactive object,
as long as the target is a proxy, the function createReac... | 2021-01-07T00:59:20 | 2021-01-07T00:59:20 | {} | NONE |
vuejs | core | 756,047,583 | 2,957 | posva | If you are submitting a fix, can you add a test that failed before and now passes? | 2021-01-07T11:03:34 | 2021-01-07T11:03:34 | {} | MEMBER |
vuejs | core | 757,614,328 | 2,973 | HcySunYang | I think the `TSMethodSignature` syntax(`{ a(n: number): void }`) can be supported like https://github.com/vuejs/vue-next/pull/2984 | 2021-01-11T04:12:24 | 2021-01-11T04:12:24 | {} | MEMBER |
vuejs | core | 757,754,835 | 2,973 | LinusBorg | @posva This issue here is about `defineEmit`, while #2983 is about `defineProps`, I think we should reopen this one again. | 2021-01-11T09:00:06 | 2021-01-11T09:00:06 | {
"+1": 1
} | MEMBER |
vuejs | core | 757,757,302 | 2,860 | uimijs | 你只需要在构建中删除defineComponent
`code.replace(/(vue.)*defineComponent\(/gi, "/*#__defineComponent__*/(")`
| 2021-01-11T09:01:52 | 2021-01-11T09:02:44 | {} | NONE |
vuejs | core | 757,766,537 | 2,975 | posva | This looks good but I wonder if it makes sense to allow numbers at all for keys with `inject`/`provide` | 2021-01-11T09:10:06 | 2021-01-11T09:10:06 | {} | MEMBER |
vuejs | core | 755,308,106 | 2,955 | HcySunYang | Remove the `:disabled="true"` | 2021-01-06T13:47:57 | 2021-01-06T13:47:57 | {} | MEMBER |
vuejs | core | 755,427,657 | 2,944 | longlho | I think we can close this once the docs has been updated since that seems to be the consensus for the action item here (so we can link from the formatjs side as well). | 2021-01-06T17:00:10 | 2021-01-06T17:00:10 | {
"+1": 1
} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.