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,027,024,437 | 5,347 | posva | Indeed, it works in a vite project too. Closing in favor of https://github.com/vuejs/vue-loader/issues/1915 then | 2022-02-01T16:20:17 | 2022-02-01T16:20:17 | {} | MEMBER |
vuejs | core | 1,028,122,040 | 5,354 | theoephraim | moving to vue-issue-helper repo - https://github.com/vuejs/vue-issue-helper/issues/73 | 2022-02-02T16:30:45 | 2022-02-02T16:42:41 | {} | NONE |
vuejs | core | 1,028,697,433 | 5,333 | yyx990803 | I would say this is the more "correct" and expected behavior compared to Vue 2. `name` is not declared by `Comp` so it gets passed on to `CompChild`, and because it's from higher-up, it has higher priority.
Also considering that changing this would technically constitute a breaking change in Vue 3, I think this is a... | 2022-02-03T07:56:31 | 2022-02-03T07:56:31 | {} | MEMBER |
vuejs | core | 1,028,701,867 | 5,335 | yyx990803 | Checking for potential readonly properties requires calling `Object.getOwnPropertyDescriptor` on every Proxy trap call, which I suspect is going to be too expensive even in dev mode.
In general, you should avoid making complex 3rd party objects reactive - i.e. don't return it from `data()` - there's no point in doin... | 2022-02-03T08:03:02 | 2022-02-03T08:03:02 | {} | MEMBER |
vuejs | core | 1,032,072,731 | 5,370 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 938dbb97bb82b7a2468d9dd177b2b413a3193476
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/6201b4dea4b6ce0008d28a6b](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-08T00:10:11 | 2022-02-08T00:10:51 | {} | NONE |
vuejs | core | 1,025,644,917 | 4,609 | hzm18 | same problem | 2022-01-31T11:33:06 | 2022-01-31T11:33:06 | {} | NONE |
vuejs | core | 1,026,934,462 | 5,347 | posva | In general, having all TS strict options activated (through `strict: true` without deactivating any) is a good idea. Some types require this to avoid loosing up some types and making them `any` | 2022-02-01T14:59:48 | 2022-02-01T14:59:48 | {} | MEMBER |
vuejs | core | 1,028,601,440 | 5,353 | edison1105 | @lidlanca
should be
```javascript
if(rawSlot._n) {
// already normalized
return rawSlot
}
``` | 2022-02-03T04:51:00 | 2022-02-03T04:52:28 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,029,858,389 | 5,361 | LinusBorg | You do all of the changes before the component event mounts, so there's no "update" happening.
If you did call `change1` and `change2` *after* mounted, though, the view would still update as as `change1()` does a reactive change.
Not sure what you are trying to demonstrate? | 2022-02-04T10:49:11 | 2022-02-04T10:49:44 | {} | MEMBER |
vuejs | core | 1,025,210,436 | 4,294 | LinusBorg | > For me this problem should get all the importance for the Vue community, because it completelly defeats the purpose of using Vue at all (with Typescript, of course). The framework was rewritten with Typescript and a simple Prop cannot be typed with actual useful types (and interfaces) that everyone use!! It's insane!... | 2022-01-30T19:15:34 | 2022-01-30T19:18:12 | {
"+1": 16,
"-1": 1,
"heart": 8
} | MEMBER |
vuejs | core | 1,029,259,563 | 5,353 | lidlanca | @edison1105
nice, so withCtx actually adds the `_n` marking, I missed that.
https://github.com/vuejs/core/blob/9c304bfe7942a20264235865b4bb5f6e53fdee0d/packages/runtime-core/src/componentRenderContext.ts#L105-L106
| 2022-02-03T18:06:13 | 2022-02-03T18:06:13 | {} | CONTRIBUTOR |
vuejs | core | 1,032,170,956 | 5,369 | NoahStahl | Thanks. Perhaps it would be helpful to use such as the error message in this case, rather than the current encouragement to file an issue on what is "likely a Vue internals bug". Likewise, the docs example showing the use of top level await could easily include a corresponding example `template` below that shows a val... | 2022-02-08T03:17:40 | 2022-02-08T03:17:40 | {} | NONE |
vuejs | core | 1,024,858,757 | 5,342 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 507b5739085030641598436998f44fc2ae92aee1
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61f4f0e34605cf0008fb7821](https://app.netlify.com/sites/vue-sfc-playground/deploys/61f4f0e34605cf0008fb7821)
... | 2022-01-29T07:46:49 | 2022-01-29T07:48:59 | {} | NONE |
vuejs | core | 1,025,932,473 | 2,027 | bglaz | > Are there other known causes of this "Avoid app logic" warning? I am migrating from Vue 2 to 3, and some routes show this warning in the console hundreds, if not thousands of times on one page.
Saving a component and triggering HMR also causes this warning to show up multiple times. | 2022-01-31T15:57:26 | 2022-01-31T15:57:26 | {} | NONE |
vuejs | core | 1,030,378,628 | 5,360 | lidlanca | issues are related and revolve around the same base bug
#4718 expects that there will be no warning, since the fragment is keyed, and it doesn't try to key the fragment nodes.
#5360 based on the same warning, try to address it, by keying individual fragment nodes manually, but fail due to syntax error
Howeve... | 2022-02-04T21:52:55 | 2022-02-04T21:52:55 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,030,635,920 | 5,362 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: ea98cfeccded9e1ec1402254b6f2aeec2e7fc3cb
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61fe8ba4b489e70008fb0ba2](https://app.netlify.com/sites/vuejs-coverage/deploys/61fe8ba4b489e70008fb0ba2)
😎 Browse th... | 2022-02-05T14:37:29 | 2022-02-05T14:44:24 | {} | NONE |
vuejs | core | 1,031,157,409 | 5,365 | LinusBorg | This is an issue with vite's plugin, which only adds this property if the dev-server is running:
https://github.com/vitejs/vite/blob/5306234aad7e7432fb55c6033a63c6cf74493c3f/packages/plugin-vue/src/main.ts?_pjax=%23js-repo-pjax-container%2C%20div%5Bitemtype%3D%22http%3A%2F%2Fschema.org%2FSoftwareSourceCode%22%5D%20m... | 2022-02-07T07:35:48 | 2022-02-07T07:35:48 | {} | MEMBER |
vuejs | core | 1,024,831,777 | 4,950 | yuwu9145 | This should be a bug and issue should be reopened | 2022-01-29T04:34:28 | 2022-01-29T04:34:28 | {} | CONTRIBUTOR |
vuejs | core | 1,024,966,127 | 5,343 | posva | Can you open an issue on vuejs eslint repo if there isn't one yet? | 2022-01-29T18:48:32 | 2022-01-29T18:48:32 | {} | MEMBER |
vuejs | core | 1,025,204,563 | 4,294 | aislanmaia | For me this problem should get all the importance for the Vue community, because it completelly defeats the purpose of using Vue at all (with Typescript, of course). The framework was rewritten with Typescript and a simple Prop cannot be typed with actual useful types (and interfaces) that everyone use!! It's insane!!!... | 2022-01-30T18:45:26 | 2022-01-30T18:45:26 | {
"+1": 43,
"laugh": 6
} | NONE |
vuejs | core | 1,026,904,673 | 5,350 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 6bc9e80e19938f9c0c658442ae0824c5b14da811
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61f943ec13a0840008ccff02](https://app.netlify.com/sites/vue-sfc-playground/deploys/61f943ec13a0840008ccff02)
... | 2022-02-01T14:30:09 | 2022-02-01T14:32:21 | {} | NONE |
vuejs | core | 1,026,904,715 | 5,350 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 6bc9e80e19938f9c0c658442ae0824c5b14da811
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61f943ec3ba2e60007e842fd](https://app.netlify.com/sites/vuejs-coverage/deploys/61f943ec3ba2e60007e842fd)
😎 Browse th... | 2022-02-01T14:30:11 | 2022-02-01T14:36:01 | {} | NONE |
vuejs | core | 1,029,371,862 | 5,358 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 604420b475f4e35f1a595b66c383f2728d7fad28
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61fc3abf3ba4b60008251b80](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f... | 2022-02-03T20:27:48 | 2022-02-03T20:28:36 | {} | NONE |
vuejs | core | 1,029,371,857 | 5,358 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 604420b475f4e35f1a595b66c383f2728d7fad28
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/61fc3abf6e92c60008a17b5f](https://app.netlify.com/sites/vue-sfc-playground/deploys/61fc3abf6e92c60008a17b5f)
... | 2022-02-03T20:27:48 | 2022-02-03T20:30:18 | {} | NONE |
vuejs | core | 1,029,371,859 | 5,358 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 604420b475f4e35f1a595b66c383f2728d7fad28
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/61fc3abf778ebb00071b3f3a](https://app.netlify.com/sites/vuejs-coverage/deploys/61fc3abf778ebb00071b3f3a)
😎 Browse th... | 2022-02-03T20:27:48 | 2022-02-03T20:33:27 | {} | NONE |
vuejs | core | 1,029,820,065 | 5,360 | LinusBorg | Duplicate of #4718 | 2022-02-04T09:58:30 | 2022-02-04T09:58:30 | {} | MEMBER |
vuejs | core | 1,030,744,888 | 1,600 | ewdieckman | For those using vue-cli, the correct syntax for vue.config.js is as follows:
```javascript
chainWebpack: config => {
config.module
.rule('vue')
.use('vue-loader')
.tap(options => {
// https://github.com/vuejs/vue-next/pull/1600
option... | 2022-02-06T03:39:14 | 2022-02-06T03:39:14 | {
"+1": 4,
"heart": 2
} | NONE |
vuejs | core | 1,032,260,434 | 5,369 | LinusBorg | We have an open issue for that, agreed | 2022-02-08T06:36:40 | 2022-02-08T06:36:40 | {} | MEMBER |
vuejs | core | 1,028,372,026 | 5,339 | benneq | @LinusBorg Thanks for the explanation. This sounded to me like `<input type="radio">` should have the same issue. But it works perfectly well for radio buttons and disabled JavaScript. Or is this something different?
```
<script setup lang="ts">
const options = ['a', 'b', 'c'];
const value = 'b';
</script>
<t... | 2022-02-02T21:25:14 | 2022-02-02T21:25:14 | {} | NONE |
vuejs | core | 1,029,062,938 | 5,356 | posva | Volar already extracts the slot typing. Duplicate of https://github.com/vuejs/core/issues/3102 (Generic components) | 2022-02-03T14:46:17 | 2022-02-03T14:46:17 | {} | MEMBER |
vuejs | core | 1,029,085,188 | 3,102 | iliubinskii | If you only need generic props then you can use this tutorial:
https://logaretm.com/blog/generically-typed-vue-components/
It worked for me
BUT:
It does not help in creating generic slots.
If anyone has solution to create generic component with both generic props and generic slots, please, share your ideas. | 2022-02-03T15:07:54 | 2022-02-03T15:07:54 | {
"+1": 1
} | NONE |
vuejs | core | 1,030,635,924 | 5,362 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: ea98cfeccded9e1ec1402254b6f2aeec2e7fc3cb
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/61fe8ba4c7e8b20007350341](https://app.netlify.com/sites/vue-next-template-explorer/deploys/61f... | 2022-02-05T14:37:29 | 2022-02-05T14:38:21 | {} | NONE |
vuejs | core | 1,030,783,451 | 3,870 | m4heshd | This is such an essential feature. Would've been amazing if it was provided by the framework. It's very odd that [Vue 3 SSR documentation](https://v3.vuejs.org/guide/ssr/introduction.html#ssr-vs-prerendering) points to `prerender-spa-plugin` when it clearly doesn't work. | 2022-02-06T09:18:04 | 2022-02-06T09:26:51 | {} | NONE |
vuejs | core | 1,024,899,322 | 5,343 | LinusBorg | I think this is about the [same TS limitation we have with props validator functions](https://staging.vuejs.org/guide/typescript/options-api.html#caveats): they either need to be arrow functions or have `this` typed to `undefined` explicitly. Both of these work fine:
```ts
emits: {
// arrow function
event: ... | 2022-01-29T12:06:28 | 2022-01-29T13:26:27 | {} | MEMBER |
vuejs | core | 1,025,434,040 | 4,733 | mika76 | @andrey-hohlov it's very strange...
In code sandbox my code look a bit like this (using a render function): https://codesandbox.io/s/old-water-skt34?file=/src/App.vue
But it works here in codesandbox. I then take the same function, copy it to my vite/vue 3 app and it does not work. I first thought it was because ... | 2022-01-31T06:59:26 | 2022-01-31T06:59:26 | {} | NONE |
vuejs | core | 1,031,020,888 | 5,281 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: ab2f0ee9a5db0a5f916ee35d83b2dbbca7d7d94b
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/620089aed1cc5e00081a26cd](https://app.netlify.com/sites/vue-sfc-playground/deploys/620089aed1cc5e00081a26cd)
... | 2022-02-07T02:53:39 | 2022-02-07T02:56:49 | {} | NONE |
vuejs | core | 1,028,224,109 | 5,352 | AaronBeaudoin | ## More Debugging Info
Here is more specifically what is happening with this bug. When the `hydrateChildren` function is run inside of the `hydrateFragment` function on line 4283, it expects to get the fragment's end anchor back from `hydrateChildren`, but in this case it get's `null` instead.
The reason for this... | 2022-02-02T18:20:03 | 2022-02-02T19:01:45 | {} | NONE |
vuejs | core | 1,031,889,385 | 5,369 | LinusBorg | Please read the yellow warning box in the docs section that you linked to.
Await is only supported in components that are nested in a Suspense component. | 2022-02-07T20:28:13 | 2022-02-07T20:28:13 | {} | MEMBER |
vuejs | core | 1,035,962,924 | 5,402 | LinusBorg | Oh, I wasn't think as a far back as pre-official 1.0 😄
Vue's focus has changed a lot since then, so my position doesn't change. | 2022-02-11T08:07:25 | 2022-02-11T08:07:25 | {} | MEMBER |
vuejs | core | 1,036,152,473 | 5,389 | pikax | I don't think we should have another type, probably it would make more sense to use [ComponentCustomProperties](https://github.com/vuejs/core/blob/9c304bfe7942a20264235865b4bb5f6e53fdee0d/packages/runtime-core/src/componentPublicInstance.ts#L71) and can you also add some dts tests please? | 2022-02-11T12:12:48 | 2022-02-11T12:12:48 | {} | MEMBER |
vuejs | core | 1,036,228,002 | 5,389 | nandi95 | > I think we can still have ComponentCustomProperties, but make the type a bit more lenient and supporting `Ref<T> | T`
I personally prefer minimising ambiguity.
Maybe what we could do is have ComponentCustomProperties declared as:
```ts
export type ComponentCustomProperties = { [K in keyof GlobalProperties]: G... | 2022-02-11T13:44:33 | 2022-02-11T13:44:33 | {} | CONTRIBUTOR |
vuejs | core | 1,037,061,837 | 5,413 | yyx990803 | https://vuejs.org/api/composition-api-setup.html#exposing-public-properties | 2022-02-12T08:23:24 | 2022-02-12T08:23:24 | {
"+1": 2,
"hooray": 1
} | MEMBER |
vuejs | core | 1,038,894,204 | 5,422 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 15d112adf1bc457d41e77e144586ca58dc6cbc03
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/620a2a304d76830008f3c88f](https://app.netlify.com/sites/vue-sfc-playground/deploys/620a2a304d76830008f3c88f)
... | 2022-02-14T10:08:54 | 2022-02-14T10:11:16 | {} | NONE |
vuejs | core | 1,038,894,194 | 5,422 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 15d112adf1bc457d41e77e144586ca58dc6cbc03
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620a2a3075cad10007d23a5d](https://app.netlify.com/sites/vuejs-coverage/deploys/620a2a3075cad10007d23a5d)
😎 Browse th... | 2022-02-14T10:08:53 | 2022-02-14T10:14:39 | {} | NONE |
vuejs | core | 1,032,107,354 | 5,218 | sxzz | I'm trying to switch Element Plus to `script-setup` syntax, but this problem is blocking us. As a 3rd party component, we should add a prefix to component name, so we should add `name` property for every Vue SFC. If I use `script-setup`, there's two `script` tags at the same time. I think it's too ugly and seems to be ... | 2022-02-08T01:07:59 | 2022-02-14T17:06:15 | {
"+1": 16
} | MEMBER |
vuejs | core | 1,041,176,146 | 5,401 | 3zzy | @LinusBorg If that's the case then the Vue doesn't get a [perfect 100% as mentioned in the docs](https://vuejs.org/guide/extras/web-components.html#using-custom-elements-in-vue) so the docs need to be updated to reflect that. | 2022-02-16T07:00:38 | 2022-02-16T07:01:21 | {
"+1": 9
} | NONE |
vuejs | core | 1,035,501,375 | 5,399 | LinusBorg | You are using v-model on the component, but not on the native select *inside* that component.
You emit `$event.target.value` which will always be a string.
if you want the select to handle non-string values, you need to use v-model on the select.
You can do so By using a computed with a getter and setter to ha... | 2022-02-10T20:50:34 | 2022-02-11T07:55:17 | {
"heart": 1
} | MEMBER |
vuejs | core | 1,036,164,240 | 5,389 | nandi95 | Only issue is while on ComponentCustomProperties a ref is available as the key, on the GlobalProperties it will be key.value | 2022-02-11T12:29:05 | 2022-02-11T12:29:05 | {} | CONTRIBUTOR |
vuejs | core | 1,036,621,484 | 5,407 | lidlanca | 
> Runtime directive used on component with non-element root node. The directives will not function as intended. | 2022-02-11T21:04:49 | 2022-02-11T21:04:49 | {} | CONTRIBUTOR |
vuejs | core | 1,037,263,098 | 3,798 | Zclhlmgqzc | see #5416 | 2022-02-12T15:45:18 | 2022-02-12T15:45:18 | {} | CONTRIBUTOR |
vuejs | core | 1,039,911,124 | 5,419 | LinusBorg | > From the DOM element analysis of the third animation,'teleport' is deleted directly, while other elements are not affected.
The teleport can't be aware that you mounted its content into a transition context. | 2022-02-15T06:38:57 | 2022-02-15T06:38:57 | {} | MEMBER |
vuejs | core | 1,040,241,833 | 5,432 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 1bd5fc0fd8c9703681d9e5e2752d016eafac3def
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620ba3543acc3d0009d2a576](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-15T12:58:01 | 2022-02-15T12:58:48 | {} | NONE |
vuejs | core | 1,041,033,860 | 5,436 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 2389d8cccd9827083230832f0834081329aedeb5
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/620c636c3835ec0007b6fbf5](https://app.netlify.com/sites/vue-sfc-playground/deploys/620c636c3835ec0007b6fbf5)
... | 2022-02-16T02:37:37 | 2022-02-16T02:40:15 | {} | NONE |
vuejs | core | 1,041,086,828 | 3,334 | flozero | Hello thank you a lot for the work here.
It will sounds like a dumb questions...
So with this PR we can't build anymore universal component library with vue demi right for vue2 and vue3 ?
Because unfortunately there is still a lot of companies that keep using vue2 and not already started the transition that w... | 2022-02-16T04:15:58 | 2022-02-16T04:15:58 | {
"+1": 2
} | NONE |
vuejs | core | 1,036,239,456 | 5,389 | nandi95 | > // they will both be `1` when used on the component
The keyword is `on the component` which is correct, but like the docblock suggests the globalProperties are also available on getCurrentInstance() | 2022-02-11T13:57:11 | 2022-02-11T13:57:24 | {} | CONTRIBUTOR |
vuejs | core | 1,033,670,219 | 5,389 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: b39a042b5a8bc2f2614c8d756ce3d1d8bb4ee97f
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/62068f9f20eefc0008404b96](https://app.netlify.com/sites/vue-sfc-playground/deploys/62068f9f20eefc0008404b96)
... | 2022-02-09T11:41:13 | 2022-02-11T16:34:47 | {} | NONE |
vuejs | core | 1,033,347,822 | 5,382 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 25a5bb6d33ac479f66dfe305f614f1db495c87a3
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620a26db08af070007690660](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-09T04:52:39 | 2022-02-14T09:56:09 | {} | NONE |
vuejs | core | 1,038,894,213 | 5,422 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 15d112adf1bc457d41e77e144586ca58dc6cbc03
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620a2a3049e50f00086669f4](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-14T10:08:54 | 2022-02-14T10:09:37 | {} | NONE |
vuejs | core | 1,036,027,033 | 1,033 | PuruVJ | Having same issue, but because I have a react and vue package in `packages` folder in a pnpm workspace, and it's by design
Svelte typings don't break though
<img width="236" alt="CleanShot 2022-02-11 at 15 10 35@2x" src="https://user-images.githubusercontent.com/47742487/153569037-fdf48587-ebc3-4d5e-9b92-e5a86f1e8c... | 2022-02-11T09:42:06 | 2022-02-11T10:48:29 | {} | NONE |
vuejs | core | 1,033,670,230 | 5,389 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: b39a042b5a8bc2f2614c8d756ce3d1d8bb4ee97f
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/62068f9f71415900071681e0](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-09T11:41:13 | 2022-02-11T16:33:26 | {} | NONE |
vuejs | core | 1,036,629,587 | 5,411 | tobiasBora | Thanks. It's a bit strange to force using a `script`, isn't it possible to let `<script setup>` automatically handle this case? | 2022-02-11T21:15:41 | 2022-02-11T21:15:41 | {} | NONE |
vuejs | core | 1,037,162,322 | 5,318 | LinusBorg | [We do identity checks](https://github.com/vuejs/core/blob/cea82cffa3963d6d7f82f490ba0dba50a1d202db/packages/shared/src/looseEqual.ts?_pjax=%23js-repo-pjax-container%2C%20div%5Bitemtype%3D%22http%3A%2F%2Fschema.org%2FSoftwareSourceCode%22%5D%20main%2C%20%5Bdata-pjax-container%5D#L13), but they fail as a raw original is... | 2022-02-12T11:32:40 | 2022-02-12T11:35:14 | {
"+1": 2,
"eyes": 1
} | MEMBER |
vuejs | core | 1,037,256,271 | 5,414 | magicseth | Thanks Evan, that workaround works.
This caused me hours of head scratching in particular because my code still work with "yarn dev" and only broke when I tried "yarn build"
Is this something that tooling could take care of with automatically adding "type" to the import statement or a reference to this possib... | 2022-02-12T15:23:28 | 2022-02-12T15:23:28 | {} | NONE |
vuejs | core | 1,037,420,028 | 5,415 | M1CK431 | Thanks a lot @LinusBorg for time and research.
Next time I will provide the error message even if it means nothing for me :hand_over_mouth:
Also, congrats for the nice and quick catch you did! :clap: :tophat: | 2022-02-12T19:37:17 | 2022-02-12T19:37:17 | {} | NONE |
vuejs | core | 1,038,196,668 | 5,035 | PurpleTape | Hello!
This does not cover the case when ref values passed to defineExpose(). And as result u can't use same interface for expose and access.
`MyComponent.d.ts`
```ts
import type { Ref } from 'vue';
export interface IMyComponent {
something: Ref<string>;
}
```
`MyComponent.vue`
```vue
<script s... | 2022-02-13T15:31:46 | 2022-02-13T15:31:46 | {} | NONE |
vuejs | core | 1,038,763,873 | 5,382 | Justineo | It's actually declared as:
https://github.com/vuejs/core/blob/1574edd490bd5cc0a213bc9f48ff41a1dc43ab22/package.json#L46-L48 | 2022-02-14T07:55:48 | 2022-02-14T07:55:48 | {} | MEMBER |
vuejs | core | 1,036,088,584 | 5,402 | csuhta | `v-pre` doesn't satisfy the use-case here, we still want to _use_ Vue features to enhance components, just not `{{interpolation}}` specifically
I understand if you don't think this request is widely useful or worth maintaining, regardless | 2022-02-11T11:01:53 | 2022-02-11T11:23:14 | {} | NONE |
vuejs | core | 1,036,615,853 | 5,411 | lidlanca | ```html
<script>
import CompA from "./CompA.vue"
export default {
components: {
CompA
}
}
</script>
<script setup>
...
</script>
| 2022-02-11T20:56:29 | 2022-02-11T20:56:29 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 1,037,074,013 | 4,294 | Miofly | `setup` 语法糖中的这种语法什么时候可以支持
```ts
interface Props extends IconProps {
value?: string;
showAction?: boolean;
animation?: boolean;
actionStyle?: object;
actionText?: string;
}
``` | 2022-02-12T08:56:43 | 2022-02-12T08:56:43 | {
"+1": 1
} | NONE |
vuejs | core | 1,037,958,442 | 5,415 | cexbrayat | @M1CK431 Thanks for the report. That's my bad, I did not think of that edge case. I was going to fix it, but @lidlanca was faster and already opened a PR with a potential fix. I'll let the rest of the team approve and merge it, and then we'll be able to release a fixed version. | 2022-02-13T09:27:03 | 2022-02-13T09:27:03 | {} | MEMBER |
vuejs | core | 1,038,896,151 | 5,421 | caozhong1996 | Your example is wrong, I can not understand it... | 2022-02-14T10:10:36 | 2022-02-14T10:10:36 | {} | CONTRIBUTOR |
vuejs | core | 1,039,475,549 | 5,398 | LinusBorg | For a quick fix just make sure to use the 2.* Version range | 2022-02-14T19:34:38 | 2022-02-14T19:34:38 | {} | MEMBER |
vuejs | core | 1,040,825,617 | 5,434 | tony19 | Duplicate of [vuejs/vue-cli#6994](https://github.com/vuejs/vue-cli/issues/6994)
Workaround is to add this config:
```js
// vue.config.js
module.exports = {
configureWebpack: {
devtool: 'eval-cheap-source-map',
},
}
```
[demo](https://stackblitz.com/edit/github-dsqfi1-zmewgq?file=vue.config.js) | 2022-02-15T21:44:53 | 2022-02-15T21:54:00 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 1,036,042,457 | 5,363 | caozhong1996 | @LinusBorg here we go
![impicture_20220211_180029](https://... | 2022-02-11T10:02:49 | 2022-02-11T10:02:49 | {
"+1": 6
} | CONTRIBUTOR |
vuejs | core | 1,036,977,750 | 4,704 | danranVm | @yyx990803 hi, please review. | 2022-02-12T03:46:48 | 2022-02-12T03:46:48 | {} | NONE |
vuejs | core | 1,032,468,154 | 4,294 | sadeghbarati | third party usecase typescript - using volar
`nested` namespace and `interface` not working in SFC `<script lang="ts">` and `<script setup lang="ts">`
```vue
<script setup lang="ts">
import DataTables from 'datatables.net'
interface Props {
options?: DataTables.Settings; //error: 'DataTables' only refers ... | 2022-02-08T10:46:45 | 2022-02-13T08:55:51 | {
"+1": 1
} | NONE |
vuejs | core | 1,039,916,783 | 5,429 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 95bdd4ad91c407b49d16df60ff5bbd52751963b4
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/620b4cfd14cfe70008fdfc01](https://app.netlify.com/sites/vue-sfc-playground/deploys/620b4cfd14cfe70008fdfc01)
... | 2022-02-15T06:49:38 | 2022-02-15T06:51:59 | {} | NONE |
vuejs | core | 1,040,614,604 | 5,420 | posva | Duplicate of https://github.com/vuejs/core/issues/5167
As you found, use the `:deep()` pseudo selector instead: `.scoped :deep(.global)` | 2022-02-15T18:14:12 | 2022-02-15T18:14:12 | {
"+1": 2
} | MEMBER |
vuejs | core | 1,037,819,618 | 5,410 | yyx990803 | We’ve never had any real use case for a forced sync flush. What we need is a use case, not just “because React has it”. | 2022-02-13T06:08:40 | 2022-02-13T06:09:59 | {
"+1": 3
} | MEMBER |
vuejs | core | 1,038,126,036 | 5,415 | M1CK431 | @cexbrayat: you're welcome, no problem, I simply fix `vue` dependency to `3.2.30` in my `package.json` waiting for the fix, not a big deal :wink: In fact, I'm proud to see that this report is useful for the community (and it was not possible without you :joy:).
@lidlanca: thanks for the so quick fix, can't wait for ... | 2022-02-13T13:41:22 | 2022-02-13T13:41:22 | {} | NONE |
vuejs | core | 1,038,797,593 | 5,420 | Niputi | related issues https://github.com/vitejs/vite/issues/6862 | 2022-02-14T08:32:34 | 2022-02-14T08:32:34 | {
"+1": 1
} | NONE |
vuejs | core | 1,039,825,663 | 5,428 | netlify[bot] | ✔️ Deploy Preview for *vue-sfc-playground* ready!
🔨 Explore the source changes: 4cb587f7a8e91a3e57adc836e125e16a9a88b786
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-sfc-playground/deploys/620b23308317900007328b73](https://app.netlify.com/sites/vue-sfc-playground/deploys/620b23308317900007328b73)
... | 2022-02-15T03:51:17 | 2022-02-15T03:53:44 | {} | NONE |
vuejs | core | 1,035,959,526 | 5,402 | csuhta | > > I believe old versions of Vue used to have an option like this somewhere
>
> Nope.
Is that not what `interpolate: true` used to control here? https://012.vuejs.org/api/global-api.html
| 2022-02-11T08:01:12 | 2022-02-11T08:05:07 | {} | NONE |
vuejs | core | 1,037,063,829 | 5,414 | yyx990803 | Vue checks whether an import is used in the template to determine whether it should be treated as a type-only import - but this leads to false positives when they are used as types in template expressions.
The workaround is using explicit `import type { ... } from './...'`. | 2022-02-12T08:29:04 | 2022-02-12T08:29:04 | {} | MEMBER |
vuejs | core | 1,037,304,795 | 5,415 | M1CK431 | Is there enough information to reopen this issue @LinusBorg ? :pray: :pleading_face: | 2022-02-12T16:53:11 | 2022-02-12T16:53:11 | {} | NONE |
vuejs | core | 1,037,562,756 | 5,417 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 834965a0b829138ec7a9ec08a8002b74e8e21a1a
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620980be4d0f24000730dc2f](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-12T23:13:29 | 2022-02-13T22:06:39 | {} | NONE |
vuejs | core | 1,039,787,150 | 5,419 | bw-CN | From the DOM element analysis of the first animation, the sub elements or sub components are removed from the DOM only when the animation of the source context is completed.
From the DOM element analysis of the third animation,'teleport' is deleted directly, while other elements are not affected.
The 'teleport'is... | 2022-02-15T02:32:54 | 2022-02-15T02:32:54 | {} | NONE |
vuejs | core | 1,039,825,678 | 5,428 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 4cb587f7a8e91a3e57adc836e125e16a9a88b786
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/620b2330f08d64000731c8a7](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-15T03:51:18 | 2022-02-15T03:52:06 | {} | NONE |
vuejs | core | 1,039,825,667 | 5,428 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 4cb587f7a8e91a3e57adc836e125e16a9a88b786
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620b233003c12400080b325e](https://app.netlify.com/sites/vuejs-coverage/deploys/620b233003c12400080b325e)
😎 Browse th... | 2022-02-15T03:51:17 | 2022-02-15T03:56:52 | {} | NONE |
vuejs | core | 1,041,195,663 | 4,344 | 941477276 | > > Hi,
> > I am building a library with vue3 and vite, when i use the library if i use slot i got same issue, i tried the solutions in this thread but i can not fix the issue.
> > error: `Uncaught TypeError: Cannot read properties of null (reading 'isCE')`
> > My vite config.js:
> > ```
> > import vue from '@vite... | 2022-02-16T07:32:18 | 2022-02-16T07:32:18 | {} | NONE |
vuejs | core | 1,036,075,427 | 5,402 | posva | Use `v-pre`: https://vuejs.org/api/built-in-directives.html#v-pre | 2022-02-11T10:46:32 | 2022-02-11T10:46:32 | {} | MEMBER |
vuejs | core | 1,036,310,870 | 5,389 | nandi95 | After a call we clarified that the `globalProperties` can be in fact set to `ComponentCustomProperties` it's just JetBrains vue plugin has an issue with unwrapping the types.
https://youtrack.jetbrains.com/issue/WI-65351 | 2022-02-11T15:07:20 | 2022-02-11T15:07:20 | {} | CONTRIBUTOR |
vuejs | core | 1,036,336,847 | 5,409 | netlify[bot] | ❌ Deploy Preview for *vuejs-coverage* failed.
🔨 Explore the source changes: 5cc64ebb00efbff81f83308dd123f4d8c460c7d5
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620681889b56b200084c0bba](https://app.netlify.com/sites/vuejs-coverage/deploys/620681889b56b200084c0bba)
| 2022-02-11T15:32:30 | 2022-02-11T15:35:11 | {} | NONE |
vuejs | core | 1,036,977,305 | 4,704 | netlify[bot] | ✔️ Deploy Preview for *vue-next-template-explorer* ready!
🔨 Explore the source changes: 86bd05702e13c2e88fd3f5831e4b4b88fe19e5e7
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vue-next-template-explorer/deploys/62072d25b1a8090008b3ff84](https://app.netlify.com/sites/vue-next-template-explorer/deploys/620... | 2022-02-12T03:44:43 | 2022-02-12T03:45:51 | {} | NONE |
vuejs | core | 1,033,347,798 | 5,382 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 25a5bb6d33ac479f66dfe305f614f1db495c87a3
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620a26db03a1610008a5f01f](https://app.netlify.com/sites/vuejs-coverage/deploys/620a26db03a1610008a5f01f)
😎 Browse th... | 2022-02-09T04:52:35 | 2022-02-14T10:01:09 | {} | NONE |
vuejs | core | 1,038,936,810 | 5,398 | laurentva | Thanks Linus! That makes sense, I'm maintaining an Electron application from 4 years ago that unfortunately uses the latest Vue release and this broke for all our customers last week, but now I know for sure we'll need to ship an update to everyone. | 2022-02-14T10:50:38 | 2022-02-14T10:50:38 | {} | NONE |
vuejs | core | 1,036,014,544 | 2,179 | Nisgrak | Any updates? | 2022-02-11T09:25:40 | 2022-02-11T09:25:40 | {
"rocket": 7
} | NONE |
vuejs | core | 1,033,670,228 | 5,389 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: b39a042b5a8bc2f2614c8d756ce3d1d8bb4ee97f
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/62068f9f7891ed000856a8e8](https://app.netlify.com/sites/vuejs-coverage/deploys/62068f9f7891ed000856a8e8)
😎 Browse th... | 2022-02-09T11:41:13 | 2022-02-11T16:38:41 | {} | NONE |
vuejs | core | 1,037,562,748 | 5,417 | netlify[bot] | ✔️ Deploy Preview for *vuejs-coverage* ready!
🔨 Explore the source changes: 834965a0b829138ec7a9ec08a8002b74e8e21a1a
🔍 Inspect the deploy log: [https://app.netlify.com/sites/vuejs-coverage/deploys/620980bef58030000761bb13](https://app.netlify.com/sites/vuejs-coverage/deploys/620980bef58030000761bb13)
😎 Browse th... | 2022-02-12T23:13:29 | 2022-02-13T22:11:33 | {} | NONE |
vuejs | core | 1,038,996,280 | 5,421 | ygj6 | 
You can only use reactive wrap objects.
| 2022-02-14T11:54:25 | 2022-02-14T11:54:25 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.