object-treeify stringifies a JavaScript object into a readable tree-style text format. It’s useful for logging or displaying nested object data, with options like custom sorting, custom rendering, and handling circular references.
Project status
- The source appears to be in maintenance mode rather than actively maintained, with the most recent upstream push and updates on 2025-01-29, about 16 months ago relative to 2026-06-09.
- Update cadence has slowed over time: several updates in mid 2022, updates again in 2023-08, then a follow-up in 2025-01, with no evidence of continued updates since.
AI summary generated
Recent updates
v5.0.1
v5.0.1 contains no source-code changes, only dependency updates. The release notes only state that dependencies were updated, without detailing which packages changed or what behavioral impact that could have.
Breakingv5.0.0
v5.0.0 primarily bumps the minimum supported Node.js version to 20. The code diff, however, shows substantial development tooling and test/coverage harness changes (ESLint, c8/mocha loader mechanism, semantic-release invocation, and updated devDependency versions).
Breakingv4.0.1
Release v4.0.1 contains no source code changes, only dependency updates. The release notes mention updated dependencies but do not specify which packages changed.
Breakingv4.0.0
v4.0.0 raises the project minimum Node.js version to 16 and updates development dependencies. The release notes only mention the Node requirement and a general dependency refresh, but the code diff also shows significant changes to the hot-reload test/loader infrastructure and repo configuration tooling.
Breakingv3.3.1
Release v3.3.1 is described in the notes only as a dependency update. However, the diff shows multiple contributor-facing and tooling changes in addition to devDependency version bumps, including removal of Coveralls-related configuration and scripts.
Breakingv3.3.0
v3.3.0 introduces an option intended to control how node values are separated from keys in the rendered tree output. The code change also adjusts the rendering contract for renderFn and changes what gets included for the root node.
Featuresv3.2.1
Release v3.2.1 contains a small documentation update and a minor internal refactor around option handling. The release notes only mention a README change, and the code diff shows no clear functional behavior changes that would affect runtime API usage.
v3.2.0
Release v3.2.0 adds a new `renderFn` option that lets consumers override how individual node values are rendered in the tree output. The implementation routes node value formatting through this callback and adds corresponding documentation and a unit test.
Featuresv3.1.2
Release v3.1.2 is described as a minor documentation update. The provided diff indicates only README content was changed, with no changes to application/library source code or behavior.
v3.1.1
v3.1.1 contains a very small documentation-only change. The release notes describe a minor docs update, and the code diff shows only a README edit with no production code modifications.