limeline | A minimalist statusbar tool for tmux | Command Line Interface library

One possible cause for the "hanging" request could be that the callback in the activateUser function is not being called. Make sure you always call the given callback function, i.e. on success and error.

One advice: use promises/async await as it helps you to keep your code cleaner and prevent errors like these.

localStorage is shared across all tabs for the given domain. If you do not want this to be the case, you can use sessionStorage instead. However, as a side effect of using sessionStorage, the data will be destroyed when the window/tag it is associated with closes.

https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage

The read-only localStorage property allows you to access a Storage object for the Document's origin; the stored data is saved across browser sessions. localStorage is similar to sessionStorage, except that while data stored in localStorage has no expiration time, data stored in sessionStorage gets cleared when the page session ends — that is, when the page is closed.

https://developer.mozilla.org/en-US/docs/Web/API/Window/sessionStorage

The sessionStorage property allows you to access a session Storage object for the current origin. sessionStorage is similar to Window.localStorage; the only difference is while data stored in localStorage has no expiration set, data stored in sessionStorage gets cleared when the page session ends. A page session lasts for as long as the browser is open and survives over page reloads and restores. Opening a page in a new tab or window will cause a new session to be initiated, which differs from how session cookies work.

You should avoid using relative urls in templates which will be served from different routes. In this case same html is getting served from http:///LimeLINE as well as http:///LimeLINE/activate/:token. The relative url of ../css/main.css will point to different locations in those two cases. Since the browser doesn't know about the directory structure on your server, it simply constructs the path relative to current url (in address bar).

For the first case it becomes http://hostname/../css/main.css which is same as http://hostname/css/main.css;

And in second case it is http:///LimeLINE/activate/../css/main.css which is same as http:///LimeLINE/css/main.css.

Just change to absolute urls (or relative to host urls, starting with /) and your code will work fine. Instead of href="../css/main.css" use href="/css/main.css"