CaptainPhoton
07/03/2022, 8:32 AMawait supertokens.getUserCount()
CaptainPhoton
07/03/2022, 8:32 AMrp_st
07/03/2022, 8:33 AMrp_st
07/03/2022, 8:33 AMrp_st
07/03/2022, 8:33 AMCaptainPhoton
07/03/2022, 8:33 AMCaptainPhoton
07/03/2022, 8:33 AMCaptainPhoton
07/03/2022, 8:34 AMrp_st
07/03/2022, 8:34 AMCaptainPhoton
07/03/2022, 8:34 AMrp_st
07/03/2022, 8:35 AMCaptainPhoton
07/03/2022, 8:35 AMCaptainPhoton
07/03/2022, 8:35 AMrp_st
07/03/2022, 8:35 AMCaptainPhoton
07/03/2022, 8:36 AMCaptainPhoton
07/03/2022, 8:36 AMCaptainPhoton
07/03/2022, 8:36 AMrp_st
07/03/2022, 8:37 AMrp_st
07/03/2022, 8:37 AMCaptainPhoton
07/03/2022, 8:37 AMrp_st
07/03/2022, 8:37 AMCaptainPhoton
07/03/2022, 8:37 AMrp_st
07/03/2022, 8:37 AMCaptainPhoton
07/03/2022, 8:38 AMCaptainPhoton
07/03/2022, 9:06 AMCaptainPhoton
07/03/2022, 9:07 AMCaptainPhoton
07/03/2022, 9:09 AMrp_st
07/03/2022, 9:09 AMrp_st
07/03/2022, 9:10 AMCaptainPhoton
07/03/2022, 9:13 AMimport supertokens from 'supertokens-node';
in the controller file, and presumably the controller file was loaded somehow before supertokens.init() was called. At this point, Supertokens seems to already try to "load" (or whatever) the initialized instance. If it doesn't exist, nothing is thrown. Then when I tried to use a method (example supertokens.getUserCount()
) in a request handler, it throws the "init not called" error. It would be better if the instance was loaded when I call the getUserCount method instead of immediately upon importing the modulerp_st
07/03/2022, 9:14 AMrp_st
07/03/2022, 9:14 AMrp_st
07/03/2022, 9:15 AMCaptainPhoton
07/03/2022, 9:15 AMCaptainPhoton
07/03/2022, 9:16 AMrp_st
07/03/2022, 9:16 AMCaptainPhoton
07/03/2022, 9:17 AMCaptainPhoton
07/03/2022, 9:17 AM