Files
react-native-devtools-frontend/node_modules/file-entry-cache/changelog.md
T
Tim van der Lippe 0a9b84dbd8 Update NPM dependencies
Major updates to Puppeteer (Chromium roll and updates to types:
https://github.com/puppeteer/puppeteer/blob/0b5969dea9048dc34a4d2e109e96c42e8928182c/CHANGELOG.md#800-2021-02-26) and Sinon (unaffected by browser support changes).

DISABLE_THIRD_PARTY_CHECK=NPM updates
R=jacktfranklin@chromium.org

Fixed: 1176642
Change-Id: I419300fc573e8086b4a7b3b6281c81602890f8d0
Reviewed-on: https://chromium-review.googlesource.com/c/devtools/devtools-frontend/+/2782553
Commit-Queue: Tim van der Lippe <tvanderlippe@chromium.org>
Auto-Submit: Tim van der Lippe <tvanderlippe@chromium.org>
Reviewed-by: Jack Franklin <jacktfranklin@chromium.org>
2021-03-24 13:47:34 +00:00

8.4 KiB

file-entry-cache - Changelog

v6.0.1

v6.0.0

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

  • 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

v1.3.1

v1.3.0

v1.2.4

  • Enhancements

v1.2.3

  • Build Scripts Changes

v1.2.2

  • Build Scripts Changes
    • Add changelogx section to package.json - a3916ff, royriojas, 11/09/2015 16:00:26

v1.2.1

  • Build Scripts Changes

  • Other changes

    • Update dependencies Replaced lodash.assign with smaller object-assign Fixed tests for windows - 0ad3000, [Bogdan Chadkin](https://github.com/Bogdan Chadkin), 11/09/2015 15:44:18

v1.2.0

  • Features
    • analyzeFiles now returns also the files that were removed - 6ac2431, royriojas, 04/09/2015 12:40:53

v1.1.1

v1.1.0