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,228,723,012 | 11,272 | Cherry | That's very interesting, thank you for taking a look.
With a fresh `npm create vue@latest` project, I'm also unable to reproduce this. But in a project at work, I still am able to when using `vue@3.4.31`, `@vue/language-core@2.0.26` and VSCode extension `vue.volar` at `v2.0.26` within VSCode, all latest versions.
... | 2024-07-15T15:04:46 | 2024-07-15T15:04:46 | {} | CONTRIBUTOR |
vuejs | core | 1,691,562,917 | 8,503 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | ----------------- |
| runtime-dom.global.prod.js | 89.8 kB (**+106 B**) | 34.3 kB (**+28 B**) | 31 kB (**+14 B**) |
| v... | 2023-08-24T12:13:37 | 2024-07-16T06:56:02 | {} | NONE |
vuejs | core | 2,230,343,828 | 5,836 | renatodeleao | > @renatodeleao As you can see, `TransitionGroup` will not re-render after `items` change, so the transition is not working.
>
> ```
> <TransitionGroup name="list" tag="ul" id="teleport-target"/>
>
> <template v-for="item in items" :key="item">
> <teleport to="#teleport-target">
> <Item :key="ite... | 2024-07-16T08:41:37 | 2024-07-16T08:50:58 | {} | NONE |
vuejs | core | 2,230,378,819 | 11,328 | Sorryhx | > Can you provide sample code where this happens? Ideally there should be a test case to demonstrate this.
Hi, Evan. I have added some test cases, and here is [the sample code](https://codepen.io/sorryhx/pen/JjQYLOQ). @yyx990803 | 2024-07-16T08:58:31 | 2024-07-16T08:58:31 | {} | CONTRIBUTOR |
vuejs | core | 1,884,526,610 | 10,066 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | -------------------- | ------------------- | -------------------- |
| runtime-dom.global.prod.js | 89.6 kB (**+243 B**) | 34.3 kB (**+90 B**) | 30.9 kB (**+69 B*... | 2024-01-10T09:55:51 | 2024-07-11T07:27:22 | {} | NONE |
vuejs | core | 1,982,752,268 | 10,472 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.3 kB | 34.1 kB | 30.8 kB |
| vue.global.prod.js | 146 kB | 53.6 kB | 47.8 kB |
### Usages
| Name | Size |... | 2024-03-07T07:34:00 | 2024-07-11T09:14:53 | {} | NONE |
vuejs | core | 2,225,729,530 | 11,340 | yyx990803 | Tested this in https://github.com/eknkc/ssr-benchmark with `renderToString` and it got 20% faster, great job! | 2024-07-12T14:38:07 | 2024-07-12T14:38:07 | {
"heart": 3,
"rocket": 15
} | MEMBER |
vuejs | core | 2,226,819,190 | 4,942 | yyx990803 | Closing as no longer reproducible. | 2024-07-13T08:20:01 | 2024-07-13T08:20:01 | {} | MEMBER |
vuejs | core | 2,228,074,812 | 11,360 | jh-leong | The vueuse build failed in ecosystem-ci because vueuse maintains its own definitions of `MaybeRef` and `MaybeRefOrGetter`, and there are mixed uses of locally defined types and types imported from `vue-demi`, leading to type compatibility issues.
I fixed this issue in PR [#4099](https://github.com/vueuse/vueuse/pull... | 2024-07-15T09:32:45 | 2024-07-15T09:32:45 | {} | MEMBER |
vuejs | core | 2,230,157,413 | 8,503 | yyx990803 | /ecosystem-ci run | 2024-07-16T06:55:16 | 2024-07-16T06:55:16 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,221,944,835 | 11,325 | yangliguo7 | @magicandskill
When props are changed, the reason for the execution of the render function is because during template parsing, reading props will store the render function as a dep.
As @linzhe141 said
The template parsing here does not store changes to props as dependencies
<img width="1627" alt="image" src="... | 2024-07-11T03:29:45 | 2024-07-11T03:29:45 | {} | CONTRIBUTOR |
vuejs | core | 2,222,465,486 | 10,066 | yyx990803 | /ecosystem-ci run | 2024-07-11T09:31:27 | 2024-07-11T09:31:27 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,227,777,735 | 11,360 | edison1105 | /ecosystem-ci run | 2024-07-15T06:25:30 | 2024-07-15T06:25:30 | {
"+1": 1,
"heart": 1
} | MEMBER |
vuejs | core | 2,227,860,997 | 11,355 | jh-leong | In your case:
```
loader: () => import('./components/HelloWorld.vue')
```
When the browser fetches a file, it caches the response regardless of whether it succeeds or fails. Therefore, each time you call retry (recalling the loader), it won’t initiate a new network request. Instead, it will immediately return the... | 2024-07-15T07:30:39 | 2024-07-15T07:30:39 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,227,963,937 | 11,328 | yyx990803 | Can you provide sample code where this happens? Ideally there should be a test case to demonstrate this. | 2024-07-15T08:32:47 | 2024-07-15T08:32:47 | {} | MEMBER |
vuejs | core | 2,228,518,303 | 11,364 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------- | ------- | ------- |
| runtime-dom.global.prod.js | 89.6 kB | 34.2 kB | 30.9 kB |
| vue.global.prod.js | 146 kB | 53.7 kB | 47.9 kB |
### Usages
| Name | Size |... | 2024-07-15T13:33:16 | 2024-07-15T14:09:32 | {} | NONE |
vuejs | core | 2,058,062,301 | 10,066 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/8698319023)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/8683642139) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/a... | 2024-04-16T01:12:58 | 2024-07-11T09:31:37 | {} | CONTRIBUTOR |
vuejs | core | 2,223,187,342 | 11,331 | LinusBorg | Please open an issue with `@mdx-js/vue` | 2024-07-11T15:07:44 | 2024-07-11T15:07:44 | {} | MEMBER |
vuejs | core | 2,225,104,693 | 11,331 | henrikruscon | Sounds like that could possibly be the case.
Maybe @LinusBorg can further clarify as to why this is an issue with `@mdx-js/vue` and not `vue`? | 2024-07-12T08:41:41 | 2024-07-12T08:41:41 | {} | NONE |
vuejs | core | 2,227,118,235 | 11,346 | LinusBorg | As @4refael explained, as you listen to the same event two times, one has to run after the other. We don't enforce one order because people might have different reasons for doing so.
So this is expected behavior | 2024-07-13T22:18:35 | 2024-07-13T22:18:35 | {} | MEMBER |
vuejs | core | 2,227,815,935 | 11,359 | LinusBorg | This issue is not actionable. And your wording is unnecessarily confrontational. Please try again. | 2024-07-15T06:58:22 | 2024-07-15T06:58:22 | {} | MEMBER |
vuejs | core | 2,230,378,130 | 5,836 | edison1105 | @renatodeleao
> Here's an [updated demo](https://play.vuejs.org/#eNqdVdtu4zYQ/ZWp+mA7iCUn2e3FdYJui0WRAm0XuwFawDIKRh7bWlOkQFK+wPC/95C62E6KBdoXm8MZnjlz1SF6V5bxpuJoHE1sZvLSkWVXlQ+pyotSG0cHMrygIy2MLqgH016nsqtqsZDcqOKkkePP9mTz6LjoDLzgvUGdqkwr6yjHlaV776Q/7YneNfWe/U/mf+a92SBVk6RmBk4QYF9K4RgS0WSeb8IBx+fKOa3ox0zm2fo+jRo2/eBhk... | 2024-07-16T08:58:10 | 2024-07-16T08:58:10 | {} | MEMBER |
vuejs | core | 2,230,459,577 | 11,246 | yyx990803 | Sorry but I don't think this is the right fix. | 2024-07-16T09:38:56 | 2024-07-16T09:38:56 | {} | MEMBER |
vuejs | core | 2,220,343,329 | 11,325 | magicandskill | > > const props = defineProps(['text','count'])
> > const text = props.text
> > const count = props.count
>
> When the App component changes the text and count, the render function of the Hellowold component will be re-executed, but the setup function of Helloworld will not be re-executed, so the text and count re... | 2024-07-10T12:07:49 | 2024-07-10T12:27:40 | {} | NONE |
vuejs | core | 2,222,424,619 | 10,403 | yyx990803 | This is expected behavior - see https://github.com/vuejs/core/pull/10436#issuecomment-2067417099 and https://github.com/vuejs/core/pull/10436#issuecomment-2222422063.
If you have a lot of global styles, just use a separate `<style>` tag without `scoped`. | 2024-07-11T09:12:41 | 2024-07-11T09:12:51 | {
"eyes": 1
} | MEMBER |
vuejs | core | 2,223,545,582 | 11,281 | MeesterDev | You are right, however, we're not talking about plain CSS, so how plain CSS works isn't really relevant.
An `@import` works inside a scoped stylesheet. This cannot be compiled to an actual `@import` in the plain CSS, as the plain CSS is something like `[data-v-xxxxx] { /* css here */ }`, yet the `@import` inside it,... | 2024-07-11T17:56:46 | 2024-07-11T17:56:46 | {} | NONE |
vuejs | core | 2,225,084,942 | 11,337 | yyx990803 | This is expected behavior and more consistent than what you suggest.
Template ref on a component is consumed where it is used - it means to get a reference to the component's public instance. If implicit fallthrough is allowed, the same usage of template ref on a component will have inconsistent behavior based on ho... | 2024-07-12T08:29:39 | 2024-07-12T08:29:39 | {} | MEMBER |
vuejs | core | 2,226,768,777 | 11,241 | jh-leong | This issue has been fixed in [this commit](https://github.com/vuejs/core/commit/685e3f381c024b9f4023e60fe0545dc60d90d984) | 2024-07-13T04:34:34 | 2024-07-13T04:34:34 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,226,791,638 | 11,281 | yyx990803 | You are confusing what it means to be "at the root level". Syntactically CSS doesn't allow `@import` statements to be nested in blocks. This has nothing to do with whether the `<style>` tag is scoped or not.
A single SFC can contain multiple `<style>` tags. If you want to import a global stylesheet, do so in a separ... | 2024-07-13T06:15:18 | 2024-07-13T06:15:18 | {} | MEMBER |
vuejs | core | 2,226,908,022 | 8,809 | yyx990803 | The direction is right, but checking only the direct children of the current vnode does not account for deeply nested `v-once` cached nodes.
In https://github.com/vuejs/core/commit/d343a0dc01663f91db42b4ddb693e6fffcb45873 I use `setBlockTracking` to mark the entire block to avoid this problem. | 2024-07-13T13:40:53 | 2024-07-13T13:40:53 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,220,032,511 | 11,323 | so1ve | What about v-if?
| 2024-07-10T09:40:21 | 2024-07-10T09:40:21 | {} | MEMBER |
vuejs | core | 2,224,099,602 | 11,331 | skirtles-code | I've tried to dig into this a bit further, though I'm very much out of my depth here.
As I understand it, MDX is setting `compilerOptions.jsxImportSource` to `'vue'`. This ultimately leads to this bit of Vue code:
https://github.com/vuejs/core/blob/314ce82e479dbb33a9281ba8c2ebe288536b32df/packages/vue/jsx-runtime... | 2024-07-11T23:11:29 | 2024-07-11T23:11:29 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 2,217,615,650 | 11,323 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ----------------- | ------------------- | ------------------- |
| runtime-dom.global.prod.js | 89.4 kB | 34.2 kB | 30.9 kB |
| vue.... | 2024-07-09T12:45:18 | 2024-07-12T03:44:15 | {} | NONE |
vuejs | core | 2,224,950,626 | 11,337 | intaek-h | > should be `$inputRef.value.$el.tagName`
Thank you for the reply. I tried your code and was able to see `DIV` printed. It feels a little inconsistent to see only the template ref not falling through even with the explicit `inheritAttrs: false` option. Can you share your thoughts on this? | 2024-07-12T06:59:51 | 2024-07-12T06:59:51 | {} | NONE |
vuejs | core | 2,226,844,508 | 11,346 | 4refael | Essentially, you have two listeners for the update event: the one you added and another one that was added by the v-model. So depending on the order of execution, the state might have already been changed.
According to the [style guide](https://vuejs.org/style-guide/rules-recommended#element-attribute-order), the re... | 2024-07-13T10:07:07 | 2024-07-13T10:07:07 | {} | NONE |
vuejs | core | 2,227,401,772 | 11,354 | LinusBorg | I'll temporarily reopen because I'm actually confused why the first watcher doesn't trigger.
Edit: ah:
```js
Number(1) === Number(1) // true
``` | 2024-07-14T16:19:05 | 2024-07-14T16:20:21 | {} | MEMBER |
vuejs | core | 2,230,232,018 | 10,069 | yyx990803 | Closing as this is fixed by the reactivity refactor in 3.5. | 2024-07-16T07:40:46 | 2024-07-16T07:40:46 | {} | MEMBER |
vuejs | core | 2,703,062,525 | 7,786 | moushicheng | > what the status on this?
I think this pr is ready, but I don't know why it's taking so long
@kaaax0815 | 2025-03-06T07:46:22 | 2025-03-06T07:46:22 | {
"confused": 2
} | CONTRIBUTOR |
vuejs | core | 2,708,918,317 | 12,935 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/13749903603)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/13714085897) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2025-03-09T15:33:36 | 2025-03-09T15:33:36 | {} | CONTRIBUTOR |
vuejs | core | 2,693,192,726 | 12,983 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/9a73cb6f-0168-47fa-abb8-5b81caf28d96)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12983
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-03T03:27:42 | 2025-03-10T01:39:07 | {} | NONE |
vuejs | core | 2,719,246,260 | 12,935 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/13822440488)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/13804039700) |
|-------|--------|----------------|
| nuxt | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci/actions/r... | 2025-03-12T22:13:03 | 2025-03-12T22:13:03 | {} | CONTRIBUTOR |
vuejs | core | 2,692,525,650 | 12,974 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/b0392faf-148e-4f45-9c9d-7509d8a3f3b4)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12974
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-02T02:45:11 | 2025-03-15T08:34:44 | {} | NONE |
vuejs | core | 2,709,227,827 | 13,015 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/630823cb-7dde-4dfa-8542-2e6dc2c2c0ca)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13015
```
</p></details>
<details><summary><b>@vue/compiler-sfc</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-10T01:39:18 | 2025-03-17T00:21:58 | {} | NONE |
vuejs | core | 2,709,227,496 | 13,014 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/159c9dce-144e-43b4-968a-341f55119533)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13014
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-10T01:38:58 | 2025-03-17T00:22:00 | {} | NONE |
vuejs | core | 2,727,781,561 | 13,048 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/48eeca86-bcc2-4143-ad61-137859272a6e)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13048
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-17T01:04:57 | 2025-03-17T01:32:40 | {} | NONE |
vuejs | core | 2,729,213,032 | 13,055 | padcom | I think the main problem is the ESLint rule. What happens is, if one has this rule enabled with auto-fix, then the code from valid (`.testProp="someReactiveValue"`) is changed to something that is invalid (`.test-prop="someReactiveValue"`).
This forces the use of `<!-- eslint-disable-next-line vue/attribute-hyphenatio... | 2025-03-17T11:55:53 | 2025-03-17T11:56:15 | {} | CONTRIBUTOR |
vuejs | core | 2,730,595,678 | 12,005 | xak2000 | Also: is it really necessary to export the intermediate type? Would it work without an `export`?
All exported types become a part of public API, so the less exported types - the better. | 2025-03-17T19:21:41 | 2025-03-17T19:21:41 | {
"+1": 1
} | NONE |
vuejs | core | 2,705,846,601 | 12,999 | edison1105 | /ecosystem-ci run | 2025-03-07T08:37:10 | 2025-03-07T08:37:10 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,568,860,486 | 12,645 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/988c7946-d308-4b59-a993-39b0b1c5f451)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12645
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-01-03T08:39:40 | 2025-03-13T06:51:17 | {} | NONE |
vuejs | core | 2,720,377,144 | 13,029 | zaalbarxx | > I think this is normal. If you want to modify the styles of the component's internal DOM, you should use :deep().
>
> // HelloWorld.vue
> <script setup>
> import { ref } from 'vue';
> import Box from './Box.vue';
>
> defineProps({
> msg: String,
> });
>
> const count = ref(0);
> </script>
>
> <template>
> <di... | 2025-03-13T08:34:08 | 2025-03-13T08:34:08 | {} | NONE |
vuejs | core | 2,722,936,897 | 11,517 | patroza | @yyx990803 is this supposed to work with SFCs?
In the following playground we will see the styles from a `defineComponent`, but not from within a `<style>` defined in a normal SFC.
https://play.vuejs.org/#eNqNU8GOmzAQ/ZWpLxskCqq6p5RdiURUbQ9t1fZW9xDBkLA1NrJNNlHEv+/YDrskykbLyZ55z35v/DiwvOuSbY9szjJT6qazYND23T2XTdspb... | 2025-03-13T23:41:21 | 2025-03-14T09:53:06 | {} | NONE |
vuejs | core | 2,727,744,616 | 13,046 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.3 kB |
| vue.global.prod.js | 158 kB | 58 kB | 51.6 kB |
### Usages
| Name | Size | G... | 2025-03-17T00:21:42 | 2025-03-17T00:21:42 | {} | NONE |
vuejs | core | 2,709,691,815 | 13,017 | edison1105 | > This limitation has been resolved in 3.3. The latest version of Vue supports referencing imported and a limited set of complex types in the type parameter position. However, because the type to runtime conversion is still AST-based, some complex types that require actual type analysis, e.g. conditional types, are not... | 2025-03-10T07:46:05 | 2025-03-10T07:46:05 | {} | MEMBER |
vuejs | core | 2,709,826,240 | 13,010 | edison1105 | Actually not. We can’t directly change it to `data-true-value="yes"`, as that would be a breaking change for users already using `true-value="yes"`. However, we could consider adding support for `data-true-value="yes"` while keeping both options valid. | 2025-03-10T08:47:02 | 2025-03-10T08:47:02 | {
"+1": 2
} | MEMBER |
vuejs | core | 2,716,604,434 | 13,027 | jh-leong | Nice catch! Thanks for your contribution. It looks like a duplicate of #12973. | 2025-03-12T05:55:53 | 2025-03-12T05:55:53 | {} | MEMBER |
vuejs | core | 2,717,418,695 | 12,613 | iiio2 | Thanks @edison1105 | 2025-03-12T10:35:36 | 2025-03-12T10:35:36 | {} | CONTRIBUTOR |
vuejs | core | 2,723,207,320 | 12,948 | mrleblanc101 | @edison1105
Can we expect this to be publish in a new version soon-ish ?
Since it's been 4 months since the last Vue path version | 2025-03-14T02:40:56 | 2025-03-14T02:40:56 | {
"+1": 1
} | NONE |
vuejs | core | 2,723,212,271 | 12,948 | edison1105 | @mrleblanc101
We are planning to release the next version | 2025-03-14T02:45:15 | 2025-03-14T02:45:15 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,725,052,196 | 13,037 | Justineo | You’re right, I initially thought you were referring to the source code. I compared the output of Vue 2, and the `name` attribute in Vue 3 does indeed seem redundant. | 2025-03-14T15:35:08 | 2025-03-14T15:35:08 | {
"+1": 2,
"heart": 1
} | MEMBER |
vuejs | core | 2,732,050,096 | 13,060 | jh-leong | /ecosystem-ci run | 2025-03-18T08:12:54 | 2025-03-18T08:12:54 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,702,874,131 | 13,001 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/5a12bd62-9898-45ca-be09-bca0bb873a2d)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13001
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-06T05:46:38 | 2025-03-06T05:46:38 | {} | NONE |
vuejs | core | 2,703,399,888 | 12,697 | dantec20 | My colleagues and I just figured out that the issue disappears when you don't put `export default [classname] extends Vue` on one line.
If you do it like this, all component errors are fixed:
```
@Component({})
class MyClassName extends Vue {
// .....
}
export default MyClassName;```
Not sure what'... | 2025-03-06T10:13:14 | 2025-03-06T10:13:37 | {} | NONE |
vuejs | core | 2,708,963,851 | 12,935 | johnsoncodehk | /ecosystem-ci run | 2025-03-09T17:04:22 | 2025-03-09T17:04:22 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,713,939,379 | 13,010 | WebMechanic | > I'm only concerned about passing the validator, but I also think that standards are important. Maybe that's in my DNA as a German ;)
German here too... I wouldn't be too religious about the W3C validator not handling custom attributes well. Are they flagged as error or warning?
The validator's not on par with many ... | 2025-03-11T12:07:20 | 2025-03-11T12:08:32 | {} | NONE |
vuejs | core | 2,692,525,391 | 12,974 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vapor-repl* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 34957eb77dc2200765b58d84204ac8b91c8d1408 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vapor-repl/d... | 2025-03-02T02:44:12 | 2025-03-15T08:35:24 | {} | NONE |
vuejs | core | 2,704,237,586 | 13,003 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 101 kB | 38.3 kB | 34.5 kB |
| vue.global.prod.js | 159 kB | 58.2 kB | 51.8 kB |
### Usages
| Name | Size | G... | 2025-03-06T15:49:32 | 2025-03-06T15:49:32 | {} | NONE |
vuejs | core | 2,716,106,317 | 12,435 | mikehwagz | An example of this being an issue is that it seems to break `appear` for Nuxt page transitions. I created a reproduction of that here: https://github.com/mikehwagz/vue-nuxt-transition-bug
Here is an issue in the Nuxt repo about this: https://github.com/nuxt/nuxt/issues/14715
cc @danielroe
If this is actually a Nuxt... | 2025-03-12T01:02:00 | 2025-03-12T01:02:00 | {
"+1": 1
} | NONE |
vuejs | core | 2,716,583,386 | 13,028 | jh-leong | When using `onError`: [Playground](https://play.vuejs.org/#eNp9U01v2zAM/SuELnYAwynWW5YG6IYctsNWbL1NOxg2nSq1JUOSkxSG/3tJKXHSIu0lEfkeyccPD+K+6/Jdj2Ihlq60qvPg0PfdSmrVdsZ6GKDCWmm8dy+6/G7IqVF7GKG2poWEYpOvE5nxI5DP2eDcjEtd97r0ymhoTFFNedIZDFIDWCpqNWjcwwOFK4dpatGZZocZgVss/QzuVpEMrPFRtWh6n1KGs58TMTdNuAqgtcYmM6rP0JjBl5ubaI38N7Ku0... | 2025-03-12T05:50:06 | 2025-03-12T05:50:06 | {} | MEMBER |
vuejs | core | 2,717,199,544 | 13,027 | edison1105 | Thank you for your contribution, but this PR is a duplicate of #12973. Please review #12973 if needed. | 2025-03-12T09:23:11 | 2025-03-12T09:23:11 | {} | MEMBER |
vuejs | core | 2,719,782,435 | 13,029 | coderwei99 | I think this is normal. If you want to modify the styles of the component's internal DOM, you should use :deep().
```vue
// HelloWorld.vue
<script setup>
import { ref } from 'vue';
import Box from './Box.vue';
defineProps({
msg: String,
});
const count = ref(0);
</script>
<template>
<div class="warp">
<Box ... | 2025-03-13T03:55:14 | 2025-03-13T03:55:14 | {} | CONTRIBUTOR |
vuejs | core | 2,723,795,074 | 13,035 | yangxiuxiu1115 | vue only exports the Component's type definition, there is no associated class or method implementation, if you set verbatimModuleSyntax: false, it does cause the problem you mentioned. I think this might be as expected though?
I haven't found a role for __VUE_PROD_DEVTOOLS__ in this, it seems to fail to package/rende... | 2025-03-14T06:43:01 | 2025-03-14T06:43:01 | {} | CONTRIBUTOR |
vuejs | core | 2,727,898,922 | 13,037 | edison1105 | ~~It's weird. It is only reproducible in the HTML of the online documentation.
I can't reproduce it in [Playground](https://play.vuejs.org/#__PROD__eNp9VW1v2zYQ/is3FUOdxpLtpskHzQn2gm7IsK3F2i/DNAy0RNmsaVIgKcdukP++h6RkK4kX2IDI43N3z73weJ/80DTZtuVJnsy/SdNC/fzb7UeSwjpyhikrnNDK0p1wK3IrTotWSJcKRfPPh+NfjG6bm6xQK+cam08mjBvt7mAj... | 2025-03-17T02:47:45 | 2025-03-17T02:57:49 | {} | MEMBER |
vuejs | core | 2,728,055,643 | 13,050 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.3 kB |
| vue.global.prod.js | 158 kB | 58 kB | 51.6 kB |
### Usages
| Name | Size | G... | 2025-03-17T03:49:44 | 2025-03-17T03:49:44 | {} | NONE |
vuejs | core | 2,702,649,187 | 12,749 | Deckluhm | I encountered what looks like the same issue but with a method using the same name than a template ref.
Here is a minimal reproduction: https://stackblitz.com/edit/vitejs-vite-h29jzpxy?file=src%2FApp.vue | 2025-03-06T02:48:39 | 2025-03-06T09:20:38 | {} | NONE |
vuejs | core | 2,709,049,436 | 12,935 | johnsoncodehk | /ecosystem-ci run | 2025-03-09T20:18:29 | 2025-03-09T20:18:29 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,709,051,884 | 12,935 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/13752142996)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/13714085897) |
|-------|--------|----------------|
| language-tools | :white_check_mark: [success](https://github.com/vuejs/ecosystem-ci... | 2025-03-09T20:25:20 | 2025-03-09T20:25:20 | {} | CONTRIBUTOR |
vuejs | core | 2,709,741,953 | 13,010 | edison1105 | > Could this be fixed by using data attributes instead?
Yes, but this will be a breaking change. Please provide more information about whether this is a real use case or just for passing the W3C validator. | 2025-03-10T08:10:53 | 2025-03-10T08:10:53 | {} | MEMBER |
vuejs | core | 2,568,860,320 | 12,645 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.3 kB |
| vue.global.prod.js | 158 kB | 58 kB | 51.6 kB |
### Usages
| Name | Size | G... | 2025-01-03T08:39:33 | 2025-03-13T06:42:39 | {} | NONE |
vuejs | core | 2,727,202,424 | 13,044 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vapor-repl* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 704fee955eb12f4e8f21fd6d1eccee46c54d27d9 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vapor-repl/d... | 2025-03-16T05:22:24 | 2025-03-16T05:23:31 | {} | NONE |
vuejs | core | 2,730,085,509 | 13,057 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vapor-repl* ready!
| Name | Link |
|:-:|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 015e1eed26a7b815ac402ab1ca10a52d771b6743 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://app.netlify.com/sites/vapor-repl/d... | 2025-03-17T16:08:53 | 2025-03-18T04:34:25 | {} | NONE |
vuejs | core | 2,720,199,765 | 13,029 | yangxiuxiu1115 | https://github.com/vuejs/core/blob/main/packages/runtime-dom/src/apiCustomElement.ts#L584-L595
Maybe it's due to the style's insertion strategy prepend and not adjusting the order when reusing the component | 2025-03-13T07:14:48 | 2025-03-13T07:14:48 | {} | CONTRIBUTOR |
vuejs | core | 2,724,049,660 | 13,035 | jh-leong | Thanks for the report.
The issue is caused by `vite-plugin-vue` incorrectly parsing `__VUE_PROD_DEVTOOLS__: 'false'` as `true`. I'm working on a fix here: [vitejs/vite-plugin-vue#545](https://github.com/vitejs/vite-plugin-vue/pull/545).
Additionally, the root cause in this case relates to the non-inline mode compil... | 2025-03-14T08:59:38 | 2025-03-14T08:59:38 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,724,631,638 | 5,385 | femans | The fix works: [Playground Example with fix](https://deploy-preview-8803--vue-sfc-playground.netlify.app/#eNqdVtuO2zYQ/ZWBXrIL2FK6yRaFfGmTIChSIG3RBuhDlAdaGttcUyRLUra3i/33Dknd7PUmaJ/GnMuZ0ZnhmA/JG63TfYNJnsxtabh2YNE1ellIXmtlHDyAwTU8wtqoGl6Q64tCFnLPDAhunYWFt199LiTAww7vc/huAnsmGrQ5fC4SViQTKJJVFGUUVRRYJF8eJ0PkzUnkOjptothGwa... | 2025-03-14T13:06:29 | 2025-03-14T13:06:29 | {} | NONE |
vuejs | core | 2,725,041,265 | 13,037 | codeflorist | @Justineo
Of course i didn't validate the template, but the actual HTML.
If you look at the source code of https://vuejs.org/guide/built-ins/transition-group, you will see this actual HTML code:
```html
<ul name="list" style="margin-top:20px;">
<li>1</li>
<li>2</li>
<li>3</li>
<li>4</li>
<li>5</li>
</ul>
... | 2025-03-14T15:31:04 | 2025-03-14T15:31:04 | {} | NONE |
vuejs | core | 2,703,168,034 | 12,998 | codeflorist | @edison1105 Ah, many thanks! Can't believe i've missed that. Sorry for the false alarm! | 2025-03-06T08:38:45 | 2025-03-06T08:38:45 | {} | NONE |
vuejs | core | 2,717,469,485 | 13,027 | Stan-BK | Appreciate that！ | 2025-03-12T10:55:10 | 2025-03-12T10:55:10 | {} | NONE |
vuejs | core | 2,730,171,752 | 2,349 | imaverickk | > In 2024, I found a solution.
>
> The binding parameter contains the instance of the component, and `onActivated` accepts a target parameter indicating the instance where the hook needs to be injected.
>
> So a possible implementation of a directive that saves the scroll position is as follows:
> ```
> export defaul... | 2025-03-17T16:37:04 | 2025-03-17T17:13:41 | {} | NONE |
vuejs | core | 2,704,238,142 | 13,003 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/1ac68e21-340e-4fb8-a009-5a4b5273b3c1)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13003
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-06T15:49:44 | 2025-03-06T15:49:44 | {} | NONE |
vuejs | core | 2,714,282,648 | 10,042 | Jannick94 | Is there any update on this issue/the pending PR? 😊 | 2025-03-11T13:35:06 | 2025-03-11T13:35:06 | {} | NONE |
vuejs | core | 2,710,770,158 | 13,019 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/75396156-babf-4d7b-8baf-2f9c5bcf3d48)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@13019
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-03-10T14:21:00 | 2025-03-11T13:36:47 | {} | NONE |
vuejs | core | 2,720,614,829 | 13,031 | KazariEX | Please try updating `vue-tsc` to `v3.0.0-alpha.0`. | 2025-03-13T09:44:37 | 2025-03-13T09:44:37 | {
"heart": 1
} | MEMBER |
vuejs | core | 2,725,025,786 | 13,037 | Justineo | Vue’s component template code isn’t strictly compatible with HTML, but the rendered output is. So, validating the template with the W3C validator wouldn’t be meaningful. | 2025-03-14T15:24:42 | 2025-03-14T15:24:42 | {} | MEMBER |
vuejs | core | 2,727,781,247 | 13,048 | github-actions[bot] | ## Size Report
### Bundles
| File | Size | Gzip | Brotli |
| -------------------------- | ------ | ------- | ------- |
| runtime-dom.global.prod.js | 100 kB | 38.1 kB | 34.3 kB |
| vue.global.prod.js | 158 kB | 58 kB | 51.6 kB |
### Usages
| Name | Size | G... | 2025-03-17T01:04:35 | 2025-03-17T01:04:35 | {} | NONE |
vuejs | core | 2,661,893,796 | 12,887 | pkg-pr-new[bot] |
[Open in Stackblitz](https://pkg.pr.new/template/79c19fa5-ab5d-4a08-8477-c6397cb08610)
<details><summary><b>@vue/compiler-core</b></summary><p>
```
npm i https://pkg.pr.new/@vue/compiler-core@12887
```
</p></details>
<details><summary><b>@vue/compiler-dom</b></summary><p>
```
npm i https://pkg.pr.new... | 2025-02-17T03:38:11 | 2025-03-17T01:04:54 | {} | NONE |
vuejs | core | 2,708,966,978 | 12,935 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/13750640734)
| suite | result | [latest scheduled](https://github.com/vuejs/ecosystem-ci/actions/runs/13714085897) |
|-------|--------|----------------|
| language-tools | :x: [failure](https://github.com/vuejs/ecosystem-ci/actions/runs/1... | 2025-03-09T17:11:12 | 2025-03-09T17:11:12 | {} | CONTRIBUTOR |
vuejs | core | 2,709,928,411 | 10,514 | cooper667 | we are using the following patch to mangage around this. It's not perfect but better than the error.
```patch
@@ -0,0 +1,20 @@
diff --git a/dist/shared.d.ts b/dist/shared.d.ts
index ab2199d7da355160a31dd4edfb55c2c354d43f6b..2dc51a82053b8631b0b42c03d4bc26fa14c19792 100644
--- a/dist/shared.d.ts
+++ b/dist/shared.d.ts
@... | 2025-03-10T09:25:27 | 2025-03-10T09:25:27 | {
"+1": 2
} | NONE |
vuejs | core | 2,718,071,351 | 12,935 | johnsoncodehk | /ecosystem-ci run | 2025-03-12T14:23:38 | 2025-03-12T14:23:38 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,718,201,855 | 4,874 | Naedri | Hello, in `"vue": "=3.5.13"` I tried to reuse the `expose.component.exposed` from [infinite-system](https://github.com/infinite-system)'s [message](https://github.com/vuejs/core/issues/4874#issuecomment-1353941493) unsuccessfully. Indeed, I had to use `expose.component.withProxy`.
However, I was not able to find docum... | 2025-03-12T15:05:02 | 2025-03-12T15:05:02 | {} | NONE |
vuejs | core | 2,721,346,308 | 13,030 | edison1105 | /ecosystem-ci run | 2025-03-13T13:53:46 | 2025-03-13T13:53:46 | {
"+1": 1
} | MEMBER |
vuejs | core | 2,723,214,021 | 13,030 | edison1105 | LGTM~ | 2025-03-14T02:46:16 | 2025-03-14T02:46:16 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.