Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More
Socket
Sign inDemoInstall
Socket

fetch-dedupe

Package Overview
Dependencies
Maintainers
1
Versions
12
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

fetch-dedupe - npm Package Versions

2

4.0.0

Diff

Changelog

Source

v4.0.0 (2020/3/19)

Breaking Changes

  • Response caching is now built in, and enabled by default.
  • Project renamed to bestfetch (from fetch-dedupe)
jmeas
published 4.0.0-beta.4 •

jmeas
published 4.0.0-beta.3 •

jmeas
published 4.0.0-beta.2 •

jmeas
published 4.0.0-beta.1 •

jmeas
published 3.0.0 •

Changelog

Source

v3.0.0 (2018/4/12)

Breaking Changes

  • When an attempt to call response[responseType]() errors, then response.data will be set as null. This can be useful if you specify the responseType as json, and the backend returns malformed JSON (such as an empty string or plain text). Instead of this error going uncaught, the fetch will work as expected.
jmeas
published 3.0.0-beta1 •

jmeas
published 2.1.0 •

Changelog

Source

v2.1.0 (2018/2/7)

New Features

  • responseType can now be specified as a function. This is useful for backends that don't respect the Accept header. "Enterprisey" backends frequently return text stack traces for errors, as an example.
jmeas
published 2.0.0 •

Changelog

Source

v2.0.0 (2018/2/4)

Breaking

  • dedupeOptions is now optional. The responseType is "json" by default, unless the status code is 204, in which case it will be "text".
jmeas
published 1.0.0 •

Changelog

Source

v1.0.0 (2018/2/4)

New features

  • init is now optional
  • A requestKey will be generated for you if it is omitted
2
SocketSocket SOC 2 Logo

Product

  • Package Alerts
  • Integrations
  • Docs
  • Pricing
  • FAQ
  • Roadmap
  • Changelog

Packages

npm

Stay in touch

Get open source security insights delivered straight into your inbox.


  • Terms
  • Privacy
  • Security

Made with ⚡️ by Socket Inc