Repository navigation
Conversation
📦 Bundle Stats —
|
| Metric | Value | vs main (89aa947) | vs v6.16.0 |
|---|---|---|---|
| Internal (raw) | 4.49 MB | - | +56.0 KB, +1.2% |
| Internal (gzip) | 1.12 MB | - | +19.5 KB, +1.7% |
| Bundled (raw) | 13.34 MB | - | +73.1 KB, +0.5% |
| Bundled (gzip) | 3.16 MB | - | +22.9 KB, +0.7% |
| Import time | 1.75s | +10ms, +0.5% | +22ms, +1.3% |
bin:sanity
| Metric | Value | vs main (89aa947) | vs v6.16.0 |
|---|---|---|---|
| Internal (raw) | 7.1 KB | - | - |
| Internal (gzip) | 2.9 KB | - | - |
| Bundled (raw) | 7.1 KB | - | - |
| Bundled (gzip) | 2.8 KB | - | - |
| Import time | 5ms | -0ms, -0.4% | +0ms, +4.0% |
🗺️ View treemap · Artifacts
Details
- Import time regressions over 10% are flagged with
⚠️ - Sizes shown as raw / gzip 🗜️. Internal bytes = own code only. Total bytes = with all dependencies. Import time = Node.js cold-start median.
ostenbom
marked this pull request as ready for review
September 29, 2026 13:45
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Compare the existing 29 auth scenarios on Playwright and Endform in CI, using the same production Studio build and GitHub runner type. The auth suite mocks its APIs, so this fork can establish a baseline without Sanity staging credentials or a Vercel deployment.
What to review
The auth job runs a Playwright/Endform matrix, with browser installation only for Playwright and verified GitHub OIDC authentication for Endform organization
2G1ZCj7X. Both runners retain failure traces and keep the existing one retry. Test files and documentation are unchanged.Testing
Both CI jobs passed on commit fcd88e5:
Endform CI dashboard. Endform's own suite timer reported 42.8s and 8.5 billable runner minutes. GitHub step durations above include CLI startup and server setup. Playwright also spent 23s installing Chromium in this first run.
The Playwright retry was
cookieAuth.spec.ts:52(login after logout syncs across tabs): the first attempt timed out clicking a hidden Sign out item at line 70. It passed on retry; the test was left unchanged. These are single-run measurements, and the retry affects the timing comparison.Locally, both runners passed all 29 tests with matching trace settings: Playwright took 13.92s total command time and Endform took 35.52s while forwarding to the Mac's preview server. Endform local run.
Formatting, lint, dependency checks, export tests and workflow security audit passed in CI. The main Studio/embedded workflows are outside this comparison and still need the fork's Sanity/Vercel configuration.
Notes for release
N/A – Internal only.