node-unzip | node.js cross-platform unzip using streams | Runtime Evironment library

I guess this is a little unconventional because the icons.scss file isn't supposed to go in the dist/ folder but rather the src/ folder. It doesn't seem impossible to put files in src/ though, and it needs to be there in order for my app.scss to import it.

The problem I'm having is that my generated icons.scss file (which is included by my main entry point for SASS (app.scss)) doesn't have time to generate before SASS is being compiled.

Is there any way of telling webpack to wait until my plugin is finished before going ahead with the build?

To be clear I have everything working relatively well, fonts are downloaded, icons.scss is generated etc, the only problem is that SASS compiles before icons.scss exists. I have no idea which compiler/compilation hook is best to use either, so would love some input on that too.

Please see this excerpt of the code for the relevant parts. I've left comments where I feel like things can improve too:

• specifies deflate compression with
• bit 3 set indicating the length of the compressed data follows the compressed data

and would like to now inflate that data using Node zlib but I cannot figure out how to feed data into zlib and receive feedback telling me when the deflate stream has self terminated.

Does Node's zlib library support consuming chunks of deflate data and returning a result letting the caller know when the deflate stream has ended?

Or is this an insane thing to do because it would imply I'm inflating on the UI thread and what I should really do is save the downloaded file and once downloaded use an NPM package? Hm.. well.. either the network is faster than inflation in which case streaming inflation would slow the network (bummer) or the network is slower than streaming inflation so why deflate while streaming (which I can't figure out how to do anyway) when I could simply saving to disk and reload-deflate while I'm sitting around waiting for the network..

Still, for my edification, I'd still like to know if Node supports streaming inflation.

The zips have a lot of files and folders within them. Extracting stops after a few files have been extracted and it stops with no errors or output.

The problem is not with all the zips, but only a few them.

I'm not a node expert so I don't really know how to debug this issue. Any way of detecting if the stream or pipe failing?

I currently have a Lambda function that streams a file from ftp (using promise-ftp) then pipes it to s3 (using s3-streams). This works just fine.

I've come across an issue where the files are zipped, and I would like to unzip them before I upload them to s3. I've had 0 luck getting any of the unzip utilities (which are all really just node-unzip under the hood) to work with local files. I've had even worse luck piping things through to unzip (at the best, I've made it save files recursively inside directories with the same name on my local machine during testing).

The relevant code I've tried is: