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 | 850,664,771 | 3,840 | yyx990803 | Manual `render` function should use `this.$slots`, `this.$attrs` etc. The arguments are for compiler-generated render functions only. | 2021-05-28T20:54:01 | 2021-05-28T20:54:01 | {} | MEMBER |
vuejs | core | 850,770,948 | 3,843 | HcySunYang | 重新给一个重现链接，你这个链接不好使 | 2021-05-29T05:03:56 | 2021-05-29T05:03:56 | {} | MEMBER |
vuejs | core | 846,705,697 | 3,807 | HcySunYang | Closed, duplicate of #3808 | 2021-05-24T03:26:25 | 2021-05-24T03:26:25 | {} | MEMBER |
vuejs | core | 846,706,299 | 3,811 | hearsay316 | > @hearsay316 我仍然无法复现问题，你看看你安装的 Vue 是什么版本的，可以更新到最新版本，我这边在 3.0.11 和 3.1.0-beta.3 下都没问题
我更新以后,打包就好了. 感谢!!!
| 2021-05-24T03:28:24 | 2021-05-24T03:28:24 | {} | NONE |
vuejs | core | 846,742,680 | 2,603 | tvkit | > You have to use Suspense on the parent (App.vue) of hello world.
@posva what about detecting that a Promise was returned, and then await automatically? What's the downside to that?
| 2021-05-24T05:12:37 | 2021-05-24T05:12:37 | {} | NONE |
vuejs | core | 847,324,786 | 3,537 | yyx990803 | Turns out we should not be hoisting when targeting SSR at all. See 3ef1fcc8 | 2021-05-24T20:49:07 | 2021-05-24T20:49:07 | {} | MEMBER |
vuejs | core | 846,871,462 | 3,695 | white-007 | Please fixed this problem, thank you! | 2021-05-24T08:22:14 | 2021-05-24T22:11:06 | {} | NONE |
vuejs | core | 847,476,245 | 1,600 | antoniandre | @yyx990803,
It's really awesome to see this PR merged in! :tada:
But I still can't figure out a way to preserve whitespaces using vue-cli 4.
I've tried to add this in the vue.config.js, like in Vue 2 (https://github.com/vuejs/vue/issues/10485#issuecomment-528729861):
```js
chainWebpack: config => {
config.m... | 2021-05-25T02:08:27 | 2021-05-25T02:19:03 | {} | NONE |
vuejs | core | 848,445,637 | 3,830 | HcySunYang | You should use `appear: true` if you want to apply transition for the initial render | 2021-05-26T04:33:10 | 2021-05-26T04:33:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 848,518,864 | 3,833 | LinusBorg | We are using Proxies to detect changes, the original object stays untouched. This is by design, and there will be no way to achieve what you want.
We realize that this leads to a few caveats when using reactivity with classes, such as the one you demonstrated, but that's the way it is.
Generally, we have always r... | 2021-05-26T06:59:00 | 2021-05-26T06:59:00 | {} | MEMBER |
vuejs | core | 849,423,615 | 3,813 | posva | It would be problematic to have the modifier applied implicitly to v model as there would be no way to turn it off and the string version is more flexible | 2021-05-27T07:58:50 | 2021-05-27T07:58:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 850,087,046 | 3,566 | Akryum | Will take a look tomorrow | 2021-05-28T03:36:44 | 2021-05-28T03:36:44 | {} | MEMBER |
vuejs | core | 850,172,929 | 3,559 | JayFate | @tjk Do you have a minute to review this pull request ? | 2021-05-28T06:23:16 | 2021-05-28T06:23:16 | {} | CONTRIBUTOR |
vuejs | core | 850,229,915 | 3,808 | wenfangdu | @edison1105 Thanks for the tip! | 2021-05-28T07:59:46 | 2021-05-28T07:59:46 | {} | NONE |
vuejs | core | 850,433,830 | 3,566 | Akryum | It seems it doesn't work well for `extends` though | 2021-05-28T13:50:34 | 2021-05-28T14:30:28 | {} | MEMBER |
vuejs | core | 850,608,712 | 3,082 | yyx990803 | The diff algorithm is able to handle a lot of fast cases without the need for creating a full key map - and in such cases Vue can correctly update the list even with duplicated keys.
e.g. `a b c a` -> `a a` can work even if there are duplicated keys because the head and tail remains the same.
The current duplicat... | 2021-05-28T19:01:10 | 2021-05-28T19:01:10 | {} | MEMBER |
vuejs | core | 851,010,449 | 3,852 | KaelWD | Should `deepMergeData` return `to` at the end? `mergedDataFn`'s return is always undefined otherwise.
https://github.com/vuejs/vue-next/blob/cd337149353d03446850b5f45b817f3fa160e5ff/packages/runtime-core/src/compat/data.ts#L6-L22 | 2021-05-30T14:37:45 | 2021-05-30T14:37:45 | {} | CONTRIBUTOR |
vuejs | core | 847,383,599 | 3,627 | yyx990803 | This is a wontfix. `isCustomElement` is a compiler-only concept in v3, so it should not and cannot affect `resolveDynamicComponent`'s runtime behavior.
When using the option with build tools it is passed to `vue-loader` or `@vitejs/plugin-vue` so it cannot be even known at runtime. If we change the behavior `app.con... | 2021-05-24T22:09:35 | 2021-05-24T22:09:35 | {} | MEMBER |
vuejs | core | 848,416,010 | 3,797 | hyf0 | @HcySunYang I think that @yaquawa means Vue3 can use this feature to fix the problem in #3478.
```
const foo = reactive({bar: 3)}
// type error
foo.bar = ref(5)
``` | 2021-05-26T02:54:21 | 2021-05-26T02:54:21 | {} | CONTRIBUTOR |
vuejs | core | 849,266,136 | 2,730 | skirtles-code | I think this will be fixed by https://github.com/vuejs/vue-next/commit/b57e995edd29eff685aeaf40712e0e029073d1cb, which is available in 3.1.0-beta.5. | 2021-05-27T02:19:44 | 2021-05-27T02:19:44 | {} | CONTRIBUTOR |
vuejs | core | 850,059,052 | 3,647 | hyf0 | doesn't have the problem after commit https://github.com/vuejs/vue-next/commit/03a7a73148a9e210a7889c7a2ecf925338735c70 | 2021-05-28T02:07:20 | 2021-05-28T02:07:20 | {} | CONTRIBUTOR |
vuejs | core | 850,760,495 | 3,559 | JayFate | @HcySunYang Do you have a minute to review this pull request ? | 2021-05-29T03:19:59 | 2021-05-29T03:19:59 | {} | CONTRIBUTOR |
vuejs | core | 850,851,272 | 3,844 | jimparis | > As a workaround you can isolate the select in a component
That worked, thank you! | 2021-05-29T15:26:49 | 2021-05-29T15:26:49 | {} | NONE |
vuejs | core | 850,982,094 | 3,850 | mivui | v-slots https://github.com/vuejs/jsx-next | 2021-05-30T11:11:04 | 2021-05-30T11:12:38 | {} | NONE |
vuejs | core | 850,995,490 | 3,850 | HcySunYang | This is not related to Vue core, move to jsx-next | 2021-05-30T12:52:05 | 2021-05-30T12:52:05 | {} | MEMBER |
vuejs | core | 847,446,604 | 3,808 | wenfangdu | > **compiler-sfc:** support tsx in setup script ([#3825](https://github.com/vuejs/vue-next/issues/3825)) ([01e8ba8](https://github.com/vuejs/vue-next/commit/01e8ba8f873afe3857a23fb68b44fdc057e31781)), closes [#3808](https://github.com/vuejs/vue-next/issues/3808)
@yyx990803 I've tried `v3.1.0-beta.4`, still reproduci... | 2021-05-25T00:39:20 | 2021-05-25T00:42:29 | {} | NONE |
vuejs | core | 848,637,726 | 3,833 | LinusBorg | why would you make the instance `reactive()` if it already uses `ref()` internally (which are reactive)?
Just don't *replace* the refs, just set their value:
```ts
get url(): string {
return this._url.value;
}
set url(newUrl: string) {
this._url.value = newUrl;
}
```
| 2021-05-26T09:57:58 | 2021-05-26T10:00:28 | {} | MEMBER |
vuejs | core | 849,467,983 | 3,829 | posva | Note you can use `onError` for a more advanced usage: https://v3.vuejs.org/api/global-api.html#defineasynccomponent | 2021-05-27T09:04:49 | 2021-05-27T09:04:49 | {} | MEMBER |
vuejs | core | 850,490,339 | 3,838 | posva | your ModalConfirm is named ModalDialog and it's rendering itself in a loop.
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-05-28T15:15:51 | 2021-05-28T15:15:51 | {} | MEMBER |
vuejs | core | 846,523,956 | 3,811 | hearsay316 | > 如果push不上GitHub，可以把最小化复现提交提交到Gitee试一下。满足提问题的条件以后开一个新的问题，谢谢。
已经提交到github了！ 已经可以试了。 | 2021-05-23T08:14:33 | 2021-05-23T08:14:33 | {} | NONE |
vuejs | core | 850,431,405 | 3,566 | Akryum | It's done here:
https://github.com/vuejs/vue-next/blob/6f8fe4eac9fe8f4aad71a829d20897dc676c155c/packages/runtime-core/src/componentPublicInstance.ts#L235 | 2021-05-28T13:46:40 | 2021-05-28T13:47:56 | {} | MEMBER |
vuejs | core | 850,910,009 | 3,849 | antoniandre | **In Vite** it works in version `vue@3.1.0-beta.6`, with explicit load of `"@vue/compiler-sfc": "3.1.0-beta.6"` with this config:
```js
export default defineConfig({
plugins: [
vue({
template: {
compilerOptions: {
whitespace: 'preserve'
}
}
})
]
```
🙏 ... | 2021-05-29T22:50:58 | 2021-05-29T23:03:35 | {
"+1": 1
} | NONE |
vuejs | core | 846,507,351 | 3,818 | davidboom95 | > Do you mean this [sfc playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8U2xpZGVyPlxuICBcdDx0ZW1wbGF0ZSAjc2xpZGU9XCJ7Y3VycmVudFNsaWRlfVwiPlxuICAgICAgPGRpdiBcbiAgICAgICAgICB2LWlmPVwiY3VycmVudFNsaWRlICE9IG51bGxcIlxuICAgICAgICAgIGNsYXNzPVwic2xpZGUtYm94XCJcbiAgICAgID5cbiAgICAgICAge3tjdXJyZW50U2xpZGV9f... | 2021-05-23T05:41:48 | 2021-05-23T05:41:48 | {} | NONE |
vuejs | core | 846,984,272 | 3,824 | DefectingCat | > `import type { State } from './types'`
it works, thank you | 2021-05-24T11:37:40 | 2021-05-24T11:37:40 | {} | NONE |
vuejs | core | 847,486,753 | 3,797 | HcySunYang | @iheyunfei Maybe not a duplicate? this one is talking about the same property with different types of `setter/getter`. | 2021-05-25T02:40:17 | 2021-05-25T02:40:17 | {} | MEMBER |
vuejs | core | 848,079,216 | 3,537 | lukewarlow | I've updated my test case to Vue 3.1.0-beta4 (https://github.com/lukewarlow/vue-server-render-bug) but I still experience the issue with incorrect srcset in the SSR output. Is there some change I need to make to my SSR code?
@yyx990803 @HcySunYang | 2021-05-25T17:39:38 | 2021-05-25T17:39:38 | {} | NONE |
vuejs | core | 848,177,040 | 906 | dacxjo | I'm facing the same issue with mode="out-in", @mduey @stuta , i'm using the latest version of vite, with vue-router ^4.0.8,
vite-plugin-pages, and vite-plugin-layouts, is there a way to fix this? | 2021-05-25T18:55:55 | 2021-05-25T18:55:55 | {} | NONE |
vuejs | core | 850,036,817 | 3,528 | yyx990803 | Good job tracing this down to 29be536b1f0b7f7f7c1e6cd5a84e12bb4c48b87c - I believe that was a bad fix because the problem in #910 should be a scheduler concern instead of the reactivity module.
So I reverted the fix in 29be536b1f0b7f7f7c1e6cd5a84e12bb4c48b87c and fixed it in the scheduler instead in 03a7a731 | 2021-05-28T00:55:22 | 2021-05-28T00:55:22 | {} | MEMBER |
vuejs | core | 894,965,033 | 3,720 | Hope555 | @edison1105
Thanks for your example. Figured out the bug in my code finally. | 2021-08-09T05:43:38 | 2021-08-09T05:43:38 | {} | NONE |
vuejs | core | 895,178,865 | 4,280 | posva | Please don't open issues without reproductions. Also please read the PR about 3.2 with docs about v-memo in the docs repo to see what its intended use cases are. | 2021-08-09T12:22:59 | 2021-08-09T12:22:59 | {} | MEMBER |
vuejs | core | 895,227,088 | 4,275 | ffigari | Got it, tyvm! | 2021-08-09T13:33:45 | 2021-08-09T13:33:45 | {} | NONE |
vuejs | core | 895,364,379 | 4,284 | 07akioni | This will make jsx behaviors wired.
```
<div>{false}{false}</div>
<div>{false}</div>
```
will show different result. | 2021-08-09T16:27:49 | 2021-08-09T16:27:49 | {} | CONTRIBUTOR |
vuejs | core | 895,611,555 | 4,287 | lidlanca | workaround cloudflare limitation is still possible
```js
function cloudflareWriteableCompatibility(writeable){
return {
getWriter(){
var w = writeable.getWriter()
w.ready = Promise.resolve()
return w
}
}
}
```
```js
let { readable, writable } = new Trans... | 2021-08-09T23:12:16 | 2021-08-09T23:12:16 | {} | CONTRIBUTOR |
vuejs | core | 895,927,617 | 4,292 | zhangenming | Now it seems that…Doesn't seem to make much sense
But this form when debugging/learning should be a little easier to understand, maybe | 2021-08-10T10:49:21 | 2021-08-10T10:49:21 | {} | CONTRIBUTOR |
vuejs | core | 896,748,239 | 4,298 | LinusBorg | So in other words: bueify wrote their render function in way that makes it look like a Vue 3 render function to `@vue/compat`. And it's because of this unnecessary/dead second argument. | 2021-08-11T11:28:56 | 2021-08-11T11:29:17 | {} | MEMBER |
vuejs | core | 894,975,707 | 4,274 | lidlanca | @edison1105 you are correct, 3.2 does not have this
but the `v3.2.0-beta.8` tag and master does.
https://github.com/vuejs/vue-next/blob/v3.2.0-beta.8/packages/compiler-sfc/src/compileScript.ts#L333-L338 | 2021-08-09T06:16:38 | 2021-08-09T06:16:38 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 895,674,829 | 4,284 | 07akioni | > I can see the argument but changing it would technically be a breaking change.
>
>
>
> The JSX transform seems to compile both to array children and should not be affected: https://vue-next-jsx-explorer.netlify.app/#%3C%3E%0A%20%20%3Cdiv%3E%7Bfalse%7D%7Bfalse%7D%3C%2Fdiv%3E%0A%20%20%3Cdiv%3E%7Bfalse%7D%3C%2Fdiv%3E... | 2021-08-10T02:12:42 | 2021-08-10T02:12:42 | {} | CONTRIBUTOR |
vuejs | core | 897,045,344 | 4,315 | Cansiny0320 | I think there are some mistakes in this test. | 2021-08-11T18:16:00 | 2021-08-11T18:16:00 | {} | CONTRIBUTOR |
vuejs | core | 895,093,530 | 4,277 | axetroy | > Like, they are cheap, I can't imagine a scenario where you would call a composition function that uses a lifecycle hook 1000's of times.
There is indeed such a scenario that will call many times lifecycle hook. Especially some users stay on one page for a long lone time.
A callback is registered in the lifecycl... | 2021-08-09T09:53:41 | 2021-08-09T09:53:41 | {} | NONE |
vuejs | core | 896,203,723 | 4,287 | yyx990803 | This should be fixed, but the special case should be removed in the long run when CF workers update their stream implementations to be spec-compliant ([they seem to be willing to](https://twitter.com/KentonVarda/status/1425139649681444868)).
Also as a workaround it is quite easy for you to implement a CF-worker-comp... | 2021-08-10T18:07:42 | 2021-08-10T18:07:42 | {} | MEMBER |
vuejs | core | 896,389,943 | 4,296 | GeniusWiki | @posva thanks. I found I posted a debug jsfiddle for our real use case that use $parent data, here is simplified version https://jsfiddle.net/robedgenius/oky8r140/26/. | 2021-08-10T23:58:24 | 2021-08-10T23:58:47 | {} | NONE |
vuejs | core | 896,503,504 | 4,303 | edison1105 | you should:
```diff
export default {
+ inheritAttrs:false,
components: {
ChildComponent,
},
};
```
see https://v3.vuejs.org/api/options-misc.html#inheritattrs | 2021-08-11T05:06:23 | 2021-08-11T05:07:36 | {} | MEMBER |
vuejs | core | 896,569,137 | 4,304 | LinusBorg | Please provide a working link | 2021-08-11T07:27:06 | 2021-08-11T07:27:06 | {} | MEMBER |
vuejs | core | 896,887,098 | 4,308 | yyx990803 | @dependabot ignore this dependency | 2021-08-11T14:41:53 | 2021-08-11T14:41:53 | {} | MEMBER |
vuejs | core | 894,941,978 | 3,720 | Hope555 | @smasinde
Hi mate, does the wrong index issue been solved? | 2021-08-09T04:25:51 | 2021-08-09T04:25:51 | {} | NONE |
vuejs | core | 894,961,325 | 4,274 | edison1105 | @jods4
Are you sure this is a problem with version `3.2.0-beta.8`?
@lidlanca
I noticed that your PR is checkout from the master branch, not `v3.2`.
because `v3.2` not contains this code
```javascript
let isUsedInTemplate = true
if (isTS && sfc.template && !sfc.template.src) {
isUsedInTemplat... | 2021-08-09T05:29:34 | 2021-08-09T05:29:34 | {} | MEMBER |
vuejs | core | 895,166,393 | 4,280 | edison1105 | It works fine in [sfc](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuIFx0PGRpdiBcbiAgIHYtZm9yPVwiaXRlbSBpbiAzXCJcbiAgIDprZXk9XCJpdGVtXCJcbiAgIHYtbWVtbz1cIltjb3VudDwyP3RydWU6Y291bnRdXCI+XG4gICAge3tjb3VudH19XG4gIDwvZGl2PlxuPC90ZW1wbGF0ZT5cblxuPHNjcmlwdCBzZXR1cD5cbmNvbnN0IGNvdW50ID0xXG48L3NjcmlwdD4ifQ==)
could y... | 2021-08-09T12:04:00 | 2021-08-09T12:04:00 | {} | MEMBER |
vuejs | core | 896,082,769 | 4,294 | yyx990803 | [Relevant RFC section](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0040-script-setup.md#type-only-propsemit-declarations)
> Currently complex types and type imports from other files are not supported. It is theoretically possible to support type imports in the future.
We'll mark it as an enhancement for... | 2021-08-10T14:34:15 | 2021-08-10T14:34:15 | {
"+1": 115,
"-1": 14,
"confused": 2,
"eyes": 37,
"heart": 26,
"hooray": 12,
"rocket": 13
} | MEMBER |
vuejs | core | 896,463,793 | 4,299 | edison1105 | > 打包成生产环境才产生的。
你可以创建一个最小可以复现demo，传到github仓库，然后我会尝试clone下来帮你查看一下问题。
说实话，没有demo，真的无从下手。 | 2021-08-11T03:04:55 | 2021-08-11T03:04:55 | {} | MEMBER |
vuejs | core | 896,768,683 | 4,298 | LinusBorg | At the risk of repeating myself. We **do** handle it. **If** the Vue 2 render function has the correct format, which is:
```js
render(createElement) {
}
```
If however you like to add arguments to functions that do nothing, like this, then we do *not* support it:
```js
render(createElement, argumentThat... | 2021-08-11T12:04:43 | 2021-08-11T14:52:09 | {} | MEMBER |
vuejs | core | 895,240,977 | 4,281 | edison1105 | see https://github.com/vuejs/vue-next/issues/3668 | 2021-08-09T13:52:03 | 2021-08-09T13:52:03 | {} | MEMBER |
vuejs | core | 895,456,195 | 4,285 | yyx990803 | Being able to access data from mixins was unintended and undocumented behavior, and was a side effect of Vue 3's different handling of options in 3.0.x.
It was made consistent with Vue 2 in 3.1, so your case is now considered expected behavior (it doesn't work in Vue 2 either). | 2021-08-09T18:48:49 | 2021-08-09T18:48:49 | {} | MEMBER |
vuejs | core | 896,984,933 | 4,309 | TatsuyaYamamoto | sorry, I accidentally close this PR.......
---
If it default-exports an object with a component property, this PR can recursively read SFCs with the current `_getStylesRecursively` . (@LinusBorg, thank you for your idea!)
```
<script>
import Child from './Child.vue'
export default {
components: { Child }... | 2021-08-11T16:47:17 | 2021-08-11T16:47:17 | {
"+1": 2
} | NONE |
vuejs | core | 894,949,687 | 3,720 | edison1105 | works fine see [sfc](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2IHYtZm9yPVwiKGl0ZW0sIGluZGV4KSBpbiBbMSwyLDNdXCI+XG4gICA8dGVsZXBvcnQgdG89XCJib2R5XCI+XG4gICAgIDxidXR0b24gQGNsaWNrPVwibG9nKGluZGV4KVwiPkNsaWNrIG1lPC9idXR0b24+XG4gICA8L3RlbGVwb3J0PlxuPC9kaXY+XG48L3RlbXBsYXRlPlxuXG48c2NyaXB0IHNldHVwPlxuY29u... | 2021-08-09T04:55:34 | 2021-08-09T04:55:34 | {} | MEMBER |
vuejs | core | 895,231,969 | 4,262 | edison1105 | ```diff
(
+ because we disable tracking the block tree here.
_openBlock(true),
_createElementBlock(_Fragment, null, _renderList(_unref(items), (id, index, ___, _cached) => {
const _memo = ([ _unref(flip) ])
+ here currentBlock is null, As a result, the block tree is not tracked correncly in isMemoSame.
... | 2021-08-09T13:40:23 | 2021-08-09T13:40:23 | {} | MEMBER |
vuejs | core | 895,924,594 | 4,171 | JohanAhlen | It's nice to see that this made it into Vue 3.2, thanks!
@yyx990803 I would also like to have some information on what tooling updates we'll need, are these features tracked somewhere? Without full support for styles we can't use it as of now, and I'm guessing that's a common requirement for many projects.
I did... | 2021-08-10T10:43:46 | 2021-08-10T10:43:46 | {
"+1": 8
} | NONE |
vuejs | core | 896,228,070 | 4,287 | Cherry | Perfect, thank you so much. I can confirm that implementing something akin to your changes with a manual `renderToSimpleStream` now works as expected! | 2021-08-10T18:44:17 | 2021-08-10T18:44:17 | {} | CONTRIBUTOR |
vuejs | core | 896,464,166 | 4,300 | edison1105 | your repro link is borken | 2021-08-11T03:05:54 | 2021-08-11T03:05:54 | {} | MEMBER |
vuejs | core | 896,761,530 | 4,298 | ghost | Why then was createElement removed from Vue 3 in the first place? If it wasn't broken, why did it have to be fixed? There are many, many libraries that relied on this API, and for @vue/compat to not be able to handle this scenario is hurtful to users trying to get on an upgrade path. | 2021-08-11T11:52:46 | 2021-08-11T11:52:46 | {} | NONE |
vuejs | core | 897,346,687 | 4,320 | edison1105 | please provide a working repro. | 2021-08-12T04:51:00 | 2021-08-12T04:51:00 | {} | MEMBER |
vuejs | core | 894,853,726 | 4,275 | ffigari | In particular, what does an alias to the "the right build of Vue" mean? | 2021-08-08T20:52:57 | 2021-08-08T20:52:57 | {} | NONE |
vuejs | core | 895,088,263 | 4,277 | LinusBorg | Maybe I misunderstand what you are asking for, but I don't really see the problem with having "many" unmount hooks "listeners" (I guess you mean callbacks?).
Like, they are cheap, I can't imagine a scenario where you would call a composition function that uses a lifecycle hook 1000's of times.
Can you provide so... | 2021-08-09T09:43:41 | 2021-08-09T09:44:00 | {} | MEMBER |
vuejs | core | 895,419,726 | 4,262 | yyx990803 | Ok, this is not a bug, but this is currently by design: **`v-memo` does not work inside `v-for`, it can only be used with `v-for` (on the same element).** Could probably be improved though. | 2021-08-09T17:52:42 | 2021-08-09T17:53:10 | {} | MEMBER |
vuejs | core | 896,288,891 | 4,223 | webfansplz | Hi. @yyx990803 maybe this can merged 😊 | 2021-08-10T20:15:04 | 2021-08-10T20:15:04 | {} | MEMBER |
vuejs | core | 896,523,699 | 4,300 | aehyok | @edison1105 compiler-sfc is 3.2.1, after it's ok. Thanks.
But I said waht does compiler-sfc ? | 2021-08-11T05:55:18 | 2021-08-11T06:00:01 | {} | NONE |
vuejs | core | 896,697,561 | 3,926 | klwfwdk | Is this change just to fix a bug in the TSX? Props does not actually have an onClick property. This will contaminate the editor's automatic code prompt. | 2021-08-11T10:15:02 | 2021-08-11T10:15:02 | {} | CONTRIBUTOR |
vuejs | core | 895,707,064 | 4,288 | kadiryazici | @webfansplz I edited type code with your pull request and nothing changed. The problem is here I think.
I don't have a good knowledge about typing types but if I change it to this, I don't get any type er... | 2021-08-10T03:50:13 | 2021-08-10T03:50:25 | {} | CONTRIBUTOR |
vuejs | core | 895,723,947 | 4,288 | kadiryazici | @webfansplz it is not the return type of emit, it is just validator. I return true from validator because I don't need validaton. Vscode type checking is enough for me.
Emit handler should return any or void always. | 2021-08-10T04:41:44 | 2021-08-10T04:41:44 | {} | CONTRIBUTOR |
vuejs | core | 896,204,859 | 4,290 | yyx990803 | Can you add a test case in https://github.com/vuejs/vue-next/blob/master/test-dts/defineComponent.test-d.tsx ? | 2021-08-10T18:09:16 | 2021-08-10T18:09:16 | {} | MEMBER |
vuejs | core | 896,747,827 | 4,298 | LinusBorg | In Vue 2, the first (and onnly) argument is `createElement`. in Vue 3, it's not. so `@vue/compat` has to handle the Vue 2 render function differently.
But here, it doesn't because it *thinks* the render function is a Vue 3 render function - because it uses >= 2 arguments. | 2021-08-11T11:28:07 | 2021-08-11T11:28:07 | {} | MEMBER |
vuejs | core | 895,019,943 | 4,274 | jods4 | @edison1105 not sure where this was introduced.
I know it happened to me with `3.2.0-beta.7`, I upgraded to beta.8 and the bug was still there.
Not sure about 3.1. | 2021-08-09T07:49:25 | 2021-08-09T07:49:25 | {} | CONTRIBUTOR |
vuejs | core | 895,343,965 | 4,277 | yyx990803 | I don't see this as necessary because you already can create your own abstractions. | 2021-08-09T16:01:26 | 2021-08-09T16:01:26 | {} | MEMBER |
vuejs | core | 895,722,485 | 4,288 | webfansplz | Hi @kadiryazici,Maybe you just forgot to return it when you invoked it
```tsx
import { defineComponent } from 'vue';
const Component = defineComponent({
emits: {
something: (value: string) => true
}
});
const OtherComponent = defineComponent({
render() {
return (
<Compo... | 2021-08-10T04:36:32 | 2021-08-10T04:41:16 | {} | MEMBER |
vuejs | core | 895,939,154 | 4,295 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-08-10T11:08:09 | 2021-08-10T11:08:09 | {} | CONTRIBUTOR |
vuejs | core | 896,438,479 | 4,299 | linziguan | 打包成生产环境才产生的。 | 2021-08-11T01:55:52 | 2021-08-11T01:55:52 | {} | NONE |
vuejs | core | 896,516,508 | 4,300 | zengjie911 | > @zengjie911
> please make sure the version of `@vue/compiler-sfc` is 3.2.1 too.
> if it's not, update it to 3.2.1 and remove the yarn.lock file and re-install deps.
i'm sure the version is 3.2.1
 {
return this.genNavbar(createElement);
}
```
Note the second argument - which does nothing. Because in Vue 2, render... | 2021-08-11T05:50:49 | 2021-08-11T14:27:50 | {} | MEMBER |
vuejs | core | 895,038,529 | 4,277 | axetroy | @posva I knew how to hack it to make it works well.
But, it's not a good solution.
```js
function cancelableonUnmounted(fn) {
let shouldSkipUnmountedHooks
// even the hook will return immediately
// but listener is still there, if the function `cancelableonUnmounted` invoke too many times
// there ... | 2021-08-09T08:22:40 | 2021-08-09T08:22:55 | {} | NONE |
vuejs | core | 895,117,568 | 4,277 | LinusBorg | The way you are using the hook is suboptimal because you are tightly coupling the `Http` class to Vue-specific implementation details
rather, I'd suggest something like this:
```ts
export function useApi (vm: VM, onUnmounted: disposable): Api{
const http = new Http()
onUnmounted(() => {
http.cancelAll... | 2021-08-09T10:34:34 | 2021-08-09T12:35:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 895,629,903 | 4,287 | Cherry | Unfortunately not. I tried something like that and every time it threw `Cannot assign to read only property 'ready' of object '#<Writer>'`.
The only way I've come close is with a hacky proxy, and something like this:
```js
const cloudflareWriteableCompatibility = function(writable){
// serious hack. We can't jus... | 2021-08-10T00:01:50 | 2021-08-10T00:03:47 | {} | CONTRIBUTOR |
vuejs | core | 895,733,263 | 4,288 | webfansplz | @kadiryazici You are right, I have mentioned PR to fix this | 2021-08-10T05:08:40 | 2021-08-10T05:08:40 | {
"heart": 1
} | MEMBER |
vuejs | core | 896,748,731 | 4,298 | ghost | Does Vue 3 ever have createElement as an argument to render function? This is inconsistent with the docs, which suggest that render has NO arguments. When would render EVER have >= 2 arguments? | 2021-08-11T11:29:55 | 2021-08-11T11:29:55 | {} | NONE |
vuejs | core | 896,749,483 | 4,298 | LinusBorg | When it's the output of a template that's been compiled with the Vue 3 compiler. Go to sfc.vuejs.org and check the "JS" tab on the right.
And no, it never has `createElement` as an argument, that's the point. In Vue 3, createElement = `h`, which is imported from `'vue'`, not a function argument of `render` - also v... | 2021-08-11T11:31:14 | 2021-08-11T11:50:08 | {} | MEMBER |
vuejs | core | 897,236,311 | 4,315 | Justineo | The use of plain `for` loops is intentional for better performance according to earlier benchmarks. Thank you. | 2021-08-11T23:52:39 | 2021-08-11T23:52:39 | {} | MEMBER |
vuejs | core | 897,282,374 | 4,309 | TatsuyaYamamoto | The document announces usage alongside normal `<script>` for declaring additional options.
https://v3.vuejs.org/api/sfc-script-setup.html#usage-alongside-normal-script
After reading this, I feel natural to declare components option in `script` . | 2021-08-12T01:45:46 | 2021-08-12T01:45:46 | {} | NONE |
vuejs | core | 895,051,357 | 2,027 | MrYusheng | 
I also had this problem, and I didn't listen to the whole route, but I found that if I used the whole route inside the method, I would also get a warning, so I only called what I needed to use, and the warni... | 2021-08-09T08:45:49 | 2021-08-09T08:48:12 | {
"+1": 1
} | NONE |
vuejs | core | 895,108,737 | 4,223 | webfansplz | The issue was closed because the [vuejs/composition-api](https://github.com/vuejs/composition-api/pull/779) fix it, but it also need the support of Vue3
In simple terms,There are some usage scenarios that require the `UnwrapNestedRefs` type when `export * from 'vue'`, such as [vue-demi](https://github.com/vueuse/vue... | 2021-08-09T10:18:42 | 2021-08-09T10:21:01 | {} | MEMBER |
vuejs | core | 895,660,809 | 4,287 | lidlanca | I dont see a reason for the proxy not to work as long as you can override the ready.
Assuming your logic is correct.
Try debugging and see if the writer close method is actually called and properly delegated to the actual writer
I didnt really get the extra ready logic | 2021-08-10T01:31:55 | 2021-08-10T01:35:46 | {} | CONTRIBUTOR |
vuejs | core | 895,978,137 | 4,291 | Justineo | Please provide a valid repro. Thank you. | 2021-08-10T12:14:29 | 2021-08-10T12:14:29 | {} | MEMBER |
vuejs | core | 896,198,102 | 4,287 | yyx990803 | Hmm, I really think CloudFlare workers should at least be implemented in a spec compliant fashion.
Theoretically this can be worked around by checking the presence of `ready` with `'ready' in writer` in `pipeToWebWritable`? | 2021-08-10T18:00:18 | 2021-08-10T18:00:18 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.