# Changelog
## 3.3.0 (2019-02-24)
- **Feature**
  - Added Request Capturer for [chrome-remote-interface-extra](https://github.com/N0taN3rd/chrome-remote-interface-extra) 
  - Added WARC writer for [chrome-remote-interface-extra](https://github.com/N0taN3rd/chrome-remote-interface-extra) 

## 3.2.0 (2018-12-28)

- **Feature**
  - It is no longer required to include the extension in the name for the WARC file to be created, 
  node-warc will add the correct extension if it is omitted
  - The default WARC file option can now be supplied as the only argument to the constructor of all writers or set via
  `setDefaultOpts` 
  - Added to all writers the ability to write a Webrecorder Player compatible bookmark list (as WARC info record) via
    `WARCWriterBase.writeWebrecorderBookmarksInfoRecord` and the `pages` property of the `genOpts` object supplied 
    to `generateWARC`
- **Breaking Change**
    - Creation of the WARC Info record using `writeWarcInfoRecord` or via `generateWARC`'s genOpts winfo property now accepts an object, Buffer, or string. 
    If info records contents is an object, the objects properties (property, property value pairs)
    are written otherwise (when Buffer or string) the content is written as is. 
    - If the supplied filename for the WARC to be written is null, undefined, or not a string an error is thrown
- **CDP Based Changes**
    - The request body (if a request had one) is no longer base64 encoded when requested via `Network.getRequestPostData`.
      Accordingly WARC writers treat the return value of this method as **UTF-8 strings** rather than base64 when creating
      the buffer.  ([TOT](https://chromedevtools.github.io/devtools-protocol/tot/Network#method-getRequestPostData), [Stable](https://chromedevtools.github.io/devtools-protocol/1-3/Network#method-getRequestPostData))

## 3.1.0 (2018-11-25)

- **Feature**
  - WARC parsing via a transform stream 
  - WARC parsing via async iteration (Node v10+)
  - WARC generator for the request library  ([@hyl](https://github.com/hyl), [#15](https://github.com/N0taN3rd/node-warc/pull/15)) 
  - Gzipped WARC generation for all WARC generators ([@hyl](https://github.com/hyl), [#13](https://github.com/N0taN3rd/node-warc/pull/13)) 
  - Puppeteer request capturer and WARC generator
  - Puppeteer CDP session request capturer and WARC generator
  - Added additional method to WARC generators to streamline WARC creation
  - Added additional convince methods to `WARCWriterBase` for record generation
  - Ability to add `WARC-Warcinfo-Id` to records that field is allowed on ([@BubuAnabelas](https://github.com/BubuAnabelas), [#7](https://github.com/N0taN3rd/node-warc/pull/7)) 
  - Added typescript definition file ([@hyl](https://github.com/hyl), [#13](https://github.com/N0taN3rd/node-warc/pull/13))
- **Fixes**
  - WARCs generated by node-warc are no longer considered invalid by openwayback/jwat-tools
  - `WARC-Concurrent-To` field is no longer missing on records it is expected to exist on ([@BubuAnabelas](https://github.com/BubuAnabelas), [#21](https://github.com/N0taN3rd/node-warc/pull/21))
- **Breaking Changes**
  - The default export is no longer `AutoWARCParser` but an object containing all primary classes provided by node-warc
  - WARC parsing has been completely reworked:
    - `node-warc/lib/warcRecordBuilder` has been removed
    - `node-warc/lib/warcRecords` has been renamed to `node-warc/lib/warcRecord`
    - Removed all WARC record type specific classes in favor of a generic WARC record class (`node-warc/lib/warcRecord/record`)
    - Consolidated and generified WARC record building (`node-warc/lib/warcRecord/builder`)
  - Request capturers no longer accept a `navMan` ([Squidwarc](https://github.com/N0taN3rd/Squidwarc) remnant)