I published the beta of my bubble chart library. Help me break it!

In January, the author unveiled a prototype of a bubble chart they had developed from scratch on Threads. Initially, the creation garnered little attention. After a ten-month period consisting of one redesign and extensive testing, the bubble chart evolved into a web-based library named OrbFlow. This library uniquely treats bubbles as though they were bubbles themselves - they ascend when the chart scrolls into view, float, push against each other, and burst upon being tapped.

The beta version of OrbFlow has now been made available on npm. The author invites readers to test it and report any issues encountered. Instructions for incorporating the library into a project include installing it using npm (version 18 or 19 is compatible with Next.js), and incorporating the OrbChart component into a React application. A plain JavaScript version is also provided for those who prefer it.

The library boasts several notable features. It has no runtime dependencies, is approximately 15 KB when gzipped, and the bubble area directly corresponds to the value - meaning that double the value will appear twice as large. Tapping a bubble will cause it to pop, with droplets appearing, and these popped bubbles can reappear subsequently. Keyboard and screen reader support are also integrated, ensuring that every bubble functions as a distinct button within a concealed list.

The developer has ensured compatibility with reduced motion settings, causing the chart to settle and remain stationary when this setting is activated. Additionally, the code is equipped with TypeScript types, and is compatible with both ESM and CommonJS formats, as well as a CDN script.

The author is seeking feedback on several aspects of the library. The proposed prop and option names are one area of interest, as is the sizing and layout functionality. The author also invites feedback on the types of data users have tried, and whether this data is effectively represented as bubbles. The author has also listed out a few tasks that remain pending before the library reaches version 1.

These tasks include completing the documentation and API reference, conducting performance tests for large datasets, and soliciting feedback. The author has expressed that anyone whose feedback leads to changes will be credited in the version 1 release notes.