Closed PlopTheReal closed 2 years ago
This is not related to next-connect
but rather the express-session
implementation. It tries to call a function when res.end
is called, resulting in the above error.
I don't think we can do anything about it.
I'm using next-connect 0.12.2 with passport in getServerSideProps like the following:
auth.js:
index.js:
calling auth.run triggers a "warn - You should not access 'res' after getServerSideProps resolves."