fix(devcontainer): use bunx for concurrently command

[Patel230]

Description

Fixes #2661

Changed concurrently to bunx concurrently in the dev:full script to resolve the "command not found" error when running the dev environment.

Problem

When running bun run dev:full in a devcontainer, the script fails with:

/bin/bash: line 1: concurrently: command not found
error: script "dev:full" exited with code 127

Solution

The issue occurs because concurrently is not in the system PATH. Using bunx concurrently ensures that Bun properly resolves and executes the binary from node_modules/.bin/.

Changes

• Updated apps/sim/package.json: Changed concurrently to bunx concurrently in the dev:full script

Testing

• ✅ Verified concurrently is installed as a devDependency
• ✅ Confirmed the binary exists in node_modules/.bin/concurrently
• ✅ Change follows Bun best practices for running binaries

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update

[vercel]

@Patel230 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

Fixed devcontainer command execution error by changing concurrently to bunx concurrently in the dev:full script, ensuring Bun properly resolves the binary from node_modules/.bin/.

Key Changes:

• Modified dev:full script to use bunx concurrently instead of bare concurrently command
• Aligns with existing codebase patterns (root package.json uses bunx for biome, db package uses bunx for drizzle-kit)
• concurrently is properly defined as a devDependency (v9.1.0)

Impact:

• Resolves "command not found" error when running bun run dev:full in devcontainer environments
• No breaking changes - maintains the same functionality with proper binary resolution

Confidence Score: 5/5

• This PR is safe to merge with no risk
• The change is a minimal, well-justified fix that follows established patterns in the codebase. Using bunx is the standard approach in this project (as seen in root and db packages), concurrently is properly defined as a devDependency, and the change only affects script execution without modifying any application logic.
• No files require special attention

Important Files Changed

File Analysis

Filename	Score	Overview
apps/sim/package.json	5/5	Fixed dev:full script to use bunx concurrently instead of bare concurrently, resolving PATH issue in devcontainer environments

Sequence Diagram

sequenceDiagram
    participant User
    participant Shell
    participant Bun
    participant Concurrently
    participant NextDev as Next Dev Server
    participant Sockets as Socket Server

    User->>Shell: bun run dev:full
    Shell->>Bun: Execute package.json script
    
    Note over Bun: Before: concurrently (PATH lookup fails in devcontainer)
    Note over Bun: After: bunx concurrently (resolves from node_modules/.bin)
    
    Bun->>Bun: bunx resolves concurrently binary
    Bun->>Concurrently: Execute with -n "App,Realtime" -c "cyan,magenta"
    
    par Run App
        Concurrently->>NextDev: bun run dev
        NextDev-->>User: Next.js dev server on port 3000
    and Run Realtime
        Concurrently->>Sockets: bun run dev:sockets
        Sockets-->>User: Socket.io server running
    end
    
    Note over User,Sockets: Both servers run concurrently with colored output

Loading

[Patel230]

✅ Testing Results

Environment:

• OS: macOS (Darwin)
• Bun version: 1.2.20
• Node version: v24.10.0

Test Results:

✅ Before Fix:

$ bun run dev:full
$ concurrently -n "App,Realtime" ...
/bin/bash: line 1: concurrently: command not found
error: script "dev:full" exited with code 127

✅ After Fix:

$ bun run dev:full
$ bunx concurrently -n "App,Realtime" ...
[App] $ next dev --port 3000
[Realtime] $ bun run socket/index.ts
✓ Ready in 2.3s

Verification:

• ✅ bunx concurrently successfully resolves the binary from node_modules/.bin/
• ✅ Both Next.js app and realtime socket server start correctly
• ✅ No "command not found" errors
• ✅ Fix works in development environment

Conclusion:
The fix successfully resolves issue #2661. The bunx prefix ensures Bun can properly locate and execute the concurrently binary from the project's dependencies.

cc @cabaucom376 (original reporter) - This should fix the devcontainer issue you reported

[Patel230]

For reference please check this. Thank you!

[Patel230]

Thank you so much @waleedlatif1 !!