You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 16, 2024. It is now read-only.
Currently, the "auth" module is implemented as a singleton. This makes it difficult to use in contexts where the same process exposes multiple OAuth endpoints. My use case is a versioned API that defines dedicated authentication routes for each version.
In the short-term, I am re-installing this module in each of my project's API-version-specific directories. Another approach (for anyone else running up against this issue) would be to remove this project's files from require.cache in each place it is used.
Ideally, I would like to be able to use the auth object in the same way as the client object. To demonstrate, here's how that would look for an example from the project's readme file:
Currently, the "auth" module is implemented as a singleton. This makes it difficult to use in contexts where the same process exposes multiple OAuth endpoints. My use case is a versioned API that defines dedicated authentication routes for each version.
In the short-term, I am re-installing this module in each of my project's API-version-specific directories. Another approach (for anyone else running up against this issue) would be to remove this project's files from
require.cache
in each place it is used.Ideally, I would like to be able to use the
auth
object in the same way as theclient
object. To demonstrate, here's how that would look for an example from the project's readme file:The text was updated successfully, but these errors were encountered: