Enhancement: Add serialization info to parser

[nzakas]

Before You File a Proposal Please Confirm You Have Done The Following...

• I have searched for related issues and found none that match my proposal.
• I have searched the current rule list and found no rules that match my proposal.
• I have read the FAQ and my problem is not listed.

Relevant Package

parser

My proposal is suitable for this project

• I believe my proposal would be useful to the broader TypeScript community (meaning it is not a niche proposal).

Description

Up until now, the flat config in ESLint was unable to serialize custom parsers, meaning that caching and --print-config would not work with typescript-eslint/parser. I just added a feature that allows parsers to export a meta key that would provide serialization information, such as:

exports.meta = {
    name: "typescript-eslint/parser",
    version: "0.0.0"
};

This should be exported on the same object as parse() and parseForESLint().

Fail

// not applicable

Pass

// not applicable

Additional Info

It seems like there may be some fields meant for rules in this template. :)

[brettz9]

FWIW, this would be useful for us in eslint-plugin-jsdoc to auto-detect from the parser metadata that the user wants TypeScript mode as far as JSDoc's.

[bradzacher]

@brettz9 - you can actually get this (in a way) in lint rules today via context.parserPath.
The metadata would help to concretely identify it (eg you could do require(context.parserPath).meta.name), but should still be able to make an educated guess by just inspecting the path.

[brettz9]

@bradzacher : Yes, thank you, that's what we have been using, but for a user trying the new flat config, it seems it is not working per eslint/eslint#16878 (comment) .

[nzakas]

You should be able to do context.parser.meta.name with either type of config.