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 store is somehow keeping the node process alive even after the HTTP server is closed. session-file-store did this too and needed cleanup code to clear the reapInterval timer. Suspect LokiJS persistence adapter is keeping things alive now, because connect-loki never closes it. See LokiJS docs (find close on the page).
Need to either find another persistence solution, or address the above issues in connect-loki.
session-file-storewas causing EPERM errors on Windows (see isaacs/node-graceful-fs#104).As a result, the code was switched over to use
connect-loki.This library doesn't look well-maintained and the following issues need addressing:
session-file-storedid this too and needed cleanup code to clear the reapInterval timer. Suspect LokiJS persistence adapter is keeping things alive now, becauseconnect-lokinever closes it. See LokiJS docs (findcloseon the page).Need to either find another persistence solution, or address the above issues in
connect-loki.