What version of Bun is running?
1.0.0+822a00c4d508b54f650933a73ca5f4a3af9a7983
What platform is your computer?
Linux 5.15.90.1-microsoft-standard-WSL2 x86_64 x86_64
What steps can reproduce the bug?
create an async function that should throw an error.
using expect with .rejects should start with await before the expect as said in the jest api
jest-api
What is the expected behavior?
the test should run successfully with this syntax as bun should be compatible with jest api and .rejects also appear to be implemented in bun docs.
What do you see instead?
await has no effect because the bun's type of expect is:
The error I get:
Additional information
No response
What version of Bun is running?
1.0.0+822a00c4d508b54f650933a73ca5f4a3af9a7983
What platform is your computer?
Linux 5.15.90.1-microsoft-standard-WSL2 x86_64 x86_64
What steps can reproduce the bug?
create an async function that should throw an error.
using expect with .rejects should start with await before the expect as said in the jest api
jest-api
What is the expected behavior?
the test should run successfully with this syntax as bun should be compatible with jest api and .rejects also appear to be implemented in bun docs.
What do you see instead?
await has no effect because the bun's type of
expectis:The error I get:
Additional information
No response