-
Notifications
You must be signed in to change notification settings - Fork 20
The type definition of $loading
in Nuxt.js conflicts with element-ui
#18
Comments
I didn't check if there is an ongoing issue for this in the Element Repo. But I don't think it will be fixed by Nuxt |
Yeah, it already has the |
Filed an issue, let's see: ElemeFE/element#17630 |
But how do you workaround this? With latest sync, yarn build is now failing |
Bad workaround I guess (changing the type to any): nuxt/typescript#49 (comment) |
I hope it works for you, too? But it's for sure no real solution. For me as a Java and little bit Kotlin software engineer it's a bit strange to have such problems with name/type clashes. |
Yes, that worked. But the repo it in broken state, unless it is documented in readme file, no one will be able to figure it out |
Yes, added to the README. However, I'm not sure if one of the projects will change anything :( |
See: nuxt/typescript#49
I did the workaround locally mentioned in
nuxt/typescript#49 (comment)
However, I hope that gets fixed. Either from the Element-UI or Next.js developers...
The text was updated successfully, but these errors were encountered: