Skip to content

chore: export internal components - #1022

Open
avivkeller wants to merge 1 commit into
mainfrom
export-internals
Open

chore: export internal components#1022
avivkeller wants to merge 1 commit into
mainfrom
export-internals

Conversation

@avivkeller

Copy link
Copy Markdown
Member

As titled; consumers may want to monkey patch these components

@avivkeller
avivkeller requested a review from a team as a code owner August 10, 2026 14:37
@vercel

vercel Bot commented Aug 10, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
api-docs-tooling Ready Ready Preview Aug 10, 2026 2:38pm

Request Review

@codecov

codecov Bot commented Aug 10, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.43%. Comparing base (f46a0bd) to head (6ebf786).

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1022   +/-   ##
=======================================
  Coverage   89.43%   89.43%           
=======================================
  Files         203      203           
  Lines       18871    18871           
  Branches     1763     1763           
=======================================
  Hits        16878    16878           
  Misses       1986     1986           
  Partials        7        7           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@github-actions

Copy link
Copy Markdown
Contributor

api-links Generator

Performance estimate (single CI run)

  • Generation time: 6.3% slower (1.26 s → 1.34 s)
  • Peak memory: 2.7% lower (364.31 MB → 354.43 MB)

legacy-html Generator

Performance estimate (single CI run)

  • Generation time: 3.1% faster (19.19 s → 18.59 s)
  • Peak memory: 4.5% lower (2.41 GB → 2.30 GB)

legacy-json Generator

Performance estimate (single CI run)

  • Generation time: 3.2% faster (9.19 s → 8.90 s)
  • Peak memory: 8.9% lower (1.79 GB → 1.63 GB)

llms-txt Generator

Performance estimate (single CI run)

  • Generation time: 24.1% faster (8.31 s → 6.31 s)
  • Peak memory: 33.5% higher (1.61 GB → 2.15 GB)

orama-db Generator

Output size: 1 file changed · net +1.00 B

File size details
File Main PR Change
orama-db.json 9.07 MB 9.07 MB +1.00 B (+0.0%)

Performance estimate (single CI run)

  • Generation time: 4.8% slower (8.32 s → 8.72 s)
  • Peak memory: 0.4% higher (1.78 GB → 1.78 GB)

web Generator

Output size: 1 file changed · net +44.00 B

File size details
File Main PR Change
all.html 31.54 MB 31.54 MB +44.00 B (+0.0%)

Performance estimate (single CI run)

  • Generation time: 0.6% faster (85.76 s → 85.23 s)
  • Peak memory: 0.6% higher (4.76 GB → 4.78 GB)

@ovflowd

ovflowd commented Aug 10, 2026

Copy link
Copy Markdown
Member

As titled; consumers may want to monkey patch these components

Monkey-patch or extend?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants