I always split my work, as following:

• Add the test case which fails
• Add the fix
• Tag the PR as ready for review

ATM, the error I got with my test seems to be related to the issue

 FAIL  packages/babel-plugin-transform-typescript/test/index.js
  ● babel-plugin-transform-typescript/exports › default function

    TypeError: /Users/tonygorez/projects/babel/packages/babel-plugin-transform-typescript/test/fixtures/exports/default-function/input.ts: Cannot read property 'name' of null

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

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit e49774e:

Tip: in the PR description, don't just write the issue number but write "Fixes #13594": if you include the "Fixes" keyword, when this PR is merged the issue will be automatically closed.

The CI seems to fail somewhere (babel-old-version). Anyway, I added a check for the node.id for the isTSDeclareFunction case. But I wonder if we shouldn't make a global check... 🤔 with && ?

Friendly ping @JLHwung 🙌