offline | Automatically display online/offline indication

Elasticache is just hosted Redis; you don't need anything special for development, just a local copy of Redis (in a container if you'd like).

Yes, for each additional language you want to use in vscode, besides a few built-in ones like Javascript, Typescript, JSON and Markdown, you need to install an extension, which supports that language. Search for the particular language in the extension list in vscode or in the vscode marketplace.

Try to read this document: https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-permissions-and-consent#offline_access.

This permission currently appears on all consent pages, even for flows that don't provide a refresh token (such as the implicit flow). This setup addresses scenarios where a client can begin within the implicit flow and then move to the code flow where a refresh token is expected.

On the Microsoft identity platform (requests made to the v2.0 endpoint), your app must explicitly request the offline_access scope, to receive refresh tokens.

It’s not currently possible to remove the offline_access scope from the initial consent screen when using the v2 endpoint with an AAD account. There is a feedback of this issue here.

Let us go through your code, specifically this block

Try to give the full path

Based on NestJS Websocket documentation, the NestJS socketIO server is still in v2.

@nestjs/platform-socket.io currently depends on socket.io v2.3 and socket.io v3.0 client and server are not backward compatible. However, you can still implement a custom adapter to use socket.io v3.0. Please refer to this issue for further information.

If you check the version compatibility, you will see that socketIO server v2 is not compatible with socketIO client v4.

The easiest solution would be to use socket.io-client v2.3.0 in your package.json of frontend.

Or, if you like to explore: socketIO server v3 is compatible with socketIO client v4. So I believe you can take a look into this issue (as mentioned in NestJS docs) and try to convert your NestJS socketIO server to support socketIO client v3. Hopefully, that would also support socketIO client v4 as well. (I didn't test this though!)

Hope this helps you. Cheers 🍻 !!!

I had to read your question 4 times to understand it. Anyways, the Discord Docs say that you can access the current loop value (as an index, the first loop is 0, the second 1, the 10th loop is 9 etc.)

You can use it like this:

You could directly initialise the value of modelLiveData as:

So apparently my issue didn't have anything to do with my IIS configuration. I still can't explain why it worked on http-server, but now I got it working on IIS, too.

After a lot of research and unsuccessful experiments, I tried to observe, what exactly ngsw-worker.js does that leads to this error. After putting some breakpoints and finding new keywords to search for I stumbled across this GitHub issue which led me to this much discussed issue. In one of his comments the user jackkoppa mentioned his StackOverflow Question where he found a workaround to fix such an issue.

Basically, I just added his script to our project and added the command for it to our project.json.

Here are the steps he describes:

To use the workaround: (Angular 5, tested w/ Angular 5.2.1)

1. npm install replace-in-file --save-dev
2. Include this script in your app, e.g. at build/fix-sw.js
3. In your package.json: