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 | 792,283,808 | 3,380 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). This questions seems to be related to vue-18n and not Vue | 2021-03-07T13:59:46 | 2021-03-07T13:59:46 | {} | MEMBER |
vuejs | core | 793,006,340 | 1,925 | gearboxdesign | Hi all,
I am also in need of an expected ETA on the IE11 support. For the exact reasons mentioned above, we have a need to cater for certain user groups in such organisations and institutions, so despite the recent(ish) announcements from Microsoft we still need to have this base covered.
We are (possibly a littl... | 2021-03-08T19:17:52 | 2021-03-08T19:17:52 | {
"+1": 8
} | NONE |
vuejs | core | 793,533,504 | 3,394 | posva | Maybe https://github.com/vuejs/vue-next/pull/3395 is a better alternative | 2021-03-09T08:21:27 | 2021-03-09T08:21:27 | {} | MEMBER |
vuejs | core | 793,564,128 | 3,367 | gertqin | I think what is needed is something like this
```ts
import OtherComponent from "./OtherComponent.vue";
const myComponent = defineComponent({
components: {
OtherComponent
},
setup() {
// ...
}
})
type ExtractLocalComponents<T> = T extends DefineComponent<
any,
any,
...
infer LC... | 2021-03-09T08:47:16 | 2021-03-09T08:49:07 | {} | NONE |
vuejs | core | 794,243,801 | 3,270 | ovidiuc | Not sure if this is related, but if you have a child component named `ChildComponent` and setup data named `childComponent` (so not the same name, but the first letter lowercased) the child also doesn't render. I'm leaving here the console warnings I get, so people can find this bug when searching for a solution:
``... | 2021-03-09T18:03:52 | 2021-03-09T19:18:52 | {} | NONE |
vuejs | core | 794,510,751 | 3,399 | johnsoncodehk | Thanks for this update, custom directives IntelliSense and Type-Checking is coming!
We also need `ComponentCustomComponents` (global components). Similar to `JSX.IntrinsicElements` but actually it's use for handle different problem. | 2021-03-09T21:57:06 | 2021-03-09T21:57:06 | {
"+1": 6,
"heart": 1
} | MEMBER |
vuejs | core | 792,533,361 | 3,382 | mixalbl4-127 | @Kingbultsea
The 3rd example is definitely a bug, since the SAME code written in the traditional style through <template> and through the Composition API behaves differently (the traditional one does not add style at all, but the Composition API adds it to the first element)
In addition, if you replace 1 element wit... | 2021-03-08T07:21:15 | 2021-03-08T07:21:37 | {} | NONE |
vuejs | core | 792,566,574 | 3,382 | Kingbultsea | try ``` if (isSecond.value) res.push(h("div", { class: "tst", key: 1 }, "second")); ``` | 2021-03-08T08:17:27 | 2021-03-08T08:17:27 | {} | CONTRIBUTOR |
vuejs | core | 793,032,750 | 3,390 | posva | <img width="729" alt="Screenshot 2021-03-08 at 20 57 39" src="https://user-images.githubusercontent.com/664177/110374398-ed2fbd80-8050-11eb-9a5c-807f3748e528.png">
| 2021-03-08T19:57:56 | 2021-03-08T19:57:56 | {} | MEMBER |
vuejs | core | 795,118,952 | 2,738 | JensDll | @kuanyui You will still need to type the validators parameter:
```ts
size: {
type: String,
default: 'md',
validator: (x: string) => { ... }
}
``` | 2021-03-10T09:04:57 | 2021-03-10T09:04:57 | {} | CONTRIBUTOR |
vuejs | core | 795,124,354 | 2,738 | kuanyui | > @kuanyui You will still need to type the validators parameter:
>
> ```ts
> size: {
> type: String,
> default: 'md',
> validator: (x: string) => { ... }
> }
> ```
@JensDll Wow magic it works! So fantastic! Thanks! | 2021-03-10T09:09:35 | 2021-03-10T09:09:35 | {} | NONE |
vuejs | core | 790,631,452 | 3,345 | posva | I would say yes: the user should manually take care of them since by default one wants to propagate such modifiers with `v-attrs` so you should define the prop like @HcySunYang proposed.
@HcySunYang unless you have any other idea, I think we can close this one | 2021-03-04T13:50:25 | 2021-03-04T13:50:25 | {} | MEMBER |
vuejs | core | 790,634,013 | 3,359 | yaquawa | @posva
Thanks! looks like `document.activeElement` solution is more cleaner than mine.
Or maybe we can create a component something like this?(which similar to the `<keep-alive>` element)
```vue
<KeepFocus>
...
</KeepFocus>
``` | 2021-03-04T13:54:17 | 2021-03-04T13:54:36 | {} | NONE |
vuejs | core | 791,148,986 | 3,364 | lafpub | Thank you for your timely reply, for some reason, I can't pay attention to github very often. If you think this feature is good and helpful, you can submit rfcs between them between them. Thank you very much. | 2021-03-05T04:42:36 | 2021-03-05T04:42:36 | {} | NONE |
vuejs | core | 791,975,513 | 3,378 | LinusBorg | Please provide a demo of the behaviour your are having problem with instead of relying on us knowing what exactly you refer to.
Also add the boilerplate you are now fighting to get a feeling of what you experience etc.
Sidenote: a good time for a breaking change would have been in the halb year of beta/rc release... | 2021-03-06T15:50:31 | 2021-03-06T15:59:16 | {
"confused": 1
} | MEMBER |
vuejs | core | 795,169,379 | 727 | takechihorn | Hi @posva Thank you for your response, ok i'll send my question to the forum, and StackOverflow. | 2021-03-10T09:49:48 | 2021-03-10T09:49:48 | {} | NONE |
vuejs | core | 791,138,072 | 3,364 | Kingbultsea | https://github.com/vuejs/rfcs | 2021-03-05T04:08:29 | 2021-03-05T04:08:29 | {} | CONTRIBUTOR |
vuejs | core | 791,155,464 | 3,364 | HcySunYang | Hi @lafpub , first of all, 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). If you are requesting new features... | 2021-03-05T05:02:10 | 2021-03-05T05:02:10 | {} | MEMBER |
vuejs | core | 791,400,024 | 3,368 | edison1105 | ur reproduction link shows 403 error. | 2021-03-05T12:51:38 | 2021-03-05T12:51:38 | {} | MEMBER |
vuejs | core | 791,879,259 | 3,371 | edison1105 | you should
```javascript
const register = (isVisible) => {
console.log("useRelocatableParent - register");
const index = nextIndex++;
// like this
registeredEntries.value[index] = { isVisible: isVisible.value };
return index;
};
``` | 2021-03-06T05:53:11 | 2021-03-06T05:53:11 | {} | MEMBER |
vuejs | core | 791,990,153 | 3,378 | DamianGlowala | An example scenario:
1) There is an input field with v-model.number modifier applied.
2) Its initial value binded to data property is null.
3) I type a random number and then decide to erase it so that the input is empty (as it was initially).
4) **The problem here is that what the empty input value defaults to i... | 2021-03-06T17:02:28 | 2021-03-06T17:04:27 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 788,968,499 | 3,183 | LinusBorg | how exaxctly? I use eslint and prettier fine with this. | 2021-03-02T14:58:03 | 2021-03-08T12:09:00 | {} | MEMBER |
vuejs | core | 793,027,984 | 3,390 | kospl | @posva I know, shouldn't there be **render** error if a typo occurs? That was basically issue report meaning. | 2021-03-08T19:50:22 | 2021-03-08T19:50:22 | {} | NONE |
vuejs | core | 794,944,855 | 3,183 | HcySunYang | I rethinked this with https://github.com/vuejs/vue-next/issues/3249. Why do we need to expose the imports from `vue`? maybe it was a mistake? I know that build-in components must be exposed, like `Teleport`:
```js
<script setup>
import { Teleport } from 'vue'
</script>
```
output:
```js
export default {
... | 2021-03-10T06:12:55 | 2021-03-10T06:12:55 | {
"+1": 1
} | MEMBER |
vuejs | core | 792,421,022 | 3,308 | dhruvkelawala | Waiting for this commit to be merged 👀 | 2021-03-08T02:42:53 | 2021-03-08T02:42:53 | {
"+1": 2
} | NONE |
vuejs | core | 793,099,634 | 3,391 | Lilja | I'm not sure why it's a problem for the component to be re-rendered. Would you care to elaborate?
I would expect that if I change a reactive value that it would be changed throughout the application. | 2021-03-08T21:40:23 | 2021-03-08T21:40:23 | {} | NONE |
vuejs | core | 794,944,021 | 3,401 | 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-10T06:12:01 | 2021-03-10T06:12:01 | {} | NONE |
vuejs | core | 791,892,227 | 3,371 | plehnen | @edison1105 this would loose reactivity. I need to pass computed refs, which will update as soon as their state change. Do you mean I should watch for changes and then call a injected function again each time? I thought the benifit of exposing computed is that I don't need to do that anymore. (This would still not expl... | 2021-03-06T08:00:43 | 2021-03-06T08:00:43 | {} | NONE |
vuejs | core | 791,905,160 | 3,368 | edison1105 | I think this is intended in DEV,if errorCapturedHooks or appErrorHandler is not configured.
and the `update()` of component still in the `queue`. | 2021-03-06T09:56:19 | 2021-03-06T11:40:16 | {} | MEMBER |
vuejs | core | 793,040,024 | 3,390 | kospl | @posva I thought Vue shows line number of error or something (in full dev mode) maybe I was wrong, sorry | 2021-03-08T20:08:16 | 2021-03-08T20:08:16 | {} | NONE |
vuejs | core | 793,983,320 | 3,089 | posva | @HcySunYang Should this be closed now that https://github.com/vuejs/vue-next/pull/3089 is merged? | 2021-03-09T14:39:25 | 2021-03-09T14:39:25 | {} | MEMBER |
vuejs | core | 791,113,094 | 3,352 | fatbone008 | I've provide two project to reproduce, May be I should put merge them into one.
And thanks for you proposal. I would check the two issues. | 2021-03-05T02:55:01 | 2021-03-05T02:55:01 | {} | NONE |
vuejs | core | 791,121,439 | 3,362 | Kingbultsea | ```bool``` is set to false by default.
is this about #3337 ? | 2021-03-05T03:18:24 | 2021-03-05T03:18:24 | {} | CONTRIBUTOR |
vuejs | core | 791,123,062 | 2,364 | werfei | I have the same problem | 2021-03-05T03:23:10 | 2021-03-05T03:23:10 | {} | NONE |
vuejs | core | 791,151,294 | 3,361 | HcySunYang | See https://codesandbox.io/s/recursive-emit-bug-forked-weqfy?file=/src/components/RecursiveEvent.vue | 2021-03-05T04:49:32 | 2021-03-05T04:49:32 | {
"heart": 3
} | MEMBER |
vuejs | core | 791,160,651 | 3,359 | HcySunYang | Focus management is complex at some level, especially in terms of accessibility. We cannot maintain focus during the patching phase, as this may go against the user’s wishes(the patching is performed in the microtask queue). For the so-called `<KeepFocus>`, it can still be implemented on the user side, and the user has... | 2021-03-05T05:16:26 | 2021-03-05T05:16:26 | {
"+1": 1
} | MEMBER |
vuejs | core | 791,887,260 | 3,368 | wzhzzmzzy | sorry, here is it.
https://codepen.io/wzhzzmzzy/pen/poNZOMM | 2021-03-06T07:07:33 | 2021-03-06T07:07:33 | {} | NONE |
vuejs | core | 788,787,427 | 3,183 | yoyoys | This workaround breaks eslint-prettier, so weird.
> It's a Bug in the compiler that doesn't differentiate between type exports and runtime exports.
>
> As a workaround, you can use `import type { Ref } from 'vue'` to import types explicitly as types.
| 2021-03-02T10:05:49 | 2021-03-08T12:08:54 | {} | NONE |
vuejs | core | 794,761,864 | 3,399 | HcySunYang | > We also need ComponentCustomComponents (global components). Similar to JSX.IntrinsicElements but actually it's use for handle different problem.
@johnsoncodehk ~~I think this is worth putting in a new issue for tracking, with as detailed information as possible. 😁~~
Edit: After reviewing the code, I think it c... | 2021-03-10T02:31:42 | 2021-03-10T02:57:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 856,906,417 | 3,909 | posva | Why? | 2021-06-08T16:14:15 | 2021-06-08T16:14:15 | {} | MEMBER |
vuejs | core | 857,322,833 | 2,116 | scriptsman | > anyway, the behaviour is consistent with objects and arrays, at least:
>
> ```js
> /* REACTIVE */
> const obj = reactive({})
> const array = reactive([])
>
> watch(obj, cb) // implicit deep: true
> watch(array, cb) // implicit deep: true
>
> obj.newProp = 'foo' // => triggers cb
> array.push('foo') // =... | 2021-06-09T02:30:19 | 2021-06-09T02:30:19 | {} | NONE |
vuejs | core | 857,476,673 | 3,919 | posva | Thank you but this one is different as it avoids the spread of an empty array and is probably intentional | 2021-06-09T07:57:53 | 2021-06-09T07:57:53 | {} | MEMBER |
vuejs | core | 857,704,694 | 3,899 | edison1105 | - Windows
- Google Chrome 已是最新版本
- 版本 91.0.4472.77（正式版本） （64 位）
works fine. | 2021-06-09T13:41:33 | 2021-06-09T13:41:33 | {} | MEMBER |
vuejs | core | 858,591,293 | 3,934 | LinusBorg | I disagree. There's been an explicit change in Vue 3 that you can only use `is` in combination with `<component>`, so that user-defined components can use `is` as an attribute name.
The behaviour in 3.1 is a side effect of the changes introduced for the compat build, as in Vue 2, `is` could be used without `<compone... | 2021-06-10T12:46:38 | 2021-06-10T17:29:21 | {} | MEMBER |
vuejs | core | 859,536,330 | 3,931 | posva | This is expected: you are responsible for the data used in your application and it being the same on server and client. In this scenario, the value should be serialized somewhere on the page for the client to pick it up and properly hydrate. | 2021-06-11T12:10:03 | 2021-06-11T12:10:03 | {} | MEMBER |
vuejs | core | 860,033,325 | 1,285 | winixt | > Yeah we should formalize that - up to this point we've been pretty liberal on the use of ES2015+ features, so there might be a few cases that should be corrected.
tsconfig compiler target is `esnext`，if code has latest es syntax，browser compatibility will become a big issue?
and if it won't, why? | 2021-06-12T10:20:58 | 2021-06-12T10:20:58 | {} | NONE |
vuejs | core | 861,086,868 | 1,228 | mgdodge | Unfortunately, this is still an issue. The output from my recent conversion from vue-cli to vite:
```
node_modules/@vue/runtime-core/dist/runtime-core.d.ts:1028:6 - error TS2748: Cannot access ambient const enums when the '--isolatedModules' flag is provided.
1028 [BooleanFlags.shouldCast]?: boolean;
... | 2021-06-15T00:46:44 | 2021-06-15T00:46:44 | {} | NONE |
vuejs | core | 857,430,725 | 3,916 | zhangenming | 
Why is it OK for my locally, I tried several times...
thanks... | 2021-06-09T06:46:13 | 2021-06-09T06:46:13 | {} | CONTRIBUTOR |
vuejs | core | 857,718,757 | 3,899 | zhangenming | > * Windows
> * Google Chrome 已是最新版本
> * 版本 91.0.4472.77（正式版本） （64 位）
>
> works fine.
Microsoft Edge
版本 91.0.864.41 (官方内部版本) (64 位)
did you open dev tools?
and i can reproduce at inPrivate Mode | 2021-06-09T13:59:28 | 2021-06-09T13:59:28 | {} | CONTRIBUTOR |
vuejs | core | 857,832,566 | 3,911 | yyx990803 | Sorry but that's not a valid reproduction and there is not enough info for us to do anything. | 2021-06-09T16:03:51 | 2021-06-09T16:03:51 | {} | MEMBER |
vuejs | core | 858,035,514 | 906 | r4pt0s | After a while of investitgation it a bit further, it turns out, that comments are messing the functionality up.
I'm not sure if this is happening in your case as well @dacxjo , but for me the issue was a comment before the first element within the template
```
<template>
<main>
<!-- Introduction -->
... | 2021-06-09T19:31:43 | 2021-06-09T19:32:29 | {
"+1": 4,
"heart": 4,
"hooray": 4,
"rocket": 2
} | NONE |
vuejs | core | 859,269,126 | 3,938 | yaquawa | @Justineo thanks for replying!
I didn't expect that, so what would be the workaround for my usecase? | 2021-06-11T05:08:41 | 2021-06-11T05:08:58 | {} | NONE |
vuejs | core | 859,348,295 | 3,926 | illumi520 | nice
| 2021-06-11T07:28:04 | 2021-06-11T07:28:04 | {} | NONE |
vuejs | core | 859,463,509 | 3,936 | jaulz | @posva actually, I traced it down to the code which I linked. | 2021-06-11T09:59:04 | 2021-06-11T09:59:04 | {} | CONTRIBUTOR |
vuejs | core | 859,633,382 | 3,932 | posva | This doesn't seem to be related to Vue as it can be reproduced [without using `reactive` by omitting the `return` statement in the `set` trap](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aDE+PC9oMT5cbjwvdGVtcGxhdGU+XG5cbjxzY3JpcHQ+XG4gIFwidXNlIHN0cmljdFwiO1xuICBmdW5jdGlvbiBoYW5kbGVyUHJveHkodGFyZ2V0KSB7XG... | 2021-06-11T14:46:08 | 2021-06-11T14:46:08 | {} | MEMBER |
vuejs | core | 859,766,527 | 1,324 | andresberrios | There is a problem with the previous solutions. Initializing the `ref(initialValue)` with `fn(original.value)` will cause the `ref` function to actually unwrap the ref (in case `MT` was indeed a ref) and also unwrap any refs that might exist in nested properties of `MT`. Casting it to `as Ref<MT>` would be lying to the... | 2021-06-11T18:33:14 | 2021-06-11T19:17:30 | {
"+1": 9
} | NONE |
vuejs | core | 862,196,840 | 3,758 | oliverzy | 
| 2021-06-16T09:17:33 | 2021-06-16T09:17:33 | {} | NONE |
vuejs | core | 856,803,184 | 3,884 | yyx990803 | As the comment suggests, it *is* intentionally testing the side effect of **reading** `__proto__`. See https://github.com/vuejs/vue-next/issues/1107 | 2021-06-08T14:11:06 | 2021-06-08T14:11:06 | {} | MEMBER |
vuejs | core | 857,829,261 | 3,915 | yyx990803 | As pointed out in https://github.com/vuejs/vue-next/issues/3910#issuecomment-857365239, regex seems to be insufficient here.
I implemented a simple lexer in https://github.com/vuejs/vue-next/commit/bc100c5c48b98b6e2eabfa1d50e0d3099ea2a90d | 2021-06-09T15:59:30 | 2021-06-09T15:59:30 | {} | MEMBER |
vuejs | core | 858,483,465 | 3,932 | Picknight | It seems Safari's bug, It works fine at Safari 14.0.3 (macOS - 10.15.7) | 2021-06-10T09:54:23 | 2021-06-10T09:55:42 | {} | CONTRIBUTOR |
vuejs | core | 858,578,906 | 3,934 | posva | I would say this is expected as `is` is a special attribute and shall not be used as a prop. Otherwise [it would still not work with a dynamic `is`](https://vue-next-template-explorer.netlify.app/#%7B%22src%22%3A%22%3Cform-input%20%3Ais%3D%5C%22oops%5C%22%2F%3E%5Cn%22%2C%22options%22%3A%7B%22mode%22%3A%22module%22%2C%2... | 2021-06-10T12:29:29 | 2021-06-10T12:29:29 | {} | MEMBER |
vuejs | core | 859,498,120 | 3,939 | LinusBorg | Hello!
Thank your for your interest in this project.
However, your issue is a usage/support question, and the issue tracker is reserved exclusively for bug reports and feature requests (as outlined in our [Contributing Guide](https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md)).
We encourage you to ... | 2021-06-11T10:56:06 | 2021-06-11T10:56:06 | {} | MEMBER |
vuejs | core | 858,047,683 | 906 | r4pt0s | Awesome. I'm glad that it worked for you as well 😀 @dacxjo | 2021-06-09T19:51:31 | 2021-06-09T19:51:31 | {} | NONE |
vuejs | core | 858,676,442 | 3,811 | ChenWeihua123 | 同样的问题我也遇到了
windows 10
vue 3.1
node 14.15.0 | 2021-06-10T14:34:45 | 2021-06-10T14:34:45 | {} | NONE |
vuejs | core | 861,155,916 | 3,948 | aantipov | @posva Thank you a lot for the workaround 👍 I didn't know I can set `type` to `null`. It gives me what I wanted to achieve.
Yet, having built-in support for that would of course be nice!
Ok, I see the problem with `[whatever, null]` as `null` is already used and has a different meaning.
Then what about the s... | 2021-06-15T04:16:57 | 2021-06-15T04:16:57 | {
"+1": 18
} | NONE |
vuejs | core | 861,509,955 | 3,958 | posva | It seems like it's treating the function as an async component (Vue 2 syntax) | 2021-06-15T13:43:21 | 2021-06-15T13:43:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 857,316,705 | 3,909 | zhangenming | > Why?
These three lines are sure to execute without any errors,
So it's not necessary use `try`.
or put `cleanup(effect)` into the try statement,inside
Anyway, these four lines should with same treatment
Is it or not? | 2021-06-09T02:12:30 | 2021-06-09T02:12:30 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 857,602,143 | 3,920 | posva | Please open a new issue with a boiled down repro with no external deps (like element-plus) and in English | 2021-06-09T11:05:13 | 2021-06-09T11:05:20 | {} | MEMBER |
vuejs | core | 857,735,288 | 3,599 | JarvisH | Any update on when this will be merged? | 2021-06-09T14:19:30 | 2021-06-09T14:19:30 | {} | NONE |
vuejs | core | 858,040,859 | 906 | dacxjo | @r4pt0s i just can't believe it, what strange behaviour, i just removed the comments in my template and now, as you say, it's working as expected! | 2021-06-09T19:40:16 | 2021-06-09T19:40:24 | {} | NONE |
vuejs | core | 858,487,476 | 3,932 | hcg1023 | > It seems Safari's bug, It works fine at Safari 14.0.3 (macOS - 10.15.7)
14.X dont have a problem, 13. X has this problem, is there no way from the Vue except to upgrade Safari? I suspected it was a Proxy problem twice, but it turned out not to be the case. It only happens when reactive is used | 2021-06-10T09:59:58 | 2021-06-10T10:00:40 | {} | CONTRIBUTOR |
vuejs | core | 858,730,809 | 3,936 | LinusBorg | We understand that providing a reproduction isn't always easy and even close to impossible in some rare edge cases.
That being said, you can surely provide a bit more than this?
* code in question
* "compat" - meaning this is a Vue 2 component runnning in compat mode? or aready moved to Vue 3?
* whats the comp... | 2021-06-10T15:41:31 | 2021-06-10T15:42:34 | {} | MEMBER |
vuejs | core | 859,047,835 | 3,936 | leopiccionia | > I think it's related to this piece of code in my dependencies
I don't know if it helps, but have you tried replacing `@inertiajs/inertia-vue` with `@inertiajs/inertia-vue3`? | 2021-06-10T20:43:07 | 2021-06-10T20:43:07 | {} | CONTRIBUTOR |
vuejs | core | 859,546,529 | 3,940 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-06-11T12:28:10 | 2021-06-11T12:28:10 | {} | CONTRIBUTOR |
vuejs | core | 860,466,204 | 3,948 | posva | You can use a `validator`: `(v: any) => typeof v === 'string' || v === null` and remove the `type`:
```ts
category: {
required: true,
type: null as unknown as PropType<string | null>,
validator: (v: any) => typeof v === 'string' || v === null,
}
```
<img width="526" alt="Screenshot... | 2021-06-14T07:49:35 | 2021-06-14T07:49:35 | {
"heart": 3
} | MEMBER |
vuejs | core | 860,878,944 | 3,951 | LinusBorg | Such aliases are a build time feature. They can not work in the runtime compiler because the compiler doesnt know about them - that's the build tool's job (here:vite) | 2021-06-14T17:57:50 | 2021-06-14T17:57:50 | {} | MEMBER |
vuejs | core | 861,407,474 | 3,956 | 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-06-15T11:08:37 | 2021-06-15T11:08:37 | {} | MEMBER |
vuejs | core | 862,109,888 | 3,914 | wenfangdu | I've found a pretty good workaround for this:
Before:
```html
<!-- `v-cascader` is a multi-root component -->
<!-- 👇 focus an inner input element currently is not possible -->
<v-cascader v-focus></v-cascader>
```
After:
```html
<!-- `v-form-item` is a single-root component -->
<!-- put `v-foc... | 2021-06-16T07:09:23 | 2021-06-16T07:09:23 | {} | NONE |
vuejs | core | 856,794,108 | 3,876 | dependabot[bot] | Superseded by #3908. | 2021-06-08T13:59:58 | 2021-06-08T13:59:58 | {} | CONTRIBUTOR |
vuejs | core | 856,795,276 | 3,877 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 42.36 KB (0%) |
| runtime-dom.global.prod.js | 28.05 KB (0%) |
| size-check.global.prod.js | 16.8 KB (0%) | | 2021-06-08T14:01:23 | 2021-06-08T14:01:23 | {} | NONE |
vuejs | core | 856,880,330 | 3,891 | caxerx | Same here, I got the same error on `@vue/compiler-sfc` `3.1.0` and `3.1.1`
```
VueCompilerError: v-model value must be a valid JavaScript member expression.
v-model="translations['zh-CN'][propName]"
``` | 2021-06-08T15:40:04 | 2021-06-08T15:40:04 | {} | NONE |
vuejs | core | 857,345,845 | 3,910 | HcySunYang | Made a PR | 2021-06-09T03:35:31 | 2021-06-09T03:35:31 | {} | MEMBER |
vuejs | core | 857,625,977 | 3,921 | huangxiaochang | Yes, you are right， it works fine in dev and there be a problems only in production env.
I aslo think it's a vue-loader bug, so i should submit this issue to vue-loader?
At 2021-06-09 18:18:16, "edison" ***@***.***> wrote:
works fine in dev see :sfc demo
I think it's a vue-loader bug.
—
You are receiving this bec... | 2021-06-09T11:45:57 | 2021-06-09T11:45:57 | {} | NONE |
vuejs | core | 858,740,624 | 3,936 | jaulz | Thanks for the quick response! So, the code is actually part of a larger code base and I just switched to `vue@3.1.1` using the compatibility mode (via webpack alias). Most of the code base consists of vue2 components but anyway I wanted to try the new compatibility version.
I thought it's maybe worth to open this i... | 2021-06-10T15:53:31 | 2021-06-10T15:53:31 | {} | CONTRIBUTOR |
vuejs | core | 859,460,479 | 3,936 | posva | Thanks for the report, if you manage to boil it down, please open a new issue so we can look further. | 2021-06-11T09:53:44 | 2021-06-11T09:53:44 | {} | MEMBER |
vuejs | core | 859,946,432 | 3,944 | chemicalcrux | Yeah, I had a feeling it wasn't very common practice.
I (ab)used the behavior almost exclusively with a language system I'd developed for a game. The vast majority of the usage is in string interpolation, so it's not like too many things broke. It just made for quite a mess when I first got the project to compile, h... | 2021-06-11T22:52:55 | 2021-06-11T22:52:55 | {} | NONE |
vuejs | core | 856,801,793 | 3,901 | yyx990803 | I don't have this error locally and the build type checks work just fine. It seems to be an issue in the version of TS you are using. | 2021-06-08T14:09:23 | 2021-06-08T14:09:23 | {} | MEMBER |
vuejs | core | 857,714,010 | 3,923 | yyx990803 | Looks like an easy fix (it should be `defaultValue.call(instance.proxy)`) - PR welcome! | 2021-06-09T13:53:34 | 2021-06-09T13:53:34 | {} | MEMBER |
vuejs | core | 857,718,608 | 3,923 | eunjae-lee | Alright. PR coming! | 2021-06-09T13:59:15 | 2021-06-09T13:59:15 | {} | CONTRIBUTOR |
vuejs | core | 857,943,182 | 3,927 | LinusBorg | I'm a bit unsure what you are trying to achieve here.
`<script setup>` is definitely not designed to export default a functional TSX component.
It's designed to work with a template. for the most part, it exists so you can have an authoring experience similar to that of a .tsx file - no need to register component... | 2021-06-09T18:20:19 | 2021-06-09T18:20:19 | {} | MEMBER |
vuejs | core | 858,674,015 | 3,935 | LinusBorg | I'd be suprised if this was "working" in 3.0.8, since this behaviour is an explicitly documented breaking change in 3.0.0:
https://v3.vuejs.org/guide/migration/attrs-includes-class-style.html#migration-strategy
If this "worked" in 3.0.8, that would have been a bug. | 2021-06-10T14:31:47 | 2021-06-10T14:31:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 859,265,251 | 3,938 | Justineo | It is expected. You don't get the `change` event when programmatically changing the values of checkboxes. You only get it after user interaction. | 2021-06-11T04:59:17 | 2021-06-11T04:59:17 | {} | MEMBER |
vuejs | core | 859,274,561 | 3,938 | lidlanca | ```js
watch(checked, ()=>console.log("changed"))
``` | 2021-06-11T05:21:25 | 2021-06-11T05:21:25 | {} | CONTRIBUTOR |
vuejs | core | 859,270,837 | 3,933 | lidlanca | bug related to fix made for https://github.com/vuejs/vue/issues/6566
https://github.com/vuejs/vue-next/blob/870f2a7ba35245fd8c008d2ff666ea130a7e4704/packages/runtime-dom/src/modules/events.ts#L118-L128
The issue is, that for browsers where the event uses the hi-res timestamp
The child window time resets/start fr... | 2021-06-11T05:12:37 | 2021-06-11T18:12:45 | {} | CONTRIBUTOR |
vuejs | core | 857,133,511 | 3,910 | LinusBorg | /cc @HcySunYang | 2021-06-08T20:53:17 | 2021-06-08T20:53:17 | {} | MEMBER |
vuejs | core | 857,365,239 | 3,910 | lidlanca | @HcySunYang
You are right the regexp approach is flawed
with the new pr this will fail.
```
isMemberExpression("a[b[c.d]][0]") => false
```
if you can't use a parser to validate the expression,due to the concern of bundling babel in browser build
perhaps change it from an error to a development warning, ... | 2021-06-09T04:35:29 | 2021-06-09T04:35:29 | {} | CONTRIBUTOR |
vuejs | core | 858,752,415 | 3,899 | Gavin-Gong | works fine after remove `debugger` or disable devtool's breakpoints.... | 2021-06-10T16:08:07 | 2021-06-10T23:09:19 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 859,355,461 | 3,937 | posva | Duplicate of https://github.com/vuejs/vue-router-next/issues/626 | 2021-06-11T07:40:34 | 2021-06-11T07:40:34 | {} | MEMBER |
vuejs | core | 861,128,369 | 3,951 | liho00 | @LinusBorg Hence, its should be a feature request for vite js or vue 3 js? It will be easier to write the code just like normal, without explicitly import each of the image path manually if i have 100 images in an array? Besides, require("imagepath") also did not work in runtime compiler. | 2021-06-15T02:48:37 | 2021-06-15T02:51:28 | {} | NONE |
vuejs | core | 861,229,841 | 3,951 | LinusBorg | I don't see a reason for a compiler feature here. This should be enough for most situations:
```js
{
template: `<img class="h-12" src="${img('./assets/logo.png')}" alt="" />`,
}
```
and define `img()` as a central helper function somewhere in your code.
If you want to continue arguing for such a feature, ... | 2021-06-15T06:53:50 | 2021-06-15T06:53:50 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.