Skip to content

Type for Intl.Segmenter #577

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
BirgitPohl opened this issue Jan 8, 2025 · 3 comments · May be fixed by #591
Open

Type for Intl.Segmenter #577

BirgitPohl opened this issue Jan 8, 2025 · 3 comments · May be fixed by #591

Comments

@BirgitPohl
Copy link

I'm installing yeoman

diff type

{
  "name": "generator-person",
  "version": "1.0.0",
  "description": ghjj",
  "license": "ISC",
  "author": "me",
  "type": "commonjs",
  "keywords": [
    "yeoman-generator"
  ],
  "files": [
    "generators"
  ],
  "main": "generators/index.js",
  "scripts": {
    "test": "test",
    "build": "npm run clean && tsc",
    "link": "npm link",
    "clean": "rm -rf generators"
  },
  "dependencies": {
    "ts-node": "^10.9.2",
    "typescript": "^5.7.2",
    "yeoman-generator": "^5.10.0"
  },
  "devDependencies": {
    "@types/yeoman-generator": "^5.2.14"
  }
}

When I

npm i
npm run build

I get an error, that

node_modules/@types/diff/index.d.ts:43:26 - error TS2694: Namespace 'Intl' has no exported member 'Segmenter'.

43     intlSegmenter?: Intl.Segmenter | undefined;

I wanted to report that here and not in definitely typed, because since you have added the support for this in 2024, you might want to check, if Intl has updated something that requires refactoring.

Currently, it blocks me.

@lsmith77
Copy link

lsmith77 commented Jan 23, 2025

any update here?

updating my tsconfig.json to use es2022 for the lib fixed it for me. need to see what the general impact is though.

@isaachinman
Copy link

Related to #303

@ExplodingCabbage
Copy link
Collaborator

Yeah, this happens if your compilation target is one for which Intl.Segmenter didn't yet exist. Interesting. I may try to address this once we're shipping our own TypeScript definitions instead of relying on DefinitelyTyped, but I don't actually know what the right approach to take here is, and will need to do some research.

@ExplodingCabbage ExplodingCabbage linked a pull request Apr 11, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants