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 | 914,590,969 | 4,330 | yyx990803 | Here's how to get the types working (add this in a `shim.d.ts`):
```ts
declare module 'vue' {
import { CompatVue } from '@vue/runtime-dom'
const Vue: CompatVue
export default Vue
export * from '@vue/runtime-dom'
}
```
Also added to [docs](https://github.com/vuejs/docs/commit/2716506b675f5d65a286073... | 2021-09-07T20:09:28 | 2021-09-07T20:16:10 | {
"+1": 2
} | MEMBER |
vuejs | core | 916,785,364 | 4,294 | MatthewTt | same problem | 2021-09-10T10:01:27 | 2021-09-10T11:00:16 | {} | NONE |
vuejs | core | 912,907,316 | 4,517 | webfansplz | i think have the same problem with `defineProps`, so I mentioned another PR to fixed it | 2021-09-04T04:51:56 | 2021-09-04T04:51:56 | {} | MEMBER |
vuejs | core | 914,458,235 | 4,460 | yyx990803 | Merged too fast - follow up in 22a9b371 | 2021-09-07T16:38:41 | 2021-09-07T16:38:47 | {} | MEMBER |
vuejs | core | 916,455,855 | 4,546 | posva | As a workaround, wrap the container ref, it will be the same ref but the compiler will generate the appropriate code:
```vue
<script setup>
import {ref } from 'vue'
import { useSomething } from "./composition.js"
const { container, handleClick } = useSomething()
const el = ref(container)
</script... | 2021-09-09T21:38:34 | 2021-09-09T21:38:34 | {
"+1": 2
} | MEMBER |
vuejs | core | 916,555,132 | 4,543 | linbuxiao | > When using suspense, it requires a single root node. So your view components must also follow that rule.
Sorry, I didn't know this because the Chinese document is missing the <Suspense> information. | 2021-09-10T01:11:54 | 2021-09-10T01:12:05 | {} | NONE |
vuejs | core | 911,707,254 | 4,433 | sxzz | Hi, @yyx990803
Sorry to disturb you, but the type of problem I mentioned above doesn't seem to be fixed.
- https://github.com/vuejs/vue-next/issues/4433#issuecomment-905143953
- [SFC Playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHRlbXBsYXRlPlxuICA8aDE+e3sgbXNnIH19PC9oMT5cbjwvdGVtcGxhdGU+XG5cbjxzY3JpcHQgc2V0dXA... | 2021-09-02T13:51:21 | 2021-09-02T13:54:50 | {} | MEMBER |
vuejs | core | 912,788,235 | 4,502 | aphex | Fix and explanation of issue supplied here. https://github.com/vuejs/vue-next/pull/4515 | 2021-09-03T20:19:02 | 2021-09-03T20:19:02 | {} | NONE |
vuejs | core | 914,132,923 | 4,532 | posva | In practice, you should really import individual functions from lodash because of the size difference, but a compiler option would definitely help. | 2021-09-07T09:10:37 | 2021-09-07T09:10:37 | {} | MEMBER |
vuejs | core | 914,414,535 | 4,427 | yyx990803 | This affects a number of `async setup()` test cases where they are intentionally `async` without using `await`. | 2021-09-07T15:38:12 | 2021-09-07T15:38:12 | {} | MEMBER |
vuejs | core | 914,987,008 | 4,309 | Justinidlerz | Hey, I'm facing the same problem now. Is there any plan to fix this?
I have an idea to add a feature for [mini-css-extract-plugin](https://github.com/webpack-contrib/mini-css-extract-plugin) to resolve this.
If we need to inject all CSS (including child components or load by other dependencies) into the root shadow-... | 2021-09-08T07:22:07 | 2021-09-08T07:22:07 | {} | NONE |
vuejs | core | 915,233,729 | 4,536 | NataliaTepluhina | @pmorch thank you for reporting this! Codepen in the docs is updated not 👍🏻 | 2021-09-08T13:21:04 | 2021-09-08T13:21:04 | {} | MEMBER |
vuejs | core | 916,562,275 | 4,543 | linbuxiao | The documentation I found through the search engine is fake and the updates are still stuck in the previous version. The real link is this: https://v3.cn.vuejs.org/. | 2021-09-10T01:33:25 | 2021-09-10T01:33:25 | {} | NONE |
vuejs | core | 916,663,726 | 4,548 | Bigfish8 | You don't access the `defineProps` returned value.The type is meaningless so it was abandoned by the sfc-compiler.
This will generate the correct type.
```
<script setup lang="ts">
type Props = {
color: 'blue' | 'red'
}
const props = defineProps<Props>() // <- access the return value
</script>
``` | 2021-09-10T06:27:24 | 2021-09-10T06:27:24 | {
"+1": 2
} | CONTRIBUTOR |
vuejs | core | 916,734,296 | 4,550 | missile-xuan | thank you | 2021-09-10T08:37:04 | 2021-09-10T08:37:04 | {} | NONE |
vuejs | core | 911,701,839 | 4,482 | yyx990803 | `namesapceURI` test cases can simply be fixed via `(node as Element).namespaceURI` for now | 2021-09-02T13:45:48 | 2021-09-02T13:45:48 | {
"+1": 1
} | MEMBER |
vuejs | core | 911,881,459 | 2,015 | Fuzzyma | @kadiryazici the example @unbyte provided is a good solution. It maybe looks a bit complicated but it boils down to:
- create a reference somewhere and fill it with the dom node via `ref="someVar"`
- use that reference as target in teleport
```vue
<teleport :to="someVar" v-if="someVar">
```
With the `v-... | 2021-09-02T16:57:54 | 2021-09-02T16:58:13 | {
"+1": 8,
"heart": 2
} | NONE |
vuejs | core | 912,284,561 | 4,505 | edison1105 | see [playground](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cCBsYW5nPVwidHNcIj5cbmludGVyZmFjZSBQcm9wcyB7XG4gIHByb3AxOiBzdHJpbmc7XG4gIHByb3AyOiBzdHJpbmc7XG4gIHByb3AzOiBzdHJpbmc7XG59XG5jb25zdCBwcm9wcyA9IHdpdGhEZWZhdWx0cyhkZWZpbmVQcm9wczxQcm9wcz4oKSwge1xuICBwcm9wMTogJ3Rlc3QnLFxufSk7XG48L3NjcmlwdD4ifQ==)
thi... | 2021-09-03T06:11:19 | 2021-09-03T06:15:57 | {} | MEMBER |
vuejs | core | 912,346,525 | 4,501 | 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).
---
You don't need Mobx with Vue but if you want... | 2021-09-03T08:08:15 | 2021-09-03T08:08:15 | {} | MEMBER |
vuejs | core | 912,618,562 | 4,468 | alexander-lindner | Hello @ygj6,
thank you for your solution/hint, it solved my problem. Is there a way for vue to print out better debug messages? Now I'm able to understand the message but it would be easier, if the message would be much more intuitive... | 2021-09-03T15:22:39 | 2021-09-03T15:22:39 | {} | NONE |
vuejs | core | 912,869,315 | 4,498 | code-farmer-i | I think this is a limitation, because when the inherited interface is imported from the outside, the complier-sfc does not know what attributes the external interface contains | 2021-09-04T00:01:04 | 2021-09-04T00:01:04 | {
"+1": 2
} | NONE |
vuejs | core | 913,231,755 | 4,524 | yyx990803 | duplicate of #4499 | 2021-09-05T21:38:31 | 2021-09-05T21:38:31 | {} | MEMBER |
vuejs | core | 911,698,309 | 4,494 | yyx990803 | closed via #4495 | 2021-09-02T13:42:36 | 2021-09-02T13:42:36 | {} | MEMBER |
vuejs | core | 911,447,068 | 4,482 | github-actions[bot] | ## Size report
| Path | Size |
| -------------------------- | ------------- |
| vue.global.prod.js | 45.81 KB (0%) |
| runtime-dom.global.prod.js | 30.22 KB (0%) |
| size-check.global.prod.js | 17.42 KB (0%) | | 2021-09-02T09:26:24 | 2021-09-02T13:52:43 | {} | NONE |
vuejs | core | 911,743,193 | 4,497 | posva | This working correctly, you should do ` <comp style="color:red;"></comp>` without the `'`.
| 2021-09-02T14:24:47 | 2021-09-02T14:24:47 | {} | MEMBER |
vuejs | core | 912,992,082 | 4,523 | pangao66 | https://forum.vuejs.org/t/how-to-set-dynamic-v-model-in-v-for-with-nested-object-and-string-path/118845 这里有个问题跟我这个问题一样的 更具体 | 2021-09-04T15:29:45 | 2021-09-04T15:29:45 | {} | NONE |
vuejs | core | 913,532,012 | 4,423 | henribru | I'm still having this issue in 3.2.9. I've been using the workaround Nisgrak and if I remove it in 3.2.9 the errors about SFCs not having a default export come back. | 2021-09-06T10:19:59 | 2021-09-06T10:19:59 | {} | NONE |
vuejs | core | 914,449,639 | 4,424 | yyx990803 | After looking into it I believe the more proper fix is ensuring style patching always respect `v-show`'s inline display value (there was already logic in there but not covering the removal case) | 2021-09-07T16:25:50 | 2021-09-07T16:25:50 | {} | MEMBER |
vuejs | core | 914,544,510 | 4,532 | theoephraim | @yyx990803 - thanks, I am using script setup already. This issue has not been a blocker at all, it's just been filling my browser console with warnings. I was able to figure out how to hide it yesterday using a custom warning handler, but I still think another config setting as mentioned above could be helpful.
For ... | 2021-09-07T18:53:11 | 2021-09-07T18:53:11 | {} | NONE |
vuejs | core | 915,119,692 | 3,577 | edison1105 | @XMBLDB could you provide a mini repro? | 2021-09-08T10:33:53 | 2021-09-08T10:33:53 | {} | MEMBER |
vuejs | core | 915,621,785 | 4,532 | yyx990803 | Hmm, I don't think this should happen with `<script setup>` (see [playground example](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcblxuY29uc3QgJHByb3BzID0gMTIzXG48L3NjcmlwdD5cblxuPHRlbXBsYXRlPlxuICA8aDE+e3sgJHByb3BzIH19PC9oMT5cbjwvdGVtcGxhdGU+IiwiaW1wb3J0LW1hcC5qc29uIjo... | 2021-09-08T22:42:11 | 2021-09-08T22:42:11 | {} | MEMBER |
vuejs | core | 640,078,309 | 629 | milewski | It was removed fine, but it did more than just provided typing no? for example I could extend 2 vue objects by doing this before:
```js
import App from 'app.vue'
export default App.extend({
data(){
...
}
})
or
export default {
extends: App
}
```
Both of these seem to have been ... | 2020-06-06T15:30:40 | 2021-09-10T07:28:19 | {
"+1": 8
} | NONE |
vuejs | core | 916,803,830 | 4,551 | posva | What is the actual use case? | 2021-09-10T10:32:36 | 2021-09-10T10:32:36 | {} | MEMBER |
vuejs | core | 913,173,571 | 4,515 | aphex | Yup, I will close mine as theirs looks good to me and has a test 😍 | 2021-09-05T15:16:54 | 2021-09-05T15:16:54 | {} | NONE |
vuejs | core | 913,215,383 | 4,516 | LinusBorg | Your plugin can expose a bootstrapping function / mixin that can be added to the root component.
That would be the usual way so far. Personally I'm not a friend of further increasing the Plugin API surface. | 2021-09-05T19:37:42 | 2021-09-05T19:37:42 | {} | MEMBER |
vuejs | core | 913,236,826 | 4,516 | yyx990803 | I think an easy improvement is allowing a plugin function to return a "cleanup" callback. | 2021-09-05T22:18:00 | 2021-09-05T22:18:00 | {} | MEMBER |
vuejs | core | 914,180,027 | 3,921 | xinxinhe1810 | 用的 webpack 5 、改成 vue-loader@16.3.1 ,没有用 thread-loader 生产环境还是有问题。 | 2021-09-07T10:15:27 | 2021-09-07T10:15:27 | {} | NONE |
vuejs | core | 914,412,402 | 4,532 | yyx990803 | You are not limited by this when using `<script setup>` - you should probably migrate if you haven't already? | 2021-09-07T15:35:21 | 2021-09-07T15:35:21 | {} | MEMBER |
vuejs | core | 916,685,590 | 4,550 | posva | This is not a bug [SFC](https://sfc.vuejs.org/#eyJBcHAudnVlIjoiPHNjcmlwdCBzZXR1cD5cbmltcG9ydCB7IHJlZiB9IGZyb20gJ3Z1ZSdcbmltcG9ydCBDb21wIGZyb20gJy4vQ29tcC52dWUnXG5cbmNvbnN0IGFyciA9IHJlZihbeyBrZXk6IDAgfSwgeyBrZXk6IDEgfV0pXG5cbmZ1bmN0aW9uIGxvZyhpKSB7XG4gIGNvbnNvbGUubG9nKCdjcmVhdGVkJywgaSlcbn1cbjwvc2NyaXB0PlxuXG48dGVtcGxhd... | 2021-09-10T07:14:20 | 2021-09-10T07:14:20 | {} | MEMBER |
vuejs | core | 899,071,131 | 4,335 | lidlanca | great pr @edison1105 please consider the changes in https://github.com/vuejs/vue-next/pull/4337
@posva closed the pr because it is similar to your pr title but actually has improved coverage of cases.
| 2021-08-15T15:59:48 | 2021-08-15T15:59:48 | {} | CONTRIBUTOR |
vuejs | core | 899,317,599 | 4,312 | joostdelange | @cutsin Did you test it with all 3.2.x versions? Downgrading to version 3.2.1 resolved the issue for me, while downgrading to 3.2.0 did not. | 2021-08-16T08:18:13 | 2021-08-16T08:18:13 | {} | NONE |
vuejs | core | 897,412,061 | 4,323 | posva | Temporary solution at https://github.com/vitejs/vite/issues/4573#issuecomment-896893090 | 2021-08-12T07:27:37 | 2021-08-12T07:27:37 | {} | MEMBER |
vuejs | core | 898,194,192 | 4,330 | philippevezina | I've also tried by adding the following in `tsconfig.json` and it did not work:
```json
"paths": {
"vue/*": [
"@vue/compat/*"
]
}
```
and
```json
"paths": {
"vue/*": [
"node_modules/@vue/compat/*"
]
}
``` | 2021-08-13T05:06:38 | 2021-08-13T05:06:38 | {} | NONE |
vuejs | core | 898,435,911 | 4,318 | jods4 | Awesome that you can take a look at that!
Thanks a lot! 🙇♂️
For the perf test, I think it'd need to be run at a few different array sizes, to find the sweet spot.
As I said in intro, we can make this look as dramatic as we want simply by picking larger and larger arrays.
When a computed runs again, there's bo... | 2021-08-13T12:50:44 | 2021-08-13T12:50:44 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 899,023,176 | 4,340 | HcySunYang | As a workaround, change this:
```html
<div>{{ `${VARIABLE}123` }}</div>
```
to
```html
<div>{{ VARIABLE }}123</div>
<!-- or -->
<div>{{ VARIABLE + `123` }}</div>
``` | 2021-08-15T09:35:11 | 2021-08-15T09:37:05 | {} | MEMBER |
vuejs | core | 899,085,503 | 4,345 | TuringJest | Works!
Now, I really wish I had not spent that time hacking around the issue 😅
Thanks a lot!
| 2021-08-15T17:31:44 | 2021-08-15T17:31:44 | {} | NONE |
vuejs | core | 897,417,463 | 4,312 | oliverzy | > I have facing a similar issue with vuedraggable ^4.0.3
>
> 
>
> 
>
>  {
return ["x", "y"].includes(direction);
},
```
see https://v3.vuejs.org/guide/typescript-support.html#annotating-props
| 2021-08-13T03:16:01 | 2021-08-13T03:16:01 | {} | MEMBER |
vuejs | core | 898,388,691 | 4,332 | posva | All the documentation is already in Vue docs | 2021-08-13T11:24:25 | 2021-08-13T11:24:25 | {} | MEMBER |
vuejs | core | 898,430,861 | 4,332 | masx200 | "@vue/reactivity"
It does not export the "watch" method, it has the "effect" method, which is not written in the documentation. | 2021-08-13T12:40:53 | 2021-08-13T12:40:53 | {
"+1": 1
} | NONE |
vuejs | core | 898,463,727 | 4,332 | edison1105 | @masx200 there is no `watch `method in reactivity. use `effect `instead.
BTW, `watchEffect` is a part of `runtime-core`.
请仔细阅读文档. | 2021-08-13T13:37:54 | 2021-08-13T13:38:56 | {} | MEMBER |
vuejs | core | 899,023,555 | 4,340 | sheremet-va | I want to point out, that the problem persist not only inside `{{ }}`, but inside any template string ('\`'). For example, inside \:name="\`${VARIABLE}123\`"
But workaround is working, yes. | 2021-08-15T09:38:51 | 2021-08-15T09:38:51 | {} | NONE |
vuejs | core | 899,646,078 | 4,356 | posva | cc @Akryum | 2021-08-16T16:27:14 | 2021-08-16T16:27:14 | {} | MEMBER |
vuejs | core | 899,781,350 | 4,331 | yyx990803 | I don't even think this needs to be specifically about usage of scope variables. `v-once` isn't designed to be used inside `v-for` so the check and the warning message can both be simpler. | 2021-08-16T20:01:30 | 2021-08-16T20:01:44 | {} | MEMBER |
vuejs | core | 897,358,900 | 4,315 | Cansiny0320 | > The use of plain `for` loops is intentional for better performance according to earlier benchmarks. Thank you.
Ok, I get it! Thank you. | 2021-08-12T05:26:11 | 2021-08-12T05:26:11 | {} | CONTRIBUTOR |
vuejs | core | 897,494,355 | 4,318 | jods4 | > As far as I can see, only in case of iteration on the shallowRef, we could omit the get trap. That makes it a bit of a niche optimization.
My thoughts:
- Shallow array are still an important case, esp. for performance conscious users. If you present a large list of readonly rows, shallow array is the right choic... | 2021-08-12T09:39:20 | 2021-08-12T09:39:20 | {} | CONTRIBUTOR |
vuejs | core | 897,635,009 | 4,321 | johnsoncodehk | I personal think this is InputHTMLAttributes types problem, hope this comment helpful: https://github.com/johnsoncodehk/vue-tsc/issues/57#issuecomment-897276138 | 2021-08-12T13:21:30 | 2021-08-12T13:21:30 | {
"+1": 1
} | MEMBER |
vuejs | core | 899,057,547 | 4,312 | mbtcg | In my project this problem only occurs in dev mode and work without problem in production build | 2021-08-15T14:16:25 | 2021-08-15T14:16:25 | {} | NONE |
vuejs | core | 899,159,875 | 4,341 | wython | > Give project for reproduction, please.
https://github.com/wython/my-vue-app
@HcySunYang
just a empty project | 2021-08-16T01:51:56 | 2021-08-16T01:59:58 | {} | NONE |
vuejs | core | 899,318,958 | 4,337 | posva | > @posva I would have appreciated you actually providing a review on this pr instead of closing it.
a lot of time and effort was put into this pr, and dismissing it is quite discouraging
Once again, this is nothing personal, it's about respecting the original author's PR and making it easier to review for the maint... | 2021-08-16T08:20:07 | 2021-08-16T08:21:01 | {} | MEMBER |
vuejs | core | 899,458,095 | 4,337 | lidlanca | haha "nothing personal", is like saying "I don't mean to offend but".
I recommend you let someone else review my contribution so you get more unbiased perspectives. :)
I actually do hope its personal, and that other people are not treated the same way.
who knows how many valid contributions were closed or dism... | 2021-08-16T12:07:55 | 2021-08-16T12:07:55 | {} | CONTRIBUTOR |
vuejs | core | 897,390,412 | 4,077 | turrsis | @edison1105 can you approve to run tests? | 2021-08-12T06:45:09 | 2021-08-12T06:45:09 | {} | CONTRIBUTOR |
vuejs | core | 897,387,636 | 4,312 | LinusBorg | > would be even better if we could have a global defineEmits/defineProps etc. without needing import every single time.
The implementation in 3.2 is providing exactly that. Are you already on 3.2.1 ? | 2021-08-12T06:38:55 | 2021-08-12T07:07:34 | {} | MEMBER |
vuejs | core | 897,404,439 | 4,321 | LinusBorg | It would be great it you could provide an acutal TS example we can run. | 2021-08-12T07:13:19 | 2021-08-12T07:13:19 | {} | MEMBER |
vuejs | core | 899,007,725 | 4,312 | HcySunYang | Results of preliminary investigation, the AST that lives in the [resolveTemplateUsageCheckString](https://github.com/vuejs/vue-next/blob/master/packages/compiler-sfc/src/compileScript.ts#L2211) function represents a template that has not been processed by `pug`, so the imported component is checked as not being used in... | 2021-08-15T07:15:25 | 2021-08-15T07:15:25 | {
"+1": 1
} | MEMBER |
vuejs | core | 899,035,720 | 4,337 | posva | Could you leave the reviews on the other PR instead of creating a new one, please? | 2021-08-15T11:24:52 | 2021-08-15T11:24:52 | {} | MEMBER |
vuejs | core | 899,052,416 | 4,343 | vue-bot | Hello, thank you for taking time filling this issue!
However, we kindly ask you to use our [Issue Helper](https://new-issue.vuejs.org/?repo=vuejs/vue-next) when creating new issues, in order to ensure every issue provides the necessary information for us to investigate. This explains why your issue has been automatic... | 2021-08-15T13:42:48 | 2021-08-15T13:42:48 | {} | CONTRIBUTOR |
vuejs | core | 899,138,475 | 4,339 | hezhongfeng | Looking forward to this feature. | 2021-08-16T00:38:07 | 2021-08-16T00:38:07 | {} | NONE |
vuejs | core | 899,187,326 | 4,283 | zhangenming | https://codesandbox.io/s/frosty-sun-471ok?file=/src/main.js
please look at the code again, thanks
@posva
Is this intentional?
we can't use Object.prototype with vue together? | 2021-08-16T03:26:30 | 2021-08-16T03:26:53 | {} | CONTRIBUTOR |
vuejs | core | 897,394,923 | 4,312 | jzs11 | > > would be even better if we could have a global defineEmits/defineProps etc. without needing import every single time.
>
> The implementation in 3.2 is providing exactly that. Are you already on 3.2.1 ?
I am using Vue 3.2.2 and Vue cli 4.5.13, just tried to do it without defineEmits, however it shows an error
... | 2021-08-12T06:55:15 | 2021-08-12T07:07:43 | {} | NONE |
vuejs | core | 897,668,626 | 4,325 | edison1105 | @harmyderoman
your repro link is broken. | 2021-08-12T14:05:38 | 2021-08-12T14:05:38 | {} | MEMBER |
vuejs | core | 898,284,007 | 4,330 | LinusBorg | @posva
* compat does provide a default export for a Vue 2 constructor.
* The Migration guide also has migration to `createApp()` in step 7 of the install guide, while the app should run in step 5 already, where the codebase should still have `new Vue()`, I think it's reasonable to expect that TS should can deal ... | 2021-08-13T08:30:38 | 2021-08-13T09:32:33 | {} | MEMBER |
vuejs | core | 899,385,227 | 4,318 | basvanmeurs | I added some benchmarks. As expected, reactive arrays are much slower than raw.
See https://github.com/basvanmeurs/vue-next-benchmarks/blob/master/src/reactiveArray.js for the benchmarks, [feel free to run them on your local machine](https://basvanmeurs.github.io/vue-next-benchmarks/?b=reactiveArray) or just view the ... | 2021-08-16T10:03:29 | 2021-08-16T10:12:01 | {
"+1": 1
} | CONTRIBUTOR |
vuejs | core | 899,477,946 | 4,307 | henribru | Seems like this issue is new in 3.2, ran into it after upgrading from 3.1.5 | 2021-08-16T12:41:13 | 2021-08-16T12:41:13 | {} | NONE |
vuejs | core | 897,694,909 | 4,325 | posva | You can't use CSS vars in media query declarations and since Vue relies on them, this is not possible. | 2021-08-12T14:37:42 | 2021-08-12T14:37:42 | {} | MEMBER |
vuejs | core | 898,153,555 | 4,329 | njzzzz | 
works good | 2021-08-13T03:09:14 | 2021-08-13T03:09:14 | {} | NONE |
vuejs | core | 898,278,485 | 4,304 | aetstapa | @Hansuku
My project's dependencies are newest.
```
"vue": "^3.2.2"
"@vue/compiler-sfc": "^3.2.2"
```
I found a weird solution that does not needs to downgrade dep package. Maybe you need to try a few times.
```
rm -fr node_modules package-lock.json
npm install
```
But the error appears irregularly, and I s... | 2021-08-13T08:20:56 | 2021-08-13T08:20:56 | {} | NONE |
vuejs | core | 898,279,446 | 4,304 | LinusBorg | When you have an install where the error pops up, try running `yarn why vue`. It will tell you which packages are depending on which version of vue.
From what we have seen elsewhere, this happens when a dependency has a dependency of vue `<3.2`. `elelement-plus`, for example, locks the vue version on `3.1.x`:
htt... | 2021-08-13T08:22:30 | 2021-08-13T08:25:46 | {} | MEMBER |
vuejs | core | 898,385,343 | 4,324 | Hazlank | bitwise will faster?it just use AND instrustion,logic operator will generate CMP and JUMP instrustion,so the first time be true will stop it | 2021-08-13T11:18:13 | 2021-08-13T11:18:13 | {} | CONTRIBUTOR |
vuejs | core | 898,454,290 | 4,330 | philippevezina | It indeed seems to be a problem with the constructor typing. That being said, the workaround does not seem to be working on my end:
```ts
ERROR in src/main.ts:1:10
TS2305: Module '"../node_modules/vue/dist/vue"' has no exported member 'Vue'.
> 1 | import { Vue, VueCompat } from 'vue'
| ^^^
2 ... | 2021-08-13T13:22:03 | 2021-08-13T13:22:03 | {} | NONE |
vuejs | core | 898,457,523 | 4,316 | sherlock1982 | I will close it as it's already in the docs and a duplicate.
| 2021-08-13T13:27:20 | 2021-08-13T13:27:20 | {} | NONE |
vuejs | core | 898,466,397 | 4,309 | pawel-marciniak | Hi, for me exporting child component in second <script> tag results in `Syntax Error: TypeError: Cannot read property 'content' of null` error :/ | 2021-08-13T13:42:16 | 2021-08-13T13:42:16 | {} | NONE |
vuejs | core | 898,601,679 | 4,330 | philippevezina | Ohh my bad! This workaround, though not ideal, does indeed work:
```ts
import Vue, { CompatVue } from 'vue'
(Vue as unknown as CompatVue).config.productionTip = false
``` | 2021-08-13T17:06:26 | 2021-08-13T17:06:26 | {} | NONE |
vuejs | core | 899,015,053 | 4,340 | sheremet-va | And the latest vue release is 3.2.2 | 2021-08-15T08:23:02 | 2021-08-15T08:23:02 | {} | NONE |
vuejs | core | 899,043,258 | 4,309 | TatsuyaYamamoto | @pawel-marciniak I can check the cause of error if there is a reproduction code(repository). | 2021-08-15T12:28:36 | 2021-08-15T12:28:36 | {} | NONE |
vuejs | core | 899,061,536 | 4,312 | joostdelange | I wanted to give my 2 cents on this issue since I was about to create one myself.
This issue does not only occur when using script `<setup>` TypeScript + Pug, for me this happens when using it with just Typescript (`<script setup lang="ts">`), without Typescript it works like expected.
And like @mbtcg says above is... | 2021-08-15T14:47:02 | 2021-08-15T14:49:07 | {
"+1": 1
} | NONE |
vuejs | core | 899,200,248 | 4,347 | Justineo | It's a deprecated element. Use CSS instead.
BTW. The reproduction link is invalid. | 2021-08-16T04:13:44 | 2021-08-16T04:13:44 | {} | MEMBER |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.