fix: npm dev launch

[ADITYA-tp01]

User description

Fixes Win32 error when starting dashboard via Start-Process.

---

CodeAnt-AI Description

Fix dashboard startup on Windows

What Changed

• Starts the dashboard development server through PowerShell to avoid the Windows launch error
• Opens the dashboard in its own terminal and keeps the server running from the correct project directory
• Continues to report the dashboard URL at http://localhost:3001

Impact

✅ Reliable Windows dashboard startup
✅ Fewer Win32 launch errors
✅ Dashboard server remains visible in its terminal

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codeant-ai]

🤖 CodeAnt AI — Review Status

Status	Commit	Started (UTC)	Finished (UTC)
✅ Reviewed your PR	32de3da	Aug 29, 2026 · 21:52	21:54

[codeant-ai]

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[qodo-code-review]

PR Summary by Qodo

Fix Windows dashboard development server launch

🐞 Bug fix 🕐 Less than 5 minutes

AI Description

• Launches the dashboard through PowerShell to avoid Windows Start-Process execution errors.
• Preserves the dashboard directory when starting the npm development server.

Diagram

graph TD
  Setup["Windows setup"] --> Shell["PowerShell child"] --> Npm["npm dev"] --> Dashboard["Dashboard server"]

Loading

High-Level Assessment

The following are alternative approaches to this PR:

1. Resolve npm.cmd directly

• ➕ Avoids creating an additional shell process
• ➕ Supports explicit working-directory and output-redirection options
• ➖ Requires careful npm shim discovery across Node installation managers
• ➖ May reintroduce Windows executable-resolution edge cases

Recommendation: The PowerShell wrapper is appropriate for this targeted Windows compatibility fix because it lets the shell resolve npm consistently and keeps the development process visible. Directly resolving npm.cmd would be preferable only if detached execution or log redirection becomes necessary.

Files changed (1) +1 / -1

Bug fix (1) +1 / -1

setup.ps1Launch dashboard npm command through PowerShell +1/-1

Launch dashboard npm command through PowerShell

• Replaces direct npm process startup with a child PowerShell command that changes to the dashboard directory and runs the development server. This avoids the Win32 error produced when Start-Process attempts to launch npm directly.

scripts/setup.ps1

[github-actions]

Failed to generate code suggestions for PR

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (1) 📘 Rule violations (0) 📜 Skill insights (0)

1. Apostrophe breaks dashboard launch 🐞 Bug ≡ Correctness

Description

The child command is built as cd '$PWD'; npm run dev, so a repository path containing an
apostrophe (for example, C:\Users\O'Brien\Mission-Control) produces invalid PowerShell syntax and
the dashboard never starts. Start-Process is asynchronous and the script does not validate the
child process before printing its startup message.

Code

scripts/setup.ps1[76]

+Start-Process powershell -ArgumentList "-NoExit", "-Command", "cd '$PWD'; npm run dev"

Relevance

●●● Strong

Accepted history flags closely related Windows launch and path-handling bugs; apostrophe quoting is
a deterministic startup failure.

PR-#5

ⓘ Recommendations generated based on similar findings in past PRs

Evidence

The changed line embeds the current directory in a single-quoted command string, where an apostrophe
terminates the literal and makes the generated command invalid. The surrounding script launches
asynchronously and only sleeps before printing its status, so this failure is not surfaced by setup.

scripts/setup.ps1[74-79]
README.md[66-68]
apps/dashboard/package.json[5-8]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The dashboard launch command interpolates `$PWD` inside a single-quoted PowerShell command. Paths containing apostrophes generate invalid child PowerShell syntax, so `npm run dev` does not start.

## Issue Context
The command runs while `Push-Location apps/dashboard` is active, then `Pop-Location` immediately follows. Preserve the intended dashboard working directory while avoiding unescaped path text in the child command.

## Fix Focus Areas
- scripts/setup.ps1[76-76]

Use `-WorkingDirectory` with the resolved dashboard path and pass only the npm arguments to the child process, or otherwise correctly escape/quote the path before invoking the nested PowerShell command. Ensure the startup failure is detectable rather than unconditionally reporting that the dashboard is starting.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Context sources

Review mode: 🚀 Fast: This is a localized one-line behavioral change in a PowerShell startup script, with limited scope and no security, data, API, or concurrency implications.

Tip of the day

💡 Did you know, you can group findings by type and pick your Finding display, from Minimal to Full

More tips ↗ | Customize Qodo ↗ | Qodo docs ↗

[qodo-code-review]

1. Apostrophe breaks dashboard launch 🐞 Bug ≡ Correctness

The child command is built as cd '$PWD'; npm run dev, so a repository path containing an
apostrophe (for example, C:\Users\O'Brien\Mission-Control) produces invalid PowerShell syntax and
the dashboard never starts. Start-Process is asynchronous and the script does not validate the
child process before printing its startup message.

Agent Prompt

## Issue description
The dashboard launch command interpolates `$PWD` inside a single-quoted PowerShell command. Paths containing apostrophes generate invalid child PowerShell syntax, so `npm run dev` does not start.

## Issue Context
The command runs while `Push-Location apps/dashboard` is active, then `Pop-Location` immediately follows. Preserve the intended dashboard working directory while avoiding unescaped path text in the child command.

## Fix Focus Areas
- scripts/setup.ps1[76-76]

Use `-WorkingDirectory` with the resolved dashboard path and pass only the npm arguments to the child process, or otherwise correctly escape/quote the path before invoking the nested PowerShell command. Ensure the startup failure is detectable rather than unconditionally reporting that the dashboard is starting.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

[codeant-ai]

Suggestion: The dashboard is launched asynchronously without capturing the process or checking its exit status, and the fixed delay does not verify that npm run dev successfully started or bound port 3001. Dependency, compilation, or port-binding failures are therefore reported as a successful dashboard startup. Start the process with observable error handling and poll the dashboard health endpoint before claiming it is available. [incomplete implementation]

Severity Level: Major ⚠️

- ❌ Windows setup hides dashboard startup failures.
- ⚠️ Users receive an unusable dashboard URL.
- ⚠️ Port conflicts and Next.js failures require manual diagnosis.

Prompt for AI Agent 🤖

This is a comment left during a code review.

**Path:** scripts/setup.ps1
**Line:** 76:76
**Comment:**
	*Incomplete Implementation: The dashboard is launched asynchronously without capturing the process or checking its exit status, and the fixed delay does not verify that `npm run dev` successfully started or bound port 3001. Dependency, compilation, or port-binding failures are therefore reported as a successful dashboard startup. Start the process with observable error handling and poll the dashboard health endpoint before claiming it is available.

Validate the correctness of the flagged issue. If correct, How can I resolve this? If you propose a fix, implement it and please make it concise.
Once fix is implemented, also check other comments on the same PR, and ask user if the user wants to fix the rest of the comments as well. if said yes, then fetch all the comments validate the correctness and implement a minimal fix

👍 | 👎