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,100,855,584 | 5,738 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | fb3177040407587dc1bc70e1374042594472e869 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-17T11:17:08 | 2022-04-24T10:40:48 | {} | NONE |
vuejs | core | 1,108,241,278 | 5,798 | LinusBorg | Such proposals belong into an RFC -> www.github.com/vuejs/rfcs | 2022-04-25T08:24:31 | 2022-04-25T08:24:31 | {} | MEMBER |
vuejs | core | 1,108,631,124 | 5,802 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 43f240246dd266d275c025a44bd34ca2328d1b55 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-25T14:12:24 | 2022-04-25T14:15:03 | {} | NONE |
vuejs | core | 1,107,044,602 | 5,787 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8118e42b31bce289cc9634118e81880c8779ab39 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-22T23:37:17 | 2022-04-25T16:16:21 | {} | NONE |
vuejs | core | 1,109,703,154 | 5,584 | zkwolf | I also meet this problem, I think this error should be output in dev env. | 2022-04-26T11:55:12 | 2022-04-26T11:55:12 | {
"+1": 10
} | NONE |
vuejs | core | 1,107,694,493 | 5,218 | gumingWu | NOW! I have the new ideas, if I want to write the JSX in `<script setup>`, maybe vue can supply a new API, like **defineTemplate**
E.g.
```vue
<script lang="ts">
setup() {
return () => (
<div></div>
)
}
</script>
```
——————
```vue
<script setup>
const msg = ref('hi')
defineTemplate(() =... | 2022-04-24T03:05:08 | 2022-04-24T03:05:08 | {
"+1": 2,
"eyes": 2,
"heart": 1,
"hooray": 1,
"laugh": 1,
"rocket": 1
} | NONE |
vuejs | core | 1,107,978,956 | 5,218 | gumingWu | #5798
@sxzz let's talk in new issue~ | 2022-04-25T01:47:48 | 2022-04-25T01:47:48 | {} | NONE |
vuejs | core | 1,107,044,615 | 5,787 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8118e42b31bce289cc9634118e81880c8779ab39 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-22T23:37:19 | 2022-04-25T16:10:48 | {} | NONE |
vuejs | core | 1,106,948,503 | 5,785 | LinusBorg | Assuming we don't have to adjust our types and this just works, this limitation still exist for TS <4.7 (and that version is still in beta afaik).
When 4.7 is released and we have tested this, we could move this to the docs repo and amend the docs accordingly. | 2022-04-22T22:27:28 | 2022-04-22T22:27:28 | {
"rocket": 1
} | MEMBER |
vuejs | core | 1,107,749,272 | 5,792 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 444860da80b4c253ebc6263769efb232c7466065 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-24T06:27:41 | 2022-04-24T06:29:58 | {} | NONE |
vuejs | core | 1,108,170,811 | 5,800 | Justineo | 提供复现请不要引入第三方库，或者请先提交 issue 给此第三方库，排除是第三方库本身的问题。 | 2022-04-25T07:21:00 | 2022-04-25T07:21:00 | {} | MEMBER |
vuejs | core | 1,109,730,614 | 5,809 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | b4732dc63faac1b9909a3c68cecba6ce9a929c1e |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-26T12:23:50 | 2022-04-26T15:12:35 | {} | NONE |
vuejs | core | 1,106,826,772 | 5,784 | maiomiaoh | Thanks! I didn't know has `.attr` modifier | 2022-04-22T20:15:45 | 2022-04-22T20:15:45 | {} | NONE |
vuejs | core | 1,107,835,332 | 5,796 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 775fefd15d74316c62c80b02591b1149bd1650f8 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-24T12:49:30 | 2022-04-24T12:50:11 | {} | NONE |
vuejs | core | 1,108,051,115 | 5,788 | hchlq | > 这种需求算好么？为什么要在事件里面使用async呢？给他绑定一个异步函数我觉得更好吧
正常情况下也不会有人这样写，而且这也不是一个需求吧，vue中本来就支持这种写法的，只是缺少了对单参无括号这样种场景的处理而已 | 2022-04-25T04:03:52 | 2022-04-25T04:22:32 | {} | CONTRIBUTOR |
vuejs | core | 1,108,262,228 | 5,801 | LinusBorg | you emit the same object twice. So the parent doesn't nee to re-render - its still the same value, the same object.
And since the object is not reactive, the fact that you did change a property of the object isn't detected and can't trigger a re-render either.
That's pretty much the basic principle of Vue & React... | 2022-04-25T08:42:42 | 2022-04-25T08:45:05 | {} | MEMBER |
vuejs | core | 1,108,452,930 | 5,801 | LinusBorg | yes.
relevant: https://vuejs.org/guide/essentials/reactivity-fundamentals.html#reactive-proxy-vs-original-1 | 2022-04-25T11:30:50 | 2022-04-25T11:32:15 | {} | MEMBER |
vuejs | core | 1,106,767,280 | 5,783 | posva | I don't think you are supposed to call the `watch` within a `watch` because then they are not related. You could however move the watch outside or create a nested effectScope to create watchers whenever you want [like this](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcb... | 2022-04-22T18:41:20 | 2022-04-22T18:41:20 | {} | MEMBER |
vuejs | core | 1,106,775,382 | 5,775 | posva | I would say you need to use [true-value](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgZmlyc3RPcHRpb24gPSByZWYodHJ1ZSk7XG5jb25zdCBzZWNvbmRPcHRpb24gPSByZWYoMSk7XG5jb25zdCB0aGlyZE9wdGlvbiA9IHJlZihcIjFcIik7XG4gIFxuICBjb25zdCBkeW5hbWljT3B0aW9uID0gcmVmKDApO1xuPC9z... | 2022-04-22T18:53:59 | 2022-04-22T18:53:59 | {} | MEMBER |
vuejs | core | 1,106,780,563 | 5,784 | posva | No, because some DOM properties could be expecting `undefined` as a possible value. You can and probably should reformat the object passed to v-bind in order to ensure valid values. As an example: you wouldn't pass `:size="size"` if size could be `null` or 0.
[You can force it as an attribute](https://sfc.vuejs.org/... | 2022-04-22T19:02:03 | 2022-04-22T19:02:03 | {} | MEMBER |
vuejs | core | 1,107,430,041 | 5,788 | hchlq | ```js
// 一种支持的方法
const fnExpRE =
/^\s*([\w$_]+|(async\s*)?(\([^)]*?\)|[^(]+))\s*=>|^\s*(async\s+)?function(?:\s+[\w$]+)?\s*\(/
``` | 2022-04-23T08:25:13 | 2022-04-23T08:25:13 | {} | CONTRIBUTOR |
vuejs | core | 1,107,435,797 | 5,777 | LinusBorg | > he fix should work for that use case as well
> the getter and setter are transparent, and the unwrapping will still be handled as
> expected by shallowUnwrapHandlers of the setupState.
>
> the only case that I am not covering is class and function declaration, which are analyzed as setup-const but in fact are al... | 2022-04-23T08:48:56 | 2022-04-23T08:48:56 | {} | MEMBER |
vuejs | core | 1,107,689,555 | 5,791 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 974a5d12db0d6cb19380ce91d9d66a7066534509 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-24T02:32:00 | 2022-04-24T02:34:26 | {} | NONE |
vuejs | core | 1,107,792,742 | 5,794 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 55a61c9e85e161c57ec09476d75182288c070deb |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-24T08:46:23 | 2022-04-24T08:57:24 | {} | NONE |
vuejs | core | 1,109,226,155 | 5,783 | edison1105 | @posva @LinusBorg
I feel this is a bug,because `effects` may be changed when an effect stoped.thats why the error is shown.
https://github.com/vuejs/core/commit/2993a246181df12e367b7abdfce0954244e8f7ec#diff-ac9e1628a205e241a9796fcffbdb27ae0dda80494c45a0830ee67309a1e3052fR57-R66
| 2022-04-26T02:15:04 | 2022-04-26T06:36:26 | {} | MEMBER |
vuejs | core | 1,109,411,449 | 5,806 | liulinboyi | > > @edison1105 Because of [this](https://developer.mozilla.org/zh-CN/docs/Web/JavaScript/Reference/Global_Objects/Array/forEach#%E5%A6%82%E6%9E%9C%E6%95%B0%E7%BB%84%E5%9C%A8%E8%BF%AD%E4%BB%A3%E6%97%B6%E8%A2%AB%E4%BF%AE%E6%94%B9%E4%BA%86%EF%BC%8C%E5%88%99%E5%85%B6%E4%BB%96%E5%85%83%E7%B4%A0%E4%BC%9A%E8%A2%AB%E8%B7%B3%E... | 2022-04-26T06:47:04 | 2022-04-26T06:47:04 | {} | MEMBER |
vuejs | core | 1,109,456,298 | 5,807 | coder-hxl | 这种用法是错误的，当你使用default插槽时，会把default插槽原先的内容替换掉。header插槽和footer插槽不存在于default里面，Vue也就无法找到这两个插槽 | 2022-04-26T07:40:32 | 2022-04-26T07:53:50 | {
"+1": 2
} | NONE |
vuejs | core | 1,103,897,699 | 5,759 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 7b7339fb8ef40901e25fd81b12496cbbfe6bf6bd |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-20T12:53:24 | 2022-04-26T11:05:37 | {} | NONE |
vuejs | core | 1,109,809,288 | 5,761 | bodograumann | Ah, thank you for the tip, @iwusong. Setting a key on the `v-if` items is a good workaround. | 2022-04-26T13:37:42 | 2022-04-26T13:37:42 | {} | NONE |
vuejs | core | 1,107,451,762 | 5,788 | hchlq | @edison1105 PR submitted | 2022-04-23T10:53:41 | 2022-04-23T10:53:41 | {} | CONTRIBUTOR |
vuejs | core | 1,107,749,276 | 5,792 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 444860da80b4c253ebc6263769efb232c7466065 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-24T06:27:42 | 2022-04-24T06:28:41 | {} | NONE |
vuejs | core | 1,107,776,653 | 4,397 | ubershmekel | I was getting:
> error TS2339: Property 'openModal' does not exist on type
Until I updated my vue-tsc from 0.29.8. Here's the fix:
```
npm install "vue-tsc@>=0.34.10"
``` | 2022-04-24T07:10:21 | 2022-04-24T07:10:21 | {
"+1": 5
} | NONE |
vuejs | core | 1,107,824,440 | 4,294 | TuringJest | @jnarowski here is a little workaround which might work for you if you want to get Intellisense for props from an imported interface on your wrapper. Tested in VsCode with Volar.
Vue will not create props for properties on the imported interface but we still can pass them through with $attrs and then provide Intel... | 2022-04-24T11:46:31 | 2022-04-24T11:48:24 | {
"+1": 2,
"eyes": 1,
"heart": 1
} | NONE |
vuejs | core | 1,107,842,939 | 5,797 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d59698056ca3cbbfbcb645cd2eb4af98e24a9675 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-04-24T13:32:36 | 2022-04-24T13:33:29 | {} | NONE |
vuejs | core | 1,107,842,937 | 5,797 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | d59698056ca3cbbfbcb645cd2eb4af98e24a9675 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-04-24T13:32:36 | 2022-04-24T13:34:51 | {} | NONE |
vuejs | core | 1,108,049,328 | 5,218 | lihanspace | I think try not to change `<script>`, maybe `defineName('Foo')` is better. | 2022-04-25T04:00:50 | 2022-04-25T04:00:50 | {
"+1": 1,
"confused": 3,
"eyes": 2,
"heart": 1,
"hooray": 1,
"laugh": 1,
"rocket": 1
} | NONE |
vuejs | core | 1,108,309,351 | 5,800 | wang-weilin | > ### There is an example and like your example, but it is running correctly.
> [SFC Example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSc7XG5pbXBvcnQgZWxJbWFnZSBmcm9tICcuL2VsLWltYWdlLnZ1ZSdcblxuY29uc3QgdW5mb2xkID0gKCkgPT4ge1xuICBhbGVydCgnMTExMTExMTExMTExJyk7XG59O1xuPC... | 2022-04-25T09:19:43 | 2022-04-25T09:19:43 | {} | NONE |
vuejs | core | 1,108,731,364 | 5,803 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vuejs-coverage* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c51a9f7b80814d60bed681b84146db398a1f4530 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https://... | 2022-04-25T15:35:19 | 2022-04-25T15:41:29 | {} | NONE |
vuejs | core | 1,027,714,255 | 5,339 | LinusBorg | This is a bit tricky as the current implementation of v-model on `select` elements does set the `selected` attribute on `mounted`, and do so on purpose, because it has to wait for the options to be rendered to then pick the right one to set the attribute on.
So in that sense, this works as intended and it's not real... | 2022-02-02T08:55:45 | 2022-02-02T08:56:09 | {} | MEMBER |
vuejs | core | 1,028,449,026 | 5,353 | lidlanca | `rawSlot` after an update will already be normalized.
resulting in a normalized slot function being normalized over and over.
with enough updates calling the normalized slot will reach the max stack size
https://github.com/vuejs/core/blob/644971ec06642817cf7e720ad4980182d2140f53/packages/runtime-core/src/compone... | 2022-02-02T23:19:04 | 2022-02-02T23:19:04 | {} | CONTRIBUTOR |
vuejs | core | 1,031,957,041 | 3,874 | lukewarlow | Just tested on latest Vue and it's still reproducible. | 2022-02-07T21:40:25 | 2022-02-07T21:40:25 | {} | NONE |
vuejs | core | 1,032,072,738 | 5,370 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 938dbb97bb82b7a2468d9dd177b2b413a3193476
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/6201b4de6bb5ab000798cd79](https://app.netlify.com/sites/vue-sfc-playground/deploys/6201b4de6bb5ab000798cd79)
... | 2022-02-08T00:10:11 | 2022-02-08T00:12:40 | {} | NONE |
vuejs | core | 1,024,966,852 | 5,333 | posva | > I'll reopen this to re-evaluate one specific thing: attrs from parent overrwriting explicit props in the child
I don't think the fact it's is a prop or an attribute matters.
Since `name` is merged from App.vue template into `Comp.vue`, it makes sense for it to override the attribute/prop (going top down). | 2022-01-29T18:53:07 | 2022-01-29T18:53:07 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,026,210,823 | 2,027 | bglaz | It looks like these warnings are coming from the new vue dev tools chrome extension. | 2022-01-31T21:08:07 | 2022-01-31T21:08:07 | {} | NONE |
vuejs | core | 1,027,301,066 | 4,756 | mnorthern2 | Someone wrote an article on this that offers a solution, albeit a very intricate one:
https://ckhconsulting.com/vue-typescript-debuggers/#correct-source-map
Note that it only works for Vue CLI 4, and it needs to be altered for Vue CLI 5. However, the altered version (or at least the one I wrote) doesn't work when u... | 2022-02-01T21:23:00 | 2022-02-02T20:34:43 | {} | NONE |
vuejs | core | 1,030,905,803 | 5,360 | espresso | @LinusBorg
I've been able to remedy this issue by removing the block of code that validates this specific condition.
**Line 155 of errors.ts:**
```[ErrorCodes.X_V_FOR_TEMPLATE_KEY_PLACEMENT]: `<template v-for> key should be placed on the <template> tag.`,```
**Line 121 of vFor.ts:**
```
// check <... | 2022-02-06T20:14:47 | 2022-02-06T20:14:47 | {} | NONE |
vuejs | core | 1,031,196,205 | 5,366 | LinusBorg | https://github.com/vuejs/rfcs | 2022-02-07T08:28:59 | 2022-02-07T08:28:59 | {} | MEMBER |
vuejs | core | 1,031,505,008 | 5,367 | JoostKersjes | I could be off-base here, but I think the problem statement above is the issue related to this Typescript error.
```
error TS2322: Type 'HTMLLIElement' is not assignable to type '{ type: string; value: number; addEventListener: { <K extends keyof HTMLElementEventMap>(type: K, listener: (this: HTMLLIElement, ev: HTMLE... | 2022-02-07T14:07:01 | 2022-02-07T14:07:01 | {
"+1": 1
} | NONE |
vuejs | core | 1,024,749,561 | 5,322 | lidlanca | sound like `undefined` or `false` should not be used.
but handling this edge case, will add checks for an edge case that can be easily avoided.
use empty string `''` or `null` to remove
and this will be on par with how the native `style.setProperty` works.
I would have said, just remove the style from the ob... | 2022-01-28T23:49:23 | 2022-01-28T23:49:23 | {} | CONTRIBUTOR |
vuejs | core | 1,024,917,634 | 5,252 | zmcode | 你需要缓存的页面必须被同一个父级包裹, 而不是祖先级, 而你的m/ index.vue文件 并没有设置keepAlive 所以无法缓存m1 和 m2, <keep-alive> 是用在其一个直属的子组件被切换的情形, 可以详细看下vue的文档: https://v3.cn.vuejs.org/api/built-in-components.html#keep-alive
修改代码: https://codesandbox.io/s/keen-phoebe-q5m8d?file=/src/layout/pages/m/index.vue | 2022-01-29T14:02:21 | 2022-01-29T14:03:48 | {} | NONE |
vuejs | core | 1,026,569,213 | 5,349 | Rolanddoda | Ahh nvm, I found out that I have to use `defineAsyncComponent` to make it work:
```js
computed: {
dynamicComponent() {
return defineAsyncComponent(() => import(`./icons/${this.name}.vue`))
}
}
``` | 2022-02-01T08:04:36 | 2022-02-01T08:04:36 | {} | NONE |
vuejs | core | 1,028,377,010 | 5,339 | LinusBorg | Radio buttons are different, as Vue can evaluate each one on their own during render, and thus can set the checked attribute before mounting the element.
The select element on the other hand needs to compare its v-model value to the options children that are created independently from it.
Not saying this is not s... | 2022-02-02T21:31:47 | 2022-02-02T21:31:47 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,029,877,237 | 5,361 | message163 | I read the example of the official website. I thought it would lose the response before mounting. I misunderstood it | 2022-02-04T10:57:52 | 2022-02-04T10:57:52 | {} | NONE |
vuejs | core | 1,030,594,118 | 4,294 | LinusBorg | @mesqueeb This is possible with a bit of type magic, yes.
```ts
import {
ExtractPropTypes,
ExtractDefaultPropTypes,
} from 'vue'
import { SetOptional } from 'type-fest'
export type ExternalProps<T extends Record<string | number | symbol, {}>>
= SetOptional<ExtractPropTypes<T>, keyof ExtractDefaultProp... | 2022-02-05T10:11:44 | 2022-02-05T10:29:29 | {
"eyes": 2,
"heart": 6
} | MEMBER |
vuejs | core | 1,030,635,930 | 5,362 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: ea98cfeccded9e1ec1402254b6f2aeec2e7fc3cb
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61fe8ba4ec11e20008c45bd0](https://app.netlify.com/sites/vue-sfc-playground/deploys/61fe8ba4ec11e20008c45bd0)
... | 2022-02-05T14:37:30 | 2022-02-05T14:40:30 | {} | NONE |
vuejs | core | 1,031,020,889 | 5,281 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: ab2f0ee9a5db0a5f916ee35d83b2dbbca7d7d94b
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620089aec53b8300083982be](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-07T02:53:39 | 2022-02-07T02:54:39 | {} | NONE |
vuejs | core | 1,031,272,004 | 5,281 | ygj6 | @LinusBorg The change of this part mainly solve the following problems: when setting a property, only the first setting is valid, and the subsequent settings are invalid.
Like the example in the test case:
```
const E = defineCustomElement({
render() {
return [
h('div', null, this.$a... | 2022-02-07T09:52:11 | 2022-02-07T09:52:11 | {} | MEMBER |
vuejs | core | 1,032,072,733 | 5,370 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 938dbb97bb82b7a2468d9dd177b2b413a3193476
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/6201b4de1c305e0007f4ee8a](https://app.netlify.com/sites/vuejs-coverage/deploys/6201b4de1c305e0007f4ee8a)
😎 Browse th... | 2022-02-08T00:10:11 | 2022-02-08T00:16:22 | {} | NONE |
vuejs | core | 1,025,115,097 | 5,333 | LinusBorg | It's an edge-case, but a breaking change that we so far haven't documented.
https://jsfiddle.net/Linusborg/qoxj71f8/6/ | 2022-01-30T10:39:04 | 2022-01-30T10:39:04 | {} | MEMBER |
vuejs | core | 1,029,728,181 | 5,359 | LinusBorg | watchEffect tracks all reactive property access that happens during synchronous execution. So this is expected and can't be prevented automatically for the reasons you laid out yourself.
You can regulate what gets tracked by pushing something on a next Tick, for example:
```js
watchEffect(async ()=> {
const msg... | 2022-02-04T07:38:46 | 2022-02-04T07:39:20 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,029,824,523 | 5,360 | petterw03 | Thank you @lidlanca for the workaround, it works well but is indeed a workaround. As already mentioned, this is not a duplicate since the previous issue addresses the console warning - however the console warning isn't a bug but the compiler error is, and it cannot be suppressed or ignored (unlike the warning). | 2022-02-04T10:04:18 | 2022-02-04T10:04:18 | {} | NONE |
vuejs | core | 1,032,253,706 | 4,344 | tangjiahui-cn | if you build with rollup. please add "external: ["vue"]" in build config file.like this:
`export default {
...
external: [
"vue"
],
...
}` | 2022-02-08T06:23:01 | 2022-02-08T06:23:01 | {
"+1": 2,
"heart": 1
} | NONE |
vuejs | core | 1,024,858,755 | 5,342 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 507b5739085030641598436998f44fc2ae92aee1
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61f4f0e3a471aa0008f56fd3](https://app.netlify.com/sites/vuejs-coverage/deploys/61f4f0e3a471aa0008f56fd3)
😎 Browse th... | 2022-01-29T07:46:48 | 2022-01-29T07:52:27 | {} | NONE |
vuejs | core | 1,025,116,735 | 5,337 | LinusBorg | This is not strictly necessary as github redirects `vue-next` to `core` automatically | 2022-01-30T10:50:10 | 2022-01-30T10:50:10 | {} | MEMBER |
vuejs | core | 1,025,235,643 | 5,346 | LinusBorg | Don't use a string, use the component directly. [sfc](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiwgZGVmaW5lQXN5bmNDb21wb25lbnQgfSBmcm9tICd2dWUnXG5jb25zdCBNeUlucHV0ID0gZGVmaW5lQXN5bmNDb21wb25lbnQoKCk9PmltcG9ydCgnLi9NeUlucHV0LnZ1ZScpKVxuPC9zY3JpcHQ+XG5cbjx0ZW1wbGF0ZT5cbiAgPGNvbXBvbmVudCA... | 2022-01-30T21:30:28 | 2022-01-30T21:30:51 | {} | MEMBER |
vuejs | core | 1,025,470,390 | 5,335 | marstamm | If it is expected, would it be possible to throw a more expressive error message? Currently, users just get a rather cryptic `property 'foo' is a read-only and non-configurable`. They then assume it is a problem with the library, as the Error is thrown from there. [Example](https://forum.bpmn.io/t/is-bpmn-js-currently-... | 2022-01-31T08:04:50 | 2022-01-31T08:04:50 | {} | NONE |
vuejs | core | 1,028,345,734 | 4,756 | mnorthern2 | To add to my previous comment, it seems using the script setup syntax also has a line offset issue. However, unlike the normal TS compilation problems, the offset seems to vary from component to component, making it unpredictable such that the solution I linked doesn't work. Even when I set the offset to test a single ... | 2022-02-02T20:49:57 | 2022-02-02T20:49:57 | {} | NONE |
vuejs | core | 1,028,824,843 | 5,184 | martijn10kb | We are using vue in jsx format, so we dont have any v-fors and v-ifs | 2022-02-03T10:08:52 | 2022-02-03T10:08:52 | {} | NONE |
vuejs | core | 1,029,088,855 | 3,102 | 07akioni | I've a hacky workaround (with setup only), it works for tsx, ts, template. However I don't recommend it.
I think it isn't a good idea to implement a generic component before vue officially support it.
```tsx
import { h, OptionHTMLAttributes, SelectHTMLAttributes, VNodeChild } from 'vue'
/**
* tsconfig:
*
... | 2022-02-03T15:11:25 | 2022-02-03T15:16:29 | {
"+1": 6
} | CONTRIBUTOR |
vuejs | core | 1,029,810,396 | 5,360 | lidlanca | possible workaround [sfc](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbiAgaW1wb3J0IHsgcmVmIH0gZnJvbSAndnVlJ1xuXG4gIGNvbnN0IGdyb3VwcyA9IHJlZihbXG4gICAge1xuICAgICAgbmFtZTogJ1Zvd2VscycsXG4gICAgICBpZDogMCxcbiAgICAgIGxldHRlcnM6IFsnYScsICdlJywgJ2knXSxcbiAgICB9LFxuICAgIHtcbiAgICAgIG5hbWU6ICdDb25zb25hbnRzJyxcbiA... | 2022-02-04T09:44:41 | 2022-02-04T09:44:41 | {} | CONTRIBUTOR |
vuejs | core | 1,030,588,754 | 4,294 | mesqueeb | @LinusBorg
when we define the props via the JS way (to be able to import/export) like so:
```js
export const mySharedProps = {
user: {
type: Object as PropType<User | undefined>,
default: undefined
}
}
```
is there any way to then _extract_ a type that would look like this:
```ts
export t... | 2022-02-05T09:32:09 | 2022-02-05T09:32:09 | {} | NONE |
vuejs | core | 1,032,134,292 | 5,368 | ygj6 | Looks like a typo here: https://github.com/vuejs/sponsors-automation/blob/main/public/sponsors.svg | 2022-02-08T02:02:01 | 2022-02-08T02:02:01 | {
"eyes": 1
} | MEMBER |
vuejs | core | 1,024,858,758 | 5,342 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 507b5739085030641598436998f44fc2ae92aee1
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f4f0e314349e0007908409](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f... | 2022-01-29T07:46:49 | 2022-01-29T07:47:34 | {} | NONE |
vuejs | core | 1,024,896,340 | 5,344 | edison1105 | should be `v-if="$slots.heading"` | 2022-01-29T11:49:33 | 2022-01-29T11:49:33 | {} | MEMBER |
vuejs | core | 1,024,896,616 | 5,344 | mika76 | Thanks @edison1105 , you know I promise I tried that like 5 times, but I must have had a typeo somewhere. Seems to work thanks 😅 | 2022-01-29T11:51:12 | 2022-01-29T11:57:55 | {} | NONE |
vuejs | core | 1,024,895,560 | 4,733 | mika76 | EDIT: Seems it works just fine, ignore this comment.
Previous Comment...
@andrey-hohlov I might have spoken too soon - I don't think `vnode.type === Comment` and `vnode.type !== Text` actually work - the text one at least is of type `Symbol("Text")` (on vue 3.2.26 at least) - also I have not managed to get a commen... | 2022-01-29T11:44:24 | 2022-01-31T07:13:43 | {} | NONE |
vuejs | core | 1,026,948,474 | 5,347 | LinusBorg | I rather suspect the issue with with a limitation of ts-loader, as described in the new docs:
https://staging.vuejs.org/guide/typescript/overview.html#note-on-vue-cli-and-ts-loader
> ts-loader can only type check post-transform code.
Doing typechecking with `vue-tsc` works fine in the provided repo. I just th... | 2022-02-01T15:11:18 | 2022-02-01T15:11:18 | {} | MEMBER |
vuejs | core | 1,028,804,862 | 5,347 | mia1024 | I think this is a separate issue from https://github.com/vuejs/vue-loader/issues/1915 because the workaround that applies to the issue doesn't apply here.
Also, is there a way to add a switch so that the generated TS code can have a `// @ts-ignore` above line 4 to avoid the error? The documentations linked only men... | 2022-02-03T09:55:08 | 2022-02-03T09:55:08 | {} | NONE |
vuejs | core | 1,029,621,564 | 3,102 | agileago | @07akioni maybe we can use class component + tsx. and it can solve all the pain points. see https://agileago.github.io/vue3-oop/
### example
```typescript
import { type ComponentProps, Mut, VueComponent } from 'vue3-oop'
import type { VNodeChild } from 'vue'
interface GenericCompProp<T> {
data: T[]
slo... | 2022-02-04T04:22:32 | 2022-02-04T04:22:32 | {} | NONE |
vuejs | core | 1,030,261,604 | 5,359 | LinusBorg | > Do you want me to open an issue over in the vuex repo to discuss this? I think it makes a lot of sense, and is also what I expected initially.
Yes. Could be an actual bug in Vuex. | 2022-02-04T18:54:10 | 2022-02-04T18:54:10 | {} | MEMBER |
vuejs | core | 1,024,993,517 | 5,333 | LinusBorg | Yeah from that perspective I have to agree. | 2022-01-29T21:53:34 | 2022-01-29T21:53:34 | {} | MEMBER |
vuejs | core | 1,025,440,737 | 4,733 | mika76 | Works here too: [SFC Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBFbXB0eU9yTm90IGZyb20gJy4vRW1wdHkudHMnXG5cbmNvbnN0IHNvbWVWYXIgPSByZWYoJycpXG48L3NjcmlwdD5cblxuPHRlbXBsYXRlPlxuXHQ8ZGl2PjxFbXB0eU9yTm90PnNvbWV0aGluZyBpbnNpZGU8L0VtcHR5T3JOb3Q+PC9kaXY+... | 2022-01-31T07:10:38 | 2022-01-31T07:10:38 | {} | NONE |
vuejs | core | 1,027,797,556 | 5,333 | LinusBorg | In the context of `Comp.vue`, `name` is a non-prop attribute - Comp.vue doesn't have a prop named `name` defined.
So the behavior matches the docs. it's just a subtle breaking change compared to Vue 2 that we so fare haven't documented. | 2022-02-02T10:35:38 | 2022-02-02T10:35:38 | {} | MEMBER |
vuejs | core | 1,031,020,881 | 5,281 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: ab2f0ee9a5db0a5f916ee35d83b2dbbca7d7d94b
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620089ae8396c10008ceac4d](https://app.netlify.com/sites/vuejs-coverage/deploys/620089ae8396c10008ceac4d)
😎 Browse th... | 2022-02-07T02:53:38 | 2022-02-07T02:59:26 | {} | NONE |
vuejs | core | 1,024,879,195 | 4,733 | mika76 | @andrey-hohlov thanks a mill! this seems to work well.
@posva I wonder if there is some way to make this better and more optimised by populating some variable/s on `InternalSlots` when a template is being compiled? | 2022-01-29T09:53:20 | 2022-01-29T09:53:20 | {} | NONE |
vuejs | core | 1,025,005,518 | 5,345 | LinusBorg | Yeah, this can't work, SCSS runs at build-time, but v-bind' value will be inserted at runtime. | 2022-01-29T23:21:01 | 2022-01-29T23:21:01 | {} | MEMBER |
vuejs | core | 1,025,220,009 | 5,333 | lidlanca | `App.vue > Comp.vue > Inner.vue`
there is importance for `name` being attribute in `Comp.vue`
attributes are expected to be applied to the root element,
which is then applied to `<inner>` root element, overriding the explicit prop/attribute
documented https://v3.vuejs.org/guide/component-attrs.html#attribut... | 2022-01-30T20:05:01 | 2022-01-30T20:05:01 | {} | CONTRIBUTOR |
vuejs | core | 1,025,341,474 | 4,733 | andrey-hohlov | @mika76
Can you please show me your code?
I made this sandbox https://codesandbox.io/s/smoosh-leftpad-wh6h1?file=/src/App.vue
And tried to cover all cases and it works everywhere. | 2022-01-31T03:19:52 | 2022-01-31T03:19:52 | {} | NONE |
vuejs | core | 1,026,904,683 | 5,350 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 6bc9e80e19938f9c0c658442ae0824c5b14da811
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f943ec4ca61600087123c1](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f... | 2022-02-01T14:30:10 | 2022-02-01T14:30:49 | {} | NONE |
vuejs | core | 1,028,682,974 | 5,184 | HackyDev | If you have **v-for** and **v-if** on the same element your code may throw this error.
I don't have this error when serving my app locally, only in production. | 2022-02-03T07:32:12 | 2022-02-03T07:32:12 | {} | NONE |
vuejs | core | 1,030,234,743 | 5,359 | kawazoe | Thanks for the `nextTick()` trick. I'll remember that.
> it might be worth exploring wether Vuex should simply be pausing tracking altogether during mutations.
Do you want me to open an issue over in the vuex repo to discuss this? I think it makes a lot of sense, and is also what I expected initially.
> How d... | 2022-02-04T18:16:27 | 2022-02-04T18:16:27 | {} | NONE |
vuejs | core | 1,030,262,056 | 5,359 | LinusBorg | I'll close this here as the behavior is fine as far as Vue core is concerned. | 2022-02-04T18:54:43 | 2022-02-04T18:54:43 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,031,197,711 | 5,365 | LinusBorg | Note we also have ongoing discussions in other issues about how to optimize component name assignment / generation in script setup. (#5218) | 2022-02-07T08:30:40 | 2022-02-07T08:30:40 | {} | MEMBER |
vuejs | core | 1,031,609,748 | 5,365 | Xenoha | Thanks @LinusBorg I submitted this to the Vite team and will keep an eye out on #5218 | 2022-02-07T15:41:43 | 2022-02-07T15:41:43 | {
"+1": 1
} | NONE |
vuejs | core | 1,024,816,095 | 4,733 | andrey-hohlov | My version of helper:
```ts
import {
Comment,
Text,
Slot,
VNode,
} from 'vue';
export function hasSlotContent(slot: Slot|undefined, slotProps = {}): boolean {
if (!slot) return false;
return slot(slotProps).some((vnode: VNode) => {
if (vnode.type === Comment) return false;
if (... | 2022-01-29T02:52:12 | 2022-01-29T02:52:21 | {
"+1": 27,
"hooray": 2
} | NONE |
vuejs | core | 1,024,887,169 | 5,341 | edison1105 | duplicate of #4997 | 2022-01-29T10:46:38 | 2022-01-29T10:46:38 | {} | MEMBER |
vuejs | core | 1,024,918,818 | 5,340 | LinusBorg | Can't test this as I'm on Monterey already, where it works fine.
Anyone on Mojave? | 2022-01-29T14:07:50 | 2022-01-29T14:07:50 | {} | MEMBER |
vuejs | core | 1,024,921,487 | 5,343 | iliubinskii | Thx for the help.
Both fixes worked.
ESLint rule would be great. It should probably replace this ESLint core rule - "object-shorthand". | 2022-01-29T14:24:27 | 2022-01-29T14:24:27 | {} | NONE |
vuejs | core | 1,024,991,201 | 5,345 | lidlanca | ```css
textarea.form-control {
&:disabled {
background-color: map-get($my-color-map, v-bind(selected));
}
}
```
once the `map-get` is processed by the scss preprocessor it is gone, and vue will not be able to inject a css variable like you might have expected
| 2022-01-29T21:38:56 | 2022-01-29T21:38:56 | {} | CONTRIBUTOR |
vuejs | core | 1,025,206,950 | 4,294 | Shinigami92 | We are already on Vue [3.2.29](https://github.com/vuejs/core/releases/tag/v3.2.29) :rofl: | 2022-01-30T18:58:15 | 2022-01-30T18:58:15 | {
"laugh": 12
} | CONTRIBUTOR |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.