v5.0.0

This version introduces new typings for HttpClient and HttpClientConfig that make them easier to use without leaning on any, and which offer easier compatibility with fetch. You may have to make changes to your code as a result, especially if you were directly using HttpClient as the params argument now requires its values to be string.

4.2.1

• Marked DestinyInventoryItemDefinition#itemCategoryHashes as nullable.

NodeJS-compatible modules

In the previous release I thought I was switching to ES modules in a compatible way, but I didn't know exactly how NodeJS wanted it. After much experimentation and help from @sundevour, this release should be compatible with newer Nodes (13.2+), through their native ES module support.

Furthermore, there are now some extra helpers in the destiny2 module for dealing with the manifest database - downloading it (whole or in parts) and accessing typed subsets.

ES Modules and enums

Two major changes - one, this package is published as ES modules now, instead of CommonJS. Second, the enums are published in the generated JavaScript as plain objects, meaning this library still works if you're using Babel or other TS build types that don't play well with const enum.

Data properties are optional

This is a major (breaking) release that makes the data parameter from Component responses optional, since the API can omit the response either because of privacy settings or during maintenance. You should update your code to handle the fact that this can be undefined.

1.0.2

First working version