build: use mjs files for ng-dev configuration

In preperation for ng-dev requiring mjs files for configuration, switch over our usage

Author: josephperrott

.ng-dev/caretaker.mts renamed to .ng-dev/caretaker.mjs

@@ -1,7 +1,9 @@
-import {CaretakerConfig} from '@angular/ng-dev';
-
-/** The configuration for `ng-dev caretaker` commands. */
-export const caretaker: CaretakerConfig = {
+/**
+ * The configuration for `ng-dev caretaker` commands.
+ *
+ * @type { import("@angular/ng-dev").CaretakerConfig }
+ */
+export const caretaker = {
   githubQueries: [
     {
       name: 'Merge Queue',

.ng-dev/commit-message.mts renamed to .ng-dev/commit-message.mjs

@@ -1,9 +1,9 @@
-import {CommitMessageConfig} from '@angular/ng-dev';
-
 /**
  * The configuration for `ng-dev commit-message` commands.
+ *
+ * @type { import("@angular/ng-dev").CommitMessageConfig }
  */
-export const commitMessage: CommitMessageConfig = {
+export const commitMessage = {
   maxLineLength: Infinity,
   minBodyLength: 0,
   minBodyLengthTypeExcludes: ['docs'],

.ng-dev/config.mts renamed to .ng-dev/config.mjs

@@ -0,0 +1,11 @@
+/**
+ * Configuration for the `ng-dev format` command.
+ *
+ * @type { import("@angular/ng-dev").FormatConfig }
+ */
+export const format = {
+  buildifier: true,
+  prettier: {
+    matchers: ['**/*.{js,ts,mts,mjs,json}'],
+  },
+};

.ng-dev/format.mjs

@@ -0,0 +1,12 @@
+/**
+ * Github configuration for the `ng-dev` command. This repository is used as
+ * remote for the merge script and other utilities like `ng-dev pr rebase`.
+ *
+ * @type { import("@angular/ng-dev").GithubConfig }
+ */
+export const github = {
+  owner: 'angular',
+  name: 'components',
+  mainBranchName: 'main',
+  useNgDevAuthService: true,
+};

.ng-dev/format.mts

@@ -1,10 +1,10 @@
-import {PullRequestConfig} from '@angular/ng-dev';
-
 /**
- * Configuration for the pull request commands in `ng-dev`. This includes the
- * setup for the merge command.
+ * Configuration for the merge tool in `ng-dev`. This sets up the labels which
+ * are respected by the merge script (e.g. the target labels).
+ *
+ * @type { import("@angular/ng-dev").PullRequestConfig }
  */
-export const pullRequest: PullRequestConfig = {
+export const pullRequest = {
   // By default, the merge script merges locally with `git cherry-pick` and autosquash.
   // This has the downside of pull requests showing up as `Closed` instead of `Merged`.
   // In the components repository, since we don't use fixup or squash commits, we can

.ng-dev/github.mjs

@@ -6,11 +6,6 @@
  * found in the LICENSE file at https://angular.dev/license
  */
 
-import semver from 'semver';
-import {ReleaseConfig} from '@angular/ng-dev';
-import {assertValidUpdateMigrationCollections} from '../tools/release-checks/check-migration-collections.mjs';
-import {assertValidNpmPackageOutput} from '../tools/release-checks/npm-package-output/index.mjs';
-
 /**
  * Packages that will be published as part of the project.
  *
@@ -30,8 +25,12 @@ export const releasePackages = [
   'material-date-fns-adapter',
 ];
 
-/** Configuration for the `ng-dev release` command. */
-export const release: ReleaseConfig = {
+/**
+ * Configuration for the `ng-dev release` command.
+ *
+ * @type { import("@angular/ng-dev").ReleaseConfig }
+ */
+export const release = {
   releaseNotes: {
     useReleaseTitle: true,
     groupOrder: releasePackages,
@@ -58,6 +57,13 @@ export const release: ReleaseConfig = {
     return performNpmReleaseBuild();
   },
   prereleaseCheck: async (newVersionStr, builtPackagesWithInfo) => {
+    const semver = await import('semver');
+    const assertValidUpdateMigrationCollections = await import(
+      '../tools/release-checks/check-migration-collections.mjs'
+    );
+    const assertValidNpmPackageOutput = await import(
+      '../tools/release-checks/npm-package-output/index.mjs'
+    );
     const newVersion = new semver.SemVer(newVersionStr);
 
     await assertValidUpdateMigrationCollections(newVersion);