Repository navigation
docs: import languages from the shared entry - #14
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
595a59e to
4dc34fa
Compare
|
@coderabbitai review |
|
@codex review |
|
4dc34fa to
c9a031c
Compare
|
Codex Review: Didn't find any major issues. 👍 Reviewed commit: ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
3b71429 to
9bd13da
Compare
Examples and the docs site import definitions from @vortexlabs/kirari/languages. Bundlers keep only the imported definitions, so bundle sizes are unchanged. Per-file paths stay documented for use without a bundler.
9bd13da to
ba7c183
Compare
What and why
Docs examples, the READMEs, and the docs site import language definitions from the shared entry:
Bundlers keep only the imported definitions, so bundle sizes do not change: a
tokenize+pythonbundle is 6,713 bytes gzip with either import path. The languages page now lists export names, notes that per-file paths such as@vortexlabs/kirari/languages/pythonremain for use without a bundler, and the API page lists the./languagesentry.Stacked on #13.
Checklist
bun run checkpassesbunx changeset), or not needed for docs, tests, or internal changes