Hi, I want to work on this issue.

I tried to reproduce this bug on the node-fetch sample program by setting KEPLOY_MODE=off, and it's returning the complete response object with the correct status code and message. Can you describe your step 2 a bit more elaborately so I can better understand how to reproduce the bug? Thanks.

Hi @Ramanjs, the problem is that I have not integrated the express hook in my local application. Hence, when you comment the require hook for express in node-fetch/server.js, then the application will crash with this message in screenshot

Hello @re-Tick I am interested to work on this issue

Hey @re-Tick I was trying to reproduce this issue. But even for me this is working fine. It would be really helpful if you can add precise instructions on how to reproduce this bug.

Steps to reproduce this is:

1. Install the sample application for TS-SDK. here
2. Comment this line and restart the sample application.
3. Now try doing the curl request to sample application.

@re-Tick Thanks for providing this info. I'm now able to reproduce the bug and I think I've understood the issue. I'll soon create a PR for this.

Hi @re-Tick, the server crashes for all modes, not just when it is off. I am a bit confused about the expected result of this issue. The node-fetch module depends upon the middleware introduced by the express hook to generate and store test cases and their mocks and deps. If I use node-fetch alone, no mocks will be generated since there is no Keploy object and no context either. It would be amazing if you could clarify how this thing works and let me know if Im approaching this wrong. Thanks!

Hi @re-Tick, the server crashes for all modes, not just when it is off. I am a bit confused about the expected result of this issue. The node-fetch module depends upon the middleware introduced by the express hook to generate and store test cases and their mocks and deps. If I use node-fetch alone, no mocks will be generated since there is no Keploy object and no context either. It would be amazing if you could clarify how this thing works and let me know if Im approaching this wrong. Thanks!

Yes, you got this right @Ramanjs. The expected behaviour should that no test/mocks are generated because of missing express integration. But it should make the actual call to node-fetch which is currently missing.

Can I work on this issue?

Hi @Shaurya-Developer, please make your changes and open a PR. Ans mention the PR in the Gsoc/2023 ts-sdk task list.

Okay, @re-Tic. And what I'm supposed to write in PR? “Solved #376 Gsoc/2023 ts-sdk” is this alright?

Okay, @re-Tic. And what I'm supposed to write in PR? “Solved #376 Gsoc/2023 ts-sdk” is this alright?

Mention this issue and your changes in your PR and provide the link of PR in TS-SDK task list

Okay, @re-Tic. And what I'm supposed to write in PR? “Solved #376 Gsoc/2023 ts-sdk” is this alright?

Mention this issue and your changes in your PR and provide the link of PR in TS-SDK task list

Alright, Thanks

Please Assign this issue to me

Hi @VishalMyla, the issues are open for all. Please feel free to discuse your changes here or make your PR.

This is the implementation I came up with! Can you please review this?