Now for the tricky-ish part. Remember, we want to learn how to add a single file what we just accomplished above as well as how to add a directory. Here, we've introduced a call to a new function addFilesFromDirectoryToZip passing it the directoryPath argument we mentioned earlier along with our zip instance our incomplete zip archive.
Focusing in on that function, we can see that it takes in the two arguments we expect: directoryPath and zip. Just inside the function body, we call to fs. Next, anticipating directoryContents to contain an array of one or more files returned as objects with a name property representing the file name currently being looped over , we use a. With that name property, we construct the path to the file, concatenating the directoryPath we passed in to addFilesFromDirectoryToZip and name.
Using this next, we perform the first of two checks to see if the path we're currently looping over is a file. If it is, we add that file to our zip, just like we saw earlier with zip. This time, though, we pass in the path as the file name JSZip will automatically create any nested directory structures when we do this and then we use fs.
Again, we're saying "at this path in the zip file as it exists in memory, populate it with the contents of the file we're reading. Next, we perform our second check to see if the file we're currently looping over is not a file, but a directory.
If it is, we recursively call addFilesFromDirectoryToZip , passing in the path we generated and our exsting zip instance. This may be confusing. Recursion is a programming concept that essentially describes code that "does something until it can't do anything else. Here, because we're traversing directories, we're saying "if the file you're looping over is a file, add it to our zip and move on.
But, if the file you're looping over is a directory, call this function again, passing in the current path as the starting point and then loop over that directory's files, adding each to the zip at its specified path.
Because we're using the sync version of fs. Touffy Touffy 5, 21 21 silver badges 27 27 bronze badges. But client-zip do not compress the data — Vagner Gon. That's not necessarily a bad thing. Indeed, many browsers automatically unzip downloaded archives, so compression would only increase CPU load for compression, and then again decompression for no bandwidth or storage savings at all.
The main reason for zipping here seems to be to achieve a one-click download of multiple attachments. Didn't say that is a bad thing. But you mentioned 'exactly this problem' that may sound that it should do the same stuff as JSZip.
Client-zip seems awesome to do what it propouses. All right. To be clear : I do not claim client-zip solves the same group of problems as JSZip, just the one in this question.
Show 1 more comment. Sangeetharaj Sangeetharaj 1 1 silver badge 8 8 bronze badges. It's a pretty bad idea to generate the output in Base64, and even a worse idea to use a Data URI like that. A waste of memory and CPU. Use a blob URL instead. Excellent, I changed the type to 'blob' and it worked like a charm! I used an anchor link on the page to trigger the download instead of changing the page url. Reasons being: Zlib is a Node native library - has been kept up-to-date for nearly 10 years now - so the proofs there for long-term supports Node allows you work with Buffers - i.
Example: input. Tran A. Tran 3 3 silver badges 12 12 bronze badges. Thanks for sharing. However, I guess the question sought a browser-side solution rather than a server-side's. Any idea on the browser-side? Instead of generating zip file and transfer it from your server, why not download data and zip them in your browsers? This is a guest posting by Mr. Ngo Viet Khanh Huy. To submit your articles for guest postings, please email to [email protected].
For each request, our backend will generate a report, upload it to Amazon S3 storage, and return its URL to the client. Since generating a report takes a while, the output files are stored and the server caches their URLs by request params. Instead of individual files, I needed to download a zip file containing hundreds of reports.
The first solution came into my mind is:. The final solution I came up with is: download all the files to the browser and zip them there. Before applying new solutions, my system allows downloading a single report file. There are many ways to do that. I choose the 2nd approach since I want to cache all the generated files. The browser will do the rest to download the file.
When it comes to download and zip multiple files, we cannot use the simple method above anymore. Another way to handle this is by using fetch to download files and store data as Blob in memory.
We can then write it to file or combine those blob data into a zip file. This function returns a promise to be resolved as a blob. We can combine with a Promise. But what happens if we need to download a huge amount of files at once? Using Promise. Your code will send a thousand requests at once.
There are many problems with that approach:. The solution I thought about is to divide the files into multiple groups. Instead of starting to download them all at once by Promise.
After finishing those 5, I will start another pack. To implement this, we can do a custom logic. Or a simpler way I could suggest is to utilize third-party library bluebirdjs. Thanks for the source code, I am using SP I managed to creat a blank SP project and imported your code, now I am getting different errors now.
July 22, at pm. I managed to deploy it SP13 and applied some changes, due to the display image functions is for Office as below, what is equvelent function for SharePoint ? Many thanks. July 23, at am. You are commenting using your WordPress. You are commenting using your Google account. You are commenting using your Twitter account.
You are commenting using your Facebook account. Notify me of new comments via email. Notify me of new posts via email. Blog at WordPress. Search for:.
0コメント