Closed deployable closed 6 years ago
Some fs errors have a path property on the error, which is missing when mock-fs throws
fs
path
mock-fs
> try { fs.readdirSync('/asdf') } catch (e) { console.log(e.path) } /asdf > require('mock-fs')() > try { fs.readdirSync('/asdf') } catch (e) { console.log(e.path) } undefined
syscall is missing too but I guess that is a bit harder to take a guess at
syscall
Some
fs
errors have apath
property on the error, which is missing whenmock-fs
throws