Change Details

Now that the monorepo does not use NNG chronik-client anywhere (and the use of ChronikClientNode has also been deprecated in the monorepo), publish in-node-only chronik-client as 0.30.0 This is a breaking change for existing users. Aliasing ChronikClientNode and all types was considered, however there is no clean way to deprecate this as users with old types will always be forced to update them unless dozens of aliases are maintained here indefinitely. Given the present low download count of the module, judged better impact to drop all legacy names and types now. Decision to minor version bump despite breaking change is also due to relatively early stage of lib development, see discussion in diff in-line comments.

Now that the monorepo does not use NNG chronik-client anywhere (and the use of ChronikClientNode has also been deprecated in the monorepo), publish in-node-only chronik-client as 1.0.0 This is a breaking change for existing users. Aliasing ChronikClientNode and all types was considered, however there is no clean way to deprecate this as users with old types will always be forced to update them unless dozens of aliases are maintained here indefinitely. Given the present low download count of the module, judged better impact to drop all legacy names and types now. Going forward, breaking changes will have major version bumps.

Now that the monorepo does not use NNG chronik-client anywhere (and the use of ChronikClientNode has also been deprecated in the monorepo), publish in-node-only chronik-client as 0.301.0.0 This is a breaking change for existing users. Aliasing ChronikClientNode and all types was considered, however there is no clean way to deprecate this as users with old types will always be forced to update them unless dozens of aliases are maintained here indefinitely. Given the present low download count of the module, judged better impact to drop all legacy names and types now. Decision to minor version bump despite breaking change is also due to relatively early stage of lib developmentGoing forward, see discussion in diff in-line commentsbreaking changes will have major version bumps.