-
-
Notifications
You must be signed in to change notification settings - Fork 81
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
Q: How to use with TypeScript? #129
Comments
Thanks @manuman94, I do plan to eventually rewrite Jasmine-Matchers in TypeScript but it will take time. In the meantime I wrote a newer version in TypeScript for Jest – but that is for Jest, not Jasmine. A Jasmine version will come in time, I'm planning to create it at expect-more-jasmine then create a backported version of that to publish in this repo. |
Thanks @JamieMason, I've been testing with this matchers and other custom matchers created by me with your library add-matchers and it is awesome. An organized way of creating useful new matchers. In the meantime I placed a script in my package.json that copies all ".d.ts" files on Thank you for this awesome library. |
Thanks a lot @manuman94, you're welcome – it's really great to hear of it being used. |
Do you have an example repo somewhere I can look at @manuman94 to try and help? Also, have you seen the TypeScript example at https://github.com/JamieMason/Jasmine-Matchers/tree/03bc19b4170dad265684f112f3a90f5d97fd6998/examples to compare against? |
Description
I tried to integrate jasmine-expect in my jasmine test framework built in Typescript and I got "types not found" problems. It's not working when I launch the tests but VSCode is complaining too throwing me errors like:
Property 'toBeArray' does not exist on type 'ArrayLikeMatchers<number>'.
I figured out that the problem is that is not finding the type definitions. I downloaded @types/jasmine-expect but is a stub and stills giving me the errors.
Suggested Solution
When I copy the
node_modules/jasmine-expect/dist
types tonode_modules/@types/jasmine-expect
folder my project is running. Why don't keep type definitions on its@types
folder?Thank you so much!
The text was updated successfully, but these errors were encountered: