[@babel/traverse]: Add support for recursive NodePath::get(…) calls

[ExE-Boss]

Please fill in this template.

• Use a meaningful title for the pull request. Include the name of the package modified.
• Test the change in your own code. (Compile and run.)
• Add or edit tests to reflect the change.
• Follow the advice from the readme.
• Avoid common mistakes.
• Run pnpm test <package to test>.

Select one of these and delete the others:

If changing an existing definition:

• Provide a URL to documentation or source code which provides context for the suggested changes: https://github.com/babel/babel/blob/55a194212612b9e2c666cc0877d07a8e1218bc36/packages/babel-traverse/src/path/family.ts#L375-L379 ¹
• If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the package.json.

Footnotes

1. Note that @babel/traverse’s internal type definitions don’t support strictNullChecks. ↩

[typescript-bot]

@ExE-Boss Thank you for submitting this PR!

This is a live comment that I will keep updated.

1 package in this PR

• babel__traverse — on npm, on unpkg (author is owner)

Code Reviews

Because this is a widely-used package, a DT maintainer will need to review it before it can be merged.

You can test the changes of this PR in the Playground.

Status

• ✅ No merge conflicts
• ✅ Continuous integration tests have passed
• ✅ Most recent commit is approved by a DT maintainer

All of the items on the list are green. To merge, you need to post a comment including the string "Ready to merge" to bring in your changes.

---

Diagnostic Information: What the bot saw about this PR

{
  "type": "info",
  "now": "-",
  "pr_number": 72228,
  "author": "ExE-Boss",
  "headCommitOid": "112ad8bc768f7e7f18019749361fc49002437bbd",
  "mergeBaseOid": "5c6992901c82e5061bb60c0a8d746d9015793c02",
  "lastPushDate": "2025-03-18T17:55:34.000Z",
  "lastActivityDate": "2025-03-26T07:44:18.000Z",
  "mergeOfferDate": "2025-03-25T16:04:48.000Z",
  "mergeRequestDate": "2025-03-26T07:44:18.000Z",
  "mergeRequestUser": "ExE-Boss",
  "hasMergeConflict": false,
  "isFirstContribution": false,
  "tooManyFiles": false,
  "hugeChange": false,
  "popularityLevel": "Critical",
  "pkgInfo": [
    {
      "name": "babel__traverse",
      "kind": "edit",
      "files": [
        {
          "path": "types/babel__traverse/babel__traverse-tests.ts",
          "kind": "test"
        },
        {
          "path": "types/babel__traverse/index.d.ts",
          "kind": "definition"
        }
      ],
      "owners": [
        "yortus",
        "marvinhagemeister",
        "rpetrich",
        "mgroenhoff",
        "dlgrit",
        "ifiokjr",
        "ExE-Boss",
        "danez"
      ],
      "addedOwners": [],
      "deletedOwners": [],
      "popularityLevel": "Critical"
    }
  ],
  "reviews": [
    {
      "type": "approved",
      "reviewer": "rbuckton",
      "date": "2025-03-25T16:04:08.000Z",
      "isMaintainer": true
    }
  ],
  "mainBotCommentID": 2734231744,
  "ciResult": "pass"
}

[typescript-bot]

🔔 @yortus @marvinhagemeister @rpetrich @mgroenhoff @dlgrit @ifiokjr @danez — please review this PR in the next few days. Be sure to explicitly select Approve or Request Changes in the GitHub UI so I know what's going on.

[typescript-bot]

@ExE-Boss: Everything looks good here. I am ready to merge this PR (at 112ad8b) on your behalf whenever you think it's ready.

If you'd like that to happen, please post a comment saying:

Ready to merge

and I'll merge this PR almost instantly. Thanks for helping out! ❤️

(@yortus, @marvinhagemeister, @rpetrich, @mgroenhoff, @dlgrit, @ifiokjr, @danez: you can do this too.)

[ExE-Boss]

Ready to merge