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,306,389,596 | 6,376 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.6 kB | 33.9 kB |
| vue.global.prod.js | 158 kB | 57.5 kB | 51.2 kB |
### Usages
| Name | Size | Gzi... | 2024-08-23T06:34:31 | 2024-08-29T06:19:02 | {} | NONE |
vuejs | core | 2,317,585,214 | 11,736 | vphatfla | @jh-leong , this issue has been there for a while, bootstrap folks are not removing the **important** from the **d-flex** class.
Why can't we add the **!important** attribute for **v-for**?
https://github.com/twbs/bootstrap/issues/22076 | 2024-08-29T12:56:10 | 2024-08-29T12:56:10 | {} | NONE |
vuejs | core | 2,319,704,784 | 11,747 | edison1105 | see https://v3-migration.vuejs.org/breaking-changes/attribute-coercion.html | 2024-08-30T02:21:19 | 2024-08-30T02:24:35 | {} | MEMBER |
vuejs | core | 2,306,349,445 | 5,717 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 100 kB (**+22 B**) | 37.6 kB (**+6 B**) | 33.9 kB (**-9 B**) |
| vue.... | 2024-08-23T05:59:45 | 2024-08-29T00:49:23 | {} | NONE |
vuejs | core | 2,316,594,688 | 11,733 | Kanade-Lu | Sorry for the late reply
```json
{
"include": [
"src/**/*.ts",
"src/**/*.tsx",
"src/**/*.vue",
"tests/**/*.ts",
"tests/**/*.tsx",
"./components.d.ts",
"./auto-imports.d.ts"
],
"typeAcquisition": { "include": ["jest"] },
"exclude": ["node_modules", "./www", "./src/plugi... | 2024-08-29T02:28:39 | 2024-08-29T02:28:56 | {} | NONE |
vuejs | core | 2,316,799,087 | 6,359 | yyx990803 | This is no longer needed in 3.5 after 313e4bf55 | 2024-08-29T06:19:07 | 2024-08-29T06:19:07 | {} | MEMBER |
vuejs | core | 2,317,905,129 | 11,736 | jh-leong | You can find related discussions in https://github.com/vuejs/vue/issues/3761.
- This is not a common case.
- Using `!important` is not recommended, as it can make overriding styles difficult and may break existing behavior if `v-show` applies `!important`.
- There are several simple workarounds mentioned in https... | 2024-08-29T14:37:10 | 2024-08-29T14:37:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,317,909,637 | 7,387 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29429578204"><code>2dfd8e1</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@7387
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://... | 2024-08-29T14:38:32 | 2024-08-29T14:38:32 | {} | NONE |
vuejs | core | 2,320,349,724 | 11,738 | bosens-China | @edison1105 After seeing your reply, I still find it somewhat counterintuitive. I mounted the current reactive type to the window object in the main window, and in the child iframe, it is also accessed based on the parent. They point to the same memory address. However, when modifying it in the child iframe, the reacti... | 2024-08-30T07:35:09 | 2024-08-30T07:35:33 | {} | NONE |
vuejs | core | 2,320,695,234 | 11,738 | edison1105 | 
You can set a breakpoint here. When the key is title, activeEffect is undefined, so no dependencies are tracked. This happens because activeEffect is still within the context of the main application, not the iframe. This might oc... | 2024-08-30T09:50:46 | 2024-08-30T09:51:30 | {} | MEMBER |
vuejs | core | 2,323,212,858 | 7,169 | tolking | I feel like the problem has been fixed [Link](https://github.com/vuejs/core/commit/7b18cdb0b53a94007ca6a3675bf41b5d3153fec6) | 2024-09-01T07:37:35 | 2024-09-01T07:37:35 | {} | CONTRIBUTOR |
vuejs | core | 2,314,987,544 | 11,733 | jh-leong | Also, could you please provide your `tsconfig.json` | 2024-08-28T10:54:32 | 2024-08-28T10:54:32 | {} | MEMBER |
vuejs | core | 2,316,546,204 | 11,736 | jh-leong | <img width="986" alt="image" src="https://github.com/user-attachments/assets/730df74d-9c52-4121-9077-513ae02d3ce5">
This issue is related to CSS specificity rather than Vue itself.
The `v-show` directive applies `display: none`, but if you also have a class like `d-flex` with `display: flex !important`, the CSS ... | 2024-08-29T01:31:43 | 2024-08-29T01:31:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,316,775,866 | 11,738 | edison1105 | When Vue.js is loaded separately in both the main application (`Parent.vue`) and the embedded `iframe`, their memory variables are not shared. This results in the following behavior during rendering and updates:
1. **Independent Memory Space**: Since Vue.js is loaded separately in the main application and the `ifram... | 2024-08-29T05:59:40 | 2024-08-29T05:59:40 | {} | MEMBER |
vuejs | core | 2,318,017,996 | 7,387 | zhangzhonghe | I just checked and found that this fix is not working in a production environment, so I will close this PR. Maybe the fix at https://github.com/vuejs/core/pull/6238 is right. | 2024-08-29T15:07:17 | 2024-08-29T15:15:40 | {} | MEMBER |
vuejs | core | 2,320,256,746 | 11,733 | Kanade-Lu | same issue #11272
seem can be fixed by #11644 | 2024-08-30T06:52:51 | 2024-08-30T06:52:51 | {} | NONE |
vuejs | core | 2,320,462,129 | 11,754 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.7 kB | 33.9 kB |
| vue.global.prod.js | 159 kB | 57.5 kB | 51.1 kB |
### Usages
| Name | Size | Gzi... | 2024-08-30T08:21:33 | 2024-08-30T08:21:33 | {} | NONE |
vuejs | core | 2,322,744,721 | 11,760 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29504004817"><code>b64b51a</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11760
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-31T03:06:08 | 2024-08-31T03:25:49 | {} | NONE |
vuejs | core | 2,316,359,287 | 11,728 | skirtles-code | I just gave this a try, but it seems that the prop hoisting breaks it:
- [Playground - this PR](https://deploy-preview-11728--vue-sfc-playground.netlify.app/#eNp9kUFPAjEQhf/KpBc0IMToiSxEJRz0oEY99oJlFgvdtmmniCH7352WgJIQbjvvfTN5b7sV99731wnFUFRRBe0JIlLyY2l1410g2ELAGlqog2ugw2hHWmmVs5FAuWQJRpm4uL6UthrsbvA2D4SNNzNCngAOE6y... | 2024-08-28T22:36:42 | 2024-08-28T22:36:42 | {} | CONTRIBUTOR |
vuejs | core | 2,316,595,731 | 11,735 | adamdehaven | > a side note: this only happens in DEV.
This _could_ be correct; however, I’m not 100% sure.
With a more complicated example, I see some properties are totally omitted; it’s not just the difference in slashes.

| 2024-08-29T02:29:44 | 2024-08-29T02:33:11 | {} | NONE |
vuejs | core | 2,319,650,176 | 6,238 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/10625326008)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/10590467405) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2024-08-30T01:43:15 | 2024-08-30T01:43:15 | {} | CONTRIBUTOR |
vuejs | core | 2,320,301,128 | 11,745 | edison1105 | > @edison1105 This issue here is not related to SSR. If this is a duplicate, does that mean that #11273 is also not related to SSR?
Neither of them is related to SSR.
The underlying problem is the same. The imported bindings are not returned from setup.

