proposal-intl-segmenter VS proposal-source-phase-imports

Splitting by grapheme clusters (or the characters the user actually sees): JS doesn't support this natively, so you'll need a library like grapheme-splitter. There's a Stage-4 proposal in the works, though: Intl.Segmenter:

Intl.Segmenter: Unicode segmentation in JavaScript slides.

But even that's not bulletproof. The best method is to divide the string into grapheme clusters before reversing, which is where Intl.Segmenter comes in.

Exactly, and emoji are outside the BMP, so it's not exactly an edge case, but the norm where two code units (UTF-16 double-bytes) are used to make one code point (Unicode character).

And it gets even worse, when you consider that for many purposes you're not even interested in code points but in graphemes -- e.g. a single visible emoji might actually be a combination of 5 code points, represented by 8 UTF-8 code units, taking up 16 bytes.

If you want to split a string by graphemes, you can either use the main dedicated library for it [3], or the relatively new API Intl.Segmenter [4] which is in Chrome and Safari, but still hasn't made it to Firefox [5].

[1] https://blog.jonnew.com/posts/poo-dot-length-equals-two

[2] https://www.contentful.com/blog/2016/12/06/unicode-javascrip...

[3] https://github.com/orling/grapheme-splitter

[4] https://github.com/tc39/proposal-intl-segmenter

[5] https://bugzilla.mozilla.org/show_bug.cgi?id=1423593

Also potentially (but not in practice so far) locale-specific. See the FAQ on Javascript's implementation: https://github.com/tc39/proposal-intl-segmenter#why-should-we-pass-a-locale-and-options-bag-for-grapheme-boundaries-isnt-there-just-one-way-to-do-it

We will soon support WASM imports (`import source foo from "./foo.wasm"`). [1]

[1]: https://github.com/tc39/proposal-source-phase-imports

Source Phase Imports: Proposal to enable importing modules at the source phase.

Import Reflection: Syntax to import ES modules with import reflection attributes.

Alternative module reflections (wasm imports): https://github.com/tc39/proposal-import-reflection

Evaluator Attributes: Enables the module import syntax to provide extra attributes along with a given import as evaluator attributes with the primary use case in mind of permitting these module type imports for Wasm slides.