fix(config): detect vite.config.c[jt]s

[NaufalK25]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation, readme, or JSdoc annotations)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality like performance)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

• resolveBuilder's hasNitroViteConfig() only checked vite.config.{ts,mts,js,mjs} when auto-detecting the vite builder, missing .cjs/.cts configs.
• Vite itself already resolves vite.config.cjs and vite.config.cts as first-class config files (see DEFAULT_CONFIG_FILES in vite's constants.ts, and the Vite config docs: "other JS and TS extensions are also supported"). Nitro's own builder detection was just out of sync with that list.
• Added .cjs and .cts to configExts so a vite.config.cjs/.cts containing the nitro() plugin is now correctly detected and builder defaults to "vite".

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[vercel]

@NaufalK25 is attempting to deploy a commit to the Nitro Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

📝 Walkthrough

Walkthrough

hasNitroViteConfig in src/config/resolvers/builder.ts gains two additional Vite config file extensions — .cts and .cjs — expanding configExts from four entries to six to cover CommonJS TypeScript and JavaScript variant filenames.

Changes

Vite Config Extension Detection

Layer / File(s)	Summary
Add .cts and .cjs to configExts src/config/resolvers/builder.ts	configExts in hasNitroViteConfig is extended with ".cts" and ".cjs", so projects using those Vite config file extensions are now detected.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• nitrojs/nitro#4058: Introduced hasNitroViteConfig with the original multi-extension scanning logic that this PR extends with .cts/.cjs.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description is related to the changeset, explaining why .cjs and .cts support was added to align with Vite's configuration file resolution.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Title check	✅ Passed	The pull request title 'fix(config): detect vite.config.c[jt]s' follows the conventional commits format with a 'fix' type and descriptive scope.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[pi0]

Thnx!