Thanks, we should be able to merge this with a few changes. But trying to understand one thing first ... Why should our TS compiler settings affect yours?

We have not set noImplicitReturns to true. Assuming that is done with reason, I'd expect this not to impact consuming projects that does set it to true as we ship js and d.ts files. Can you give some context?

In this case, I think setting noImplicitReturns to true and fix the problem makes sense. But I'd also argue it should not be needed. So I'd like to try and understand what's going on prior to merging this.

I gave this a try in a project using [email protected] and @auth0/[email protected] and have set "noImplicitReturns": true.I was able to include and use the SDK just fine without any compiler issue. Which was also concluded by @nandan-bhat here: #1280 (comment).

So I think we need a reproduction to investigate what is happening, rather than merge a PR that fixes something that we can not reproduce.

So the problem was on my end. I imported the file wrong. Using the normal import fixes the problem too without needing a noImplicitReturns workaround. my bad!