How serious is the context loss risk?

[creativefctr]

Hi,
Thanks for the great library.
In the documents, there is a mention of potential context loss risk.

• Is this something that can happen randomly at runtime, or can we assume that if our app works locally in the smoke tests, we won’t encounter this issue at all?
• Is it just a precautionary warning, or have there actually been instances of this occurring during development?
• I’m still unsure whether I can safely use this in my project—are there any guidelines or best practices that could help me make that decision?

Thanks

[alexdln]

Hi. Sorry for the incredibly late reply.

Unfortunately, the honest answer is still the same as before: I don't know. The package has passed 700 similar tests, and context hasn't been lost in any of them. This API (nodejs AsyncLocalStorage) is also used in dozens of places in next.js, meaning the risk is comparable to the entire framework's build logic. Meanwhile, next.js strictly controls the scope of this API, while I have no control over how users will use the library.

So, I'm making the note the node.js team mentioned to be more honest with users. Unfortunately (or fortunately), I haven't yet received a request about context loss in this library. There's also no clear answer from the node.js team. I can only assume that if it works for you now, the same code will build reliably. But at some point, you'll add some specific new code, and the context will be lost.