提交: eaa41d57266683296de7d118f574d0c2652e1fc4
日期: 2024-08-07T20:16:39.455Z
Electron: 30.1.2
ElectronBuildId: 9870757
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 22.5.0 | 2024-08-28T10:41:36 | 2024-08-28T10:41:36 | {} | NONE |
vuejs | core | 2,316,590,726 | 11,739 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29400289061"><code>977261d</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11739
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-29T02:24:38 | 2024-08-29T02:24:38 | {} | NONE |
vuejs | core | 2,316,800,724 | 6,376 | yyx990803 | The fix is no longer needed in 3.5 after 313e4bf55, but the test case is merged as it is useful to prevent future regressions. | 2024-08-29T06:20:32 | 2024-08-29T06:20:32 | {} | MEMBER |
vuejs | core | 2,317,341,759 | 11,745 | LinusBorg | We will have a hard time investigating this without a way to reproduce it. | 2024-08-29T11:09:06 | 2024-08-29T11:09:06 | {} | MEMBER |
vuejs | core | 2,320,281,870 | 11,319 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29463051054"><code>9a14e9d</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11319
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-30T07:04:55 | 2024-08-30T07:04:55 | {} | NONE |
vuejs | core | 2,320,335,262 | 11,675 | edison1105 | @xieyuschen This PR is not a high priority and may not be merged as quickly | 2024-08-30T07:28:48 | 2024-08-30T07:28:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,316,111,947 | 5,717 | skirtles-code | @edison1105 Properties in `data` are allowed to start with `_` or `$`. It's been documented as allowed for a long time:
- https://vuejs.org/api/options-state.html#data
- https://v2.vuejs.org/v2/api/#data
I don't think we should be adding a warning for that.
The key thing is that they aren't proxied through th... | 2024-08-28T19:37:10 | 2024-08-28T19:37:10 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,316,795,763 | 6,358 | yyx990803 | This is now triggering twice in 3.5 - once for `ref` being mutated, and once for `.value` being mutated as a proxied property. IMO triggering twice is the expected behavior. | 2024-08-29T06:16:15 | 2024-08-29T06:16:15 | {} | MEMBER |
vuejs | core | 2,316,808,482 | 11,724 | artmakarov | > I want to contribute to this issue. But before that, is it correct that to solve this problem, we still need to set a key when using v-if, and the goal is to not expose that key as a prop of the slot?
Yes, that's right. But the physically set `key` prop must be passed. | 2024-08-29T06:26:47 | 2024-08-29T06:29:46 | {
"+1": 2
} | NONE |
vuejs | core | 2,317,906,296 | 7,387 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 37.7 kB | 33.9 kB |
| vue.global.prod.js | 159 kB | 57.5 kB | 51.1 kB |
### Usages
| Name | Size | Gzi... | 2024-08-29T14:37:31 | 2024-08-29T14:37:31 | {} | NONE |
vuejs | core | 2,320,462,751 | 11,754 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29465962052"><code>80bfbbe</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11754
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-30T08:21:46 | 2024-08-30T08:21:46 | {} | NONE |
vuejs | core | 2,307,599,357 | 11,702 | alexanderturinske | May be related to https://github.com/vuejs/core/issues/4566#issuecomment-917997056
This PR does not fix the solution, but starts TDD with a test | 2024-08-23T18:27:20 | 2024-08-23T18:30:38 | {} | NONE |
vuejs | core | 2,308,030,047 | 11,703 | makedopamine | Have changed the permission to public for the link. | 2024-08-24T03:33:10 | 2024-08-24T08:17:03 | {} | CONTRIBUTOR |
vuejs | core | 2,308,860,356 | 4,339 | fgt1t5y | > > > > 这个特性能用了吗?
> > >
> > >
> > > 想多了
> >
> >
> > 我真服了,我直接patch源代码得了
>
> 我用的都是楼上的一个大牛的方案做的,等这个特性要死人的
大概率unplanned了...
刚把源代码patch了一下,先凑合用吧,反正patch能跟着项目走

| 2024-08-25T14:00:11 | 2024-08-25T14:00:11 | {
"+1": 1
} | NONE |
vuejs | core | 2,309,677,785 | 11,717 | l123wx | https://play.vuejs.org/#eNqtVl9z2jgQ/yoav0AyDk766JLMZfJnLndpe9Ne7wXzIOwFFITkkWQIw/DdbyXZwi5cy6V9SazV7m///HZXbKPbshysKojSaGhgWXJq4CYThAwXAOUF5WwFJGUi51UB11mU03wOz0ybLHJqqJjLZSkFCIN6GlVWDNZ6RHODpv/g90e6hHEWkXQBG7zuXqA88f6SvUMUOFHBVmR1waZopedyfdfy/eQjIvaYkhHZbkkIbfAimej34t4Z2e3IeJggjvcxUf6/Fdy6OIgNJLXm3bjQ8lu7YFnnzURZGcKK... | 2024-08-26T08:44:45 | 2024-08-26T08:44:45 | {} | NONE |
vuejs | core | 2,311,726,367 | 11,458 | GalacticHypernova | Alright thank you! | 2024-08-27T07:03:00 | 2024-08-27T07:03:00 | {} | CONTRIBUTOR |
vuejs | core | 2,314,864,289 | 11,733 | jh-leong | This seems to only happen in the playground; I can't reproduce this locally in VSCode either.
Did you try updating the `Vue - Official` extension to the latest version? | 2024-08-28T09:54:29 | 2024-08-28T09:54:29 | {} | MEMBER |
vuejs | core | 2,309,801,090 | 11,458 | GalacticHypernova | Hey @edison1105 ,
I'm working on condition-based delayed hydration (a "hydrate if/when something is true" scenario) for general purpose use, which I would need to watch for changes in the hydration strategy to then call hydrate. I have this code to demonstrate:
```ts
// componentLoader is the dynamic import, attrs... | 2024-08-26T09:46:46 | 2024-08-26T09:50:55 | {} | CONTRIBUTOR |
vuejs | core | 2,306,659,312 | 11,696 | riskysciolism | It does not work fine in v3.4.
It does work fine in v3.3. | 2024-08-23T09:14:54 | 2024-08-26T09:58:48 | {} | NONE |
vuejs | core | 2,310,939,719 | 11,718 | skirtles-code | Could you add a test for this? | 2024-08-26T19:37:25 | 2024-08-26T19:37:25 | {} | CONTRIBUTOR |
vuejs | core | 2,309,827,623 | 11,718 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29289553021"><code>f664639</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11718
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-26T10:00:19 | 2024-08-27T05:24:51 | {} | NONE |
vuejs | core | 2,309,154,548 | 11,708 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29341643283"><code>b71cd79</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11708
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-26T01:58:33 | 2024-08-28T01:45:22 | {} | NONE |
vuejs | core | 2,313,982,785 | 11,721 | edison1105 | uh... sorry, I think I got my thoughts mixed up just now. 😓
I prefer type 2 by the way. | 2024-08-28T02:37:21 | 2024-08-28T02:37:59 | {} | MEMBER |
vuejs | core | 2,311,413,305 | 11,458 | edison1105 | @GalacticHypernova
I think this usage is fine | 2024-08-27T01:50:04 | 2024-08-27T01:50:04 | {} | MEMBER |
vuejs | core | 2,311,426,879 | 7,809 | edison1105 | Duplicate of #8539 | 2024-08-27T02:03:39 | 2024-08-27T02:03:39 | {} | MEMBER |
vuejs | core | 2,309,827,315 | 11,718 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 99.1 kB (**+18 B**) | 37.5 kB (**+11 B**) | 33.8 kB (**-22 B**) |
... | 2024-08-26T10:00:10 | 2024-08-27T05:18:28 | {} | NONE |
vuejs | core | 2,307,856,698 | 10,609 | mashpie | usually I don't express any emotion... and pleas don't get me wrong I don't mean to blame anyone. I came to this issue because of:
```
[nuxt] [request error] [unhandled] [500] decode_js.EntityDecoder is not a constructor
at new Tokenizer (./.output/server/chunks/routes/renderer.mjs:15285:28)
at ./.output/serv... | 2024-08-23T21:52:47 | 2024-08-23T21:55:42 | {} | NONE |
vuejs | core | 2,309,709,962 | 8,621 | edison1105 | see https://github.com/vuejs/core/issues/8629#issuecomment-1603875593 | 2024-08-26T09:00:51 | 2024-08-26T09:00:51 | {} | MEMBER |
vuejs | core | 2,313,906,004 | 11,724 | linzhe141 | Vue internally sets a key for elements using v-if
[It might be related to this pull request.](https://github.com/vuejs/core/pull/11323)
https://github.com/vuejs/core/blob/342657b717a8e1de7792fde6c418bfa5eb5245cd/packages/compiler-core/src/transforms/vIf.ts#L40-L63 | 2024-08-28T01:25:53 | 2024-08-28T01:26:53 | {} | MEMBER |
vuejs | core | 2,314,810,295 | 11,731 | edison1105 | the cause is here https://github.com/vuejs/core/blob/741d8a0710e08c925da2511ce764aa87c4a291d9/packages/compiler-core/src/transforms/transformElement.ts#L345-L351
| 2024-08-28T09:29:45 | 2024-08-28T09:29:45 | {} | MEMBER |
vuejs | core | 2,314,848,867 | 4,051 | yyx990803 | Fixed by https://github.com/vuejs/core/pull/10801 | 2024-08-28T09:47:10 | 2024-08-28T09:47:10 | {} | MEMBER |
vuejs | core | 2,311,776,976 | 11,721 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------------------ | ------------------ | ------------------- |
| runtime-dom.global.prod.js | 99 kB (**-25 B**) | 37.5 kB (**+1 B**) | 33.8 kB (**+45 B**) |
| vue.... | 2024-08-27T07:33:37 | 2024-08-28T09:51:51 | {} | NONE |
vuejs | core | 2,308,474,499 | 11,695 | dsonet | It reduces the memory usage as well. | 2024-08-24T17:58:34 | 2024-08-24T17:58:34 | {} | CONTRIBUTOR |
vuejs | core | 2,308,803,866 | 11,706 | LinusBorg | This is expected. Calls that need to be aware of the current component context need to happen synchronously in setup.
We do work around that limitation in `script setup` with the compiler, but in normal components, the above limitation applies. | 2024-08-25T12:03:05 | 2024-08-25T12:03:33 | {} | MEMBER |
vuejs | core | 2,309,215,919 | 11,715 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29232323271"><code>addc24f</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11715
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-26T03:11:34 | 2024-08-26T03:11:34 | {} | NONE |
vuejs | core | 2,309,602,414 | 8,662 | zhangenming | maybe resolved by v3.4.32
https://play.vuejs.org/#eNp9UstOwzAQ/JWVL6RS5QoCl/CQeB3gAAi41RUKybZ1SW3Lj7aoyr+zcUgLqPQSOTuzs7Njr9mlMXwRkGXszBVWGg8OfTAXQsm50dbDGizmhZcL7IOb5lWll8/fBahhbPUcDkjgQCihCq2ch9za/BPO/7KT4ah3Ch2JpuygKFzCC/qk1zvtiPp9RsTOQ7KGPIMTqEmKtISKw7gJbpoQs2kjZZ6XZffb6ugKeaUnyZBzHltGfWjORB71D4/SNO3BYACvU3QIpRyP0... | 2024-08-26T08:06:49 | 2024-08-26T08:06:49 | {} | CONTRIBUTOR |
vuejs | core | 2,309,737,384 | 11,717 | edison1105 | a workaround
```vue
:include="[...cacheList]"
``` | 2024-08-26T09:13:57 | 2024-08-26T09:13:57 | {} | MEMBER |
vuejs | core | 2,314,754,064 | 11,725 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 99.1 kB | 37.5 kB | 33.8 kB |
| vue.global.prod.js | 157 kB | 57.3 kB | 51 kB |
### Usages
| Name | Size |... | 2024-08-28T09:03:39 | 2024-08-28T09:03:39 | {} | NONE |
vuejs | core | 1,705,151,010 | 7,419 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 99.1 kB | 37.5 kB | 33.8 kB |
| vue.global.prod.js | 157 kB | 57.3 kB | 51 kB |
### Usages
| Name | Size |... | 2023-09-04T12:03:55 | 2024-08-28T09:49:20 | {} | NONE |
vuejs | core | 2,309,168,770 | 11,710 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29357954741"><code>5926825</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11710
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-26T02:15:33 | 2024-08-28T09:54:59 | {} | NONE |
vuejs | core | 2,306,770,026 | 10,567 | zewt | Running into this too. It seems like :deep just doesn't understand nested selectors, which is a bit of a showstopper. Putting :global around every nested selector in a complex stylesheet makes quite a mess...
| 2024-08-23T10:14:39 | 2024-08-23T10:14:39 | {} | NONE |
vuejs | core | 2,308,855,989 | 4,339 | cons2act | > > > 这个特性能用了吗?
> >
> >
> > 想多了
>
> 我真服了,我直接patch源代码得了
我用的都是楼上的一个大牛的方案做的,等这个特性要死人的 | 2024-08-25T13:53:50 | 2024-08-25T13:53:50 | {} | NONE |
vuejs | core | 2,309,159,229 | 6,819 | edison1105 | I prefer the proposal in this PR to https://github.com/vuejs/rfcs/discussions/587. This implementation is more flexible, giving the user control over exactly what is returned, rather than just returning a boolean value.
| 2024-08-26T02:03:51 | 2024-08-26T02:03:51 | {} | MEMBER |
vuejs | core | 2,309,195,868 | 11,703 | makedopamine | > This is not a bug, it was a documented breaking change in Vue 3
Thank you for clarifying that. I missed that detail in the documentation. | 2024-08-26T02:47:53 | 2024-08-26T02:47:53 | {} | CONTRIBUTOR |
vuejs | core | 2,310,397,956 | 11,716 | LinusBorg | `effect` runs synchronously, `watchEffect` runs on next Tick when triggered by a reactive change.
`watch` doesn't run it's callback at all because the getter returns `1` both times, so there's no need to run the callback | 2024-08-26T14:47:00 | 2024-08-26T14:52:10 | {} | MEMBER |
vuejs | core | 2,314,754,595 | 11,725 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29355455767"><code>91ec974</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11725
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-28T09:03:54 | 2024-08-28T09:03:54 | {} | NONE |
vuejs | core | 2,308,757,039 | 11,458 | GalacticHypernova | Can Vue methods like watch/ref be used inside custom hydration strategies? | 2024-08-25T09:51:57 | 2024-08-25T09:51:57 | {} | CONTRIBUTOR |
vuejs | core | 2,309,087,319 | 11,478 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29229072388"><code>e46dfdd</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11478
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-26T00:43:47 | 2024-08-26T00:43:47 | {} | NONE |
vuejs | core | 2,309,249,402 | 11,712 | edison1105 | https://github.com/vuejs/core/blob/4b608a9449fcfaa9c6105c96573ed30b599d2800/packages/runtime-core/src/scheduler.ts#L264
This is validation in the development environment, not in the production environment. | 2024-08-26T03:48:00 | 2024-08-26T03:48:00 | {} | MEMBER |
vuejs | core | 2,309,585,966 | 11,716 | edison1105 | That's expected behavior. What's your confusion? | 2024-08-26T07:58:18 | 2024-08-26T07:58:18 | {} | MEMBER |
vuejs | core | 2,309,635,268 | 11,716 | zhangenming | Why is the result of effect/watchEffect and watch inconsistent? I expect the result to be consistent
In this case, the watch will not be has a reactive responsive
| 2024-08-26T08:23:14 | 2024-08-26T08:23:14 | {} | CONTRIBUTOR |
vuejs | core | 2,310,862,896 | 2,349 | nolimitdev | Hooks activated and deactivated still not supported for plugins after almost 4 years :( It really complicates plugins for custom directives v-custom-directive="...". | 2024-08-26T18:56:36 | 2024-08-26T18:56:36 | {
"+1": 2
} | NONE |
vuejs | core | 2,311,354,716 | 11,720 | edison1105 | This is the intended behavior. The `model` is a custom ref and only triggers when `.value` is replaced. | 2024-08-27T00:44:36 | 2024-08-27T00:44:36 | {
"+1": 2,
"confused": 3
} | MEMBER |
vuejs | core | 2,311,478,597 | 9,663 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29286305880"><code>4247ccf</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@9663
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https://... | 2024-08-27T03:05:45 | 2024-08-27T03:05:45 | {} | NONE |
vuejs | core | 2,311,645,985 | 10,193 | edison1105 | Thanks for this PR.
Closing as the problem has been fixed via https://github.com/vuejs/core/pull/8304. | 2024-08-27T06:06:12 | 2024-08-27T06:06:12 | {} | MEMBER |
vuejs | core | 2,313,871,304 | 11,721 | edison1105 | @HEGGRIA
<s>This change is incorrect. When `batchDepth` is 1, both type 1 and type 2 will early return. It's not consistent with the following logic.
```ts
if (batchDepth > 1) {
batchDepth--
return
}
batchDepth--
//...
```
</s> | 2024-08-28T00:47:40 | 2024-08-28T02:26:24 | {} | MEMBER |
vuejs | core | 2,314,847,579 | 8,825 | yyx990803 | Looks like this is fixed by https://github.com/vuejs/core/pull/10801 | 2024-08-28T09:46:34 | 2024-08-28T09:46:34 | {} | MEMBER |
vuejs | core | 2,307,869,689 | 10,609 | mashpie | ...for reference (as @lzl0304 stated) the output of `pnpm why entities -r` shows a mix of entities@4.5.0 and entities@2.1.0
[why.txt](https://github.com/user-attachments/files/16734017/why.txt)
| 2024-08-23T22:08:33 | 2024-08-23T22:30:09 | {
"hooray": 1
} | NONE |
vuejs | core | 2,308,041,193 | 11,703 | Trandx | in this case, you can add a settimeout and inside this, add tailwind animation or custom css animation.
eg:
```
@click="removeAnimation"
const timer = 500;
const elt = ref()
const animeClass = 'fade-out'
const removeAnimation = () => {
elt.value?.attribList.add(animClass)
setTimeOut(() => {
this.$em... | 2024-08-24T04:01:37 | 2024-08-24T04:01:37 | {} | NONE |
vuejs | core | 2,308,365,954 | 11,703 | LinusBorg | This is not a bug, it was a documented breaking change in Vue 3:
https://v3-migration.vuejs.org/breaking-changes/transition-as-root.html | 2024-08-24T11:49:24 | 2024-08-24T11:49:24 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,308,643,870 | 4,339 | cons2act | > 这个特性能用了吗?
想多了 | 2024-08-25T03:57:57 | 2024-08-25T03:57:57 | {} | NONE |
vuejs | core | 2,309,213,073 | 11,713 | pkg-pr-new[bot] |
_commit: <a href="https://github.com/vuejs/core/runs/29232263076"><code>1812045</code></a>_
<details><summary><b>@vue/compiler-core</b></summary><p>
```
pnpm add https://pkg.pr.new/@vue/compiler-core@11713
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
pnpm add https:/... | 2024-08-26T03:08:15 | 2024-08-26T03:08:15 | {} | NONE |
vuejs | core | 2,309,666,022 | 11,717 | edison1105 | Talk is cheap, show me the code. | 2024-08-26T08:38:51 | 2024-08-26T08:38:51 | {} | MEMBER |
vuejs | core | 2,309,690,051 | 11,717 | l123wx | The code is here @edison1105 | 2024-08-26T08:50:45 | 2024-08-26T08:50:45 | {} | NONE |
vuejs | core | 2,311,385,996 | 9,364 | edison1105 | closed via https://github.com/vuejs/core/commit/f476b7f030f2dd427ca655fcea36f4933a4b4da0
see https://github.com/vuejs/core/issues/7876#issuecomment-2232196747 | 2024-08-27T01:18:22 | 2024-08-27T01:21:04 | {} | MEMBER |
vuejs | core | 2,309,880,899 | 11,664 | Mini-ghost | To ensure the return value behaves consistently with `onCleanup`, may I suggest that when the return value is `Promise<() => any>`, we also consider collecting the returned function as `cleanup`?
The implementation might look like this:
```ts
const cleanup = call
? call(cb!, WatchErrorCodes.WATCH_CALLBACK, ar... | 2024-08-26T10:28:47 | 2024-08-27T02:00:50 | {} | CONTRIBUTOR |
vuejs | core | 2,313,030,415 | 11,726 | LinusBorg | That's expected. Vue will not respect classes that are added manually through DOM APIs because they are not part of the virtualDOM created during rendering. | 2024-08-27T16:32:42 | 2024-08-27T16:32:42 | {} | MEMBER |
vuejs | core | 2,314,848,388 | 7,419 | yyx990803 | This is superseded by https://github.com/vuejs/core/pull/10801 | 2024-08-28T09:46:57 | 2024-08-28T09:46:57 | {} | MEMBER |
vuejs | core | 2,306,846,615 | 11,687 | edison1105 | > Thanks a lot for the workaround :) Still interested in whether that's expected behaviour or a bug though.
I think this is expected behavior. aligin with vue2. | 2024-08-23T11:00:43 | 2024-08-23T11:00:43 | {} | MEMBER |
vuejs | core | 2,307,883,388 | 10,609 | mashpie | HA! removed all and every package that required an `entities? version < 4.5 (thanks again @lzl0304) and violá build & run works as I were running local dev in production... conclusion?
> monorepos have a limit when trying to mix legacy and modern packages. Stick to single repos in that case - cheers! (hope, this hel... | 2024-08-23T22:26:04 | 2024-08-23T22:33:05 | {
"hooray": 1
} | NONE |
vuejs | core | 2,307,989,660 | 11,688 | patchthecode | You were correct.
i didnt know `defineOptions({ name: 'feed-screen' })` was even needed.
thank you. | 2024-08-24T01:57:05 | 2024-08-24T01:57:05 | {} | NONE |
vuejs | core | 2,309,101,961 | 11,671 | edison1105 | @Procrustes5 PR welcome. | 2024-08-26T01:01:08 | 2024-08-26T01:01:08 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,309,154,291 | 11,708 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 99.1 kB | 37.5 kB | 33.8 kB |
| vue.global.prod.js | 157 kB | 57.3 kB | 51 kB |
### Usages
| Name | Size |... | 2024-08-26T01:58:18 | 2024-08-26T01:58:18 | {} | NONE |
vuejs | core | 2,309,166,785 | 6,429 | edison1105 | Thanks for the PR, but sorry, we saw this PR too late. This issue has already been fixed in #11540.
see https://github.com/vuejs/core/pull/11540 | 2024-08-26T02:13:12 | 2024-08-26T02:13:12 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.