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

cf. #10315, #9924

I see the concern with the added dependency - but without this, it just doesn't work with strict package managers and can cause some weird issues in the ones that rely on the flattened node_modules. I had an issue today where different packages were accidentally loading @babel/types from different locations and thus causing type issues because those types were not quite compatible. This wouldn't happen if the dependency would be declared explicitly.

I personally prefer to remove the import and return any or {type:xxx...}.

but without this, it just doesn't work with strict package managers

While that is correct both Yarn and pnpm declare this dependency automatically so in this case they're not affected.
https://github.com/yarnpkg/berry/blob/444eea50e8bdbd8c6a3afef51633a011e4f30069/packages/yarnpkg-extensions/sources/index.ts#L160-L165

I've looked at the past two PRs and it seems that only bundling of types is an acceptable solution.
Currently I'm doing something similar in #15094, if we want the types of @babel/types to be bundled together as well, then I don't have to try to suppress the error warning from ts . (see Failed CI)

Thanks to merceyz for the information, in my opinion, since yarn and pnpm already have @babel/types as a dependency, it is acceptable for us to add it.
But maybe packaging the types can report some compatibility issues for users, I'm not sure about that.