Pete Gonzalez

@MichaelDeBoey I see -- v4.4 hasn't been released yet. 1. If you think someone would realistically depend on them, then I can temporarily include them. 2. If you think that...

I'm still waiting to hear from @bradzacher

> @octogonz might know... can we get around this by using the [`bundledPackages`](https://api-extractor.com/pages/configs/api-extractor_json/#bundledpackages) flag for API extractor? Would that inline the `SyntaxKind` declaration? It would, but because the TypeScript API...

Ok, lemme find some time, and I will fix up my draft PR so we can get this fixed.

IIRC the build was failing, maybe because of a unit test. If someone can fix that, it would be helpful. I've been on vacation so haven't had time to look...

Thanks, that's helpful! It seems that when I made my draft PR, I didn't try building the entire monorepo, so I wasn't aware that `@typescript-eslint/typescript-estree` internally relies on the `TSESTree.PunctuatorTokenToText`...

> So if we can get these types exposed by TypeScript, we could remove the whole `TokenToText` map and could just go for the solution you're currently having, right? 🤔...

Yes, when my project imports `TSESTree` like this... ```ts import type { TSESLint, TSESTree } from '@typescript-eslint/experimental-utils'; ``` ...it imports from `@typescript-eslint\types\dist\ts-estree.d.ts` which imports `@typescript-eslint\types\dist\ast-spec.d.ts`. That's what failed to compile...

+1 I encountered this problem today with code like this: ```ts // The error goes away if you delete "readonly": type T = readonly string[] | { color: 'red' }...

@slorber Maybe we can improve this manual page: https://docusaurus.io/docs/markdown-features/links Somehow I read that page several times without understanding that I need to be writing `[thing](../path/thing.md)` instead of `[thing](../path/thing)` or `[thing](/path/thing)`....