jsdf / browserify-incremental

incremental rebuild for browserify
175 stars 13 forks source link

using md5/sha1 for caches instead of / in addition to last modified time? #39

Open xaviergonz opened 7 years ago

xaviergonz commented 7 years ago

The thing is that I use typescript sources that get compiled into new js files with new modified times even though the sources themselves do not change, which means that the incremental build always think they changed even when they actually didn't.

Could there be an option to switch from mtimes to md5/sha1 hashes?

Actually it could even be both for speed reasons: if mtime did not change, file did not change else if hash did not change file did not change and update mtime else file did change and update mtime and hash

xaviergonz commented 7 years ago

Helpful code

export const generateHashEntryAsync = (filePath) => {
  const hash = crypto.createHash('sha1');
  const stream = fs.createReadStream(filePath);

  return new Promise((resolve, reject) => {
    stream.once('error', (err: Error) => {
      reject(err);
    });

    stream.on('data', (data: Buffer) => {
      hash.update(data);
    });

    stream.once('end', () => {
      resolve(hash.digest('base64'));
    });
  });
};