Build successful! You can test your changes in the REPL here: https://babeljs.io/repl/build/58524

What was the motivation for this?

Loading configuration files can be slow, so this improves performance over the default.

Mh, in which case would somebody want to use @babel/eslint-parser but without checking which syntax plugins to enable? 🤔 If they are using it with no syntax plugins, they may as well just use the default ESLint parser.

I thought there was an agreement to change it somewhere.

As one uses @babel/eslint-parser, but not using any babel transform, I use it only because espree is slow to add new features (at least it was before).

I just want to say there are too many falses to pass, and I didn't even know there are

      ignore: null,
      only: null,
      browserslistConfigFile: false,

This is what I use usually https://github.com/sindresorhus/eslint-plugin-unicorn/blob/eb08fc523c3229722df167d91095cf4f5f5895be/test/utils/parsers.js#L21

Search for @babel/eslint-parser requireConfigFile: false on github, there seems a lot result

If we don't want change the default behavior, can we make it simpler to config?