-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
listArchive not working #36
Comments
logging entries seems ok:
prints
|
Not sure why that could be happening on Mac. Have you tried/confirmed on non macOS device? |
Thanks for the quick response, I've tested on MacOS on node's from v14-v20.3.0, and I've just tested on Windows 10 on node 14.16.1 which gives the identical problem. I'll continue to try and poke my way through the code, prob tomorrow eve |
So far, I can't tell you much, but can say:
(and 1.1.6 has the same problem as 1.1.7) |
That means binary not actually available. Not downloaded and extracted there. You might need to delete whole folder tree and do another install. |
https://github.com/TheTechsTech/node-7z-archive/blob/master/src/index.ts#L335 Change: - .progress((data: string) => progress(onprogress(data)))
+ .progress((data) => resolve(onprogress(data)))
why does the result of
Seems like madness: |
You should read all posted issues about my stand on typescript. That is part of it's introduction by another contributor. Check/run CI tests and submit PR. |
Thanks! I tried to read the posted issues you mention but couldn't find them (are they in node-7z-forall maybe? I'd genuinely be interested if you could point me at the things that happened that make you uncomfortable with the TypeScript code here? Maybe I can offer some help in the future?) This issue just needs closing: I've just fundamentally misunderstood/failed to grok the API that was set at the beginnning of the node-7z project, since when's archive.list('archive.zip'
.progress( files => files ) //allow insertion for progress updates (return is ineffectual)
.then( spec => spec) //reporting outcome: why you might need the file spec If only there was an easy way to invert the Hate to make a bad joke but at least I'm 'making progress' now tho ;-) |
No, you have completely drifted off course. You say, you read issues, still confuse, and think you can help me with typescript. Lol, that's funny! Which one you did see not #23, nor did go thru PR, https://github.com/TheTechsTech/node-7z-archive/pull/12/files#diff-a2a171449d862fe29692ce031981047d7ab755ae7f84c707aef80701b3ea0c80R74 where typescript was added? Your solution is just going back to the original https://github.com/TheTechsTech/node-7z-archive/pull/12/files#diff-92bbac9a308cd5fcf9db165841f2d90ce981baddcb2b1e26cfff170929af3bd1 I can go on a rant about peoples adherence to somebody else project code expectation usage. Ideas won't evolve, there will be no progress, nothing. So I am going to figure you just brand new to coding. I have spelled out in some issues that, "I don't actually use JavaScript like when I started the project". Any real changes will come from others PR's. |
I had seen #23, and in it your comments regarding others' contribution of the TS code, hence me asking you for more info. I hadn't looked through #12 - thanks for the link! I had already appreciated that you don't use JS anymore and only PRs from others will change the project I wasn't suggesting any solution, just looking to use this module in a project and I'd misread the (somewhat surprising!) API...I shouldn't have opened this issue, the real issue is that the API will likely need changing in the future, and I was mulling on how else to achieve the 2-stage async with-progress the current API provides (as |
MacOS 10.15.7, node tested from v14-v20.3.0
prints (only)
expected result would be a list of files in the archive (i.e.: the filenames from the tail of example command-line p7zip output):
The text was updated successfully, but these errors were encountered: