Skip to content

Releases: sindresorhus/decompress-response

v9.0.0

28 May 21:43
Compare
Choose a tag to compare

Breaking

Fixes

  • Fix it incorrectly modifying the original response 8e713c3

v8.1.0...v9.0.0

v8.1.0

23 Feb 16:52
Compare
Choose a tag to compare

v8.0.0...v8.1.0

v8.0.0

27 Oct 10:55
Compare
Choose a tag to compare

Breaking

Fixes

  • Preserve content-encoding header if the respose is passed through b35646b

v7.0.0...v8.0.0

v7.0.0

12 Feb 10:21
Compare
Choose a tag to compare

Breaking

  • Remove content-encoding header (#30) 9355974
    It should only be a breaking change for TypeScript users since the return type changed.

v6.0.0...v7.0.0

v6.0.0

15 May 03:09
Compare
Choose a tag to compare
  • Node.js compatibility fixes (#27) c17015d
    This is a major release just to be safe. It should in theory not be breaking.

v5.0.0...v6.0.0

v5.0.0

01 Nov 13:55
Compare
Choose a tag to compare

Breaking

  • Require Node.js 10 cad4054
    This is so that we can use stream.pipeline for more reliable stream handling. Node.js 8 will exit LTS in a month anyway.
  • Only use a CommonJS export for the TypeScript definition
    You need to change import decompressResponse from 'decompress-response'; to import decompressResponse = require('decompress-response');

v4.2.1...v5.0.0

v4.2.1

12 Aug 21:44
Compare
Choose a tag to compare
  • Case-insensitively check the content-encoding header (#21) 01397b5

v4.2.0...v4.2.1

v4.2.0

31 Mar 11:47
Compare
Choose a tag to compare
  • Refactor TypeScript definition to CommonJS compatible export (#17) 03c09de

v4.1.0...v4.2.0

v4.1.0

11 Mar 06:55
Compare
Choose a tag to compare

v4.0.0...v4.1.0

v4.0.0

20 Jan 10:52
Compare
Choose a tag to compare

Breaking:

Other: