Worktree upgrade deps - #15
Conversation
BREAKING CHANGES: - Fix E0432: replace oxc_ast::Visit with oxc_ast_visit::Visit in oxc_parser - Migrate next.config.ts to next.config.mjs in examples Features: - Add new native architecture layers (application, domain, infrastructure, interface, shared) - Add native tests module - Add new scripts for v45 and v49 migrations - Add package-lock.json for next-js-app example Improvements: - Update native build configuration (build.rs) - Add Cargo.lock for native module - Update all domain packages (analyzer, core, engine, preset, runtime-css, scanner, shared) - Update infrastructure packages (cli, devtools, studio-desktop, vscode) - Update presentation packages (next, rspack, vite) - Update validation scripts and TypeScript configurations Dependencies: - Update package.json dependencies - Update tsup.config.ts configuration - Update tsconfig.json
feat: major update with oxc_parser fix and new native architecture
add(lib.rs/original)
β¦r-ddd Stabilize variant IDs & sanitize component names; add DDD API and harden Next/webpack loaders
Tailwnd js
- Rename and move css_resolver to application/legacy_part - Add service layer and adapters across domain, infrastructure, and interface - Add test modules for improved test coverage
refactor: restructure codebase following cleaner architecture
- Add lazy-loading for Node.js built-ins in @tailwind-styled/shared - Use --external node:* in tsup build to prevent bundling - Fix Windows path handling in @tailwind-styled/next - Fix exports configuration in package.json files - Add .mjs extension support for loader resolution - Fix file:// URL parsing on Windows (file:///C:/ paths)
fix: make @tailwind-styled packages browser-compatible
- Add externals configuration for @tailwind-styled packages in webpack - Use createRequire(import.meta.url) for lazy Node.js module loading - Fix path handling for Windows file:// URLs - Add .mjs extension support for loader resolution
Tailwnd js
chore: update workflow, configs, and scanner module
- Add tailwind engine compiler - Add type generation utilities - Update native Rust bindings - Add diagnostic suppressor for VSCode - Update workspace settings provider
- Merge atomic CSS parser and compiler into native engine - Implement cascade resolver for conflicting atomic rules - Add cache resolver for atomic class caching and deduplication - Integrate plugin registry for atomic processing pipeline - Update theme system with atomic value mapping - Complete native bridge for atomic CSS generation - Add impact analysis and scoring for atomic rules - Implement ID registry for atomic class tracking - Update workspace analyzer with atomic detection - Enhance semantic analysis for atomic class extraction - Complete integration of all domain modules with atomic support
- Update Rust dependencies in Cargo.lock and Cargo.toml (autocfg, bitflags, bitvec, bumpalo, bytes, compact_str, ctor, dashmap, and others) - Remove unused dependencies: anyhow, assert-unchecked, ctor-proc-macro, dtor, and dtor-proc-macro - Add new dependency: dragonbox_ecma 0.1.12 - Update npm/yarn dependencies across all workspace packages (domain, infrastructure, and presentation layers) - Bump package versions in analyzer, animate, atomic, compiler, core, engine, plugin-registry, plugin, preset, runtime-css, runtime, scanner, shared, testing, and theme packages - Update infrastructure packages: cli, dashboard, devtools, storybook-addon, studio-desktop, and vscode - Update presentation layer packages: next, rspack, svelte, vite, and vue - Improve dependency management by removing deprecated proc-macro crates and consolidating versions
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Code Review Roast π₯Verdict: 4 Issues Found | Recommendation: Address before merge Overview
Issue Details (click to expand)
π Best part: The OXC AST parser upgrade actually fixes a real API mismatch β changing π Worst part: React peer dependencies jumped from π Overall: Like finding a Ferrari engine in a Honda Civic β technically impressive upgrade, but you might not be able to drive it home if you're still on the old tires. Files Reviewed (5 files)
Fix these issues in Kilo Cloud Reviewed by laguna-m.1-20260312:free Β· Input: 2.5M Β· Output: 13.8K Β· Cached: 3.8M |
| "peerDependencies": { | ||
| "react": ">=18", | ||
| "react-dom": ">=18" | ||
| "react": ">=19", |
There was a problem hiding this comment.
π₯ The Roast: React peer dependency jumped from >=18 to >=19 without any migration grace period. It's like throwing a party and only inviting people who bought the latest outfit.
π©Ή The Fix: Consider using >=18 for broader compatibility β React 19 is still rolling out and many apps won't have migrated yet.
π Severity: suggestion
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| "devDependencies": { | ||
| "svelte": "^5.56.3", | ||
| "tsup": "^8.0.0", | ||
| "typescript": "^6" |
There was a problem hiding this comment.
π₯ The Roast: Svelte peer dependency rocketed from >=4.0.0 to >=5.0.0. That's not a minor upgrade, that's a major version cliff dive.
π©Ή The Fix: Keep compatibility with older Svelte versions using >=4.0.0 <6.0.0 or document the breaking change clearly.
π Severity: warning
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| oxc_span = "0.55" | ||
| oxc_syntax = "0.55" | ||
| oxc_ast_visit = "0.55" | ||
| oxc_parser = "0.137" |
There was a problem hiding this comment.
π₯ The Roast: OXC parser jumped from 0.55 to 0.137 β that's not semantic versioning, that's semantic chaos. An 80-version leap in one PR is either a time machine or a typo.
π©Ή The Fix: This massive version jump should be documented with migration notes. At minimum, pin to known working versions while testing compatibility.
π Severity: suggestion
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
| "inversify": "^8.1.1", | ||
| "postcss": "^8.5.15", | ||
| "reflect-metadata": "^0.2.2", | ||
| "zod": "^4.3.6" |
There was a problem hiding this comment.
π₯ The Roast: The optional oxc-parser dependency went from ^0.120.0 to ^0.137.0 β another 17-version skip. Pre-release versioning (0.x) doesn't give you a free pass to break semver conventions.
π©Ή The Fix: Use >=0.120.0 <0.140.0 or document why the specific version range is required.
π Severity: suggestion
Reply with @kilocode-bot fix it to have Kilo Code address this issue.
No description provided.