-
-
Notifications
You must be signed in to change notification settings - Fork 513
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
Mammoth not returning anything [Windows 7, 32-bit node] #29
Comments
Hmm, it is strange that you're not even getting any errors. What happens if:
|
@mwilliamson, 1) When I run it through the CLI I get the following:
No file is created, no error response.
I just installed mammoth@0.3.11 on my Debian machine and completely reinstalled it on my windows one. |
Hmm. Could you try running the tests? In case it's not clear how to do so:
|
@mwilliamson here is the CMD copy of the result from both commands: and here is the screen: http://i.imgur.com/Gjh995s.png I ran http://i.imgur.com/PPHnF7f.png Only these tests fails |
Thanks for running the tests. Strange that the actual failures seem to be missing from the output. I'll try it out myself on a Windows machine when I get a chance, although that might not be until the weekend. My extremely elaborate plan is just to stick in a load of debugging print statements until I discover where in the execution the program seems to stop. |
A few thoughts:
|
I couldn't reproduce when I tried this myself on Windows 7 using 32-bit node, so closing. Feel free to reopen if this is still an issue. |
Hello. I tried installing mammoth, but I didn't succeeded. I tried typing
in a test.js file, but when I run it, it instantly closes and no error or message are returned. I'm sure file exists and it's a valid docx.
OS: NodeJs 32bit on Windows 7
Any ideas, why I cannot run it @mwilliamson?
Thanks.
The text was updated successfully, but these errors were encountered: