feat: replace dependency graphemer with Intl.Segmenter

[fasttime]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request? (put an "X" next to an item)

[ ] Documentation update
[ ] Bug fix (template)
[ ] New rule (template)
[ ] Changes an existing rule (template)
[ ] Add autofix to a rule
[ ] Add a CLI option
[ ] Add something to the core
[X] Other, please explain: replace a dependency with a native implementation.

See the discussion in #17835

Fixes #17835

What changes did you make? (Give an overview)

Replaced graphemer with the native Segments implementation provided by Intl.Segmenter.

Is there anything you'd like reviewers to focus on?

• The implementations are not 100% equivalent
• The Segments behavior with respect to which sequences are considered graphemes is expected to change with newer version of Unicode
• Graphemer is currently used in the rules id-length and key-spacing
• As of today, the Segments API is not supported in all browsers: https://caniuse.com/?search=Segments

[netlify]

✅ Deploy Preview for docs-eslint canceled.

Name	Link
🔨 Latest commit	7264835
🔍 Latest deploy log	https://app.netlify.com/sites/docs-eslint/deploys/662165e29278460008dc6cc6

[github-actions]

Hi everyone, it looks like we lost track of this pull request. Please review and see what the next steps are. This pull request will auto-close in 7 days without an update.

[fasttime]

This is currently blocked on Firefox not supporting Intl.Segmenter in release builds: https://bugzilla.mozilla.org/show_bug.cgi?id=1423593#c58.

[aladdin-add]

it's supported on node.js >= 16, so it seems not a blocker:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Segmenter#browser_compatibility

re Firefox, can we add a polyfill in the playground?

[fasttime]

it's supported on node.js >= 16, so it seems not a blocker: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Intl/Segmenter#browser_compatibility

I can't say if it's acceptable for ESLint to have a core rule that works in Node.js but not in (all major) browsers. The Linter API is intended to work also outside of Node.js, but the same may not apply to individual rules, so maybe it's okay.

re Firefox, can we add a polyfill in the playground?

graphemer is likely the best polyfill these days.

[aladdin-add]

Currently eslint doesn't officially support browsers, so I think that's acceptable. thoughts? @nzakas @mdjermanovic

[nzakas]

The purpose of this effort was to remove graphemer as a dependency. If we need to include it as a polyfill, then we're not really getting any benefit.

[aladdin-add]

@nzakas seems we are not on the same page. It will remove graphemer from eslint's dependencies, and add the polyfill in our website(playground).

[nzakas]

Ah, I see, thanks for explaining. In that case, I'm 👍

[fasttime]

Intl.Segmenter is available in new Firefox 125.

[nzakas]

Release notes for Firefox 125: https://developer.mozilla.org/en-US/docs/Mozilla/Firefox/Releases/125

[nzakas]

LGTM. Looks like all tests are passing, so I think we're good to go.

[nzakas]

Would like an approval from @aladdin-add based on previous comments before merging.

[aladdin-add]

LGTM, thanks!

[ota-meshi]

Thank you 🎉