编辑 | blame | 历史 | 原始文档

file-entry-cache - Changelog

v6.0.1

  • Other changes
  • Delete previous mtime when checksum is used and vice versa - abcf0f9, [Milos Djermanovic](https://github.com/Milos Djermanovic), 19/02/2021 18:19:43

  • Adds travis jobs on ppc64le - 92e4d4a, dineshks1, 25/11/2020 04:52:11

    v6.0.0

  • Refactoring
  • Align file-entry-cache with latest eslint - 4c6f1fb, [Roy Riojas](https://github.com/Roy Riojas), 08/11/2020 02:43:09

  • Upgrade deps - 8ab3257, [Roy Riojas](https://github.com/Roy Riojas), 08/11/2020 02:41:53

  • updated packages - 3dd4231, [Roy Riojas](https://github.com/Roy Riojas), 08/11/2020 02:29:37

  • Upgrade flat-cache to version 3 - d7c60ef, [Roy Riojas](https://github.com/Roy Riojas), 08/11/2020 01:18:04

    v5.0.1

  • Bug Fixes
  • Fix missing checksum comparison from reconcile since now we use mtime and size by default. - e858aa9, [Roy Riojas](https://github.com/Roy Riojas), 04/02/2019 09:30:22

    Old mode using checkSum can still be used by passing the useCheckSum parameter to the create or createFromFile methods.

v5.0.0

  • Refactoring
  • Make checksum comparison optional - b0f9ae0, [Roy Riojas](https://github.com/Roy Riojas), 03/02/2019 18:17:39

    To determine if a file has changed we were using the checksum in the newer versions, but eslint was relying on the old behavior where we use the mtime and file size to determine if a file changed. That's why we decided to make the checksum check optional.

    To use it:

    // to make the cache use the checkSum check do the following:
    var fCache = fileEntryCache.create(cacheName, dir, useCheckSum); // pass the third parameter as true
    var otherCache = fileEntryCache.createFromFile(cacheName, useCheckSum); // pass the second parameter as true
    

v4.0.0

  • Build Scripts Changes
  • use the same node versions eslint use - 563cfee, [Roy Riojas](https://github.com/Roy Riojas), 08/01/2019 20:29:34

  • Other changes
  • Remove object-assign dependency. - d0f598e, [Corey Farrell](https://github.com/Corey Farrell), 08/01/2019 20:09:51

    node.js >=4 is required so object-assign is no longer needed, the native
    Object.assign can be used instead.

v3.0.0

v2.0.0