Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Enhancement: useIntl.Segmenter instead ofgraphemer #11803

Open
Labels
accepting prsGo ahead, send a pull request that resolves this issueenhancementNew feature or request
@JstnMcBrd

Description

@JstnMcBrd

Before You File a Proposal Please Confirm You Have Done The Following...

Relevant Package

eslint-plugin

My proposal is suitable for this project

  • I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

Description

In#7068, it was proposed that we switch fromgrapheme-splitter tographemer because eslint did (eslint/eslint#17160).

Well, since then, eslint has switched fromgraphemer toIntl.Segmenter (eslint/eslint#18110).

It would be great for@typescript-eslint/eslint-plugin to also switch toIntl.Segmenter for consistency and dependency deduplication.

(It's also a recommended module replacement - seehttps://github.com/es-tooling/module-replacements/blob/main/docs/modules/graphemer.md)

Additional Info

See also:this comment from Sep 2022:

... after Node.js v14 hits EoL and typescript-eslint only supports Node.js 16 or later, we can useIntl.Segmenter.

Node v14 has hit EoL, and typescript-eslint only supports v18.18.0 or later, so it sounds like we're ready.

Metadata

Metadata

Assignees

No one assigned

    Labels

    accepting prsGo ahead, send a pull request that resolves this issueenhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions


      [8]ページ先頭

      ©2009-2025 Movatter.jp