Improved Ember dev server startup#27702
Conversation
Normal Ember dev server runs were building test and Mirage assets, which pulled large dev-only dependencies into the hot path. Keeping those assets behind an explicit opt-in reduces the default startup workload while preserving test builds.
|
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
WalkthroughThe pull request introduces centralized control for test asset inclusion in the build process. Two files are modified: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. 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. Comment |
- uses app.env for post-constructor test asset imports so they follow the generated build type instead of only the process environment
Summary
/testssupport available withEMBER_INCLUDE_TESTS=true.Why
ember servewas building test and Mirage assets by default in development, pulling large dev-only dependencies such as Faker into the default startup path. This keeps the normal dev server focused on the app graph while preserving explicit test-server support.Validation
ember serve --port 4210 --live-reload falseprofiling before and after the change.Build successful, ~19.8s profiled Ember build, 716 Broccoli steps, ~1.68 GB max RSS.