From the list in
#45349 (comment),
excluding the JSX errors, decorator errors and unresolved #private
error. The latter re-uses "Cannot resolve name X" which naturally shows
up a *lot* in plain JS.

Also remove checkGrammarArguments; it's blocked entirely by the same
parser error.

sandersn deleted the plain-js-grammar-errors branch

sandersn added a commit that referenced this pull request

These are the last ones that I know of. They come from calls to
`grammarErrorOnFirstToken`.

Fixes part of #45349
Follow-up to #47067

sandersn added a commit that referenced this pull request

These are the last ones that I know of. They come from calls to
`grammarErrorOnFirstToken`.

Fixes part of #45349
Follow-up to #47067

mprobst pushed a commit to mprobst/TypeScript that referenced this pull request

* Plain JS grammar errors

From the list in
microsoft#45349 (comment),
excluding the JSX errors, decorator errors and unresolved #private
error. The latter re-uses "Cannot resolve name X" which naturally shows
up a *lot* in plain JS.

* Add grammarErrorAtPos errors

Also remove checkGrammarArguments; it's blocked entirely by the same
parser error.

mprobst pushed a commit to mprobst/TypeScript that referenced this pull request

These are the last ones that I know of. They come from calls to
`grammarErrorOnFirstToken`.

Fixes part of microsoft#45349
Follow-up to microsoft#47067

microsoft locked as resolved and limited conversation to collaborators