DOM.AsyncIterable not recognized as a valid lib

[thomas-darling]

🔎 Search Terms

dom.asynciterable lib

🕗 Version & Regression Information

• This changed in commit or PR Add asynciterable libs #56723
• This changed between versions ______ and 5.4.5

⏯ Playground Link

No response

💻 Code

My tsconfig.json file, as I wanted it to look:

{
  "compilerOptions": {
    "lib": [
      "ES2022",
      "WebWorker.ImportScripts",
      "DOM",
      "DOM.Iterable",
      "DOM.AsyncIterable" // This is not recognized as a valid lib
    ],
    "module": "ES2022",
    "target": "ES2022",
    etc...
  }
  etc...
}

🙁 Actual behavior

This line in es2022.full.d.ts indicates there should be a lib named DOM.AsyncIterable - but when I try to add that to my own set of libs in my tsconfig.json file, it says no such lib exists.

🙂 Expected behavior

I was under the impression that all the libs referenced in those *.full.d.ts files should also be available for use individually - meaning that I should be able to specify DOM.AsyncIterable as a lib in my tsconfig.json file.

Additional information about the issue

The documentation for libs in general is extremely lacking, and really needs to be improved.

[fatcerberus]

Just to be clear, is this a full-on compile-time error, or is it only your IDE (VSCode?) saying it’s not valid? Because if it’s the latter then it would just mean the JSON schema VSCode is using hasn’t been updated yet.

[thomas-darling]

It's both, actually - and it's a little weird.
Scratch that - it actually appears to be only a schema violation:

 

The compile-time errors I thought were caused by this, actually seem to be intermittent - can't quite pin down when exactly they occur, but they seem to be related to editing of tsconfig in general, not just that one lib, and they seem to go away if I build a second time. That's super weird, but seems to be unrelated to this issue... maybe a bug in Webpack, or in the ts compiler, if that does any kind of persistent caching.

[fatcerberus]

Those errors are definitely bizarre, but it looks like they're all coming up while running TSLint; TSLint has been deprecated since 2019; I expect the TS devs would tell you that it's not officially supported and you should have switched to ESLint by now.

https://palantir.github.io/tslint/

⚠️ TSLint has been deprecated as of 2019. Please see this issue for more details: Roadmap: TSLint → ESLint. typescript-eslint is now your best option for linting TypeScript.

[thomas-darling]

Sorry, I just updated my comment - seems the errors are something else.
As for tslint - yeah, I need to migrate away from that, but that's not running as part of the build, so that's not the cause.

[RyanCavanaugh]

Opened SchemaStore/schemastore#3858