TypeScript refactoring: option to use `export default` with "Move to a new file"

Among other reasons, I'd like to avoid barrel files and I find that default exports make doing so more intuitive (named exports are easily spread into a barrel file while default exports not so much).

Some files like default exports and some folks do not. I get that.

Unless there's a need to do so, I'd like VSCode to make it just as easy to use default exports as named exports. Today, TypeScript refactoring with Visual Studio Code favors named exports. This default behavior may provide some encouragement/bias to use them and not use default exports as much.

There is also a "Convert between default export and named export" refactoring which is handy but requires another step and an aware/intentional decision to use default exports.

Can "Move to a new file" be split into two options or otherwise support prompting developers to explicitly select which type of export to use while they are refactoring?

e.g.

1. "Move to a new file as default export"
2. "Move to a new file as named export"

Read the linked TypeScript refactoring documentation and start from the “Move to a new file” refactoring described in the issue. Define the scope for offering explicit default-export and named-export choices; done means users can select either export style during that refactoring.