-
Notifications
You must be signed in to change notification settings - Fork 157
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
Testing with TypeScript and TS-Jest #519
Comments
Goes without saying this is weird because the method exist if you import this way But does not function properly after being ran actively, needs to be reverted and ignored to be useful. I'm sure I'm missing a setting somewhere, but this is ridiculous in the year 2023. |
Something is wrong in the way the types are exported. |
Hi there,
I was following the TypeScript and Testing guides but I had to work a lot in order to get the tests run with ts-jest.
Setup
This is my setup:
index.ts
defines the handlerindex.test.ts
defines the handler's testjest.config.ts
ts-jest config filetsconfig.json
defines TS settingsEnvironment
Node 18.12.1
TypeScript 4.9.5
jest 29.4.3
ts-jest 29.0.5
@google-cloud/functions-framework 3.1.3
OS: macOS Ventura on M1 Pro processor
Error
I get this error when I try to import the
testing
submodule without the// @ts-ignore
in the test fileI think it's related to this TypeScript issue and the way the package.json is declared in
@google-cloud/functions-framework
module.The test will also fail if not using the --experimental-vm-modules whith jest, but that's because of the
await import("./index")
statement in the hook.So you need to add this to the
package.json
scripts"test": "NODE_OPTIONS=--experimental-vm-modules jest"
and then launch
npm test
.Workaround
Adding the
// @ts-ignore
does the trick. However, if I am not messing up with the TS settings too much, wouldn't it be nice to have a more TS-friendly testing module package declaration?And if you think (and I might agree with you) that this issue is more a TS problem than your library's, then could you please extend the documentation by adding a "testing with typescript" section in the docs (feel free to add my workaround if deemed good enough)?
The text was updated successfully, but these errors were encountered: