chore(no-sync): remove @typescript-eslint/utils

[risantos]

Description

• Remove @typescript-eslint/utils, which has typescript as a peer dependency.
  Update the getParserServices function to handle parser services directly without relying on the removed utility.

Related issues

• Warning received while installing eslint-plugin-n on JS projects without typescript:

  warning "eslint-plugin-n > @typescript-eslint/[email protected]" has unmet peer dependency "typescript@>=4.8.4 <5.9.0".
  warning "eslint-plugin-n > [email protected]" has unmet peer dependency "typescript@>=4.0.0".
  warning "eslint-plugin-n > @typescript-eslint/utils > @typescript-eslint/[email protected]" has unmet peer dependency "typescript@>=4.8.4 <5.9.0".
  warning "eslint-plugin-n > @typescript-eslint/utils > @typescript-eslint/typescript-estree > @typescript-eslint/[email protected]" has unmet peer dependency "typescript@>=4.8.4 <5.9.0".
  warning "eslint-plugin-n > @typescript-eslint/utils > @typescript-eslint/typescript-estree > @typescript-eslint/[email protected]" has unmet peer dependency "typescript@>=4.8.4 <5.9.0".
  warning "eslint-plugin-n > @typescript-eslint/utils > @typescript-eslint/typescript-estree > [email protected]" has unmet peer dependency "typescript@>=4.8.4".

[Copilot]

Pull Request Overview

This PR removes the @typescript-eslint/utils dependency and inlines its parser services logic.

• Removed @typescript-eslint/utils from package.json.
• Reimplemented getParserServices in lib/util/get-parser-services.js with custom error handling and parser detection.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
package.json	dropped @typescript-eslint/utils dependency
lib/util/get-parser-services.js	added inline parserServices logic, error messages, and a flag for type-info requirements

Comments suppressed due to low confidence (1)

lib/util/get-parser-services.js:58

• This error branch is newly introduced but lacks corresponding tests. Add unit tests to cover the scenario where parserServices.program is null and allowWithoutFullTypeInformation is false to ensure throwError is invoked as expected.

    if (parserServices.program == null && !allowWithoutFullTypeInformation) {

[scagood]

Generally love this change 💜

Thank you

[MichaelDeBoey]

CC/ @JoshuaKGoldberg

[scagood]

Awesome, thanks.

[JoshuaKGoldberg]

👋 @MichaelDeBoey thanks for the ping but I'm a bit lost, is there something I should be doing here?

[MichaelDeBoey]

@JoshuaKGoldberg I figured since you're the maintainer of the original package, you could maybe give some more insights into if this replacement is done properly and maybe we forgot some edge cases here that are important and that's why you guys have TS as a dependency.
Or if not, maybe we could thrive the original package to exclude TS from its dependencies.

[JoshuaKGoldberg]

Ah gotcha, thanks! Yeah I think you're on the right track. We've been experimenting with splitting up @typescript-eslint/utils: e.g. typescript-eslint/typescript-eslint#10383. In the meantime this is pretty much the right strategy.

If you don't think you'd end up wanting to use the standalone @typescript-eslint/rule-creator package, we could take an issue asking for a standalone getParserServices.

[MichaelDeBoey]

@JoshuaKGoldberg I think it would be awesome if we could just keep using the original code without all the problems mentioned here in this PR.
Forking it in this package would mean we would have 2 places where possible changes/bugfixes need to happen, which won't be beneficial of everybody's time imo.

CC/ @eslint-community/eslint-plugin-node

[ota-meshi]

I think ts-declaration-location also has typescript in its peer dependencies. I don't think this PR alone will completely solve the problem, am I right?

Sorry. I realized later that there was a #451.

[aladdin-add]

so what's the next step here?