dataloader
2.2.3 · 3 Dec 2024MIT16.1M / weekRepositorynpmAtom feed
Upgrading dataloader from 1.0.0 to 1.4.0
4 releases in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 1
- fix
Release by release
- fixed
Fixed an issue where Flow may complain about the provided batch function's return type.
- fixed
1.1.0 – 1.3.03 releases, nothing new or fixed in the notes
9 other lines we could not sort, mostly version bumps
- 1.4.0
Direct support for using Dataloader in a browser
- 1.4.0
The integrity of custom provided Cache Maps are now checked during construction.
- 1.4.0
Flow type no longer complains when using
require("dataloader") - 1.4.0
Flow types from public API are now directly exported
- 1.3.0
Thanks to contributions from many, the documentation for DataLoader is now significantly better, with portions of
README.mdreworked and improved and more information inexamples/. - 1.3.0
DataLoader installs now come with both TypeScript and Flow type definitions. (#43, #45)
- 1.3.0
Batch loads can now be limited to a certain number of keys
- 1.1.0
Provide a custom cache-key function. #15 — Since JavaScript does not use value equality, but fetch keys are often treated as values, this allows for a custom function to be provided to produce a cache-key for any load-key. Example:
- 1.1.0
Provide a custom cache instance. #17 — By default, DataLoader uses a Map as a cache. However this simple cache does not support anything like TTL or a cache eviction policy. Now you may provide any object which implements the Map API to use as a cache. Example: