MyCrypto: Windows Build Errors

Error: no such file or directory
    at MemoryFileSystem.readFileSync (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\memory-fs\lib\MemoryFileSystem.js:107:10)
    at devMiddleWare.waitUntilValid (C:\Users\user\Desktop\MyEtherWallet-develop\webpack_config\server.js:59:22)
    at ready (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\webpack-dev-middleware\lib\util.js:38:12)
    at Function.waitUntilValid (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\webpack-dev-middleware\index.js:93:7)
    at app.get (C:\Users\user\Desktop\MyEtherWallet-develop\webpack_config\server.js:58:17)
    at Layer.handle [as handle_request] (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\layer.js:95:5)
    at next (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\route.js:137:13)
    at Route.dispatch (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\route.js:112:3)
    at Layer.handle [as handle_request] (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\layer.js:95:5)
    at C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\index.js:281:22
    at param (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\index.js:354:14)
    at param (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\index.js:365:14)
    at Function.process_params (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\index.js:410:3)
    at next (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\index.js:275:10)
    at middleware (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\webpack-hot-middleware\middleware.js:26:48)
    at Layer.handle [as handle_request] (C:\Users\user\Desktop\MyEtherWallet-develop\node_modules\express\lib\router\layer.js:95:5)

I’m doing a fresh build. Did npm install on windows 10 and then npm run dev, but i’m getting this error. Did I not install one of the requirements?

About this issue

Original URL
State: closed
Created 6 years ago
Comments: 27 (15 by maintainers)

Most upvoted comments

It goes without saying though, if you can find a way to get the build working well in Windows, I’d be happy to test and review any changes that need to happen!

wbobeirne on Jan 9, 2018

Alright, I found some time to run through this, and boy is it a pain in the ass. Took a while to even get the modules to install (Couldn’t find python, couldn’t find node-gyp, etc. etc.)

I figured out a hilarious reason for the main issue. We use a component called Aux to reduce unnecessary nesting, however AUX is a reserved filename in the windows system. So cloning the repo omits the file common/components/ui/Aux.tsx, which blows up the build. I’ll put up a PR that renames this. (EDIT: Pr is #771)

After that, I was still left with the scss errors. We use node-sass, and they have a guide on windows installation. That guide personally didn’t work for me, but someone suggested I run npm rebuild node-sass and that seemed to fix some of them up.

However, after all of that, I still ended up with some errors that I’m still trying to sort out. Windows support is definitely something I’d like to work out long term, but in the short term early stages of this project, I don’t feel I can spend too much time looking into it. Running a VM or the windows ubuntu bash prompt will chop this Gordian knot much faster than I can untangle it.

wbobeirne on Jan 9, 2018

Hey @sulkhanp,

The bulk of the team is on Unix-based operating systems, so sometimes Windows support falls by the wayside. I’ve got a Windows machine at home that I’ll try to run through and see if I get the same issues. FWIW the first error message you posted usually has more logging information in your terminal. It just shows that whenever index.html cannot be output. Until I can get a better look though, my suggestions would be:

Make sure you are on a version of node >= 8.0.0
Try deleting node_modules and reinstalling, in case there’s any weird caching going on

wbobeirne on Jan 9, 2018