fix(api): added pkgs , socket server

[sundaram2021]

Summary

Brief description of what this PR does and why.
previously not able to run the cmd bun run dev:sockets in apps/sim .
Issuse was , some of the packages were not present in package.json.
So , I have added required packages in package.json

Fixes #(1782)

Type of Change

• [ x] Bug fix
• New feature
• Breaking change
• Documentation
• Other: ___________

Testing

How has this been tested? What should reviewers focus on?
Manually Tested

Checklist

• [x ] Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing
• No new warnings introduced
• [x ] I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

@sundaram2021 is attempting to deploy a commit to the Sim Team on Vercel.

A member of the Team first needs to authorize it.

[greptile-apps]

Greptile Overview

Greptile Summary

This PR resolves the runtime error when running bun run dev:sockets by adding missing package dependencies.

Key changes:

• Added [email protected] to dependencies - required by the logger used in the socket server (apps/sim/lib/logs/console/logger.ts:7)
• Added [email protected] to dependencies - explicitly declares state management library used across 27 files (was previously only available as a transitive peer dependency from reactflow)
• Removed dotenv from devDependencies - not used anywhere in the codebase, environment handling is done through the existing env module
• Added @types/[email protected] to packages/db devDependencies for proper TypeScript support
• Updated @types/node in the main app to 24.10.0 (from 22.18.7)

The changes are well-scoped and directly address the issue. The socket server at apps/sim/socket-server/index.ts imports a logger that depends on chalk, and the application's state management depends on zustand. Making these explicit dependencies ensures the socket server can run independently.

Confidence Score: 4/5

• This PR is safe to merge with minor testing recommended for zustand version compatibility
• The PR correctly identifies and adds missing dependencies (chalk and zustand) that were causing runtime errors. The changes are well-scoped and address the actual problem. However, adding [email protected] while reactflow uses zustand@^4.4.1 creates a dual-version scenario that should be tested, particularly for workflow state management functionality. The removal of unused dotenv is a positive cleanup.
• apps/sim/package.json - verify zustand version compatibility with reactflow after deployment

Important Files Changed

File Analysis

Filename	Score	Overview
apps/sim/package.json	4/5	Added [email protected] and [email protected] as dependencies, removed dotenv from devDependencies - resolves socket server runtime errors
packages/db/package.json	5/5	Added @types/[email protected] to devDependencies for proper TypeScript type support
bun.lock	5/5	Lockfile updated to reflect dependency changes - chalk, zustand, and @types/node version updates

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant BunCLI as bun run dev:sockets
    participant SocketServer as socket-server/index.ts
    participant Logger as lib/logs/console/logger.ts
    participant Chalk as [email protected]
    participant Stores as App Stores
    participant Zustand as [email protected]
    
    Dev->>BunCLI: Run socket server command
    BunCLI->>SocketServer: Execute index.ts
    SocketServer->>Logger: createLogger
    Logger->>Chalk: Import for colored logging
    Note over Chalk: Missing before PR - Added as dependency
    Chalk-->>Logger: Color formatting functions
    Logger-->>SocketServer: Logger instance
    SocketServer->>SocketServer: Initialize HTTP server
    Note over SocketServer: Server starts successfully
    Stores->>Zustand: Import for state management
    Note over Zustand: Was peer dependency - Now explicit
    Zustand-->>Stores: State management utilities

Loading

_{2 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[sundaram2021]

this fix already a part of this PR.
I have reviewed it and tested it manually , gave some suggestion .