CreateComponent failing with mkdir
Closed this issue · 5 comments
hesselberg commented
I cannot seem to get the createComponent
command to work.
It appears to be failing at creating a folder.
Getting the result of const joined = dirPath.slice(0, index + 1).join('/');
produces an empty result.
fs.js:114
throw err;
^
Error: ENOENT: no such file or directory, mkdir
at Object.mkdirSync (fs.js:757:3)
at dirPath.forEach (/Users/larshesselberg/Work/NovicellUK/Customers/BMA/bma.frontend/config/createComponent/index.js:153:10)
at Array.forEach (<anonymous>)
at checkAndCreateDestinationPath (/Users/larshesselberg/Work/NovicellUK/Customers/BMA/bma.frontend/config/createComponent/index.js:150:11)
at createDir (/Users/larshesselberg/Work/NovicellUK/Customers/BMA/bma.frontend/config/createComponent/index.js:143:5)
at createAtom (/Users/larshesselberg/Work/NovicellUK/Customers/BMA/bma.frontend/config/createComponent/index.js:178:3)
at Object.<anonymous> (/Users/larshesselberg/Work/NovicellUK/Customers/BMA/bma.frontend/config/createComponent/index.js:221:5)
at Module._compile (internal/modules/cjs/loader.js:776:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
at Module.load (internal/modules/cjs/loader.js:653:32)```
ankeris commented
@hesselberg, Hi, thanks for informing. Can you give any details about what OS are you experiencing this on? And also what terminal are you using? Nodejs version?
hesselberg commented
I’m on Mac OSX High Sierra. Happening on both terminal and iTerm2.
hesselberg commented
Sorry I lied - I'm on Mojave, the newest one
Bjornnyborg commented
I've tested on a Mojave machine (node v.12.7), and it seems to work just fine. :)
Did commit #301 maybe fix it? And did you remember to run "npm link" in root dir, of your project?
hesselberg commented
@Bjornnyborg it worked with #301 -- I think this was never closed as a part of fixing it :-)