cookie.js | Cookie Manipulation API | Runtime Evironment library

It's not clear which module your initializeMaps() function is defined in, but that particular Google API requires that it be a global symbol so Google can find it when that script executes. And, it will have to be defined before the Google script executes too.

With ES6 modules, nothing in the script is automatically defined as globally available. So, unlike the older script files, top level variables in your script only have module scope and are not available globally. This is an important change with ES6 modules. You have to either export a symbol to make it available to other scripts or you have to explicitly make it global by assigning it to the window object (in the browser) like this:

You have 2 copies of jQuery in your page. This can cause errors, conflicts and other unexpected behaviour, especially if they are not the same version of jQuery. And even if it didn't, it's inefficient and unnecessary.

I suggest removing the second one (vendor/jquery/jquery.min.js).

Welcome to so. tablesorter() by default works only for static table content. All dynamically added tr's must be added into the tablesorter by addRows() method, so your function formatPlayerList() should be changed as follows:

Maybe it helps you::

It's not the issue with yours web.config, but Google Analytics (GA) server's. So you have to adjust requests to meet GA requirements.

1. GA responses do not want to be cached (underlined in green). All transfer of statistics is done in the send request, the answer is only confirmation of delivery (the text like 1gfr).

2. GA do not accept requests with credentials (underlined in red) because of:
   - presents of wildcard * in Access-Control-Allow-Origin response header
   - absent of Access-Control-Allow-Credentials: true in responce header

Hence GA wait cross-origin requests with no credentials (no auth cookies should not be sent). The feth() uses mode: 'cors', credentials: 'same-origin' by default (send credentials only to same-origin requests), therefore all should be OK.

But if you still have got CORS error above, it means some browsers send credentials. Try to set Request.credentials to "omit" as recommended by Mozilla.

Or may be it's possible to exclude GA from caching and let process GA requests native way (GA natively use XMLHttpRequest with withCredentials = false option, not fetch()).

This loads jQuery (an ancient, unsupported version of jQuery with known security problems in it, but jQuery none the less):

You are trying to access instance property statically. You need to create an instance of App class before trying to access cookieStore property. You can create an instance and export it in your app.js to have singleton instance.

If you want to use the session inside of the cookieMiddleware(), then you have to move the session middleware to be BEFORE cookieMiddleware() is called. Right now, you have the session middleware after so req.session has not yet been configured when cookieMiddleware() gets called.

Middleware is run in the order it is registered so to use req.session, the session middleware has to have already run before the middleware where you're trying to use req.session. So, you can either move cookieMiddleware() to be later (after session middleware) or move your session middleware earlier before cookieMiddleware() is called.

Firstly, note that your use of $(this) in the get() method of the cookie is incorrect. You need to use the index of the .bookmark element which can be retrieved through the first argument provided to each().