it looks like SuperTokens.init() makes an HTTP request. Is there any easy way to mock SuperTokens so that this doesn't happen during my tests?

Hey! There isn’t a way to stop that at the moment I’m afraid. Maybe open an issue about this. For now, you can surround it with a try catch and ignore the error. Things should still work fine regardless.

We ended up mocking the module using jest mocks and mocking init so that the real init doesn't get called during tests

ah fair enough