Skip to content

Worktree upgrade deps - #15

Open
Dictionar32 wants to merge 23 commits into
tailwnd-js-cssfrom
worktree-upgrade-deps
Open

Worktree upgrade deps#15
Dictionar32 wants to merge 23 commits into
tailwnd-js-cssfrom
worktree-upgrade-deps

Conversation

@Dictionar32

Copy link
Copy Markdown
Owner

No description provided.

Dictionar32 and others added 23 commits April 14, 2026 17:49
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
…r-ddd

Stabilize variant IDs & sanitize component names; add DDD API and harden Next/webpack loaders
- 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
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
@chatgpt-codex-connector

Copy link
Copy Markdown

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.

@vercel

vercel Bot commented Jun 24, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
css-in-rust-dashboard Ready Ready Preview, Comment Jun 24, 2026 10:26pm

@kilo-code-bot

kilo-code-bot Bot commented Jun 24, 2026

Copy link
Copy Markdown

Code Review Roast πŸ”₯

Verdict: 4 Issues Found | Recommendation: Address before merge

Overview

Severity Count
🚨 critical 1
⚠️ warning 1
πŸ’‘ suggestion 2
Issue Details (click to expand)
File Line Roast
package.json 239 React peer dependency jumped from >=18 to >=19 without migration path
packages/presentation/svelte/package.json 32 Svelte peer bumped from >=4 to >=5 β€” that's a major version leap
native/Cargo.toml 26 OXC parser 0.55 β†’ 0.137 is an 80-version leap, not a patch
packages/domain/compiler/package.json 36 oxc-parser optional dep 0.120 β†’ 0.137 skips semantic versioning

πŸ† Best part: The OXC AST parser upgrade actually fixes a real API mismatch β€” changing BindingPatternKind::BindingIdentifier to BindingPattern::BindingIdentifier shows the author did the work to migrate the code, not just bumping versions blindly.

πŸ’€ Worst part: React peer dependencies jumped from >=18 to >=19 across the entire monorepo. That's not a dependency upgrade, that's a forced migration. Users on React 18 will get hard failures, and there's no compatibility window. It's like upgrading a highway bridge by removing the old one first.

πŸ“Š 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)
  • package.json - React 18 β†’ 19 peer dep bump
  • packages/presentation/svelte/package.json - Svelte 4 β†’ 5 peer dep bump
  • native/Cargo.toml - OXC 0.55 β†’ 0.137 upgrade
  • packages/domain/compiler/package.json - oxc-parser 0.120 β†’ 0.137
  • packages/domain/runtime-css/package.json - postcss ^8 β†’ ^8.5.15

Fix these issues in Kilo Cloud


Reviewed by laguna-m.1-20260312:free Β· Input: 2.5M Β· Output: 13.8K Β· Cached: 3.8M

Comment thread package.json
"peerDependencies": {
"react": ">=18",
"react-dom": ">=18"
"react": ">=19",

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ”₯ 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"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ”₯ 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.

Comment thread native/Cargo.toml
oxc_span = "0.55"
oxc_syntax = "0.55"
oxc_ast_visit = "0.55"
oxc_parser = "0.137"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ”₯ 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"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

πŸ”₯ 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.

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.

1 participant