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 | 897,422,092 | 4,312 | jzs11 | > > I have facing a similar issue with vuedraggable ^4.0.3
> > 
> > 
> >  :/
EDIT:
I see th... | 2021-08-13T13:13:20 | 2021-08-13T13:18:28 | {} | NONE |
vuejs | core | 899,008,570 | 4,340 | HcySunYang | Update the dependency package (vue/vue-cli) to the latest version will not have this issue. | 2021-08-15T07:24:30 | 2021-08-15T07:24:30 | {} | MEMBER |
vuejs | core | 899,014,864 | 4,340 | sheremet-va | I don't use vue-cli, I am using Vite. Repro link inside the issue was provided by your creating issues template. I just reproduced the error.
The problem was a non-issue, until I updated my dependencies to the latest versions. I have my versions strict. (without `^`). And only ^3.2.0 gives me this unexpected behavio... | 2021-08-15T08:21:13 | 2021-08-15T08:37:41 | {} | NONE |
vuejs | core | 899,017,423 | 3,399 | pikax | @yyx990803 one compat test is failing but I can't see any change that might be causing it (because I mainly touch types 🤔 ), any idea what might be causing it? | 2021-08-15T08:46:06 | 2021-08-15T08:46:06 | {} | MEMBER |
vuejs | core | 899,082,892 | 4,345 | sqal | You can already do this. These hooks was renamed to `onVnodeXXX`
```vue
<Comp @vnodeUpdated="doSomething" />
```
```js
h(Comp, {
onVnodeUpdated: doSomething,
onVnodeMounted: doSomething,
// etc..
})
```
| 2021-08-15T17:09:01 | 2021-08-15T17:09:01 | {
"+1": 5
} | CONTRIBUTOR |
vuejs | core | 899,479,034 | 4,283 | lidlanca | use `Object.defineProperty` to define the property on the prototype.
| 2021-08-16T12:43:09 | 2021-08-16T12:43:09 | {} | CONTRIBUTOR |
vuejs | core | 899,493,468 | 4,283 | zhangenming | > use `Object.defineProperty` to define the property on the prototype.
It does work
but why, use Object.propotype will error
is it a bug? | 2021-08-16T13:05:10 | 2021-08-16T13:05:10 | {} | CONTRIBUTOR |
vuejs | core | 899,783,277 | 4,312 | yyx990803 | @cutsin @joostdelange if your issue is not related to pug, please open a separate issue with your own reproduction since they are likely not the same problem. **It doesn't help if we can't see the code of your components!** | 2021-08-16T20:04:20 | 2021-08-16T20:05:12 | {
"+1": 1
} | MEMBER |
vuejs | core | 898,270,026 | 4,330 | posva | You need to use `createApp()`. Are you following https://v3.vuejs.org/guide/migration/migration-build.html#installation with the example commits? https://github.com/vuejs/vue-hackernews-2.0/compare/migration.
Maybe it's worth adding more info in the docs repo. If you think so, a PR would be welcome 🙂 | 2021-08-13T08:06:29 | 2021-08-13T08:06:29 | {} | MEMBER |
vuejs | core | 898,270,765 | 4,324 | posva | ~~@dsonet can you share the benchmark you have ran to see the difference?
Note that in some scenarios it would still do 2 operations in all cases.~~
Edit: forgot to say that this actually reduces to 1 operation **in all cases** because terser will minify `2 | 4` to `6` at compile time. Not that it changes much in t... | 2021-08-13T08:07:43 | 2021-08-13T12:30:47 | {} | MEMBER |
vuejs | core | 897,424,154 | 4,077 | turrsis | @edison1105 is it my failure, or with my changes all ok? | 2021-08-12T07:50:01 | 2021-08-12T07:50:01 | {} | CONTRIBUTOR |
vuejs | core | 897,617,152 | 4,321 | antony-k1208 | Sorry, I hope this helps: https://codesandbox.io/s/admiring-sky-ucmn0?file=/src/components/HelloWorld.vue
It seems to be only showing this in VS Code with Volar, at least from what I can tell. | 2021-08-12T12:57:40 | 2021-08-12T12:57:40 | {} | NONE |
vuejs | core | 898,469,729 | 4,307 | baronkoko | I have a similar problem using data values https://prnt.sc/1o0ew0a. If I use the simple const variable, everything works as expected.
Reproduction link: https://github.com/baronkoko/vue-reactive-type-error/blob/main/src/App.vue
Vue 3.2.2 | 2021-08-13T13:47:41 | 2021-08-13T13:47:41 | {} | NONE |
vuejs | core | 899,025,935 | 4,340 | HcySunYang | Just add a hint here, we can't completely strip the Template strings(Template literals), https://github.com/vuejs/vue-next/blob/master/packages/compiler-sfc/src/compileScript.ts#L2249 | 2021-08-15T10:00:53 | 2021-08-15T10:00:53 | {} | MEMBER |
vuejs | core | 899,715,296 | 4,283 | lidlanca | you are adding a property to all objects, it is possible that you broke code that did not expect to have that property there.
| 2021-08-16T18:12:04 | 2021-08-16T18:14:09 | {} | CONTRIBUTOR |
vuejs | core | 897,505,014 | 4,077 | edison1105 | > @edison1105 can you approve to run tests?
Sorry, I have no permission to re-run CI.the failure seems not to relate to this PR. If you rebase your code from the master branch and push again. the CI will re-run.
| 2021-08-12T09:56:26 | 2021-08-12T09:56:26 | {} | MEMBER |
vuejs | core | 897,630,090 | 4,321 | posva | @johnsoncodehk can you confirm the problem is within vue? | 2021-08-12T13:14:53 | 2021-08-12T13:14:53 | {} | MEMBER |
vuejs | core | 897,682,860 | 4,325 | edison1105 | I'm not sure if this usage scenario is reasonable. | 2021-08-12T14:23:09 | 2021-08-12T14:23:09 | {} | MEMBER |
vuejs | core | 898,011,183 | 4,324 | dsonet | It doesn't really reduce any operations. In fact it may increase operations since this gonna make these statements at least do 2 operations instead of just 1. | 2021-08-12T22:32:39 | 2021-08-12T22:32:39 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 898,200,131 | 4,322 | phucnguyen035 | Hey, I would like to report similar type issue, but I have the opposite problem. It works with boolean value for, but fails for string value.
Example taken from doc page, refactored to use `typescript` and `script setup` https://v3.vuejs.org/guide/forms.html#radio
![image](https://user-images.githubusercontent.co... | 2021-08-13T05:25:12 | 2021-08-13T05:25:12 | {
"+1": 2
} | NONE |
vuejs | core | 898,262,633 | 4,312 | njzzzz | same issue +1 | 2021-08-13T07:52:55 | 2021-08-13T07:52:55 | {} | NONE |
vuejs | core | 898,108,401 | 4,327 | njzzzz | +1 | 2021-08-13T02:14:18 | 2021-08-13T02:14:18 | {} | NONE |
vuejs | core | 898,153,193 | 4,329 | njzzzz | 
| 2021-08-13T03:08:42 | 2021-08-13T03:08:42 | {} | NONE |
vuejs | core | 898,239,389 | 4,304 | Hansuku | I reappeared, and i downgraded `@vue/compiler-sfc` to 3.0.4, it work. | 2021-08-13T07:06:54 | 2021-08-13T07:06:54 | {} | NONE |
vuejs | core | 898,404,189 | 4,332 | LinusBorg | The API is documented here, which is 99% of what one might need: https://v3.vuejs.org/api/reactivity-api.html
You can open an issue in the [docs repo](https://github.com/vuejs/docs) asking for a little usage intro on standalone usage. That might fit well on the Page I linked above. | 2021-08-13T11:52:54 | 2021-08-13T11:53:18 | {} | MEMBER |
vuejs | core | 898,432,506 | 4,318 | basvanmeurs | I agree. Let's see if I can create some performance tests. I have another solution in mind that could be nearly as fast, for both shallow and deep reactives and even for arrays, objects and collections, but with less code. If it works.. I'll get back on this next week | 2021-08-13T12:44:18 | 2021-08-13T12:44:18 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 898,486,927 | 4,330 | LinusBorg | ...which is why I directly deleted my comment again, seems you were faster though.
For one, the type is `CompatVue`, but the real problem was that i couldn't figure out how to augment the module without killing all the other types `vue` exposes. | 2021-08-13T14:12:49 | 2021-08-13T14:13:50 | {} | MEMBER |
vuejs | core | 898,537,952 | 4,333 | posva | I have no idea what's exactly causing it but the error seems to come from vite and no error happens in the SFC playground. You should open an issue there instead.
It's weird that removing it seems to solve it while still allowing to add it again without crashing. | 2021-08-13T15:20:07 | 2021-08-13T15:20:07 | {} | MEMBER |
vuejs | core | 899,069,334 | 4,344 | fatawesome | Yep, that definitely helped. Thank you @LinusBorg :) | 2021-08-15T15:45:03 | 2021-08-15T15:45:03 | {} | NONE |
vuejs | core | 899,301,874 | 4,312 | cutsin | Same issue in new scaffold with `yarn create vite + ts` but no Pug used.
Error: [Vue warn]: Invalid vnode type when creating vnode: undefined.
Vue version: 3.2.x | 2021-08-16T07:54:12 | 2021-08-16T07:54:12 | {} | NONE |
vuejs | core | 898,554,815 | 4,333 | mariusa | > It's weird that removing it seems to solve it while still allowing to add it again without crashing.
Took me a while to figure out: because of node_modules/.vite/ cache | 2021-08-13T15:46:13 | 2021-08-13T15:46:13 | {} | NONE |
vuejs | core | 899,067,530 | 4,344 | fatawesome | Sounds legit, thanks!
I will try messing with Module Federation configs (maybe forgot to mark package as singleton or smth) and let know if it helped. | 2021-08-15T15:30:18 | 2021-08-15T15:30:18 | {} | NONE |
vuejs | core | 899,768,010 | 4,351 | yyx990803 | Hmm, not sure if this is the best place to put this, since the `onXXX` listener convention applies to all APIs where props are expected. This will be better documented in the upcoming new docs site. | 2021-08-16T19:37:33 | 2021-08-16T19:37:33 | {} | MEMBER |
vuejs | core | 899,772,911 | 4,313 | yyx990803 | Good catch and thanks for the test cases! | 2021-08-16T19:46:36 | 2021-08-16T19:46:36 | {} | MEMBER |
vuejs | core | 897,461,015 | 4,318 | basvanmeurs | Hi jods, thanks for sharing your thoughts again!
I think that you have a valid point regarding array iteration performance.
As far as I can see, only in case of iteration on the shallowRef, we could omit the get trap. That makes it a bit of a niche optimization. Besides, it would require all the mutation traps t... | 2021-08-12T08:48:55 | 2021-08-12T08:50:02 | {} | CONTRIBUTOR |
vuejs | core | 898,794,556 | 4,334 | edison1105 | I tried it works fine and [the test case](https://github.com/vuejs/vue-next/commit/9d5fd33d6dadf3186f7979d811dedf092f3ddcb7#diff-881a91030fede45c3f2124b4d2eee7ed57fbcd53b2cd347839f609f8e9a1e5ecR17) passed.
Could you provide a mini repro ? I might be missing something? | 2021-08-14T02:02:44 | 2021-08-14T02:02:44 | {} | MEMBER |
vuejs | core | 899,015,811 | 4,340 | sheremet-va | <img width="1617" alt="Снимок экрана 2021-08-15 в 11 29 16" src="https://user-images.githubusercontent.com/16173870/129472221-da526723-7bc2-46e3-af73-7ff669b05d63.png">
Here, I made a reproduction (using Vite starter template): https://github.com/sheremet-va/vue-template-string-setup-bug | 2021-08-15T08:30:31 | 2021-08-15T08:35:22 | {} | NONE |
vuejs | core | 899,025,429 | 4,341 | HcySunYang | Give project for reproduction, please. | 2021-08-15T09:56:35 | 2021-08-15T09:56:35 | {} | MEMBER |
vuejs | core | 930,285,748 | 1,359 | henribru | This is presumably an issue on `eslint-plugin-vue`'s side, but just as a heads-up to people, it seems ESLint can't format expressions in the template if they contain Typescript syntax | 2021-09-29T15:28:04 | 2021-09-29T15:28:28 | {} | NONE |
vuejs | core | 930,295,588 | 1,359 | Spittal | In an environment without ESLint this still throws. I'm using the `yarn create vite` `vue-ts`. I updated to vue version `3.2.19`, added the following to `App.vue`
```
//...
const hi = ref('hi');
</script>
<template>
<input type="text" v-model="hi!">
//...
```
and I still get the error. Even on ... | 2021-09-29T15:39:18 | 2021-09-29T15:39:18 | {} | NONE |
vuejs | core | 930,490,744 | 4,697 | yyx990803 | This is already covered by the other test cases. | 2021-09-29T19:48:03 | 2021-09-29T19:48:03 | {} | MEMBER |
vuejs | core | 931,350,508 | 4,710 | posva | This is rather expected. It would be a huge pain for most users if any TS error prevented the page from rendering by default. You can probably configure it otherwise if you want to. | 2021-09-30T14:00:53 | 2021-09-30T14:00:53 | {} | MEMBER |
vuejs | core | 931,459,716 | 4,710 | posva | A syntax or runtime error prevents the page from rendering but type errors do not. This is one of the benefits of using TS: it will generate JS code even if it's not type safe. | 2021-09-30T16:05:55 | 2021-09-30T16:05:55 | {} | MEMBER |
vuejs | core | 931,460,907 | 4,710 | posva | Also, you catch type errors before going to production with TS or vue-tsc, not during development.
Feel free to develop a plugin (vite/webpack) that shows an overlay for those errors | 2021-09-30T16:07:18 | 2021-09-30T16:07:18 | {} | MEMBER |
vuejs | core | 931,522,864 | 4,710 | RollingTL | It is very basic vue-cli installation. Nothing special.
```
{
"name": "vue4",
"version": "0.1.0",
"private": true,
"scripts": {
"serve": "vue-cli-service serve",
"build": "vue-cli-service build",
"lint": "vue-cli-service lint"
},
"dependencies": {
"@vuelidate/core": "^2.0.0-alph... | 2021-09-30T17:31:08 | 2021-09-30T17:31:08 | {} | NONE |
vuejs | core | 932,088,425 | 4,717 | Oleksii14 | Regarding the issue duplication: there are no answers since 11 days after publication, so I decided to ask here. But I will take it into consideration | 2021-10-01T09:55:52 | 2021-10-01T09:55:52 | {} | NONE |
vuejs | core | 937,370,398 | 4,745 | yyx990803 | The new syntax require using `:deep` (or `::v-deep`) as a **pseudo function** - i.e. the parens are required:
```js
:deep {} /* this is wrong */
:deep(div) {} /* this is correct */
```
Without parens you are using it as a **combinator**, which is exactly what the message is warning you about. | 2021-10-07T01:24:43 | 2021-10-07T01:25:10 | {
"+1": 11,
"-1": 13
} | MEMBER |
vuejs | core | 931,349,018 | 4,709 | posva | Using `updated` should be fine.
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-09-30T13:59:13 | 2021-09-30T13:59:13 | {} | MEMBER |
vuejs | core | 933,345,652 | 4,733 | marina-mosti | Thanks for the reply @posva this seems like a good base solution, do you think there's a chance that it can be implemented as the official one? I'm more than happy to copy/paste and call it resolved, but still gives me the feels that it has too much internal API "know-how" in it | 2021-10-04T10:20:25 | 2021-10-04T10:20:25 | {} | NONE |
vuejs | core | 933,438,690 | 4,733 | posva | I don't think it makes sense to add this API if we cannot reach a consensus on what `isVNodeEmpty()` means (ref the comment I linked).
There is nothing internal about that function, it's safe to use | 2021-10-04T12:32:51 | 2021-10-04T12:32:51 | {
"+1": 1
} | MEMBER |
vuejs | core | 935,897,920 | 4,735 | LinusBorg | When the new docs are done, which is in the works. | 2021-10-06T10:08:41 | 2021-10-06T10:08:41 | {
"+1": 1,
"confused": 1
} | MEMBER |
vuejs | core | 930,320,613 | 1,359 | Spittal | Hm, yeah it seems that 3.2.19 did fix most syntax, but not the non-null assertion operator at the end of a name. | 2021-09-29T16:08:30 | 2021-09-29T16:08:30 | {} | NONE |
vuejs | core | 933,463,228 | 4,733 | marina-mosti | Thanks @posva makes sense, closing | 2021-10-04T13:05:18 | 2021-10-04T13:05:18 | {} | NONE |
vuejs | core | 932,299,262 | 3,478 | KaelWD | https://github.com/microsoft/TypeScript/issues/43826 | 2021-10-01T14:52:10 | 2021-10-01T14:52:10 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 933,258,059 | 1,414 | einavk | Hi,
I am using the suggested setup, like @jfbrennan , and when running the application on dev env using "vue-cli-service serve" I do not get the warnings. However, on production, I see the warnings in the console. I assumed these are build-time created warnings, and I am using the vue-cli-service for build with the sa... | 2021-10-04T08:23:43 | 2021-10-04T08:23:43 | {} | NONE |
vuejs | core | 932,084,424 | 4,717 | posva | Don't duplicate issues, thanks.
It's because of the limitation of HTML:
```html
<custom-component @my-event="doSomething" />
```
using `@myEvent` in HTML will render as `@myevent` but with `v-model` the event listener is added by vue so we don't have that limitation | 2021-10-01T09:49:28 | 2021-10-01T09:49:28 | {} | MEMBER |
vuejs | core | 932,753,785 | 4,730 | klwfwdk | [模板引用](https://v3.cn.vuejs.org/guide/composition-api-template-refs.html#jsx-%E4%B8%AD%E7%9A%84%E7%94%A8%E6%B3%95) 这个
确实setup运行时没有render，使用对应的变量是`undefined`. 但是在写在setup函数中的生命周期回调里面就有对应的节点了 | 2021-10-02T13:38:21 | 2021-10-02T13:38:21 | {} | CONTRIBUTOR |
vuejs | core | 932,783,641 | 4,729 | yyx990803 | These are code paths that are not shipped to the browser in production so they don't need tree-shaking annotations. | 2021-10-02T16:55:31 | 2021-10-02T16:55:31 | {
"+1": 1
} | MEMBER |
vuejs | core | 934,571,082 | 4,738 | kad-tijhuo | Our use case is being able to switch between pdf's and looping through the pages to render them. Each page is a child component of the pdf viewer.
When switching between 4 pdf's, one after another and forcing garbage collection before taking the screenshots:
Vue 3.2.13 (expected, the last pdf was 20 pages long):
... | 2021-10-05T16:33:11 | 2021-10-05T16:33:11 | {} | NONE |
vuejs | core | 936,275,184 | 4,741 | LinusBorg | A bit further up you find this:
https://github.com/vuejs/vue-next/blob/6171aecdcd5f71163c384479b225b731a10a8184/packages/runtime-dom/types/jsx.d.ts#L32-L41
Which says you can either add an index signature yourself or add individual custom properties, for better type safety.
```ts
// style.d.ts
import type {... | 2021-10-06T13:51:29 | 2021-10-06T13:54:37 | {
"+1": 3
} | MEMBER |
vuejs | core | 929,353,852 | 4,267 | cloydlau | ```ts
<script setup>
import { getCurrentInstance, onMounted } from 'vue'
onMounted(() => {
getCurrentInstance().proxy.$xxx()
})
</script>
``` | 2021-09-28T15:47:11 | 2021-09-28T15:47:11 | {
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 930,698,615 | 2,483 | hulkyhawk | > Not sure what you mean by that, `Boolean` props default to `false`
i mean if you use object literal to make ts infer the type, then vue will know that if you have a default field in the PropOption. use `Prop` type will loose the information, since default is optional
sorry, boolean is not proper here, you ca... | 2021-09-30T02:27:16 | 2021-09-30T02:43:30 | {} | NONE |
vuejs | core | 931,525,800 | 4,710 | posva | Then put it in a repo (with only vue, no need for any of your other deps like vue-router, xstate, etc) with repro steps and specify what Vue version used to work. | 2021-09-30T17:35:29 | 2021-09-30T17:35:29 | {} | MEMBER |
vuejs | core | 931,537,447 | 4,713 | aleksander237 | Thanks for quick response.
My point is that all undeclared properties are available in the `$attrs`. As soon as the property is declared it is available somwhere else, but with the listeners declaration (including in emits) makes a listener "unaccessible". So what is the solution here? Should I simply exclude listen... | 2021-09-30T17:51:51 | 2021-09-30T17:51:51 | {} | NONE |
vuejs | core | 932,754,372 | 4,730 | anonymous1132 | > [模板引用](https://v3.cn.vuejs.org/guide/composition-api-template-refs.html#jsx-%E4%B8%AD%E7%9A%84%E7%94%A8%E6%B3%95) 这个 确实setup运行时没有render，使用对应的变量是`undefined`. 但是在写在setup函数中的生命周期回调里面就有对应的节点了
这样写的确方便多了，谢谢了 | 2021-10-02T13:42:56 | 2021-10-02T13:42:56 | {} | NONE |
vuejs | core | 933,290,383 | 4,731 | posva | This is likely intended because const enums are replaced with their value (1, 2, or 3) when bundling. | 2021-10-04T09:06:22 | 2021-10-04T09:06:22 | {} | MEMBER |
vuejs | core | 935,893,154 | 4,741 | LinusBorg | Please provide a runnable reproduction as required. In case of type issues, at the **very** least, provide the code used to get the type error. | 2021-10-06T10:05:41 | 2021-10-06T10:05:41 | {} | MEMBER |
vuejs | core | 937,369,062 | 4,744 | yyx990803 | It definitely isn't a recommended option anymore in official docs or default tooling (moving to Vite-based soon and vue-cli will be in maintenance mode).
Deprecation will depend on actual usage and @ktsn's intention on further working on the project. I suggest moving the discussion to `vue-class-component` repo itse... | 2021-10-07T01:20:59 | 2021-10-07T01:20:59 | {
"+1": 1
} | MEMBER |
vuejs | core | 930,091,005 | 4,701 | LinusBorg | I found that the reason is found in our `Deepreadonly` type.
It currently doesn't account for Refs, and instead treats refs like plain objects, which exposes that RefSymbol property as a result of the recursive nature of this type.
I'll send a patch later | 2021-09-29T11:31:03 | 2021-09-29T11:31:55 | {} | MEMBER |
vuejs | core | 931,888,374 | 4,699 | caozhong1996 | > We already mostly use `.slice` across the codebase so I think it's better to be consistent and use `.slice` everywhere. It's also shorter.
That's right, I now used `.slice` instead of `.substring` .
I also added a type check in `global.d.ts` to avoid using 'substring' in this project.
I don't know if this ... | 2021-10-01T04:28:14 | 2021-10-01T04:29:02 | {} | CONTRIBUTOR |
vuejs | core | 935,441,003 | 4,740 | caozhong1996 | Some API need to be imported, others don't. This will confuse users, I don't agree with that.
Maybe use compiler macro to auto import API which be used is a good idea?（Maybe too costly）
In fact, `@vue/ref-transform` did something similar.
BTW, go into a discussion in the rfcs repo would be better😀 | 2021-10-06T04:45:46 | 2021-10-06T04:45:46 | {} | CONTRIBUTOR |
vuejs | core | 932,086,390 | 4,717 | Oleksii14 | Got it. What if we use the Vue event name directly in our code?
```vue
<custom-component :model-value="value" @update:modelValue="onUpdate" />
```
Will it break the Styleguide recommendations?
Also, wouldn't it be better to use the one style in both projects' code base and Vue core? | 2021-10-01T09:52:37 | 2021-10-06T18:58:39 | {} | NONE |
vuejs | core | 929,727,736 | 3,874 | edison1105 | @lukewarlow
Let's pushing this. ping @yyx990803 | 2021-09-29T00:41:45 | 2021-09-29T00:41:45 | {} | MEMBER |
vuejs | core | 930,090,762 | 2,483 | KaelWD | Not sure what you mean by that, `Boolean` props default to `false` | 2021-09-29T11:30:40 | 2021-09-29T11:30:40 | {} | CONTRIBUTOR |
vuejs | core | 930,692,012 | 4,703 | ygj6 | @unuseless Your first demo's `vm` is the return of `mount`, but your second demo's `vm` is the return of `Vue.createApp`.
https://v3.vuejs.org/api/application-api.html#mount | 2021-09-30T02:11:29 | 2021-09-30T02:12:24 | {} | MEMBER |
vuejs | core | 931,016,883 | 4,706 | posva | You could use a prop.
Changing this would be a breaking change and the rationale was discussed in the RFC (rfcs repo) | 2021-09-30T08:22:50 | 2021-09-30T08:22:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 931,321,680 | 4,709 | Pentadome | You are not watching `a`, you are watching an function that returns `props.a`.
Try
``` typescript
watch(props.a, console.log)
```
instead.
Also this place is not for asking questions. Try https://stackoverflow.com/questions/tagged/vue.js instead. | 2021-09-30T13:26:34 | 2021-09-30T13:26:34 | {} | CONTRIBUTOR |
vuejs | core | 932,752,798 | 4,730 | anonymous1132 | > 这个本来就是文档里面写了的吧，如果不覆盖你怎么在setup里面处理模板里面的节点 应该避免这两个变量同名。
> […](#)
> ---原始邮件--- 发件人: ***@***.***> 发送时间: 2021年10月2日(周六) 晚上9:10 收件人: ***@***.***>; 抄送: ***@***.***>; 主题: [vuejs/vue-next] setup中返回的属性名与元素模板中使用的ref名相同会导致setup中返回的属性被覆盖 (#4730) Version 3.2.19 Reproduction link sfc.vuejs.org/ Steps to reproduce <script... | 2021-10-02T13:30:47 | 2021-10-02T13:30:47 | {} | NONE |
vuejs | core | 934,164,603 | 4,736 | marina-mosti | Thanks @LinusBorg that's a nice workaround! Hopefully, we can get a proper solution 🙏🏻
I agree with you that `$attrs` should not include it as it does feel like the magic box of "everything else". | 2021-10-05T08:02:12 | 2021-10-05T08:02:12 | {
"+1": 1
} | NONE |
vuejs | core | 934,401,227 | 3,811 | little-buddy | Hey, everybody, who can help me?
When I update vue-loader@version, I can build success in local,
but when I push to publish with netlify, it don' work.
It's really hard to understand 😭 | 2021-10-05T13:13:00 | 2021-10-05T13:13:00 | {} | NONE |
vuejs | core | 929,951,716 | 2,483 | hulkyhawk | @KaelWD if you use `Prop` type to default props instead of an object literal, then Vue cannot guarantee there is a default field then;
```ts
const props: { foo: Prop<boolean> } = { foo: { type: Boolean } }
``` | 2021-09-29T08:22:11 | 2021-09-29T08:22:11 | {} | NONE |
vuejs | core | 931,458,561 | 4,711 | posva | Duplicate of #4710 | 2021-09-30T16:04:33 | 2021-09-30T16:04:33 | {} | MEMBER |
vuejs | core | 932,071,787 | 4,717 | Oleksii14 | Related issue created in the vuejs/docs:
https://github.com/vuejs/docs/issues/1250 | 2021-10-01T09:29:42 | 2021-10-01T09:29:42 | {} | NONE |
vuejs | core | 933,942,001 | 4,731 | caozhong1996 | Thanks for your reply. | 2021-10-04T23:51:59 | 2021-10-04T23:51:59 | {} | CONTRIBUTOR |
vuejs | core | 930,489,349 | 1,359 | yyx990803 | Please report bugs for TS in templates as separate issues with reproductions. Do not reuse closed issues. | 2021-09-29T19:45:47 | 2021-09-29T19:45:47 | {} | MEMBER |
vuejs | core | 930,745,042 | 4,689 | danranVm | my final solution is as follows:
```ts
export const iconProps = {
iconfont: IxPropTypes.bool.def(false),
name: IxPropTypes.string,
rotate: IxPropTypes.oneOfType([Boolean, Number, String]),
}
export type IconProps = IxInnerPropTypes<typeof iconProps> // This is the type used internally
export type Ico... | 2021-09-30T03:20:29 | 2021-09-30T03:20:29 | {} | NONE |
vuejs | core | 931,599,365 | 4,714 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 46.24 KB (0%) |
| runtime-dom.global.prod.js | 30.59 KB (0%) |
| index.js | 18.02 KB (0%) | | 2021-09-30T19:22:48 | 2021-09-30T19:22:48 | {} | NONE |
vuejs | core | 932,250,275 | 4,705 | yyx990803 | It's intentional... | 2021-10-01T13:54:28 | 2021-10-01T13:54:28 | {} | MEMBER |
vuejs | core | 932,971,601 | 4,273 | Aaminly | The main problem is that in the SSR environment, if an instruction is written on the label but not declared, an error will be reported, and the error information is not intuitive enough | 2021-10-03T15:16:19 | 2021-10-03T15:16:19 | {} | NONE |
vuejs | core | 936,024,231 | 4,741 | posva | Next time, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro
If you don't want to spend that time, use the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js) for questions first. But feel free to come ba... | 2021-10-06T11:19:36 | 2021-10-06T11:19:36 | {} | MEMBER |
vuejs | core | 929,021,431 | 4,693 | jan-thoma | Thanks issue is now here [https://github.com/vuejs/docs/issues/1261](url) | 2021-09-28T09:32:15 | 2021-09-28T09:32:15 | {} | NONE |
vuejs | core | 930,296,662 | 1,359 | henribru | Sorry for the confusion, my comment wasn't related to yours | 2021-09-29T15:40:33 | 2021-09-29T15:40:33 | {} | NONE |
vuejs | core | 931,527,124 | 4,713 | posva | By defining the emits, you ensure they are not passed to `$attrs`. This is intentional. | 2021-09-30T17:37:25 | 2021-09-30T17:37:25 | {} | MEMBER |
vuejs | core | 936,151,110 | 4,741 | livthomas | Ok. It looks like it is a more complicated issue than I originally thought. I should probably explain it more.
I recently migrated to `vue-tsc` and it immediately started complaining about every `style` attribute I used saying that it should be of type `StyleValue`. So I used this type for all my style variables but... | 2021-10-06T12:34:30 | 2021-10-06T12:34:30 | {} | NONE |
vuejs | core | 937,375,514 | 4,727 | dependabot[bot] | OK, I won't notify you about serve again, unless you re-open this PR or update it yourself. 😢 | 2021-10-07T01:39:38 | 2021-10-07T01:39:38 | {} | CONTRIBUTOR |
vuejs | core | 930,300,304 | 4,702 | LinusBorg | First is not supposed to be working, because there is no `item` to render.
Please use chat.vuejs.org to ask for help. | 2021-09-29T15:44:51 | 2021-09-29T15:44:51 | {} | MEMBER |
vuejs | core | 930,951,874 | 4,706 | posva | The listener will appear if you don't define it with `defineEmits()`. This is intended. | 2021-09-30T07:44:02 | 2021-09-30T07:44:02 | {} | MEMBER |
vuejs | core | 931,819,327 | 4,712 | edison1105 | This will lead to performance degradation. | 2021-10-01T01:18:00 | 2021-10-01T01:18:00 | {} | MEMBER |
vuejs | core | 931,875,874 | 4,712 | edison1105 | see https://github.com/vuejs/vue-next/pull/408 https://github.com/vuejs/vue-next/pull/3400 https://github.com/vuejs/vue-next/pull/4082
Exactly the same as this PR
see https://github.com/vuejs/vue-next/pull/319 | 2021-10-01T03:59:47 | 2021-10-01T04:01:38 | {
"+1": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.