Repository navigation
perf: reuse pending list-marker matches #40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft
tannerlinsley
wants to merge
1
commit into
main
Choose a base branch
from
taren/reuse-pending-list-marker
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "@tanstack/markdown": patch | ||
| --- | ||
|
|
||
| Reuse pending list-marker matches while parsing list items. |
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
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
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Script executed:
rg -n 'size|limit|budget|ceiling|parser' scripts/measure-size.ts package.jsonRepository: TanStack/markdown
Length of output: 875
Script executed:
Repository: TanStack/markdown
Length of output: 13120
Script executed:
Repository: TanStack/markdown
Length of output: 13080
Script executed:
Repository: TanStack/markdown
Length of output: 11870
Script executed:
Repository: TanStack/markdown
Length of output: 1141
Shrink the parser change or approve a higher parser budget.
The parser-only bundle has about 1 byte of minified headroom. Its ceiling is 12649 bytes, and the committed report records 12648. The added marker-cache branch adds emitted code, so the
verifyjob will likely fail intests/bundle-size.test.ts. Brotli has no headroom.Possible approaches
listMarkerpath or the extra locals.tests/bundle-size.test.ts. Do not change the ceiling without that approval.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Confirmed. The measured parser-only bundle is 12,711 bytes against the 12,649-byte ceiling. This is part of the exact owner decision already requested in the PR description. No approval has been received, and the budgets, draft status and this finding remain unchanged pending that decision.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tannerlinsley Understood. Your measurement confirms the parser-only bundle is 62 bytes over the current ceiling. The finding remains open pending the owner decision already requested in the PR description.
You are interacting with an AI system.