@babel/core: add loadPartialConfigAsync

[SimenB]

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 npm 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/1a05b81387eedbb2fb86a404e8df69dc96ac21e9/packages/babel-core/src/index.js#L23-L30
• If this PR brings the type definitions up to date with a new version of the JS library, update the version number in the header.

[typescript-bot]

@SimenB Thank you for submitting this PR!

This is a live comment which I will keep updated.

1 package in this PR

• babel__core on npm, on unpkg
  • owner-approval: @marvinhagemeister

Code Reviews

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

Status

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

Once every item on this list is checked, I'll ask you for permission to merge and publish the changes.

---

Diagnostic Information: What the bot saw about this PR

{
  "type": "info",
  "now": "-",
  "pr_number": 51741,
  "author": "SimenB",
  "headCommitOid": "5d5385a32a101e7974058320685dcb5761e8881c",
  "lastPushDate": "2021-03-14T12:08:58.000Z",
  "lastActivityDate": "2021-03-14T12:33:37.000Z",
  "maintainerBlessed": false,
  "hasMergeConflict": false,
  "isFirstContribution": false,
  "popularityLevel": "Critical",
  "pkgInfo": [
    {
      "name": "babel__core",
      "kind": "edit",
      "files": [
        {
          "path": "types/babel__core/babel__core-tests.ts",
          "kind": "test"
        },
        {
          "path": "types/babel__core/index.d.ts",
          "kind": "definition"
        }
      ],
      "owners": [
        "yortus",
        "marvinhagemeister",
        "mgroenhoff",
        "Jessidhia",
        "ifiokjr"
      ],
      "addedOwners": [],
      "deletedOwners": [],
      "popularityLevel": "Critical"
    }
  ],
  "reviews": [
    {
      "type": "approved",
      "reviewer": "marvinhagemeister",
      "date": "2021-03-14T12:33:37.000Z",
      "isMaintainer": false
    }
  ],
  "ciResult": "pass"
}

[typescript-bot]

🔔 @yortus @marvinhagemeister @mgroenhoff @Jessidhia @ifiokjr — 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]

👋 Hi there! I’ve run some quick measurements against master and your PR. These metrics should help the humans reviewing this PR gauge whether it might negatively affect compile times or editor responsiveness for users who install these typings.

Let’s review the numbers, shall we?

Comparison details 📊

	master	#51741	diff
Batch compilation
Memory usage (MiB)	99.1	100.1	+1.0%
Type count	13579	13580	0%
Assignability cache size	181463	181463	0%
Language service
Samples taken	235	235	0%
Identifiers in tests	235	235	0%
getCompletionsAtPosition
Mean duration (ms)	122.3	122.4	+0.1%
Mean CV	15.1%	14.7%
Worst duration (ms)	164.7	162.2	-1.5%
Worst identifier	sourceCode	body
getQuickInfoAtPosition
Mean duration (ms)	125.8	125.4	-0.3%
Mean CV	12.8%	12.0%
Worst duration (ms)	173.3	169.9	-1.9%
Worst identifier	map	body

It looks like nothing changed too much. I won’t post performance data again unless it gets worse.

[typescript-bot]

@marvinhagemeister Thank you for reviewing this PR! The author has pushed new commits since your last review. Could you take another look and submit a fresh review?

[typescript-bot]

I just published @types/[email protected] to npm.