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,125,803,364 | 3,034 | yyx990803 | After another look, this is unnecessary. If the component is already loaded when the timers fire:
- `delay` is no longer a dependency of the render function, so changing it won't trigger anything.
- The timeout timer checks for loading state before doing anything, so again it won't cost anything. | 2022-05-13T08:43:31 | 2022-05-13T08:43:31 | {} | MEMBER |
vuejs | core | 1,126,655,062 | 5,887 | liulinboyi | Maybe fixed with this [Pull requests](https://github.com/vuejs/core/pull/5781). | 2022-05-14T06:37:32 | 2022-05-14T06:37:32 | {} | MEMBER |
vuejs | core | 1,030,588,193 | 3,399 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a59d3c5e1086c4b397730c306be36715c2e8ddb9 |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-02-05T09:27:57 | 2022-05-12T07:17:09 | {} | NONE |
vuejs | core | 1,124,880,873 | 5,218 | Mrlilili | > [1693924](https://github.com/vuejs/core/commit/16939241b0f64cefea254b024a9b5a25caea93d9) automatically infers component name based on filename.
When a component contains multiple subcomponents, the directory structure looks like this:
<img width="345" alt="image" src="https://user-images.githubusercontent.com/8... | 2022-05-12T11:32:48 | 2022-05-12T11:32:48 | {
"+1": 9
} | NONE |
vuejs | core | 1,125,431,195 | 4,994 | enjoyyourcopepods | @xgvargas
For me, using `<script setup lang="ts">`, importing `defineProps` solves the "defineProps is not defined" error, e.g.:
```
<script setup lang="ts">
import { defineProps } from "vue";
const props = defineProps({
id: {
required: true,
type: String,
},
});
</script>
```
However, E... | 2022-05-12T21:17:35 | 2022-05-12T21:18:30 | {} | NONE |
vuejs | core | 1,125,772,980 | 5,856 | yyx990803 | Ah I see, didn't notice the check regex is being dynamically generated now. | 2022-05-13T08:08:34 | 2022-05-13T08:08:34 | {} | MEMBER |
vuejs | core | 1,125,843,917 | 5,781 | lingosandi | any news on when this fix would be merged? | 2022-05-13T09:28:28 | 2022-05-13T09:28:28 | {
"+1": 1
} | NONE |
vuejs | core | 1,030,588,192 | 3,399 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-sfc-playground* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | a59d3c5e1086c4b397730c306be36715c2e8ddb9 |
|<span aria-hidden="true">🔍</span> Latest deploy log | http... | 2022-02-05T09:27:57 | 2022-05-12T07:18:29 | {} | NONE |
vuejs | core | 1,125,534,864 | 5,856 | antfu | We built the regex here using the options https://github.com/vuejs/core/blob/af488c26764b97133e785cfc2a7ad708c61ffb67/packages/reactivity-transform/src/reactivityTransform.ts#L59-L62
which also affects how `shouldTransform` works.
I also exposed the top-level APIs to be compatible
https://github.com/vuejs/cor... | 2022-05-13T00:13:58 | 2022-05-13T00:13:58 | {} | MEMBER |
vuejs | core | 1,125,538,901 | 5,350 | yyx990803 | Thanks for the PR and sorry for the late review - I happened to fix these in https://github.com/vuejs/core/commit/54753c340145e4d037b9a619a5e47184ba0f80c9 (`v2-compat` is safer than `pnpm` since the latter is temporary and may be deleted in the future) | 2022-05-13T00:21:39 | 2022-05-13T00:21:39 | {} | MEMBER |
vuejs | core | 1,125,556,108 | 5,445 | yyx990803 | `v-html` with constant value is stringifiable, we just didn't implement the logic for it. See https://github.com/vuejs/core/commit/6283b2ec413b78fe88775d249d3598cdce977b7a | 2022-05-13T00:58:18 | 2022-05-13T00:58:18 | {} | MEMBER |
vuejs | core | 1,124,688,908 | 5,898 | yyx990803 | Thanks for the PR! However, this causes `:style` with array literal values to be no longer hoisted.
A better fix is by detecting this in element transform phase - see 0f00cf43 | 2022-05-12T08:32:19 | 2022-05-12T08:32:19 | {} | MEMBER |
vuejs | core | 1,125,320,126 | 5,905 | posva | Hi, thanks for your interest but Github issues are for bug reports and feature requests only. You can ask questions on the [forum](http://forum.vuejs.org/), the [Discord server](https://vue-land.js.org/) or [StackOverflow](http://stackoverflow.com/tags/vue.js). | 2022-05-12T18:53:43 | 2022-05-12T18:53:43 | {} | MEMBER |
vuejs | core | 1,125,527,078 | 5,825 | yyx990803 | The CI requires strict lockfile when bumping deps, so I did it in 8758da47 | 2022-05-12T23:56:19 | 2022-05-12T23:56:19 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,125,723,093 | 5,832 | iwusong | after https://github.com/vuejs/core/commit/51f3d386de7f5fcec6eb4c1c223ba824be036648
```
<template v-if="true">
<!-- comment-->
<span>aaa</span>
</template>`
```
this template as stable fragment can not have attribute fallthrough ,
but template
```
<template v-if="t... | 2022-05-13T07:04:12 | 2022-05-13T07:20:22 | {} | CONTRIBUTOR |
vuejs | core | 1,125,887,954 | 1,791 | gokalpfirat05 | Any progress on this request? I guess there are tons of applications use this feature at Vue 2 but it's missing in Vue 3 strangely. I don't know if it's not implemented on purpose. @yyx990803 | 2022-05-13T10:19:36 | 2022-05-13T10:19:36 | {} | NONE |
vuejs | core | 1,126,983,451 | 5,918 | liulinboyi | 变通的写法可能是这个
```javascript
<script setup>
import { onMounted, nextTick } from "vue"
onMounted(
nextTick(() => {
console.log("setup onMounted 组件 mounted")
}))
</script>
``` | 2022-05-15T17:30:47 | 2022-05-15T17:30:47 | {} | MEMBER |
vuejs | core | 1,127,145,193 | 5,918 | Hubmeat | 嗯..明白这个特点，但我们的组件库统一使用 Composition api 进行编写，现在需要对所有 vue 实例在 mounted 阶段 hack 或植入一些代码，但植入代码的顺序需要在组件 mounted 以前，为了不影响组件本身的代码，从官方文档的角度出发，mixin 的设计是一个比较好的方式...如果全局 mixin 在设计上无法与 options api 保持一直，那后续官方文档上标记下吧 | 2022-05-16T02:18:06 | 2022-05-16T02:18:06 | {} | NONE |
vuejs | core | 1,124,542,104 | 5,904 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | c35b9cc145bc837f3f7e677752542e7ca4aaabf8 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-05-12T05:23:22 | 2022-05-12T05:25:28 | {} | NONE |
vuejs | core | 1,124,677,608 | 5,727 | cexbrayat | @yyx990803 The PR is rebased and only kept the relevant changes: add linting for test files and ensure that we don't let focused tests slip through. | 2022-05-12T08:20:27 | 2022-05-12T08:20:27 | {} | MEMBER |
vuejs | core | 1,124,750,361 | 5,905 | fxy060608 | uni-app 小程序端不支持使用 slots | 2022-05-12T09:32:49 | 2022-05-12T09:32:49 | {
"+1": 2
} | NONE |
vuejs | core | 1,114,051,300 | 5,766 | DrJume | Thanks! This is also a good alternative.
It would be nice, if the Vue compiler could do this automatically. | 2022-04-30T20:44:50 | 2022-05-12T19:22:11 | {} | CONTRIBUTOR |
vuejs | core | 1,125,526,132 | 5,857 | yyx990803 | They can be hoisted by the compiler and reused across renders. This is intentional.
[See example](https://template-explorer.vuejs.org/#eyJzcmMiOiI8ZGl2PlxuICA8ZGl2IGlkPVwiYVwiIGNsYXNzPVwiaGVsbG9cIj57eyB4IH19PC9kaXY+XG48L2Rpdj4iLCJzc3IiOmZhbHNlLCJvcHRpb25zIjp7ImhvaXN0U3RhdGljIjp0cnVlfX0=) | 2022-05-12T23:53:51 | 2022-05-12T23:54:02 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,125,562,151 | 5,571 | yyx990803 | Warning added in #5573
I don't think we should automatically unmount for the user since this could be unintended and it's better to force the user to
be explicit about their intentions. | 2022-05-13T01:11:22 | 2022-05-13T01:11:22 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,125,596,304 | 5,436 | yyx990803 | I refactored it to only use bracket notation when necessary. This introduces fewer changes and also fewer bytes in generated code. | 2022-05-13T02:29:18 | 2022-05-13T02:29:18 | {} | MEMBER |
vuejs | core | 1,126,650,768 | 5,915 | liulinboyi | You can do the same thing without using `app.ctx`, like this [example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdD5cbmltcG9ydCB7IGdldEN1cnJlbnRJbnN0YW5jZSwgcmVmLCBjb21wdXRlZCB9IGZyb20gXCJ2dWVcIlxuaW1wb3J0IHVzZVZhcmlhbnQgZnJvbSBcIi4vdmFyaWFudC5qc1wiXG4gICAgIFxuZXhwb3J0IGRlZmF1bHQge1xuXHRuYW1lOiBcIkNSYWRpb1wiLFxuXH... | 2022-05-14T06:09:36 | 2022-05-14T06:09:36 | {} | MEMBER |
vuejs | core | 1,126,709,478 | 5,920 | mprinc | I have noticed that [the SFC Playground](https://sfc.vuejs.org/) doesn't handle the code properly so here it is again:
```vue
<script lang="ts" setup>
import { reactive } from "vue";
class TestGeneric<eX extends number> {
protected x!: number;
constructor(protected y: eX) {
this.x = y;
... | 2022-05-14T12:41:24 | 2022-05-14T12:41:24 | {} | NONE |
vuejs | core | 1,126,739,774 | 5,916 | liulinboyi | It's resolved.
https://user-images.githubusercontent.com/41336612/168438831-7479bf75-3df4-4859-9e0d-e60f65fb3d7a.mp4
| 2022-05-14T15:43:24 | 2022-05-14T15:43:24 | {} | MEMBER |
vuejs | core | 1,126,904,321 | 4,537 | SomeoneIsWorking | It would also help me a lot if `const errorMessages` could just be an export.
I want to report compile errors from production build to server so management users can see error logs. | 2022-05-15T10:29:06 | 2022-05-15T10:29:06 | {} | NONE |
vuejs | core | 1,126,956,416 | 5,924 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 86cd1d77869b5fe2f7d60d37c4a774d68b2f1244 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-05-15T14:46:59 | 2022-05-15T14:50:29 | {} | NONE |
vuejs | core | 1,124,543,452 | 5,904 | hchlq | hello @yyx990803 , in the compilation stage, teleport is always parsed not as slot. Teleport will not enter this judgment. Can it be removed. if other compilation environments are different, you can turn off this pr | 2022-05-12T05:26:00 | 2022-05-12T05:27:24 | {} | CONTRIBUTOR |
vuejs | core | 1,124,866,037 | 5,906 | netlify[bot] | ### <span aria-hidden="true">✅</span> Deploy Preview for *vue-next-template-explorer* ready!
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 0810d7e65a3e3e3c2044133f096e3c121847060b |
|<span aria-hidden="true">🔍</span> Latest deploy lo... | 2022-05-12T11:15:39 | 2022-05-12T20:44:04 | {} | NONE |
vuejs | core | 1,125,561,640 | 5,595 | yyx990803 | Closing in favor of #5573
I don't think we should automatically unmount for the user since this could be unintended and it's better to force the user to
be explicit about their intentions. | 2022-05-13T01:10:16 | 2022-05-13T01:10:16 | {} | MEMBER |
vuejs | core | 1,125,779,086 | 4,798 | yyx990803 | This is fine, since these tests may need to change to include await ticks in the future. | 2022-05-13T08:15:54 | 2022-05-13T08:15:54 | {} | MEMBER |
vuejs | core | 1,125,787,399 | 5,672 | yyx990803 | Already fixed in https://github.com/vuejs/core/commit/54753c340145e4d037b9a619a5e47184ba0f80c9 | 2022-05-13T08:25:16 | 2022-05-13T08:25:16 | {} | MEMBER |
vuejs | core | 1,125,805,471 | 3,215 | yyx990803 | This is nice in theory but happens very rarely in real world templates. Not worth it IMO. | 2022-05-13T08:45:58 | 2022-05-13T08:45:58 | {} | MEMBER |
vuejs | core | 1,126,805,334 | 5,915 | LinusBorg | This is an internal API. Using these is strongly discouraged and requires in-depth knowledge of Vue's internals.
In this case, comments in the source code tell us that this is the target for the public component proxy, which doesn't exist duriong prod for script-setup components because these are closed.
In short... | 2022-05-14T20:18:05 | 2022-05-14T20:18:05 | {} | MEMBER |
vuejs | core | 1,127,019,258 | 5,864 | ScottAwesome | @telion2 the work around with key would be adding the `:key` attribute to the component (or teleport, not sure exactly which is most appropriate @posva). If you change the key, Vue will register that when diffing and that will force a re-render
Its not a feature that has to be exclusively used with `v-for` or itera... | 2022-05-15T20:19:26 | 2022-05-15T20:20:08 | {} | NONE |
vuejs | core | 1,174,630,995 | 5,584 | franklx | This bug is very annoying but there's a workaround:
```ts
if (import.meta.env.PROD) { var modelValue = toRef(props, 'modelValue') }
```
it's a ugly but it works, the only thing you need to adapt is the production check (import.meta.env.PROD is a Vite variable). | 2022-07-05T05:30:53 | 2022-07-05T05:30:53 | {} | NONE |
vuejs | core | 1,174,863,331 | 5,584 | ArkoxHub | Isn't it the main purpose of 2 way data binding? The availability to change the value of a property either in parent or child component? | 2022-07-05T09:53:59 | 2022-07-05T09:53:59 | {} | NONE |
vuejs | core | 1,175,092,348 | 2,969 | LinusBorg | See [Playground](https://sfc.vuejs.org/#eNp9UstOwzAQ/JXFl6RSmhRxi9IKxIUjByQuvpRk06SKH7KdVCjyv7N22lIB4mTvzOx4NeuZPWmdTyOyklW2Nr12YNGNesdlL7QyDmYw2GbQYNtLfLKfsn5WxEiULoMOPLRGCUjII+GSS4BaSesgiGD7Z1uarmC7A4kneKXe3mKaGrRqmDASc3CBMMdbL1CNl4YzDjRQFKdXIECyQVPCouzSpOmnJIPEoXXJ6qLz55vP4GGz2cTKr+LxPfmgDjT4YhQQNWBOWHrjxeUiFTZIKZ80... | 2022-07-05T13:56:48 | 2022-07-05T13:56:48 | {} | MEMBER |
vuejs | core | 1,173,648,715 | 6,222 | lisonge | vue@3.2.37 ， vue-router@4.0.16, vite@2.9.13 , @vitejs/plugin-vue@2.3.3
当 router-view 把 keep-alive 包裹的时候，无论 component key 是什么，热更新 router-view 下的根组件 都会报错 ，子组件不会
```txt
TypeError: parentComponent.ctx.deactivate is not a function
``` | 2022-07-04T10:29:43 | 2022-07-06T03:30:31 | {
"+1": 10
} | NONE |
vuejs | core | 1,177,176,127 | 6,228 | Adoew | @LinusBorg Thank you for the help. However in my bigger project I have several errors which look like this : "The requested module '/node_modules/.vite/deps/vue.js?v=46b42f12' does not provide an export named 'default'" when I use dependencies like VueKonva or MDBootstrap. I updated the minimal repro with a simple MDBo... | 2022-07-07T07:09:18 | 2022-07-07T07:09:18 | {} | NONE |
vuejs | core | 1,177,250,186 | 5,525 | liulinboyi | > Hi, thank you for the answer, unfortunately all workarounds posted seem to add values to the ref array, but contrary to what I was able to do in vue 2, in vue 3 I cannot access any method defined on the ref. So let's say I have a `validate()` method on the first ref of the itemRefs array, in vue 2 I was able to call ... | 2022-07-07T08:31:00 | 2022-07-07T08:31:00 | {} | MEMBER |
vuejs | core | 1,174,974,003 | 6,228 | Adoew | @LinusBorg Alright I'm going to look around that. | 2022-07-05T11:56:20 | 2022-07-05T11:56:20 | {} | NONE |
vuejs | core | 1,175,001,129 | 5,584 | jackkitley | This issue flared up recently. Am i doing something wrong in vue? i dont think im modifying props as its bad practise and throws error.
We are still unable to release in prod because of this issue. | 2022-07-05T12:27:24 | 2022-07-05T12:27:24 | {} | NONE |
vuejs | core | 1,175,738,803 | 6,222 | lisonge | @chenhaihong
我之前的描述反了，应该是当 router-view 把 keep-alive 包裹
我用 keep-alive 是为了 `移动端路由 在回退时 恢复状态`
App.vue
```html
<script setup>
</script>
<template>
<router-view v-slot="{ Component }">
<!-- TODO keep-alive 路由回退需要清除缓存 -->
<keep-alive>
<component
... | 2022-07-06T03:29:40 | 2022-07-06T03:35:03 | {} | NONE |
vuejs | core | 1,161,985,389 | 6,155 | KaelWD | This doesn't seem to fully fix my problem, the teleport is still rendered on SSR as
```html
<!--[-->
<!---->
<!--]-->
```
but I can't reproduce it | 2022-06-21T16:30:47 | 2022-07-06T16:03:28 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,177,178,936 | 6,228 | LinusBorg | We should not use this issue ad a general support ticket.
Please use the discord community, forum or stack oberflow.
Hint: sounds like some deps are for Vue2 (which has a default export) | 2022-07-07T07:12:36 | 2022-07-07T07:13:05 | {} | MEMBER |
vuejs | core | 1,177,742,115 | 5,525 | jifka | After I updated with the version that fixed it, I was able to remove the workaround and ref worked properly again. Unless there was another regression, I can attest to the bug having been fixed.
| 2022-07-07T14:53:33 | 2022-07-07T14:53:33 | {} | NONE |
vuejs | core | 1,179,274,957 | 6,242 | skirtles-code | > /cc @skirtles-code What do you think about this in terms of docs, expected behavior and such?
We probably can tighten this up a bit in the docs, but I also feel like there genuinely is a core bug here.
The `ref: search` part in the compiled output is only being included if some very specific criteria are being ... | 2022-07-08T18:52:08 | 2022-07-08T18:52:08 | {
"hooray": 1
} | CONTRIBUTOR |
vuejs | core | 1,179,319,582 | 6,241 | LinusBorg | reopened for now, following discussion in #6242 | 2022-07-08T20:00:08 | 2022-07-08T20:00:08 | {} | MEMBER |
vuejs | core | 1,174,846,581 | 6,228 | LinusBorg | ```js
resolve: {
dedupe: ['vue']
}
```
https://vitejs.dev/config/#resolve-dedupe | 2022-07-05T09:37:35 | 2022-07-05T09:37:47 | {} | MEMBER |
vuejs | core | 1,174,967,644 | 6,228 | LinusBorg | Stupid question: you did restart vite after that change?
I'll have another look when I'm home, but generally these issues are solved reliably by dedupe. maybe the file: dependency path is a problem? not sure. Either way this is a build tooling problem, not a Vue core problem. | 2022-07-05T11:48:14 | 2022-07-05T11:48:14 | {} | MEMBER |
vuejs | core | 1,175,047,540 | 3,015 | LinusBorg | We welcome a PR to the docs. | 2022-07-05T13:15:26 | 2022-07-05T13:15:26 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,175,305,035 | 6,220 | LinusBorg | > I am using the provide/inject inside a component, but in the onMounted hook, outside the setup scope. In the code that I need this, I check whether the users prefers dark mode with a media query and a class in the body tag,
You can still do the injection in setup and then check the result in the hook. No need for... | 2022-07-05T17:12:35 | 2022-07-05T17:13:35 | {} | MEMBER |
vuejs | core | 1,179,542,304 | 6,244 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 489df2e2db55d0847f762b7fb5be43127b9e440a |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-07-09T13:06:44 | 2022-07-09T13:06:44 | {} | NONE |
vuejs | core | 1,174,940,561 | 6,228 | Adoew | @LinusBorg Thank you for your response but I've already tested that in vite.config.js and I didn't work. Is there a particular place tu put this option ? | 2022-07-05T11:15:15 | 2022-07-05T11:15:15 | {} | NONE |
vuejs | core | 1,175,035,556 | 5,767 | MilkoEmanuilov | I've had the same issue with nuxt3 + vite + vuetify.
In my case adding
`server: {
watch: {
usePolling: true,
},
},`
This solved the problem for me but for the solution that is posted did not work.
Is there anyone who have any suggestion? | 2022-07-05T13:03:22 | 2022-07-05T13:03:22 | {} | NONE |
vuejs | core | 1,175,333,845 | 6,192 | KaelWD | This isn't a bug. It might look like it's working but `props.params1` is still a ref and you will get a runtime error if you try to use it as a number. You should put `testBind` and `hookResult` in a `reactive()` to unwrap all the refs before passing it to the component. | 2022-07-05T17:49:34 | 2022-07-05T17:49:34 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,176,160,848 | 5,525 | Sven89 | same problem. Still only works with wrapper | 2022-07-06T12:27:28 | 2022-07-06T12:27:28 | {} | NONE |
vuejs | core | 1,177,039,170 | 5,657 | javastation | The render function is also a workaround, like above reproduction:[sfc.vuejs.org](https://sfc.vuejs.org/#eNp9U01vozAQ/SsjVAkigdlEWmmFmlS7PffW27IHAkOgCzayTT4U8d93sDFJ6bZRFMf2m+c3M2+u3s+uY8cevcR7VLmsOw27lNdtJ6SGKwj+InqusQhBYhlCBQOUUrTgU4w/A19es32D0w2L9bhjb4oAeDaAAsusb4gx5QAKdd8FK7sByAVXGlQlTpZlOz4VlFmjcHWP0OJw+Ooa6WcLgRS... | 2022-07-07T04:06:59 | 2022-07-07T04:06:59 | {} | CONTRIBUTOR |
vuejs | core | 1,177,471,291 | 6,160 | Innei | Hello, this type of definition has any problems? | 2022-07-07T11:39:22 | 2022-07-07T11:39:22 | {} | CONTRIBUTOR |
vuejs | core | 1,177,931,988 | 5,513 | AwesomeDude091 | How likely is it that this will be fixed? | 2022-07-07T16:58:07 | 2022-07-07T16:58:07 | {
"+1": 9,
"laugh": 9
} | NONE |
vuejs | core | 1,174,730,863 | 5,584 | ArkoxHub | To be honest, I still do not understand this problem.
I have form components which are working as expected using <script setup> but the only one is not working in production is the BaseSelect component I created.
This is my code, let's see if you could see what's happening here, at least to understand the issue.
... | 2022-07-05T07:47:58 | 2022-07-05T07:56:29 | {
"+1": 1
} | NONE |
vuejs | core | 1,174,941,666 | 6,214 | shtse8 | It's just an example of using span to demonstrate.
in practice, it will conflict with other classes out scope.
I don't think it's a bad idea to use class with advanced selector as it is the standard of css.
| 2022-07-05T11:16:41 | 2022-07-05T11:16:41 | {} | NONE |
vuejs | core | 1,175,809,462 | 6,229 | LinusBorg | You're injecting this SCSS file into each and every scss file and `<style>` block. that `additionalData` option should only be used to inject scss variables, mixins etc. - so SCSS code that disappears during compilation.
Injecting actual CSS like this will lead to duplication, and will lead to the CSS being scoped -... | 2022-07-06T05:51:12 | 2022-07-06T05:51:37 | {} | MEMBER |
vuejs | core | 1,176,327,346 | 5,657 | BabOuDev | > Hi everyone. I also have this issue only in prod mode. A temporary workaround: remove a `key` attribute from your `v-for`. The error will still be in the console, but it fixes the issue with the rendering
In my case, I don't have any `v-for` in this page...
I do have a `v-if` , but I can't get rid of it...
| 2022-07-06T14:57:20 | 2022-07-06T14:57:20 | {
"+1": 2
} | NONE |
vuejs | core | 1,179,476,021 | 6,219 | chenhaihong | > see #4339
看来我只能砍需求了 !- - | 2022-07-09T04:20:33 | 2022-07-09T04:20:33 | {} | NONE |
vuejs | core | 1,179,644,050 | 6,240 | xfq | > 请教下，在style标签中能使用v-if么？
You can use `v-bind()` with the the conditional operator in CSS. See [this example](https://sfc.vuejs.org/#eNp9kU1uwjAQha8yuIuARGKhLqjSQNsTdNeVN4mZkEBiW7YDqlDu0V2lnrBH6JikArUSu/l58/nN+MRejEkOHbKUZU7a2nhw6DuzFqpujbYeTmCxhB5Kq1uISBoJJZTUynnIj+h0i7AKmqm3Hc6EyvgAIgQlHlvT5B4pA8iKznut4Fk2tdyvBLsAJ... | 2022-07-10T02:50:08 | 2022-07-10T02:50:08 | {} | NONE |
vuejs | core | 1,174,036,435 | 3,842 | dev-itsheng | > > How to fix that, i have same error today. Its complete project, what working 2 years, nad that problems goin only today in 1765 files, wow. How i can ifx that?
>
> i have same problem 2 days ago( are you fix it?
I'm sorry, I haven't had time to deal with this issue because I've been too busy recently, but as ... | 2022-07-04T17:50:48 | 2022-07-04T17:50:48 | {} | CONTRIBUTOR |
vuejs | core | 1,174,548,249 | 4,387 | wuyuweixin | +1 | 2022-07-05T02:55:47 | 2022-07-05T02:55:47 | {} | NONE |
vuejs | core | 1,174,854,765 | 3,116 | LinusBorg | I would argue that this is a limitation that we can't really change.
the array in the ref has all refs in its items unwrapped, so its type is, correctly, `{ isNew: Boolean}[]`.
One can either go the route that posva described, if one wants to preserve the refs, or one can use `reactive` to also unwrap the item ... | 2022-07-05T09:45:53 | 2022-07-05T09:45:53 | {} | MEMBER |
vuejs | core | 1,174,873,283 | 5,584 | Shhu | @preeteshjain There is two issues :
- Different behavior between dev and prod (and thats a huge problem)
- Different behavior between legacy component and setup component | 2022-07-05T10:03:35 | 2022-07-05T10:04:37 | {} | NONE |
vuejs | core | 1,175,761,184 | 6,230 | uCloudCastle | > Vue3的插件是针对实例的，你这个插件所实现的功能更像一个函数做的事情吧 `const app = Plugin(config) ;`
Vue2 的时候用 install 是因为同时有很多 原型链挂载、Mixin 的动作要做。现在 Vue3 的话插件得在实例构造方法被调用后，再对 app 做相关操作，逻辑上差别较大。目前想在一个插件内把 Vue2 和 Vue3 统一兼容起来，实现上没问题，就是看怎么写比较优雅。 | 2022-07-06T04:14:34 | 2022-07-06T04:14:34 | {} | NONE |
vuejs | core | 1,176,925,582 | 5,525 | edison1105 | @Sven89 @vervelover
this because `$setup.itemRefs`(DEV) and `itemRefs.value`(PROD) both are `Proxy` values.
as a [workaround](https://sfc.vuejs.org/#eNp9kctug0AMRX/Fmg0g8dhTEqkf0E2lrjpdpMSEScAzmgdRhfj3ekBJq1TqBl3b3IN9mcWzMeUUUNSica1VxoNDH8xekhqNth5msNjl0OrRBI/HHDS96EAsYYHO6hES9idPkiS1mhwDLsq80dUeDOyiOX3/yOL0bkzTDH... | 2022-07-07T01:15:38 | 2022-07-07T01:25:03 | {} | MEMBER |
vuejs | core | 1,179,096,751 | 6,243 | LinusBorg | This is not related to functional components, and it's expected behavior.
`onUpdated` runs whenever the component went trough another render cycle. But in your code, `HelloWorld`never re-renders, because it's template/render function does not depend on `isOpen`. Since the value is only read on the slot that is being... | 2022-07-08T15:10:50 | 2022-07-08T15:10:50 | {} | MEMBER |
vuejs | core | 1,179,130,413 | 6,242 | adamsol | It's a pity, I hoped I could use `<script setup>` to import child components without having to redeclare them via Options API. The documentation saying:
> `<script setup>` can be used alongside normal `<script>`. A normal `<script>` may be needed in cases where we need to: [...]
certainly doesn't suggest that it'... | 2022-07-08T15:42:55 | 2022-07-08T15:42:55 | {
"+1": 1
} | NONE |
vuejs | core | 1,175,019,976 | 6,214 | shtse8 | Understandable. I am not asking for a change. It just confuse me a bit and hope other can notice this behavior if they are facing the same issue..
In my case, it does happen when I am writing my component to our project using scoped CSS.
it works great when I test. Other team members took it to use as a component i... | 2022-07-05T12:47:36 | 2022-07-05T12:50:46 | {} | NONE |
vuejs | core | 1,175,102,646 | 3,738 | LinusBorg | key is a reserved word, and workarounds have been provided, so I think this can be closed | 2022-07-05T14:05:55 | 2022-07-05T14:05:55 | {} | MEMBER |
vuejs | core | 1,175,109,857 | 4,010 | LinusBorg | I *think* this should be resolved ever since we brought back the old Vue 2 v-for ref behaviour. Am I correct in assuming that, @DV8FromTheWorld ? | 2022-07-05T14:12:25 | 2022-07-05T14:12:25 | {} | MEMBER |
vuejs | core | 1,178,750,578 | 1,791 | PatrikRacsko | > @CyberAP Your idea is very good, and I think I'll try to implement it this way, and maybe I will not have to modify the server-renderer package, if I'm able to call the renderToString of the server renderer function from the render function of this cache wrapper on the default slot content... And on Client Side, the ... | 2022-07-08T09:13:44 | 2022-07-08T09:13:44 | {} | NONE |
vuejs | core | 1,174,705,605 | 5,584 | NielsJorck | I had a similar issue recently, the workaround I went with was creating a computed with a get and set. Passing the get to model and having the set emit the update.
```js
const value = computed({
get() {
return props.modelValue;
},
set(value) {
emit("update:modelValue", value);
},
});
```
``... | 2022-07-05T07:17:56 | 2022-07-05T07:17:56 | {
"+1": 13,
"hooray": 3
} | NONE |
vuejs | core | 1,174,968,624 | 6,228 | Adoew | @LinusBorg Thank you for your time. I will check your hint and I already have posted an issue on Vite's GitHub. | 2022-07-05T11:49:30 | 2022-07-05T11:49:47 | {} | NONE |
vuejs | core | 1,175,100,758 | 3,896 | LinusBorg | I am correct to assume that this request is now outdated? @tangjinzhou
Or are you still waiting on this for your migration?
| 2022-07-05T14:04:14 | 2022-07-05T14:04:14 | {} | MEMBER |
vuejs | core | 1,175,496,041 | 6,220 | LinusBorg | 1. create and provide a ref in `setup`.
2. set the value of the ref whenever you are ready to, i.e. in onMounted().
3. inject and use the ref in children in a way that makes sense, depending on the use case. if its value is set delayed, maybe watch it. or access it in the child's onMounted() ... | 2022-07-05T21:03:07 | 2022-07-05T21:04:58 | {} | MEMBER |
vuejs | core | 1,175,700,036 | 6,230 | snowwolfjay | Vue3的插件是针对实例的，你这个插件所实现的功能更像一个函数做的事情吧
`
const app = Plugin(config) ;
` | 2022-07-06T02:13:19 | 2022-07-06T02:13:19 | {} | NONE |
vuejs | core | 1,176,412,645 | 1,033 | elevatebart | With the lack of traction on this issue, I think we should be OK closing it.
The brittle workaround is to use `patch-package` to remove the JSX global declarations that we do not want.
It works, with the caveat that every time we update vue, we have to re-write the patch.
PNPM has an equivalent `pnpm patch` th... | 2022-07-06T16:10:08 | 2022-07-06T16:10:08 | {} | CONTRIBUTOR |
vuejs | core | 1,176,430,080 | 5,657 | eliasbermudez | Hi. I also have this issue only in prod mode. | 2022-07-06T16:27:53 | 2022-07-06T16:27:53 | {} | NONE |
vuejs | core | 1,176,484,301 | 1,033 | Andarist | IMHO the issue should stay open because it's still valid. As mentioned in the past - I'm willing to work on this if somebody green lights this. I would probably also need to chat with the maintainers before getting to work because we'd need to establish the risks, breakage concerns, potential migration strategies etc | 2022-07-06T17:19:57 | 2022-07-06T17:19:57 | {
"+1": 8
} | NONE |
vuejs | core | 1,177,051,719 | 6,238 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 3e404253a1a01292544a512a6e2f28d29bdf91b0 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-07-07T04:27:58 | 2022-07-07T04:27:58 | {} | NONE |
vuejs | core | 1,179,446,267 | 6,219 | edison1105 | see https://github.com/vuejs/core/pull/4339 | 2022-07-09T00:46:40 | 2022-07-09T00:46:40 | {} | MEMBER |
vuejs | core | 1,173,891,407 | 5,256 | basvanmeurs | Thanks. For vite you can use:
```javascript
plugins: [vue({ template: { compilerOptions: { hoistStatic: false } } })],
``` | 2022-07-04T14:34:59 | 2022-07-04T14:35:12 | {
"+1": 3
} | CONTRIBUTOR |
vuejs | core | 1,174,634,014 | 5,584 | preeteshjain | This approach is even [documented in docs](https://vuejs.org/guide/components/props.html#mutating-object-array-props), but it doesn't work in production:
| 2022-07-05T05:35:21 | 2022-07-05T05:35:21 | {
"confused": 2
} | NONE |
vuejs | core | 1,174,791,179 | 5,584 | preeteshjain | To everyone facing this issue, the only way to fix this problem is to make sure (*double check carefully*) that you are not modifying your props from child component.
We are now modifying the data from the parent only and passing it down as a prop to the child component and it is working in production environment.
... | 2022-07-05T08:47:27 | 2022-07-05T09:02:35 | {
"+1": 2
} | NONE |
vuejs | core | 1,174,969,804 | 6,228 | LinusBorg | Its likely also not a bug in vite, just a question of correct config to make sure one copy of vue is included only. | 2022-07-05T11:50:59 | 2022-07-05T11:50:59 | {} | MEMBER |
vuejs | core | 1,173,709,580 | 5,256 | basvanmeurs | I also ran into this issue while trying to fix a memory leak. It's quite inconvenient while hunting for leaks, as it's something that will get you on the wrong track. Glad to know this now.. | 2022-07-04T11:31:46 | 2022-07-04T11:31:46 | {} | CONTRIBUTOR |
vuejs | core | 1,173,723,516 | 5,256 | meteor199 | You can temporarily circumvent this problem by using the following methods
vue-cli:
```js
chainWebpack: (config) => {
config.module
.rule('vue')
.use('vue-loader')
.tap((options) => {
options.compilerOptions = options.compilerOptions || {};
options.compilerOptions.hois... | 2022-07-04T11:47:18 | 2022-07-04T11:47:18 | {} | NONE |
vuejs | core | 1,174,643,339 | 5,584 | LinusBorg | @preeteshjain Your approach is not mutating an object or array prop, and you approach is still mutating a prop, so that's *not* what the docs recommend. | 2022-07-05T05:51:04 | 2022-07-05T05:51:04 | {} | MEMBER |
vuejs | core | 1,175,482,737 | 6,220 | HipyCas | My main problem is not with the inject but rather with the provide, as I need to provide the value based on media queries, which I can only access through the document in the onMounted hook. | 2022-07-05T20:47:23 | 2022-07-05T20:47:23 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.