Serve marko's code-split runtime dist to the playground - #274
Conversation
|
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 18 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (6)
Comment |
PR Preview DeployedYour changes are live at markojs.com/previews/pr-274. commit bdc6d3e |
marko 6.3.33 builds each
*.featmodule as a separate entry, so the runtime dist is code-split andmarko/domimports a hashed chunk the playground could not resolve (it inlined only the four entry files). A build-time virtual module now captures the full runtime dist, and the playground resolves entries,*.featimports, and chunk-relative imports against it. A regression test asserts every import within the captured files resolves.