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 | 748,456,891 | 2,842 | posva | Please read https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro and open a new issue with a full reproduction: Your repro seems to be missing the actual code to show the problem and should not contain TS, routing, nor stores | 2020-12-19T10:50:10 | 2020-12-19T10:50:10 | {} | MEMBER |
vuejs | core | 748,457,821 | 2,827 | posva | I would say in practice, naming a component the same in different folders is a bad practice (https://v3.vuejs.org/style-guide/#tightly-coupled-component-names-strongly-recommended and all the naming recommendations).
In Vue 2, we used to need a `name` on the recursive component. Not needing it anymore looks like an ... | 2020-12-19T10:58:50 | 2020-12-19T10:58:50 | {} | MEMBER |
vuejs | core | 745,561,982 | 2,826 | LinusBorg | The problem is that you bundle Vue into the foo-bar package. This means that bar-app now contain two versions of Vue which are in conflict.
The solution is to properly configure rollup in foot-test to exclude Vue from the final bundle. | 2020-12-15T20:56:12 | 2020-12-15T20:56:12 | {} | MEMBER |
vuejs | core | 746,235,983 | 2,829 | 07akioni | > It's really complicated too.like #2768
Yes, I think it may be caused by the same reason (due to the version in which it fails). However I have no time for debugging it😂. Hope it can be fixed soon. | 2020-12-16T12:45:32 | 2020-12-16T12:45:32 | {} | CONTRIBUTOR |
vuejs | core | 747,204,098 | 1,155 | xialvjun | ```tsx
defineComponent({
props: {
title:{
type: String,
required: true,
},
},
setup: (props) => {
return () => (
<p>{props.title}</p>
)
}
})
```
code like above is tedious.
I think this is better:
```tsx
defineComponent<{title:string, subTitle?: string}>... | 2020-12-17T04:53:23 | 2020-12-17T04:54:26 | {
"+1": 10,
"eyes": 3,
"heart": 1
} | NONE |
vuejs | core | 747,428,094 | 1,837 | LinusBorg | Vnodes in Vue 3 are context-free by design. This likely won't change.
There are other ways to achieve a solution so I'll close this. | 2020-12-17T13:07:02 | 2020-12-17T13:07:02 | {} | MEMBER |
vuejs | core | 747,501,803 | 2,469 | talmand | I'm not sure at this moment. Shortly after this issue was opened and a PR created the syntax and some of the functionality of the feature changed. So I closed the PR until these changes were more locked down. At this point I wouldn't be against closing the issue to reopen later if it something of this nature still pers... | 2020-12-17T15:17:23 | 2020-12-17T15:17:23 | {} | NONE |
vuejs | core | 747,900,347 | 2,841 | shadowings-zy | That's because the kebab-case custom event `foo-bar` in web components will parse to `foobar`. Vue will add `foobar` as the name of event listener. I think this needs a fix. | 2020-12-18T06:37:17 | 2020-12-18T06:37:17 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 745,697,095 | 2,821 | edison1105 | @fredrivett It's relate to version of `@vue/compiler-sfc`.
Using a component in its own template allows for recursive components after this commit 67d1aac6ae683a3a7291dff15071d1eeacb7d22a.
I think it works fine in `v3.0.3`.
if use `"@vue/compiler-sfc": "3.0.4"` will be encountered this problem.
| 2020-12-16T01:08:25 | 2020-12-16T01:08:25 | {
"+1": 2
} | MEMBER |
vuejs | core | 745,801,226 | 2,786 | dependabot-preview[bot] | Superseded by #2830. | 2020-12-16T06:41:32 | 2020-12-16T06:41:32 | {} | CONTRIBUTOR |
vuejs | core | 746,463,926 | 1,600 | martinbean | @yyx990803 Can we _please_ get an official response from _someone_ on this issue? Vue should _not_ be usurping browser default behaviour of inline element spacing. | 2020-12-16T15:21:17 | 2020-12-16T15:21:17 | {
"+1": 4
} | NONE |
vuejs | core | 747,259,921 | 2,838 | dreamSeekerYu | 当我移除 Element3 之后，这个 bug 不复存在，显然这个问题不是 vue 本身导致，建议关闭此 issue | 2020-12-17T07:15:30 | 2020-12-17T07:15:30 | {} | NONE |
vuejs | core | 747,260,126 | 2,838 | dreamSeekerYu | 当我移除 Element3 之后，这个 bug 不复存在，显然这个问题不是 vue 本身导致，建议关闭此 issue | 2020-12-17T07:15:57 | 2020-12-17T07:15:57 | {} | NONE |
vuejs | core | 747,421,517 | 1,166 | LinusBorg | > Actually, we may need to detect non composition api usage for backwards compat. Or we need an RFC to officially deprecate this (I never considered it good practice anyway, and it creates a TON of complexity when used inside nested v-fors.)
@yyx990803 We actually can do the same thing we recommend for the compositi... | 2020-12-17T12:53:15 | 2020-12-17T12:53:15 | {} | MEMBER |
vuejs | core | 747,433,501 | 2,669 | LinusBorg | I'm torn about what to do here.
In Vue 2, all components had root nodes, and we always applied the data-v property to child components' root element.
That actually was a caveat, as styles from the parent could accidentally bleed into the child if the child root contained a class of the same name (unintentionally... | 2020-12-17T13:17:49 | 2020-12-17T13:17:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 747,868,495 | 2,843 | edison1105 | IMO, this will make `shallowProxy` and `reactiveProxy` confused. Developers do not know how to choose which API to use. | 2020-12-18T04:59:31 | 2020-12-18T04:59:31 | {} | MEMBER |
vuejs | core | 747,954,585 | 2,143 | liuweiGL | > > Similar to `<transition>`, the new Suspense now must be used with `<router-view>` via its [slot-based syntax](https://next.router.vuejs.org/api/#router-view-s-v-slot) because it now must have direct access to the toggled root node:
> > ```
> > <router-view v-slot="{ Component }">
> > <suspense>
> > <compo... | 2020-12-18T08:54:15 | 2020-12-18T08:54:41 | {
"rocket": 3
} | NONE |
vuejs | core | 748,466,056 | 2,850 | Philipp-M | Thanks, this is actually what I came up with as well. | 2020-12-19T12:10:15 | 2020-12-19T12:10:15 | {} | NONE |
vuejs | core | 745,184,906 | 2,817 | posva | Wouldn't this completely remove vnode reusage and end up in a big perf impact? | 2020-12-15T10:04:24 | 2020-12-15T10:04:24 | {} | MEMBER |
vuejs | core | 746,198,900 | 2,828 | LinusBorg | This is expected behaviour as all slots in Vue 3 are now scoped slots, for which reactive dependencies within the slot content are collected in the child, as @07akioni correctly explained.
There are mutlitple way to deal with this, i.e. watching the data in question or using the [transition's events](https://v3.vuej... | 2020-12-16T12:14:46 | 2020-12-16T12:15:09 | {} | MEMBER |
vuejs | core | 747,411,654 | 2,826 | LinusBorg | This is a topic that needs documentation in the docs/cookbook section, in a recipe for how to build plugins/libraries. It's not solvable in this repo. | 2020-12-17T12:31:51 | 2020-12-17T12:31:51 | {} | MEMBER |
vuejs | core | 747,655,095 | 2,429 | lee-orr | I'm still getting this issue w/ `@vue/compiler-sfc 3.0.4` & `vue 3.0.4`. Was able to reproduce it in a JSFiddle that only relies on the unpkg dist for vue 3.0.4: https://jsfiddle.net/meo9Lfya/3/
You'll notice that the event works when clicking the "lowercase" button, but not the "kebab" button, but when using "addEven... | 2020-12-17T19:36:24 | 2020-12-17T19:36:24 | {} | NONE |
vuejs | core | 748,092,155 | 2,848 | 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).
Please read https://new-issue.vuejs.org/?repo=vuejs/vue... | 2020-12-18T13:45:45 | 2020-12-18T13:46:13 | {} | MEMBER |
vuejs | core | 748,241,215 | 2,850 | LinusBorg | Conceptually, returning a computed from a computed doesn't make sense in my book.
Architecturally, computed's need to be called synchronously in setup in order to be properly garbage collected later.
Technically, the value should probably be properly unwrapped anyway, but as this is not really a use case concidered... | 2020-12-18T18:17:46 | 2020-12-18T18:19:12 | {} | MEMBER |
vuejs | core | 745,191,689 | 2,790 | qq397023775 | Just calling @yyx990803 , I believe he can give me the answer. | 2020-12-15T10:16:53 | 2020-12-15T10:16:53 | {} | NONE |
vuejs | core | 745,250,738 | 2,790 | luwuer | > The problem you see comes from logging in the console the HTML node, but the variable contains the right HTMLElement all the time: the `div` with the `hello` text. At some point, the node gets reused (as mentioned in a comment above) but the ref ends up pointing to the correct node.
Ref pointing to wrong HTMLElem... | 2020-12-15T12:14:23 | 2020-12-15T12:16:32 | {} | CONTRIBUTOR |
vuejs | core | 745,801,295 | 2,787 | dependabot-preview[bot] | Superseded by #2831. | 2020-12-16T06:41:43 | 2020-12-16T06:41:43 | {} | CONTRIBUTOR |
vuejs | core | 747,411,144 | 2,835 | LinusBorg | ```postcss
.main-menu, :slotted(.main-menu) {
```
This will apply styles to both the current component and the slotted elements.
I would not recommend `:deep()` as that will apply the styles to *all* nested DOM elements, possibly messing with styles in other, nested components. `:deep-()` is an escape hatch you... | 2020-12-17T12:30:46 | 2020-12-17T12:30:46 | {
"+1": 1
} | MEMBER |
vuejs | core | 747,603,266 | 2,835 | LinusBorg | I'll reopen this for the sass error, that seems worth investigating.
We might have to do something here at the compiler level to make these nested syntaxes work. Or maybe I'm missing something. | 2020-12-17T18:02:07 | 2020-12-17T18:02:07 | {
"+1": 3
} | MEMBER |
vuejs | core | 748,458,140 | 2,809 | posva | The typing is correct. If you want it to be a number, you should do
```ts
const r = ref<{ a: number } | undefined>({ a: 3 });
``` | 2020-12-19T11:01:17 | 2020-12-19T11:01:28 | {
"+1": 1
} | MEMBER |
vuejs | core | 748,473,714 | 2,164 | pikax | I believe the build is failing because of usage of Typescript `^4.1.x` with `@microsoft/api-extractor` | 2020-12-19T13:17:07 | 2020-12-19T13:17:07 | {} | MEMBER |
vuejs | core | 745,237,023 | 2,821 | edison1105 | It is indeed done deliberately. If we compare `filename `here, maybe we can avoid this problem.
https://github.com/vuejs/vue-next/blob/64d4681e4b9d88e17cd1515014866d43d0424d14/packages/compiler-core/src/transforms/transformElement.ts#L266-L273
https://github.com/vuejs/vue-next/blob/67d1aac6ae683a3a7291dff15071d1e... | 2020-12-15T11:45:03 | 2020-12-15T11:45:03 | {} | MEMBER |
vuejs | core | 745,455,133 | 2,819 | lukaskoeller | Now I created another component `<TestButton>` that only differs from `<Button>` that its `name:` is accordingly. Implemented the same way `<TestButton>` is also showing no error anymore... | 2020-12-15T17:46:45 | 2020-12-15T17:46:45 | {} | NONE |
vuejs | core | 745,802,633 | 2,832 | 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%) | | 2020-12-16T06:44:56 | 2020-12-16T06:44:56 | {} | NONE |
vuejs | core | 747,162,894 | 1,600 | Justineo | See https://codesandbox.io/s/jolly-poincare-ibywi?file=/src/App.vue
Whitespace-only text nodes will be removed only when they include line feeds. If something is treated as inline content, just put them in the same line and it should just work.
/cc @vuejs/docs I think we should put this into the docs so that peop... | 2020-12-17T02:26:47 | 2020-12-17T02:26:47 | {
"rocket": 1
} | MEMBER |
vuejs | core | 747,426,322 | 1,762 | LinusBorg | confirmed | 2020-12-17T13:03:32 | 2020-12-17T13:03:32 | {} | MEMBER |
vuejs | core | 747,643,038 | 2,835 | LinusBorg | To be honest, nested styles probably weren't considered during the design of this pseudo selector api - likely because we usually don't, or rarely, use it in SFCs. Scoped styles usually make BEM unnecessary in my opinion, flat styles work fine for most things.
We will have to discuss how to approach this.
For no... | 2020-12-17T19:15:13 | 2020-12-18T06:57:50 | {} | MEMBER |
vuejs | core | 745,184,302 | 2,790 | posva | The problem you see comes from logging in the console the HTML node, but the variable contains the right HTMLElement all the time: the `div` with the `hello` text. At some point, the node gets reused (as mentioned in a comment above) but the ref ends up pointing to the correct node. If you manage to reproduce it where ... | 2020-12-15T10:03:26 | 2020-12-15T10:03:26 | {} | MEMBER |
vuejs | core | 747,495,999 | 2,840 | posva | Do you mean we should remove the check of `typeof` of `string`? https://github.com/vuejs/vue-next/pull/1788/files#r465890830 | 2020-12-17T15:09:09 | 2020-12-17T15:09:09 | {} | MEMBER |
vuejs | core | 738,207,998 | 2,720 | ozguruysal | Thanks for quick response @posva. Not sure if there's another way but, I cloned and built Vue, and copied the new `dist` folder to my project's `node_modules/vue` folder to test. If I've done it right, I can still see the issue happening. | 2020-12-03T18:36:09 | 2020-12-03T18:36:22 | {} | NONE |
vuejs | core | 738,571,277 | 2,618 | tangjinzhou | @posva @HcySunYang 3.0.4 also have this problem | 2020-12-04T05:20:18 | 2020-12-04T05:20:18 | {} | CONTRIBUTOR |
vuejs | core | 739,018,476 | 2,378 | yyx990803 | Appreciate the PR, but as @unbyte has pointed out, these added tests are redundant since `ref(obj).value === reactive(obj)`. | 2020-12-04T21:02:01 | 2020-12-04T21:02:01 | {} | MEMBER |
vuejs | core | 739,072,635 | 2,462 | yyx990803 | See https://github.com/vuejs/vue-next/issues/2450#issuecomment-739072455 | 2020-12-04T23:19:00 | 2020-12-04T23:19:00 | {} | MEMBER |
vuejs | core | 739,467,156 | 2,732 | HcySunYang | This PR has made some ambiguities, that is, a pre-flush cb is not actually executed before rendering. | 2020-12-06T07:30:35 | 2020-12-06T07:30:35 | {} | MEMBER |
vuejs | core | 739,703,469 | 2,746 | 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%) | | 2020-12-07T06:37:35 | 2020-12-07T06:37:35 | {} | NONE |
vuejs | core | 739,824,739 | 2,650 | joudinet | Yes I can get a tarball from npm registry (e.g., https://registry.npmjs.org/vue/-/vue-3.0.4.tgz) but this tarball is missing the LICENSE file. | 2020-12-07T10:24:19 | 2020-12-07T10:24:19 | {} | NONE |
vuejs | core | 739,845,424 | 2,650 | posva | Yeah, so I think we could copy the LICENSE file from the root to all the packages when publishing. Right now it's not included because the License is only at the root folder | 2020-12-07T11:02:45 | 2020-12-07T11:02:45 | {} | MEMBER |
vuejs | core | 741,561,515 | 2,773 | 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%) | | 2020-12-09T06:26:15 | 2020-12-09T06:26:15 | {} | NONE |
vuejs | core | 738,314,654 | 2,720 | yyx990803 | This is broken due to e2618a63 and #2716 does not fix it.
So I just landed cbaa3805 which makes the code work but requires using `@enter` and `@leave` instead of `@before-enter` and `@before-leave`.
I know this is technically still a breaking change, but it's somewhat necessary to adhere to the intended behavior.... | 2020-12-03T21:11:49 | 2020-12-03T21:12:06 | {} | MEMBER |
vuejs | core | 738,585,636 | 2,618 | HcySunYang | it's solved, see: https://codesandbox.io/s/red-shape-bc720 | 2020-12-04T06:03:57 | 2020-12-04T06:03:57 | {} | MEMBER |
vuejs | core | 738,844,903 | 2,721 | yyx990803 | fixed in vue-loader 16.1.1: https://github.com/vuejs/vue-loader/releases/tag/v16.1.1 | 2020-12-04T15:25:28 | 2020-12-04T15:25:28 | {
"+1": 1
} | MEMBER |
vuejs | core | 739,449,907 | 2,737 | HcySunYang | This has been fixed in https://github.com/vuejs/vue-next/commit/c59897c7b0dbd82b5bbf3fbca945c0639ac37fb8. Not released | 2020-12-06T03:40:01 | 2020-12-06T03:40:01 | {
"+1": 1
} | MEMBER |
vuejs | core | 739,703,245 | 2,744 | 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%) | | 2020-12-07T06:37:09 | 2020-12-07T06:37:09 | {} | NONE |
vuejs | core | 739,954,060 | 2,753 | edison1105 | > Can you add tests?
Done! | 2020-12-07T14:30:58 | 2020-12-07T14:30:58 | {} | MEMBER |
vuejs | core | 740,099,629 | 2,756 | posva | That is like not using `reactive` at all and returning what is passed as an argument... | 2020-12-07T18:33:05 | 2020-12-07T18:33:05 | {} | MEMBER |
vuejs | core | 740,313,615 | 2,735 | CHOYSEN | > @CHOYSEN if you build my [repo](https://github.com/stephanedemotte/_issue-vue3-script-setup) you didn't get [that](http://test-vue-export.gaidaandsteph.com/) ?
Yes, i clone your repo and build it, then start a server with koa, it work fine for me | 2020-12-08T02:11:03 | 2020-12-08T02:11:03 | {} | CONTRIBUTOR |
vuejs | core | 740,380,143 | 2,735 | CHOYSEN | @stephanedemotte
There are some `vue3.0.3` information in the file, which should be caused by this | 2020-12-08T05:12:49 | 2020-12-08T05:12:49 | {} | CONTRIBUTOR |
vuejs | core | 741,564,148 | 2,775 | terminalqo | 
| 2020-12-09T06:31:53 | 2020-12-09T06:31:53 | {} | NONE |
vuejs | core | 741,577,009 | 2,766 | yustnip | Thanks, it works! | 2020-12-09T07:00:30 | 2020-12-09T07:00:30 | {} | NONE |
vuejs | core | 738,588,927 | 2,723 | 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/11226?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... | 2020-12-04T06:13:21 | 2020-12-04T06:13:21 | {} | CONTRIBUTOR |
vuejs | core | 739,460,412 | 2,721 | yoyoys | @yyx990803 thanks, how can I use newer vue-loader for vue-cli project? | 2020-12-06T05:58:48 | 2020-12-06T05:58:48 | {} | NONE |
vuejs | core | 739,667,667 | 2,743 | edison1105 | You should do it like this:
``` javascript
const { proxy } = getCurrentInstance()
console.log(proxy.$store)
```
It is not recommended to use `const {ctx} = getCurrentInstance()` because the production environment and development environment get `ctx` inconsistent.
| 2020-12-07T05:11:32 | 2020-12-07T05:31:43 | {} | MEMBER |
vuejs | core | 741,552,454 | 2,768 | luwuer | Repetitive description.
And its really complicated. | 2020-12-09T06:04:49 | 2020-12-09T06:04:49 | {} | CONTRIBUTOR |
vuejs | core | 738,637,570 | 2,724 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/2720 | 2020-12-04T08:18:24 | 2020-12-04T08:18:24 | {} | MEMBER |
vuejs | core | 739,415,575 | 2,738 | yyx990803 | This is a known issue and is a limitation of TypeScript handling circular inference of `ThisType` (which is only present if using a non-arrow function).
There is currently no fix for this (will have to be upstream in TS) so using arrow function is the recommended workaround. | 2020-12-05T21:01:13 | 2020-12-05T21:01:13 | {
"+1": 3
} | MEMBER |
vuejs | core | 739,448,188 | 2,737 | jw-foss | This bug might be caused by https://github.com/vuejs/vue-next/blame/v3.0.4/packages/runtime-core/src/renderer.ts#L1007, I'm also looking for its root cause. | 2020-12-06T03:13:14 | 2020-12-06T03:13:14 | {} | NONE |
vuejs | core | 739,703,683 | 2,747 | 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%) | | 2020-12-07T06:38:04 | 2020-12-07T06:38:04 | {} | NONE |
vuejs | core | 739,916,270 | 2,754 | 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 should help you https://v3.vuejs.org/guide/install... | 2020-12-07T13:24:33 | 2020-12-07T13:24:33 | {} | MEMBER |
vuejs | core | 739,958,377 | 2,736 | surmon-china | @yyx990803 | 2020-12-07T14:38:27 | 2020-12-07T14:38:27 | {} | NONE |
vuejs | core | 739,118,343 | 2,728 | edison1105 | a little complicated
https://github.com/vuejs/vue-next/blob/8936e53b10a507b80ffc5b0ecaa6a1a0322f46cc/packages/runtime-core/src/componentOptions.ts#L903-L937
Maybe, need to use `pauseTracking`, `resetTracking` wraps `handler`.
| 2020-12-05T03:51:11 | 2020-12-07T14:55:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 740,422,717 | 2,761 | 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%) | | 2020-12-08T06:59:00 | 2020-12-08T06:59:00 | {} | NONE |
vuejs | core | 741,560,869 | 2,772 | 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%) | | 2020-12-09T06:24:55 | 2020-12-09T06:24:55 | {} | NONE |
vuejs | core | 737,759,795 | 2,715 | web-97 | > I don't get an error (could be a cache problem of Codesandbox) but you are using the same `key` for all of your todos, they must be different.
Thanks, updated the new code is not a problem with key | 2020-12-03T08:53:44 | 2020-12-03T08:53:55 | {} | NONE |
vuejs | core | 738,769,500 | 2,726 | edison1105 | I think this warning will not affect the display of the page. | 2020-12-04T12:56:20 | 2020-12-04T13:37:06 | {} | MEMBER |
vuejs | core | 739,505,823 | 2,740 | leopiccionia | I think that PR #2729 should be a fix. | 2020-12-06T13:52:58 | 2020-12-06T17:13:53 | {} | CONTRIBUTOR |
vuejs | core | 739,698,754 | 2,743 | edison1105 | Because this approach is not recommended, it is not explained in the documentation.
The recommended approach is：https://v3.vuejs.org/api/application-config.html#globalproperties
``` javascript
app.config.globalProperties.foo = 'bar'
app.component('child-component', {
mounted() {
console.log(this.foo) //... | 2020-12-07T06:27:21 | 2020-12-07T06:27:21 | {} | MEMBER |
vuejs | core | 739,792,313 | 2,749 | AliLozano | @posva thanks by the fast reply, and to not leave the problem in the air, because I think it could be a important problem and could be problematic for news APIs, there are a possibility to create a method "reactiveWithRefs" that make reactive but without unwrapping? this could solve the problem, or it is a breaking cha... | 2020-12-07T09:26:25 | 2020-12-07T09:26:25 | {} | NONE |
vuejs | core | 740,422,600 | 2,760 | 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%) | | 2020-12-08T06:58:43 | 2020-12-08T06:58:43 | {} | NONE |
vuejs | core | 738,593,472 | 2,722 | edison1105 | I rebase the latest master and debug this bug, strangely, it works fine. | 2020-12-04T06:26:10 | 2020-12-04T06:26:10 | {} | MEMBER |
vuejs | core | 740,552,573 | 2,751 | signor-pedro | Looks like this might be related, will investigate later https://github.com/vuejs/vue-next/issues/2474 | 2020-12-08T11:06:14 | 2020-12-08T11:06:14 | {} | NONE |
vuejs | core | 737,857,029 | 2,195 | basvanmeurs | > @basvanmeurs Sorry I missed your comment. The ability to "re-activate" a scope is indeed interesting. But as the `effect` is not `re-activatable` with the current implementation, I'd suggest you open a RFC to add the ability to resume a stopped `effect`. After that, we can easily adapt it to the `effectScope`. What d... | 2020-12-03T10:37:16 | 2020-12-03T10:46:29 | {} | CONTRIBUTOR |
vuejs | core | 738,612,988 | 2,722 | sakura-flutter | > I rebase the latest master and debug this bug, strangely, it works fine.
I used the previous version and encountered the same problem, only global.prod.js | 2020-12-04T07:15:43 | 2020-12-04T07:15:43 | {} | NONE |
vuejs | core | 738,864,668 | 2,259 | yyx990803 | I'm not sure what this achieves honestly, this is an internal type for type inference only. The public type is `VNodeProps`. | 2020-12-04T16:01:21 | 2020-12-04T16:01:21 | {} | MEMBER |
vuejs | core | 739,072,455 | 2,450 | yyx990803 | *Note the following is using the updated `<script setup>` syntax but the same behavior applies.*
This is expected behavior, you could legit have a variable that is a valid tag or component definition and use it like this, e.g.:
```html
<script setup>
import { ref } from 'vue'
const tagToRender = ref('button')
... | 2020-12-04T23:18:19 | 2020-12-04T23:18:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 739,929,032 | 2,735 | stephanedemotte | @CHOYSEN if you build my [repo](https://github.com/stephanedemotte/_issue-vue3-script-setup) you didn't get [that](http://test-vue-export.gaidaandsteph.com/) ? | 2020-12-07T13:48:12 | 2020-12-07T13:48:12 | {} | NONE |
vuejs | core | 740,378,660 | 2,735 | CHOYSEN | @stephanedemotte
I find it, you should remove your `yarn.lock` and `node_modules`, then run `yarn` again | 2020-12-08T05:07:48 | 2020-12-08T05:07:48 | {} | CONTRIBUTOR |
vuejs | core | 740,502,357 | 2,762 | posva | Read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next&lang=zh-cn#why-repro
And open issues in English | 2020-12-08T09:33:38 | 2020-12-08T09:33:38 | {} | MEMBER |
vuejs | core | 739,774,364 | 2,748 | Zcating | The error should be `ToRef` type. | 2020-12-07T08:54:12 | 2020-12-07T08:54:12 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 739,777,456 | 2,739 | HcySunYang | https://github.com/vuejs/vue-next/blob/master/packages/compiler-core/src/transforms/vIf.ts#L270, the `createVNode` helper should be removed correctly. | 2020-12-07T09:00:10 | 2020-12-07T09:00:10 | {} | MEMBER |
vuejs | core | 739,787,580 | 2,748 | Zcating | ```
class ObjectRefImpl<T extends object, K extends keyof T> {
public readonly __v_isRef = true
constructor(private readonly _object: T, private readonly _key: K) {}
get value() {
return this._object[this._key]
}
set value(newVal) {
this._object[this._key] = newVal
}
}
```
The `O... | 2020-12-07T09:17:48 | 2020-12-07T09:18:08 | {} | CONTRIBUTOR |
vuejs | core | 739,795,821 | 2,650 | posva | The assets are now the source code without the dist files. The dist files are published on the npm registry so there must be a way to retrieve the actual url | 2020-12-07T09:32:48 | 2020-12-07T09:32:48 | {} | MEMBER |
vuejs | core | 739,798,308 | 2,751 | posva | @signor-pedro moved to the correct repository | 2020-12-07T09:37:26 | 2020-12-07T09:37:26 | {} | MEMBER |
vuejs | core | 739,920,858 | 2,754 | flyyuan | But no resolve my problem | 2020-12-07T13:33:12 | 2020-12-07T13:33:12 | {} | NONE |
vuejs | core | 740,660,394 | 2,766 | yustnip | Yes, it is. But I can't remove it another way. Example:
```
<template>
<component
:is="tag"
:type="tag === 'input' ? 'text' : null"
/>
</template>
<script lang="ts">
import { defineComponent } from 'vue';
export default defineComponent({
props: {
tag: {
type: String,... | 2020-12-08T14:41:59 | 2020-12-08T14:41:59 | {} | NONE |
vuejs | core | 741,454,129 | 2,765 | luwuer | Seems like that code executed synchronously does not have this problem because of code below:
https://github.com/vuejs/vue-next/blob/d87bc2b3b48dc3094f50e4a87227ddb09b8c7e38/packages/runtime-core/src/component.ts#L704-L711 | 2020-12-09T02:08:35 | 2020-12-09T02:36:03 | {} | CONTRIBUTOR |
vuejs | core | 741,575,088 | 2,775 | terminalqo | This is fine.
but : https://v3.vuejs.org/guide/component-props.html#prop-validation
| 2020-12-09T06:56:19 | 2020-12-09T06:56:50 | {} | NONE |
vuejs | core | 737,772,112 | 2,715 | posva | Then provide a valid reproduction, it's still the same code:
| 2020-12-03T09:15:49 | 2020-12-03T09:15:49 | {} | MEMBER |
vuejs | core | 738,174,524 | 2,720 | posva | Can you check if https://github.com/vuejs/vue-next/pull/2716 fixed the issue? | 2020-12-03T17:48:38 | 2020-12-03T17:48:38 | {} | MEMBER |
vuejs | core | 738,840,701 | 2,726 | LinusBorg | Yes. This warning will only affect attribute inheritance. components will continue to render and work.
Your issue is likely something else, please narrow it down - You can ask for help on chat.vuejs.org.
We don't have the capacity here to debug a complete application. When you can reproduce the issue, feel free t... | 2020-12-04T15:17:49 | 2020-12-04T15:18:33 | {} | MEMBER |
vuejs | core | 738,913,799 | 2,720 | ozguruysal | Ok I've figured out how to test the development build properly after reading [here](https://github.com/vuejs/vue-next/blob/master/.github/contributing.md#yarn-dev).
Just tested and works perfectly now. Thanks for the quick fix! | 2020-12-04T17:31:45 | 2020-12-04T17:31:45 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.