-
Notifications
You must be signed in to change notification settings - Fork 16
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
Failed to fetch unrar.wasm #37
Comments
@honeo I cannot reproduce in on node v18.3.0, can you create a sample project and shared on github? |
I have created a repository to reproduce the problem, please check it. Also, the fact that the unrar.js code is displayed in the console when an error occurs was inconvenient because other logs were flowing during the verification. |
@honeo I've pushed a new version v2.0.0 to enable the support of node v18, please install the v2.0.0 and try again. for(let {fileHeader, extraction} of files){
fileHeader.flags.directory ?
await fsp.mkdir(fileHeader.name):
await fsp.writeFile(fileHeader.name, extraction);
} Because in RAR archive, the files are placed at begging and folders are on the end. You may change it to |
Thanks for the fix, now we can update Node.js! That code is just a SAMPLE and as I mentioned in the comments, it doesn't work. |
Confirmed on Windows 10, Ubuntu 22.04.
Since Node.js v18.1.0 I get the following error.
The text was updated successfully, but these errors were encountered: