fix(vitest): silence Vite native configLoader warnings (#1922)

* fix(vitest): silence Vite native configLoader warnings

Vite's configLoader: "native" (the future default) can't load config
files that use ESM syntax under CommonJS resolution or extensionless
relative imports. Fix both classes of warning:

- Rename root-level *.config.ts files (and
  packages/design-token-ts-plugin/vitest.config.ts) to .mts, since the
  nearest package.json has no "type" field and defaults to CommonJS.
- Add "type": "module" to packages/i18n/package.json, matching
  packages/nimbus and packages/nimbus-mcp. It's an internal build tool
  only ever invoked via tsx (unaffected by "type") or imported from
  Vite config loaders, so this is safe.
- Add explicit .ts extensions to the now-flagged relative imports in
  packages/nimbus's vite/vitest configs (allowImportingTsExtensions is
  already enabled in tsconfig).

Verified pnpm test:dev, the unit/unit-isolated/ts-plugin/scripts
projects, and typecheck:dev all pass with the warnings gone.

* docs(testing): update root orchestrator filename to vitest.config.mts

Keeps the unit-testing guideline in sync with the rename in
a4c1efb (fix(vitest): silence Vite native configLoader warnings).

* fix(i18n): fix CI build breakage from prior commit

The previous commit added "type": "module" to packages/i18n/package.json
to silence a Vite native configLoader warning about ESM syntax loaded
as CommonJS. That broke this package's build pipeline: its tsx-invoked
scripts (build:split, build:compile-strings, build:dictionaries) use
CommonJS __dirname without an ESM fallback, and tsx treats a file as
ESM once the nearest package.json sets "type": "module". Every script
failed with `ReferenceError: __dirname is not defined`, no *.messages.ts
files got generated, and packages/nimbus's build then failed with
~36 "Cannot find module '*.messages'" errors.

Fix by reverting the package-wide "type": "module" and instead
renaming just the offending file to locales.mts (same approach already
used for the root-level vitest configs), which makes Vite's native
config loader treat it as ESM without touching how tsx resolves every
other file in the package. Updated the file's extensionless importers
(compile-component-messages.ts, extract-messages.ts,
generate-dictionaries.ts, split-by-component.ts) to the explicit
.mts extension, since tsx's CJS-mode resolver doesn't probe for .mts
on extensionless specifiers. Also updated the one cross-package import
in packages/nimbus/vite.config.ts and doc references
(packages/i18n/CLAUDE.md, packages/i18n/README.md).

Verified: pnpm --filter @commercetools/nimbus-i18n build succeeds,
pnpm --filter @commercetools/nimbus build succeeds (the exact command
that failed in CI), and the unit/unit-isolated/ts-plugin/nimbus-mcp/
scripts vitest projects all pass (2019 tests).

Author: ByronDWall

docs/file-type-guidelines/unit-testing.md

@@ -44,7 +44,7 @@ See [Testing Strategy Guide](./testing-strategy.md) for detailed rules.
 The project uses **Vitest** with two separate test projects:
 
 ```typescript
-// vitest.config.ts - Root orchestrator
+// vitest.config.mts - Root orchestrator
 export default defineConfig({
   test: {
     projects: [

package.json

@@ -34,8 +34,8 @@
     "test": "pnpm vitest run",
     "test:unit": "pnpm vitest run --project=unit",
     "test:storybook": "pnpm vitest run --project=storybook",
-    "test:dev": "pnpm vitest run --config vitest.dev.config.ts",
-    "test:storybook:dev": "pnpm vitest run --config vitest.dev.config.ts --project=storybook-dev",
+    "test:dev": "pnpm vitest run --config vitest.dev.config.mts",
+    "test:storybook:dev": "pnpm vitest run --config vitest.dev.config.mts --project=storybook-dev",
     "check:bundle-size": "node .github/actions/bundle-size/check-bundle-size.mjs",
     "check:package-shape": "node scripts/check-package-shape.mjs",
     "bundle-sizes:trend": "node scripts/bundle-sizes-trend.mjs"

…/design-token-ts-plugin/vitest.config.ts …design-token-ts-plugin/vitest.config.mtspackages/design-token-ts-plugin/vitest.config.ts renamed to packages/design-token-ts-plugin/vitest.config.mts packages/design-token-ts-plugin/vitest.config.ts renamed to packages/design-token-ts-plugin/vitest.config.mts

@@ -68,7 +68,7 @@ packages/i18n/
 │   ├── split-by-component.ts
 │   ├── compile-component-messages.ts
 │   ├── generate-dictionaries.ts
-│   └── locales.ts
+│   └── locales.mts
 ├── .temp/             # Temporary build artifacts (gitignored)
 │   └── by-component/  # Messages grouped by component
 ├── package.json
@@ -286,7 +286,7 @@ from the generated `*.messages.ts` files.
 
 ## Supported Locales
 
-Available locales (defined in `scripts/locales.ts`):
+Available locales (defined in `scripts/locales.mts`):
 
 - `en` - English
 - `de` - German
@@ -300,7 +300,7 @@ English for unsupported locales.
 
 To add a new locale:
 
-1. Add locale code to `scripts/locales.ts`
+1. Add locale code to `scripts/locales.mts`
 2. Create `data/[locale].json` file with Transifex translations
 3. Update Vite config's `optimize-locales-plugin` to include new locale
 4. Run build to compile: `pnpm --filter @commercetools/nimbus-i18n build`

packages/i18n/CLAUDE.md

@@ -33,7 +33,7 @@ This is an **internal build tool package** that:
 ### Locale Configuration
 
 **Single Source of Truth:** All supported locales are defined in
-`packages/i18n/scripts/locales.ts` and shared between the build scripts and the
+`packages/i18n/scripts/locales.mts` and shared between the build scripts and the
 Vite config (`optimize-locales-plugin`).
 
 ### Build Pipeline

packages/i18n/README.md

@@ -32,7 +32,7 @@ import { compileStrings } from "@internationalized/string-compiler";
 import fs from "fs/promises";
 import path from "path";
 import { format } from "prettier";
-import { LOCALE_CODES } from "./locales";
+import { LOCALE_CODES } from "./locales.mts";
 
 const LOCALES = LOCALE_CODES;
 

packages/i18n/scripts/compile-component-messages.ts

@@ -8,7 +8,7 @@
 import { glob } from "glob";
 import * as fs from "fs";
 import * as path from "path";
-import { LOCALE_CODES } from "./locales";
+import { LOCALE_CODES } from "./locales.mts";
 
 // Type definitions for message descriptors in .i18n.ts files
 type MessageDescriptor = {

packages/i18n/scripts/extract-messages.ts

@@ -37,7 +37,7 @@
 import fs from "fs/promises";
 import path from "path";
 import { format, resolveConfig } from "prettier";
-import { SUPPORTED_LOCALES } from "./locales";
+import { SUPPORTED_LOCALES } from "./locales.mts";
 
 const LOCALES = SUPPORTED_LOCALES;
 

packages/i18n/scripts/generate-dictionaries.ts

@@ -42,7 +42,7 @@
 
 import fs from "fs/promises";
 import path from "path";
-import { LOCALE_CODES } from "./locales";
+import { LOCALE_CODES } from "./locales.mts";
 
 const LOCALES = LOCALE_CODES;