-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Vue mount type definitions error on SFCs with only one define
API used
#24818
Comments
I wonder why adding Either way, let's fix this - I have no idea why an empty mounting options arg triggers this. Vue core changed their types a bunch recently, I wonder if that's related. Also, I wonder if Test Utils has the same issue. |
Hey team! Please add your planning poker estimate with Zenhub @amehta265 @astone123 @lmiller1990 @marktnoonan @mike-plummer @warrensplayer @ZachJW34 |
Probably just need to copy+paste latest typedefs from Test Utils, or update to the latest version of Test Utils. |
This is blocking us from upgrading to TypeScript 4.9 |
It will be in the next release, please wait a bit. We release every two weeks. I should have targeted master so this would have been auto-released, but I forgot, sorry about that. |
I know this issue is closed, but I want to add that after upgrading to TypeScript 5, a new type error for the emits occur (not exactly same, but seems related).
|
Hi @mbp please open a new issue if you are encountering problem while using Cypress. |
Current behavior
Upgrading to Cypress v11 (any minor version) has resulted in TypeScript errors appearing in my component test files, specifically when using mount with an SFC that has only one of the
defineProps
,defineEmits
anddefineExpose
API's used in itssetup
.Changing the component definition code to the follow will make the error disappear:
Desired behavior
TypeScript should not throw an error when mounting a Vue SFC component with the following syntax, regardless of the component definition:
Test code to reproduce
Due to the similarities to #23653 that I submitted a while back, I forked the repo that @lmiller1990 graciously provided there. Turns out, all I had to do was upgrade the package versions to reproduce the error :)
https://github.com/JoostKersjes/cypress-issue-23653/tree/v11-upgrade-type-issue
Cypress Version
11.2.0 (reproducable for any version >= 11.0.0)
Node version
v16.8.0
Operating System
Kubuntu 20.04
Debug Logs
No response
Other
No response
The text was updated successfully, but these errors were encountered: