update dependencies

[tomusdrw]

No description provided.

[netlify]

✅ Deploy Preview for pvm-debugger ready!

Name	Link
🔨 Latest commit	e66ffbf
🔍 Latest deploy log	https://app.netlify.com/projects/pvm-debugger/deploys/6924d01afaee2600084cc24c
😎 Deploy Preview	https://deploy-preview-453--pvm-debugger.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Important

Review skipped

Auto incremental reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

📝 Walkthrough

Walkthrough

Major dependency upgrades: React 18→19, Tailwind 3→4, Zod 3→4. Updated associated type declarations and API calls. Component prop types broadened from JSX.Element to ReactNode. CSS refactored from Tailwind @apply to explicit CSS variables. PostCSS config migrated to array-based plugin syntax. Documentation enhanced.

Changes

Cohort / File(s)	Summary
Dependency & Build Configuration package.json, postcss.config.js	Upgraded React (^18.x → ^19.0.0), Tailwind (^3.4.6 → ^4.1.17), Zod (^3.24.1 → ^4.1.13) with type declaration updates. PostCSS plugin config changed from object mapping to array-based instantiation.
Documentation AGENTS.md	Added explanatory sections and bullet points across Project Structure, Build Commands, Coding Style, Testing Guidelines, and Commit Guidelines.
Component Type Signature Updates src/components/ProgramEdit/index.tsx, src/packages/ui-kit/Header/index.tsx	Broadened startSlot and endSlot prop types from JSX.Element to ReactNode with corresponding imports.
Zod v4 API Migration src/components/ProgramLoader/loadingUtils.ts	Updated type imports to Zod v4 (ZodIssue, ZodSafeParseResult). Changed error handling from result.error.errors to result.error.issues. Added explicit type annotation to schema.
CSS & Styling Refactoring src/globals.css	Replaced Tailwind @apply directives with explicit CSS properties using CSS variables (border-color: hsl(var(--border)), background-color, color, font-family).
Ref Composition Refactor src/components/MemoryPreview/MemoryRangesRow.tsx	Introduced connectRefs callback to safely attach drag and drop refs only when row is not the last item, consolidating ref attachment logic.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~50–75 minutes

• React 19 compatibility: Verify all component behavior aligns with React 19 changes, especially regarding type exports and rendering APIs.
• Zod v4 migration in loadingUtils.ts: Confirm error path changes (issues vs errors) handle all validation scenarios correctly, particularly for file upload parsing.
• Tailwind 4 CSS output: Visually test src/globals.css changes to ensure explicit CSS properties produce identical styling; verify PostCSS plugin array order doesn't affect output.
• Drag-and-drop functionality: Test MemoryRangesRow ref composition to ensure drag/drop behavior remains intact when row is not last, and refs attach correctly.
• Cross-component type changes: Verify ReactNode broader type acceptance in ProgramEdit and Header doesn't introduce unintended flexibility or prop validation issues.

Possibly related PRs

• Add agents file #450: Updates AGENTS.md documentation with overlapping guidelines content.

Pre-merge checks and finishing touches

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	You can run @coderabbitai generate docstrings to improve docstring coverage.
Description check	❓ Inconclusive	No pull request description was provided by the author. While a description would be helpful, the changes are extensive enough that evaluation is inconclusive without one.	Provide a description explaining the rationale for these dependency upgrades, any breaking changes addressed, and migration notes for React 19, Zod 4, and Tailwind 4.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'update dependencies' is directly related to the main changeset, which involves upgrading React, Zod, Tailwind, TypeScript types, and other dependencies.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

package.json (1)

74-87: Replace @tailwind directives with @import statement and verify space utility layouts in Tailwind 4.

In Tailwind CSS v4, the @tailwind directives (base, components, utilities) are removed and replaced with a single @import "tailwindcss" statement. This is found in src/globals.css lines 3-5 and must be updated.

Additionally, space utility selectors have changed in Tailwind 4 from applying margins to the top of every sibling except the first, to applying margins to the bottom of every sibling except the last. This change affects combinations like space-y with labels and inputs used in shadcn/ui patterns. The following files contain space utilities that may experience layout regressions and should be tested:

• src/components/ui/dialog.tsx (space-y-1.5, space-x-2)
• src/components/ui/card.tsx (space-y-1.5)
• src/components/NumeralSystemSwitch/index.tsx (space-x-2)
• src/components/MemoryPreview/MemoryRangesRow.tsx (space-y-1)
• src/components/ProgramEdit/index.tsx (space-x-2)
• src/components/ProgramLoader/ProgramFileUpload.tsx (space-x-6, space-x-2)

Use the automated upgrade tool (npx @tailwindcss/upgrade@next) to handle most migration changes.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 972b21a and 05b9bca.

⛔ Files ignored due to path filters (1)

• package-lock.json is excluded by !**/package-lock.json

📒 Files selected for processing (8)

• AGENTS.md (2 hunks)
• package.json (4 hunks)
• postcss.config.js (1 hunks)
• src/components/MemoryPreview/MemoryRangesRow.tsx (4 hunks)
• src/components/ProgramEdit/index.tsx (1 hunks)
• src/components/ProgramLoader/loadingUtils.ts (3 hunks)
• src/globals.css (1 hunks)
• src/packages/ui-kit/Header/index.tsx (1 hunks)

🧰 Additional context used

🧬 Code graph analysis (2)

src/packages/ui-kit/Header/index.tsx (1)

src/components/Header/index.tsx (1)

• Header (101-103)

src/components/ProgramLoader/loadingUtils.ts (1)

src/components/ProgramLoader/types.ts (1)

• ProgramUploadFileInput (12-37)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: test

🔇 Additional comments (11)

postcss.config.js (1)

1-6: LGTM! Correct migration to Tailwind 4 PostCSS plugin syntax.

The shift from object-based to array-based plugin configuration aligns with Tailwind 4's requirements. The imports are correctly added and the plugins are instantiated as functions.

src/packages/ui-kit/Header/index.tsx (1)

15-17: LGTM! Improved prop typing with ReactNode.

Broadening the endSlot prop from JSX.Element to ReactNode provides better flexibility and aligns with React 19 best practices. The change is backwards compatible with existing usage.

src/components/ProgramEdit/index.tsx (1)

9-11: LGTM! Consistent prop typing improvement.

The startSlot prop type change from JSX.Element to ReactNode mirrors the pattern in Header component and provides better type flexibility. This aligns with React 19 conventions.

src/globals.css (1)

95-101: LGTM! Correct migration away from @apply directives.

Replacing Tailwind's @apply with explicit CSS values using CSS variables is required for Tailwind 4. The hsl(var(--variable)) pattern correctly applies the theme tokens, and the font family declaration is properly structured.

src/components/MemoryPreview/MemoryRangesRow.tsx (2)

67-92: LGTM! Improved ref composition for React 19 compatibility.

The refactoring from chained refs (ref(drop(node))) to a connectRefs callback is a cleaner pattern that works better with React 19's ref handling. The explicit separation of dragRef and dropRef, combined with the conditional attachment logic, makes the code more maintainable and avoids potential ref conflicts.

---

125-125: LGTM! Card ref correctly uses the new callback pattern.

The Card component now uses ref={connectRefs} which properly integrates the drag-and-drop functionality through the new ref composition approach.

src/components/ProgramLoader/loadingUtils.ts (3)

4-10: LGTM! Correct Zod 4 type migration.

The import changes from SafeParseReturnType to ZodSafeParseResult and the addition of ZodIssue align with Zod 4's updated API. The ValidationResult type is correctly updated to use the new type.

---

24-24: LGTM! Explicit schema typing improves type safety.

Adding the explicit type annotation z.ZodType<ProgramUploadFileInput> ensures the schema structure matches the expected type, providing better type checking and IDE support.

---

143-146: LGTM! Correct Zod 4 error handling update.

The change from result.error.errors to result.error.issues is required for Zod 4. The ZodIssue type annotation on the err parameter provides proper typing for the error mapping function.

AGENTS.md (1)

1-26: LGTM! Documentation updates align with project changes.

The documentation cleanly reflects the current project structure and development workflow. The minor formatting adjustments improve readability without changing the core guidance.

package.json (1)

59-59: Zod v4 compatibility verified—no breaking changes detected.

The codebase is already fully compatible with Zod v4.1.13. The only Zod usage is in src/components/ProgramLoader/loadingUtils.ts, which correctly uses:

• ZodSafeParseResult type (correct for v4)
• .safeParse() validation
• .error.issues for error handling (the correct pattern in v4, not the deprecated .error.errors)

None of the common breaking changes from Zod v3→v4 were found in the codebase. The upgrade is safe.