Skip to content

Releases: jsonstat/toolkit

v2.2.2

09 Jun 17:20
79b8f1d

Choose a tag to compare

This release updates the toolkit to version 2.2.2. It rolls up several major, minor, and patch updates that have been introduced since the last GitHub release (v1.6.0).

🚀 Major Modernization (v2.0.0)

  • ES2016 Transition: The codebase has been fully reviewed and updated to ES2016 standards.
  • Dependency Reduction: Removed node-fetch as it is no longer required.

✨ New Features (v2.1.0 - v2.2.1)

  • Transform() Method:
    • Introduced the new Transform() method as a modern replacement for the toTable() method.
    • Integrated Transform() internally into the Dice() and Slice() methods.
    • Added support for the "objarr" output format in Transform().
    • Added support for the "object" output format in Transform() (providing direct compatibility with Google's DataTable).

🐛 Bug Fixes & Optimizations

  • Performance: Optimized the Unflatten() method for greater efficiency.
  • toTable() Fixes:
    • Fixed a bug when unit=true.
    • Fixed a bug when type="arrobj", comma=true, and field="label".
  • Transform() Fixes: Corrected the treatment of null values when the comma=true option is enabled.

🔒 Security & Build Updates (v2.2.2)

  • Resolved security vulnerabilities by upgrading build tools and dependencies:
    • Bumped rollup devDependency to 4.59.0.
    • Upgraded serialize-javascript transitive dependency (used by @rollup/plugin-terser) to 7.0.5.
    • Upgraded picomatch transitive dependency to 4.0.4.

📝 Documentation & Examples

  • Substantially expanded documentation across API.md, EXAMPLES.md, and INSTALL.md with comprehensive examples (e.g., unemployment rates, population pyramids) and links to Observable notebooks.

jsonstat-toolkit version 1.6.0

11 Jul 15:38
4d6fb85

Choose a tag to compare

This is the last release of JSON-stat Toolkit version 1.

Version 0 supported very old ECMAScript and browsers' versions and is deprecated.

Version 1 was build upon version 0: some minor functionality was removed but many new features were added. The new features were usually developed using more modern ECMAScript but, as a whole, version 1 remained rooted in very old practices for compatibility's sake. Version 1 is not fully compatible with version 0. Version 1 has stood the test of time.

In the meantime, ECMAScript has continued to evolve over the years. In future version 2, the code will be upgraded to comply with modern standards, aiming to improve its efficiency while maintaining broad compatibility across modern ECMAScript engines, ensuring seamless functionality in all widely used browsers on current user systems.