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 | 2,146,953,899 | 11,067 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9363929471)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9344510539) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/936... | 2024-06-04T08:44:15 | 2024-06-04T12:09:40 | {} | CONTRIBUTOR |
vuejs | core | 2,147,379,793 | 11,051 | yyx990803 | `onMounted`, like all other lifecycle hooks, should be registered during setup phase, not conditionally inside other lifecycle hooks. Such usage is not supported by design. | 2024-06-04T12:11:46 | 2024-06-04T12:11:46 | {} | MEMBER |
vuejs | core | 2,139,304,277 | 9,559 | sunnyphp | Still not fixed.
Same issues with PR's:
https://github.com/vuejs/core/issues/8068
https://github.com/vuejs/core/issues/5970 | 2024-05-30T11:00:32 | 2024-05-30T11:00:32 | {} | NONE |
vuejs | core | 2,141,093,692 | 6,783 | skirtles-code | I don't think this is the right fix.
Rather than adding a warning, it should ignore the comment in production, same as during dev.
It's possible that #6238 or #7387 will already fix this problem, though I think those PRs still need more work before they can be merged. | 2024-05-31T01:41:52 | 2024-05-31T01:41:52 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,142,581,269 | 9,370 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9321052390)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9313156194) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-05-31T16:12:59 | 2024-05-31T16:12:59 | {} | CONTRIBUTOR |
vuejs | core | 2,143,673,683 | 7,247 | edison1105 | /ecosystem-ci run | 2024-06-02T02:38:47 | 2024-06-02T02:38:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,145,386,849 | 11,048 | sxzz | In TypeScript 5.5, an error will occur because the `target` in `tsconfig.json` is set to `ES2016`. | 2024-06-03T14:43:35 | 2024-06-03T14:43:35 | {} | MEMBER |
vuejs | core | 2,139,233,216 | 8,505 | yyx990803 | Thanks for the PR - it took a long time for me to decide to close this because I was thinking about how to explain the reasoning.
For one - these type guard helpers mainly serve to reduce code size as they minify into a single letter function call compared to the inline `typeof` checks. However this is only meaningf... | 2024-05-30T10:16:34 | 2024-05-30T10:16:34 | {} | MEMBER |
vuejs | core | 2,139,432,068 | 7,312 | anboo | +
Same problem | 2024-05-30T12:19:00 | 2024-05-30T12:19:00 | {} | NONE |
vuejs | core | 2,140,767,139 | 9,082 | skirtles-code | There have been significant changes to the reactivity system since this PR was opened, but the `ref = toRaw(ref)` line is still present, so I've just tested this change against the latest `main` branch.
With the new reactivity system, code like this will fail if we remove the `ref = toRaw(ref)` line:
```js
impor... | 2024-05-30T19:54:19 | 2024-05-30T19:54:19 | {} | CONTRIBUTOR |
vuejs | core | 2,142,152,970 | 11,036 | jh-leong | could you please rerun the ecosystem-ci | 2024-05-31T13:20:09 | 2024-05-31T13:20:09 | {} | MEMBER |
vuejs | core | 2,142,528,510 | 6,864 | yyx990803 | https://github.com/vuejs/core/issues/6859#issuecomment-2142528208 | 2024-05-31T15:43:39 | 2024-05-31T15:43:39 | {} | MEMBER |
vuejs | core | 2,142,547,978 | 7,689 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ----------------- | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 91 kB (**+4 B**) | 34.6 kB (**-3 B**) | 31.2 kB (**+2 B**) |
| vue.glo... | 2024-05-31T15:56:06 | 2024-05-31T15:56:06 | {} | NONE |
vuejs | core | 2,143,001,627 | 6,359 | skirtles-code | The title of this PR is currently a bit misleading. It refers to an earlier iteration of the code, but the code has changed significantly since then.
---
Some notes for reviewers...
There's another PR, #6376, that attempts to fix the same problem. They take very different approaches, so I've written a brief co... | 2024-05-31T21:29:30 | 2024-05-31T21:29:30 | {} | CONTRIBUTOR |
vuejs | core | 2,143,003,374 | 6,376 | skirtles-code | For anyone looking to review this, I've posted a comparison with https://github.com/vuejs/core/pull/6359#issuecomment-2143001627 on that PR. | 2024-05-31T21:31:08 | 2024-05-31T21:31:08 | {} | CONTRIBUTOR |
vuejs | core | 2,144,123,869 | 7,745 | edison1105 | @skirtles-code
Thanks for your explanation. I marked it as `need guidance`, waiting for Evan's input.
| 2024-06-03T01:33:57 | 2024-06-03T01:33:57 | {} | MEMBER |
vuejs | core | 2,144,689,965 | 11,053 | roberthand9 | The documentation surrounding the onErrorCaptured hook is transparent that the argument is swapped in prod vs dev - but I can appreciate what you're saying
I did consider slicing the URL but it felt like relying on an unstable detail (please ignore my use of suspense for this argument...)
As you've suggested I th... | 2024-06-03T09:12:36 | 2024-06-03T09:12:36 | {
"+1": 1
} | NONE |
vuejs | core | 2,146,934,871 | 10,959 | yyx990803 | Thanks a lot for bringing this up. After looking at this and #5256 in depth, I felt the best solution is to actually move away from hoisting vnodes altogether, but rather cache them per-instance. See https://github.com/vuejs/core/pull/11067 | 2024-06-04T08:35:23 | 2024-06-04T08:35:23 | {
"heart": 2
} | MEMBER |
vuejs | core | 2,146,939,859 | 11,067 | yyx990803 | /ecosystem-ci run | 2024-06-04T08:37:42 | 2024-06-04T08:37:42 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,146,908,067 | 11,067 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ---------------------- | ---------------------- | ---------------------- |
| runtime-dom.global.prod.js | 94.3 kB (**+3.29 kB**) | 35.6 kB (**+998 B**) ... | 2024-06-04T08:22:18 | 2024-06-04T12:01:07 | {} | NONE |
vuejs | core | 2,140,195,677 | 11,038 | Joebayld | @edison1105 that's odd. I've tested it on different machines and made the link public. | 2024-05-30T16:36:54 | 2024-05-30T16:36:54 | {} | NONE |
vuejs | core | 2,139,160,962 | 9,363 | vue-bot | 📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9300275667)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9280497438) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-c... | 2024-05-30T09:36:33 | 2024-05-30T09:52:13 | {} | CONTRIBUTOR |
vuejs | core | 2,139,244,185 | 8,533 | yyx990803 | I thought about this again and my conclusion is that we don't really want this. Users have gotten used to macros being "just available" inside `<script setup>` - allowing aliasing actually only creates ways to make the code look different and less consistent across codebases. | 2024-05-30T10:22:56 | 2024-05-30T10:22:56 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,144,177,971 | 9,739 | skirtles-code | I did a bit of investigation into this myself. This was the example I came up with:
- [Playground](<https://play.vuejs.org/#eNqtVk1v2kAQ/SurvSRRqI1J+oUANUmplEr5UKjUQ7cHYxYw2LvW7pqCkP97Z2xjm5DAwb4gPPP89s2bB/aW3kSRtYo57dKe9pQfGaK5iaMBE34YSWXIlig+JQmZKhmSM4CeFa2Hzd3cDyZ5y7Lza+QDEBOeFNqQJd+QPpKcty+wOo2FZ3wpsKS4np9fkC0TB... | 2024-06-03T02:43:35 | 2024-06-03T02:43:35 | {} | CONTRIBUTOR |
vuejs | core | 2,146,726,519 | 11,048 | sxzz | Without dotAll, [the performance](https://jsbenchmark.com/#eyJjYXNlcyI6W3siaWQiOiJjQV9ZNDJybFpQUjBkbngwQmlxVlciLCJjb2RlIjoiY29uc3QgcmVnZXggPSAvXjwhLS0uKi0tPiQvc1xucmVnZXgudGVzdChgPCEtLWNvbW1lbnRcbmhlbGxvXG53b3JsZC0tPmApIiwiZGVwZW5kZW5jaWVzIjpbXSwibmFtZSI6ImRvdEFsbCJ9LHsiaWQiOiJxYmNaMTAwUEFvRFpsaXZGdkkyUGYiLCJjb2RlIjoiY... | 2024-06-04T06:39:15 | 2024-06-04T06:39:15 | {} | MEMBER |
vuejs | core | 2,147,372,472 | 11,068 | LinusBorg | Issues require runnable reproductions. The description is also not very clear | 2024-06-04T12:07:54 | 2024-06-04T12:07:54 | {} | MEMBER |
vuejs | core | 2,139,241,613 | 8,717 | yyx990803 | I don't think this PR makes meaningful improvements as the case discussed does not apply to any of the use sites affected in the PR. | 2024-05-30T10:21:27 | 2024-05-30T10:21:27 | {} | MEMBER |
vuejs | core | 2,139,306,251 | 11,018 | edison1105 | Well, the `Console` already has an error log, and you can determine the cause of the error. Vue cannot detect all exception codes. | 2024-05-30T11:01:45 | 2024-05-30T11:01:45 | {} | MEMBER |
vuejs | core | 2,141,717,516 | 11,037 | yangliguo7 | https://github.com/kkagura/test-unmount/blob/7d8e091fc7215bdd020dbd1df1197f88a8630aa3/src/views/Page2.vue#L8-L10
use mode `out-in` will trigger mount effect when use `unmount`. the `mount` effect will be added to effetc quene
https://github.com/vuejs/core/blob/main/packages/runtime-core/src/components/Suspense.t... | 2024-05-31T10:23:40 | 2024-05-31T10:23:40 | {} | CONTRIBUTOR |
vuejs | core | 2,142,532,100 | 11,048 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 91 kB | 34.6 kB | 31.2 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-05-31T15:45:57 | 2024-05-31T15:45:57 | {} | NONE |
vuejs | core | 2,142,553,288 | 6,859 | obj63mc | I am still able to reproduce this on all our sites example - https://moosylvania.com/
Currently as soon as vue3 mounts, it loads all the images. It still shows in the markup that loading="lazy" is set but the images at the bottom of the page shouldn't be loading right away. You can see that they are loaded via the... | 2024-05-31T15:59:40 | 2024-05-31T15:59:40 | {} | NONE |
vuejs | core | 2,143,522,165 | 11,038 | jonasfreitas-dev | I accessed here and was able to see the problem happening. Below is a screenshot:
| 2024-06-01T17:26:46 | 2024-06-01T17:26:46 | {} | NONE |
vuejs | core | 2,143,650,490 | 9,370 | edison1105 | vant's test case failed, it seems related to [this commit](https://github.com/vuejs/core/commit/537a571f8cf09dfe0a020e9e8891ecdd351fc3e4) and they should update those snapshots. | 2024-06-02T00:52:32 | 2024-06-02T00:52:32 | {} | MEMBER |
vuejs | core | 2,144,251,961 | 9,451 | skirtles-code | For anyone who's interested, there's an open issue for the `key` problem at #10882. | 2024-06-03T04:26:03 | 2024-06-03T04:26:03 | {
"heart": 1
} | CONTRIBUTOR |
vuejs | core | 2,144,991,465 | 9,783 | xvaara | > @xvaara I'm not sure exactly what problem you're having, but based on the example you gave I don't think this PR will fix it. This change only impacts cases where `disabled` is `false` and the `to` is `null`/`undefined`, which doesn't seem to be what you're describing.
@skirtles-code
That is exactly the case I'm... | 2024-06-03T11:48:12 | 2024-06-03T11:49:18 | {} | NONE |
vuejs | core | 2,146,664,623 | 11,064 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 91 kB | 34.6 kB | 31.2 kB |
| vue.global.prod.js | 148 kB | 53.8 kB | 48.1 kB |
### Usages
| Name | Size | Gzi... | 2024-06-04T05:49:48 | 2024-06-04T05:49:48 | {} | NONE |
vuejs | core | 1,902,165,372 | 10,165 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 91.1 kB | 34.6 kB | 31.2 kB |
| vue.global.prod.js | 148 kB | 53.9 kB | 48.2 kB |
### Usages
| Name | Size |... | 2024-01-20T16:16:07 | 2024-06-04T18:08:02 | {} | NONE |
vuejs | core | 2,109,710,290 | 10,882 | quiteeasy | @Doctor-wu, please review my pull request and the comments I've left on yours. I've highlighted some potential areas for improvement in both PRs. Your feedback and collaboration on these suggestions would be greatly appreciated. | 2024-05-14T09:24:41 | 2024-05-14T09:24:41 | {} | CONTRIBUTOR |
vuejs | core | 2,115,836,717 | 10,959 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.8 kB (**+56 B**) | 34.5 kB (**+24 B**) | 31.1 kB (**+27 B**) |
... | 2024-05-16T17:36:23 | 2024-05-17T12:16:08 | {} | NONE |
vuejs | core | 2,119,021,560 | 10,959 | skirtles-code | It wasn't immediately clear to me from the title and description, but this change affects all VNode-related hoisting, not just the hoisting of the VNodes themselves. e.g. Hoisted prop objects and dynamic prop arrays.
So this template code:
```html
<div :data-a="msg">
```
would now generate:
```js
const _... | 2024-05-18T22:46:30 | 2024-05-18T22:46:30 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,119,029,718 | 10,959 | antfu | Yeah, good points @skirtles-code, I shared the concerns as well. I didn't do much benchmark, but this was just a quick idea during my discussion with @sxzz, in which he might have better context for this).
I think at least this PR should not be merged as-is, and we either need to introduce a flag to opt-in, or/and t... | 2024-05-18T23:33:42 | 2024-05-18T23:33:42 | {} | MEMBER |
vuejs | core | 2,123,739,638 | 10,929 | Shyam-Chen | For workarounds:
```ts
watch(
value,
(newVal, oldVal) => {
swapOptions(newVal, oldVal);
},
{ flush: "post" },
);
```
Or use `v-model`:
https://play.vuejs.org/#eNqtVM2O0zAQfpWRT6kUUlo4laYSrFZiOQACbnEOaeK2XhI78k/aKsq7M7aTbqtFi4T2EGlmvm9+PZOefGzbpLOMrMhal4q3BupC7FNKjKYENDO23VDBm1YqAz0otovhWJjy... | 2024-05-22T02:07:59 | 2024-05-22T09:42:43 | {} | CONTRIBUTOR |
vuejs | core | 2,113,162,192 | 7,928 | AndreBooysen | please implement something to remove cached components via key. In my scenario I open dashboards (example /dashboard/:id) in different tabs. The users need to be able to tab between the dashboards without having to reload them (dashboards keeping their state). Everything works great except being able to remove the comp... | 2024-05-15T18:17:31 | 2024-05-15T18:17:31 | {} | NONE |
vuejs | core | 2,113,933,813 | 10,936 | edison1105 | duplicate of https://github.com/vuejs/core/issues/4662 | 2024-05-16T03:12:46 | 2024-05-16T03:12:46 | {} | MEMBER |
vuejs | core | 2,117,069,853 | 10,969 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.8 kB (**+110 B**) | 34.5 kB (**+35 B**) | 31.2 kB (**+99 B**)... | 2024-05-17T08:53:05 | 2024-05-17T08:53:05 | {} | NONE |
vuejs | core | 2,117,518,557 | 10,959 | edison1105 | Actually, this PR will not fix #5256
I prefer to generate the following code to avoid calling `hosted()` every time.
```js
export function render(_ctx, _cache) {
return (_openBlock(), _createElementBlock("div", null, [
_cache[1] || (_cache[1] = _hoisted_1()),
_createTextVNode(_toDisplayString(_ctx.foo... | 2024-05-17T12:42:57 | 2024-05-17T12:57:17 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,117,321,182 | 5,002 | MetRonnie | I think it would be really useful to have a directive called `v-provide` so that you can make any component a dependency provider without being required to add this to the component's `setup`, or having to user a wrapper component.
E.g.,
```vue
<!-- A root component -->
<template>
<div>
<component
... | 2024-05-17T10:59:12 | 2024-05-17T16:15:06 | {
"+1": 2
} | NONE |
vuejs | core | 2,119,177,095 | 10,978 | ibeladi-mrsool | I am not sure if the first part is for the core repo or https://github.com/vuejs/language-tools, if it is not for the core repo, please let me know and I will create a different issue there
For the second issue, if it is not valid, you can discard that
If both are invalid, I will close this issue and create one i... | 2024-05-19T10:02:27 | 2024-05-19T10:02:27 | {} | NONE |
vuejs | core | 2,126,504,686 | 10,999 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 1c790c2cba8cbf4507c311efe85616265cccbe0d |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vue... | 2024-05-23T08:15:54 | 2024-05-23T08:15:54 | {} | NONE |
vuejs | core | 2,112,518,955 | 10,748 | tonliver | @edison1105 What else can I do? | 2024-05-15T13:24:18 | 2024-05-15T13:24:18 | {} | CONTRIBUTOR |
vuejs | core | 2,117,069,249 | 10,963 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-17T08:52:45 | 2024-05-17T08:52:45 | {} | NONE |
vuejs | core | 2,120,579,314 | 10,982 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-05-20T14:29:26 | 2024-05-20T14:29:26 | {} | NONE |
vuejs | core | 2,123,840,606 | 10,990 | dinyo | sorry, i intended to zeroing the value to compare the effect. `number` is ignoring the 0 and keep adding. `numberRef` is set to 0 first before adding. | 2024-05-22T04:24:03 | 2024-05-22T04:24:03 | {} | NONE |
vuejs | core | 2,126,313,604 | 10,995 | Simon-He95 | > That would depend on the implementation of that component. Seems that it rendered nothing, maybe because of a v-if? I cant tell without seeing it这将取决于该组件的实现。似乎没有渲染任何内容，也许是因为 v-if？不亲眼所见我无法分辨
<img width="1658" alt="image" src="https://github.com/vuejs/core/assets/57086651/5a30e26f-8171-4d8e-add2-7c8e7722dea4">
It’s... | 2024-05-23T06:15:06 | 2024-05-23T06:15:06 | {} | CONTRIBUTOR |
vuejs | core | 2,109,689,773 | 10,939 | quiteeasy | In this PR, we lose the actual reference to the `.exp` property from the `:key` resolved in `transformElement.ts` within the returned function. As a result, the `keyProperty` injected as a prop in the `vFor.ts` exit function no longer references the actual expression of `keyProp`.
This change introduces bugs when w... | 2024-05-14T09:14:38 | 2024-05-14T09:14:38 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 2,116,975,561 | 10,813 | nongtan7898 | Thank you it's ok But if I want to add data to data, it still gives the same error even though I add
```
await nextTick();
```
Go in. Please take a look. I have commit in github.
@edison1105 | 2024-05-17T08:01:41 | 2024-05-17T08:01:41 | {} | NONE |
vuejs | core | 2,117,661,731 | 9,085 | zwacky | running into the same issue. did you find a solution to this? | 2024-05-17T13:53:20 | 2024-05-17T13:53:20 | {} | NONE |
vuejs | core | 2,120,205,138 | 10,869 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9157557577)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9153738484) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-05-20T10:57:01 | 2024-05-20T10:57:01 | {} | CONTRIBUTOR |
vuejs | core | 2,126,505,098 | 10,999 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 1c790c2cba8cbf4507c311efe85616265cccbe0d |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/s... | 2024-05-23T08:16:08 | 2024-05-23T08:16:08 | {} | NONE |
vuejs | core | 2,117,232,719 | 10,970 | liuhanqu | ```js
watch( () => props.propData, () => {})
```
`props.propsData` is not ref. | 2024-05-17T10:17:40 | 2024-05-17T10:17:40 | {} | NONE |
vuejs | core | 2,117,556,951 | 10,970 | CGQAQ | https://github.com/vuejs/core/blob/main/packages/runtime-core/src/apiWatch.ts#L241-L281
```js
if (isRef(source)) {
getter = () => source.value
forceTrigger = isShallow(source)
} else if (isReactive(source)) {
getter = () => reactiveGetter(source)
forceTrigger = true
} else if (isArray(source... | 2024-05-17T13:02:28 | 2024-05-17T13:03:06 | {} | NONE |
vuejs | core | 2,118,470,382 | 10,964 | ferreraa | The problem seems to be related to the function syntax used.
A workaround to the issue is to define your default function that way `default: () => { return ''; }` | 2024-05-17T23:00:12 | 2024-05-17T23:00:12 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,120,285,067 | 10,938 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/9158043319)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/9153738484) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-05-20T11:39:24 | 2024-05-20T11:39:24 | {} | CONTRIBUTOR |
vuejs | core | 2,120,521,443 | 10,517 | haoqunjiang | Closing due to lack of reproduction. | 2024-05-20T13:59:11 | 2024-05-20T13:59:11 | {} | MEMBER |
vuejs | core | 2,105,428,286 | 10,886 | neneodonkor | From the docs it says: `.number` cast valid input string to numbers.
I think it means strings that are being typed into an input or text box. With the radio button you are not inputing any text. You are just changing the state of the radio button from checked to unchecked. And you have an attribute with the name value... | 2024-05-11T01:12:19 | 2024-05-21T11:39:52 | {} | NONE |
vuejs | core | 2,122,885,655 | 10,985 | avivkeller | As far as I know, `pull_requests[0]` with the `pull_request` event will always be the submitted PR. | 2024-05-21T15:24:53 | 2024-05-21T15:25:01 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,109,652,259 | 10,941 | dten | scoped styles work by requiring the final matcher also matching being from the component
so your can see in your link the compiled css looks as follows
and since your inner div is a div which is the first child within a div then it matches. in this case the outer div is waaay above your component. but this is how... | 2024-05-14T08:57:51 | 2024-05-14T08:57:51 | {} | NONE |
vuejs | core | 2,109,720,454 | 10,784 | quiteeasy | close #10655 | 2024-05-14T09:29:13 | 2024-05-14T09:29:13 | {} | CONTRIBUTOR |
vuejs | core | 2,110,787,941 | 10,946 | LinusBorg | You should likely open this issue in the vite repo, or the `create-vue` repo. This is about the build tooling, not the vue core runtime. | 2024-05-14T17:43:36 | 2024-05-14T17:43:36 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,111,735,702 | 10,908 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-15T07:02:39 | 2024-05-15T07:02:39 | {} | NONE |
vuejs | core | 2,113,973,905 | 4,662 | truthtenfold | Three years and still no resolution. This problem is not so simple to solve. The context of the webcomponent needs to be maintained, and the inserted style tags need to be marked to prevent repeated insertion when the component is used multiple times. Currently, I deprecated scoped, and all styles are imported into .ce... | 2024-05-16T03:49:41 | 2024-05-16T03:49:41 | {
"confused": 5,
"heart": 4
} | NONE |
vuejs | core | 2,114,202,570 | 10,929 | Shyam-Chen | https://eslint.vuejs.org/rules/require-v-for-key.html | 2024-05-16T06:55:37 | 2024-05-16T06:55:37 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,115,018,186 | 4,314 | cyfung1031 | @yyx990803 Almost 3 years passed. Any update? Even just a sentence to explain why this is not an option. | 2024-05-16T11:49:18 | 2024-05-16T11:49:18 | {
"+1": 3
} | NONE |
vuejs | core | 2,122,441,563 | 10,886 | neneodonkor | @YiMo1 感謝 | 2024-05-21T11:40:58 | 2024-05-21T11:40:58 | {} | NONE |
vuejs | core | 2,123,840,811 | 10,990 | Shyam-Chen | ```diff
number.value = 0;
- number.value += 1;
+ nextTick(() => {
+ number.value += 1;
+ });
``` | 2024-05-22T04:24:21 | 2024-05-22T04:24:29 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,125,053,781 | 9,417 | skirtles-code | I don't think these changes can be merged. Changing the runtime behaviour for watching a reactive array will break too many real applications.
I found it interesting that the changes proposed here didn't trigger any test failures. I opened #10848 (now merged) to try to address that. Several of those tests would fail... | 2024-05-22T15:12:59 | 2024-05-22T15:12:59 | {} | CONTRIBUTOR |
vuejs | core | 2,126,301,961 | 10,991 | Math-chen | 这个和vue没关系，应该是你在vite中加的插件vite-plugin-top-level-await导致的问题，导入所有模块可以使用const modules = import.meta.glob('./dir/*.js', { eager: true }) | 2024-05-23T06:05:04 | 2024-05-23T06:05:04 | {
"+1": 1
} | NONE |
vuejs | core | 2,116,769,898 | 10,966 | LinusBorg | Correct analysis by @warunacds
Your computed returns a copy of the reactive array, and that copy is plain, non-reactive. changing it (i.e. by pushing to it) will not trigger any reactive effects. | 2024-05-17T05:59:20 | 2024-05-17T05:59:20 | {
"heart": 2
} | MEMBER |
vuejs | core | 2,119,032,777 | 10,959 | antfu | For a bit more context, this was brought up when we were discussing about the `up-front initiation cost` and `GC for hoisted objects` that the hoisted approach introduced. Without hoisting, all those objects were created with as the component being used, and disposed by GC when all instances of the component get unrefe... | 2024-05-18T23:50:52 | 2024-05-18T23:50:52 | {
"eyes": 2
} | MEMBER |
vuejs | core | 2,109,705,958 | 10,942 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| v... | 2024-05-14T09:22:33 | 2024-05-20T07:18:33 | {} | NONE |
vuejs | core | 2,121,959,719 | 10,985 | Disservin | out of curiosity, what is wrong with `${{ github.event.number }}` ? | 2024-05-21T07:38:22 | 2024-05-21T07:38:31 | {} | CONTRIBUTOR |
vuejs | core | 2,122,737,389 | 10,987 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48.1 kB |
### Usages
| Name | Size |... | 2024-05-21T14:13:51 | 2024-05-21T14:13:51 | {} | NONE |
vuejs | core | 2,126,089,854 | 10,994 | Shyam-Chen | > https://github.com/vuejs/babel-plugin-jsx/issues/710 | 2024-05-23T02:47:45 | 2024-05-23T02:47:45 | {} | CONTRIBUTOR |
vuejs | core | 2,127,374,109 | 575 | camiloforero | @craigrileyuk solution works excellently for all cases I could think of
I created [a playground example](https://play.vuejs.org/#eNq9VMtu2zAQ/JUtU8AJ4FiH9OQ6Afow0PbQFo2BHMqiUKy1rVQiCZJSbBj69y5pPW1HfRgI4AO5s8sZ7c56y94oNcozZGM2MXMdKwsGbaZuuIhTJbWFLWhcQAELLVMYUOqghm4Tae90qBTqEh4FrZh7d/CaCy7mUhgLqVnCtXvtfPABk0TCndRJ9GJw... | 2024-05-23T15:04:55 | 2024-05-23T15:47:18 | {
"+1": 4
} | NONE |
vuejs | core | 2,110,806,664 | 10,943 | LinusBorg | * As soon as `temp.value >= 80` evaluates to `true`, the Javascript runtime will no longer evaluate the second condition (`height.value >= 80`)
* Consequently, `height.value` isn't being accessed anymore,
* and consequently, it no longer is a reactive dependency of the effect.
This is indeed a small footgun in `w... | 2024-05-14T17:55:40 | 2024-05-14T17:55:40 | {} | MEMBER |
vuejs | core | 2,118,982,520 | 10,977 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.8 kB (**+34 B**) | 34.5 kB (**+14 B**) | 31.1 kB (**+10 B**) |
... | 2024-05-18T19:22:08 | 2024-05-18T19:22:08 | {} | NONE |
vuejs | core | 2,119,520,929 | 10,980 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-20T01:41:42 | 2024-05-20T01:41:42 | {} | NONE |
vuejs | core | 2,126,211,725 | 10,995 | LinusBorg | ```js
import { creatApp, h } from 'vue'
import App from 'App.vue'
const app = createApp({
onMounted() {
// do what you need here
},
render: () => h(App)
})
``` | 2024-05-23T04:33:34 | 2024-05-23T04:33:34 | {} | MEMBER |
vuejs | core | 2,111,398,167 | 10,943 | KaixinTree | I see. Thank you for your time.thank you! | 2024-05-15T01:01:38 | 2024-05-15T01:01:38 | {} | NONE |
vuejs | core | 2,115,870,815 | 10,959 | kermanx | I am wondering if it is worth it to init hoisted v-nodes lazily🥺
- Hoisted v-nodes are now functions, and have to be called in every rendering, which introduces some new costs.
- Hoisted v-nodes are created lazily in this PR, but they still can't be released after they are no longer used. So the improvement of mem... | 2024-05-16T17:56:19 | 2024-05-16T17:57:43 | {} | CONTRIBUTOR |
vuejs | core | 2,119,191,185 | 7,475 | PeterEsenwa | @baiwusanyu-c, is this PR ready to go through? I can try to fix the failing test, if that is all that is left. | 2024-05-19T10:54:46 | 2024-05-20T09:17:55 | {} | NONE |
vuejs | core | 2,123,801,414 | 10,989 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 90.9 kB (**+144 B**) | 34.5 kB (**+39 B**) | 31.1 kB (**+14 B**)... | 2024-05-22T03:29:33 | 2024-05-22T03:29:33 | {} | NONE |
vuejs | core | 2,125,907,169 | 10,948 | Tjaitil | +1. I have also searched high and low for the very same thing you are describing. It seems like a big limitation in defineCustomElement to not being able to pass arguments to the underlying CustomElement constructor. In this case attachInternals & static formAssociated properties.
Did you find any solution to your p... | 2024-05-22T22:49:10 | 2024-05-22T23:01:29 | {} | NONE |
vuejs | core | 2,126,315,446 | 10,995 | Simon-He95 | I will give you a warehouse address later. Are you interested in helping track it down? | 2024-05-23T06:16:38 | 2024-05-23T06:16:38 | {} | CONTRIBUTOR |
vuejs | core | 2,126,987,436 | 9,783 | xvaara | @yyx990803 could we have this merged? It's weird that you have to have have an "or" in the to prop:
```vue
<Teleport :to="props.teleportTo || 'body'" :disabled="!props.teleportTo">
```
if you forget, the ssr doesn't render the content anywhere. | 2024-05-23T12:29:19 | 2024-05-23T12:31:04 | {} | NONE |
vuejs | core | 2,095,103,193 | 10,869 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 90.7 kB (**+6 B**) | 34.5 kB (**+3 B**) | 31.1 kB (**+16 B**) |
| vue.... | 2024-05-06T02:43:00 | 2024-05-15T11:50:25 | {} | NONE |
vuejs | core | 2,118,989,965 | 10,066 | 719media | Don't forget about this important issue! Could it be added to https://github.com/orgs/vuejs/projects/13 ? | 2024-05-18T20:00:52 | 2024-05-18T20:00:52 | {} | NONE |
vuejs | core | 2,113,393,441 | 10,813 | AtesComp | I've just checked against 3.4.27 and the errors have evaporated.
Having read the release info for 3.4.27, it leaves me perplexed about the error. Something in the code changes effectively "fixed" the cause of the error. I've looked over the various changed code files with a diff between 3.4.23 and 3.4.24 and betwe... | 2024-05-15T20:24:38 | 2024-05-15T20:24:38 | {} | NONE |
vuejs | core | 2,118,247,202 | 10,959 | antfu | After a second thought, I think having a flag to opt in is probably better. The lazies might have benefit only when many components bundled into a single entry, where in normal app structure, components especially routes are splitter intro dynamic chunks, which by itself is lazy already. Maybe it can be an optimization... | 2024-05-17T19:28:29 | 2024-05-17T19:28:29 | {} | MEMBER |
vuejs | core | 2,119,521,022 | 10,981 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 90.7 kB | 34.5 kB | 31.1 kB |
| vue.global.prod.js | 148 kB | 53.7 kB | 48 kB |
### Usages
| Name | Size |... | 2024-05-20T01:41:51 | 2024-05-20T01:41:51 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.