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
The documentation states it clearly that this library shouldn't be used in production because it blocks the application. Which is true, except there are examples where you actually want to block the application and here is mine:
I have a node service that accepts requests, these requests come with a signed JWT, and in order to verify the signature I need the public key from the signing service. So when the first service starts, and before I allow express to receive requests, I want the service to load the public key from the signing service, and this module is very handy in this situation. The public key is fetched once only at the beginning of the application and that's why this module doesn't have a negative effect on my service at all, on the contrary, it saved the day for me.
What I suggest is to beside the warning, leave a room for the developer to choose what's good for their situation.
The text was updated successfully, but these errors were encountered:
Hello
The documentation states it clearly that this library shouldn't be used in production because it blocks the application. Which is true, except there are examples where you actually want to block the application and here is mine:
I have a node service that accepts requests, these requests come with a signed JWT, and in order to verify the signature I need the public key from the signing service. So when the first service starts, and before I allow express to receive requests, I want the service to load the public key from the signing service, and this module is very handy in this situation. The public key is fetched once only at the beginning of the application and that's why this module doesn't have a negative effect on my service at all, on the contrary, it saved the day for me.
What I suggest is to beside the warning, leave a room for the developer to choose what's good for their situation.
The text was updated successfully, but these errors were encountered: