Bump memfs to 3.4.2

[ivanbacher]

Bug report

installed node v18.2.0

Dev server randomly dies with the following error message:

node:events:505
      throw er; // Unhandled 'error' event
      ^

TypeError: Cannot set property closed of #<Readable> which has only a getter
    at FsReadStream.close (/Users/.../node_modules/memfs/lib/volume.js:2047:17)
    at FsReadStream._destroy (/Users/.../node_modules/memfs/lib/volume.js:2032:10)
    at _destroy (node:internal/streams/destroy:109:10)
    at class_1.destroy (node:internal/streams/destroy:71:5)
    at class_1.<anonymous> (/Users/.../node_modules/memfs/lib/volume.js:1962:22)
    at class_1.emit (node:events:539:35)
    at endReadableNT (node:internal/streams/readable:1344:12)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at process.processImmediate (node:internal/timers:442:9)
Emitted 'error' event on class_1 instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at emitErrorCloseNT (node:internal/streams/destroy:116:3)
    at processTicksAndRejections (node:internal/process/task_queues:82:21)
    at runNextTicks (node:internal/process/task_queues:64:3)
    at process.processImmediate (node:internal/timers:442:9)

Node.js v18.2.0

Found this issue on memfs library:

🎉 This issue has been resolved in version 3.4.2 🎉

Actual Behavior

Expected Behavior

How Do We Reproduce?

Please paste the results of npx webpack-cli info here, and mention other relevant information

[alexander-akait]

Yep, known issue, described here #1260, looks like we have a patch, so I will do release today

[ivanbacher]

Sorry didn't see that.

Awesome. Thank you.

[alexander-akait]

Fixed #1260, WIP on release