Add note about Vite .mts ESM syntax support

[pwizla]

This PR updates documentation based on strapi/strapi#25238.

Adds a new TabItem example showing .mts ESM syntax for Vite configuration, along with a note explaining that ESM syntax is now supported and recommended.

Generated automatically by the docs self-healing workflow (micro-edit, Haiku).
Review before merging.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
documentation	Ready	Preview, Comment	Apr 22, 2026 10:08am

[strapi-cla]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ pwizla
❌ github-actions[bot]
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[pwizla]

After reviewing the source PR (strapi/strapi#25238) and checking the Vite documentation and Strapi codebase, here are some concerns about the third "TypeScript (ESM)" tab:

The code is identical across the TypeScript and TypeScript (ESM) tabs. The only difference is the filename (vite.config.ts → vite.config.mts). Both use the same import/export ESM syntax. A dedicated tab for identical code with just a different extension adds UI noise without adding clarity.

The claim "CJS is being phased out by Vite" is misleading. The official Vite config docs (vite.dev/config) still recommend vite.config.js and vite.config.ts as primary options. CJS is not formally deprecated for config files.

Potential loader issue in Strapi. The USER_CONFIGS array was updated to include vite.config.mts, but the loadFile function in packages/core/strapi/src/node/core/files.ts registers esbuild with extensions ['.js', '.mjs', '.ts'] — .mts is not explicitly included. This may cause issues in practice.

Proposed changes:

• Remove the third tab
• Replace with a short tip/note mentioning .mts support for users who need explicit ESM module resolution in their package.json
• Remove the :::info admonition about CJS being phased out (unsupported claim)

[pwizla]

Correction to my earlier comment: Vite 6 does deprecate the CJS Node API (see Vite 6 troubleshooting), so the direction is real. However, Strapi currently ships with Vite 5.4.21, where CJS is not deprecated.

The .mts support is worth documenting as a forward-looking option, but calling it "the recommended approach" is premature while Strapi runs on Vite 5. I've updated the tip in the code to reflect this nuance.

[pwizla]

Now fully approved ✅