Mix of express/koa with passport in both breaks about koa-passport HOT 3 CLOSED

Would it help to not use the global instance in your express app?

const instance = new passport.Passport()

from koa-passport.

Like i said, ive done this. Maybe i should mention, im using esm modules, not commonjs. maybe this is the reason?
The passport.framework(...) call will be still executed and set the framework for every instance created after koa-passport is used. since i cant change the code of the express app, i need to make sure koa-passport is not setting this global or only in the instance.
Edit: To mention here also the express app is importing the global passport. So i cant use an instance in there.

Current workaround is to reset your settings after i imported koa-passport, so just set the default framework again.

Would still prefer to have an "better" solution for this. Seems this problem will maybe affect more ppl, since esm modules is the new standard.

But like i said ive a working solution, so not rly a "bug" anymore. More a feature request to make this somehow configurable

from koa-passport.

I am afraid that I feel like this is too much of an edge case (especially the part of not being able to adjust the express app) and thus not worth adding. Thanks for bringing this up anyway. I'll go ahead and close the issue, but anyone feel free to jump in if you have a similar requirement/use-case.

from koa-passport.