-
-
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
Test the app on windows #3
Comments
nope |
C:\Users\me>mcpd C:\Users\me\AppData\Roaming\npm\node_modules\mcpd\lib\config.js:56 save(defaultConfig).then(({ error }) => { ^ ReferenceError: save is not defined at Object. (C:\Users\me\AppData\Roaming\npm\node_modules\mcpd\lib\config.js:56:3) at Module._compile (internal/modules/cjs/loader.js:1158:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10) at Module.load (internal/modules/cjs/loader.js:1002:32) at Function.Module._load (internal/modules/cjs/loader.js:901:14) at Module.require (internal/modules/cjs/loader.js:1044:19) at require (internal/modules/cjs/helpers.js:77:18) at Object. (C:\Users\me\AppData\Roaming\npm\node_modules\mcpd\lib\utils.js:3:20) at Module._compile (internal/modules/cjs/loader.js:1158:30) at Object.Module._extensions..js (internal/modules/cjs/loader.js:1178:10) |
hmm |
C:\Users\me>node -v |
hmm |
This comment has been minimized.
This comment has been minimized.
@zRattly update mcpd and check now ;) |
trying |
Tryed connecting, crashed my minecraft lol |
For now 1.12.2 is hardcoded ;/ |
oh, tryed joining with 1.8.9 lol |
but there are some errors in gui and console |
{"statusCode":500,"code":"ENOENT","error":"Internal Server Error","message":"ENOENT: no such file or directory, open 'C:\Users\giova\public\index.html'"} this is the web error |
UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, mkdir 'C:\Users\me\AppData\Roaming\mcpd\Config' at Object.mkdirSync (fs.js:840:3) at C:\Users\giova\AppData\Roaming\npm\node_modules\mcpd\lib\config.js:59:12 (node:4568) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag |
@zRattly should've fixed those two errors |
@Ethan-Vann, there's an open PR for that #10 |
@Ethan-Vann, @zRattly any news after #10 has been merged? |
should have tried this before. just switched to arch to test back then. is the npm build outdated? grabbing with npm produces same error but getting from source is working now |
Yup, use the github version |
Now we need to update NPM package and close this issue |
@Saiv46 so you confirm it working? |
Yep. |
@wvffle Fixed package version still not published :/ |
Thanks for reminding me that. Currently I have no spare time for mineflayer related projects. Lots of work and also studies :/ I'll publish it in a minute Edit: already done, @Saiv46 |
Does everything work on windows?
The text was updated successfully, but these errors were encountered: