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 | 691,807,682 | 2,109 | dsonet | I think it actually doesn't matter. Because in the end the value is correct. | 2020-09-14T04:46:56 | 2020-09-14T04:58:23 | {} | CONTRIBUTOR |
vuejs | core | 692,314,075 | 2,091 | yyx990803 | see be946ea5 - the order needs to be preserved, otherwise key expressions referencing v-for alias are also prefixed. | 2020-09-14T21:05:35 | 2020-09-14T21:05:35 | {
"+1": 1
} | MEMBER |
vuejs | core | 692,391,612 | 1,998 | yyx990803 | ~~Technically `NaN` is not a valid index so IMO it **should** be treated like a non-index property.~~ nvm, the fix is correct! | 2020-09-15T00:39:15 | 2020-09-15T00:40:03 | {} | MEMBER |
vuejs | core | 693,445,536 | 2,125 | HcySunYang | Related to this: https://github.com/vuejs/vue-next/commit/5f4053967cb61620d3dd27518f571166d7b5ec8f
Consider the following use cases, they can all reproduce the issue:
```js
watchEffect(() => {
// track
price.value
// trigger
price.value = 20
});
```
```js
watch(price, () => {
... | 2020-09-16T14:31:35 | 2020-09-16T14:31:35 | {} | MEMBER |
vuejs | core | 693,496,801 | 2,130 | yyx990803 | `v-show` works by toggling a DOM element's `display` style property. Using `v-show` on a component implicitly applies that `v-show` on that component's root node. You are essentially creating two `v-show` with contradicting values on the same node, which doesn't make any sense. | 2020-09-16T15:50:43 | 2020-09-16T15:50:43 | {} | MEMBER |
vuejs | core | 694,289,997 | 2,143 | husayt | I have the same issue | 2020-09-17T14:53:39 | 2020-09-17T14:53:39 | {} | NONE |
vuejs | core | 694,539,679 | 2,154 | posva | That's the one for bundlers, you need to use https://unpkg.com/@vue/reactivity@3.0.0-rc.12/dist/reactivity.esm-browser.js
Not sure if we can change anything here because we still want to keep those variables in bundlers environments | 2020-09-17T22:45:51 | 2020-09-17T22:45:51 | {} | MEMBER |
vuejs | core | 694,614,982 | 2,137 | unbyte | @CyberAP any repro in Vue 2? 😲 | 2020-09-18T02:42:43 | 2020-09-18T02:42:43 | {} | CONTRIBUTOR |
vuejs | core | 694,712,243 | 2,154 | posva | @justinfagnani I realized this was in the wrong repo! I transferred the issue even though I don't think we can change anything because the field in the package.json file is used by different systems (like bundlers and CDNs like unpkg)
Note that if you are building a library for Vue, you should import from vue. Creat... | 2020-09-18T07:43:02 | 2020-09-18T07:43:02 | {} | MEMBER |
vuejs | core | 694,835,381 | 2,155 | IndexXuan | @posva bro, I know use other event emitter instead of new Vue. It is feature, not question
buttonRef.$props.onClick = evt => alert(1) not work because of code
https://github.com/vuejs/vue-next/blob/f316a332b055d3f448dc735365551d89041f1098/packages/reactivity/src/baseHandlers.ts#L200
It means if we want add eve... | 2020-09-18T12:20:45 | 2020-09-18T12:20:45 | {} | NONE |
vuejs | core | 694,857,167 | 2,155 | IndexXuan | @posva this is for component container listener，not component emitted listener | 2020-09-18T13:08:19 | 2020-09-18T13:08:19 | {} | NONE |
vuejs | core | 694,983,403 | 2,035 | luka-mikec | @yyx990803 the problem is present in v3.0 too | 2020-09-18T17:10:51 | 2020-09-18T17:10:51 | {} | NONE |
vuejs | core | 692,132,680 | 2,116 | zmtlwzy | I find this api from : https://v3.vuejs.org/api/instance-methods.html#watch
It's works better than vue2
thanks ! | 2020-09-14T15:27:13 | 2020-09-14T15:27:13 | {} | NONE |
vuejs | core | 693,460,094 | 2,125 | unbyte | As a supplement to what @HcySunYang pointed out, calling some methods can both trigger and track in one effect, which can lead to an infinite recursion in some scenarios.
e.g. `Array.prototype.push`, gets `.length` and sets values,
```js
const a = reactive([])
const b = ref(0)
const c = ref(0)
wa... | 2020-09-16T14:53:57 | 2020-09-16T15:14:34 | {} | CONTRIBUTOR |
vuejs | core | 693,788,450 | 1,834 | xjh1230 | why refs value changed from array(vue2) to single(vue3) | 2020-09-17T03:37:02 | 2020-09-17T03:37:02 | {} | NONE |
vuejs | core | 693,838,849 | 2,130 | wcycode | I understand what v-show means. but I can't decide how users use it. So we don't recommend use v-show in root node ?
| 2020-09-17T04:49:32 | 2020-09-17T04:49:32 | {} | NONE |
vuejs | core | 694,114,066 | 2,141 | 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).
---
In most scenarios, you would have everything acc... | 2020-09-17T09:29:08 | 2020-09-17T09:29:08 | {} | MEMBER |
vuejs | core | 694,854,965 | 2,155 | leopiccionia | Have you tried something like `buttonRef.$el.addEventListener('click', handleClick)`? | 2020-09-18T13:04:06 | 2020-09-18T13:05:05 | {} | CONTRIBUTOR |
vuejs | core | 691,684,532 | 2,054 | teabagp | @yyx990803 Why? Why I get this single fragment node when I getting slots? but in HTML I see only elements without the node | 2020-09-13T15:18:19 | 2020-09-13T15:18:19 | {} | NONE |
vuejs | core | 691,779,622 | 2,110 | HcySunYang | In V3, the `<template>` without the `v-if/else/else-if/for/slot` directives is treated as a [HTML Content Template (`<template>`) element](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/template) | 2020-09-14T02:46:23 | 2020-09-14T02:46:23 | {} | MEMBER |
vuejs | core | 693,504,173 | 2,135 | unbyte | @yyx990803 This fix has nothing to do with https://github.com/vuejs/vue-next/commit/3810de7d6bd0044177f043285228c2e988093883 | 2020-09-16T16:02:14 | 2020-09-16T16:02:14 | {} | CONTRIBUTOR |
vuejs | core | 692,394,511 | 1,984 | yyx990803 | Good catch, thanks! | 2020-09-15T00:50:20 | 2020-09-15T00:50:20 | {} | MEMBER |
vuejs | core | 692,395,008 | 1,952 | yyx990803 | Thanks - I changed it to `additionalData` since `data` is actually meant to be the entire source in `node-sass` usage, so I think `additionalData` is more explicit and avoids potential confusion. It also [aligns with `sass-loader`](https://webpack.js.org/loaders/sass-loader/#additionaldata). | 2020-09-15T00:52:20 | 2020-09-15T00:52:20 | {
"+1": 2
} | MEMBER |
vuejs | core | 692,761,517 | 2,115 | yyx990803 | Thanks for the PR but I don't think this is necessary. A union literal is more straightforward in my opinion. | 2020-09-15T14:42:11 | 2020-09-15T14:42:11 | {} | MEMBER |
vuejs | core | 694,227,344 | 2,143 | posva | Probably related to the rendered component being nested. The component is displayed if the `v-slot` api is used | 2020-09-17T13:19:33 | 2020-09-17T13:19:33 | {} | MEMBER |
vuejs | core | 694,239,641 | 2,143 | cexbrayat | You mean if we use `<hello />` directly instead of `<router-view />`? If so, yes it does work. But as it was nice to be able to use Suspense around the RouterView to handle the async loading, I thought it was worth opening an issue. | 2020-09-17T13:36:09 | 2020-09-17T13:36:09 | {} | MEMBER |
vuejs | core | 694,640,896 | 2,143 | yyx990803 | Similar to `<transition>`, the new Suspense now must be used with `<router-view>` via its [slot-based syntax](https://next.router.vuejs.org/api/#router-view-s-v-slot) because it now must have direct access to the toggled root node:
```html
<router-view v-slot="{ Component }">
<suspense>
<component :is="Comp... | 2020-09-18T04:19:37 | 2020-09-18T04:19:37 | {
"+1": 13,
"heart": 6,
"hooray": 2,
"rocket": 3
} | MEMBER |
vuejs | core | 695,198,763 | 2,166 | LinusBorg | you're using Vue 2's template-compiler (and likely vue-loader in laravel mix as well).
Vue 3 requires new versions of these build-time dependencies, which might mean laravel mix has to upgrade as well? not familiar with that tool's details.
vue-template-compiler -> @vue/sfc-compiler
vue-loader v15 -> v16.0.0-b... | 2020-09-19T10:55:39 | 2020-09-19T10:55:39 | {} | MEMBER |
vuejs | core | 692,317,649 | 2,116 | yyx990803 | This is somewhat intended. Technically, `watch: 'key'` should only trigger when the binding itself has been mutated - Vue 2's behavior is overly-eager because due to ES5 restrictions we have to track more than we should when Arrays are encountered. Vue 3's reactivity tracking is more precise thanks to Proxies, so in th... | 2020-09-14T21:13:18 | 2020-09-14T21:13:18 | {
"+1": 7
} | MEMBER |
vuejs | core | 692,836,903 | 2,048 | yyx990803 | Thanks for the PR! Unfortunately, after merging #1883, I wasn't able to resolve the conflicts in a way that passes all the tests (specifically I couldn't get props with default from mixins to be made optional). Would you mind rebase your PR on top of master? Thanks! | 2020-09-15T16:43:37 | 2020-09-15T16:43:37 | {} | MEMBER |
vuejs | core | 693,503,233 | 2,135 | yyx990803 | This is fixed by 3810de7d | 2020-09-16T16:00:39 | 2020-09-16T16:00:39 | {} | MEMBER |
vuejs | core | 694,658,086 | 2,151 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/9499?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your test... | 2020-09-18T05:21:57 | 2020-09-18T05:21:57 | {} | CONTRIBUTOR |
vuejs | core | 694,859,618 | 2,154 | yyx990803 | In addition to the dev-only code (warnings and edge case checks), the `esm-bundler` distribution format also contains the ability to expose compile-time feature flags (tree-shakes features when flags are disabled), which is impossible in browser-oriented builds. This is important because Vue as a framework has a lot of... | 2020-09-18T13:12:38 | 2020-09-18T13:14:23 | {} | MEMBER |
vuejs | core | 694,883,110 | 2,155 | IndexXuan | it should be buttonRef.onClick = comp emitted click event | 2020-09-18T13:56:04 | 2020-09-18T13:56:04 | {} | NONE |
vuejs | core | 691,889,892 | 2,112 | posva | The error comes from your computed:
```js
comp() {
return `${this.rows[0].name} ${this.rows[0].job} `;
}
```
`this.rows[0]` is undefined
---
Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](... | 2020-09-14T08:00:32 | 2020-09-14T08:00:32 | {} | MEMBER |
vuejs | core | 692,110,260 | 2,116 | posva | You need to add a `deep: true` to the watcher options. I couldn't find this breaking change but I'm also not sure if this was intended. If it was, it should be added to the migration guide | 2020-09-14T14:52:38 | 2020-09-14T14:52:38 | {
"+1": 12
} | MEMBER |
vuejs | core | 692,181,010 | 2,059 | yyx990803 | Yes, this is an intentional change (`v-bind` appearance order now affects merge result) and we should document it in the migration guide. | 2020-09-14T16:50:52 | 2020-09-14T16:50:52 | {} | MEMBER |
vuejs | core | 692,340,129 | 2,110 | yyx990803 | I guess the question is why would one ever use `<template>` without a directive like that. It is indeed a different behavior from v2 but I don't think the v2 behavior has any practical use cases (while at the same time blocking the ability to render a native `<template>` tag). For that I would consider this an intended... | 2020-09-14T22:09:12 | 2020-09-14T22:09:12 | {
"+1": 2
} | MEMBER |
vuejs | core | 694,882,697 | 2,155 | IndexXuan | @posva no way to listen component emitted inside setup？very sad ... | 2020-09-18T13:55:13 | 2020-09-18T13:55:13 | {} | NONE |
vuejs | core | 710,096,359 | 2,397 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | -------------------- |
| vue.global.prod.js | 39.95 KB (-0.05% 🔽) |
| runtime-dom.global.prod.js | 26.28 KB (-0.06% 🔽) |
| size-check.global.prod.js | 15.8 KB (0%) | | 2020-10-16T14:55:12 | 2020-10-16T14:55:12 | {} | NONE |
vuejs | core | 711,085,154 | 2,409 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 39.97 KB (0%) |
| runtime-dom.global.prod.js | 26.3 KB (0%) |
| size-check.global.prod.js | 15.8 KB (0%) | | 2020-10-17T21:56:15 | 2020-10-17T21:56:15 | {} | NONE |
vuejs | core | 707,542,248 | 2,370 | HcySunYang | I found that using `markRaw` can make it work correctly:
```js
this.canvas = Vue.markRaw(new fabric.Canvas(c, {
width: c.clientWidth,
height: c.clientHeight
}));
``` | 2020-10-13T07:14:40 | 2020-10-13T07:14:40 | {
"+1": 3
} | MEMBER |
vuejs | core | 708,193,447 | 2,280 | HcySunYang | Now it works | 2020-10-14T06:38:48 | 2020-10-14T06:38:48 | {} | MEMBER |
vuejs | core | 708,218,410 | 2,376 | LinusBorg | then pleasse provide a small github repo with a actually runnable reproduction. | 2020-10-14T07:32:21 | 2020-10-14T07:32:21 | {} | MEMBER |
vuejs | core | 708,942,100 | 2,382 | LinusBorg | That's still very, very little information.
* How did you create the project, Vue CLI? which version do the dependencies have? Can you just put the project on github for us to run?
* How did you run it?
* Is that a compilation error from Vue CLI after running `npm run serve` or an IDE error from in-Editor checks? | 2020-10-15T06:55:23 | 2020-10-15T06:56:40 | {} | MEMBER |
vuejs | core | 709,037,956 | 2,381 | posva | I tried boiling it down but couldn't: https://jsfiddle.net/posva/gtmksj37/
Please open a new issue if you manage to provide a boiled down reproduction | 2020-10-15T09:30:50 | 2020-10-15T09:30:50 | {} | MEMBER |
vuejs | core | 710,014,202 | 629 | swaprenge | > @LinusBorg I've literally just implemented that :-)
>
> ```
> componentDefinition = defineComponent({ extends: defineComponent({ ...component }), data: () => ({params: params}), created: function() { componentInstance = this.$root }});
>
> createApp(componentDefinition).mount(container);
> ```
>
> This wor... | 2020-10-16T12:26:13 | 2020-10-16T12:26:13 | {} | NONE |
vuejs | core | 711,085,196 | 2,410 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 39.97 KB (0%) |
| runtime-dom.global.prod.js | 26.3 KB (0%) |
| size-check.global.prod.js | 15.8 KB (0%) | | 2020-10-17T21:56:47 | 2020-10-17T21:56:47 | {} | NONE |
vuejs | core | 711,104,081 | 2,411 | 07akioni | try this?
```js
watch(
toRef(dataObject, 'propA'),
...
)
``` | 2020-10-18T01:39:02 | 2020-10-18T01:39:02 | {} | CONTRIBUTOR |
vuejs | core | 711,134,274 | 2,411 | posva | There isn't always a name property to be passed but you can do that by using an array:
```js
const name = ref('dynamic name')
const object = reactive({})
watch(() => [name.value, object[name.value]], ([newName, newValue]) => {})
``` | 2020-10-18T08:24:23 | 2020-10-18T08:24:23 | {} | MEMBER |
vuejs | core | 707,353,152 | 2,244 | thomasgauthier | I came across this problem and realized it was because I was using Vue 2 instead of Vue 3.
```npm install vue@^3.0.0``` did the trick.
| 2020-10-12T21:24:44 | 2020-10-12T21:24:44 | {} | NONE |
vuejs | core | 707,975,698 | 2,199 | yyx990803 | See https://github.com/vuejs/vue-next/issues/2097#issuecomment-707975628 | 2020-10-13T20:01:41 | 2020-10-13T20:01:41 | {} | MEMBER |
vuejs | core | 708,120,833 | 2,367 | tassioFront | > Please don't open issues with unfinished reproductions, it seems to work: https://jsfiddle.net/0jxhdrvw/
Sorry for it. I will pay attention. I will try reproduce it and open again. Thank you | 2020-10-14T02:46:36 | 2020-10-14T02:46:36 | {} | NONE |
vuejs | core | 708,124,421 | 2,376 | santoshpandey-lilly | > you are using vue2
The JsFiddle shows Vue2 but I am using Vue3.
The fiddle is just to show the code.
The code needs router setup and some other custom code so its hard to put all that in Js Fiddle. | 2020-10-14T02:58:26 | 2020-10-14T02:58:26 | {} | NONE |
vuejs | core | 708,966,085 | 2,195 | knightly-bot | 
🌒 Knightly build enabled, release every night at 00:00 UTC <sup>(skip if no change)</sup>
📦 [npm package](https://www.npmjs.com/package/@knightly/vue/v/pr2195) | 2020-10-15T07:44:56 | 2020-10-15T07:44:56 | {
"rocket": 1
} | NONE |
vuejs | core | 709,426,088 | 2,384 | dependabot-preview[bot] | OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting `@dependabot ignore this major version` or `@dependabot ignore this minor version`.
If you change your mind, just re-... | 2020-10-15T16:02:34 | 2020-10-15T16:02:34 | {} | CONTRIBUTOR |
vuejs | core | 709,887,201 | 2,388 | posva | You can use an empty string as a workaround | 2020-10-16T07:51:15 | 2020-10-16T07:51:15 | {} | MEMBER |
vuejs | core | 711,221,042 | 2,400 | 69hunter | I think for the provide/inject API, the component should not be able to `self-inject` it's own `provide`, regardless of the order of `provide` and `inject` in the `setup` function. As previously mentioned in https://github.com/vuejs/vue-next/issues/1818. | 2020-10-18T15:24:52 | 2020-10-18T15:24:52 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 707,696,005 | 2,372 | posva | you cannot pass the same object to two different `reactive`, `ref`, etc functions. It has to be a different object every time:
```js
console.log(isReactive(shallowReactive({a:{b:1}}).a)); // should always be false
console.log(isReactive(reactive({a:{b:1}}).a)); // should always be true
``` | 2020-10-13T12:10:43 | 2020-10-13T12:10:43 | {} | MEMBER |
vuejs | core | 707,984,797 | 2,369 | yyx990803 | Nice, let's remove the `check-size` job from CircleCI's config. | 2020-10-13T20:19:33 | 2020-10-13T20:19:33 | {} | MEMBER |
vuejs | core | 708,122,014 | 2,376 | unbyte | you are using vue2 | 2020-10-14T02:50:34 | 2020-10-14T02:50:34 | {} | CONTRIBUTOR |
vuejs | core | 710,095,952 | 2,395 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 39.95 KB (0%) |
| runtime-dom.global.prod.js | 26.28 KB (0%) |
| size-check.global.prod.js | 15.8 KB (0%) | | 2020-10-16T14:54:26 | 2020-10-16T14:54:26 | {} | NONE |
vuejs | core | 711,085,118 | 2,407 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 39.97 KB (0%) |
| runtime-dom.global.prod.js | 26.3 KB (0%) |
| size-check.global.prod.js | 15.8 KB (0%) | | 2020-10-17T21:55:52 | 2020-10-17T21:55:52 | {} | NONE |
vuejs | core | 708,988,256 | 2,382 | posva | Please read https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro and open a new issue if you manage to provide a boiled down reproduction. Note it can still be a repository on github created with vue-cli
---
Remember to use the [forum](http://forum.vuejs.org/) or the [Discord chat](https://vue-land.js.org/) to a... | 2020-10-15T08:26:15 | 2020-10-15T08:26:15 | {} | MEMBER |
vuejs | core | 708,005,521 | 2,280 | yyx990803 | The current implementation has two issues:
1. The generated code contains a resolve call `const _component_component = _resolveComponent("component")`, which leads to a warning for unresolved component.
2. The following SSR test case fails:
```js
const app = createApp({
data() {
return {
obj: {... | 2020-10-13T20:58:56 | 2020-10-13T20:58:56 | {} | MEMBER |
vuejs | core | 708,482,970 | 2,244 | FossPrime | For the curious: The penalty in disabling treeshaking with @thomasgauthier 's workaround on a vanilla project is roughly 32KB of additional js in the vendor's chunk, one KB extra the app chunk. The more dependencies you have, the worse the workaround gets... specially with vuetify and lager projects that rely on trees ... | 2020-10-14T15:34:21 | 2020-10-14T16:31:30 | {
"+1": 1
} | NONE |
vuejs | core | 711,115,732 | 2,412 | unbyte | `update: modelValue` => `update:modelValue`
no space | 2020-10-18T04:40:07 | 2020-10-18T04:40:07 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 707,074,390 | 2,364 | unbyte | https://caniuse.com/?search=const | 2020-10-12T11:55:08 | 2020-10-12T11:55:08 | {} | CONTRIBUTOR |
vuejs | core | 707,366,281 | 2,244 | thomasgauthier | After hitting the problem again in a webpack environment I realized [this export](https://github.com/vuejs/vue-next/blob/ffdb05e1f1b69e737e249b081e7049c74aaf25e8/packages/runtime-core/src/index.ts#L272) is the culprit.
The ssrUtils object in Vue 3 only gets exported in CommonJS builds. When the target isn't node, W... | 2020-10-12T21:57:45 | 2020-10-13T04:25:25 | {
"+1": 3
} | NONE |
vuejs | core | 707,975,628 | 2,097 | yyx990803 | It's not documented but yes it's possible to render using existing app context:
```js
import { h, render } from 'vue'
const childTree = h('div', 'some message')
treeToRender.appContext = app._context
render(childTree, document.getElementById('target'))
```
We can make this a method on the app instance:
... | 2020-10-13T20:01:32 | 2020-10-13T20:01:32 | {
"+1": 14
} | MEMBER |
vuejs | core | 708,243,140 | 2,376 | posva | The template for reproductions for vue-router in on the issue helper (https://jsfiddle.net/posva/3yq6ojLv/5). One thing I see in your code is `formData`, `@prev-page`, `
@next-page`, etc are all passed to `router-view` instead of `component`. If you manage to boil it down and reproduce it with router-view, please open... | 2020-10-14T08:21:45 | 2020-10-14T08:21:45 | {} | MEMBER |
vuejs | core | 708,372,555 | 2,027 | mannok | @yyx990803 How about setting `watch(route, () => {}, { deep: false })` instead? Can I avoid deep watch as well? | 2020-10-14T12:36:16 | 2020-10-14T12:36:16 | {} | NONE |
vuejs | core | 708,931,811 | 2,382 | jahnli | I just created a new Vue3.0 project and ran it on WebStorm with this error | 2020-10-15T06:34:08 | 2020-10-15T06:34:08 | {} | NONE |
vuejs | core | 709,432,732 | 2,369 | yyx990803 | I noticed the action only operates on PRs but ideally we want the number for directly pushed commits as well. Can we make it just run on commits and log it so we can check in the github actions log? | 2020-10-15T16:12:57 | 2020-10-15T16:12:57 | {} | MEMBER |
vuejs | core | 707,132,138 | 2,364 | und3fined | Any bug in here?
```
if(s)for(const e in s)t[e]=s[e]
``` | 2020-10-12T13:49:41 | 2020-10-12T13:49:41 | {} | NONE |
vuejs | core | 707,559,244 | 2,370 | deerchao | Thanks, it works with `markRaw`. | 2020-10-13T07:48:57 | 2020-10-13T07:48:57 | {} | NONE |
vuejs | core | 708,070,443 | 2,374 | dependabot-preview[bot] | One of your CI runs failed on this pull request, so Dependabot won't merge it.
- [ci/circleci: test](https://circleci.com/gh/vuejs/vue-next/10264?utm_campaign=vcs-integration-link&utm_medium=referral&utm_source=github-build-link)
Dependabot will still automatically merge this pull request if you amend it and your tes... | 2020-10-13T23:51:43 | 2020-10-13T23:51:43 | {} | CONTRIBUTOR |
vuejs | core | 708,329,491 | 2,378 | unbyte | sorry but this is a redundant test, for value inside `ref` is `reactive`. and your test just confirms this fact. | 2020-10-14T11:03:01 | 2020-10-14T11:04:30 | {} | CONTRIBUTOR |
vuejs | core | 708,936,831 | 2,381 | LinusBorg | watch effects created with `$watch` are cleaned up up on unmount automatically so I don't see the need to do that manually. Try leaving that call out.
so my first suspicion was that the effects simply were already cleanup up when your code is called by that's not the case, so something we should probably take a look... | 2020-10-15T06:44:50 | 2020-10-15T06:44:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 709,172,465 | 2,379 | raukaute | Closing this one on favour of #2386. | 2020-10-15T10:52:44 | 2020-10-15T10:52:44 | {} | NONE |
vuejs | core | 710,767,942 | 2,400 | 07akioni | Although it works if I put `provide` after `inject`, I think it shouldn't work in this way. | 2020-10-17T07:41:36 | 2020-10-17T07:41:36 | {} | CONTRIBUTOR |
vuejs | core | 711,084,997 | 2,398 | dependabot-preview[bot] | Superseded by #2409. | 2020-10-17T21:54:19 | 2020-10-17T21:54:19 | {} | CONTRIBUTOR |
vuejs | core | 707,111,753 | 2,364 | und3fined | > https://caniuse.com/?search=const
Hi @unbyte,
with vue@2, no any problem with FF 48a2
But with vue@3, I don't understand why.
------------
I want to build KaiOS (FF 48a2) application with vue@3. Maybe I can't do that with vue@3 | 2020-10-12T13:12:30 | 2020-10-12T13:22:41 | {} | NONE |
vuejs | core | 707,332,709 | 2,367 | posva | Please don't open issues with unfinished reproductions, it seems to work: https://jsfiddle.net/0jxhdrvw/ | 2020-10-12T20:34:44 | 2020-10-12T20:34:44 | {} | MEMBER |
vuejs | core | 708,139,982 | 2,345 | basvanmeurs | > Can you summarize a list of changed APIs (both internally and externally)?
## Reactivity API changes
1. ReactiveEffect is now an object instead of a function. It must now be invoked using the run method (`effect.run()` vs `effect()`).
2. The `effect` function has changed. The properties `lazy`, `allowRecurse... | 2020-10-14T03:54:02 | 2020-10-14T03:54:02 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 709,517,203 | 2,387 | jacekkarczmarczyk | dom properties are not reactive | 2020-10-15T18:38:23 | 2020-10-15T18:38:23 | {} | CONTRIBUTOR |
vuejs | core | 711,067,620 | 2,406 | posva | This is because Vue 3 no longer replaces thes #app element but appends inside of it
| 2020-10-17T19:19:26 | 2020-10-17T19:19:26 | {} | MEMBER |
vuejs | core | 711,290,774 | 2,419 | 07akioni | 厉害了 hhh | 2020-10-18T17:00:42 | 2020-10-18T17:00:42 | {} | CONTRIBUTOR |
vuejs | core | 708,068,467 | 2,335 | dependabot-preview[bot] | Superseded by #2373. | 2020-10-13T23:44:46 | 2020-10-13T23:44:46 | {} | CONTRIBUTOR |
vuejs | core | 708,215,757 | 2,375 | LinusBorg | > Reactive API is not supported because the return store is a proxy and this is bound to origin object. It's there any possibility to provide an observable API like Vue 2.0?
That partially correct, even though for most use cases, the reactive proxy implementation of Vue 3 works with classes just fine - but yes, ther... | 2020-10-14T07:26:37 | 2020-10-14T07:29:34 | {} | MEMBER |
vuejs | core | 709,519,474 | 2,387 | yyx990803 | This is expected behavior. Vue does not observe native DOM elements. Only plain userland objects can be made reactive. | 2020-10-15T18:42:44 | 2020-10-15T18:43:20 | {} | MEMBER |
vuejs | core | 710,683,785 | 2,338 | JensDll | I'm also having a lot of problems with props in TypeScript.
Version
3.0.1
Reproduction link
[TS Playground](https://www.typescriptlang.org/play?#code/PTAEF5K6dv9ABQE4HsAOBnC9d-gFAAuAnugKagDCqAtuqgHbmNEoaYDy6RAlk5gA8iCKAAiAQyISAfBAKhQAH2p0GzVpwBGAK3IBjNmizc+A4TIXLQmIsl6MA5gG0AugWJlKNekxZFtPUN2Ex5+RiERcHEpWVEAbyt... | 2020-10-16T22:40:33 | 2020-10-16T22:40:33 | {} | CONTRIBUTOR |
vuejs | core | 711,135,783 | 2,414 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/1618 | 2020-10-18T08:38:09 | 2020-10-18T08:38:09 | {} | MEMBER |
vuejs | core | 708,980,740 | 2,385 | posva | Please see https://new-issue.vuejs.org/?repo=vuejs/vue#why-repro | 2020-10-15T08:12:10 | 2020-10-15T08:12:10 | {} | MEMBER |
vuejs | core | 709,400,917 | 2,345 | basvanmeurs | After the latest updates:
| 2020-10-15T15:23:58 | 2020-10-15T15:23:58 | {
"+1": 9
} | CONTRIBUTOR |
vuejs | core | 710,016,810 | 629 | swaprenge | > @swapagarwal this part:
>
> `data: () => ({params}),`
>
> makes `params` available to the created component (via `this.params`).
>
> So just provide what you need via the `data` function
okay, but cant we pass `props` to the created component? | 2020-10-16T12:31:57 | 2020-10-16T12:32:23 | {} | NONE |
vuejs | core | 710,109,179 | 2,390 | soletan | I basically second this fear of totally misusing `app.component()` for declaring new components in an instance and would opt for a different way limited to looking up existing components, only. I also agree this is an edge case and thus consider this opportunity to be some kind of "syntactic sugar" which I see in compl... | 2020-10-16T15:17:28 | 2020-10-16T15:21:03 | {} | NONE |
vuejs | core | 711,288,766 | 2,418 | LinusBorg | This is expected and was like that in Vue 2 as well, and is documented.
Vue's state is not immutable. the whole Reactivity is based on mutating state. So the old array is the same as the new array.
there's no way to compare the old and new state like that. | 2020-10-18T16:55:59 | 2020-10-18T16:55:59 | {} | MEMBER |
vuejs | core | 707,986,095 | 2,315 | yyx990803 | Can you please fix the typing issue and add a test case? | 2020-10-13T20:22:12 | 2020-10-13T20:22:12 | {
"+1": 1
} | MEMBER |
vuejs | core | 708,009,096 | 2,345 | yyx990803 | This is great work! However, it seems it contains some non trivial changes to the usage of `effect`, which is technically part of the public API of `@vue/reactivity`. Can you summarize a list of changed APIs (both internally and externally)?
Regarding the benchmarks - this is very helpful, it'd be awesome to maybe e... | 2020-10-13T21:06:17 | 2020-10-13T21:06:17 | {
"eyes": 1
} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.