filesaver | Fast parallel file size scanner

For anyone who comes across this question, here is how I resolved it...

On Microsoft Azure in the storage container, I opened the properties for the file I was downloading. I changed the "CONTENT-TYPE" from "application/vnd.ms-excel" to "text/csv".

I used the same "downloadCSV" function in my service.ts and used the following function in my component.ts. The changes are so that the filename is changed to "AGENCIES.csv" instead of the random url key.

So, as I stated in the comment, you have to move jest.mock('file-saver', ()=>({saveAs: jest.fn()})) from the body of the test to the top of the file, just under the imports. The reason for it is actually answered in the documentation here, but to wrap it up:

In your test file you are using import statement which fires up at start, before any code has a chance to run. Then you try to mock file-saver, but it is already imported with real implementation, not mocked. If you instruct jest to mock module at top of the file it will automatically hoist jest.mock calls to the top of the module so your function exportToExcel will receive mocked file-saver instead of the real one.

But if you really want to mock file-saver in the body of the test for some strange reason you would need to mock file-saver, then include all modules in test which use file-saver, something like this:

After some research and a lot of failed tries I came to an answer on how to merge the PDFs in the correct order, and bonus add an image (in my case a signature) on every page of the final PDF.

This is the final code:

If your app works in iOS Safari, but not in iOS Chrome browser, the issue may be how Apple has Chrome configured.

From this reference

Google Chrome is now available for the iPhone and iPad, but before you get too excited, you need to realize that it isn't Chrome at all. It's Apple's Safari with a 'chrome' interface. The actual browser, the rendering, and javascript engine is 100% Apple Safari.

The reason is simple. Apple wants control and force people to create native apps, and are thus limiting the performance of web apps in third party apps. ... This is purely anti-competitor behavior that limits choice and forces people to create native apps.

When I write Progressive Web Apps (PWA), I have to tell my users that they have to use the OS native browser. Android=Chrome, iOS=Safari. Period. No substitutes. Apple clearly doesn’t want universal browser code functionality.

Note: I know that reference above is pretty old. But as far as I know the essence of the facts still stand. Note: I'm coming at this from the perspective of developing Progressive Web Apps. The one feature I really rely on is the ability to "Save link to home page". And that is just not available in Chrome on iOS, even now. Not sure you have exactly the same use case.

It turned out that I needed to convert the content type into "application/vnd.ms-outlook" As it wasn't recognized via Google chrome as .msg

My backend ASP.Net Core Code for mapping MIME Type:

I had the same issue as a lot of other people: https://github.com/eligrey/FileSaver.js/issues/375

What I did was created a function that checked if the user is on iOS/Safari it opened file in new window, so that the user needed to do the additional click in another tab in order to save file:

Looks like you might be able to exclude it in the tsconfig or in the angular.json, maybe try both?

Exclude files from build in Angular 2

In your code snippet change the second line to:

zip.gzip.generateAsync() returns a Promise. This Promise will resolve with a Blob, some times later, but it's a Promise, not a Blob.
So you need to await the resolution of this Promise to access the generated Blob.

You can either mark your function as async and then use the await keyword: