fix: truncate to larger size

[toyobayashi]

No description provided.

[G-Rath]

Could you give a bit more a context about this change? why is it a problem, how did you discover it, what does Node do? etc

[toyobayashi]

@G-Rath

const fs = require('fs')

const fd = fs.openSync('./test', 'w');
fs.writeFileSync(fd, '12345');
console.log(fs.readFileSync('./test', 'utf8') === '12345');
fs.truncateSync('./test', 10);
console.log(fs.readFileSync('./test', 'utf8') === '12345\0\0\0\0\0');

According to https://nodejs.org/dist/latest-v18.x/docs/api/fs.html#fsftruncatefd-len-callback

If the file previously was shorter than len bytes, it is extended, and the extended part is filled with null bytes ('\0'):

[toyobayashi]

I'm using memfs in browser, before this change, ftruncateSync just throws RangeError if truncate to a larger size

[streamich]

🎉 This PR is included in version 3.4.8 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