fix(config): respect override dev value

[huang-julien]

🔗 Linked issue

📚 Description

Something I noticed while testing @nuxt/hints, setting dev in overrides doesn't work due to https://github.com/nuxt/nuxt/blob/d52a4fdd7ad5feb035dcf3f56c3b2d0ab059b1d4/packages/kit/src/loader/nuxt.ts#L24

[coderabbitai]

📝 Walkthrough

Walkthrough

The Nuxt config loader's dev flag resolution has been modified to derive its value from configuration overrides instead of always using false as a hardcoded default. If no override value is provided, it falls back to false. A reference comment to the Nuxt source has been added. This change affects the runtime behavior of Nuxt/Nitro config resolution without modifying exported function signatures or altering other configuration defaults.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description is directly related to the changeset, explaining the specific issue encountered and referencing the problematic behavior in Nuxt's loader that the fix addresses.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.
Title check	✅ Passed	The title directly reflects the main change: respecting the override dev value in the Nuxt config loader, which aligns perfectly with the PR's objective.

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

✨ Finishing Touches

• 📝 Generate docstrings (stacked PR)
• 📝 Generate docstrings (commit on current branch)

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix/respect_dev_option

---

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.}