localForage | Wraps IndexedDB | Storage library

Well... we remove the await keyword from this line

You can access these functions inside Sidebar component by passing them as props

I do believe that working code will looks like this (pay attention to the new Promise :

You can use ngModel with tow-way binding, to save and manipulate search filters:

One thing that is (probably) incorrect is the window reference.

Cypress runs the browser window as an automation "shell", which is what you get when you use

The IndexedDB can be manipulated easily from Cypress by using localforage package. I'm using it to set things like the access_token inside the IndexedDB. Example:

@D-Money pointed me in the right direction. So basically axios-cache-adapter v3 fixes the issue of not caching requests with responseType blob or arraybuffers, however it's currently only available in beta so you'll have to install that as follows in the interim:

npm install axios-cache-adapter@beta

Then you'll have to make a slight adjustment by setting readHeaders: false, in the axios-cache-adapter options in setup and additionally move the axios default config directly into setup, which in my case results in the following net changes:

This is intentional. Your decision as to whether or not to call event.respondWith() needs to be done synchronously, within the top-level execution of your fetch handler.

This allows you to do things like examine the request URL and headers synchronously, but it does preclude you from performing asynchronous lookups against things like IndexedDB.

If you can't transition your criteria to use something synchronous, then your best option is to call event.respondWith() unconditionally, and when the criteria is not met, use return fetch(event.request) to come as close as you could to the "default" behavior you'd get if you didn't respond at all. (That's basically what you're doing in the second example.)

As @Mir entafaz Ali already answered as comment, you have to import the module, to be able to use the component. For what I can see in your code, you're using a routing module. Meaning that you're lazy loading the pages. What you should do.

In the app-routing.module.ts you should be loading the tabs. like follow