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,345,975,849 | 7,323 | LinusBorg | I have trouble understand what supposed problem a UMD build would solve. I also don'T see the connection with the linked issues.
* Both a UMD and a IIFE build (our `vue.global.js`) will add a global variable called `Vue` when directly included via a `<script>` element i.e. from a CDN. Both won't add any other global... | 2022-12-12T06:45:39 | 2022-12-12T06:45:39 | {} | MEMBER |
vuejs | core | 1,346,011,693 | 7,323 | joebnb | the way to solve the issue => close.
* HOW many npmpkgs now support esm bundle?
* if majority not why not choice a sleek upgrade plan to step by step change it
* if vue use esm bundle use '.mjs' extention as a common principle
did UMD format bad as `VAR VUE = XXXX`
im not use it in a commonjs enviro... | 2022-12-12T07:28:13 | 2022-12-12T08:10:33 | {} | NONE |
vuejs | core | 1,336,640,411 | 7,255 | lixiaofa |
> your reproduction is not minimal. Could you provide a demo without any third-party component?
OK. If the third-party component is removed, another error will be reported.
This is the problem on the home page
https://github.com/lixiaofa/nuxt-app.git
It should be the same type of error
@edison1105 @Lin... | 2022-12-05T02:17:22 | 2022-12-05T02:19:57 | {} | NONE |
vuejs | core | 1,338,022,257 | 7,278 | LinusBorg | This seems to be the same report as #7277 just with more info and from another account. Can i close the other one? | 2022-12-05T19:27:11 | 2022-12-05T19:27:11 | {} | MEMBER |
vuejs | core | 1,339,574,514 | 7,280 | zhangzhonghe | Thanks for the report, can you provide a minimal reproduction without dependencies on vue-router and vant? | 2022-12-06T15:43:33 | 2022-12-06T15:43:33 | {} | MEMBER |
vuejs | core | 1,345,576,832 | 7,316 | wsypower | currently, only the return value of the clear method is different from the rules of Map and Set.
```javascript
const readonlyMap = readonly(new Map())
console.log('size',readonlyMap.size) // 0
console.log('get',readonlyMap.get('key')) // undefined
console.log('set',readonlyMap.set('key',2)) // readonlyMap
console... | 2022-12-11T15:01:19 | 2022-12-11T15:01:19 | {} | CONTRIBUTOR |
vuejs | core | 1,345,978,330 | 7,323 | LinusBorg | If you hav an actual bug to report, please do so in an issue with a bug report with a runnable reproduction | 2022-12-12T06:49:48 | 2022-12-12T06:49:48 | {} | MEMBER |
vuejs | core | 1,346,030,104 | 7,323 | joebnb | > If you hav an actual bug to report, please do so in an issue with a bug report with a runnable reproduction
in this issue i talk about 2 issue one is vue umd support,one is vite bundle of pollution global (and this have a link).
if the issue would be fix,just fix.in this case,i can switch to react and i can m... | 2022-12-12T07:49:03 | 2022-12-12T07:49:42 | {} | NONE |
vuejs | core | 1,347,677,306 | 7,331 | kingyue737 | Duplicated #7329 | 2022-12-13T03:01:04 | 2022-12-13T03:01:04 | {} | NONE |
vuejs | core | 1,315,771,527 | 6,390 | jaytonic | > > Hi @zhangzhonghe , Thank you for the debugging! I'm quite new to Vue, so I'm not sure what you mean by "not a bug in vue core" ?
> > Yes, it's a project created with vue cli. But I've the same project with Vite and the same issue occurs(which I initially reported here: [vitejs/vite-plugin-vue#3](https://github.com... | 2022-11-15T19:29:52 | 2022-12-03T06:18:18 | {} | NONE |
vuejs | core | 1,338,217,102 | 7,278 | LinusBorg | @pikax It feels we had this or a very similar issue before ... can you recall?
Should we just re-export that type? Is that really necessary? Those are private so far for a reason, and have worked for many lib authors ... | 2022-12-05T21:44:58 | 2022-12-05T21:44:58 | {} | MEMBER |
vuejs | core | 1,345,446,662 | 7,268 | rudyxu1102 | > I prefer to use `\s\S` instead of `(.|\n)` since some cases have already used it.
>
> https://github.com/vuejs/core/blob/fe77e2bddaa5930ad37a43fe8e6254ddb0f9c2d7/packages/compiler-core/src/transforms/vFor.ts#L311
Thanks | 2022-12-11T03:30:04 | 2022-12-11T03:30:04 | {} | CONTRIBUTOR |
vuejs | core | 1,314,257,857 | 6,390 | jaytonic | Hi @zhangzhonghe ,
Thank you for the debugging! I'm quite new to Vue, so I'm not sure what you mean by "not a bug in vue core" ?
Yes, it's a project created with vue cli. But I've the same project with Vite and the same issue occurs(which I initially reported here: https://github.com/vitejs/vite-plugin-vue/issues/3... | 2022-11-14T19:19:35 | 2022-12-03T06:18:18 | {} | NONE |
vuejs | core | 1,346,792,605 | 7,322 | LinusBorg | This is not by accident. it's a compromise to get better performance when using an iterator.
Your proposed change would introduce a bug where a `map.set()` operation will no longer trigger effects that used i.e. `map.values()` or `map.entries()`. That's because for performance reasons, we use the original non-react... | 2022-12-12T16:03:03 | 2022-12-12T16:03:03 | {} | MEMBER |
vuejs | core | 1,337,326,222 | 7,274 | LinusBorg | Vue component props can't be defined with types alone, they need to be defined at runtime as well.(*)
```ts
const component = defineComponent<HelloWorldProps>((props) => {
const msg = ref(props.msg);
if (!props.msg) {
console.error(
`Can not get props from defineComponent function in tsx file: pro... | 2022-12-05T13:20:07 | 2022-12-05T13:21:44 | {} | MEMBER |
vuejs | core | 1,338,027,617 | 7,278 | Ragura | > This seems to be the same report as #7277 just with more info and from another account. Can i close the other one?
Yes, my apologies, that was a colleague's quick report of the same issue. I was told it would be deleted when I made a more thorough one instead, but since that hasn't happened yet you can safely clos... | 2022-12-05T19:29:39 | 2022-12-05T19:29:39 | {} | NONE |
vuejs | core | 1,340,060,348 | 7,283 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 245df3f7785c1624406f95291d9b89268a9f3ca9 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-06T21:55:06 | 2022-12-06T21:55:06 | {} | NONE |
vuejs | core | 1,340,309,622 | 1,033 | datalater | > Using this thread to remind that because of those jsx types clobbering the global namespace (on vue 2.7.13 at least), React and Vue cannot be used on the same project which is a real problem.
That's exactly what happened to me as well. As below, React and Vue have different global namespace JSX types. And that's w... | 2022-12-07T03:03:52 | 2022-12-07T03:03:52 | {} | NONE |
vuejs | core | 1,344,488,164 | 7,280 | Yhspehy | In your App.vue, it will preserve one Home component instances.
So it will mounted twice when you navigate to page1, because the preserved instances will mount Page1 component one time, and the `<component :is="Component" v-if="!$route.meta.keepAlive" :key="$route.fullPath" />` will mount another time. | 2022-12-09T16:08:32 | 2022-12-09T16:08:32 | {} | NONE |
vuejs | core | 1,345,552,889 | 7,319 | edison1105 | @posva
Actuality, the instance in the regular watch callback is also incorrect and is unmounted. It can execute because we don't determine if the instance is unmounted [like watchEffect does](https://github.com/vuejs/core/blob/11bd8db768f1f3587ed7e820357369551c081c60/packages/runtime-core/src/apiWatch.ts#L234).
``... | 2022-12-11T13:19:31 | 2022-12-11T13:19:31 | {} | MEMBER |
vuejs | core | 1,346,038,662 | 7,323 | LinusBorg | > screen shot or logs not enough
Yes. Not enough. Good day to you to. | 2022-12-12T07:59:33 | 2022-12-12T07:59:33 | {} | MEMBER |
vuejs | core | 1,347,921,819 | 7,330 | LinusBorg | Good call, will do. | 2022-12-13T08:28:43 | 2022-12-13T08:28:43 | {} | MEMBER |
vuejs | core | 1,314,760,578 | 6,390 | zhangzhonghe | > Hi @zhangzhonghe , Thank you for the debugging! I'm quite new to Vue, so I'm not sure what you mean by "not a bug in vue core" ?
>
> Yes, it's a project created with vue cli. But I've the same project with Vite and the same issue occurs(which I initially reported here: [vitejs/vite-plugin-vue#3](https://github.com... | 2022-11-15T04:35:17 | 2022-12-03T06:18:18 | {} | MEMBER |
vuejs | core | 1,340,307,485 | 7,284 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 60290d8ae7f7da71354d0288dfc3f4f97a1bb123 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-07T03:00:23 | 2022-12-07T03:00:23 | {} | NONE |
vuejs | core | 1,340,581,169 | 7,278 | pikax | This is odd error, because those types are internals, only `Ref` should be exposed on the types declaration file, the `RawSymbol` should be only used in the library itself. | 2022-12-07T08:30:33 | 2022-12-07T08:30:33 | {} | MEMBER |
vuejs | core | 1,342,175,480 | 7,291 | LinusBorg | ### Cause
The click handler on the child gets a new inline function on every parent re-render, causing every child to update:
```js
const _item = (_openBlock(), _createBlock(Item, {
key: i,
isSpread: i.age,
onClick: $event => (ageUp(index)) // <-- this causes the re-re... | 2022-12-08T07:05:28 | 2022-12-08T07:05:28 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,345,842,153 | 7,234 | zhangzhonghe | Duplicate of #7155 | 2022-12-12T04:09:41 | 2022-12-12T04:09:41 | {} | MEMBER |
vuejs | core | 1,346,037,870 | 7,323 | joebnb | ok ok,we need a runnable reproductions to debug it,screen shot or logs not enough,leave it and have a good day. | 2022-12-12T07:58:38 | 2022-12-12T07:58:38 | {} | NONE |
vuejs | core | 1,346,135,139 | 7,324 | richex-cn | > Usage of `getCurrentInstance` is strongly discouraged in application code. Do **NOT** use it as an escape hatch to get the equivalent of `this` in Composition API.
https://github.com/vuejs/docs/blob/10ed910a8c7f6cad665aa74e7c0e921107b34868/src/api/composition-api.md?plain=1#L216-L223 | 2022-12-12T09:12:13 | 2022-12-12T09:18:10 | {} | NONE |
vuejs | core | 1,346,185,877 | 7,327 | tsyMzhc | 生活这么不如意 | 2022-12-12T09:52:46 | 2022-12-12T09:52:46 | {} | NONE |
vuejs | core | 1,338,215,356 | 7,277 | LinusBorg | duplicate of #7278 | 2022-12-05T21:43:10 | 2022-12-05T21:43:10 | {} | MEMBER |
vuejs | core | 1,340,300,359 | 5,996 | dedisuryadi | Just run into this issue today on `"vue": "^3.0.0"`
```
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'length')
at flushPreFlushCbs (runtime-core.esm-bundler.js?f781:323:1)
at flushJobs (runtime-core.esm-bundler.js?f781:371:1)
flushPreFlushCbs @ runtime-core.esm-bundler.js?f781... | 2022-12-07T02:47:19 | 2022-12-07T02:47:19 | {} | NONE |
vuejs | core | 1,342,130,642 | 7,291 | torder-jkj | ERROR: type should be string, got "\r\nhttps://user-images.githubusercontent.com/103406163/206367443-5aef6f7f-1d80-44de-82ab-34359dadc327.mov\r\n\r\n" | 2022-12-08T06:25:28 | 2022-12-08T06:25:28 | {
"+1": 1
} | NONE |
vuejs | core | 1,342,858,061 | 4,314 | gnuletik | @yashwanth2714 Vue typescript config seems different than the one on your repo. You can ignore TS errors by adding the following line at the top of `localApiCustomElement.ts`:
```
// @ts-nocheck
``` | 2022-12-08T14:55:48 | 2022-12-08T14:55:48 | {
"+1": 2
} | NONE |
vuejs | core | 1,344,263,280 | 7,308 | LinusBorg | I'll summarize a few things, some of which you might be aware, just for clarity:
There are two levels of compat:
1. compiler
2. runtime
Consequently, there are 2 places that require compat config:
1. compiler config (you set that to 3)
2. runtime (you did not set that at all, meaning it defaults to 2)
... | 2022-12-09T12:41:18 | 2022-12-09T12:55:48 | {} | MEMBER |
vuejs | core | 1,346,035,299 | 7,323 | LinusBorg | Bug reports require runnable reproductions. even us core contributors do follow that rule when we open issues ourselves. We ask the same from other people reporting problems. Runnable reproductions are required for us to be able to understand a problem clearly.
Now a few points, trying to explain my problems of unde... | 2022-12-12T07:55:27 | 2022-12-12T07:58:57 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,347,656,344 | 1,556 | DrPep | Thanks for a clear and readable RFC. Problem solved! | 2022-12-13T02:23:29 | 2022-12-13T02:23:29 | {} | NONE |
vuejs | core | 1,347,732,853 | 7,323 | yyx990803 | https://github.com/vitejs/vite/issues/10822 的问题是你没搞明白 Vite 的输出产物格式。vite build 的默认输出是 esm,需要用 `<script type="module">` 引入。你没有用 Vite 生成的 HTML 而是自己去掉了文件 hash 引入,但用的是普通的 `<script>` 而不是 esm script,所以才导致全局污染。这不是 bug,而是用法不对。
另一方面,这跟 Vue 是否提供 UMD 根本是不相干的问题,Vue 的 global build 就是专门用于非 ESM 的普通 `<script>` 场景的,暴露全局变量就是这个 build 的... | 2022-12-13T04:28:03 | 2022-12-13T04:42:46 | {
"+1": 7
} | MEMBER |
vuejs | core | 1,348,840,701 | 7,338 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 0a98c6921b6997ed7f587ef8ffdff4e22ea177ad |
|<span aria-hidden="true">🔍</span> Latest deploy l... | 2022-12-13T15:42:07 | 2022-12-13T15:54:13 | {} | NONE |
vuejs | core | 1,349,040,276 | 7,339 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8dc7722fbc76245953db4e0be2f0a16cd65c8ddb |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-12-13T16:47:49 | 2022-12-13T16:52:46 | {} | NONE |
vuejs | core | 1,352,691,602 | 7,346 | SimmeNilsson | > as workaround
>
> ```js
> // Move this to the front of top level await
> defineExpose({
> callMe,
> });
>
> // Make async
> await new Promise((resolve) => setTimeout(resolve, 1));
> ```
That works, but would require all teams to make changes and remember the order.
Is there no way to work around i... | 2022-12-15T08:05:55 | 2022-12-15T08:05:55 | {} | NONE |
vuejs | core | 1,352,492,233 | 7,346 | edison1105 | duplicate of https://github.com/vuejs/core/issues/4930
In fact, version 3.2.45 will also have problems with production. | 2022-12-15T02:56:45 | 2022-12-15T09:07:00 | {} | MEMBER |
vuejs | core | 1,354,367,044 | 7,344 | edison1105 | @baiwusanyu-c
great work! but not working with [this scenario](https://deploy-preview-7344--vue-sfc-playground.netlify.app/#__DEV__eNqlkU1u2zAQha8y5cYJYEqLBijgOka76AmaTQFuZGlks6FIYjiSIxi+e4aS4hjJMloIePPzvtHTWf2OsRh6VBu1Zeyiqxh3xgNs9z1z8PCrdrZ+fjQqHcPp6Wj9AR7h21UYtXsKh4ND4Cy35by2WFC5m15ZGW9YEA5jIAYOYrkPzSgGuSvTTJVPlu2... | 2022-12-16T08:16:10 | 2022-12-16T08:16:10 | {} | MEMBER |
vuejs | core | 1,348,360,564 | 5,666 | rudyxu1102 | Just use lower-case `element` instead of `Element`.

| 2022-12-13T11:53:38 | 2022-12-13T11:53:38 | {
"-1": 4
} | CONTRIBUTOR |
vuejs | core | 1,356,278,131 | 7,356 | abrbabey | > I don't think you should package the vue code into your library because it will overwrite some of the global variables that vue needs to use.
@zhangzhonghe, thank you for the reply. It is true that removing `vue` from the library package will avoid this conflict, but that also greatly weakens my real use case for ... | 2022-12-17T14:19:24 | 2022-12-17T14:19:24 | {} | NONE |
vuejs | core | 1,356,182,079 | 7,358 | LinusBorg | That setting only matters to injections in Options API, so you don't have to type `this.someInjection value`. As there is no `this` in composition API, unwrapping the injection itself doesn't make sense.
And yes, `props` is not unwrapped, that's by design. Unwrapping usually happens in the parent template, leaving t... | 2022-12-17T11:03:50 | 2022-12-18T21:48:34 | {} | MEMBER |
vuejs | core | 1,349,063,194 | 7,312 | theoephraim | @moushicheng - Thanks for adding this. Im not surprised... It seems to have to do with not finding an actual parent node to attach the inline style to. | 2022-12-13T16:58:17 | 2022-12-13T16:58:17 | {
"+1": 1
} | NONE |
vuejs | core | 1,351,840,392 | 7,343 | LinusBorg | > > @talhameer could you please remove/work around the dependency on stripe?
>
> I've removed the extra code around Stripe. Please check [here](https://stackblitz.com/edit/vitejs-vite-48q3zs?file=src%2Fviews%2FCartView.vue)
The demo is still unusable because I'd need your secret stripe API key to make it run.
... | 2022-12-14T17:43:56 | 2022-12-14T17:44:37 | {} | MEMBER |
vuejs | core | 1,355,305,245 | 7,359 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 02d0bd5bb3e0e853e4de762e778c2bc7b52c2d87 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-16T17:49:36 | 2022-12-16T17:49:36 | {} | NONE |
vuejs | core | 1,356,460,257 | 7,329 | sxzz | https://github.com/remorses/esbuild-plugins/pull/19
This PR is also blocking... | 2022-12-17T20:36:14 | 2022-12-17T20:36:14 | {
"eyes": 3
} | MEMBER |
vuejs | core | 1,356,881,993 | 7,358 | sigtm | Thanks, appreciate the clarification @LinusBorg 👍
Bit of a bummer since it would have been a really elegant way for components to provide default prop values for their descendants, but nothing I can't work around. | 2022-12-18T21:41:06 | 2022-12-18T21:41:06 | {} | NONE |
vuejs | core | 1,357,355,966 | 7,369 | frankykubo | @LinusBorg thanks for responding. Anyway, is there any official recommended method to inject variables to css from Vue SFC Javascript part? | 2022-12-19T09:31:41 | 2022-12-19T09:31:41 | {} | NONE |
vuejs | core | 1,358,493,787 | 7,356 | abrbabey | The recommended change in `vite.config.ts` worked to prevent my library from interfering with the consuming app's HMR operations. This makes my library build output closer to a production-like artifact, as I intended.
Thank you @zhangzhonghe, I am closing this issue! | 2022-12-19T22:27:37 | 2022-12-19T22:27:37 | {
"+1": 1
} | NONE |
vuejs | core | 1,350,189,612 | 7,312 | edison1105 | This is because Teleport is not patched in the fast path.
Maybe we should re-consider the solution in https://github.com/vuejs/core/pull/4609
| 2022-12-14T00:50:41 | 2022-12-14T00:50:41 | {} | MEMBER |
vuejs | core | 1,352,683,489 | 7,351 | LinusBorg | this would rather be because of the transition than because of the router.
I'll move this issue to vue core. | 2022-12-15T07:57:34 | 2022-12-15T07:57:34 | {} | MEMBER |
vuejs | core | 1,352,704,541 | 7,351 | posva | Duplicate of https://github.com/vuejs/core/issues/4830 | 2022-12-15T08:18:04 | 2022-12-15T08:18:04 | {} | MEMBER |
vuejs | core | 1,354,381,871 | 7,333 | jason-chang | @sxzz Thanks for the suggestion, but if I use typescript before version 4.9, my decision should be in the right direction, right? | 2022-12-16T08:27:36 | 2022-12-16T08:27:36 | {} | NONE |
vuejs | core | 1,356,459,103 | 7,329 | ice1000 | https://github.com/rollup/plugins/pull/1373 is merged :) | 2022-12-17T20:27:09 | 2022-12-17T20:27:09 | {} | NONE |
vuejs | core | 1,357,234,828 | 4,339 | qq229338869 |
> 应该大部分都是做多tab单页应用的来提这个feature.
>
> @liweijian1 在页面组件外面包个壳,像下面这样子,能完全可控操作keep-alive缓存, 而且不需要额外的内部规范,比如,页面组件必须强制加上组件名,配合在meta里配置上页面组件名称,
>
> ```
> <template>
> <router-view v-slot="{ Component, route }">
> <keep-alive :include="include">
> <component :is="wrap(route.fullPath, Component)" :key=... | 2022-12-19T08:01:26 | 2022-12-19T08:16:52 | {} | NONE |
vuejs | core | 1,349,080,261 | 6,908 | gngrchrl | Hi! Would it be possible to merge this PR? I currently have the same issue and this would really help me out as it completely fixes the issue. | 2022-12-13T17:05:55 | 2022-12-13T17:05:55 | {} | NONE |
vuejs | core | 1,352,990,715 | 7,346 | LinusBorg | @edison1105 #4951 was too outdated, author just closed it. I'll reopen this issue here until we have a fresh fix. Also, since it works in 3.2.44, it must be something that changed in the meantime, right? | 2022-12-15T12:29:05 | 2022-12-15T12:29:05 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,353,456,914 | 4,294 | dakt | This is quite bad...beside generic components and untyped slots, probably the biggest drawback of Vue3 | 2022-12-15T17:29:20 | 2022-12-15T17:29:20 | {
"+1": 25,
"-1": 4,
"confused": 2
} | NONE |
vuejs | core | 1,354,954,815 | 5,952 | fabienbergerat | Is there any update on the status of this issue? | 2022-12-16T14:37:14 | 2022-12-16T14:37:14 | {
"+1": 7,
"eyes": 9
} | NONE |
vuejs | core | 1,355,172,029 | 5,303 | emahuni | https://www.npmjs.com/package/vue-deepunref | 2022-12-16T16:26:42 | 2022-12-16T16:26:42 | {
"-1": 3
} | NONE |
vuejs | core | 1,356,316,407 | 4,294 | AlertNull | > This is quite bad...beside generic components and untyped slots, probably the biggest drawback of Vue3
Talk Is Cheap, Show Me Your Code Please. | 2022-12-17T15:55:23 | 2022-12-17T15:55:23 | {
"-1": 21,
"laugh": 11
} | NONE |
vuejs | core | 1,357,870,661 | 7,334 | LinusBorg | Thanks | 2022-12-19T15:49:08 | 2022-12-19T15:49:08 | {} | MEMBER |
vuejs | core | 1,357,891,185 | 7,370 | sj7112 | 

| 2022-12-19T16:04:47 | 2022-12-19T16:04:47 | {} | NONE |
vuejs | core | 1,358,424,049 | 7,376 | LinusBorg | You can manipulate the DOM as long as you don't mess with the parts Vue controls.
In your example, the "mustache" part is a DOM text node inside of a span. That text node is controlled by Vue, its content is being updated by Vue with the mustache code's value on each re-render.
But after you did replace this te... | 2022-12-19T21:43:00 | 2022-12-19T21:45:51 | {} | MEMBER |
vuejs | core | 1,351,709,290 | 6,548 | JeremCafeyn | Hi @edison1105 ,
Thanks for your work
Do you know if this one will be merge soon? | 2022-12-14T16:13:39 | 2022-12-14T16:13:50 | {} | NONE |
vuejs | core | 1,357,129,500 | 7,356 | zhangzhonghe | > Are there any mechanisms for protecting the global variables you mention from interference? Perhaps a configuration or transformation to be applied to Vue in the library code or its build process?
You can change the ```vite.config.ts``` to this:
```ts
export default defineConfig(({ mode }) => {
return {
... | 2022-12-19T05:45:26 | 2022-12-19T05:45:26 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,357,900,928 | 7,370 | LinusBorg | This is not a runnable reproduction. this is a screenshot and a code snippet. | 2022-12-19T16:11:39 | 2022-12-19T16:11:39 | {} | MEMBER |
vuejs | core | 1,351,609,504 | 7,343 | rudyxu1102 | Discussion https://github.com/vuejs/core/discussions/7332 | 2022-12-14T15:16:34 | 2022-12-14T15:16:34 | {} | CONTRIBUTOR |
vuejs | core | 1,356,268,719 | 7,333 | sxzz | @jason-chang Not really necessary.
```ts
defineComponent({
setup(props, { expose }) {
const exposed: Type = { foo: 1 }
expose(exposed)
},
})
``` | 2022-12-17T13:44:24 | 2022-12-17T13:44:24 | {} | MEMBER |
vuejs | core | 1,357,850,791 | 7,370 | sj7112 | Actually I created two imports:
<script lang="ts" setup>
import '@/utils/string'; // some extension such as String.property.xxx functions
import '@/utils/object'; // some extension such as Object.property.xxx functions
......
Checkout my debug picture. It's weird! Object.property.getTuple is the first functi... | 2022-12-19T15:34:07 | 2022-12-19T15:35:38 | {} | NONE |
vuejs | core | 1,357,872,590 | 7,370 | LinusBorg | I can't follow. Please, provide runnable code. Otherwise I will have to close this issue. | 2022-12-19T15:50:45 | 2022-12-19T15:51:07 | {} | MEMBER |
vuejs | core | 1,349,196,612 | 7,340 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8162b6aad08d99c5f04cfe8113391194688d2e23 |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-12-13T17:30:13 | 2022-12-13T17:43:24 | {} | NONE |
vuejs | core | 1,351,791,803 | 7,347 | LinusBorg | * The change to `title` makes the component re-render
* During the re-render, a fresh inline array is being created in the template and passed to `OtherComponent`, which makes `OtherComponent` re-render, because the attribute's content changed (it's a new array).
Expected Behavior.
Solution: extract the array into... | 2022-12-14T17:12:35 | 2022-12-14T17:13:15 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,352,488,614 | 7,346 | edison1105 | as workaround
```javascript
// Move this to the front of top level await
defineExpose({
callMe,
});
// Make async
await new Promise((resolve) => setTimeout(resolve, 1));
``` | 2022-12-15T02:49:46 | 2022-12-15T02:49:46 | {} | MEMBER |
vuejs | core | 1,354,766,550 | 7,344 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vuejs-coverage* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | f4a605c95dc31b29399aacef4b7bcdf24c7272a9 |
|<span aria-hidden="true">🔍</span> Latest deploy log | https:/... | 2022-12-16T13:28:36 | 2022-12-16T13:28:36 | {} | NONE |
vuejs | core | 1,355,409,675 | 7,258 | vanillajonathan | Firefox 108 now supports import maps. :+1:
https://www.mozilla.org/en-US/firefox/108.0/releasenotes/ | 2022-12-16T18:45:05 | 2022-12-16T18:45:05 | {} | NONE |
vuejs | core | 1,356,450,340 | 7,364 | skirtles-code | Could you maybe explain how your proposed solution compares to the existing PRs for those two issues?
* #7341
* #7344 | 2022-12-17T20:12:17 | 2022-12-17T20:12:17 | {} | CONTRIBUTOR |
vuejs | core | 1,356,678,894 | 7,364 | tinyfind |
>discard use css attribute `data-v-owner` that cancel `updateCssVars` limit browser environment only, so #7341 get fixed
modify `updateCssVars` make cssVar can work in multilevel nesting teleport
https://github.com/vuejs/core/blob/fe77e2bddaa5930ad37a43fe8e6254ddb0f9c2d7/packages/runtime-core/src/components/Telepo... | 2022-12-18T05:37:46 | 2022-12-18T05:37:46 | {} | NONE |
vuejs | core | 1,357,770,860 | 7,372 | LinusBorg | You should however be able to use this library's components *without* registering the plugin by using the unplugin-vue-components plugin (which also works with webpack). Check their docs, open an issue there. | 2022-12-19T14:41:38 | 2022-12-19T14:41:38 | {} | MEMBER |
vuejs | core | 1,357,847,104 | 7,334 | hongguang-alt | > please provide a runnable reproduction. you already created a playground, why would you not link it here?
please, the link is
https://sfc.vuejs.org/#eNqtk8uO2zAMRX+F1SYtENuz6cZ1AyT9hS610cRMq4EtCRLtJgjy76Ue8eQx6KqAYYvS5aEsXp3F1rl6nlC0ogt7rx1tpNGjs57ghx3dFg7ejrCqmxRF6epOsLsT7IpAGjwmSY8HNQ0EZ2kA9qywBg2FFs4Zvy6QyzoKekX... | 2022-12-19T15:31:03 | 2022-12-19T15:31:03 | {} | NONE |
vuejs | core | 1,349,269,013 | 7,333 | sxzz | You can use `satisfies` operator with TypeScript 4.9 instead, to constraint exposed type. Also, please create an issue before PR.
For example:
```ts
defineComponent({
setup(props, { expose }) {
expose({
foo: 1,
} satisfies { foo: boolean })
},
})
``` | 2022-12-13T17:48:34 | 2022-12-13T17:48:54 | {} | MEMBER |
vuejs | core | 1,351,363,063 | 6,908 | LinusBorg | All vnodes should have a `type` property, it's a mandatory field. So I'm worried that simply "working around" a case where a vnode has an undefined type, might mask the true source of the issue - especially as we still don't have a proper reproduction for us to debug, even though the issue came up multiple times so far... | 2022-12-14T13:34:39 | 2022-12-14T13:35:20 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,353,740,856 | 4,874 | infinite-system | > Just for the record what you can quite easily do for now is use a wrapper component like this:
>
> ```js
> import { h, reactive } from 'vue'
> import App from './App.vue'
>
> const props = reactive({ whatever })
>
> const app = createApp({
> render: () => h(App, props)
> })
>
> app.mount('#app')
> ... | 2022-12-15T21:38:22 | 2022-12-15T21:40:02 | {} | NONE |
vuejs | core | 1,354,245,395 | 5,584 | ErosBurastero | >
It is possible to change emit() for const emit = defineEmits() ?? because with emit() doesn't work properly, thanks | 2022-12-16T05:32:50 | 2022-12-16T05:32:50 | {} | NONE |
vuejs | core | 1,357,744,430 | 7,370 | LinusBorg | Please provide a runnable reproduction. if the SFC playground does not work for you, provide a github repository.
I can't really follow your instructions, sorry. | 2022-12-19T14:19:34 | 2022-12-19T14:20:08 | {
"+1": 1
} | MEMBER |
vuejs | core | 1,348,841,303 | 7,338 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-sfc-playground* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 0a98c6921b6997ed7f587ef8ffdff4e22ea177ad |
|<span aria-hidden="true">🔍</span> Latest deploy log | htt... | 2022-12-13T15:42:19 | 2022-12-13T15:53:57 | {} | NONE |
vuejs | core | 1,351,284,795 | 7,344 | moushicheng | [see here](https://deploy-preview-7344--vue-sfc-playground.netlify.app/#eNqlVM1um0AQfpXpXpxIXjg0UiXXsdpDr+2huVTigmGwt4Xd1e4ARZbfvbNAMYlRoiQXpJmd72e+1XISX62NmhrFRmwJK1umhLtEA2z3NZHR8CUrVfbnPhH+aNqHo9IHuIcPU5GI3YM5HEoECuU2HmAjhYt3/SdUfSdXDWRl6j0TEv4lhoc+gDZALtVekTJ63ZdYojWOelzMwAvLZXJEL/BCI1Uxtz1JAfz69vOR2vcfj9Tmetv4iVii... | 2022-12-14T12:41:17 | 2022-12-14T12:41:17 | {} | CONTRIBUTOR |
vuejs | core | 1,353,031,949 | 7,346 | edison1105 | > it must be something that changed in the meantime, right?
@LinusBorg
Yes, and is not working all the time in reproduction mode. | 2022-12-15T13:03:57 | 2022-12-15T13:03:57 | {} | MEMBER |
vuejs | core | 1,353,618,204 | 5,679 | funkyvisions | @LinusBorg I've create issue https://github.com/vuejs/core/issues/7355 | 2022-12-15T19:42:18 | 2022-12-15T19:42:18 | {} | NONE |
vuejs | core | 1,354,765,890 | 7,355 | funkyvisions | Oh. So this sounds a little more serious then. My app is very dependent on being able to go over the max limit and relying on it purging things properly. | 2022-12-16T13:28:08 | 2022-12-16T13:28:08 | {} | NONE |
vuejs | core | 1,354,935,663 | 7,357 | SpringHgui | eidit `vite.config.ts` below to solve `process is not defined`

anoter error encountered
... | 2022-12-16T14:26:44 | 2022-12-16T14:26:44 | {} | NONE |
vuejs | core | 1,355,384,809 | 7,258 | skirtles-code | I've opened a PR to make using Pinia with the SFC Playground a little less troublesome: #7311. See the example link at the top of the PR. | 2022-12-16T18:29:29 | 2022-12-16T18:29:29 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,349,041,017 | 7,339 | netlify[bot] | ### <span aria-hidden="true">❌</span> Deploy Preview for *vue-next-template-explorer* failed.
| Name | Link |
|---------------------------------|------------------------|
|<span aria-hidden="true">🔨</span> Latest commit | 8dc7722fbc76245953db4e0be2f0a16cd65c8ddb |
|<span aria-hidden="true">🔍</span> Latest deploy l... | 2022-12-13T16:48:01 | 2022-12-13T16:52:37 | {} | NONE |
vuejs | core | 1,347,730,531 | 7,312 | moushicheng | It's not just the problem of transition components,
see here,[playground](https://sfc.vuejs.org/#eNp9UttuwjAM/RUvL4AEzTsLaNN+gce80NZAWZtEiQtDiH+f3QvqNmmt1ObE9rGP7bt6DyG7tKjWyqQiVoEgIbVha13VBB8J7hDxAA84RN/AjF1nT9OHb8Jwn2kBwsRmAOsK7xJB4WsfYSMU81nEcrYYLenkr7tT5Y6DlWKLi1frjO7L4AIMYRPqPSGfwZLJWyLv4K2oq+JzY9WU4uUJrNru/PFYI5... | 2022-12-13T04:23:22 | 2022-12-14T02:42:46 | {} | CONTRIBUTOR |
vuejs | core | 1,350,687,959 | 6,253 | leifmarcus | Any update here? This is a huge thing if this is not solved, as this cannot be worked around.
Even when deactivating the `TRANSITION_CLASSES` in the `compatConfig`, this error will still be there. | 2022-12-14T09:11:18 | 2022-12-14T09:11:18 | {} | NONE |
vuejs | core | 1,351,834,322 | 7,343 | talhameer | > @talhameer could you please remove/work around the dependency on stripe?
I've removed the extra code around Stripe.
Please check [here](https://stackblitz.com/edit/vitejs-vite-48q3zs?file=src%2Fviews%2FCartView.vue) | 2022-12-14T17:39:05 | 2022-12-14T17:41:15 | {} | NONE |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.