I am getting a throws error from fs.js when i run the following command:
mongration -f "./mongration/migrations" -c "./mongration/config/config.js"
The following is the error given.
fs.js:114
throw err;
^
Error: EISDIR: illegal operation on a directory, read
at Object.readSync (fs.js:498:3)
at tryReadSync (fs.js:332:20)
at Object.readFileSync (fs.js:369:19)
at StepFile.read (C:\MYPATH\npm\node_modules\mongration\src\steps\step-file-reader.js:19:23) at Migration. (C:\MYPATH\npm\node_modules\mongration\src\migration.js:126:46)
at Array.forEach ()
at Migration.migrate (C:\MYPATH\npm\node_modules\mongration\src\migration.js:125:25)
at Object. (C:\MYPATH\npm\node_modules\mongration\bin\mongration.js:60:11)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10
Am I needing to reconfigure the path supplied?
**I noticed earlier in testing that when I ran the command and it worked(somewhat) it created a new db in my instance, not sure if my config was still unsaved or what...
I am getting a throws error from fs.js when i run the following command:
mongration -f "./mongration/migrations" -c "./mongration/config/config.js"
The following is the error given.
fs.js:114
throw err;
^
Error: EISDIR: illegal operation on a directory, read
at Object.readSync (fs.js:498:3)
at tryReadSync (fs.js:332:20)
at Object.readFileSync (fs.js:369:19)
at StepFile.read (C:\MYPATH\npm\node_modules\mongration\src\steps\step-file-reader.js:19:23) at Migration. (C:\MYPATH\npm\node_modules\mongration\src\migration.js:126:46)
at Array.forEach ()
at Migration.migrate (C:\MYPATH\npm\node_modules\mongration\src\migration.js:125:25)
at Object. (C:\MYPATH\npm\node_modules\mongration\bin\mongration.js:60:11)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10
Am I needing to reconfigure the path supplied?
**I noticed earlier in testing that when I ran the command and it worked(somewhat) it created a new db in my instance, not sure if my config was still unsaved or what...