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 | 993,699,018 | 3,024 | octavioamu | @snwokenk you save me, been days trying to figure out that.
For those having this error `'get' on proxy: property 'provider' is a read-only ....` you should wrap the provider with markRaw like:
```
const web3 = new Web3Provider(wallet.provider, 'any');
provider = markRaw(web3);
``` | 2021-12-14T16:10:57 | 2021-12-14T16:10:57 | {
"+1": 9,
"heart": 2
} | NONE |
vuejs | core | 995,494,465 | 5,121 | posva | Do you have an actual reproduction? Because this seems to work:
```ts
defineComponent({
props: {
value: String
},
setup(props) {
const a = toRef(props, 'value')
a.value
}
})
``` | 2021-12-16T06:57:25 | 2021-12-16T06:57:25 | {} | MEMBER |
vuejs | core | 991,577,699 | 4,397 | xiaoxiangmoe | My workaround:
```ts
// file: vue-type-helpers.ts
import { UnwrapRef } from '@vue/composition-api';
// or
import { UnwrapRef } from 'vue';
export type ExposedToComputed<T extends object> = {
[key in keyof T]: () => UnwrapRef<T[key]>;
};
```
```vue
<script lang="ts">
import type { ExposedToComputed ... | 2021-12-11T09:44:06 | 2021-12-17T07:21:00 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 996,702,924 | 5,134 | LinusBorg | Please understand that we don't have the capacity to debug 3rd-party component libraries in order to check wether we have a bug in Vue or they have a bug in their code.
If you can come up with an example that replicates the issue without 3rd party dependencies we are happy to have a second look | 2021-12-17T12:58:38 | 2021-12-17T12:58:38 | {
"+1": 1,
"-1": 2
} | MEMBER |
vuejs | core | 990,029,071 | 5,082 | posva | What feature is this implementing? If there isn't any, do you have a real world scenario that **requires** this change? | 2021-12-09T16:47:59 | 2021-12-09T16:48:18 | {} | MEMBER |
vuejs | core | 990,712,991 | 5,086 | CamilleDrapier | If that helps, here is a performance capture of the action described above:
| 2021-12-10T07:58:48 | 2021-12-10T07:58:48 | {} | NONE |
vuejs | core | 990,742,286 | 5,087 | posva | Please, search existing issues and pull requests before opening issues, it saves maintainers a lot of time 🙏: https://github.com/vuejs/vue-next/issues?q=is%3Aissue+sort%3Aupdated-desc+v-bind+is+is%3Aclosed | 2021-12-10T08:46:02 | 2021-12-10T08:46:02 | {} | MEMBER |
vuejs | core | 990,753,781 | 5,086 | LinusBorg | Just as a preliminary explanation:
* calling `push()` on an array with 2000 items results in **1** set operation.
* calling `unshift()` on an array with 2000 items results in **2001** set operations, as all array items have to be reassigned to index+1.
The latter is still very fast with plain arrays as the Brow... | 2021-12-10T09:03:41 | 2021-12-10T09:03:41 | {
"+1": 2
} | MEMBER |
vuejs | core | 990,813,251 | 5,088 | posva | Those properties (as anything that starts with _) is private API. If you have a breaking example not using internal properties, please open a new issue | 2021-12-10T10:18:17 | 2021-12-10T10:18:17 | {
"confused": 1
} | MEMBER |
vuejs | core | 991,235,167 | 2,669 | tuan-lm97 | This still not have been fixed yet ?
Just run into this problem today. Spent a good 30m to understand why.
I think the very least thing we can do is issue this problem in the doc about fragment. Because it is expected that everything have bound to an element, it should behave like the root of the child component | 2021-12-10T19:24:20 | 2021-12-10T19:24:20 | {} | NONE |
vuejs | core | 991,813,041 | 5,093 | yyx990803 | In general, we will not consider major additions of new directives to Vue's template syntax unless it unlocks something that was **not possible** before.
In this case, the syntax really isn't fundamentally different from `v-if/v-else-if/v-else` chains, but the implementation complexity and introduced API surface is ... | 2021-12-12T00:53:46 | 2021-12-12T00:53:46 | {} | MEMBER |
vuejs | core | 993,213,289 | 5,104 | caozhong1996 | Duplicate #4994, this is the expected behavior, but maybe people need a proper hint from the document. | 2021-12-14T06:52:26 | 2021-12-14T06:52:26 | {} | CONTRIBUTOR |
vuejs | core | 993,371,549 | 2,133 | danimajo | Tried this in recent Firefox (95) on Win10 - looks like the fade-in transition works sometimes, fade-out always.
| 2021-12-14T10:02:25 | 2021-12-14T10:02:25 | {} | NONE |
vuejs | core | 993,829,165 | 1,679 | guilhermemart | Worked perfectly, thanks a lot | 2021-12-14T17:49:46 | 2021-12-14T17:50:07 | {
"+1": 1
} | NONE |
vuejs | core | 994,514,272 | 5,109 | posva | You need to wrap the expression [with quotes](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IHsgcmVmIH0gZnJvbSAndnVlJ1xuXG4gIGxldCBhID0gcmVmKDEwMClcbiAgbGV0IGIgPSByZWYoMjAwKVxuXG48L3NjcmlwdD5cblxuPHRlbXBsYXRlPlxuICBzMSA6IHt7YSArIGIgLyAyICsgJ3B4J319PGJyPlxuICBzMjoge3soYSArIGIpIC8gMiArICdweCd9fTx... | 2021-12-15T08:52:29 | 2021-12-15T08:52:29 | {} | MEMBER |
vuejs | core | 997,082,327 | 4,707 | runxc1 | @Xulio-Xulio did you ever solve this? I'm running into the same issue on a large project | 2021-12-17T23:08:39 | 2021-12-17T23:08:39 | {
"+1": 1
} | NONE |
vuejs | core | 990,092,510 | 5,082 | jaulz | @posva yep, like I mentioned this change will allow custom directives to do the same as `v-html` does. In my case I have a `v-emojis` directive that walks through it's children and replaces UTF-8 emojis with images (`<img src="..." />`). Since it is supposed to work in SSR context as well this is the only possible way ... | 2021-12-09T18:02:49 | 2021-12-09T18:05:18 | {} | CONTRIBUTOR |
vuejs | core | 990,877,758 | 2,279 | Fuzzyma | @kepi0809 you sure? Afaik, undefined props are skipped | 2021-12-10T11:08:51 | 2021-12-10T11:08:51 | {} | NONE |
vuejs | core | 991,018,642 | 5,023 | zhenzhenChange | I see, that's why `watchPostEffect` is needed, `watchPostEffect` is not just shorthand for `Api` | 2021-12-10T14:28:14 | 2021-12-10T14:28:14 | {} | NONE |
vuejs | core | 991,257,999 | 5,092 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4736 | 2021-12-10T20:03:11 | 2021-12-10T20:03:11 | {} | MEMBER |
vuejs | core | 991,846,322 | 5,086 | lidlanca | note that calling unshift in a loop, invokes reactivity overhead per each call.
the lost of optimization mentioned is actually the overhead of the reactivity system implementation.
Adding 50 items to a 2000 items array will iterate the full list 50 times performing different check to maintain the reactivity sys... | 2021-12-12T07:09:46 | 2021-12-12T07:09:46 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 990,016,312 | 5,041 | codymikol | I'm interested in this as well and I can't seem to find a related issue. | 2021-12-09T16:33:06 | 2021-12-09T16:33:06 | {} | CONTRIBUTOR |
vuejs | core | 990,385,286 | 5,083 | RollingTL | Thanks. Will do this way. | 2021-12-09T23:07:37 | 2021-12-09T23:07:37 | {} | NONE |
vuejs | core | 991,056,178 | 5,078 | LinusBorg | In which case does this cause any problems/errors? | 2021-12-10T15:16:36 | 2021-12-10T15:16:36 | {} | MEMBER |
vuejs | core | 993,126,335 | 5,102 | lidlanca | in your example
you have a `<div>` wrapping the async component in the `<child>` component.
the div being the root element of the `<Child>`.
if you remove that, it will possibly be more accurate repro.
however based on the docs
>Once a `<suspense>` has resolved the contents of its default slot, it can ... | 2021-12-14T03:36:27 | 2021-12-14T03:36:27 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 990,336,386 | 5,083 | tony19 | You don't necessarily need to use Codesandbox or Stackblitz to create a reproduction. You can scaffold a new Vue 3 project with TypeScript and `<script setup>`, using either of the following commands. Then, edit the project to recreate the problem, upload to GitHub, and share a link here.
### `npm init vue my-projec... | 2021-12-09T22:13:13 | 2021-12-09T22:13:13 | {} | CONTRIBUTOR |
vuejs | core | 990,745,399 | 5,086 | posva | Let's keep one issue with https://github.com/vuejs/vue-next/issues/4318
In your case, you can use a few tricks like `Object.freeze()` or `markRaw()` to improve performance. There are a few other tricks in the docs too | 2021-12-10T08:51:15 | 2021-12-10T08:51:15 | {
"+1": 1
} | MEMBER |
vuejs | core | 990,866,500 | 2,279 | Fuzzyma | I think you ate killing some performance there because that function will lead to unnecessary rerendering. Why not just `v-bind="{...obj, is: undefined}"`? | 2021-12-10T10:53:39 | 2021-12-10T10:53:39 | {} | NONE |
vuejs | core | 992,753,423 | 5,101 | horia16 | I have uploaded an example video just to explain the behavior better.
https://user-images.githubusercontent.com/32731652/145868046-35f546df-8125-4312-9a29-d05df678b306.mp4
| 2021-12-13T18:30:08 | 2021-12-13T18:30:08 | {} | NONE |
vuejs | core | 994,382,967 | 5,110 | LinusBorg | Components with async setup **have to be** nested in a Suspense component. | 2021-12-15T06:50:40 | 2021-12-15T06:50:40 | {} | MEMBER |
vuejs | core | 996,544,405 | 5,132 | caozhong1996 | It seems about vue-cli, I tried it by vite that all is well.🤷 | 2021-12-17T08:55:04 | 2021-12-17T09:02:09 | {} | CONTRIBUTOR |
vuejs | core | 996,724,516 | 4,804 | benkroeger | anything else required here @posva ? | 2021-12-17T13:30:58 | 2021-12-17T13:30:58 | {} | NONE |
vuejs | core | 997,159,555 | 5,126 | ygj6 | Looks like the same problem as #3869.
The solution reference is as follows:
https://github.com/vuejs/vue-next/issues/3869#issuecomment-852115768 | 2021-12-18T07:17:02 | 2021-12-18T07:17:02 | {} | MEMBER |
vuejs | core | 998,618,114 | 5,144 | ygj6 | Duplicate of #2457 | 2021-12-21T09:33:16 | 2021-12-21T09:33:16 | {} | MEMBER |
vuejs | core | 991,021,604 | 5,082 | jaulz | The failing test does not fail in my local environment... | 2021-12-10T14:32:01 | 2021-12-10T14:32:01 | {} | CONTRIBUTOR |
vuejs | core | 993,338,612 | 4,314 | conanliuhuan | 确实很想要这样的功能！！！
有的时候在使用别的原生JS工具时，别人写的东西要求渲染成element才能用（例如开发editor.js的插件）。这种时候要想vue配合起来，只能考虑defineCustomElement。
然而vue3的这个功能总是会有一个shadow-root，导致全局的样式根本无法对vue的渲染结果起作用。这就非常尴尬了。 | 2021-12-14T09:22:40 | 2021-12-14T09:22:40 | {} | NONE |
vuejs | core | 995,493,307 | 5,122 | posva | Thanks but this is correct | 2021-12-16T06:54:51 | 2021-12-16T06:54:51 | {} | MEMBER |
vuejs | core | 997,174,836 | 5,126 | zhangyuang | 🤔 As the solution, i can't determine what should i do
What's your mean is i should use some library like js-dom and inserts ctx.teleports into the exactly dom node in server side? But if i use renderToNodeStream what should i do? | 2021-12-18T09:18:50 | 2021-12-18T09:18:50 | {} | CONTRIBUTOR |
vuejs | core | 899,838,192 | 4,341 | yyx990803 | Can't reproduce: I cloned the app, tried with both yarn and npm install, both successfully type check and build. | 2021-08-16T21:44:16 | 2021-08-16T21:44:16 | {} | MEMBER |
vuejs | core | 899,967,570 | 3,909 | zhangenming | 这样吗 挺尴尬的哈
我其实是觉得,
前面三行的代码是没有什么出错的几率的
这样让try只包括fn() 会让人更加醒目这里try的作用 | 2021-08-17T03:34:44 | 2021-08-17T03:34:44 | {} | CONTRIBUTOR |
vuejs | core | 900,398,138 | 4,363 | yyx990803 | Sorry I didn't see this PR when I worked on 57f10812
Do note your change actually breaks the case of mapping `<foo-qux>` to `FooQux` | 2021-08-17T15:28:03 | 2021-08-17T15:28:03 | {
"+1": 1
} | MEMBER |
vuejs | core | 900,469,207 | 4,357 | posva | In that case you should use a computed, not a default value for the prop.
| 2021-08-17T17:00:44 | 2021-08-17T17:00:44 | {} | MEMBER |
vuejs | core | 901,083,800 | 4,382 | LinusBorg | you are passing a string, so you get a string.
the recommended best practice for custom elements seems to be to use DOM properties for passing object/arrays values. Which Vue already does.
https://developers.google.com/web/fundamentals/web-components/best-practices#always-accept-primitive-data-strings,-numbers,-b... | 2021-08-18T12:44:12 | 2021-08-18T12:46:16 | {} | MEMBER |
vuejs | core | 901,758,658 | 2,220 | dev-itsheng | > > Hello, I realized a similar problem, and then tried to come to GitHub Issue to find a solution. I found it here, but it was not resolved. Finally, I figured out a way to solve this problem by myself, which is to customize the declaration file through the [module augmentation](https://www.typescriptlang.org/docs/han... | 2021-08-19T09:27:59 | 2021-08-19T09:27:59 | {} | CONTRIBUTOR |
vuejs | core | 901,767,587 | 4,387 | titld | 所以 你是怎么解决的呢？我也遇到这个问题了，key值这块儿好像没用，路由版本已经是最新的4.0了 | 2021-08-19T09:41:15 | 2021-08-19T09:42:26 | {} | NONE |
vuejs | core | 902,571,751 | 4,393 | posva | It should definitely be renamed to something else | 2021-08-20T09:43:07 | 2021-08-20T09:43:07 | {} | MEMBER |
vuejs | core | 899,819,958 | 4,322 | yyx990803 | Since this is also related to `v-model` + JSX typing + Volar, I'll close this one to keep the discussion in #4321. | 2021-08-16T21:09:03 | 2021-08-16T21:09:03 | {} | MEMBER |
vuejs | core | 900,054,065 | 4,358 | zhenzhenChange | - `node v14.9.0`
- `npm v6.14.8`
- `yarn v1.22.10`
- `Windows 10`
- `Google Chrome v92.0.4515.131` | 2021-08-17T07:13:55 | 2021-08-17T07:14:05 | {} | NONE |
vuejs | core | 901,441,575 | 4,374 | posva | This would require keeping track of all refs created with `toRef()` no matter where they come from, which could increase memory usage depending on libraries. In most cases, this shouldn't be a problem though.
If this really makes a difference in your application, you can still implement your own cached version with ... | 2021-08-18T21:27:09 | 2021-08-18T21:27:09 | {} | MEMBER |
vuejs | core | 901,798,160 | 4,389 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4294
| 2021-08-19T10:26:59 | 2021-08-19T10:26:59 | {} | MEMBER |
vuejs | core | 900,209,184 | 4,364 | Bigfish8 | I dont think this is a bug.You should guarantee 'option' is an object here. | 2021-08-17T11:17:11 | 2021-08-17T11:17:11 | {} | CONTRIBUTOR |
vuejs | core | 900,884,916 | 4,377 | LinusBorg | link is broken | 2021-08-18T07:26:30 | 2021-08-18T07:26:30 | {} | MEMBER |
vuejs | core | 900,895,301 | 4,376 | posva | This is mentioned in the RFC | 2021-08-18T07:44:41 | 2021-08-18T07:44:41 | {} | MEMBER |
vuejs | core | 900,895,727 | 4,377 | posva | Open a new issue with a working link and the steps in English, please | 2021-08-18T07:45:27 | 2021-08-18T07:45:27 | {} | MEMBER |
vuejs | core | 902,474,706 | 4,398 | posva | You can workaround by creating a copy of the component:
```js
createApp({...App}).mount("#app2");
``` | 2021-08-20T06:51:59 | 2021-08-20T06:51:59 | {
"+1": 4
} | MEMBER |
vuejs | core | 900,187,292 | 4,331 | Bigfish8 | > I don't even think this needs to be specifically about usage of scope variables. `v-once` isn't designed to be used inside `v-for` so the check and the warning message can both be simpler.
Thanks for the review, I will simplify it. | 2021-08-17T10:42:33 | 2021-08-17T10:42:33 | {} | CONTRIBUTOR |
vuejs | core | 900,852,132 | 4,378 | ygj6 | Upgrade the node version to v16.7.0, The test cases can be passed.
For details, see:
https://nodejs.org/dist/latest-v16.x/docs/api/webstreams.html#webstreams_web_streams_api | 2021-08-18T06:22:40 | 2021-08-18T06:22:40 | {
"hooray": 1
} | MEMBER |
vuejs | core | 901,682,724 | 4,388 | posva | Thank you but this avoids an extra call | 2021-08-19T07:37:50 | 2021-08-19T07:37:50 | {} | MEMBER |
vuejs | core | 901,763,556 | 4,389 | ygj6 | https://github.com/vuejs/vue-next/issues/4294#issuecomment-896082769 | 2021-08-19T09:35:05 | 2021-08-19T09:35:05 | {} | MEMBER |
vuejs | core | 901,855,377 | 4,387 | ygj6 | I have fixed @danyadev's project: https://github.com/ygj6/vue3-bug/tree/bug-2
Hope it could help you. | 2021-08-19T12:00:13 | 2021-08-19T12:00:13 | {} | MEMBER |
vuejs | core | 902,521,733 | 4,400 | posva | You can put the array in a ref as a workaround | 2021-08-20T08:18:22 | 2021-08-20T08:18:22 | {} | MEMBER |
vuejs | core | 902,547,798 | 4,393 | zhangenming | did we have two `toNumber` at the same time?
| 2021-08-20T09:02:55 | 2021-08-20T09:02:55 | {} | CONTRIBUTOR |
vuejs | core | 902,677,492 | 4,400 | LinusBorg | This isn't technically a bug, or is it? the items array is nonreactive, so refs are not unwrapped. The correct way to print the content in the template would be:
```html
<li v-for="(item, index) of items" :key="index">{{ item.label.value }}</li>
```
...and this renders the desired result. Alternatively, wrappi... | 2021-08-20T13:03:22 | 2021-08-20T13:11:53 | {
"+1": 1
} | MEMBER |
vuejs | core | 899,803,145 | 4,317 | yyx990803 | Note this only happens if both `style` and `:style` are used AND the value of `:style` is a constant (not referring any component state). Quite an edge case here... | 2021-08-16T20:38:42 | 2021-08-16T20:38:42 | {} | MEMBER |
vuejs | core | 900,060,508 | 4,360 | LinusBorg | No that's not possible. WE would have to parse the JS AST for this, which is not something that would fit into the browser build. | 2021-08-17T07:25:04 | 2021-08-17T07:25:04 | {} | MEMBER |
vuejs | core | 900,272,793 | 4,364 | oliverpool | > You should guarantee 'option' is an object here.
You are right, I just saw on https://v3.vuejs.org/api/directives.html#v-bind:
**Expects:** `any (with argument) | Object (without argument)` (my case is _without argument_, so it must be an object).
---
I fixed my code like this:
```
<slot v-bind="{ opt... | 2021-08-17T12:54:45 | 2021-08-17T12:54:45 | {} | NONE |
vuejs | core | 900,836,258 | 3,249 | LinusBorg | This no longer applies, see [this playground's](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aDE+e3sgbXNnIH19PC9oMT5cbjwvdGVtcGxhdGU+XG5cbjxzY3JpcHQgc2V0dXA+XG4gIGltcG9ydCB7cmVmfSBmcm9tICd2dWUnXG5jb25zdCBtc2cgPSByZWYoJ0hlbGxvIFdvcmxkIScpXG48L3NjcmlwdD4ifQ==) compiled JS output. | 2021-08-18T06:04:50 | 2021-08-18T06:04:50 | {
"+1": 1
} | MEMBER |
vuejs | core | 902,461,668 | 4,376 | klwfwdk | > This is mentioned in the RFC
why it works well in js, and only `lang="ts"` has error. | 2021-08-20T06:21:52 | 2021-08-20T06:21:52 | {} | CONTRIBUTOR |
vuejs | core | 899,824,298 | 4,321 | yyx990803 | @johnsoncodehk 77223df2 should fix the following cases:
- checkbox with Array `v-model` value
- `<input>` with non-primitive `value` bindings
However the case for radio needs to be fixed in Volar. Volar is mapping the `v-model` on a radio input to `checked`, which is incorrect:
```js
<input type="radio" v-mo... | 2021-08-16T21:16:43 | 2021-08-16T21:16:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 899,971,547 | 4,283 | zhangenming | @posva is this a bug? Can you reconsider reopen ? thank you | 2021-08-17T03:47:53 | 2021-08-17T03:47:53 | {} | CONTRIBUTOR |
vuejs | core | 900,761,392 | 4,373 | minikiller | @wtto00 thanks.
| 2021-08-18T02:20:49 | 2021-08-18T02:20:49 | {} | NONE |
vuejs | core | 901,079,795 | 4,382 | edison1105 | similar to https://github.com/vuejs/vue-next/issues/4370 | 2021-08-18T12:37:55 | 2021-08-18T12:37:55 | {} | MEMBER |
vuejs | core | 902,599,218 | 1,723 | SasanFarrokh | I think most of those who use SSR use the ClientOnly component (same as Nuxt) and they are using this implementation
```js
// https://github.com/frandiox/vite-ssr/blob/master/src/vue/components.ts
export const ClientOnly = defineComponent({
name: 'ClientOnly',
setup(_, { slots }) {
const show = ref(false)... | 2021-08-20T10:32:21 | 2021-08-20T10:32:43 | {} | NONE |
vuejs | core | 899,787,373 | 4,312 | yyx990803 | Note: the fix skips the import usage check since with a custom `lang`, `@vue/compiler-sfc` won't be able to reliably analyze the template to determine whether an import is used in the template or not. **This means if you are using Pug or other template pre-processors with `<script setup>` + TS, you will need to explici... | 2021-08-16T20:10:37 | 2021-08-16T20:10:50 | {
"+1": 2
} | MEMBER |
vuejs | core | 900,081,449 | 4,361 | posva | is this really a good idea? Because `Object.keys()` is slower than `for in` (even if it's called less often than rendering since it's in prop normalization) and there is no reason to support code that follows such a problematic antipattern as extending `Object.prototype`. Using such pattern will break in other librarie... | 2021-08-17T08:00:59 | 2021-08-17T08:03:08 | {} | MEMBER |
vuejs | core | 900,083,659 | 4,358 | zhenzhenChange | 好的，我再尝试一下找找问题所在。
但我想向你确认一点，在`<script setup lang="ts">`中，导入的组件，命名必须是要大写的对嘛？ | 2021-08-17T08:04:15 | 2021-08-17T08:07:41 | {} | NONE |
vuejs | core | 900,575,679 | 4,369 | yyx990803 | I think this is reasonable since it aligns with the compilation mental model and we already expose imports from normal `<script>` blocks as well. | 2021-08-17T19:34:35 | 2021-08-17T19:34:35 | {} | MEMBER |
vuejs | core | 900,757,112 | 4,373 | wtto00 | you should add [defineExpose](https://v3.vuejs.org/api/sfc-script-setup.html#defineexpose) in child component. | 2021-08-18T02:09:10 | 2021-08-18T02:09:10 | {} | NONE |
vuejs | core | 900,772,965 | 4,331 | Bigfish8 | Yes, I’ll be glad to. | 2021-08-18T02:53:33 | 2021-08-18T02:53:33 | {} | CONTRIBUTOR |
vuejs | core | 901,156,166 | 4,381 | jods4 | See #4318 | 2021-08-18T14:20:17 | 2021-08-18T14:20:17 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 901,309,128 | 4,380 | LinusBorg | > But I think props in component is designed to validate type rather than change type.
I agree with this - but the wc wrapper could cast strings to numbers if the component expects a number for a given prop. | 2021-08-18T17:47:52 | 2021-08-18T17:47:52 | {
"+1": 1
} | MEMBER |
vuejs | core | 902,201,155 | 4,314 | gnuletik | Also looking forward this proposal !
As of today, I did not find any way to share CSS across multiple components using Vue+Vite (CSS `@import` are processed by `postcss-import` on Vite, which inlines shared CSS in each component). | 2021-08-19T19:58:47 | 2021-08-19T19:58:47 | {
"+1": 2,
"eyes": 1
} | NONE |
vuejs | core | 899,794,101 | 4,312 | spenserblack | Thank you for the fix! :tada:
> **This means if you are using Pug or other template pre-processors with `<script setup>` + TS, you will need to explicitly import types with `import type { xxx } from '...'`** to avoid them from being returned from `setup()` during dev.
Because of this, would it be recommended to a... | 2021-08-16T20:21:32 | 2021-08-16T20:21:32 | {} | NONE |
vuejs | core | 899,797,026 | 4,354 | yyx990803 | This is intentional for now, since `deferredComputed` doesn't provide 100% consistent behavior as normal `computed`. It is currently only exported in `@vue/reactivity` for testing / internal use cases. | 2021-08-16T20:27:05 | 2021-08-16T20:27:05 | {
"+1": 1
} | MEMBER |
vuejs | core | 900,250,364 | 4,357 | zumm | ```vue
// component1.vue
<template>
<span>Prop1: {{ prop1 }}</span>
<span>Prop2: {{ prop2 }}</span>
<template>
<script>
export default {
name: 'Component1',
props: {
prop1: {
type: String,
required: true
},
prop2: {
type: String,
default: (props) => props.prop... | 2021-08-17T12:22:17 | 2021-08-17T12:22:17 | {} | NONE |
vuejs | core | 900,435,988 | 4,331 | yyx990803 | Could you also add the same check for `v-memo` since they have the same limitations? | 2021-08-17T16:14:38 | 2021-08-17T16:14:38 | {} | MEMBER |
vuejs | core | 900,465,226 | 4,369 | posva | I'm not sure this is safe to do this automatically without creating a breaking change. Having to alias it seems like a very reasonable way to do it since having expensive operations inside of an SFC is not something that happens that often:
```vue
<template>
<h1>{{ msg }} {{ name }}</h1>
</template>
<script>... | 2021-08-17T16:55:07 | 2021-08-17T16:55:07 | {} | MEMBER |
vuejs | core | 900,790,849 | 3,249 | dengrc | Double <script>
Don’t need to export, put the first one
```typescript
<script lang="ts">
import { ref } from 'vue'
</script>
<script setup lang="ts">
const expanded = ref(false)
</script>
``` | 2021-08-18T03:49:30 | 2021-08-18T03:49:30 | {} | NONE |
vuejs | core | 902,112,452 | 4,385 | LinusBorg | I'm not super familiar with Vue 2 SSR as I never built something worthwhile with it, but I don't think we have `context.renderStyles()` ... where would you get them from now, and what do they return? The actual code or links to the chunks output by the bundler? | 2021-08-19T17:40:11 | 2021-08-19T17:40:11 | {} | MEMBER |
vuejs | core | 902,168,856 | 4,392 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/4370 | 2021-08-19T19:07:23 | 2021-08-19T19:07:23 | {} | MEMBER |
vuejs | core | 900,076,956 | 4,358 | HcySunYang | 没有重新我们无法给你更多帮助 | 2021-08-17T07:53:41 | 2021-08-17T07:53:41 | {} | MEMBER |
vuejs | core | 900,091,991 | 4,358 | HcySunYang | 不必须大写 | 2021-08-17T08:16:34 | 2021-08-17T08:16:34 | {} | MEMBER |
vuejs | core | 901,370,936 | 4,382 | posva | Probably worth adding a note to docs at https://v3.vuejs.org/guide/web-components.html#definecustomelement. Could you open a PR or issue in the vuejs/docs repo? | 2021-08-18T19:25:31 | 2021-08-18T19:25:31 | {} | MEMBER |
vuejs | core | 901,850,622 | 3,688 | chukwumaokere | I'm having this very issue running vue 3.2.4
package.json: "vue": "^3.2.4"
```
<script>
export default {
...
setup(){
...
let boardThemeLight = Themes.cpc_board_theme[0]; // Themes.cpc_board_theme is just a basic array ['#646372','#353340']
let boardThemeDark = Themes.cpc_board_theme[1]; // ['#646... | 2021-08-19T11:51:39 | 2021-08-19T11:52:41 | {} | NONE |
vuejs | core | 902,194,300 | 4,380 | posva | This shared function `toNumber()` is also used in other places like `v-model` so I don't think it's a good idea to change its behavior | 2021-08-19T19:47:47 | 2021-08-19T19:47:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 902,512,583 | 4,399 | posva | Duplicate of https://github.com/vuejs/vue-next/issues/1359 | 2021-08-20T08:03:39 | 2021-08-20T08:03:39 | {} | MEMBER |
vuejs | core | 900,046,123 | 4,358 | zhenzhenChange | https://gitee.com/zhenzhenChange/vue-next-issuse-4358 [GitHub 被墙了，推不上]
[](https://imgtu.com/i/f48xpQ)
---
[](https://imgtu.com/i/f4GanI)
---
[](... | 2021-08-17T07:01:49 | 2021-08-17T07:11:07 | {} | NONE |
vuejs | core | 900,218,339 | 4,364 | LinusBorg | It's definitely not documented usage, but worked in 3.1.5.
Conceptually/technically, it make some sense, as the slot content is a function receiving an argument, which *could* just be a string or any other type of value, there's not technical limitation saying it has to be an object on that end.
So we *could* ar... | 2021-08-17T11:32:19 | 2021-08-17T11:35:22 | {} | MEMBER |
vuejs | core | 900,896,102 | 4,370 | ygj6 | There are some bugs here:
https://github.com/vuejs/vue-next/blob/872b3f7ec5e1a41c60018bb1f64d841c309b8939/packages/runtime-dom/src/apiCustomElement.ts#L248-L250
Will convert `attribute` to `number`. | 2021-08-18T07:46:05 | 2021-08-18T07:46:05 | {} | MEMBER |
vuejs | core | 901,144,076 | 4,380 | LinusBorg | I don't think this is a real fix/solution for #4370.
While it would improve problems in converting numbers, the real issue is that `_setAttrs` in the custom element class doesn't respect the component's prop type. it should not convert it to a number if the component expects a string.
| 2021-08-18T14:05:17 | 2021-08-18T14:05:17 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.