Goals

1. Make it easier to migrate away from --env-mode=loose
2. Make it easier to integrate with orchestrators/CI platforms (In particular .Net Aspire, which relies heavily on environment variables for its integration, and was the reason I created this issue)

Non-goals

No response

Background

This is kind of the inverse of #8757, which recently shipped.

Proposal

Calling this command

turbo run dev --env=API1_BASE_URL --env=API2_BASE_URL

with this configuration:

{
  "$schema": "https://turbo.build/schema.json",
  "tasks": {
    "dev": {
    }
  }
}

would be equivalent to this:

{
  "$schema": "https://turbo.build/schema.json",
  "tasks": {
    "dev": {
      "env": ["API1_BASE_URL", "API2_BASE_URL"]
    }
  }
}

just like how this command

turbo run dev --env-mode=loose

with this configuration:

{
  "$schema": "https://turbo.build/schema.json",
  "tasks": {
    "dev": {
    }
  }
}

is equivalent to this:

{
  "$schema": "https://turbo.build/schema.json",
  "tasks": {
    "dev": {
      "envMode": "loose"
    }
  }
}