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 | 803,753,680 | 3,455 | trainiac | To be clear this doesn't work and I'd like typescript to tell me what what is being passed to ref is an error
```tsx
import { defineComponent } from "vue";
import CustomComponent from './CustomComponent'
defineComponent({
setup() {
const dom = ref(null)
const title = 'info'
return () => (
... | 2021-03-22T04:35:29 | 2021-03-22T04:36:27 | {} | NONE |
vuejs | core | 804,536,036 | 3,459 | kerm1it | Yes，you are right.
Although `override` is a very dangerous behavior, it should be allowed. We can display a warning message (eslint error) instead of a compilation error and cause the page to crash. | 2021-03-23T02:30:41 | 2021-03-23T02:30:41 | {} | NONE |
vuejs | core | 804,714,884 | 3,465 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.92 KB (0%) |
| runtime-dom.global.prod.js | 27.17 KB (0%) |
| size-check.global.prod.js | 16.47 KB (0%) | | 2021-03-23T08:27:31 | 2021-03-23T08:27:31 | {} | NONE |
vuejs | core | 805,083,637 | 3,470 | f-p-g | ok, my bad: I was using `v-bind` instead of `v-model`. | 2021-03-23T17:20:19 | 2021-03-23T17:20:19 | {} | NONE |
vuejs | core | 801,031,710 | 3,432 | HcySunYang | Currently, if an event is declared as `emits`, then we have no way to access its listener, neither through `$props` nor `$attrs`. Most of the time it’s okay, but it’s a little uncomfortable in recursive components, see https://github.com/vuejs/vue-next/issues/3361
| 2021-03-17T12:09:57 | 2021-03-17T12:09:57 | {
"+1": 3
} | MEMBER |
vuejs | core | 802,611,215 | 3,445 | LinusBorg | @jacekkarczmarczyk Thanks. totally missed the point of the example.
Looks like a bug in the compiler for that experimental syntax, indeed.
@zhangenming Sorry for misunderstanding. | 2021-03-19T07:17:10 | 2021-03-19T07:18:23 | {} | MEMBER |
vuejs | core | 803,470,916 | 2,819 | andre-cgn | Could you please re-open this ticket? The issue didn't magically disappear. If you don't use vue-cli but a webpack config with wp 5.27.0 and vue-loader 4.1.1 it can be re-procuded. For me it always happens when using component tag names with dashes. So using the tag name "value-input" causes the error while "valueinput... | 2021-03-20T22:12:51 | 2021-03-20T22:13:41 | {} | NONE |
vuejs | core | 803,748,030 | 3,280 | arpowers | @HcySunYang suggest this check is removed since it also causes slots not to work with SSR | 2021-03-22T04:16:36 | 2021-03-22T04:16:36 | {} | NONE |
vuejs | core | 803,759,016 | 3,455 | HcySunYang | I know what you mean: you mean that if jsx is used as the return value of setup then it is not allowed to be specified as a string, otherwise, it can. But we cannot restrict ref to not be able to specify a string, because it **actually** allows the use of string types. And I don’t think we can limit ref correctly unles... | 2021-03-22T04:55:12 | 2021-03-22T04:55:12 | {} | MEMBER |
vuejs | core | 804,531,007 | 3,459 | HcySunYang | One thing you did not realize is that even if you specify `null` or `undefined` for `v-html`, it will also overwrite the `children`:
```html
<div v-html="null">text</div>
```
The text node of this `div` tag will be overwritten, which is by design. If you want to do different processing according to the type of ... | 2021-03-23T02:15:58 | 2021-03-23T02:15:58 | {} | MEMBER |
vuejs | core | 801,536,799 | 3,437 | edison1105 | @LeonVlad
You mean that v3.0.6 works normally, but v3.0.7 reports an error, right?
| 2021-03-18T00:55:12 | 2021-03-18T00:55:12 | {} | MEMBER |
vuejs | core | 802,513,439 | 3,446 | HcySunYang | Add this to `hello-app/vue.config.js`, see https://github.com/vuejs/vue-next/issues/1503 for details
```js
config.resolve.alias.set('vue$', resolve(__dirname, 'node_modules/vue'))
``` | 2021-03-19T03:14:28 | 2021-03-19T03:14:28 | {
"+1": 4,
"hooray": 3
} | MEMBER |
vuejs | core | 803,515,189 | 3,451 | HcySunYang | Hey @rhengles , this is a bug, now you can’t use async components as your app's root.
Use cases that will fail:
```js
const app = createSSRApp(defineAsyncComponent({/* ... */}))
app.mount('xxx')
```
As a workaround, you can use functional components or stateful components to wrap it:
```js
const asyncC... | 2021-03-21T05:19:39 | 2021-03-21T05:19:39 | {
"+1": 3,
"rocket": 1
} | MEMBER |
vuejs | core | 803,516,340 | 3,453 | HcySunYang | > These codes enlarge the bundle code size very much, but they are no use for production mode.
This is wrong, for the production build bundle, the DEV code will not be included | 2021-03-21T05:32:35 | 2021-03-21T05:32:35 | {} | MEMBER |
vuejs | core | 803,738,043 | 3,258 | kuanyui | Any review progression on this PR? I think this is a necessary feature for validator.
I'm making a customed `<Input>` component like this, but the current API seems no way to refer a `prop` from another `prop`:
```js
type input_type_t = 'number' | 'text' | 'password'
const ALL_INPUT_TYPE: input_type_t[] = ['number'... | 2021-03-22T03:36:56 | 2021-03-22T03:38:25 | {} | NONE |
vuejs | core | 803,748,937 | 3,455 | HcySunYang | But according to the example I provided above, it allows specifying ref as a string | 2021-03-22T04:19:30 | 2021-03-22T04:19:30 | {} | MEMBER |
vuejs | core | 802,830,195 | 3,450 | posva | Since this is used in dev only, I think it makes more sense to add it on userland:
```js
app.config.globalProperties.console = console
```
This was also never supported in Vue 2 and it's very rare to use console.log in templates. It usually happens in methods, computed etc | 2021-03-19T13:24:36 | 2021-03-19T13:34:43 | {
"+1": 2,
"-1": 1
} | MEMBER |
vuejs | core | 803,752,970 | 3,455 | trainiac | jsx-next provides two syntaxes for writing render functions. It does work the way you wrote it but it does not work the way I wrote it. I prefer returning a render function from setup as it's more succinct and typescript tells me when a custom component is not within the template scope. jsx-next offers a way to write ... | 2021-03-22T04:32:49 | 2021-03-22T04:37:09 | {} | NONE |
vuejs | core | 803,799,639 | 3,455 | HcySunYang | @trainiac I made a PR https://github.com/vuejs/vue-next/pull/3458, but I’m not sure if it will eventually be accepted | 2021-03-22T06:31:25 | 2021-03-22T06:31:25 | {
"heart": 1
} | MEMBER |
vuejs | core | 803,939,250 | 3,457 | posva | Please, don't troll like this... The proper fix should still display the warning when appropriate. | 2021-03-22T10:07:32 | 2021-03-22T10:07:32 | {} | MEMBER |
vuejs | core | 804,518,025 | 3,459 | kerm1it | But when using it in jsx，it appears error instead of warning msg:
I think we should allow to use children and innerHTML at the same time.
In this case:
`<span innerHTML={ typeof msg === 'string' ?... | 2021-03-23T01:36:09 | 2021-03-23T01:36:44 | {} | NONE |
vuejs | core | 805,000,170 | 2,943 | ghost | Hi everyone!
I'm running into an error related to this when trying to run a simple test using typescript. I've come up with a minimum repo to reproduce this case at https://github.com/jjdive/vite-vue-ts-tests-error. Anyways, this is the error i get and it points to `if (container instanceof window.ShadowRoot &&` at ... | 2021-03-23T15:31:02 | 2021-03-23T15:31:02 | {
"+1": 1
} | NONE |
vuejs | core | 800,851,363 | 3,434 | HcySunYang | It’s better to use the first solution because it’s easier to understand | 2021-03-17T07:08:45 | 2021-03-17T07:08:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 803,514,477 | 3,453 | HcySunYang | 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-03-21T05:12:55 | 2021-03-21T05:12:55 | {} | MEMBER |
vuejs | core | 803,763,213 | 3,455 | trainiac | I'm not saying that vue should limit it for everyone. I'm saying that consumers of vue should be able to customize it for their own purposes. For example, by adding this to my application type definition files I fix this issue for custom components, because it ends up overriding what is defined in `@vue/runtime-dom`.
... | 2021-03-22T05:06:29 | 2021-03-22T05:15:24 | {} | NONE |
vuejs | core | 804,992,227 | 3,469 | posva | Native events always have strings. This is normal. You need to use `v-model` to allow `null` (and any other non string value):
```vue
<template>
<select v-model="localValue">
<option :value="null">Not set</option>
<option :value="10">10</option>
<option :value="20">20</option>
</select>
</temp... | 2021-03-23T15:21:11 | 2021-03-23T15:21:11 | {} | MEMBER |
vuejs | core | 801,663,133 | 3,438 | 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-18T06:20:36 | 2021-03-18T06:20:36 | {} | NONE |
vuejs | core | 802,863,497 | 3,445 | zhangenming | @edison1105
Does your PR allow for the opposite
```js
ref: x
function f(){
let $x
console.log($x) // It compiles to x, which should be $x
}
``` | 2021-03-19T14:13:40 | 2021-03-19T14:14:49 | {} | CONTRIBUTOR |
vuejs | core | 803,184,442 | 3,451 | posva | Do you have the repository? If you can, make sure it's boiled down without the router | 2021-03-19T23:12:27 | 2021-03-19T23:12:27 | {} | MEMBER |
vuejs | core | 791,924,476 | 3,377 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.93 KB (+0.11% 🔺) |
| runtime-dom.global.prod.js | 27.2 KB (+0.13% 🔺) |
| size-check.global.prod.js | 16.51 KB (+0.26% 🔺) | | 2021-03-06T11:58:48 | 2021-03-20T15:10:58 | {} | NONE |
vuejs | core | 804,526,140 | 3,459 | kerm1it | It isn't problem of jsx-next.
As you said，when using `children` and `innerHTML` at the same time in SFC，it will appear error:
My problem is vue should allow to use `children` and `innerHTML` at the ... | 2021-03-23T02:01:22 | 2021-03-23T02:01:22 | {} | NONE |
vuejs | core | 805,051,824 | 3,470 | 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 do not open issues with fake reproduction... | 2021-03-23T16:36:44 | 2021-03-23T16:36:44 | {} | MEMBER |
vuejs | core | 805,080,534 | 2,943 | ghost | @sodatea, you're totally right! `vue-jest@5` is asking for `ts-jest@24` (as per 5.0.0-alpha.7) which in turn requires `jest@24`, so i had to update with:
```
npm i -D jest@26 --legacy-peer-deps
```
and the sample test runs without issues (i know this might lead to errors at some point so i'll be looking forward t... | 2021-03-23T17:15:52 | 2021-03-23T17:17:02 | {} | NONE |
vuejs | core | 800,895,149 | 3,308 | HcySunYang | @knightly-bot build this | 2021-03-17T08:28:39 | 2021-03-17T08:28:39 | {} | MEMBER |
vuejs | core | 800,907,307 | 3,308 | 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-03-17T08:47:41 | 2021-03-17T08:47:41 | {} | NONE |
vuejs | core | 801,851,546 | 3,445 | zhangenming | > reproduction missing, also don't use `let`
so, how reproduction vue setup with jsfiddle | 2021-03-18T11:40:39 | 2021-03-18T11:40:39 | {} | CONTRIBUTOR |
vuejs | core | 801,997,697 | 3,379 | carlosmaniero | Hello @reinink!
In order to make it working at the server webpack config I needed to externalize dependencies:
https://github.com/carlosmaniero/vue-create-component-instance-error/blob/master/webpack.server.js#L14 | 2021-03-18T14:58:49 | 2021-03-18T15:05:53 | {} | NONE |
vuejs | core | 802,662,750 | 3,446 | deathlynocturnal | @HcySunYang Thank you, really appreciate it, I have been stuck for a week now trying to figure out why it wasn't working. | 2021-03-19T08:52:48 | 2021-03-19T08:52:48 | {} | NONE |
vuejs | core | 804,100,945 | 3,451 | rhengles | @posva The sense is that I treat every single component as async in my app. I don't use the public instance returned from `.mount()` and I think most people don't either.
Don't worry about performance because when the app is prerendered, every component in the page is cached and the load is equivalent to `Promise.re... | 2021-03-22T14:21:06 | 2021-03-22T14:21:06 | {} | NONE |
vuejs | core | 770,789,043 | 3,122 | 07akioni | Update: the comment is outdated. HcySunYang's ExtractPropsType has parameter on whether to make default props optional.
For props will be passed to `h`, you can turn it on.
For props from setup, you can keep the default parameter.
---
> You really misunderstood the purpose of `ExtractPropTypes`, but I think i... | 2021-02-01T11:31:52 | 2021-02-03T13:00:31 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 772,609,432 | 2,889 | HcySunYang | After this https://github.com/vuejs/vue-next/pull/3070, I think it's ok to define merge logic in `applyOptions` | 2021-02-03T15:49:01 | 2021-02-03T15:49:01 | {} | MEMBER |
vuejs | core | 773,024,514 | 3,131 | HcySunYang | @eli-crow Great thanks, then I close this one. | 2021-02-04T04:44:40 | 2021-02-04T04:44:40 | {} | MEMBER |
vuejs | core | 773,396,165 | 1,414 | fengdu555 | 需要安装vue-loader@next和vue-template-compiler能行 | 2021-02-04T15:32:12 | 2021-02-04T15:32:12 | {} | NONE |
vuejs | core | 773,421,349 | 2,701 | chaochis | > ### What problem does this feature solve?
> Seems like the instruction on how to type `ComponentCustomProperties` and `ComponentCustomOptions` aren't covered by the TS integration page of Vue3 docs.
>
> I could find some examples into the TSDocs of the related interfaces.
>
> https://github.com/vuejs/vue-next/... | 2021-02-04T16:07:43 | 2021-02-04T16:07:43 | {} | NONE |
vuejs | core | 774,491,016 | 3,173 | posva | I think this was for performance reasons. There are no practical reasons to not remove `class` and it was highlighted in other issues in Vue 2 and dismissed already.
Definitely not a bug but worth checking if the perf implication still exists | 2021-02-06T15:07:04 | 2021-02-06T15:07:04 | {} | MEMBER |
vuejs | core | 774,564,716 | 3,180 | posva | Here is the actual TS error:
Do `const data = ref<Item>(item)`
| 2021-02-07T00:16:08 | 2021-02-07T00:16:08 | {} | MEMBER |
vuejs | core | 774,628,320 | 2,975 | yangmingshan | @posva Can we move this PR forward? | 2021-02-07T07:40:38 | 2021-02-07T07:40:38 | {} | CONTRIBUTOR |
vuejs | core | 772,736,743 | 2,732 | LinusBorg | @evan this change would allow a normal, `pre` mode `watch()` on a template ref to work properly. Do you see any potential issues with this? | 2021-02-03T18:50:16 | 2021-02-03T18:50:16 | {} | MEMBER |
vuejs | core | 773,275,057 | 2,710 | LinusBorg | Vue CLI is compatible with PostCSS, verified by @sodatea, so we should be good to merge here. | 2021-02-04T12:38:24 | 2021-02-04T12:38:24 | {
"+1": 11,
"heart": 1
} | MEMBER |
vuejs | core | 773,552,071 | 2,907 | wagoon | Hi
in which version it will be this fix distributed? | 2021-02-04T19:31:26 | 2021-02-04T19:31:26 | {} | NONE |
vuejs | core | 772,127,765 | 2,892 | edison1105 | > @edison1105 Your fix does not solve the real cause. And there are problems according to your changes, let's say if the `Transition` has an `out-in` mode, then the `subtree` may be `undefined`. I made another PR, see #3150
Nice to know this and I will close my PR. | 2021-02-03T01:03:44 | 2021-02-03T01:03:44 | {} | MEMBER |
vuejs | core | 772,450,377 | 3,132 | JonasKruckenberg | > A new test that checks the generated srcset would be better to avoid a regression
I get that, how am I supposed to test the generated srcset though? Since all I get is the intermediate AST, I can either test the ASTs properties or to a string comparison with the generated string.
Which is basically what a snapsho... | 2021-02-03T11:49:05 | 2021-02-03T11:49:05 | {} | CONTRIBUTOR |
vuejs | core | 773,382,135 | 2,970 | basmilius | Also having this problem in components that have multiple slots. If it helps, one of the slots is inside a teleport. I wonder how to mark a template with $dynamic-slots and which template... | 2021-02-04T15:13:00 | 2021-02-04T15:13:00 | {} | NONE |
vuejs | core | 773,771,656 | 3,165 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.56 KB (0%) |
| runtime-dom.global.prod.js | 26.95 KB (0%) |
| size-check.global.prod.js | 16.31 KB (0%) | | 2021-02-05T04:02:31 | 2021-02-05T04:02:31 | {} | NONE |
vuejs | core | 773,816,644 | 2,834 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.56 KB (-0.01% 🔽) |
| runtime-dom.global.prod.js | 26.95 KB (0%) |
| size-check.global.prod.js | 16.31 KB (-0.01% 🔽) | | 2021-02-05T06:12:42 | 2021-02-05T06:45:33 | {} | NONE |
vuejs | core | 774,384,273 | 3,173 | HcySunYang | I don’t think this is a bug, but it’s reasonable to optimize that behavior. | 2021-02-06T02:42:45 | 2021-02-06T02:42:45 | {} | MEMBER |
vuejs | core | 774,674,876 | 3,182 | posva | Since you are passing a slot:
```vue
<advance-search>
<slot v-if="$slots['crud-search']" name="crud-search"></slot>
</advance-search>
```
`$slots.default` has to exist. Its evaluation `$slots.default()` is what will tell you if there is anything to render or not. In yuor scenario, because there is a `v-... | 2021-02-07T13:30:48 | 2021-02-07T13:30:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 772,304,032 | 3,154 | 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-02-03T07:40:05 | 2021-02-03T07:40:05 | {} | NONE |
vuejs | core | 772,305,194 | 3,155 | 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-02-03T07:42:29 | 2021-02-03T07:42:29 | {} | NONE |
vuejs | core | 772,389,456 | 3,151 | davy-tw | > There is already a warning in version `3.0.5`, see https://codesandbox.io/s/adoring-khayyam-5qrr4?file=/src/index.ts
wow thank you :) | 2021-02-03T10:05:48 | 2021-02-03T10:05:48 | {} | NONE |
vuejs | core | 773,818,780 | 3,160 | dependabot-preview[bot] | Superseded by #3169. | 2021-02-05T06:17:49 | 2021-02-05T06:17:49 | {} | CONTRIBUTOR |
vuejs | core | 774,224,988 | 2,929 | LinusBorg | @yyx990803 We might need your input here as well. | 2021-02-05T18:58:26 | 2021-02-05T19:50:36 | {} | MEMBER |
vuejs | core | 774,522,726 | 3,178 | sqal | It is already implemented (not documented though). Use it like this @vnode**HookName**="fn"
```vue
<child-component @vnodeMounted="doWhatever" />
```
in js
```js
h(ChildComponent, {
onVnodeMounted() {
// ...
}
})
``` | 2021-02-06T18:42:36 | 2021-02-06T18:47:35 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 774,648,371 | 2,768 | HcySunYang | Great thanks for @edison1105 's PR, but that still has shortcomings. I have written enough for the details, check out: https://github.com/vuejs/vue-next/pull/3184 | 2021-02-07T10:18:53 | 2021-02-07T10:18:53 | {} | MEMBER |
vuejs | core | 772,275,517 | 3,152 | HcySunYang | You never need that feature, you can just do:
```js
const obj = reactive({ a: 20 });
```
then, you can use `toRef()` or `toRefs()` to get a ref version of `a`:
```js
const refA = toRef(obj, 'a')
refA.value // 20
// or
const { a: refA } = toRefs(obj)
refA.value // 20
``` | 2021-02-03T06:43:19 | 2021-02-03T06:43:19 | {} | MEMBER |
vuejs | core | 772,296,470 | 1,010 | HcySunYang | We can close this one, due to https://github.com/vuejs/vue-next/issues/2474 | 2021-02-03T07:25:08 | 2021-02-03T07:25:08 | {} | MEMBER |
vuejs | core | 772,327,241 | 1,135 | HcySunYang | The latter made a rewrite of Ref, using `ref(2)` to replace the computed ref `a`. Details can be found here https://github.com/vuejs/vue-next/blob/master/packages/reactivity/__tests__/reactive.spec.ts#L200-L213. But I think we should ban this behavior, the first reason is that it will cause TS type mismatch:
, the conclusion is that these two cannot coexist because they basically do the same thing. The #2902 also provides an implementation of `onServerPrefetch`, and the implementation mechanism is the same as other hooks. That mechanism provides the ability to pause tracking... | 2021-02-04T04:05:00 | 2021-02-04T04:05:00 | {
"eyes": 1
} | MEMBER |
vuejs | core | 773,087,838 | 3,154 | dependabot-preview[bot] | Superseded by #3159. | 2021-02-04T07:13:12 | 2021-02-04T07:13:12 | {} | CONTRIBUTOR |
vuejs | core | 773,090,132 | 3,160 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [size](https://github.com/vuejs/vue-next/runs/1828767584)
Dependabot will still automatically merge this pull request if you amend it and your tests pass. | 2021-02-04T07:17:28 | 2021-02-04T07:17:28 | {} | CONTRIBUTOR |
vuejs | core | 773,611,170 | 3,161 | LinusBorg | About `computed`:
That's expected behavior. Computed properties are evaluated lazily, which means: the function is run only once the computed property is actually being read.
As a consequence, if one computed property A depends on another computed property B, and B updates, then A will always update as well - wet... | 2021-02-04T21:20:33 | 2021-02-04T21:20:33 | {} | MEMBER |
vuejs | core | 773,676,932 | 3,164 | HcySunYang | Duplicate of https://github.com/vuejs/vue-next/issues/2668 | 2021-02-04T23:43:17 | 2021-02-04T23:43:17 | {} | MEMBER |
vuejs | core | 773,731,960 | 3,163 | HcySunYang | We don’t need to care about this, and sometimes it’s intentionally | 2021-02-05T02:10:21 | 2021-02-05T02:10:21 | {} | MEMBER |
vuejs | core | 773,817,995 | 3,159 | dependabot-preview[bot] | Superseded by #3167. | 2021-02-05T06:15:54 | 2021-02-05T06:15:54 | {} | CONTRIBUTOR |
vuejs | core | 774,675,165 | 3,183 | HcySunYang | Oh, the code it generates looks like this:
```js
import {Ref} from 'vue'
export default {
expose: [],
setup(__props) {
return { Ref }
}
}
```
But I can't find any way other than list all types through enumeration, or we can consider imports beginning with capital letters as types, but exclude ... | 2021-02-07T13:32:49 | 2021-02-07T13:32:49 | {
"+1": 1
} | MEMBER |
vuejs | core | 772,436,058 | 3,070 | Akryum | The GH action can't download the `actions/checkout` action for some reason :man_shrugging: | 2021-02-03T11:22:58 | 2021-02-03T11:22:58 | {} | MEMBER |
vuejs | core | 773,012,916 | 3,070 | HcySunYang | @LinusBorg @posva , Can you help me take a look at these two PRs(#2902 and https://github.com/vuejs/vue-next/pull/3070)? thanks. | 2021-02-04T04:09:14 | 2021-02-04T04:09:14 | {} | MEMBER |
vuejs | core | 773,601,577 | 3,162 | 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).
---
take a look at the existing tests using compile ... | 2021-02-04T21:02:22 | 2021-02-04T21:02:22 | {} | MEMBER |
vuejs | core | 773,772,077 | 3,039 | 07akioni | It seems the CI fail is irrelevant | 2021-02-05T04:03:52 | 2021-02-05T04:03:52 | {} | CONTRIBUTOR |
vuejs | core | 773,677,286 | 2,834 | edison1105 | > Hey @edison1105 do you have an idea for a test case?
>
done！ | 2021-02-04T23:44:13 | 2021-02-05T06:51:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 773,888,971 | 3,170 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 40.55 KB (-0.02% 🔽) |
| runtime-dom.global.prod.js | 26.94 KB (-0.03% 🔽) |
| size-check.global.prod.js | 16.31 KB (0%) | | 2021-02-05T08:48:38 | 2021-02-05T08:48:38 | {} | NONE |
vuejs | core | 774,385,644 | 3,173 | HcySunYang | Check out the new attributes coercion behavior https://github.com/vuejs/rfcs/blob/master/active-rfcs/0024-attribute-coercion-behavior.md | 2021-02-06T02:53:22 | 2021-02-06T02:53:22 | {} | MEMBER |
vuejs | core | 772,303,683 | 2,876 | dependabot-preview[bot] | Superseded by #3155. | 2021-02-03T07:39:21 | 2021-02-03T07:39:21 | {} | CONTRIBUTOR |
vuejs | core | 773,089,246 | 3,159 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 40.56 KB (0%) |
| runtime-dom.global.prod.js | 26.95 KB (0%) |
| size-check.global.prod.js | 16.31 KB (0%) | | 2021-02-04T07:15:43 | 2021-02-04T07:15:43 | {} | NONE |
vuejs | core | 772,695,060 | 3,070 | Akryum | > @Akryum How about this https://github.com/vuejs/vue-next/pull/2902, it supports hooks from mixin/extend.
I think both can co exist | 2021-02-03T17:45:08 | 2021-02-03T17:45:08 | {} | MEMBER |
vuejs | core | 773,238,893 | 3,134 | HcySunYang | Hi, I close this one because it has been fixed, sorry I forgot it was fixed by me. see https://github.com/vuejs/vue-next/pull/2750 | 2021-02-04T11:29:57 | 2021-02-04T11:29:57 | {} | MEMBER |
vuejs | core | 773,473,416 | 2,834 | LinusBorg | Hey @edison1105 do you have an idea for a test case?
| 2021-02-04T17:21:06 | 2021-02-04T17:21:06 | {} | MEMBER |
vuejs | core | 774,537,593 | 3,178 | yuantongkang |
发自我的iPhone
> 在 2021年2月7日，上午3:40，plc-dev <notifications@github.com> 写道：
>
>
> Ah gotcha, thanks for pointing it out!
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub, or unsubscribe.
| 2021-02-06T20:17:42 | 2021-02-06T20:17:42 | {} | NONE |
vuejs | core | 774,654,559 | 3,183 | LinusBorg | Don't think so, that issue revolved around runtime exports (`unref`, `openBlock`).
There were also comments about the problem with Type exports in the RFC comments that found the same solution/workaround:
https://github.com/vuejs/rfcs/pull/227#issuecomment-766427503 | 2021-02-07T11:02:57 | 2021-02-07T11:03:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 774,678,195 | 3,183 | HcySunYang | > Should we consider this an enhancement rather than a bug as import type works for now, and the RFC is still in flux?
Agree | 2021-02-07T13:54:27 | 2021-02-07T13:54:27 | {} | MEMBER |
vuejs | core | 772,279,573 | 3,151 | HcySunYang | There is already a warning in version `3.0.5`, see https://codesandbox.io/s/adoring-khayyam-5qrr4?file=/src/index.ts | 2021-02-03T06:52:01 | 2021-02-03T06:52:01 | {} | MEMBER |
vuejs | core | 772,741,442 | 2,765 | LinusBorg | @edison1105 Thoughts on the last comment? Does that cover the case you mentioned? | 2021-02-03T18:57:49 | 2021-02-03T18:57:49 | {} | MEMBER |
vuejs | core | 773,602,679 | 2,907 | LinusBorg | Upcoming 3.0.6 | 2021-02-04T21:04:38 | 2021-02-04T21:04:38 | {} | MEMBER |
vuejs | core | 773,683,528 | 3,106 | HcySunYang | I think it's an edge case because it only occurs when rendering errors | 2021-02-05T00:01:54 | 2021-02-05T00:01:54 | {} | MEMBER |
vuejs | core | 774,675,879 | 3,183 | LinusBorg | Yeah, don't think that would be a reliable heuristic. I don't think the compiler can reliably determine wether or not an import is a Type or a runtime object, so in theory we would have to clean up the imports with Ts somehow before generating the code.
No idea if something like this is even feasable, not really fam... | 2021-02-07T13:38:11 | 2021-02-07T13:38:11 | {
"+1": 1
} | MEMBER |
vuejs | core | 774,679,320 | 1,724 | sheldonstewart | so what is the solution? | 2021-02-07T14:02:14 | 2021-02-07T14:02:14 | {} | NONE |
vuejs | core | 772,561,729 | 2,847 | shadowings-zy | > can you add a test case?
@posva hi, I have added test case for this commit | 2021-02-03T14:44:23 | 2021-02-03T14:44:23 | {} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.