start-dev-server

Step 0: Get User Preferences

• Ask the user if they want to start the dev server(s) as a background task in the current session, or on their own in a separate terminal:
  • Starting as a background task
    • Pros: The agent has more autonomy, can respond directly to dev server logs (warnings, errors).
    • Cons: Certain actions can be slower, and the user has less direct control. Server logs are only visibile to the user from within the background tasks tab.
  • Starting externally (User)
    • Pros: The user has more direct control over app development and the Wasp CLI commands. Can be advantageous for more advanced users.
    • Cons: Debugging and feature discovery can be slower, as the agent doesn't have direct access to dev server logs (warnings, errors) or Wasp CLI commands.
• Depending on the user's choice, follow the steps below and run the commands for the user as background tasks, or guide them through running them manually in a separate terminal.

Step 1: Prepare the Checkout

If node_modules is missing, install the project dependencies:

wasp install