memfs breaks with fs-extra^10.0.0

memfs does not export fs.realpath.native. It is available since Node.js 9.2.0. https://nodejs.org/api/fs.html#fsrealpathnativepath-options-callback

fs-extra uses univeralify to create a promise version of fs.realpath.native. Because memfs does not provide it, universalify throws a error:

TypeError: Cannot read properties of undefined (reading 'name')

      at Object.<anonymous>.exports.fromCallback (../../node_modules/fs-extra/node_modules/universalify/index.js:15:26)
      at Object.<anonymous> (../../node_modules/fs-extra/lib/fs/index.js:57:27)
      at Object.<anonymous> (../../node_modules/fs-extra/lib/index.js:5:6)

The error occurs even if realpath.native is not used.

The line of code: https://github.com/jprichardson/node-fs-extra/blob/a84ef6dd8969f57d16e23267e1790def791e9a82/lib/fs/index.js#L57

[Phillip9587]

@peteriman I’m gonna look into it on monday. Hope it was no wrong report from my side.

[lamweili]

@G-Rath, assuming it’s not a NodeJS <9.2.0 issue, I am unable to replicate it using NodeJS 14 with memfs@^3.4.1.

const assert = require('assert');
const memfs = require('memfs'); // memfs@^3.4.1

assert(typeof fs.realpath.native === 'function'); // is fine, not undefined

const fse = require('fs-extra'); // fs-extra@^10.0.1 - is fine, no errors as claimed

Might need more details from @Phillip9587. It is also possible to be an inherent nx behaviour that altered fs but reported wrongly as https://github.com/nrwl/nx/pull/8531.