Closed speedytwenty closed 2 years ago
Noting, that I'm anticipating a breaking v0.7.0
release with #295. To continue supporting Node version 13.x is likely more hassle than it's worth. It could be avoided, but it probably makes sense to drop support for Node 13 to avoid dependency issues.
👋 @speedytwenty
sorry, I was on vacation. I just gave you publish permission on npm. thanks a lot for your work on this package! :)
I'm seeking access [and any inapparent special instructions] to publish [npm] releases for cli-table3. @Turbo87 @DanielRuf
The short term roadmap is a bug-fix and feature additions release:
v0.6.2
. Followed later by av0.6.3
release which hones in on performance—both speed and memory consumption—without breaking the API**. I'm not sure where Typescript support stands but I aim to know before v0.6.3 (#295).I've spent the last ~10 days methodically picking a couple years worth of low-hanging-fruit as well as getting pretty intimate with this entire package; including source, tests, dependencies, documentation, and documentation generation.
If granted, I will seek to automate and document the release process for ourselves and future contributors to include any of the following that may not already be present:
Proposed (short-term) roadmap
v0.6.2
This will be a release of the latest fixes and feature additions—before further refactoring. Including:
v0.6.3
potentially v0.7.0
Performance knockout! This will reduce the rending time of cli-table3 by ~3,600% and memory usage will be minimized without breaking the API.
Custom cells Cell will be heavily refactored and the API sanitized. Not sure how well it will be documented, but it will be possible to populate tables with custom cells that extend the [refactored] Cell.
**There may be "deep" API breakage in v0.6.3 for anyone that uses cli-table3's internal classes or functions.