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 | 876,168,183 | 4,078 | 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-07-08T06:30:40 | 2021-07-08T06:30:40 | {} | MEMBER |
vuejs | core | 876,643,134 | 4,082 | dsonet | I think you should use new Array (length) instead of [] for the test. | 2021-07-08T18:12:17 | 2021-07-08T18:12:17 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 877,234,409 | 4,083 | loadpixels | @skirtles-code - yes your diagnosis was correct I found the answer here last night https://github.com/vitejs/vite/issues/4089
Turns out it was because of how I was installing my library locally - if I npm pack my library and then install the resulting .tgz file it works perfectly | 2021-07-09T14:34:43 | 2021-07-09T14:34:43 | {} | NONE |
vuejs | core | 877,251,194 | 4,002 | cristijora | Getting the same issue. Unfortunately as @ilicmarko mentioned, it's super hard to debug and get more context and reproduce at smaller scale because it seems like the stack trace stops in runtime-core and vue-router. | 2021-07-09T15:00:41 | 2021-07-09T15:00:41 | {
"+1": 1
} | NONE |
vuejs | core | 877,776,279 | 3,678 | YY88Xu | hello，现在这个问题解决了吗？需要在 Vue3 中注册使用 window 的 pageshow 事件，发现也不能注册，最后怎么解决呢？ | 2021-07-11T10:29:56 | 2021-07-11T10:29:56 | {} | NONE |
vuejs | core | 879,034,098 | 1,679 | guilhermemart | I have the same problem.
Doing:
Vue.createApp({
delimiters: ['{%', '%}']
...
})
we lose all the functionalities of Vue.createApp(App)
How can we still rendering App but with delimiters changed? Or at least do something like:
Vue.createApp({
delimiters: ['{%', '%}']
...
data(){...}
**components:{ com... | 2021-07-13T12:11:34 | 2021-07-13T12:11:34 | {} | NONE |
vuejs | core | 875,633,557 | 3,618 | yyx990803 | This is technically wrong usage anyway - you should **not** store values created inside a computed getter into your actual state tree.
The reason is that objects created inside a computed getter are temporary/transient/ephemeral - every time the computed updates, new objects will be created, so they should never be ... | 2021-07-07T14:05:22 | 2021-07-07T14:06:21 | {} | MEMBER |
vuejs | core | 876,809,869 | 4,067 | lidlanca | seem like the sfc-playground "emulated" module import and is not handled "purely" by the browser.
which makes the module loading logic more complex.
if only browsers allowed imports of modules defined in inline `<script name="moduleA" type=module>` tags
then most of the issues would probably be solved.
fixi... | 2021-07-08T23:36:24 | 2021-07-08T23:36:24 | {} | CONTRIBUTOR |
vuejs | core | 876,379,215 | 4,050 | paraboul | > Thanks for the research into this @jods4 - I think it's ok for the API to be a bit unwieldy as long as it is easy to automatically generate.
>
> It isn't that much a burden for userland composition functions to ensure proper placement of `await` - in fact I'd say it's good to discourage `await` in composition func... | 2021-07-08T12:00:52 | 2021-07-09T07:24:36 | {} | CONTRIBUTOR |
vuejs | core | 877,471,002 | 4,092 | jods4 | A small post-scriptum:
I have build errors when the _consuming_ template is a script setup component.
How the component itself is declared seems irrelevant, so that probably means a `slots: { ... }` addition to classical `<script>` would keep everything consistent. | 2021-07-09T21:41:21 | 2021-07-09T21:41:21 | {} | CONTRIBUTOR |
vuejs | core | 880,010,033 | 4,117 | lidlanca | removing whitespace is an optimization and simplification process to reduce the amount of nodes vue has to deal with.
you will have to find your own workaround, there is no easy way disabling whitespace removal except by a compiler option, which effect the whole project.
```
<span>a </span>
<span>b </span>
<s... | 2021-07-14T15:53:27 | 2021-07-14T15:53:52 | {} | CONTRIBUTOR |
vuejs | core | 880,230,291 | 3,836 | yyx990803 | This would require special handling in build tool plugins as `@vue/compiler-sfc` doesn't handle src imports alone. | 2021-07-14T21:43:44 | 2021-07-14T21:43:44 | {} | MEMBER |
vuejs | core | 875,554,422 | 4,075 | posva | The warning tells you about it:
```
[Vue warn]: Failed to locate Teleport target with selector "h1". Note the target element must exist before the component is mounted - i.e. the target cannot be rendered by the component itself, and ideally should be outside of the entire Vue component tree.
at <App>
```
T... | 2021-07-07T12:16:35 | 2021-07-07T12:16:35 | {} | MEMBER |
vuejs | core | 873,891,037 | 1,791 | vertcitron | Hi everybody and @yyx990803.
We need to migrate a very large scale SSR app written in Vue 2.6 / TS to Vue 3, and our Vue 2.6 makes an heavy use of component caching to ensure the best performance.
In consequence we can't wait this feature to be added, and we need to try to implement it ourself.
Before starting, I'd ... | 2021-07-05T07:57:11 | 2021-07-09T20:00:36 | {
"+1": 8
} | NONE |
vuejs | core | 877,767,963 | 3,478 | jcppman | having the opposite (but technically the same) issue here.
There's no way to make Typescript happy currently except using the ugly `@ts-ignore`.
My Environment:
- Typescript@4.3.5
- Vue@3.1.4
Attempt 1:
```typescript
interface TodoItem {
title: string;
completed: boolean;
}
interface TodoList {
... | 2021-07-11T09:18:17 | 2021-07-11T09:31:56 | {} | NONE |
vuejs | core | 879,207,908 | 4,114 | lidlanca | https://v3.vuejs.org/guide/migration/render-function-api.html#vnode-props-format | 2021-07-13T15:56:52 | 2021-07-13T15:56:52 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 880,251,172 | 3,921 | yyx990803 | Isn't this a bug of `thread-loader` causing loader context to lose `mode` then?
Either way this is not something that can be fixed in Vue core.
/cc @sodatea | 2021-07-14T22:28:02 | 2021-07-14T22:28:02 | {} | MEMBER |
vuejs | core | 880,836,965 | 2,839 | posva | Thanks for the PR. Apparently this got fixed with https://github.com/vuejs/vue-next/commit/e2ca67b59a4de57a9bce8d3394263ba493a35a39 | 2021-07-15T16:21:50 | 2021-07-15T16:21:50 | {} | MEMBER |
vuejs | core | 880,875,916 | 4,125 | yyx990803 | Thanks for the PR, but I refactored static insertion to simpler and safer logic in c0db807844194a227f6d0dad6cc3e1e8f148770f | 2021-07-15T17:18:28 | 2021-07-15T17:18:28 | {} | MEMBER |
vuejs | core | 876,272,096 | 4,081 | Justineo | Issue 仅接受 bug 报告与新特性请求，不负责解决用法的问题，有疑问请前往[论坛](https://forum.vuejs.org/)、[StackOverflow](https://stackoverflow.com/questions/tagged/vue.js) 或者 [Discord 聊天室](https://chat.vuejs.org/) 请求帮助，谢谢。
---
请参考：https://v3.cn.vuejs.org/guide/migration/introduction.html | 2021-07-08T09:11:07 | 2021-07-08T09:11:07 | {} | MEMBER |
vuejs | core | 875,635,372 | 3,870 | Trinovantes | Vue3 cannot be prerendered
You need to either:
- Rewrite to SSR
- Delete all `<script>` tags in the `postProcess` step
- Delete all contents of your `<body>` in the `postProcess` step
- Just accept the FOUC
| 2021-07-07T14:07:29 | 2021-07-08T20:55:37 | {
"+1": 1
} | NONE |
vuejs | core | 877,797,694 | 3,678 | Bruce-Ming | @YY88Xu 那就直接在html里线注册，是由于vue router拖慢了vue3的setup时机，错过了监听触发的时机，所以才监听不到的。 | 2021-07-11T13:13:04 | 2021-07-11T13:13:04 | {} | NONE |
vuejs | core | 878,643,283 | 4,109 | posva | Please, next time consider using 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 back and open an issue if it turns out to be a bug 🙂
Remember to follow https://new-issue.vuejs.or... | 2021-07-12T22:37:00 | 2021-07-12T22:37:00 | {} | MEMBER |
vuejs | core | 880,971,027 | 3,392 | yyx990803 | According to [docs](https://v3.vuejs.org/api/application-config.html#compileroptions-comments):
> By default, Vue will remove HTML comments inside templates in production. Setting this option to true will force Vue to preserve comments even in production. **Comments are always preserved during development.**
This... | 2021-07-15T19:53:32 | 2021-07-15T19:53:32 | {} | MEMBER |
vuejs | core | 877,636,173 | 4,076 | tangjinzhou | @userquin thanks. I know we should use createApp after inject.
But If we develop some components for everyone. Our compoennts cannot give warning to user.
Maybe we can give tips `you cannot use xxx after inject` at doc. But user donot know `useRouter` `useStore` ...... was implemented by inject. | 2021-07-10T13:14:42 | 2021-07-10T13:14:42 | {} | CONTRIBUTOR |
vuejs | core | 878,432,737 | 4,003 | MarMun | No idea if related in any way but I have a [memory leak problem](https://github.com/vuejs/vue-router-next/issues/730) were each route sticks in memory on first visit.
Reproduction: https://github.com/MarMun/vue-memleak
Maybe it helps. | 2021-07-12T16:48:01 | 2021-07-12T16:49:51 | {} | NONE |
vuejs | core | 875,485,984 | 3,870 | voxtobox | @Trinovantes Hi!
So, do you resolve your issue? I’m migration from vue2 to vue3 and have the same problem with prerender spa plugin and hydration. | 2021-07-07T10:24:09 | 2021-07-07T10:24:09 | {} | NONE |
vuejs | core | 879,131,915 | 4,092 | jods4 | I don't know since when, but today I noticed that Volar is able to type slots that are inside components defined by `script setup`, when they're used in the same project.
That's super cool and a great QoL improvement ✨
It would be super-duper awesome if there was a way to couple that Volar inferrence with a way t... | 2021-07-13T14:21:01 | 2021-07-13T14:21:01 | {} | CONTRIBUTOR |
vuejs | core | 879,979,297 | 4,118 | posva | You need to use toRaw, as described in docs, to get the original object reference | 2021-07-14T15:15:02 | 2021-07-14T15:15:02 | {} | MEMBER |
vuejs | core | 880,026,295 | 4,117 | leaon4 | @lidlanca Thanks, I see.
| 2021-07-14T16:14:04 | 2021-07-14T16:14:04 | {} | CONTRIBUTOR |
vuejs | core | 877,100,227 | 4,093 | LinusBorg | ```js
export default defineComponent({
setup() {
const data = ref({ v1: 'test', v2: 'test2' })
const bind = {
// bind a var
modelValue: computed(() => data.value.v1)
}
const change = (val, key) => {
data.value[key] = val
}
return { data, bind, change }
}
})
``` | 2021-07-09T10:58:22 | 2021-07-09T10:58:22 | {} | MEMBER |
vuejs | core | 877,900,792 | 4,104 | edison1105 | I didn't reproduce the bug.
1. download your repro
2. remove `yarn.lock`
3. update both `vue` and `vue/compiler-sfc` to `3.1.4`
4. yarn
5. yarn dev
6. replace line 3 class max-w-screen-sm to max-w-screen-md and save file
works fine.
This bug has already fixed in https://github.com/vuejs/vue-next/commit/fded... | 2021-07-12T01:13:53 | 2021-07-12T01:13:53 | {} | MEMBER |
vuejs | core | 879,079,622 | 3,996 | yyx990803 | Just use `InstanceType<typeof CompA>` | 2021-07-13T13:17:00 | 2021-07-13T13:17:00 | {} | MEMBER |
vuejs | core | 879,378,980 | 4,092 | yyx990803 | I'm curious what is the real benefit of type checking generated code here - `vue-tsc` can type check `*.vue` files directly so you'd preferably use that - which works on your source code providing more accurate error locations. Then you'd use `esbuild` or transpile-only mode of TS for faster builds. Am I missing someth... | 2021-07-13T20:26:12 | 2021-07-13T20:26:12 | {} | MEMBER |
vuejs | core | 880,833,395 | 2,791 | yyx990803 | This has been fixed by e2ca67b | 2021-07-15T16:16:57 | 2021-07-15T16:16:57 | {
"hooray": 1
} | MEMBER |
vuejs | core | 875,496,594 | 4,017 | basvanmeurs | > could you please rebase your branch?
Rebase to 3.2 I suppose? Done!
| 2021-07-07T10:40:26 | 2021-07-07T10:40:31 | {} | CONTRIBUTOR |
vuejs | core | 875,647,771 | 4,065 | yyx990803 | @andrewcourtice maybe! But realisticly, something like that typically involves major rewrites (like Jason is doing) so it's unlikely to happen in the short term. We may experiment with it in the future for sure. | 2021-07-07T14:22:07 | 2021-07-07T14:22:07 | {
"+1": 4
} | MEMBER |
vuejs | core | 876,103,516 | 4,078 | replygirl | you can use a second `<script>` block to define options
```vue
<script lang=“ts”>
import { defineComponent } from ‘vue’
export default defineComponent({ name: ‘MyComponent’ })
</script>
<script setup lang=“ts”>
// …
</script>
``` | 2021-07-08T03:55:41 | 2021-07-08T03:55:41 | {} | NONE |
vuejs | core | 879,134,171 | 4,112 | Bigfish8 | yes,you are right! I will change it. | 2021-07-13T14:23:46 | 2021-07-13T14:23:46 | {} | CONTRIBUTOR |
vuejs | core | 867,533,140 | 3,995 | basvanmeurs | > Do you still plan to work on the memory-saving aspect and the dep cleanup optimizations (described by @jods4 [here](https://github.com/vuejs/vue-next/pull/2345#issuecomment-727200679))?
I actually tried to avoid set add/removes and sync them after the effect (https://github.com/Planning-nl/vue-next/commit/f8cc160a... | 2021-06-24T10:42:37 | 2021-06-24T10:44:51 | {} | CONTRIBUTOR |
vuejs | core | 871,304,017 | 4,024 | nym21 | Thanks a lot ! | 2021-06-30T11:01:20 | 2021-06-30T11:01:20 | {} | NONE |
vuejs | core | 872,062,421 | 2,195 | basvanmeurs | Besides, I think that a warning should be thrown when an effect is created outside of any effectScope:
```typescript
setup() {
fetch(...).then(() => {
watchEffect(..)
});
}
```
Notice, due to the promise, that watchEffect is executed outside of the component's effectScope (in fact: outside of *any* effe... | 2021-07-01T08:59:54 | 2021-07-01T09:12:02 | {} | CONTRIBUTOR |
vuejs | core | 867,777,012 | 3,999 | 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-24T16:23:56 | 2021-06-24T16:23:56 | {} | MEMBER |
vuejs | core | 869,126,377 | 3,414 | snltty | 这个啥时候能用上呢 | 2021-06-27T08:54:56 | 2021-06-27T08:54:56 | {} | NONE |
vuejs | core | 869,296,058 | 3,994 | hubvue | @posva hi, Do I need to solve the CI error caused by `useContext`? | 2021-06-28T02:42:10 | 2021-06-28T02:42:10 | {} | NONE |
vuejs | core | 869,414,019 | 4,011 | 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-28T07:01:28 | 2021-06-28T07:01:28 | {} | CONTRIBUTOR |
vuejs | core | 869,582,644 | 4,013 | beastrovich | I managed to actually setup a working reproduction link. That sfc playground is confusing. | 2021-06-28T10:52:24 | 2021-06-28T10:52:24 | {} | CONTRIBUTOR |
vuejs | core | 870,305,827 | 4,016 | jods4 | Sorry I did not find the duplicate (#3692 is a PR not an issue).
Glad it's already fixed! | 2021-06-29T06:57:34 | 2021-06-29T06:57:34 | {} | CONTRIBUTOR |
vuejs | core | 870,648,037 | 4,018 | 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-29T14:24:35 | 2021-06-29T14:24:35 | {} | MEMBER |
vuejs | core | 871,507,083 | 4,030 | LinusBorg | Seems not to be related to `script setup`.
https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8bWFpbj5cbiAgICA8cHJlIGNsYXNzPVwiY29kZVwiIC8+XG4gIDwvbWFpbj5cbjwvdGVtcGxhdGU+XG5cbjxzY3JpcHQgbGFuZz1cInRzXCI+XG4gIGV4cG9ydCBkZWZhdWx0IHt9XG48L3NjcmlwdD4ifQ== | 2021-06-30T15:33:13 | 2021-06-30T15:33:13 | {} | MEMBER |
vuejs | core | 871,620,561 | 4,030 | LinusBorg | Sure. But if you use a closing tag, it'd working for now, so we have a workaround until it's fixed 😊 | 2021-06-30T18:08:28 | 2021-06-30T18:08:28 | {} | MEMBER |
vuejs | core | 872,050,953 | 2,195 | basvanmeurs | @antfu Could we please expose the currently active scope as well? This would allow us to reuse the active scope in setup asyncs:
```typescript
const scope = getActiveEffectScope();
fetch(...).then(() => {
extendScope(scope, () => {
effect(() => (doubled = counter.num * 2))
})
});
... | 2021-07-01T08:43:14 | 2021-07-01T08:44:33 | {} | CONTRIBUTOR |
vuejs | core | 872,135,481 | 4,033 | posva | You are using a deep watcher, it's expensive. In prod it does take 70ms. If you don't need it (for object for examples), just use a different watcher that is more precise. You can also create multiple watchers
```js
Vue.watch(
() => [data.test, data.datalist],
(newVal, oldVal) => {
console.log('bla')
... | 2021-07-01T10:52:44 | 2021-07-01T10:52:44 | {} | MEMBER |
vuejs | core | 867,331,298 | 3,995 | basvanmeurs | > Although I'm still amazed that simple `reactive({})` call somehow got faster because of this PR
I don't think it got faster. In theory, the changes in this PR shouldn't affect it at all. That particular benchmark just gives very different result every run for some reason..
> I noticed this PR no longer use a cl... | 2021-06-24T04:48:33 | 2021-06-24T10:45:53 | {} | CONTRIBUTOR |
vuejs | core | 868,161,218 | 4,003 | wukang0718 | This demo can't replicate my problem | 2021-06-25T02:47:40 | 2021-06-25T02:47:40 | {} | NONE |
vuejs | core | 868,523,297 | 3,921 | edison1105 | I did a test, The same code with vite works fine. | 2021-06-25T14:03:45 | 2021-06-25T14:03:45 | {} | MEMBER |
vuejs | core | 869,565,937 | 4,013 | posva | @LordTerabyte The link is broken, can you fix it? | 2021-06-28T10:23:33 | 2021-06-28T10:23:33 | {} | MEMBER |
vuejs | core | 869,686,629 | 4,015 | posva | You cannot change the slots programatically, only declaratevely. Regarding your code, [you can do this](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8ZGl2PlxuICAgIDxkaXY+XG4gICAgICA8YnV0dG9uIEBjbGljaz1cInRvZ2dsZVRhcmdldFwiPlxuICAgICAgICB7e3Nob3cgPyBcImhpZGUgdGFyZ2V0XCIgOiBcInNob3cgdGFyZ2V0XCJ9fVxuICAgICAgP... | 2021-06-28T13:29:47 | 2021-06-28T13:31:16 | {} | MEMBER |
vuejs | core | 867,787,923 | 3,395 | DV8FromTheWorld | @HcySunYang Are you planning to fix this PR?
If not I will open a PR with similar changes as I am in need of this fix. | 2021-06-24T16:35:33 | 2021-06-24T16:35:33 | {} | CONTRIBUTOR |
vuejs | core | 867,796,282 | 3,998 | liamdebeasi | Please correct me if I am wrong, but I thought my original syntax is also valid? Passing a function to `defineComponent` is the same thing as passing a `setup` function according to https://v3.vuejs.org/api/global-api.html#definecomponent. This particular syntax seems to be used in Vue 3 tests implying that it is valid... | 2021-06-24T16:48:58 | 2021-06-24T16:51:56 | {} | NONE |
vuejs | core | 869,575,905 | 4,002 | ilicmarko | @posva
This has nothing to do with Quasar. I just updated our app from `3.0.10` to `3.1.2`, and routing is broken now. This is a custom app with only `vue` and `vue-router` so no framework.
It is really hard to debug as Vue is of no help :disappointed:
```
[Vue warn]: Unhandled error during execution of sch... | 2021-06-28T10:40:48 | 2021-06-28T12:31:27 | {
"+1": 2
} | NONE |
vuejs | core | 870,074,356 | 4,016 | posva | Duplicate of https://github.com/vuejs/vue-next/pull/3962 | 2021-06-28T22:02:23 | 2021-06-28T22:02:23 | {} | MEMBER |
vuejs | core | 871,379,609 | 4,027 | posva | This is because you are using the same name for the computed and prop (options). Make sure to name it differently. It works with the script setup because it allows variable shadowing while the options do not. This will make more sense if you take a look at the generated JS for both Option components | 2021-06-30T12:55:21 | 2021-06-30T12:55:21 | {
"+1": 1
} | MEMBER |
vuejs | core | 868,960,611 | 3,921 | huangxiaochang | > I did a test, The same code with vite works fine.
I am sorry, i forgot to submit the build tool.
I build the project with vue-cli4.5.12. and it have problem.
yes, it works fine with vite,
| 2021-06-26T07:12:30 | 2021-06-26T07:12:30 | {} | NONE |
vuejs | core | 869,163,642 | 3,210 | JerryYuanJ | Anyone looking at this ? | 2021-06-27T13:34:09 | 2021-06-27T13:34:09 | {} | NONE |
vuejs | core | 869,494,981 | 4,005 | m0ksem | @posva, This already works, true, but there is an issue with types. For some reason, there are not props types in the ComponentOptionsBase type.
I created code sandbox: https://codesandbox.io/s/eloquent-golick-996nz?file=/src/App.vue
 seems to be a related issue. | 2021-06-28T10:34:44 | 2021-06-28T10:34:44 | {} | CONTRIBUTOR |
vuejs | core | 869,652,966 | 3,210 | JerryYuanJ | @posva Hi, I know it's a very little one. But sometimes in small apps or some demos, we just want to add one or two to excludes/includes, so it's quite convenient to directly add strings, since we support it out of box. | 2021-06-28T12:44:41 | 2021-06-28T12:44:41 | {} | NONE |
vuejs | core | 870,020,595 | 3,740 | yyx990803 | See a slightly more efficient fix in 62c1b2f7 (avoids filter and indexOf calls) | 2021-06-28T20:33:15 | 2021-06-28T20:33:15 | {} | MEMBER |
vuejs | core | 871,394,801 | 4,017 | basvanmeurs | Note: this PR has been tested and verified in our local project which uses advanced reactivity. | 2021-06-30T13:15:13 | 2021-06-30T13:15:13 | {} | CONTRIBUTOR |
vuejs | core | 870,683,998 | 2,389 | basvanmeurs | > Problem is that weak references are a recent JS addition. They won't work in pre-2020 browsers, won't work in neither Safari nor Opera, and it's not something you can polyfill. So I suppose they're out of question here.
Safari now supports this as well. Now that IE11 support has been dropped, that only leaves Oper... | 2021-06-29T15:09:29 | 2021-07-01T07:26:54 | {} | CONTRIBUTOR |
vuejs | core | 872,035,735 | 3,910 | whitespacecode | @yyx990803 I updated to vue 3.1.2 and still get the error
`[plugin:vite:vue] v-model value must be a valid JavaScript member expression.`
My code:
`<child-component v-model="form.options[lang][index]"></child-component >`
I'm using compat build.
**temporary work around i use**
```
:value="form.options[lang][in... | 2021-07-01T08:22:24 | 2021-07-01T08:32:32 | {
"+1": 2
} | NONE |
vuejs | core | 868,036,256 | 4,002 | posva | As described in the new issue website, please open the issue on Quassar first or use the discord chat to ask questions | 2021-06-24T23:35:06 | 2021-06-24T23:35:06 | {
"-1": 1
} | MEMBER |
vuejs | core | 870,062,085 | 3,546 | yyx990803 | I don't think we should prioritize global asset registrations over local variable resolutions. Local resolution should always have higher priority.
To reduce the potential shadowing of directives (which is *way* less obvious and more likely than components), I reverted it to require the variable to have a `v` prefix... | 2021-06-28T21:37:35 | 2021-06-28T21:37:35 | {} | MEMBER |
vuejs | core | 872,076,302 | 4,032 | jacekkarczmarczyk | https://v3.vuejs.org/guide/reactivity-computed-watchers.html#watching-reactive-objects
| 2021-07-01T09:16:47 | 2021-07-01T09:16:47 | {} | CONTRIBUTOR |
vuejs | core | 867,881,484 | 3,998 | inspire22 | .native doesn't work in the compat view, so there doesn't even seem to be a workaround for this. There's not steps shown in the console at all if not using .native - just nothing fires.
FYI this breaks all of the ionic/vue system with 3.1 | 2021-06-24T19:02:32 | 2021-06-24T19:02:32 | {} | NONE |
vuejs | core | 869,149,523 | 4,008 | edison1105 | duplicate of https://github.com/vuejs/vue-next/issues/3953 | 2021-06-27T11:56:02 | 2021-06-27T11:56:02 | {} | MEMBER |
vuejs | core | 870,369,100 | 2,043 | zarub2k | I see this issue is closed but I am not seeing any conclusion on this thread. Am I missing something? I am also looking for solution to my problem. | 2021-06-29T07:58:37 | 2021-06-29T07:59:33 | {} | NONE |
vuejs | core | 871,635,281 | 3,998 | inspire22 | @posva Any tips how to get click events to fire in components we don't control with 3.1 compat? I.e. via the ionic framework. Since the removal of .native there doesn't seem to be any way to make this work. There's no console migration notices besides to remove .native - just no click events fire. I think maybe thi... | 2021-06-30T18:31:52 | 2021-06-30T18:31:52 | {} | NONE |
vuejs | core | 867,678,065 | 3,998 | liamdebeasi | Thanks! I tried that, but the click handler still does not fire. I am doing:
```html
<app-cmp v-on:click.native="onClick()">Click me!</app-cmp>
``` | 2021-06-24T14:22:28 | 2021-06-24T14:22:28 | {} | NONE |
vuejs | core | 869,010,342 | 3,921 | edison1105 | The root cause is:
`loaderContext.mode` is `undefined `in the reproduction project.
https://github.com/vuejs/vue-loader/blob/next/src/resolveScript.ts#L35
And
https://github.com/vuejs/vue-loader/blob/next/src/stylePostLoader.ts#L17
`this.mode` is `production`
so the generated name of `cssVars `is different.
... | 2021-06-26T14:20:54 | 2021-06-26T14:20:54 | {} | MEMBER |
vuejs | core | 869,175,987 | 4,008 | edison1105 | is this what you want: https://codesandbox.io/s/frosty-flower-21wge?file=/src/components/HelloWorld.vue
I'm a bit confused about your feature.
| 2021-06-27T14:51:38 | 2021-06-27T14:51:38 | {} | MEMBER |
vuejs | core | 869,494,882 | 4,012 | 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).
---
You should check this PR and the linked RFC: htt... | 2021-06-28T08:44:07 | 2021-06-28T08:44:07 | {} | MEMBER |
vuejs | core | 870,600,475 | 2,027 | mehdinourollah | For me it's because of my Axios requests ...Whenever I use an Axios (or even fetch doesn't matter) I get this warning...It doesn't vanish even with disabling devtools (So It has nothing to do with the devtools).
I used interceptors of Axios to handle some error/catch cases but I don't think it has something to do wit... | 2021-06-29T13:28:34 | 2021-06-29T13:28:34 | {
"+1": 1
} | NONE |
vuejs | core | 871,514,561 | 4,030 | jods4 | My bad! 🤣
I made that supposition based on other components in my app before I identified what the culprit was...
This bug has annoying consequences, because there are things you can't do on a fragment component, such as using directives. | 2021-06-30T15:42:50 | 2021-06-30T15:42:50 | {} | CONTRIBUTOR |
vuejs | core | 867,670,736 | 3,998 | Justineo | In Vue 2 you need to use the `.native` modifier with `v-on` bindings when the component itself is not emitting `click`. I believe the compat build is aimed to align with this behavior. | 2021-06-24T14:13:02 | 2021-06-24T14:13:02 | {} | MEMBER |
vuejs | core | 867,789,142 | 3,998 | posva | You have other warnings telling you the next steps for migration in the console, so I'm closing this.
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to ask questions! | 2021-06-24T16:37:36 | 2021-06-24T16:37:36 | {} | MEMBER |
vuejs | core | 869,218,936 | 4,009 | 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).
---
Bug reports should follow https://new-issue.vuej... | 2021-06-27T20:21:45 | 2021-06-27T20:21:45 | {} | MEMBER |
vuejs | core | 871,646,250 | 4,029 | Giwayume | I'm requesting it be added back, not listed as breaking. Maybe I'll just keep using Vue 2 forever. | 2021-06-30T18:49:39 | 2021-06-30T18:50:15 | {} | NONE |
vuejs | core | 871,664,057 | 3,998 | LinusBorg | `.native` is listed as being fully supported in compat build.
@liamdebeasi Your app is missing is the second part of the webpack config described in the migration guide - setting the compiler to compat mode:
```
config.module
.rule('vue')
.use('vue-loader')
.tap(options => {
return ... | 2021-06-30T19:18:55 | 2021-06-30T19:18:55 | {
"+1": 2
} | MEMBER |
vuejs | core | 868,871,405 | 4,005 | posva | This already works. Please use the chat or discord if you have questions! | 2021-06-25T22:55:29 | 2021-06-25T22:55:29 | {} | MEMBER |
vuejs | core | 869,179,813 | 4,008 | kooriookami | > is this what you want: https://codesandbox.io/s/frosty-flower-21wge?file=/src/components/HelloWorld.vue
> I'm a bit confused about your feature.
Yes, I mean this. It's the same value of props in setup. But I wonder why they are different.
This is the link that I got props in setup.
https://codesandbox.io/s/co... | 2021-06-27T15:16:43 | 2021-06-27T15:16:43 | {} | NONE |
vuejs | core | 871,371,888 | 4,027 | userquin | >
>
> I know that now but why does it matter if I return a property `XYZ` directly or if I spread an object with a property `XYZ`? should it work the same in both cases? Shouldn't the setup context be taken into account first when accessing properties in the template? and why it currently works differently in the r... | 2021-06-30T12:46:44 | 2021-06-30T12:46:44 | {} | MEMBER |
vuejs | core | 871,375,341 | 4,027 | userquin | ~~but you are right, not working...~~ working with:
```ts
function useOptions(props) {
const options = computed(() => props.options.map(o => ({
label: o,
value: o,
})))
return options
}
``` | 2021-06-30T12:50:46 | 2021-06-30T12:52:11 | {} | MEMBER |
vuejs | core | 871,425,291 | 4,027 | posva | The thing is: you shouldn't name a computed like an existing prop. I'm referring to these:
![Screen Shot 2021-06-30 at 15 52 57](https://user-images.githubusercontent.com/664177... | 2021-06-30T13:53:52 | 2021-06-30T13:53:52 | {
"+1": 1
} | MEMBER |
vuejs | core | 871,680,277 | 3,998 | liamdebeasi | Yeah I think the intro section threw me off with the way it was worded. I'll think of a clearer way to word it and make an issue/PR on the docs-next repo. Thanks! | 2021-06-30T19:46:46 | 2021-06-30T19:46:46 | {} | NONE |
vuejs | core | 868,156,254 | 4,003 | wukang0718 | 
| 2021-06-25T02:34:11 | 2021-06-25T02:34:11 | {} | NONE |
vuejs | core | 869,189,122 | 4,008 | LinusBorg | vnode.props only contains the props actually passed to the vnode during render of the parent. default values and camelCase conversion are handled in the component instance and are not reflected on the vnode.
This is not a bug. Think of `vnode.props` as the raw input. | 2021-06-27T16:20:50 | 2021-06-27T16:21:13 | {} | MEMBER |
vuejs | core | 870,682,639 | 4,020 | posva | You need to either create a computed or a `toRef()` out of `store.state.value`. Otherwise, you are reading the value once. only
```js
const value = toRef(store.state, 'count');
const value = computed(() => store.state.count);
```
[Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aDE+e3sgb... | 2021-06-29T15:07:52 | 2021-06-29T15:07:52 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.