When a file is changed in a memfs volume, its ctime does not update.

[thomasperi]

mtime and atime both seem to behave as expected, but ctime does not.

Seems like it could be related to #891 and #889

Here's a test I wrote that fails when using a memfs volume but passes when using the real 'fs':

const fs = require('fs');
const path = require('path');
const assert = require('assert');
const { Volume } = require('memfs');

describe('memfs ctime', async () => {

  it('should change ctime', async () => {
    const vol = new Volume();
    
    const _fs_ = vol; // test fails
    // const _fs_ = fs; // test passes
    
    const file = '/tmp/test-memfs-ctime.txt';
    
    // Wait 1ms between actions to be sure the times change.
    const sleep = () => new Promise(resolve => setTimeout(resolve, 1));

    // Create the file if it doesn't exist.
    _fs_.mkdirSync(path.dirname(file), {recursive: true});
    _fs_.closeSync(_fs_.openSync(file, 'a'));
    
    // Get the ctime before any changes.
    let initial = _fs_.statSync(file).ctimeMs;
    
    // Get the ctime after writing to the file.
    await sleep();
    _fs_.writeFileSync(file, 'testing memfs ctime', 'utf8');
    let afterWrite = _fs_.statSync(file).ctimeMs;

    // Get the ctime after changing the file's atime and mtime.
    await sleep();
    let oneSecondAgo = new Date(Date.now() - 1000);
    _fs_.utimesSync(file, oneSecondAgo, oneSecondAgo);
    let afterMtimeChange = _fs_.statSync(file).ctimeMs;
    
    assert(afterWrite > initial, 'ctime should be greater after write than before');
    assert(afterMtimeChange > afterWrite, 'ctime should be greater after utimes change than before');
  });

});

[G-Rath]

Would you mind seeing if your test passes with the changes from #891?

[thomasperi]

Indeed it does!

[streamich]

🎉 This issue has been resolved in version 3.5.1 🎉

The release is available on:

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

Your semantic-release bot 📦🚀