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 | 866,021,894 | 3,987 | DV8FromTheWorld | I'm not sure what more information I can provide given that the repo _does_ break for me.
What direction would you like to pursue for this? | 2021-06-22T14:14:51 | 2021-06-22T14:14:51 | {} | CONTRIBUTOR |
vuejs | core | 866,306,906 | 3,993 | jacekkarczmarczyk | > if you function does not have dynamic arguments, you can wrap the function in a computed
Yeah, but if it has and they come from `v-for` (like in the example in my comment in the mentioned commit) i can't use computed.
I wonder why do we even need this check, vue doesn't check if you have proper expression in `v-b... | 2021-06-22T20:22:16 | 2021-06-22T20:22:16 | {} | CONTRIBUTOR |
vuejs | core | 862,134,543 | 3,950 | edison1105 | I've re-thought the question. Maybe my PR is not correct.
There are two effects in the queue
1. `update` of Transition
2. `update` of Foo.vue
After the queue is flushed, the animation takes effect.
So skipping the update of Foo.vue is not correct.
Maybe should delay updating Foo.vue after Transition has done.... | 2021-06-16T07:47:30 | 2021-06-23T01:11:00 | {} | MEMBER |
vuejs | core | 866,484,762 | 3,961 | hubvue | Due to code conflict, resubmit PR | 2021-06-23T03:02:51 | 2021-06-23T03:02:51 | {} | NONE |
vuejs | core | 864,033,242 | 3,977 | HorseLuke | I will try to provide another minimal reproduction asap. | 2021-06-18T13:18:29 | 2021-06-18T13:18:29 | {} | NONE |
vuejs | core | 864,102,736 | 3,976 | ShGKme | In addition this works in Vue 2 and isn't mentioned in the Migration Guide. | 2021-06-18T15:03:51 | 2021-06-18T15:03:51 | {
"+1": 1
} | NONE |
vuejs | core | 864,131,436 | 3,978 | posva | This is because you are calling a function that returns a new async component every time. Async components must be registered in `components` or passed to a `shallowRef()`:
```js
const AsyncComp = defineAsyncComponent(() =>
import('./components/AsyncComponent.vue')
)
const currentComponent = shallowRef(Async... | 2021-06-18T15:51:40 | 2021-06-18T15:51:40 | {
"+1": 2
} | MEMBER |
vuejs | core | 864,557,760 | 3,980 | Amour1688 | see https://github.com/vuejs/vue-next/pull/3926 | 2021-06-20T13:45:40 | 2021-06-20T13:45:40 | {
"heart": 1
} | MEMBER |
vuejs | core | 864,868,424 | 3,979 | wtcodeai | @posva so, the problem was solved, but it was not in the component `key:`, the nested `<div>` hierarchy caused this, thanks for the solution | 2021-06-21T09:08:46 | 2021-06-21T09:08:46 | {} | NONE |
vuejs | core | 864,945,743 | 3,979 | posva | There is already an open PR for that warning #2337.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-06-21T11:08:04 | 2021-06-21T11:08:04 | {} | MEMBER |
vuejs | core | 865,850,141 | 3,990 | johnsoncodehk | `dobule` does not unwrap by `defineComponent`.
```ts
const Comp = defineComponent({
setup() {
const count = ref(0)
const double = Math.random() < 0.5 ? computed(() => count.value * 2) : undefined;
return { count, double }
}
})
const comp = new Comp()
type TDobule = typeof comp.double // type TDobule... | 2021-06-22T10:07:04 | 2021-06-22T10:07:04 | {} | MEMBER |
vuejs | core | 866,184,290 | 3,987 | DV8FromTheWorld | Yeah, so the problem here is:
https://github.com/vuejs/vue-next/blob/master/packages/shared/src/codeframe.ts#L8
Basically, everything else in the parser deals with `\n` vs `\r\n` by using the `.length` property, thus getting `1` or `2` respectively.
This split treats `\n` and `\r\n` identically, so every time anot... | 2021-06-22T17:26:21 | 2021-06-22T17:26:21 | {} | CONTRIBUTOR |
vuejs | core | 866,204,098 | 3,974 | yyx990803 | Oh I only noticed this PR after I fixed it in https://github.com/vuejs/vue-next/commit/9b607fe409d70e991ba458e7c994e008a4b621e8 ... sorry about that! | 2021-06-22T17:56:16 | 2021-06-22T17:56:16 | {} | MEMBER |
vuejs | core | 862,245,646 | 3,960 | LinusBorg | I'm having a problem with the sandbox where it won't load anymore after I made a change, so I an't say for sure, but:
It seems the issue is that the ref name you use is also the name of the state variable: `numberValidateForm`.
If you have a look at `template refs` in the composition API docs, you will find this... | 2021-06-16T10:33:20 | 2021-06-16T10:40:12 | {} | MEMBER |
vuejs | core | 862,796,225 | 2,819 | m4heshd | @andre-cgn I've ran into this multiple times. It's just an issue with HMR. Just rebuild and run your application. It should be fine. | 2021-06-16T23:24:40 | 2021-06-16T23:24:40 | {} | NONE |
vuejs | core | 863,989,673 | 3,977 | posva | Please provide a boiled down reproduction in a new issue not a copy of the part of your project that shows the error. This is too much to check. The title and description of your issue suggest the reproduction could be much much smaller and easier to follow.
---
Remember to use the [forum](http://forum.vuejs.org/... | 2021-06-18T12:06:06 | 2021-06-18T12:06:06 | {} | MEMBER |
vuejs | core | 863,289,166 | 3,968 | edison1105 | @posva
the test case has done. feel free to review.
time to go to bed. | 2021-06-17T14:29:39 | 2021-06-17T14:29:39 | {} | MEMBER |
vuejs | core | 863,352,310 | 3,973 | posva | It wouldn't work with transitions (https://github.com/vuejs/vue-next/blob/master/packages/runtime-dom/src/directives/vShow.ts)
A new directive could do but it should go through an RFC in the rfcs repository. Can you follow that if it still makes sense? | 2021-06-17T15:44:34 | 2021-06-17T15:44:34 | {} | MEMBER |
vuejs | core | 863,912,390 | 3,976 | posva | I would say the workaround is the preferred way to write it so you pass one single slot. | 2021-06-18T09:50:27 | 2021-06-18T09:50:27 | {} | MEMBER |
vuejs | core | 864,389,033 | 3,979 | EatherToo | 
try like this | 2021-06-19T10:43:29 | 2021-06-19T10:43:29 | {} | NONE |
vuejs | core | 865,259,296 | 3,090 | yyx990803 | ### Vue 2
<img width="792" alt="Screen Shot 2021-06-21 at 2 36 59 PM" src="https://user-images.githubusercontent.com/499550/122811488-8c925c80-d29e-11eb-9ec2-18558c0c30c0.png">
### Vue 3 before fix
<img width="864" alt="Screen Shot 2021-06-21 at 2 36 03 PM" src="https://user-images.githubusercontent.com/499550... | 2021-06-21T18:40:31 | 2021-06-21T18:40:31 | {
"heart": 8,
"rocket": 20
} | MEMBER |
vuejs | core | 865,759,379 | 3,988 | posva | Can't reproduce and the codesandbox is not editable. Let me know if you change it to reproduce the code and say **what** template code should be commented. | 2021-06-22T08:52:14 | 2021-06-22T08:52:14 | {
"-1": 6
} | MEMBER |
vuejs | core | 862,343,417 | 3,794 | posva | Closing in favor of https://github.com/vuejs/vue-next/issues/3963 | 2021-06-16T12:36:55 | 2021-06-16T12:36:55 | {} | MEMBER |
vuejs | core | 862,954,417 | 2,337 | cexbrayat | @posva nice job! I'll close this one since your PR should indeed fix it. Looking forward to get rid of this annoying warning with the next release 🙂 | 2021-06-17T06:06:30 | 2021-06-17T06:06:30 | {} | MEMBER |
vuejs | core | 863,938,609 | 1,600 | martinbean | Has any one gotten this working with Laravel Mix yet? No matter how I try and pass these options, whitespace still gets removed from inline elements when mounting view to a containing element, like `<div id="app">`. | 2021-06-18T10:31:10 | 2021-06-18T10:31:10 | {} | NONE |
vuejs | core | 863,966,029 | 1,539 | thenickname | > What's the point of using render functions inside single file components? Just for `<style>`? Also, if it's a Vite issue, please open separate issue in Vite's repo.
one use case is to use JSX/TSX instead of templates (e. g. for better editor support), but still have everything in a SFC and not spread across a .jsx... | 2021-06-18T11:21:04 | 2021-06-18T11:21:35 | {} | NONE |
vuejs | core | 864,693,308 | 1,600 | hawkeye64 | I found an alternative to this by deep-diving Vue compiler options.
simply this:
```js
const oldPreTagFunc = conf.build.vueLoaderOptions.compilerOptions.isPreTag
vueLoaderOptions.compilerOptions.isPreTag = (tag) => tag === 'pre'
|| tag === 'q-markdown'
|| (typeof oldPreTagFunc === 'function' ? oldPreTagFu... | 2021-06-21T03:15:05 | 2021-06-21T03:15:05 | {} | NONE |
vuejs | core | 864,818,205 | 3,979 | posva | You should add the `key` to `<component>` and place it right after suspense:
```vue
<router-view v-slot="{ Component }">
<div style="height: 100%">
<Suspense>
<component :is="Component" :key="route.path" />
</Suspense>
</div>
</router-view>
``` | 2021-06-21T08:02:12 | 2021-06-21T08:02:12 | {} | MEMBER |
vuejs | core | 866,066,355 | 3,987 | posva | make sure you update the dependencies then. I used yarn to install them | 2021-06-22T15:07:39 | 2021-06-22T15:07:39 | {} | MEMBER |
vuejs | core | 866,299,753 | 3,993 | lidlanca | some improvements were made in (bc100c5c48b98b6e2eabfa1d50e0d3099ea2a90d )
to cover more valid expressions, but it does not cover all valid member expressions.
like the one you encountered.
```
<input v-model="what().ever">
```
if your function does not have dynamic arguments, you can wrap the function in ... | 2021-06-22T20:10:53 | 2021-06-22T20:18:05 | {} | CONTRIBUTOR |
vuejs | core | 866,397,755 | 3,334 | yyx990803 | Note: I noticed that we still have mostly duplicated logic in `createVNode` and `createComponentVNode`, while at the same time we end up nesting several function calls in order to reuse other logic.
Since the gain in `createComponentVNode` will be rather minimal, `createElementVNode` seems to be the bigger win here.... | 2021-06-22T23:15:06 | 2021-06-22T23:15:06 | {
"+1": 2
} | MEMBER |
vuejs | core | 867,127,610 | 3,995 | yyx990803 | I noticed this PR no longer use a class/prototype implementation for effects - does this mean this PR doesn't affect memory consumption like #2345 did? | 2021-06-23T20:14:46 | 2021-06-23T20:14:46 | {} | MEMBER |
vuejs | core | 862,230,571 | 3,758 | oliverzy | https://github.com/vuejs/vue-next/commit/0e59770b9282992f6a5af4d8fef33dafb948fc8b | 2021-06-16T10:08:29 | 2021-06-16T10:08:29 | {} | NONE |
vuejs | core | 863,300,868 | 2,345 | basvanmeurs | @yyx990803 would you prefer a new PR which only includes the performance improvements that don't affect the API? | 2021-06-17T14:43:07 | 2021-06-17T14:43:07 | {} | CONTRIBUTOR |
vuejs | core | 864,340,949 | 3,930 | qmhc | @yyx990803 谢谢回复。
我的失误。
我发现这个问题原始项目是添加了 `external: ['vue']` 的，测试库忘记添加，现在已加上，并已移除本地的 link。
> 运行 yarn run build 打包 Test 组件后，用 vite 的模版创建一个新的项目，link 引用原始项目打包的组件，随后运行 yarn run dev 后得到标题中的警告，在这个项目打包后，页面不能正常打开。
可能是我表达不清晰，在 [测试库](https://github.com/qmhc/vue-test) 打包后，使用 `yarn create @vitejs/app test-project --templ... | 2021-06-19T02:07:20 | 2021-06-19T02:10:49 | {} | NONE |
vuejs | core | 864,900,397 | 3,966 | yuripave | > [e2ca67b#diff-07826ed1d9f7699d925ee15d9212e2879af5320b155c0c878fc2dcba71b3e564L110-L113](https://github.com/vuejs/vue-next/commit/e2ca67b59a4de57a9bce8d3394263ba493a35a39#diff-07826ed1d9f7699d925ee15d9212e2879af5320b155c0c878fc2dcba71b3e564L110-L113)
>
> This seems to be intentional.
I also agree this breakin... | 2021-06-21T09:55:09 | 2021-06-21T09:55:09 | {} | NONE |
vuejs | core | 864,912,432 | 3,984 | edison1105 | you should:
```javascript
<Comp :config="config" />
setup(){
const config = {a:1}
return{
...
config
}
}
``` | 2021-06-21T10:12:59 | 2021-06-21T10:12:59 | {} | MEMBER |
vuejs | core | 866,076,298 | 3,987 | DV8FromTheWorld | Cleared my `node_modules`, installed yarn, ran `yarn install` and `yarn run serve`.
Resulted in the same behavior.
Here is the generated `yarn.lock` file if you'd like to do a diff between it and your own.
https://gist.github.com/DV8FromTheWorld/8bd1dc6dc8288b86663630b44f466324 | 2021-06-22T15:18:48 | 2021-06-22T15:18:48 | {} | CONTRIBUTOR |
vuejs | core | 925,375,623 | 4,633 | yyx990803 | There is no bug here - `autocomplete` on button is not valid, so it's not supported in the JSX typing. Despite typing, you still *can* render an `autocomplete` attribute on a button if you want, so I don't know what is expected here. | 2021-09-22T22:30:48 | 2021-09-22T22:30:48 | {} | MEMBER |
vuejs | core | 925,559,351 | 4,010 | cyfung1031 | > You may be able to work around this problem via passing the intended index of the ref to your `handleItemRef` and using it to set the ref into the array instead of relying on `.push(ref)`.
>
> The follow example highlights how this could be implemented
>
> ```
> <template>
> <ul>
> <li
> v-for=... | 2021-09-23T07:14:33 | 2021-09-23T07:14:33 | {} | NONE |
vuejs | core | 926,527,186 | 4,668 | LinusBorg | I also don't know how to reproduce this.
This issue is not actionable without a runnable reproduction. Please provide one or we will have to close the issue.
Mentioning how you upgraded ts-loder to v9, which requires webpack 5, while ts-loader works with webpack 4, I'd suspect you simply have incompatible depende... | 2021-09-24T10:41:37 | 2021-09-24T11:26:19 | {} | MEMBER |
vuejs | core | 926,684,685 | 4,668 | LinusBorg | I just run that command in your repo and got 0 errors, just:
```
Laravel Mix v6.0.31
✔ Compiled Successfully in 2871ms
┌──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────... | 2021-09-24T14:44:55 | 2021-09-24T14:44:55 | {} | MEMBER |
vuejs | core | 926,687,181 | 4,668 | LinusBorg | ah, Interesting.
* The error happens when I run `npm run dev`,
* but doesn't happen when I run `yarn dev`, even though that runs the same script.
* but when I directly run `yarn mix` (which `yarn dev` runs as well), the errors show up and the build fails.
This is super weird, but I'd guess and say it's somehow... | 2021-09-24T14:48:20 | 2021-09-24T14:53:03 | {} | MEMBER |
vuejs | core | 926,928,968 | 2,860 | yyx990803 | Ok, so this is because the `lib-vue` build minifies the dist files, which removes the `/*#__PURE__*/` annotations in the generated code. You also forgot to add `/*#__PURE__*/` before your own `defineComponent` calls (I'm not sure why you are doing it in the first place, since you don't need it if you are not using TS, ... | 2021-09-24T21:27:19 | 2021-09-24T21:41:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 927,249,210 | 4,397 | zhuchentong | I have same problem, when run `vue-tsc` will show error
```
error TS2339: Property 'getFormValue' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: Partial<{}> & Omit<Readonly<{ page?: unknown; forms?: unknown; } & {} & { page?: PageService | undefined; forms?: TableFormConfig[] | undefine... | 2021-09-26T07:22:48 | 2021-09-26T07:22:48 | {
"+1": 4
} | NONE |
vuejs | core | 927,545,025 | 4,668 | iraklisg | It seems that this issue is not related to laravel-mix. I copy from https://github.com/laravel-mix/laravel-mix/issues/3110#issuecomment-927440289
> This consistently happens regardless of package manager used to install or run the scripts. It also happens when invoking mix directly using `./node_modules/.bin/mix`.... | 2021-09-27T05:32:23 | 2021-09-27T05:32:23 | {} | NONE |
vuejs | core | 927,564,828 | 4,662 | tony19 | Also encountered this issue. Here's a couple more repros:
* [w/Vue CLI](https://stackblitz.com/edit/vue-nested-custom-elements-lose-styles-vue-cli?file=src%2FApp.ce.vue)
* [w/Vite](https://stackblitz.com/edit/vue-nested-custom-elements-lose-styles?file=src%2FApp.vue) | 2021-09-27T06:16:16 | 2021-09-27T06:16:16 | {
"+1": 3,
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 926,292,797 | 4,654 | WJCHumble | @long-hai-yang @Sun3 You can refer to this answer https://stackoverflow.com/questions/15806152/how-do-i-override-nested-npm-dependency-versions | 2021-09-24T02:18:24 | 2021-09-24T02:18:24 | {} | NONE |
vuejs | core | 926,520,620 | 4,671 | LinusBorg | In Vue 3, you need to set any non-boolean attribute to `null` or `undefined` to have it removed.
See: https://v3.vuejs.org/guide/migration/attribute-coercion.html#_2-x-syntax | 2021-09-24T10:29:11 | 2021-09-24T10:29:11 | {} | MEMBER |
vuejs | core | 926,694,249 | 4,673 | syropian | @edison1105 Oop, you're right, I'll edit the issue to just mention the export bug! | 2021-09-24T14:57:34 | 2021-09-24T15:02:36 | {} | NONE |
vuejs | core | 926,050,811 | 4,663 | amw | `titled2` is not used through `.value`. `titled1.value` is working correctly. What does not work is using `titled2` though `_unref(titled2)`. But I would _not_ say this is correct on TypeScript part. Both of these have the same inferred type:
`titled1.value` is `Titled | undefined` and `_unref(titled2)` is also `Tit... | 2021-09-23T18:23:06 | 2021-09-23T20:35:28 | {} | NONE |
vuejs | core | 926,580,493 | 4,663 | amw | Casting would be an okay-ish work-around if I could cast inside setup function body to let Vue compiler know it can use `.value` in the render function. But that is not picked up by Vue at this time.
So I am left with casting within the template's conditional branch and it doesn't make any sense - it kills type safe... | 2021-09-24T12:18:42 | 2021-09-24T12:18:42 | {
"+1": 1
} | NONE |
vuejs | core | 926,882,793 | 2,860 | mgdodge | @yyx990803 , I don't believe this is truly fixed...at least, I can't get it to work. I created another minimal repo to demonstrate - https://github.com/mgdodge/vue-compiler-treeshaking-bug.
The repo uses vite directly instead of any custom rollup configuration. In the demo, I have updated vite to the latest beta, wh... | 2021-09-24T19:52:28 | 2021-09-24T19:52:28 | {} | NONE |
vuejs | core | 926,319,839 | 4,667 | yyx990803 | 这是因为 style 被 parse 成了对象，为的是处理 auto-prefixing。直接写 `background: #18191c url('http://abc.bcd.com/efg.jpeg');` 就可以避免了。 | 2021-09-24T03:45:47 | 2021-09-24T03:45:47 | {} | MEMBER |
vuejs | core | 927,227,897 | 4,678 | Guervyl | **It's great that vue3 does not touch the original object.** I wasn't modifying the external object to expect Vue3 to react. I was assigning the external object to `this.object` after I modified the external object.
**I found the problem.** Somewhere in the code it was destroying the Vue html container.
Thanks fo... | 2021-09-26T04:17:13 | 2021-09-26T04:17:13 | {} | NONE |
vuejs | core | 927,877,745 | 4,662 | raffobaffo | I also encountered it and just worked on a fix, will create a PR soon (my first one here 😨 ) | 2021-09-27T13:30:14 | 2021-09-27T13:30:14 | {
"+1": 3
} | NONE |
vuejs | core | 928,112,333 | 1,359 | Spittal | Hey @yyx990803 is there a way to annotate a prop with a generic so that the types get carried over through scoped slots?
CompA
```
<script lang ="ts">
import { defineComponent, PropType } from 'vue';
defineComponent({
props: {
items: {
type: Array as PropType<T[]>,
required: true,
},
... | 2021-09-27T17:53:47 | 2021-09-27T17:54:12 | {} | NONE |
vuejs | core | 928,591,601 | 4,471 | Alanscut | Thanks! | 2021-09-28T01:43:35 | 2021-09-28T01:43:35 | {} | CONTRIBUTOR |
vuejs | core | 925,547,721 | 4,654 | long-hai-yang | > 应该固定在`vue-loader@16.8.1`.
我固定在`vue-loader@16.8.1`无效，还是报这警告，并且页面空白。这是我package-lock.json的截图：
以及查看node_modules文件夹下安装的vue-loader的package.json截图：
), so it's not recognized by Vue as a boolean attribute. Thus, as mentioned above, it can only be removed wit... | 2021-09-24T10:35:07 | 2021-09-24T10:35:16 | {} | MEMBER |
vuejs | core | 926,835,471 | 4,654 | Sun3 | It's working again for me...
I reinstalled vue cli via ```npm install -g u/vue/cli``` then deleted my projects ```package-lock.json``` file. Then from the project, I ran ```npm install``` and the hot reload is working again.
| 2021-09-24T18:24:09 | 2021-09-24T19:21:50 | {} | NONE |
vuejs | core | 926,920,332 | 4,666 | yyx990803 | Fixed in 3.2.18 | 2021-09-24T21:08:17 | 2021-09-24T21:08:17 | {} | MEMBER |
vuejs | core | 927,088,647 | 4,676 | LinusBorg | > Running twice of create stage doesn't make sense
That totally depends on your use case, though.
* You might want to have the effect run immediately, maybe it triggers an API call you want to have going ASAP.
* you might want to have it run again if a reactive dependency did change before mounted, which might ... | 2021-09-25T08:35:16 | 2021-09-25T08:35:16 | {} | MEMBER |
vuejs | core | 927,543,378 | 4,684 | LinusBorg | This is not a use case for a computed property. | 2021-09-27T05:27:46 | 2021-09-27T05:27:46 | {} | MEMBER |
vuejs | core | 921,622,223 | 4,619 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 46.19 KB (+0.08% 🔺) |
| runtime-dom.global.prod.js | 30.55 KB (+0.11% 🔺) |
| index.js | 18.05 KB (+0.17% 🔺) | | 2021-09-17T08:47:30 | 2021-09-27T15:22:34 | {} | NONE |
vuejs | core | 925,627,333 | 4,660 | LinusBorg | Should be solved by this already merged PR:
https://github.com/vuejs/vue-next/pull/4606
This is part of 3.2.13 | 2021-09-23T09:01:35 | 2021-09-23T09:02:16 | {} | MEMBER |
vuejs | core | 925,703,141 | 4,566 | SupertigerDev | I fixed my issue by adding INSTANCE_LISTENERS: false as suggested 😀 | 2021-09-23T10:52:15 | 2021-09-23T10:52:15 | {
"+1": 4
} | NONE |
vuejs | core | 927,963,504 | 4,686 | yyx990803 | This is expected behavior in Vue 3 since the parent component in this case did not update, which is a form of optimization.
A workaround here is using the `@vnode-updated="updateRefs"` event on a container element inside the slot instead.
| 2021-09-27T15:05:02 | 2021-09-27T15:05:02 | {} | MEMBER |
vuejs | core | 928,008,443 | 4,690 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 46.24 KB (+0.19% 🔺) |
| runtime-dom.global.prod.js | 30.59 KB (+0.27% 🔺) |
| index.js | 18.02 KB (0%) | | 2021-09-27T15:56:23 | 2021-09-27T16:01:31 | {} | NONE |
vuejs | core | 925,728,924 | 4,661 | posva | `defineReturn` would completely defeat the purpose of script setup which allows you to use everything defined inside: you should explicitly import anything used `import { foo } from './file'` | 2021-09-23T11:33:48 | 2021-09-23T11:33:55 | {} | MEMBER |
vuejs | core | 926,297,440 | 4,663 | amw | The only excuse I can find for TypeScript is that it's safer to assume `myRef.value` will not change between ternary condition and its use in ternary branch. `unref(myRef)` being a function could return random results. But it's just optics as `myRef.value` executes a getter function.
But like I said – it might be Ty... | 2021-09-24T02:34:38 | 2021-09-24T02:34:38 | {} | NONE |
vuejs | core | 926,323,746 | 4,666 | yyx990803 | Ok... this actually has a bigger implication than it seems, because without adding an `exports` field to `vue` there is no way to retain the same `vue/server-renderer` import path for both CJS and ESM. And we need to do that because Vite currently converts the ESM-based SSR code to CJS in its runtime. | 2021-09-24T04:00:17 | 2021-09-24T04:00:17 | {} | MEMBER |
vuejs | core | 926,336,014 | 4,666 | yyx990803 | For now you can pass [this option](https://github.com/vuejs/vue-next/blob/master/packages/compiler-core/src/options.ts#L282) to change the import location | 2021-09-24T04:39:05 | 2021-09-24T04:39:05 | {
"heart": 1
} | MEMBER |
vuejs | core | 926,906,821 | 4,674 | yyx990803 | `rollup-plugin-vue` is no longer maintained. Please use [Vite](https://vitejs.dev/) instead (it uses Rollup under the hood and has official Vue plugin). | 2021-09-24T20:40:16 | 2021-09-24T20:40:16 | {
"+1": 1
} | MEMBER |
vuejs | core | 927,648,192 | 4,679 | ropez | @ygj6 No, the comments are inserted by SSR to provide information about template boundaries for the hydration. If you remove them, hydration fails which is reported in the console:
```
Hydration completed but contains mismatches.
```
Update: I've reversed engineered Vue SSR, to figure out where to put these com... | 2021-09-27T08:30:04 | 2021-09-27T08:32:23 | {} | NONE |
vuejs | core | 927,799,780 | 4,689 | danranVm | The cause of this problem is due to this change: #4578 | 2021-09-27T11:54:55 | 2021-09-27T11:54:55 | {} | NONE |
vuejs | core | 927,951,056 | 4,689 | yyx990803 | /cc @Amour1688
| 2021-09-27T14:51:29 | 2021-09-27T14:51:29 | {} | MEMBER |
vuejs | core | 925,473,851 | 4,654 | Sun3 | I am new to Vue, how would you pin vue-loader to 16.5.x ? I am using npm.
Thank you. | 2021-09-23T03:06:28 | 2021-09-23T03:06:28 | {
"+1": 1
} | NONE |
vuejs | core | 925,942,082 | 4,404 | gnuletik | I implemented slot without shadow DOM on the same principle as https://github.com/vuejs/vue-web-component-wrapper/ (creating a VNode with `innerHTML`).
I'm using a local copy of `apiCustomElement.ts` for the needs of my project.
If anyone is interested, I can share it!
Let me know if you want me to add the slot ... | 2021-09-23T15:53:40 | 2021-09-23T15:53:40 | {
"+1": 5,
"heart": 2
} | NONE |
vuejs | core | 926,308,767 | 4,663 | yyx990803 | Oh, I didn't notice the `v-if` part. I see this is strictly related to the generated render function code - technically something we should fix, although it's probably not easy. You should be able work around this by casting it though. | 2021-09-24T03:10:00 | 2021-09-24T03:10:00 | {} | MEMBER |
vuejs | core | 926,309,371 | 4,654 | yyx990803 | @epaezrubio you can always remove the lockfile and re-install to force latest version. | 2021-09-24T03:11:43 | 2021-09-24T03:11:43 | {
"+1": 2
} | MEMBER |
vuejs | core | 926,521,295 | 4,671 | LinusBorg | Hm, `disabled` is a boolean attribute so `false` should work ... | 2021-09-24T10:30:33 | 2021-09-24T10:30:33 | {} | MEMBER |
vuejs | core | 926,644,387 | 4,668 | iraklisg | My appologies for omitting the reproduction link. I have created an error reproduction [repo](https://github.com/iraklisg/vue-typescript) and updated my initial post.
You may run `npm run dev` to see the errors
Please let me know if I can help you to track down this issue | 2021-09-24T13:54:33 | 2021-09-24T13:54:33 | {} | NONE |
vuejs | core | 926,770,495 | 4,658 | yyx990803 | Test failure seems unrelated, try rebasing on latest master. | 2021-09-24T16:38:50 | 2021-09-24T16:38:50 | {} | MEMBER |
vuejs | core | 927,302,227 | 4,681 | LinusBorg | Manipulation of the original object instead of the reactive proxy can't be tracked. | 2021-09-26T12:57:21 | 2021-09-26T12:57:21 | {} | MEMBER |
vuejs | core | 927,613,467 | 4,685 | dboy2018 | 在<script lang="ts">里面 编译不通过,是正确的
在<script setup lang="ts">里面,编译通过了,不应该 | 2021-09-27T07:41:53 | 2021-09-27T07:41:53 | {} | NONE |
vuejs | core | 927,850,425 | 4,683 | yyx990803 | The concern is mostly loading speed, as Monaco is significantly larger than CodeMirror (close to 3Mb vs less than 100kb).
I think for sfc playground it probably makes sense to use Monaco, but ideally we want to provide two different versions, one optimized for editing experience (standalone playground) and one optim... | 2021-09-27T13:00:37 | 2021-09-27T13:00:37 | {} | MEMBER |
vuejs | core | 927,853,354 | 4,471 | yyx990803 | This is only for the monorepo workspace. Not for published packages. | 2021-09-27T13:03:46 | 2021-09-27T13:03:46 | {} | MEMBER |
vuejs | core | 926,034,897 | 4,663 | yyx990803 | I would say TypeScript is doing the right thing here since `titled2.value` can possibly be undefined, and if it is indeed `undefined` there would be a runtime error. | 2021-09-23T18:00:45 | 2021-09-23T18:00:59 | {} | MEMBER |
vuejs | core | 926,264,530 | 4,665 | edison1105 | in v3.2.12
in v3.2.13
| 2021-09-24T00:48:37 | 2021-09-24T01:01:18 | {} | MEMBER |
vuejs | core | 926,672,497 | 4,672 | edison1105 | see https://v3.vuejs.org/guide/reactivity-computed-watchers.html#watching-reactive-objects | 2021-09-24T14:28:25 | 2021-09-24T14:28:25 | {} | MEMBER |
vuejs | core | 926,691,210 | 4,673 | edison1105 | I would say this should be
```javascript
const stringWithOpenAndClosedScriptTag = "<script><\/script>"
``` | 2021-09-24T14:53:31 | 2021-09-24T14:53:31 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.