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 | 826,611,287 | 3,674 | posva | Apparently, there was a reason for the dark color to be picked in the past but let's do the proposal and see if this is possible! | 2021-04-26T08:09:54 | 2021-04-26T08:09:54 | {} | MEMBER |
vuejs | core | 827,405,728 | 3,674 | klef-dev | Looking at it, is there any language currently using this proposed color code #41b883 on github? | 2021-04-27T08:05:25 | 2021-04-27T08:05:25 | {} | NONE |
vuejs | core | 827,612,911 | 3,577 | yowzadave | Agree with the others--this was a bug, upgrading to 3.0.11 for vue and @vue/compiler-sfc resolved it for me. Thanks for the suggestion!
| 2021-04-27T13:37:26 | 2021-04-27T13:37:26 | {} | NONE |
vuejs | core | 828,264,814 | 3,687 | hyf0 | misunderstood your meaning just now.
Now, I get it. `as PropType<'test' | 'trolley'>` is just a type , It will disapper after compiling, so it won't affect runtime. If you want a runtime check, you need do something like this
```ts
msg: {
type: String as PropType<'test' | 'trolley'>,
validate: (msg: ... | 2021-04-28T08:34:29 | 2021-04-28T08:46:12 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 826,137,940 | 3,665 | posva | Please open an issue with a boiled down repro (no i18n, no ts, no jest, no babel, no router, etc) | 2021-04-24T18:54:44 | 2021-04-24T18:54:44 | {} | MEMBER |
vuejs | core | 826,295,507 | 3,661 | HcySunYang | Then it is probably not related to the Vue core, let’s track it in https://github.com/vuejs/vue-cli/issues/6282 | 2021-04-25T10:00:24 | 2021-04-25T10:00:24 | {} | MEMBER |
vuejs | core | 827,379,628 | 3,683 | HcySunYang | This is expected, do not manipulate the original data in Vue3 | 2021-04-27T07:25:32 | 2021-04-27T07:25:32 | {} | MEMBER |
vuejs | core | 827,519,801 | 3,685 | posva | The problem with this is the warning could still be useful if someone forgets an existing `beforeDestroy` and ads a `beforeUnmount()` but I think it's still reasonable to omit the warning if both hooks are present. You should also add a test | 2021-04-27T11:04:03 | 2021-04-27T11:04:03 | {} | MEMBER |
vuejs | core | 828,317,222 | 3,687 | posva | Runtime validation requires `validate`. IDE validation can be achieved with VS code extensions like Volar and Vetur but it's not something that can be addressed in Vue Core | 2021-04-28T09:46:14 | 2021-04-28T09:46:14 | {} | MEMBER |
vuejs | core | 829,030,067 | 3,422 | hairyf | 
又出现了这个问题，我们同事都炸了 | 2021-04-29T08:09:59 | 2021-04-29T08:09:59 | {} | NONE |
vuejs | core | 830,076,322 | 2,513 | LinusBorg | As indicated by the open issue, there's no solution yet. | 2021-04-30T12:57:19 | 2021-04-30T12:57:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 830,103,466 | 2,513 | zauan | The "solution" we are using in production is to manually modify a vue file and disable this ( runtime-dom.esm-bundler.js in our case ), however, I do not recommend doing so as other problems may appear.
The changes we've made:
https://gist.github.com/zauan/a3488a9feb799242df607c983de9c5b7
We have this modificati... | 2021-04-30T13:41:12 | 2021-04-30T13:41:12 | {
"hooray": 1
} | NONE |
vuejs | core | 825,529,307 | 3,655 | Bigfish8 | > This is intentional, you can check the implementation of isReactive
I know the implementation.But I think if don't use markRaw, isReactive() will also return false.So isReadonly() will be more reasonable？ | 2021-04-23T09:27:26 | 2021-04-23T09:27:26 | {} | CONTRIBUTOR |
vuejs | core | 825,533,524 | 3,655 | HcySunYang | Hmmm, Instead of deleting the `isReactive` line, it would be better to add another line:
```js
expect(isReactive(obj.bar)).toBe(false)
expect(isReadonly(obj.bar)).toBe(false)
```
They co-exist | 2021-04-23T09:34:45 | 2021-04-23T09:36:09 | {} | MEMBER |
vuejs | core | 826,041,594 | 3,001 | edison1105 | @nfplee
> any idea when this pull request will go live?
I also don't know.
If you are very anxious, maybe we can try to release a `Knightly build` version via https://github.com/knightly-bot | 2021-04-24T06:08:13 | 2021-04-24T06:08:13 | {} | MEMBER |
vuejs | core | 827,409,529 | 3,674 | wenfangdu | @klefcodes Nope. | 2021-04-27T08:10:48 | 2021-04-27T08:10:48 | {} | NONE |
vuejs | core | 829,331,169 | 3,694 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 41.73 KB (0%) |
| runtime-dom.global.prod.js | 27.61 KB (0%) |
| size-check.global.prod.js | 16.79 KB (0%) | | 2021-04-29T15:22:08 | 2021-04-29T15:22:08 | {} | NONE |
vuejs | core | 830,171,193 | 3,693 | TakNePoidet | Without specifying generic typescript does not understand what type of props
even when specifying the type as in the documentation
| 2021-04-30T15:29:41 | 2021-04-30T15:29:41 | {} | NONE |
vuejs | core | 826,048,052 | 3,661 | zizyzhang | I did `cnpm install vue@3.0.11 && cnpm install @vue/compiler-sfc@3.0.11` and updete the `package.json` file.
Still not working for me. | 2021-04-24T07:11:13 | 2021-04-24T07:11:13 | {} | NONE |
vuejs | core | 826,017,215 | 3,349 | felipec | > I do care. I just asked you to help a bit by opening an issue in the correct repo, and be a bit more specific about what you said you read in the docs.
**My** issue is with Vue 3's code, which does not work correctly.
**Your** issue is with Vue 3's documentation.
**My** issue has absolutely nothing to do wit... | 2021-04-24T02:01:42 | 2021-04-24T10:01:44 | {} | NONE |
vuejs | core | 826,699,513 | 3,681 | HcySunYang | Vue3 uses the `innerHTML` of the container as the template for components. | 2021-04-26T10:03:19 | 2021-04-26T10:03:19 | {} | MEMBER |
vuejs | core | 826,820,594 | 3,014 | klevron | Well, it was not so difficult (thanks to pikax on discord) :
```ts
function customComponent<P extends Readonly<ComponentPropsOptions> = {}>(
props: P
) {
return defineComponent({
extends: Parent,
props
})
}
``` | 2021-04-26T13:06:56 | 2021-04-26T13:06:56 | {} | NONE |
vuejs | core | 827,384,351 | 3,682 | HcySunYang | > I would say this is an advanced usage, with the current implementation it won't support props declared on mixins/extends since to merge those you will need to extract $props which will lose the generic template.
I agree with this point | 2021-04-27T07:32:58 | 2021-04-27T07:32:58 | {} | MEMBER |
vuejs | core | 829,033,078 | 3,422 | HcySunYang | Please open a new issue and provide a **valid minimum** repro, otherwise it will still be closed | 2021-04-29T08:14:46 | 2021-04-29T08:14:46 | {} | MEMBER |
vuejs | core | 830,177,820 | 3,693 | TakNePoidet | Okay. Thank you
| 2021-04-30T15:32:27 | 2021-04-30T15:32:27 | {} | NONE |
vuejs | core | 826,049,032 | 3,661 | zizyzhang | > 
>
> 1. remove yarn.lock file
> 2. update `vue `to `3.0.11`
> 3. update `@vue/compiler-sfc` to `3.0.11`
>
> I'm sure it will work fine and I've tested it locally.
` | 2021-04-23T06:53:42 | 2021-04-23T06:54:13 | {} | MEMBER |
vuejs | core | 825,535,453 | 3,645 | hyf0 | > > type annotation will get a compile error, while type assertion don't
>
> Cast `as ...` is not as good practice, but I don't see the compiler error that you mention, do you mind explaining? The code should be building and passing all the tests regardless of this changes 🤔
I create a [demo here](https://www.ty... | 2021-04-23T09:38:17 | 2021-04-23T09:38:17 | {} | CONTRIBUTOR |
vuejs | core | 825,596,949 | 3,659 | edison1105 | Duplicate of https://github.com/vuejs/vue-next/issues/3328 | 2021-04-23T11:33:57 | 2021-04-23T11:33:57 | {} | MEMBER |
vuejs | core | 955,030,704 | 4,876 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4397
Don't skip the issue template | 2021-10-29T20:30:54 | 2021-10-29T20:30:54 | {} | MEMBER |
vuejs | core | 955,181,862 | 4,397 | Blackfaded | Having the same issue. Any Workaround available? | 2021-10-30T09:43:24 | 2021-10-30T09:43:24 | {
"+1": 5,
"eyes": 1
} | NONE |
vuejs | core | 955,880,418 | 4,871 | gcxfd | I already add coffeescript loader
```
<script lang="coffee">
import HelloWorld from "./vue/HelloWorld.vue"
export default {
setup:=>
}
</script>
```
it works
but `<script lang="coffee" setup>` not work
| 2021-11-01T02:49:28 | 2021-11-01T02:49:28 | {} | NONE |
vuejs | core | 957,064,008 | 4,882 | yyx990803 | We intentionally avoid using optional chaining in the codebase because we target ES2016 and TS will transpile it to something much more verbose. | 2021-11-02T03:17:45 | 2021-11-02T03:17:45 | {
"+1": 1
} | MEMBER |
vuejs | core | 957,266,737 | 593 | zs-g | > 在 Vue3 中，我尝试了以下代码，它可以卸载一个组件（不是整个应用程序）：
>
> ```
> <router-view v-slot="{Component, route}">
> <keep-alive ref="keepAlive"><component :key="route.path" :is="Component" /></keep-alive>
> </router-view>
> ```
>
> ```
> onCloseTab(targetName) {
> const route = this.tabRoutes.find(... | 2021-11-02T09:34:51 | 2021-11-02T09:36:03 | {} | NONE |
vuejs | core | 958,643,294 | 4,891 | edison1105 | see https://v3.vuejs.org/api/sfc-script-setup.html#defineexpose
[demo](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG5jb25zdCBtc2cgPSByZWYoJ0hlbGxvIFdvcmxkJylcbmNvbnN0IGNvbXBvbmVudCA9Q29tcFxuY29uc3QgY29tUmVmPXJlZihudWxsKVxuXG5... | 2021-11-03T04:12:20 | 2021-11-03T04:44:51 | {} | MEMBER |
vuejs | core | 958,899,556 | 1,120 | rashfael | d10835a fixed this for me. We're currently running vue@3.2.20 in a project with `v-if="…<…"` in pug templates. I'd recommend creating a clean reproduction and opening a new issue. My reproduction from this issue is working after updating vue and forking the sandbox to force a clean install https://codesandbox.io/s/frie... | 2021-11-03T10:50:46 | 2021-11-03T10:50:46 | {
"+1": 1
} | NONE |
vuejs | core | 953,719,430 | 4,872 | LinusBorg | A short explanation: In Vue 2, we added global properties by extending the prototype. To mimic this with `globalProperties`, we bind functions provided as global properties to the component proxy instance. but calling `fn.bind()` creates a *new* function that is missing any additional properties that were defined on th... | 2021-10-28T10:32:48 | 2021-10-28T10:32:48 | {} | MEMBER |
vuejs | core | 954,023,965 | 4,874 | trusktr | Here is a non-ideal workaround that requires modifying the props shape of the root component (this may not be ideal if the root component is imported from a third party).
[sfc.vuejs.org](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdD5cbiAgaW1wb3J0IENvbXAgZnJvbSAnLi9Db21wLnZ1ZSdcbiAgaW1wb3J0IHtjcmVhdGVBcHAsIHJlYWN... | 2021-10-28T16:50:12 | 2021-10-28T16:50:12 | {} | NONE |
vuejs | core | 954,044,507 | 4,874 | posva | I would say you need to pass an [object of refs to props](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdD5cbiAgaW1wb3J0IENvbXAgZnJvbSAnLi9Db21wLnZ1ZSdcbiAgaW1wb3J0IHtjcmVhdGVBcHAsIHJlYWN0aXZlLCB0b1JlZnN9IGZyb20gJ3Z1ZSdcblxuICBleHBvcnQgZGVmYXVsdCB7XG4gICAgbW91bnRlZCgpIHtcbiAgICAgIGNvbnN0IGRpdiA9IHRoaXMuJHJlZnMuZGl2XG4... | 2021-10-28T17:17:29 | 2021-10-28T17:17:29 | {} | MEMBER |
vuejs | core | 957,055,329 | 4,883 | yyx990803 | The Vue 2 issue you linked to seems to be a bug in Vue 2's scoped ID handling, can you replicate the behavior in Vue 3?
Even if the same issue can be reproduced in Vue 3, it should be fixed as a scoped ID bug. There should still be no duplicated attributes and IMO it's better to warn the user instead of silently ign... | 2021-11-02T02:59:20 | 2021-11-02T02:59:20 | {
"+1": 1
} | MEMBER |
vuejs | core | 957,090,993 | 4,792 | yyx990803 | Looks like this was already fixed by https://github.com/vuejs/vue-next/commit/3ca83179d1a798f65e4e70215c511e2f1b64adb6 since I can no longer reproduce #4716, even without this PR. | 2021-11-02T04:23:37 | 2021-11-02T04:23:37 | {} | MEMBER |
vuejs | core | 958,000,505 | 4,845 | 07akioni | > > I want the animation play on its first mount.
>
> your description is really incomplete . if you want that animation play on its first mount , so what is the bug?
When default `v-show` is set to `true`, everything works fine.
The main problem is when the default `v-show` is set to `false`, the animation do... | 2021-11-02T18:07:11 | 2021-11-02T18:09:33 | {} | CONTRIBUTOR |
vuejs | core | 953,572,428 | 4,854 | jeffydc | Sorry for the invalid issue. It was [DuckDuckGo extension](https://addons.mozilla.org/en-US/firefox/addon/duckduckgo-for-firefox/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search) causing this error. | 2021-10-28T07:24:08 | 2021-10-28T07:24:08 | {} | CONTRIBUTOR |
vuejs | core | 953,624,078 | 4,866 | ygj6 | I simplified it [sfc.vuejs.org/](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aW5wdXQgOnJlZj0naW5wdXQnLz5cbjwvdGVtcGxhdGU+XG5cbjxzY3JpcHQgbGFuZz1cInRzXCIgc2V0dXA+XG5pbXBvcnQgeyBvbk1vdW50ZWQsIHJlZiB9IGZyb20gJ3Z1ZSdcbmNvbnN0IGlucHV0ID0gJ3JlZk5hbWUnXG5jb25zdCByZWZOYW1lID0gcmVmKG51bGwpXG5vbk1vdW50ZWQoKCkgPT4g... | 2021-10-28T08:32:01 | 2021-10-28T08:32:01 | {
"+1": 1
} | MEMBER |
vuejs | core | 957,103,991 | 4,792 | yyx990803 | Hmm, I may have missed something but this PR doesn't seem to affect either #4716 or #4789. But it does fix the added test case. | 2021-11-02T05:03:28 | 2021-11-02T05:03:28 | {} | MEMBER |
vuejs | core | 957,110,724 | 4,792 | yyx990803 | I refactored the resolve call a bit more and I believe 4b7f76e3 should be a more efficient fix (it avoids some unnecessary `_update()` calls) | 2021-11-02T05:21:35 | 2021-11-02T05:21:35 | {} | MEMBER |
vuejs | core | 957,669,083 | 4,879 | posva | You can provide multiple slots and nest them inside of the component receiving them to allow this:
```vue
<template>
<slot name="container">
<div class="container">
<slot name="inner" />
</div>
</slot>
</template
```
If you want to propose a new syntax, please use the RFC process in the ... | 2021-11-02T14:14:35 | 2021-11-02T14:14:43 | {} | MEMBER |
vuejs | core | 957,977,470 | 4,845 | 07akioni | > @07akioni , I think you should delete the `appear` attribute from the transition because according to docs :
>
> > If you also want to apply a transition on the initial render of a node, you can add the appear
>
> The element has rendered because v-show will just add an `display:none` to element and when you ad... | 2021-11-02T17:36:52 | 2021-11-02T17:36:52 | {} | CONTRIBUTOR |
vuejs | core | 957,999,273 | 4,887 | LinusBorg | FYI, fork-ts-checker is being used for perf reasons, afaik. you should be able to remove that plugin and have ts-loader typecheck instead, which should work better as it will receive the compiled script already.
No guarantees, but may be worth a try. | 2021-11-02T18:05:28 | 2021-11-02T18:05:28 | {} | MEMBER |
vuejs | core | 958,690,591 | 593 | mrzhxping | > In Vue3, I tried the following code, and it can unmount an component (not the whole app):
>
> ```
> <router-view v-slot="{Component, route}">
> <keep-alive ref="keepAlive"><component :key="route.path" :is="Component" /></keep-alive>
> </router-view>
> ```
>
> ```
> onCloseTab(target... | 2021-11-03T06:50:08 | 2021-11-03T06:50:08 | {} | NONE |
vuejs | core | 958,953,973 | 4,897 | bodograumann | I'm seeing the same issue.
Same context (I think): `<script setup lang="ts">` and boolean prop set to true. Correctly works in dev mode, but not in production build.
It worked with vue-cli@5.0.0-beta.3 and fails in vue-cli@5.0.0-beta.6. | 2021-11-03T11:45:29 | 2021-11-03T11:45:29 | {
"+1": 1
} | NONE |
vuejs | core | 955,184,766 | 4,873 | LinusBorg | I'm can't follow ... | 2021-10-30T10:07:46 | 2021-10-30T10:07:46 | {} | MEMBER |
vuejs | core | 957,054,262 | 4,871 | yyx990803 | This is by design. `<script setup>` can only work with plain JS or TS because we need to analyze the AST before the code is transformed by other plugins. | 2021-11-02T02:56:55 | 2021-11-02T02:56:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 955,182,547 | 4,873 | caozhong1996 | I have an idea, maybe we can record external library when seting globalProperties. So that we know if call fn.bind(proxy)🤔
````ts
set(
{ _: instance }: ComponentRenderContext,
key: string,
value: any
): boolean {
const { data, setupState, ctx } = instance
if (setupState !== EMPTY_OBJ ... | 2021-10-30T09:49:30 | 2021-11-02T05:49:22 | {} | CONTRIBUTOR |
vuejs | core | 958,774,298 | 1,120 | mehdi-aouadi | I am facing the same issue.
I am migrating a Vue 2 app to Vue 3 following [the migration guide](https://v3.vuejs.org/guide/migration/migration-build.html).
I am getting the same error when using a logical expression within a v-if tag:
`VueCompilerError: Illegal tag name. Use '<' to print '<'. `
@rashfael Did y... | 2021-11-03T09:23:50 | 2021-11-03T09:23:50 | {} | NONE |
vuejs | core | 958,980,498 | 4,874 | trusktr | It seems like a "regression" in terms of what we could do in Vue 2 but no longer can in Vue 3. This is Vue 2:
```js
import ThirdPartyComponent from 'somewhere'
const component = new Vue({...ThirdPartyComponent})
// ...
component.someProp = 123 // it works.
```
In Vue 3? | 2021-11-03T12:22:50 | 2021-11-03T12:44:47 | {
"+1": 2
} | NONE |
vuejs | core | 957,251,315 | 4,806 | mianmalife | Encountered the same problem | 2021-11-02T09:16:49 | 2021-11-02T09:16:49 | {} | NONE |
vuejs | core | 958,891,847 | 4,896 | posva | This might be expected as passed props are used in the generated JS to know when to render again.
You can use `v-memo="msg"` (or [msg]) to tell the component not to render if msg didn't change | 2021-11-03T10:47:13 | 2021-11-03T10:47:13 | {} | MEMBER |
vuejs | core | 953,684,728 | 4,872 | lqfxz520 | @posva When I comment out '@vue/compat', `this.$axios` has a `post` property，What accounts for this result?
```
import { defineConfig } from "vite";
import createVuePlugin from "@vitejs/plugin-vue";
export default defineConfig({
plugins: [
createVuePlugin({
template: {
compilerOptions: {
... | 2021-10-28T09:43:35 | 2021-10-28T09:44:31 | {} | NONE |
vuejs | core | 954,102,867 | 4,874 | LinusBorg | And don't get me wrong, it would make sense to allow/support it I think. It's just not a bug in my book. | 2021-10-28T18:39:24 | 2021-10-28T18:39:38 | {} | MEMBER |
vuejs | core | 954,462,157 | 4,333 | mariusa | Should have been fixed in vite: https://github.com/vitejs/vite/issues/4598 | 2021-10-29T06:21:54 | 2021-10-29T06:21:54 | {} | NONE |
vuejs | core | 957,092,845 | 4,789 | yyx990803 | Looks like the same bug as #4716 and fixed by 3ca8317 | 2021-11-02T04:27:28 | 2021-11-02T05:03:46 | {} | MEMBER |
vuejs | core | 957,181,562 | 4,859 | soulsam480 | just discovered this issue where the handler is getting fired two time. | 2021-11-02T08:01:35 | 2021-11-02T08:01:35 | {
"+1": 1
} | NONE |
vuejs | core | 957,234,304 | 4,397 | luyuhong0329 | Having the same issue.Only checking by as any.
` // login-panel.vue `
`import LoginAccount from './login-account.vue';`
`const accountRef = ref<InstanceType<typeof LoginAccount>>()`
`const handleLoginClick = () => {`
` (accountRef.value as any)?.loginAction()`
}`
`// login-account.vue`
`const loginAction =... | 2021-11-02T08:54:49 | 2021-11-02T09:01:00 | {
"+1": 1
} | NONE |
vuejs | core | 958,727,430 | 4,894 | ygj6 | https://github.com/vuejs/vue-next/pull/4471#issuecomment-927853354 | 2021-11-03T08:08:11 | 2021-11-03T08:08:11 | {
"+1": 2
} | MEMBER |
vuejs | core | 958,882,136 | 4,895 | posva | If workflows are failing the locks probably need to be updated instead 🤔 | 2021-11-03T10:42:35 | 2021-11-03T10:42:35 | {
"+1": 1
} | MEMBER |
vuejs | core | 958,975,609 | 4,897 | haoqunjiang | I can reproduce this issue with Vite too. So I'm transferring it to the vue-next repository. | 2021-11-03T12:16:44 | 2021-11-03T12:16:44 | {
"+1": 1
} | MEMBER |
vuejs | core | 959,028,150 | 4,897 | haoqunjiang | Oh the fix has just been merged:
https://github.com/vuejs/vue-next/pull/4790 | 2021-11-03T13:07:19 | 2021-11-03T13:07:19 | {
"+1": 3
} | MEMBER |
vuejs | core | 959,820,963 | 4,898 | posva | Your reproduction is not minimal, please read and follow https://new-issue.vuejs.org/?repo=vuejs/vue-next#why-repro when reporting a bug. Most bugs should be reproducible with the [SFC Playground](https://sfc.vuejs.org). | 2021-11-03T18:45:59 | 2021-11-03T18:45:59 | {} | MEMBER |
vuejs | core | 960,497,263 | 4,895 | ygj6 | > If workflows are failing the locks probably need to be updated instead 🤔
Well, I'm not sure. Now let's modify the lock file.:grin: | 2021-11-04T06:43:58 | 2021-11-04T06:43:58 | {
"rocket": 1
} | MEMBER |
vuejs | core | 953,653,972 | 4,868 | posva | I think he's referring to the generated JS as one is `type: [null, Boolean]` while the other is `type: Boolean` | 2021-10-28T09:05:15 | 2021-10-28T09:05:15 | {
"+1": 1
} | MEMBER |
vuejs | core | 953,996,897 | 4,845 | Bigfish8 | It is Intentional?
Just in my option,v-show means element actually render.It seems reasonable if it trigger the enter hooks. | 2021-10-28T16:15:01 | 2021-10-28T16:15:01 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 955,147,195 | 2,855 | josh-berry | Hitting this or a very similar issue in my vue-loader/webpack-based project even without `<script setup>` / with an explicit `defineComponent` call in my `<script lang="ts">` section. The issue just started after a recent update to vue-loader (which now apparently sends template code through the TypeScript compiler).
... | 2021-10-30T04:45:30 | 2021-10-30T04:45:30 | {} | NONE |
vuejs | core | 955,767,007 | 4,871 | mehanalavimajd | Hi , I searched google and i think you should install the vue coffee plugin:
```
vue-cli add coffee
```
my [ reference ](https://stackoverflow.com/questions/54332996/coffee-lang-in-vue-cli-3) is for vue-cli 3 but i guess it also works on vue3 | 2021-10-31T18:07:41 | 2021-10-31T18:07:41 | {} | CONTRIBUTOR |
vuejs | core | 958,894,494 | 4,894 | posva | Vue and it's `@vue/*` published packages are still compatible with the same versions of Node. This change is just for the collaborators of the repo. | 2021-11-03T10:48:28 | 2021-11-03T10:48:28 | {} | MEMBER |
vuejs | core | 953,472,088 | 4,866 | 651778286 | @posva Thank you for your reply, but this plan did not work.
```
<component :is="currentTabComponent" :ref="currentTabRef"></component>
```
```
const currentTabRef = computed(() => currentTab.value + '_View')
```
```
const Home_View = ref(null)
const Posts_View = ref(null)
const Archive_View = ... | 2021-10-28T03:30:50 | 2021-10-28T03:30:50 | {} | NONE |
vuejs | core | 955,690,935 | 4,877 | PayteR | @posva could you at least write me a hint on how to fix this or at least make ignore this errors?
If I'm right that prettier check this after compilation-time, is even possible to fix this? | 2021-10-31T12:27:09 | 2021-10-31T12:27:09 | {} | NONE |
vuejs | core | 957,927,541 | 4,887 | LinusBorg | that would be something to work out in the correct repository, where we already have an open issue for this - it's a problem with a dependency:
https://github.com/vuejs/vue-cli/issues/6716
| 2021-11-02T16:37:24 | 2021-11-02T16:37:40 | {
"+1": 1
} | MEMBER |
vuejs | core | 958,791,265 | 4,893 | posva | You should use a `ref()` instead so you [can replace the whole value](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgb25Nb3VudGVkIH0gZnJvbSAndnVlJ1xuXG5jb25zdCBteUxpc3QgPSByZWYoW3tcbiAgbmFtZTogJ3ZiJ1xufV0pXG5cbm9uTW91bnRlZCgoKSA9PiB7XG4gIG15TGlzdC52YWx1ZSA9IFt7bmFtZTogJ2Zpc2gnfV1cbn0pXG4... | 2021-11-03T09:48:24 | 2021-11-03T09:48:24 | {} | MEMBER |
vuejs | core | 958,943,660 | 1,120 | mehdi-aouadi | Actually I am using vue@3.2.20 with vue/compat@3.2.20 with compatConfig MODE=2 and I am facing the same issue.
I will try to create a reproduction sandbox.
Thanks | 2021-11-03T11:29:30 | 2021-11-03T11:29:30 | {
"+1": 1
} | NONE |
vuejs | core | 953,773,524 | 4,868 | RorzGonzalez | I have create a repo of the setup and description of the errors.
Specifically the Login1 and Login2 pages provide default null prop values using the two different styles.
The readme explains
https://github.com/CamdenGonzalez/vue-inertia-typescript-laravel | 2021-10-28T11:55:09 | 2021-10-28T11:55:09 | {} | NONE |
vuejs | core | 954,102,473 | 4,874 | LinusBorg | I can't remember when I last needed that. Though I can remember that I did use a wrapper component for such a thing once. | 2021-10-28T18:38:46 | 2021-10-28T18:38:46 | {
"+1": 1,
"-1": 6
} | MEMBER |
vuejs | core | 954,362,813 | 4,333 | ralfsqual | @mariusa Have you solved it? I encountered just now, - - er. remove the comments . 3Q | 2021-10-29T02:39:27 | 2021-10-29T02:45:57 | {} | NONE |
vuejs | core | 956,112,458 | 4,880 | LinusBorg | you need to provide the quotation marks in the binding's string value
[playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IHsgcmVmIH0gZnJvbSAndnVlJ1xuY29uc3QgdGVzdCA9IHJlZignXCJ0ZXN0XCInKVxuY29uc3QgdGVzdENvbG9yID0gcmVmKCdncmVlbicpXG5jb25zdCB0ZXN0QmFja2dyb3VuZCA9IHJlZignYmx1ZScpXG48L3Njc... | 2021-11-01T10:23:19 | 2021-11-01T10:23:19 | {
"+1": 3,
"hooray": 3
} | MEMBER |
vuejs | core | 957,055,201 | 4,871 | gcxfd | why not convert coffee to js first , then analyze the AST ？ | 2021-11-02T02:59:04 | 2021-11-02T02:59:04 | {} | NONE |
vuejs | core | 957,091,096 | 4,716 | yyx990803 | fixed by 3ca8317 | 2021-11-02T04:23:50 | 2021-11-02T04:23:50 | {
"hooray": 1
} | MEMBER |
vuejs | core | 953,539,350 | 4,869 | ygj6 | Duplicate of #4397 | 2021-10-28T06:25:31 | 2021-10-28T06:25:31 | {} | MEMBER |
vuejs | core | 953,989,817 | 4,866 | Bigfish8 | It seems can not compile the template inside setup when there exists dynamic ref... | 2021-10-28T16:06:41 | 2021-10-28T16:06:41 | {} | CONTRIBUTOR |
vuejs | core | 954,096,303 | 4,845 | 07akioni | > It is Intentional? Just in my option,v-show means element actually render.It seems reasonable if it trigger the enter hooks.
I don't think so. Enter is transition's enter, not the child element's enter. | 2021-10-28T18:29:56 | 2021-10-28T18:30:23 | {} | CONTRIBUTOR |
vuejs | core | 957,608,899 | 4,885 | 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). | 2021-11-02T13:46:12 | 2021-11-02T13:46:12 | {} | MEMBER |
vuejs | core | 958,096,570 | 4,888 | posva | Thank you but the read are intentional. The dummy variables not having a type is probably just for convenience | 2021-11-02T19:20:43 | 2021-11-02T19:20:51 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.