perf(nuxt): defer version/config checks to after vite build - #30567
Conversation
|
|
WalkthroughThe pull request introduces modifications to error handling and control flow in two core Nuxt files: In The changes enhance the testing coverage by introducing a new test suite for dependency version checks while removing an outdated test suite that previously handled dependency mismatches. 📜 Recent review detailsConfiguration used: CodeRabbit UI 📒 Files selected for processing (4)
💤 Files with no reviewable changes (1)
🚧 Files skipped from review as they are similar to previous changes (1)
🔇 Additional comments (7)
Finishing Touches
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
@nuxt/kit
@nuxt/rspack-builder
nuxt
@nuxt/schema
@nuxt/vite-builder
@nuxt/webpack-builder
commit: |
🔗 Linked issue
📚 Description
this slightly improves Nuxt startup performance by deferring the start of these checks until after a successful vite build.
(they were already non-blocking but might have contended for fs access)