-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
Error in build.js/copystatic() ENOENT: no such file or directory, open '.../nodejs.org/build/static/event-geo.json'
#383
Conversation
Strange, not able to reproduce this issue on my machine. What's your OS/version? |
If this was a problem then there might be some issue in the core. |
I'm on linux mint debian edition v2. |
Agreed, which probably should be reported. I wouldn't mind replacing two levels of callbacks with sync here, as it's simpler to grasp and doesn't really matter for performance reasons as @justsml mentioned. Trying to build with these changes results in an error for me though... $ npm start
> nodejs.org@1.0.0 start /nodejs.org
> npm run serve
> nodejs.org@1.0.0 serve /nodejs.org
> node build.js serve
fs.js:842
return binding.mkdir(pathModule._makeLong(path),
^
Error: EEXIST: file already exists, mkdir '/nodejs.org/build'
at Error (native)
at Object.fs.mkdirSync (fs.js:842:18)
at copystatic (/nodejs.org/build.js:175:6)
... |
The problem here is not sync or performance. It's why it fails. |
I've started using metalsmith, and got this same error. No idea why it worked, but deleting the existing |
could you re-target to master now that the branch is merged |
I pushed a hotfix for this just pushing the geo create to before the timer end. |
After I switched to nodejs v5.0, running a clean build no longer worked.
It doesn't seem to be creating the directories before the
fs.mkdir
callback(s)??It's a build script, so hopefully a synchronous fix isn't the worst...