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 | 1,426,229,613 | 5,707 | olfek | I'm seeing the exact same issue with `watch()` on `3.2.45` as does @mStirner , can someone reopen this please. @yyx990803 ? | 2023-02-10T19:14:05 | 2023-02-10T19:14:05 | {} | NONE |
vuejs | core | 1,427,968,927 | 7,704 | vampics | I see thats could be a duplicate of [6435](https://github.com/vuejs/core/issues/6435)
@edison1105 A ETA for this would be nice. Annoying bug :/ | 2023-02-13T13:46:54 | 2023-02-13T13:48:20 | {} | NONE |
vuejs | core | 1,428,853,207 | 5,688 | posva | FYI you can still use `v-bind` within component to set a CSS variable and use that CSS variable directly anywhere you need
```vue
<style>
.my-class {
--my-var: v-bind(val);
}
</style>
```
[SFC](https://sfc.vuejs.org/#eNpdkcFugzAMhl/Fy4VWGqBeGUXabW+wSy4UQqFN4igOTBXi3edAmaZeolj/5/+PnVl8OpdNoxKFKKnxgwtAKoyuknYwDn2AGbz... | 2023-02-13T23:24:08 | 2023-02-13T23:24:08 | {} | MEMBER |
vuejs | core | 1,430,657,366 | 7,700 | Autumn-one | > First, it is normal to print 'aaa' twice, because the foo property is changed to `true` by the button, and changed to `false` by the `watch` callback.↳
>
> And 'bbb' is not printed, which I guess is due to the slot's update mechanism.↳
>
> You can use `nextTick` as mentioned in the comments above, or you can se... | 2023-02-15T02:18:10 | 2023-02-15T02:18:10 | {} | NONE |
vuejs | core | 1,425,695,590 | 5,409 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4143573844)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4143573844/jobs/7165579043) | :x: failure |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/4143573844/jobs/7165579... | 2023-02-10T11:46:13 | 2023-02-10T11:52:55 | {} | CONTRIBUTOR |
vuejs | core | 1,425,718,472 | 7,432 | haoqunjiang | Sorry, I forgot that ecosystem-ci could only be run when the PR is up-to-date with the `main` branch. Now force pushed.
/ecosystem-ci run | 2023-02-10T12:04:41 | 2023-02-10T12:04:41 | {} | MEMBER |
vuejs | core | 1,425,722,749 | 7,432 | haoqunjiang | /ecosystem-ci run | 2023-02-10T12:08:16 | 2023-02-10T12:08:16 | {} | MEMBER |
vuejs | core | 1,425,702,289 | 7,432 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4143578570)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4143578570/jobs/7165626640) | :x: failure |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/4143578570/jobs/7165626... | 2023-02-10T11:49:36 | 2023-02-10T12:39:14 | {} | CONTRIBUTOR |
vuejs | core | 1,426,378,879 | 7,688 | LinusBorg | This seems to be unrelated to #5707.
The problem here is that the component's `props` object is not being properly updated when the route changes - so the watch of course can't run, as `props` didn't change.
Here's what I could find out quickly:
The renderer triggers a re-render of the HomeView component, be... | 2023-02-10T21:41:41 | 2023-02-10T21:42:32 | {} | MEMBER |
vuejs | core | 1,429,253,468 | 7,707 | edison1105 | 这是 `el.setAttribute('$type', val)` 报错的。
可能vue2中是：`el['$type'] = val` | 2023-02-14T07:26:32 | 2023-02-14T07:36:17 | {} | MEMBER |
vuejs | core | 1,430,657,740 | 7,707 | leivii | @code-ManL @edison1105 确实是 `el.setAttribute` 报错的，属性的任何位置包含 `$` 符号都会导致报错，这对于我们之前的 v2 版本升级来说，真是个灾难啊 ): | 2023-02-15T02:18:24 | 2023-02-15T02:18:24 | {} | NONE |
vuejs | core | 1,430,667,910 | 7,707 | leivii | @AlexVagrant 是的，谢谢！
对于低代码平台来说，我们需要把通用属性和用户自定义组件的属性做隔离，否则可能导致冲突，有没有备选方案？
我们做低代码的初衷是让业务和技术分离，我们在升级技术（如vue3）时，业务配置可以保持不变。
所以我暂能想到的是，在低代码组件中将 `$type` 等通用属性做转换，比如 `LC_type`，尽管这看起来有点丑。
Yes, thank you!
For low-code platforms, we need to separate the common props from the props of user-defined components, otherwise ... | 2023-02-15T02:34:50 | 2023-02-15T02:34:50 | {} | NONE |
vuejs | core | 1,432,467,714 | 7,727 | edison1105 | please provide a minimal reproduction. | 2023-02-16T03:50:41 | 2023-02-16T03:50:41 | {} | MEMBER |
vuejs | core | 1,425,694,721 | 5,409 | haoqunjiang | /ecosystem-ci run | 2023-02-10T11:45:49 | 2023-02-10T11:45:49 | {} | MEMBER |
vuejs | core | 1,427,214,165 | 7,685 | baiwusanyu-c | I think this is expected because the task of updating the component after the props change is done in a queue.
cc @LinusBorg | 2023-02-13T01:52:02 | 2023-02-13T01:52:02 | {} | MEMBER |
vuejs | core | 1,427,811,566 | 7,700 | LinusBorg | The reason is that by the time the second watcher's getter is run, `props.foo` has been reset to `false` already by the first watcher's callback.
The getter function (`() => props.foo`) *does* run for the second watcher, but the callback won't be run because the getter's return values hasn't changed - it was and is... | 2023-02-13T11:51:59 | 2023-02-13T11:52:10 | {} | MEMBER |
vuejs | core | 1,432,376,121 | 7,676 | Justineo | See @baiwusanyu-c's comment. | 2023-02-16T02:17:03 | 2023-02-16T02:17:03 | {} | MEMBER |
vuejs | core | 1,426,861,680 | 7,688 | olfek | The difference of behavior between dev and production is caused by the `optimized` parameter? @LinusBorg | 2023-02-11T19:39:27 | 2023-02-11T19:39:27 | {} | NONE |
vuejs | core | 1,427,475,341 | 7,662 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4161150988)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4161150988/jobs/7198812693) | :white_check_mark: success |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/41611509... | 2023-02-13T07:33:46 | 2023-02-13T07:38:39 | {} | CONTRIBUTOR |
vuejs | core | 1,427,747,453 | 3,671 | pawelmiklas | +1 | 2023-02-13T11:04:53 | 2023-02-13T11:04:53 | {} | NONE |
vuejs | core | 1,427,840,010 | 7,700 | vivipure | First, it is normal to print 'aaa' twice, because the foo property is changed to `true` by the button, and changed to `false` by the `watch` callback.
And 'bbb' is not printed, which I guess is due to the slot's update mechanism.
You can use `nextTick` as mentioned in the comments above, or you can set the flush ... | 2023-02-13T12:13:13 | 2023-02-13T12:13:13 | {} | NONE |
vuejs | core | 1,428,978,739 | 7,695 | smoonsf | I see. But there is no way to unregister onCleanup right? Then condition should be inside cleanup function.
I think official guide about onCleanup is unclear for understanding its logic. 😢
| 2023-02-14T01:39:37 | 2023-02-14T01:39:37 | {} | NONE |
vuejs | core | 1,431,251,944 | 7,708 | han1822815550 | > > > @han1822815550 你的组件名是 Priceterms.vue 么？如果是还不能正常被 keep-alive 的话，请提供一个最小可复现的 demo。
> >
> >
> > 路由里name是Priceterms，组件文件名是index.vue（priceterms文件夹下的index.vue），然后index.vue中没手动声明name
>
> （在 3.2.34 或以上的版本中，使用 <script setup> 的单文件组件会自动根据文件名生成对应的 name 选项，无需再手动声明。）
>
> keepalive是根据文件名字缓存的，跟路由没关系。
明白了，感谢！ | 2023-02-15T11:55:15 | 2023-02-15T11:55:15 | {} | NONE |
vuejs | core | 1,425,733,878 | 3,478 | Pentadome | ```typescript
import type { UnwrapRef } from "vue";
/**
* This function simply returns the value typed as `T` instead of `Ref<T>` so it can be assigned to a reactive object's property of type `T`.
* In other words, the function does nothing.
* You can assign a Ref value to a reactive object and it will be autom... | 2023-02-10T12:18:17 | 2023-02-10T12:24:34 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 1,425,696,230 | 7,432 | haoqunjiang | /ecosystem-ci run | 2023-02-10T11:46:30 | 2023-02-10T12:39:11 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,425,790,832 | 7,432 | edison1105 | > The Ecosystem CI is all green now. But the snapshot test failed, and I can't understand the error message. Could you take a look?
just update the snapshot, all test green now. | 2023-02-10T13:11:56 | 2023-02-10T13:11:56 | {} | MEMBER |
vuejs | core | 1,426,823,199 | 7,626 | sxzz | /ecosystem-ci run | 2023-02-11T16:55:36 | 2023-02-11T16:55:36 | {} | MEMBER |
vuejs | core | 1,427,475,074 | 7,662 | edison1105 | /ecosystem-ci run | 2023-02-13T07:33:24 | 2023-02-13T07:33:24 | {} | MEMBER |
vuejs | core | 1,427,709,801 | 5,525 | johanmolen | @liulinboyi I cant explain why but it is working now (after a node_modules delete and reinstall) haha. Thanks anyway! | 2023-02-13T10:36:14 | 2023-02-13T10:36:14 | {} | NONE |
vuejs | core | 1,429,253,558 | 7,692 | liuseen-l | LGTM | 2023-02-14T07:26:38 | 2023-02-14T07:26:38 | {} | CONTRIBUTOR |
vuejs | core | 1,429,794,651 | 7,652 | atlemagnussen | Should be changed to match standards. if you want to emit an array - then you emit an array.
As many of us wants to convert to vue on a component level - one could easily switch between old component written in some old framework with vue-components when they emit custom events the same way. | 2023-02-14T14:02:06 | 2023-02-14T14:02:32 | {} | NONE |
vuejs | core | 1,429,865,335 | 7,713 | baiwusanyu-c | I think it is illegal to pass a null to v-bind, but in order to avoid this kind of error, I think it is still necessary to deal with fixing it.
cc @LinusBorg | 2023-02-14T14:48:22 | 2023-02-14T14:48:22 | {} | MEMBER |
vuejs | core | 1,425,762,507 | 7,365 | haoqunjiang | /ecosystem-ci run | 2023-02-10T12:46:14 | 2023-02-10T12:46:14 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,426,350,861 | 7,688 | olfek | [watch-watchEffect-bug.zip](https://github.com/vuejs/core/files/10711195/watch-watchEffect-bug.zip)
| 2023-02-10T21:09:21 | 2023-02-10T21:09:21 | {} | NONE |
vuejs | core | 1,426,823,658 | 7,626 | vue-bot |
📝 Ran ecosystem CI: [Open](https://github.com//vuejs/ecosystem-ci/actions/runs/4152293282)
| suite | result |
|-------|--------|
| [nuxt](https://github.com/vuejs/ecosystem-ci/actions/runs/4152293282/jobs/7183156148) | :x: failure |
| [pinia](https://github.com/vuejs/ecosystem-ci/actions/runs/4152293282/jobs/7183156... | 2023-02-11T16:55:58 | 2023-02-11T17:05:35 | {} | CONTRIBUTOR |
vuejs | core | 1,427,210,289 | 7,685 | huzedong2015 | >  need more info
I filled out the expected and actual data inversely，
Updated description | 2023-02-13T01:45:07 | 2023-02-13T01:45:55 | {} | NONE |
vuejs | core | 1,427,707,550 | 4,339 | jiangshengdev | #7702
This scheme can be tried while waiting for the merger, although it is extremely harmful.
But you can use it now | 2023-02-13T10:34:15 | 2023-02-13T10:34:15 | {} | NONE |
vuejs | core | 1,427,709,692 | 7,699 | AlexVagrant | I think you can find why `useSlots().default` is a function from this line:https://github.com/vuejs/core/blob/main/packages/runtime-core/src/componentSlots.ts#L130.
I hope that can help you. | 2023-02-13T10:36:08 | 2023-02-13T10:36:08 | {} | CONTRIBUTOR |
vuejs | core | 1,554,504,219 | 8,374 | xiaoxiangmoe | In @jd-solanki 's demo. I update vue to 3.3.4 and Change `StrictUnwrapSlotsType`'s `Readonly<T>` to `T`. And I found
```vue
<script lang="ts" setup generic="Row extends Record<string, unknown>">
import { objectKeys } from '../utils';
import { aTableProps, aTableSlots } from './meta';
const props = defineProps(... | 2023-05-19T12:32:10 | 2023-05-19T14:07:01 | {} | CONTRIBUTOR |
vuejs | core | 1,556,899,563 | 7,156 | tjx666 | @sxzz 我看 elk 也是一堆 index.vue，你们平时不用 vue-devtools 吗？我没跑过 elk，不知道它有没有解决这个问题
我所在的项目，因为这个问题不允许组件文件名为 index.vue，因为 vue devtools 可读性不好。
我准备写一个 eslint 插件禁止团队成员这么做了。 | 2023-05-22T09:45:19 | 2023-05-22T09:47:00 | {} | NONE |
vuejs | core | 1,557,485,968 | 8,390 | Alfred-Skyblue | Perhaps you can use `ButtonHTMLAttributes['disabled']`, which is exported in `runtime-dom.d.ts`. | 2023-05-22T16:01:00 | 2023-05-22T16:01:00 | {} | MEMBER |
vuejs | core | 1,559,784,363 | 3,399 | FichteFoll | https://github.com/vuejs/core/pull/7963 has been merged 2 months ago, but I don't know to which extent that addresses this issue/PR and haven't had the time to try it out. | 2023-05-23T16:26:14 | 2023-05-23T16:26:24 | {} | NONE |
vuejs | core | 1,561,025,369 | 8,391 | baiwusanyu-c | You are right, the `script setup` does behave differently | 2023-05-24T12:23:20 | 2023-05-24T14:18:51 | {} | MEMBER |
vuejs | core | 1,562,383,833 | 8,391 | cschra | > Furthermore, when using npm run build to get a production build, the app will be rendered as a blank page (mounted/lifecycle hooks will be called) - replacing the in-dom template completely. I have created a [stackblitz example](https://stackblitz.com/edit/vitejs-vite-rsn38e?startScript=build,preview) for this aswell... | 2023-05-25T07:02:10 | 2023-05-25T07:02:10 | {} | NONE |
vuejs | core | 1,563,694,811 | 8,399 | edison1105 | - for setup, It should be:
```js
export default {
extends: Comp,
setup(){}
}
```
- `defineOptions` already supported extends [see]( https://play.vuejs.org/#eNp9UctOwzAQ/JWVLylSYx/KKQRUQJzhjjmUZtsa6odspyBF+XfWTVq5QXDcmfXMeqZj987xQ4usYnVYe+UiBIytu5NGaWd9hA48bqCHjbcaClotztSj1e7pO6JpwkhzkWFJt7iRphaDMmnSEFG7/Spim... | 2023-05-26T01:24:44 | 2023-05-26T01:24:44 | {} | MEMBER |
vuejs | core | 1,563,704,408 | 8,415 | edison1105 | This error probably not related to vue
Closed due to no reproduction. | 2023-05-26T01:43:29 | 2023-05-26T01:43:29 | {} | MEMBER |
vuejs | core | 1,554,477,058 | 8,374 | jd-solanki | Whoa! Thanks so much for quick action ❤️ | 2023-05-19T12:08:28 | 2023-05-19T12:08:28 | {} | NONE |
vuejs | core | 1,556,723,792 | 8,383 | Tyh2001 | > 根据指南提供复制品
I don't understand what you mean | 2023-05-22T07:58:49 | 2023-05-22T07:58:49 | {} | NONE |
vuejs | core | 1,562,351,316 | 8,391 | cschra | Hey @baiwusanyu-c , thank you for your time and effort, creating a PR to fix this issue!
I already had a look at the vue-core code, but couldn't figure it out - just out of curiosity, with my limited understanding the snap/test changes related to this issue were just wrong before/should have expose this bug, right?
... | 2023-05-25T06:29:05 | 2023-05-25T06:29:55 | {} | NONE |
vuejs | core | 1,563,895,508 | 8,018 | coolCucumber-cat | When will this no longer be experimental and opt-in? Should I avoid using it in my project until it's stable? | 2023-05-26T06:56:54 | 2023-05-26T06:56:54 | {
"+1": 16,
"eyes": 6
} | NONE |
vuejs | core | 1,564,119,751 | 3,930 | bruce4code |
> > @qmhc 我刚刚解决了这个问题，我修改了两个地方。1.rollup.config 中增加 resolve: { dedupe: ['vue'] } （这个是从vite，尤大回复别人的一个问题） 2.把vue从dependencies 改为 devDependencies 。不知道是哪个起作用了，但是确实解决了
>
> 我遇到了相同的问题，在 vite.config.ts 中增加 `resolve: { dedupe: ['vue'] }` 这个配置解决了，感谢！
在 vite.config.ts 中增加 `resolve: { dedupe: ['vue'] }` ，我也加了这个就好了
new d... | 2023-05-26T09:47:31 | 2023-05-26T09:54:35 | {} | NONE |
vuejs | core | 1,554,407,366 | 8,310 | pikax | @rodrigocfd your issue is not the same issue on this issue, you can open another issue if you think your usage is valid.
The issue is not present inside the `setup`:
```html
<script setup lang="ts" generic="T">
const props = withDefaults(
defineProps<{
value?: T | null;
list: T[];
}>(),
{
... | 2023-05-19T11:04:43 | 2023-05-19T11:04:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,556,721,210 | 8,383 | LinusBorg | Provide a reproduction as per the guidelines | 2023-05-22T07:57:09 | 2023-05-22T07:57:09 | {} | MEMBER |
vuejs | core | 1,557,210,983 | 7,942 | baiwusanyu-c | > Are you aware of #4404 and https://github.com/EranGrin/vue-web-component-wrapper?
I'm aware of `#4404`, but I didn't include it in my plugin because it already has a PR. And my plugin is only implemented according to the PR I proposed, which is an intrusive way to the source code, which is completely different fro... | 2023-05-22T13:19:40 | 2023-05-22T13:20:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,558,063,598 | 8,146 | soletan | Just came across the same error message in a bunch of basically different use cases. AFAICT, this particular issue is just a follow up to some other issue which is causing Vue to throw in a wrong moment such as the set up of a component in my case.
I was observing it several times within the last two hours due to s... | 2023-05-22T21:44:55 | 2023-05-22T21:44:55 | {} | NONE |
vuejs | core | 1,558,547,888 | 8,388 | Pancake-Q | https://github.com/Pancake-Q/vue-jsx.git @baiwusanyu-c github repo address | 2023-05-23T05:27:36 | 2023-05-23T05:27:36 | {} | NONE |
vuejs | core | 1,560,716,926 | 8,403 | baiwusanyu-c | The implementation of this unit test is very inelegant, I think I need some guidance | 2023-05-24T08:56:27 | 2023-05-24T08:56:27 | {} | MEMBER |
vuejs | core | 1,560,791,957 | 8,403 | Alfred-Skyblue | ```ts
expect(slots).toHaveProperty('arguments[1].elements[0].arguments[1].returns.properties[1].value.returns[0].codegenNode.props.properties[0]',spy)
``` | 2023-05-24T09:42:20 | 2023-05-24T09:42:20 | {} | MEMBER |
vuejs | core | 1,562,223,571 | 8,407 | Alfred-Skyblue | I see it works, can you provide the browser version and more information? | 2023-05-25T03:56:04 | 2023-05-25T03:56:04 | {} | MEMBER |
vuejs | core | 1,555,289,926 | 8,286 | marsidev | There is a safe way (without `/* @vue-ignore */`) to extends `Props` with `HTMLAttributes`? | 2023-05-19T21:46:54 | 2023-05-19T21:46:54 | {} | NONE |
vuejs | core | 1,556,729,719 | 8,375 | jacekkarczmarczyk | related (i guess) https://github.com/vuejs/core/pull/5912 | 2023-05-22T08:02:22 | 2023-05-22T08:02:22 | {} | CONTRIBUTOR |
vuejs | core | 1,562,884,958 | 8,413 | baiwusanyu-c | > [demo](https://play.vuejs.org/#eNp9VM1u2zAMfhXCGJAESORDd/KcIlux0x6h7sG1mcSr/iDJbgvD7z5Klj0lA6ZLwt+P/Eh6zL5rzYYesyIrbWM67cCi6/VjJTuhlXEwgsEzTHA2SsCGXDer6UkJ/fPDoWxtNLM80fm8m2+VbJS0Doaa9whHn237/LKrZJnPgARFgkOhee3QS65MMw8HoVrkhUWOjeuU/IWf9lhlIWGVgbAXkq7IuYJ3ZXhbZZQEyrQUUpT5CpHts7mDg6g1+22VpPZHioEqGmyVFRA0Xkd9eJlAnNO2yPN... | 2023-05-25T13:11:30 | 2023-05-26T07:18:58 | {} | MEMBER |
vuejs | core | 1,556,068,904 | 8,378 | edison1105 | duplicate of https://github.com/vuejs/core/issues/7238 | 2023-05-21T02:47:55 | 2023-05-21T02:47:55 | {} | MEMBER |
vuejs | core | 1,556,491,645 | 8,373 | an501920078 | I don't think it had anything to do with defineExpose | 2023-05-22T04:06:07 | 2023-05-22T04:07:54 | {} | NONE |
vuejs | core | 1,557,055,718 | 8,385 | samydoesit | We need to use the runtime version of defineEmits and defineProps - https://github.com/vuejs/core/discussions/7927 | 2023-05-22T11:32:33 | 2023-05-22T11:32:33 | {} | NONE |
vuejs | core | 1,557,173,652 | 4,404 | leonheess | Are you aware of #7942 and https://github.com/baiwusanyu-c/unplugin-vue-ce? | 2023-05-22T12:57:57 | 2023-05-22T12:59:51 | {
"+1": 1
} | NONE |
vuejs | core | 1,560,637,373 | 8,140 | gVguy | I get this error (only during build) when importing a type with relative path eg:
```
'../types/myfile' ❌
```
when I use project root import, it resolves without errors
```
'@/types/myfile' ✅
```
I should note that this error arises when I import a file to use in `defineProps<MyType>()` since we can do ... | 2023-05-24T08:02:25 | 2023-05-24T08:02:25 | {
"+1": 5
} | NONE |
vuejs | core | 1,563,895,774 | 8,413 | baiwusanyu-c | @edison1105 @Alfred-Skyblue
I don't think this is a bug. According to the documentation, `Fallthrough Attributes` will not inherit `emits` related attributes, so `onUpdate:selectionKeys
` should not appear in `attrs`, and according to the related description of `emits` and `defineEmits` in the document, `emits` shou... | 2023-05-26T06:57:10 | 2023-05-26T06:58:31 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,564,620,415 | 8,423 | yyx990803 | I'm not sure if I understand what you are asking for, but I assume you want the `v-data-xxxx` scope attribute to be included in `attrs`?
If so, I'm afraid that is not something we will support. It violates the scoping rules (only root node of child shares parent scope), and will also be a breaking change. | 2023-05-26T16:11:48 | 2023-05-26T16:11:48 | {} | MEMBER |
vuejs | core | 1,554,551,482 | 8,374 | jd-solanki | @pikax I want to point out that we also have additional slot that is concated using `&` like in your PR's test but that isn't present in your self contained example.
Additionally, I want to point out that user might separate component's metas like props, slots, emits in another ts file and import it in SFC like I do... | 2023-05-19T13:11:41 | 2023-05-19T13:11:41 | {} | NONE |
vuejs | core | 1,555,117,852 | 8,214 | waldi | @TheSeg @leonardorafael `.valueAsNumber` returns a `NaN` for me | 2023-05-19T19:11:31 | 2023-05-19T19:12:17 | {} | NONE |
vuejs | core | 1,555,228,201 | 8,214 | waldi | @leonardorafael that's because NaN is transformed to null in JSON.stringify | 2023-05-19T20:45:10 | 2023-05-19T20:45:10 | {
"+1": 1
} | NONE |
vuejs | core | 1,555,293,791 | 8,214 | leonardorafael | > @leonardorafael that's because NaN is transformed to null in JSON.stringify
True, living and learning | 2023-05-19T21:52:25 | 2023-05-19T21:52:25 | {
"heart": 2
} | NONE |
vuejs | core | 1,555,423,375 | 8,375 | qijizh | This is expected, because the trigger is determined by comparing the oldValue and the newValue. In your example, `const c2 = computed(() => [c1.value]);`, even though `c1.value` didn't change (so the first `watch` was not triggered), you wrapped it in an array when returning it, which always made it unequal, like `[0] ... | 2023-05-20T01:55:57 | 2023-05-20T01:55:57 | {} | NONE |
vuejs | core | 1,555,992,523 | 8,378 | sphinxrave | It was compiled to ...
```js
_createVNode(__import_1__.default, {
text: "BUG",
onSelectFiles: _cache[0] || (_cache[0] =
(a) => {
for (const file of a.files) {
_unref(log)('aa', _ctx.file.name);
}
}
)//...
```
renaming file to other variables does n... | 2023-05-20T20:29:37 | 2023-05-20T20:29:37 | {} | NONE |
vuejs | core | 1,556,707,910 | 8,373 | ml1nk | Not directly at least, that's true. Most probably the typing is broken independant on how you define them. | 2023-05-22T07:46:17 | 2023-05-22T07:46:17 | {} | NONE |
vuejs | core | 1,559,141,281 | 8,388 | baiwusanyu-c | > 请使用 `<script setup lang="jsx">`
> 不要在普通的 JS 代码块中写 JSX。
>
> 由这个 PR 引起：https://github.com/vuejs/core/pull/5846
> 我觉得这不能算 bug，之前的行为（把所有 JS 当 JSX 识别）才是 bug。
有相关文档中指出这一点吗，如果没有我觉得有必要说明一下😃 | 2023-05-23T11:55:11 | 2023-05-23T11:55:11 | {} | MEMBER |
vuejs | core | 1,563,779,598 | 7,437 | Syntax-J | same here @yyx990803 | 2023-05-26T04:00:31 | 2023-05-26T04:00:31 | {} | NONE |
vuejs | core | 1,563,801,585 | 8,374 | localusercamp | Any news on merging this?
I really miss this feature =) | 2023-05-26T04:43:43 | 2023-05-26T04:43:43 | {} | NONE |
vuejs | core | 1,564,607,632 | 8,391 | cschra | @yyx990803 sorry to bring this up again, but with composition API export it is working and shouldn't those 2 be feature equal?
As far as I understand, the `script setup` is just syntactic sugar for the standard composition API, but maybe I am wrong here... | 2023-05-26T16:01:40 | 2023-05-26T16:02:57 | {} | NONE |
vuejs | core | 1,554,536,439 | 8,374 | pikax | @xiaoxiangmoe please provide an contained example, otherwise there's too many running pieces that might get this broken.
I would discourage using `props.` on the template, there's a lot of things going on typescript side that might break the correct type.
Here's a full working self contained example:
```htm... | 2023-05-19T13:00:24 | 2023-05-19T13:00:24 | {} | MEMBER |
vuejs | core | 1,556,236,033 | 8,286 | dimatakoy | This is a rather strange situation, it turns out that if you want to use basic html attributes on a component, you have to specify them all explicitly or use a hack with ignore comment.
Given that we have attribute passing down, and we don't need to validate them, vue-tsc could suggest valid attributes for html elem... | 2023-05-21T17:37:31 | 2023-05-21T17:37:31 | {
"+1": 2
} | NONE |
vuejs | core | 1,556,420,310 | 8,375 | mr-pajamas | Thank you qijizh for answering! The point is that the first computed (c1) has not changed, it might recompute because its dependency's value has changed, but the output of the computation remains the same (0 === 0). Thus the watcher observing c1 is not triggered, but why is c2's recomputation triggered if its only depe... | 2023-05-22T02:21:09 | 2023-05-22T02:21:09 | {} | NONE |
vuejs | core | 1,562,373,091 | 8,391 | cschra | Mh, this sounds a bit sobering.
In my opinion this is a bug with VueJS and I was hoping that it gets attention and I think it deserves a fix, as a part of the community, who uses vue with serverside languages, relies heavily on the in-dom-template functionality and `script setup` is much cleaner.
Thanks for your e... | 2023-05-25T06:52:26 | 2023-05-25T06:53:02 | {} | NONE |
vuejs | core | 1,556,731,813 | 8,375 | mr-pajamas | Thank you so much LinusBorg, I was just reading your article: [Vue: When a computed property can be the wrong tool](https://dev.to/linusborg/vue-when-a-computed-property-can-be-the-wrong-tool-195j) | 2023-05-22T08:03:41 | 2023-05-22T08:03:41 | {
"+1": 1
} | NONE |
vuejs | core | 1,564,602,090 | 8,391 | yyx990803 | Maybe the doc could be more explicit about this, but `<script setup>` requires template to be in the same SFC. It cannot work with in-DOM templates.
In short, this was never an intended use case. | 2023-05-26T15:57:48 | 2023-05-26T15:57:48 | {} | MEMBER |
vuejs | core | 1,554,486,275 | 8,374 | xiaoxiangmoe | @pikax Hi, I tried it and it seems not fix https://github.com/vuejs/language-tools/issues/3141 now. Is there anything I miss? | 2023-05-19T12:17:15 | 2023-05-19T12:17:15 | {
"eyes": 1
} | CONTRIBUTOR |
vuejs | core | 1,554,575,029 | 8,374 | pikax | > @pikax I want to point out that we also have additional slot that is concated using `&` like in your PR's test but that isn't present in your self contained example.
Because that's very straightforward and the adding extra doesn't reproduce the bug.
<img width="628" alt="image" src="https://github.com/vuejs/core/... | 2023-05-19T13:25:19 | 2023-05-19T13:25:19 | {
"+1": 4
} | MEMBER |
vuejs | core | 1,558,377,083 | 8,388 | baiwusanyu-c | Can you provide a repo that reproduces the problem？🧐 | 2023-05-23T01:52:49 | 2023-05-23T01:52:49 | {} | MEMBER |
vuejs | core | 1,558,883,892 | 8,388 | baiwusanyu-c | I think it's a problem with the jsx babel plugin | 2023-05-23T09:17:30 | 2023-05-23T09:17:30 | {} | MEMBER |
vuejs | core | 1,560,658,859 | 8,140 | edison1105 | @gVguy
relative import is already supported.
Could you provide a runnable minimal reproduction? | 2023-05-24T08:16:42 | 2023-05-24T08:16:42 | {} | MEMBER |
vuejs | core | 1,560,679,550 | 8,388 | haoqunjiang | > 有相关文档中指出这一点吗，如果没有我觉得有必要说明一下😃
完全没有预料到会有用户依赖这个 bug……这是目前收到的唯一一例报告。如果问的用户多了的话，可以考虑在文档里提一下。
| 2023-05-24T08:30:55 | 2023-05-24T08:30:55 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,562,507,009 | 8,410 | edison1105 | 没有简单的复现demo，我们没办法调查问题。
先关闭了，等有了复现，我再打开。 | 2023-05-25T08:35:29 | 2023-05-25T08:35:29 | {} | MEMBER |
vuejs | core | 1,564,286,255 | 5,002 | ghost | why this not to do? | 2023-05-26T12:01:52 | 2023-05-26T12:01:52 | {} | NONE |
vuejs | core | 1,559,029,810 | 3,948 | kentliau | Facing this problem as well, the database/json definitely have a lot of null, so I think ability to make a props type nullable is quite important
`type: null as unknown as PropType<string | null>` is my current workaround for my component.
I use Quasar, they export another type definition to make `string | null |... | 2023-05-23T10:38:18 | 2023-05-23T10:39:50 | {} | NONE |
vuejs | core | 1,560,406,493 | 8,391 | baiwusanyu-c | I think this is all in line with expectations, because your html code is written directly in `index.html`, not in the `.vue` file, which makes them not recognized by the vue compiler and compiled into rendering functions, and because `createApp (App).mount('#vue-app')`, then `onMounted` will naturally execute. | 2023-05-24T03:24:28 | 2023-05-24T03:24:28 | {} | MEMBER |
vuejs | core | 1,560,817,707 | 5,657 | BenNiks1 | also faced this problem on nuxt 3.3.1
the error was not always there and I started to move from commit to commit to understand in what moment it appeared and what changes could lead to this error.
in my case, I came to a new project, which is written quite badly and there was such a construction:
```
<script setup>... | 2023-05-24T09:59:19 | 2023-05-24T09:59:47 | {} | NONE |
vuejs | core | 1,562,357,964 | 8,391 | baiwusanyu-c | I think this may be because the `script setup` compiler ignored this scenario during the implementation process, which caused problems in using the `script setup`. Therefore, the relevant test snapshots before may be meaningless, so I updated the snapshots in pr.
But I think the possibility of this change being merged... | 2023-05-25T06:36:44 | 2023-05-25T06:36:44 | {} | MEMBER |
vuejs | core | 1,562,419,125 | 8,407 | edison1105 | Related https://github.com/chromium/chromium/commit/9f26d474dc4b87e705dc8a2e1ab2632c87dc1eb7
| 2023-05-25T07:32:09 | 2023-05-25T07:32:09 | {} | MEMBER |
vuejs | core | 1,562,451,200 | 8,410 | 15890182384 | 
| 2023-05-25T07:55:49 | 2023-05-25T07:55:49 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.