Closed dferber90 closed 1 year ago
We saw this error appearing when using statsig-node inside of a middleware on Vercel.
I saw that you are already checking whether timer.unref exists before calling it on other places, so I amended this instance which was causing the error.
timer.unref
Closing as this made its way in through https://github.com/statsig-io/node-js-server-sdk/releases/tag/v5.9.3
We saw this error appearing when using statsig-node inside of a middleware on Vercel.
I saw that you are already checking whether
timer.unref
exists before calling it on other places, so I amended this instance which was causing the error.