Dunqing/typack - CodSpeed

typack

Performance History

Latest Results

chore: upgrade all dependencies to latest (#23) Rust crates: - oxc_* crates 0.115.0 -> 0.136.0 - oxc_resolver 11.19 -> 11.21, oxc_sourcemap 6 -> 8, oxc_index 4 -> 5 - napi 3.4 -> 3.9, napi-derive 3.2 -> 3.5, napi-build 2.1 -> 2.3 - codspeed-criterion-compat 4.3 -> 4.7 - Bump pinned toolchain 1.93.1 -> 1.94.0 (required by oxc 0.136) Code migration for the oxc API changes: - ParserReturn/IsolatedDeclarationsReturn/SemanticBuilderReturn `.errors` field replaced by `.diagnostics` (Diagnostics type); use has_errors() - `oxc_span::Ident` moved to `oxc_str::Ident` (added oxc_str dependency) - `SourceMap` now carries a lifetime; store owned `SourceMap<'static>` via into_owned() through the generate pipeline - Box the resolution Err and the SourceJoiner mapped variant to satisfy new clippy 1.94 result_large_err / large_enum_variant lints - Refresh real-world snapshots for codegen mapped-type formatting (`] :` -> `]:`) and a newly preserved JSDoc comment npm packages (latest across workspace): bumpp 11, monaco-editor 0.55, splitpanes 4, @vitejs/plugin-vue 6, tailwindcss 4.3, typescript 6, vite 8, wrangler 4.101, @napi-rs/cli 3.7, emnapi 1.11 Claude-Session: https://claude.ai/code/session_01XpWCTwYxQ7UUf7mpdG1835 Co-authored-by: Claude <noreply@anthropic.com>

main

4 months ago

chore: upgrade all dependencies to latest Rust crates: - oxc_* crates 0.115.0 -> 0.136.0 - oxc_resolver 11.19 -> 11.21, oxc_sourcemap 6 -> 8, oxc_index 4 -> 5 - napi 3.4 -> 3.9, napi-derive 3.2 -> 3.5, napi-build 2.1 -> 2.3 - codspeed-criterion-compat 4.3 -> 4.7 - Bump pinned toolchain 1.93.1 -> 1.94.0 (required by oxc 0.136) Code migration for the oxc API changes: - ParserReturn/IsolatedDeclarationsReturn/SemanticBuilderReturn `.errors` field replaced by `.diagnostics` (Diagnostics type); use has_errors() - `oxc_span::Ident` moved to `oxc_str::Ident` (added oxc_str dependency) - `SourceMap` now carries a lifetime; store owned `SourceMap<'static>` via into_owned() through the generate pipeline - Box the resolution Err and the SourceJoiner mapped variant to satisfy new clippy 1.94 result_large_err / large_enum_variant lints - Refresh real-world snapshots for codegen mapped-type formatting (`] :` -> `]:`) and a newly preserved JSDoc comment npm packages (latest across workspace): bumpp 11, monaco-editor 0.55, splitpanes 4, @vitejs/plugin-vue 6, tailwindcss 4.3, typescript 6, vite 8, wrangler 4.101, @napi-rs/cli 3.7, emnapi 1.11 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01XpWCTwYxQ7UUf7mpdG1835

claude/upgrade-all-deps-np752m

4 months ago

feat: keep `export` on declarations in DTS bundler output Instead of always splitting `export interface Foo {}` into `interface Foo {}; export { Foo };`, preserve the inline `export` keyword on entry module declarations when no renaming occurs. This matches TypeScript's own `.d.ts` output format. The decision is made at render time via a precomputed per-entry `entry_can_keep_exports` flag (O(1) check). Exports are kept inline when: the module is the entry, not namespace-wrapped, and has no symbol or fallback renames. Otherwise the existing split form is preserved. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

feat/keep-export-on-declarations

7 months ago

feat/keep-export-on-declarations

7 months ago

release: napi v0.3.0

main

7 months ago

feat: support .ts entry points via Oxc IsolatedDeclarations (#21) * feat: support `.ts` entry points via Oxc IsolatedDeclarations When a `.ts` file is encountered as an entry or dependency, it is transformed to `.d.ts` in-memory using Oxc's IsolatedDeclarations before bundling. The source `.ts` must conform to TypeScript's `isolatedDeclarations` constraints. - Add `oxc_isolated_declarations` dependency - Add `tsconfig.rs` module for reading `isolatedDeclarations` and `stripInternal` from tsconfig.json (with comment stripping) - Extract `parse_module()` from `add_module()` to handle both `.d.ts` (parse as-is) and `.ts` (parse → ID → codegen → re-parse) - Add `--tsconfig <PATH>` CLI flag and `tsconfig` API option (relative paths resolved against `cwd`) - Emit warning when `.ts` files used without `isolatedDeclarations` enabled in tsconfig - Update napi bindings with `tsconfig` option - Add dedicated README section for `.ts` entry point support - Add benchmark for `.ts` entry bundling Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: address PR review comments for .ts entry support - Scope `find_bool_field` to `compilerOptions` block via `extract_compiler_options()` - Return `Result` from `ScanStage::new()` for explicit tsconfig errors - Replace `debug_assert!` with real error return for re-parsed .d.ts - Emit isolatedDeclarations warning for .ts dependencies, not just entries Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * test: add real-world .ts entry point tests Add integration tests that bundle actual .ts source files (vitest) through the IsolatedDeclarations transform path, validating parse, semantic, and export correctness. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix(repl): write default tsconfig.json so .ts entries work with IsolatedDeclarations Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> * fix: handle escaped quotes in tsconfig compilerOptions parser The `extract_compiler_options` escape handling used `continue` on `\\` but still processed the next byte normally, so `\"` inside a JSON string would incorrectly end the string and break brace-depth counting. Switched to an index-based loop that skips the character after `\\`. Also added a tsconfig.json to the benchmark fixture to suppress the unnecessary `isolatedDeclarations` warning during bench runs, and added unit tests for the escape handling edge cases. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>

main

7 months ago

fix: handle escaped quotes in tsconfig compilerOptions parser The `extract_compiler_options` escape handling used `continue` on `\\` but still processed the next byte normally, so `\"` inside a JSON string would incorrectly end the string and break brace-depth counting. Switched to an index-based loop that skips the character after `\\`. Also added a tsconfig.json to the benchmark fixture to suppress the unnecessary `isolatedDeclarations` warning during bench runs, and added unit tests for the escape handling edge cases. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

feat/ts-entry-isolated-declarations

7 months ago

fix(repl): write default tsconfig.json so .ts entries work with IsolatedDeclarations Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

feat/ts-entry-isolated-declarations

7 months ago

Latest Branches

+5%

chore: upgrade all dependencies to latest#23

4 months ago

7166bdc

claude/upgrade-all-deps-np752m

feat: keep `export` on declarations in DTS output#22

7 months ago

aa3dc81

feat/keep-export-on-declarations

-1%

feat: support .ts entry points via Oxc IsolatedDeclarations#21

7 months ago

4e67da4

feat/ts-entry-isolated-declarations

Home Terms Privacy Docs