jridgewell

Yah, I was using char interchangeably with code point. I also used byte instead of code unit.

> truncate a string without splitting a codepoint in O(1) is still useful

Agreed!

This isn't quite right. In invalid UTF8, a continuation byte can also emit a replacement char if it's the start of the byte sequence. Eg, `0b01100001 0b10000000 0b01100001` outputs 3 chars: a�a. Whether you're at the beginning of an output char depends on the last 1-3 bytes.

With the number of VPs sending emails, I think it's much larger than "hundreds".

`0.015.toFixed(2) === "0.01"`, and `0.087.toFixed(2) === "0.09"`

We plan on supporting both. We're still in the alpha phase, and have not designed the plugin API yet.

It's _currently_ Next specific, but we plan on making it generic and usable in any setup.

Our initial development cycles were dedicated on getting Next working. But we absolutely plan on expanding the to support generic bundling and will include that in the docs.