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 | 800,072,038 | 3,426 | HcySunYang | What really happened?
| 2021-03-16T08:47:21 | 2021-03-16T08:47:21 | {} | MEMBER |
vuejs | core | 797,513,474 | 3,414 | posva | I think this should go through an RFC first to explore the different possible APIs, e.g. we could also **only** match by key if another prop is passed `by-key`, or `match-by`, etc | 2021-03-12T14:10:14 | 2021-03-12T14:10:14 | {} | MEMBER |
vuejs | core | 798,839,015 | 1,539 | yanyang1116 |
i have same problem:
| 2021-03-14T05:46:47 | 2021-03-14T05:46:47 | {
"+1": 4
} | NONE |
vuejs | core | 799,125,798 | 3,419 | GGwujun | 11 | 2021-03-15T05:36:09 | 2021-03-15T05:36:09 | {} | NONE |
vuejs | core | 797,233,700 | 2,457 | edison1105 | should change code as below?
```diff
terser({
module: /^esm/.test(format),
compress: {
ecma: 2015,
pure_getters: true
},
+ mangle:{ safari10: true },
safari10: true
})
``` | 2021-03-12T04:54:43 | 2021-03-15T08:57:11 | {} | MEMBER |
vuejs | core | 800,346,414 | 2,600 | industral | still have the same weird issue, have no idea what's going on. Tried to remove one div - warning gone.
| 2021-03-16T15:10:06 | 2021-03-16T15:10:06 | {} | NONE |
vuejs | core | 797,278,417 | 2,457 | edison1105 | > @edison1105 Has the problem been solved?I opened it blank in iOS10 +
It seems has not been fixed. | 2021-03-12T06:53:17 | 2021-03-12T06:53:17 | {} | MEMBER |
vuejs | core | 797,312,539 | 3,183 | Blackfaded | For Types the import type solution worked for me. But I cant get interfaces working. I always get the warning, that the interface is not exported.
```bash
"export 'Consultation' was not found in '@/libs/shared/interfaces/consultation'
``` | 2021-03-12T08:07:35 | 2021-03-12T08:07:35 | {} | NONE |
vuejs | core | 797,841,902 | 3,412 | yxmg | @LinusBorg Thank you for your response. I used it wrong. I try to use the parse function of @vue/compiler-sfc, it works👍 Thank you again~ | 2021-03-13T01:25:54 | 2021-03-13T01:25:54 | {} | NONE |
vuejs | core | 799,761,818 | 3,424 | posva | Please boil down the problew without external dependencies like twilio-video. You likely need to use
```js
import { markRaw } from 'vue'
markRaw(await createLocalVideoTrack({ video: true }))
``` | 2021-03-15T21:23:24 | 2021-03-15T21:23:24 | {} | MEMBER |
vuejs | core | 799,985,184 | 3,428 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.89 KB (0%) |
| runtime-dom.global.prod.js | 27.16 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-16T06:17:07 | 2021-03-16T06:17:07 | {} | NONE |
vuejs | core | 800,502,610 | 3,433 | mymusise | Thank you guy! I got my answer. | 2021-03-16T18:25:12 | 2021-03-16T18:25:12 | {} | NONE |
vuejs | core | 797,471,934 | 3,413 | dinfer | Binding the `this.elRef, I got the same result.
```
import { defineComponent, onMounted, ref, toRaw, h, createApp } from "vue";
const Test = defineComponent({
name: "test",
setup() {
const elRef = ref("test");
// should log out the div html element
// but I got 'test'
onMounted(() => co... | 2021-03-12T12:54:07 | 2021-03-12T12:54:07 | {} | NONE |
vuejs | core | 797,883,848 | 3,415 | ygj6 | This is the same as vue-class-component issue#514
https://github.com/vuejs/vue-class-component/issues/514 | 2021-03-13T07:35:19 | 2021-03-13T07:35:19 | {} | MEMBER |
vuejs | core | 798,937,566 | 3,188 | gaborfeher | I think the fix is not yet included in 3.0.7 according to the [changelog](https://github.com/vuejs/vue-next/blob/master/CHANGELOG.md). | 2021-03-14T16:34:55 | 2021-03-14T16:34:55 | {} | NONE |
vuejs | core | 799,161,061 | 3,421 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.89 KB (0%) |
| runtime-dom.global.prod.js | 27.16 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-15T06:47:34 | 2021-03-15T06:47:34 | {} | NONE |
vuejs | core | 799,983,931 | 3,396 | dependabot-preview[bot] | Superseded by #3428. | 2021-03-16T06:14:42 | 2021-03-16T06:14:42 | {} | CONTRIBUTOR |
vuejs | core | 795,295,002 | 3,403 | posva | This is too much for a reproduction, please boil it down and open a new issue | 2021-03-10T11:41:07 | 2021-03-10T11:41:07 | {} | MEMBER |
vuejs | core | 797,259,977 | 3,410 | Justineo | According to Terser's docs, `safari10: true` already indicates `mangle: { safari10: true }`, unless there's a bug on Terser's side. | 2021-03-12T06:09:14 | 2021-03-12T06:09:14 | {} | MEMBER |
vuejs | core | 799,317,629 | 3,418 | posva | Please provide a boiled down issue like asked in the new issue helper. It contains a js fiddle you should use. Closing until one is provided | 2021-03-15T10:47:27 | 2021-03-15T10:47:27 | {} | MEMBER |
vuejs | core | 799,553,736 | 3,423 | LinusBorg | > I know it is a bug related not just to Vue, but to Chrome extensions
Can you provide more details? You say this is a general bug in chrome.storage? Then we can't really do anything about this ... | 2021-03-15T16:22:50 | 2021-03-15T16:22:50 | {} | MEMBER |
vuejs | core | 799,357,421 | 3,418 | LinusBorg | @posva I reopened as I'm familiar with the issue myself. Already started talking to some of our team how to best resolve this.
It's not strictly a bug as it's more of a conceptual blind spot we have to fill somehow. the recommended approach from the docs can fail under certain circumstances, i.e. this:
```vue
<t... | 2021-03-15T11:50:32 | 2021-03-15T16:25:21 | {} | MEMBER |
vuejs | core | 799,831,222 | 3,418 | bazuka5801 | Because In my opinion,
The system is to blame, not the people and the system needs to be improved | 2021-03-15T23:34:27 | 2021-03-15T23:34:27 | {} | NONE |
vuejs | core | 800,077,875 | 3,426 | WarWithinMe | > What really happened?
>
> 
I see, perhaps it's because I have noImplicitAny set to false in tsconfig.json | 2021-03-16T08:56:35 | 2021-03-16T08:56:35 | {} | NONE |
vuejs | core | 796,594,116 | 3,399 | HcySunYang | yeah, they are different. | 2021-03-11T09:22:15 | 2021-03-11T09:22:15 | {} | MEMBER |
vuejs | core | 797,281,586 | 2,457 | HcySunYang | Oh sure, I made a mistake | 2021-03-12T07:00:57 | 2021-03-12T07:00:57 | {} | MEMBER |
vuejs | core | 797,489,048 | 3,413 | LinusBorg | > By the way, I found if I watch a reactive object which has a ref to DOM element with deep: true option, the traverse function will search all properties of the DOM element, and because of something like parentNode, vue will traverse up to the window object. Therefore, the web page cannot response any event.
Please... | 2021-03-12T13:26:11 | 2021-03-12T13:26:20 | {} | MEMBER |
vuejs | core | 796,584,713 | 3,408 | zhaoxm2016 | @LinusBorg
why?
那假如后期还需要引入类似这些声明文件，难道都需要引入到main.ts中吗 | 2021-03-11T09:07:01 | 2021-03-11T09:07:01 | {} | NONE |
vuejs | core | 797,262,978 | 3,411 | edison1105 | you should
```javascript
h(Item)
// or
h(resolveComponent("Item"))
``` | 2021-03-12T06:16:32 | 2021-03-12T06:27:51 | {} | MEMBER |
vuejs | core | 799,984,608 | 3,427 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.89 KB (0%) |
| runtime-dom.global.prod.js | 27.16 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-16T06:16:03 | 2021-03-16T06:16:03 | {} | NONE |
vuejs | core | 800,068,254 | 2,077 | HcySunYang | Closed, tracking here https://github.com/vuejs/rfcs/pull/284 | 2021-03-16T08:40:55 | 2021-03-16T08:40:55 | {} | MEMBER |
vuejs | core | 800,068,456 | 1,518 | HcySunYang | Closed, tracking here https://github.com/vuejs/rfcs/pull/284 | 2021-03-16T08:41:16 | 2021-03-16T08:41:16 | {} | MEMBER |
vuejs | core | 800,426,430 | 3,432 | LinusBorg | Yeah that's by design. Like props, emits aren't part of `attrs`. It contains only attributes that are *not* part of the components props or emits.
I see the use case though - we don't have an event counterpart to `$props`.
You can make it work like this, adding it to `props:` instead of `emits:`:
```html
<temp... | 2021-03-16T16:43:17 | 2021-03-16T17:31:45 | {} | MEMBER |
vuejs | core | 800,770,512 | 3,308 | lanmaomm | Why not merge this commit for so long time since it's already approved? | 2021-03-17T03:41:58 | 2021-03-17T03:41:58 | {} | NONE |
vuejs | core | 797,479,533 | 3,413 | dinfer | It works, thanks, I didn't find it in the `Render function` doc.
By the way, I found if I watch a reactive object which has a ref to DOM element with `deep: true` option, the traverse function will search all properties of the DOM element, and because of something like `parentNode`, vue will traverse up to the `wind... | 2021-03-12T13:09:02 | 2021-03-12T13:09:02 | {} | NONE |
vuejs | core | 797,378,759 | 3,317 | viniciuskneves | Hey, sorry for getting back late here, I was not available in the past ~2 weeks.
I've setup a branch in the project using `readonly`: https://github.com/viniciuskneves/vue-snakke/compare/typescript-readonly
I want to run: `npm run build:types` to generate my declarations.
If I run it in the above branch, I get t... | 2021-03-12T09:59:44 | 2021-03-12T21:57:43 | {} | NONE |
vuejs | core | 798,925,040 | 3,391 | HarryOneTwoFour | @Lilja I found that if I replace `<component :is="activeComponent" :myRef="myRef" />` with `<Foo :myRef="myRef" />` , it woks as expected.
So I think the key point is syntax `:is` . I'm new to vue, and I have no idea about it. | 2021-03-14T15:16:29 | 2021-03-14T15:16:29 | {} | NONE |
vuejs | core | 799,780,896 | 3,424 | JshGrn | @posva I cannot believe I overlooked that when it quite clearly states in clear english re complex third party classes.
@LinusBorg I see it, but it doesn't look like it is in a hurry to be merged in
markRaw has solved this painful issue for me... **thank you**... | 2021-03-15T21:55:51 | 2021-03-15T21:55:51 | {} | NONE |
vuejs | core | 799,830,217 | 3,418 | bazuka5801 | https://github.com/vuejs/docs-next/blame/master/src/guide/migration/array-refs.md
For avoid these confuses we need test docs examples, it is possible?)) | 2021-03-15T23:31:46 | 2021-03-15T23:40:15 | {} | NONE |
vuejs | core | 808,418,963 | 3,491 | danelowe | @edison1105 @yyx990803 Thanks. This still leaves serverPrefetch no bubbling up errors though?
https://github.com/vuejs/vue-next/blob/0a583d5ca224d2cba878dc6b0fb8d468e658f1ef/packages/server-renderer/src/render.ts#L99
Is there a reason for this? | 2021-03-26T18:07:30 | 2021-03-26T18:07:30 | {} | NONE |
vuejs | core | 808,723,437 | 3,493 | relief-melone | OK updating the compiler manually to 3.0.8 also seems to work for the rollup plugin (probably just forgot to npm serve again the first time). The only thing that I noticed is that backward compatiblity would also be an issue. So if I compile my library with 3.0.8 but leave my test environment on 3.0.7 this will also re... | 2021-03-27T12:14:17 | 2021-03-27T12:14:17 | {} | NONE |
vuejs | core | 808,740,188 | 3,334 | HcySunYang | This PR is backward compatible, but not forward compatible. This means that if a third-party library is built with this PR, then this library cannot be used in the lower version of the Vue runtime. But it does not affect the user to use the old library | 2021-03-27T14:18:12 | 2021-03-27T14:18:12 | {} | MEMBER |
vuejs | core | 809,516,615 | 3,514 | yyx990803 | Already fixed in 69b47272 - the original variable declaration walk is too loose. | 2021-03-29T16:17:22 | 2021-03-29T16:17:22 | {} | MEMBER |
vuejs | core | 805,087,052 | 3,469 | Livijn | Okay, but there is still something strange going on when a `<select>` isn't tiny. If you click `submit` on [this url](https://kdcwo.csb.app/) you will see that they behave differently. The url will change to: `https://kdcwo.csb.app/?small=&large=null`. So, if a `<select>` is larger than X, the `null` value is rendered ... | 2021-03-23T17:25:05 | 2021-03-23T17:54:32 | {} | NONE |
vuejs | core | 805,622,867 | 3,474 | HcySunYang | @posva yes, I am aware of this and have corrected it. | 2021-03-24T08:58:32 | 2021-03-24T08:58:32 | {} | MEMBER |
vuejs | core | 806,491,710 | 3,483 | 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-03-25T09:18:12 | 2021-03-25T09:18:12 | {} | CONTRIBUTOR |
vuejs | core | 806,733,866 | 2,513 | Kingbultsea | > I have the same problem in 3.0.7. Is there a solution now？[the reproduce](https://stackblitz.com/edit/vue3-iframe-teleport-demo?file=src%2FApp.vue)
raise by the iframe's event.timeStamp. need to wait until the iframe's creation time longer than clickEvent's creation time. | 2021-03-25T13:22:58 | 2021-03-25T13:22:58 | {} | CONTRIBUTOR |
vuejs | core | 807,584,522 | 3,106 | yyx990803 | Actually, since there can never be nested `renderComponentRoot` calls, we can just always reset `blockStack` when there's a render error. See da944cb3 | 2021-03-25T22:05:04 | 2021-03-25T22:05:04 | {} | MEMBER |
vuejs | core | 808,248,535 | 2,827 | yyx990803 | Since the inferred filename is actually causing breakage, I adjusted its priority in abd129d8 and it is now used as a fallback only when normal resolution fails.
The issue with adding another built-in tag is that it could technically be a breaking change. I think with the fix in abd129d8, it is no longer strictly ne... | 2021-03-26T14:07:45 | 2021-03-26T14:07:45 | {} | MEMBER |
vuejs | core | 809,110,975 | 2,982 | HcySunYang | Closed because it is stale | 2021-03-29T06:36:26 | 2021-03-29T06:36:26 | {} | MEMBER |
vuejs | core | 809,233,101 | 3,511 | posva | Duplicate of #3510 | 2021-03-29T09:37:32 | 2021-03-29T09:37:32 | {} | MEMBER |
vuejs | core | 809,310,315 | 3,512 | posva | Read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro | 2021-03-29T11:40:59 | 2021-03-29T11:40:59 | {} | MEMBER |
vuejs | core | 809,647,578 | 3,507 | danyadev | https://github.com/vuejs/vue-next/issues/1167
| 2021-03-29T19:24:55 | 2021-03-29T19:24:55 | {
"laugh": 3
} | CONTRIBUTOR |
vuejs | core | 809,691,910 | 3,516 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/3288 | 2021-03-29T20:31:44 | 2021-03-29T20:31:44 | {} | MEMBER |
vuejs | core | 809,700,604 | 2,878 | yyx990803 | Thanks a lot for the PR! I think the type literal syntax is more pleasant (and also closer to the runtime object equivalent):
```ts
defineEmit<{
(e: 'foo' | 'bar'): void
(e: 'baz', id: number): void
}>()
```
Which is implemented in bb8cdcad. I think it's better to not allow too many variances so closing ... | 2021-03-29T20:43:57 | 2021-03-29T20:43:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 806,490,346 | 1,539 | jiraiyame | this problem seems can be solved by using `::v-slotted()` pseudo element in scoped style. it's works for me:
https://github.com/vuejs/rfcs/blob/master/active-rfcs/0023-scoped-styles-changes.md | 2021-03-25T09:16:07 | 2021-03-25T09:18:09 | {
"+1": 2
} | NONE |
vuejs | core | 808,474,731 | 2,765 | yyx990803 | See d5824b97 - the tracking happens because the watcher callbacks are flushed during `updateComponentPreRender`, so it makes more sense for the tracking to be disabled there instead. | 2021-03-26T19:54:07 | 2021-03-26T19:54:07 | {} | MEMBER |
vuejs | core | 805,607,686 | 3,469 | Livijn | I created a new issue instead so it will be clearer: #3475 | 2021-03-24T08:32:27 | 2021-03-24T08:32:27 | {} | NONE |
vuejs | core | 808,721,364 | 3,493 | relief-melone | Thanks for the quick reply. That was indeed the problem. Since in my test project (where I am actually importing the source from my library) I was adding vue from cdn but using the compiler version 3.0.7 this did not work. And importing the built version did not work as it was compiled using an older version.
Now I ... | 2021-03-27T11:57:21 | 2021-03-27T12:00:21 | {} | NONE |
vuejs | core | 809,146,906 | 389 | HcySunYang | This PR is stale... | 2021-03-29T07:36:54 | 2021-03-29T07:36:54 | {} | MEMBER |
vuejs | core | 809,515,926 | 3,510 | yyx990803 | Fixed in 69b47272 | 2021-03-29T16:16:20 | 2021-03-29T16:16:20 | {} | MEMBER |
vuejs | core | 805,630,396 | 3,475 | Justineo | https://github.com/vuejs/vue-next/blob/eb1fae63f926435fb0eef890663d24e09d4c79e1/packages/compiler-dom/src/transforms/stringifyStatic.ts#L73-L85
As we can see if you have more than 4 `<option>`s, Vue's compiler will try to stringify static nodes for performance reasons. So when you have 5 `<option>`s, the first `<opt... | 2021-03-24T09:10:02 | 2021-03-24T09:11:00 | {
"+1": 2
} | MEMBER |
vuejs | core | 806,843,651 | 3,401 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-25T14:23:06 | 2021-03-25T14:23:06 | {} | CONTRIBUTOR |
vuejs | core | 806,943,519 | 3,377 | yyx990803 | See cleaner fix in 41e02f0f | 2021-03-25T15:23:57 | 2021-03-25T15:23:57 | {} | MEMBER |
vuejs | core | 808,262,550 | 3,491 | yyx990803 | Should be fixed by d668d48e | 2021-03-26T14:27:06 | 2021-03-26T14:27:06 | {} | MEMBER |
vuejs | core | 808,723,313 | 3,493 | LinusBorg | `rollup-plugin-vue` supports all compiler versions:
https://github.com/vuejs/rollup-plugin-vue/blob/next/package.json#L26
you just have to make sure that the compiler installed in the project is for 3.0.8.
But before doing that maybe wait a bit until we can communicate clearly how we proceed with this issue.
... | 2021-03-27T12:13:27 | 2021-03-27T12:13:27 | {} | MEMBER |
vuejs | core | 808,850,797 | 3,395 | HcySunYang | > Also strange comment text here
should be fine now | 2021-03-28T05:37:59 | 2021-03-28T05:37:59 | {} | MEMBER |
vuejs | core | 809,627,496 | 3,515 | posva | Read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-03-29T18:53:11 | 2021-03-29T18:53:11 | {} | MEMBER |
vuejs | core | 805,534,878 | 3,472 | edison1105 | Duplicate of #2821 see #2827 | 2021-03-24T06:19:41 | 2021-03-24T06:20:43 | {} | MEMBER |
vuejs | core | 805,519,985 | 3,471 | edison1105 | as a workround:
```javascript
const defaultV = { val: 1 }
props: {
foo: {
type: Object,
default: () => (defaultV)
},
}
``` | 2021-03-24T05:49:30 | 2021-03-24T09:15:23 | {} | MEMBER |
vuejs | core | 806,294,691 | 3,478 | HcySunYang | This has already been discussed, please see [this thread](https://github.com/vuejs/vue-next/issues/1135), we will track it there. | 2021-03-25T01:36:19 | 2021-03-25T01:36:19 | {} | MEMBER |
vuejs | core | 808,037,342 | 1,218 | takhello | ueCompilerError: v-model value must be a valid JavaScript member expression.
v-model="getColumn(rowIndex, index)._filterVisible" | 2021-03-26T08:33:32 | 2021-03-26T08:33:32 | {
"+1": 1
} | NONE |
vuejs | core | 808,038,055 | 1,234 | takhello | err~
v-model="getColumn(rowIndex, index)._filterVisible" | 2021-03-26T08:35:02 | 2021-03-26T08:35:02 | {} | NONE |
vuejs | core | 808,169,840 | 3,486 | AZmake | Thanks, and I found solution in this [vite2 vue jsx](https://github.com/vitejs/vite/issues/1286) | 2021-03-26T12:15:09 | 2021-03-26T12:15:09 | {
"+1": 2
} | NONE |
vuejs | core | 809,466,600 | 3,389 | lycHub | I have the same problem. Have you solved it? | 2021-03-29T15:18:01 | 2021-03-29T15:18:01 | {} | NONE |
vuejs | core | 805,621,084 | 3,474 | posva | If we save the cache on the prop definition object, wouldn't it fail with two instances of the same component (as both would use the same reference to the same object)? It could also fail if people use the same prop object in two props (which they shouldn't), no?
Maybe it's safer to save it in the instance? It could... | 2021-03-24T08:55:36 | 2021-03-24T08:55:36 | {} | MEMBER |
vuejs | core | 808,722,067 | 3,493 | LinusBorg | > maybe we can introduce these changes together in 3.1 ?
Would be a better strategy. Also gives us to to rethink how to introduce the change while creating as little friction as possible. | 2021-03-27T12:02:20 | 2021-03-27T12:02:20 | {} | MEMBER |
vuejs | core | 809,001,019 | 3,500 | HcySunYang | This is expected, if you want to inject the reactive version, you need to wrap the `commentList` with another object, see https://codepen.io/hcysunyang/pen/yLgJGJQ | 2021-03-29T01:05:41 | 2021-03-29T01:05:41 | {
"heart": 1
} | MEMBER |
vuejs | core | 809,096,751 | 3,242 | HcySunYang | What problem does this PR want to solve? | 2021-03-29T06:08:08 | 2021-03-29T06:08:08 | {} | MEMBER |
vuejs | core | 809,699,125 | 3,505 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2021-03-29T20:41:29 | 2021-03-29T20:41:29 | {} | CONTRIBUTOR |
vuejs | core | 805,621,508 | 3,308 | posva | Not yet | 2021-03-24T08:56:19 | 2021-03-24T08:56:19 | {} | MEMBER |
vuejs | core | 806,584,228 | 3,481 | HcySunYang | @pikax I updated the PR, can you give a new review | 2021-03-25T11:44:36 | 2021-03-25T11:44:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 808,066,540 | 1,218 | Kingbultsea | > ueCompilerError: v-model value must be a valid JavaScript member expression.
>
> v-model="getColumn(rowIndex, index)._filterVisible"
you can use ```@change``` and ```:value``` | 2021-03-26T09:25:34 | 2021-03-26T09:25:34 | {} | CONTRIBUTOR |
vuejs | core | 808,250,697 | 3,489 | yyx990803 | ```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-03-26T14:10:54 | 2021-03-26T14:11:50 | {} | MEMBER |
vuejs | core | 808,715,438 | 3,493 | HcySunYang | You should rebuild your project(`vue-mapbox-ts`) with vue 3.0.8's compiler. In 3.0.8, we refactored the runtime implementation of scope style, it has no changes to the user-side API, but for library authors, you must rebuild your library with vue 3.0.8's new compiler, otherwise it cannot be used for 3.0.8+ | 2021-03-27T11:16:40 | 2021-03-27T11:16:40 | {} | MEMBER |
vuejs | core | 809,037,039 | 3,498 | HcySunYang | This seems to be intentional. With or without `v-slot` determines whether it needs to be processed by the `vFor` transform, so in essence, they are treated differently. We can see the details here https://github.com/vuejs/vue-next/blob/master/packages/compiler-core/src/transform.ts#L463-L465 | 2021-03-29T03:18:26 | 2021-03-29T03:18:26 | {} | MEMBER |
vuejs | core | 809,121,104 | 3,504 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.34 KB (0%) |
| runtime-dom.global.prod.js | 27.42 KB (0%) |
| size-check.global.prod.js | 16.58 KB (0%) | | 2021-03-29T06:54:57 | 2021-03-29T06:54:57 | {} | NONE |
vuejs | core | 809,121,493 | 3,505 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.34 KB (0%) |
| runtime-dom.global.prod.js | 27.42 KB (0%) |
| size-check.global.prod.js | 16.58 KB (0%) | | 2021-03-29T06:55:40 | 2021-03-29T06:55:40 | {} | NONE |
vuejs | core | 809,123,123 | 3,506 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/13057?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your tes... | 2021-03-29T06:58:31 | 2021-03-29T06:58:31 | {} | CONTRIBUTOR |
vuejs | core | 809,127,384 | 2,948 | HcySunYang | Hi, thanks for this PR, but please see https://github.com/vuejs/vue-next/pull/3501 | 2021-03-29T07:05:53 | 2021-03-29T07:05:53 | {} | MEMBER |
vuejs | core | 806,867,547 | 3,478 | henribru | I'm a bit confused about why this is a duplicate. That issue seems to be talking about runtime behavior (and is also related to `computed`, although I guess that doesn't necessarily matter) while I'm talking about types? Like I mentioned what I'm doing works fine at runtime, it's strictly Typescript that forbids me fro... | 2021-03-25T14:37:56 | 2021-03-25T14:39:13 | {
"+1": 2
} | NONE |
vuejs | core | 807,006,125 | 3,377 | LinusBorg | Definitely the better solution, thanks. | 2021-03-25T16:03:04 | 2021-03-25T16:03:04 | {} | MEMBER |
vuejs | core | 808,598,859 | 3,490 | HcySunYang | The SFC parser is opinionated, can you put your use case here? | 2021-03-27T00:10:11 | 2021-03-27T00:10:11 | {} | MEMBER |
vuejs | core | 808,756,060 | 3,395 | kospl | Also _strange_ comment text here:
https://github.com/vuejs/vue-next/blob/67039b34342d2a00029e1ad0cf8eb98fdfcf0730/packages/compiler-core/src/options.ts#L51-L57 | 2021-03-27T16:13:59 | 2021-03-27T16:13:59 | {} | NONE |
vuejs | core | 808,873,277 | 3,496 | HcySunYang | This is intentional, text interpolation always stringifies it. If you want to render VNode in template, you need to use dynamic components, see https://codesandbox.io/s/laughing-hoover-fgipn?file=/src/App.vue | 2021-03-28T09:51:32 | 2021-03-28T09:51:32 | {} | MEMBER |
vuejs | core | 808,993,410 | 2,513 | niqingyang | > > I have the same problem in 3.0.7. Is there a solution now？[the reproduce](https://stackblitz.com/edit/vue3-iframe-teleport-demo?file=src%2FApp.vue)
>
> raise by the iframe's event.timeStamp. need to wait until the iframe's creation time longer than clickEvent's creation time.
It's not a solution.🙁 | 2021-03-29T00:38:46 | 2021-03-29T00:38:46 | {} | NONE |
vuejs | core | 809,228,571 | 3,509 | posva | Let's keep #3508 and add a code review there next time, it's easier to handle.
It's also not a good idea from a perf perspective to create an array everytime | 2021-03-29T09:31:28 | 2021-03-29T09:31:28 | {} | MEMBER |
vuejs | core | 805,493,747 | 3,472 | thexeos | This has a simple workaround: changing the alias of the subcomponent that is causing the problem.
For example, instead of having:
> pages/PrivacyPolicy.vue
```
<template>
<PrivacyPolicy />
</template>
```
You can have:
> pages/PrivacyPolicy.vue
```
<template>
<PrivacyPolicyContents />
</templat... | 2021-03-24T04:51:16 | 2021-03-24T04:51:16 | {} | NONE |
vuejs | core | 805,671,304 | 3,475 | Justineo | There seems to be another bug that `<option :value="null">` is rendered as `<option value>` when not taking the optimization path as for Vue 3 we have taken [a new strategy for attribute coercion](https://github.com/vuejs/rfcs/blob/master/active-rfcs/0024-attribute-coercion-behavior.md) and the expected output should b... | 2021-03-24T10:10:41 | 2021-03-24T10:10:41 | {} | MEMBER |
vuejs | core | 808,118,804 | 3,478 | posva | Isn't this a limitation of the typing system:
- When reading from reactive you always get a raw value (no ref wrapper):
```ts
const data = reactive({ a: ref(0) })
data.a // 0
```
- When writing/setting, you need to use the same type, otherwise you would have to add the necessary checks when reading too
... | 2021-03-26T10:55:05 | 2021-03-26T10:55:05 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.