perf(dev): improve cold start of dev server#902
Conversation
Bundle Stats — create-nuxt size comparisonHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded
Removed
Bigger
Smaller
Unchanged
|
Bundle Stats — nuxt-cli size comparisonHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded
Removed
Bigger
Smaller
Unchanged
|
Bundle Stats — nuxi size comparisonHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded
Removed
Bigger
Smaller
Unchanged
|
commit: |
CodSpeed Performance ReportMerging #902 will improve performances by ×2.5Comparing Summary
Benchmarks breakdown
|
🔗 Linked issue
❓ Type of change
📚 Description
this is a set of changes aimed to improve the cold start of the dev server, including using a standalone entrypoint file instead of
nuxi _dev, usingexsolvefor module resolution, starting fork 'earlier' in the process, and deduplicating some code for more consistencyin addition, we now start for the first time in no-fork mode, while creating a pre-warmed fork ready to go if we need to hard-restart.
Important
this does not scale linearly with your project size - the improvements here are shaving off time to the fixed time that
nuxt devtakes to initialise