Awesome Node.js has a "changelog" section under all projects. You can find it next to the "Repo" button in the header. There are two features that make it unique.

  1. It is an aggregation of parsed "CHANGELOG.md" files and releases information from Github. This way, it is easier to see all changes in a single place and a uniform style.
  2. All changelogs are "emojified". This helps with identifying each change easier. Emojification is achieved by parsing each line and applying a specific emoji based on the first word or some other tokens.

The combination of the above two makes module changelogs on Awesome Node.js unique.

As you know, an example is worth a 1,000 words 🚀

Changelog examples

  • launchdarkly-server-sdk 3.0.0 (June 27, 2022)

    ➕ Added:

    • ➕ Add flag support for the client side availability property, as well as the older the ability to decode from the older clientSide format.
    • 📇 The new allFlagsState function should be used instead of allFlags if you are passing flag data to the front end for use with the JavaScript SDK. It preserves some flag metadata that the front end requires in order to send analytics events correctly. Versions 2.5.0 and above of the JavaScript SDK are able to use this metadata, but the output of allFlagsState will still work with older versions.
    • 👀 It is now possible to inject feature flags into the client from local JSON files, replacing the normal LaunchDarkly connection. This would typically be for testing purposes. See LaunchDarkly.Server.Integrations.FileData.
    • ✅ LaunchDarkly.Server.Integrations.TestData is another new way to inject feature flag data programmatically into the SDK for testing—either with fixed values for each flag, or with targets and/or rules that can return different values for different users. Unlike FileData, this mechanism does not use any external resources, only the data that your test code has provided.

    🔄 Changed:

    • 🏗 CI builds now include a cross-platform test suite implemented in https://github.com/launchdarkly/sdk-test-harness. This covers many test cases that are also implemented in unit tests, but may be extended in the future to ensure consistent behavior across SDKs in other areas.
    • The SDK will track the last known server time as specified in the Date header when sending events. This value, along with the current system time, will be used to determine if debug event should still be sent.
    • VariationIndex has been changed from Natural to Integer.

    🛠 Fixed:

    • When evaluating against a user attribute, if the attribute is null, it should always be treated as a non-match.
  • force-layout 0.2.0.1 (December 22, 20130)
    • Allow base-4.7
  • niv 0.2.20 (April 04, 2022)

Recent releases