unoverse 0.1.69 → 0.1.71

package/operator/lib/deploy.sh

@@ -11,17 +11,129 @@
 # Nothing is softened. Destroys are shouted, the full technical plan is one keystroke
 # away, and the SAVED plan is what runs, so what was approved is what happens. Identical
 # for every cloud: the summary reads the plan JSON, which is provider-agnostic.
+# Terraform is one static binary: install it from the official release rather than
+# sending anyone to brew, whose compile chain can demand Xcode Command Line Tools
+# updates for a tool that needs no compiling.
+_ensure_terraform() {
+  command -v terraform >/dev/null 2>&1 && return 0
+  local REPLY tf_arch tf_os tf_v="1.9.8" tf_dir
+  read -r -p "  Terraform is needed. Install it now (official binary, ~30 MB)? [Y/n] " REPLY
+  [[ "$REPLY" =~ ^[Nn]$ ]] && { fail "terraform is needed to continue"; return 1; }
+  tf_arch=$(uname -m)
+  case "$tf_arch" in arm64|aarch64) tf_arch=arm64 ;; *) tf_arch=amd64 ;; esac
+  [ "$(uname -s)" = "Darwin" ] && tf_os=darwin || tf_os=linux
+  tf_dir=$(mktemp -d)
+  curl -fsSL -o "$tf_dir/tf.zip" "https://releases.hashicorp.com/terraform/${tf_v}/terraform_${tf_v}_${tf_os}_${tf_arch}.zip" \
+    && unzip -o -q "$tf_dir/tf.zip" -d "$tf_dir" || { fail "download failed"; rm -rf "$tf_dir"; return 1; }
+  if [ -w /usr/local/bin ]; then mv "$tf_dir/terraform" /usr/local/bin/terraform
+  else sudo mv "$tf_dir/terraform" /usr/local/bin/terraform || { fail "could not install to /usr/local/bin"; rm -rf "$tf_dir"; return 1; }
+  fi
+  rm -rf "$tf_dir"
+  ok "terraform $(terraform version | head -1 | awk '{print $2}') installed"
+}
+
+
+# Everything that must be TRUE before a plan is worth looking at: every value filled,
+# and the database decision made. It lives in a function because deploy has one flow now
+# and this step belongs in it — it used to sit inside the "no .env.production yet" branch,
+# so an already-initialised ground skipped straight to planning and the Postgres question
+# was never asked. Two paths, and the configuration existed in only one of them.
+_ensure_ground_config() {
+  local cloud="$1"
+  local tfv="$ROOT/infra/$cloud/terraform.tfvars"
+    _tf_put() {  # key value — safe replacement via node (values may hold sed specials)
+      node -e 'const fs=require("fs");const[f,k,v]=process.argv.slice(1);let s=fs.readFileSync(f,"utf8");s=s.replace(new RegExp("^"+k+"(\\s*)=\\s*\"FILL_ME\"","m"),k+"$1= "+JSON.stringify(v));fs.writeFileSync(f,s)' "$tfv" "$1" "$2"
+    }
+    _tf_fill() {  # key envname prompt
+      local key="$1" envname="$2" prompt="$3" val
+      grep -q "^${key}[[:space:]]*=[[:space:]]*\"FILL_ME\"" "$tfv" 2>/dev/null || return 0
+      val=$(grep "^${envname}=" "$ROOT/.env" 2>/dev/null | head -1 | cut -d= -f2-)
+      if [ -n "$val" ]; then
+        _tf_put "$key" "$val"
+        ok "$key ${DIM}from your .env${NC}"
+      else
+        read -r -p "  $prompt: " val
+        [ -n "$val" ] && _tf_put "$key" "$val"
+      fi
+    }
+    echo ""
+    # POSTGRES: ASK, DO NOT ASSUME. The ground discovers an existing cluster and writes
+  # it as a COMMENTED line, so the default silently provisions a SECOND database next
+  # to one the account already pays for. A choice with a monthly bill attached is a
+  # question, not a line to notice in a file.
+  if [ "$cloud" = "digitalocean" ] \
+     && grep -q '^#[[:space:]]*existing_pg_cluster_name' "$tfv" 2>/dev/null \
+     && ! grep -q '^existing_pg_cluster_name' "$tfv" 2>/dev/null \
+     && ! grep -q '^byo_postgres_url' "$tfv" 2>/dev/null; then
+    local found
+    found=$(grep '^#[[:space:]]*existing_pg_cluster_name' "$tfv" | sed -E 's/.*"([^"]+)".*/\1/')
+    if [ -n "$found" ]; then
+      echo ""
+      echo -e "  ${CYAN}${BOLD}You already have a database.${NC} ${DIM}$found${NC}"
+      echo ""
+      pick_option "Use it" "Create a new one   ~\$15/month"
+      if [ "$PICKED" = "0" ]; then
+        node -e 'const fs=require("fs");const[f,c]=process.argv.slice(1);let s=fs.readFileSync(f,"utf8");s=s.replace(/^#\s*(existing_pg_cluster_name\s*=.*)$/m,"$1");fs.writeFileSync(f,s)' "$tfv" "$found"
+        ok "Reusing $found"
+      else
+        ok "A new database will be created"
+      fi
+    fi
+  fi
+
+  _tf_fill docr_token     DOCR_TOKEN     "Registry access token (from your Unoverse admin)"
+  _tf_fill openai_api_key OPENAI_API_KEY "OPENAI_API_KEY (powers the platform's AI)"
+  if grep -q '^auth_issuer[[:space:]]*=[[:space:]]*"FILL_ME"' "$tfv" 2>/dev/null; then
+    local env_auth
+    env_auth=$(grep "^AUTH_ISSUER=" "$ROOT/.env" 2>/dev/null | cut -d= -f2-)
+    if [ -z "$env_auth" ]; then
+      echo ""
+      info "A deployed universe requires a login. Local auth-off does not deploy"
+      info "${DIM}(Auth0 or any OIDC provider; the issuer looks like https://your-tenant.auth0.com)${NC}"
+    fi
+  fi
+  _tf_fill auth_issuer    AUTH_ISSUER    "AUTH_ISSUER"
+  _tf_fill auth_client_id AUTH_CLIENT_ID "AUTH_CLIENT_ID"
+
+  # VALUES only: the file's own header comment says the word FILL_ME, and matching
+  # it declared a complete file blank.
+  if grep -qE '=[[:space:]]*"FILL_ME"' "$tfv" 2>/dev/null; then
+    echo ""
+    warn "Some values are still blank in ${BOLD}infra/$cloud/terraform.tfvars${NC} — fill them, then:"
+    info "  cd infra/$cloud && terraform init && terraform apply"
+    info "  cd ../.. && unoverse deploy"
+    echo ""
+    exit 1
+  fi
+  ok "terraform.tfvars is complete"
+
+  # SIZE IS NOT A ONE-WAY DOOR. small is the POC box, and the plan below is about to
+  # quote its monthly cost — the moment someone wonders whether they are committing to
+  # it. One line, here, rather than a discovery later.
+  local cur_size
+  cur_size=$(grep -E '^size[[:space:]]*=' "$tfv" 2>/dev/null | sed -E 's/.*"([^"]+)".*/\1/')
+  [ -n "$cur_size" ] && info "Size: ${BOLD}${cur_size}${NC} ${DIM}(small · medium · large — change it in terraform.tfvars and deploy again whenever you outgrow it)${NC}"
+
+  # STRAIGHT INTO TERRAFORM. Its plan plus its own typed "yes" IS the decision gate
+  # for billable infrastructure; a [Y/n] in front of it was asking permission to ask
+  # permission. Answering "no" is terraform's "no".
+  echo ""
+
+}
+
 _ground_apply() {
   local cloud="$1" tmp planfile rc
   # SEPARATE STATEMENT. On macOS bash 3.2 a single `local a="$1" b="...$a"` expands $a
   # EMPTY, so dir became "$ROOT/infra/" and terraform answered "No configuration files".
+
+
   # Same trap that once made the release publish the repo root.
   local dir="$ROOT/infra/$cloud"
   tmp=$(mktemp -d); planfile="$tmp/plan"
 
   terraform -chdir="$dir" init -input=false >/dev/null 2>&1 || { fail "terraform init failed"; rm -rf "$tmp"; return 1; }
 
-  info "Working out what needs to change..."
+  info "Working out what needs to change ${DIM}($cloud)${NC}..."
   terraform -chdir="$dir" plan -input=false -detailed-exitcode -out="$planfile" >"$tmp/plan.log" 2>&1
   rc=$?
   case "$rc" in
@@ -34,8 +146,11 @@ _ground_apply() {
     terraform -chdir="$dir" show "$planfile"
   fi
 
+  # `read -p` does NOT interpret escapes, so ${DIM} printed as literal \033[2m. Colour
+  # the hint with echo -e first, then take a plain prompt.
   local REPLY
-  read -r -p "  Go ahead? [y/N] ${DIM}(d for the full technical plan)${NC} " REPLY
+  echo -e "  ${DIM}(d shows the full technical plan)${NC}"
+  read -r -p "  Go ahead? [y/N] " REPLY
   if [[ "$REPLY" =~ ^[Dd]$ ]]; then
     terraform -chdir="$dir" show "$planfile"
     read -r -p "  Go ahead? [y/N] " REPLY
@@ -70,178 +185,54 @@ cmd_deploy() {
     done
   fi
 
-  # INFRA CHANGES SHIP TOO. If the ground has pending changes (edited tfvars, a new
-  # resource in main.tf from an update), deploy applies them first — through
-  # terraform's own plan-and-yes gate — then re-renders the env, since outputs may
-  # have changed. Without this, deploy only ever shipped images once a server
-  # existed, and infrastructure edits silently rotted.
-  local g_applied
-  if command -v terraform >/dev/null 2>&1; then
-    local g rc
-    for g in digitalocean aws; do
-      [ -d "$ROOT/infra/$g/.terraform" ] || continue
-      _ground_apply "$g"; rc=$?
-      [ "$rc" = "1" ] && exit 1
-      if [ "$rc" = "0" ]; then
-        terraform -chdir="$ROOT/infra/$g" output -raw env_production > "$env_prod" 2>/dev/null \
-          && ok "Refreshed .env.production from the ground"
-        g_applied=1
-      fi
-      break
-    done
-  fi
-
-  # Missing .env.production is not an error if a ground has been applied — the
-  # file is just a Terraform output, so render it ourselves. Reading state is
-  # not wrapping terraform: apply stays the developer's explicit act.
-  if [ ! -f "$env_prod" ] && command -v terraform >/dev/null 2>&1; then
-    local g
-    for g in digitalocean aws; do
-      [ -d "$ROOT/infra/$g" ] || continue
-      if terraform -chdir="$ROOT/infra/$g" output -raw env_production > "$env_prod.tmp" 2>/dev/null \
-         && grep -q '^DEPLOY_HOST=' "$env_prod.tmp"; then
-        mv "$env_prod.tmp" "$env_prod"
-        ok "Rendered .env.production from your $g ground"
-        info "It holds CREDENTIAL_ENCRYPTION_KEY — back it up with the DB, never commit it."
-        break
-      fi
-      rm -f "$env_prod.tmp"
-    done
-  fi
+  # ── ONE FLOW ────────────────────────────────────────────────────────────────
+  # Which ground, is it configured, plan it, apply it, ship it. In that order, every
+  # time, whether this is the first deploy or the fiftieth.
+  local cloud="" g rc
+  for g in digitalocean aws; do
+    [ -f "$ROOT/infra/$g/terraform.tfvars" ] && { cloud="$g"; break; }
+  done
 
-  # NO SERVER YET is not an error, it is the first question. deploy owns the whole
-  # journey: pick the cloud right here (ground is no longer a command to know about),
-  # prefill its Terraform, and name the two commands left. `terraform apply` stays the
-  # developer's own explicit act — it creates billable infrastructure.
-  if [ ! -f "$env_prod" ]; then
+  if [ -z "$cloud" ]; then
     echo ""
     echo -e "  ${CYAN}${BOLD}Where should this universe live?${NC}"
     echo ""
-    local cloud
     pick_option "DigitalOcean" "AWS"
     [ "$PICKED" = "1" ] && cloud=aws || cloud=digitalocean
     echo ""
-    # An existing tfvars is PROGRESS, not a conflict: the previous run wrote it. Only
-    # a missing file needs the ground; either way the flow continues below.
-    if [ -f "$ROOT/infra/$cloud/terraform.tfvars" ]; then
-      ok "Using your existing infra/$cloud/terraform.tfvars"
-    else
-      cmd_ground "$([ "$cloud" = "aws" ] && echo aws || echo do)" || {
-        echo ""
-        info "Once that is sorted, run ${BOLD}unoverse deploy${NC} again. It picks up right here."
-        echo ""
-        exit 1
-      }
-    fi
-    echo ""
-    ok "Your $cloud ground is prefilled ${DIM}(infra/$cloud/terraform.tfvars)${NC}"
-
-    # FILL THE BLANKS OURSELVES. Every FILL_ME the universe already knows (.env from
-    # setup) is copied in silently; only genuine unknowns are asked. Hand-copying
-    # values between our own files is not a step a developer should ever see.
-    local tfv="$ROOT/infra/$cloud/terraform.tfvars"
-    _tf_put() {  # key value — safe replacement via node (values may hold sed specials)
-      node -e 'const fs=require("fs");const[f,k,v]=process.argv.slice(1);let s=fs.readFileSync(f,"utf8");s=s.replace(new RegExp("^"+k+"(\\s*)=\\s*\"FILL_ME\"","m"),k+"$1= "+JSON.stringify(v));fs.writeFileSync(f,s)' "$tfv" "$1" "$2"
-    }
-    _tf_fill() {  # key envname prompt
-      local key="$1" envname="$2" prompt="$3" val
-      grep -q "^${key}[[:space:]]*=[[:space:]]*\"FILL_ME\"" "$tfv" 2>/dev/null || return 0
-      val=$(grep "^${envname}=" "$ROOT/.env" 2>/dev/null | head -1 | cut -d= -f2-)
-      if [ -n "$val" ]; then
-        _tf_put "$key" "$val"
-        ok "$key ${DIM}from your .env${NC}"
-      else
-        read -r -p "  $prompt: " val
-        [ -n "$val" ] && _tf_put "$key" "$val"
-      fi
-    }
-    echo ""
-    # POSTGRES: ASK, DO NOT ASSUME. The ground discovers an existing cluster and writes
-    # it as a COMMENTED line, so the default silently provisions a SECOND database next
-    # to one the account already pays for. A choice with a monthly bill attached is a
-    # question, not a line to notice in a file.
-    if [ "$cloud" = "digitalocean" ] \
-       && grep -q '^#[[:space:]]*existing_pg_cluster_name' "$tfv" 2>/dev/null \
-       && ! grep -q '^existing_pg_cluster_name' "$tfv" 2>/dev/null \
-       && ! grep -q '^byo_postgres_url' "$tfv" 2>/dev/null; then
-      local found
-      found=$(grep '^#[[:space:]]*existing_pg_cluster_name' "$tfv" | sed -E 's/.*"([^"]+)".*/\1/')
-      if [ -n "$found" ]; then
-        echo ""
-        echo -e "  ${CYAN}${BOLD}You already have a database.${NC} ${DIM}$found${NC}"
-        echo ""
-        pick_option "Use it" "Create a new one   ~\$15/month"
-        if [ "$PICKED" = "0" ]; then
-          node -e 'const fs=require("fs");const[f,c]=process.argv.slice(1);let s=fs.readFileSync(f,"utf8");s=s.replace(/^#\s*(existing_pg_cluster_name\s*=.*)$/m,"$1");fs.writeFileSync(f,s)' "$tfv" "$found"
-          ok "Reusing $found"
-        else
-          ok "A new database will be created"
-        fi
-      fi
-    fi
-
-    _tf_fill docr_token     DOCR_TOKEN     "Registry access token (from your Unoverse admin)"
-    _tf_fill openai_api_key OPENAI_API_KEY "OPENAI_API_KEY (powers the platform's AI)"
-    if grep -q '^auth_issuer[[:space:]]*=[[:space:]]*"FILL_ME"' "$tfv" 2>/dev/null; then
-      local env_auth
-      env_auth=$(grep "^AUTH_ISSUER=" "$ROOT/.env" 2>/dev/null | cut -d= -f2-)
-      if [ -z "$env_auth" ]; then
-        echo ""
-        info "A deployed universe requires a login. Local auth-off does not deploy"
-        info "${DIM}(Auth0 or any OIDC provider; the issuer looks like https://your-tenant.auth0.com)${NC}"
-      fi
-    fi
-    _tf_fill auth_issuer    AUTH_ISSUER    "AUTH_ISSUER"
-    _tf_fill auth_client_id AUTH_CLIENT_ID "AUTH_CLIENT_ID"
-
-    # VALUES only: the file's own header comment says the word FILL_ME, and matching
-    # it declared a complete file blank.
-    if grep -qE '=[[:space:]]*"FILL_ME"' "$tfv" 2>/dev/null; then
+    cmd_ground "$([ "$cloud" = "aws" ] && echo aws || echo do)" || {
       echo ""
-      warn "Some values are still blank in ${BOLD}infra/$cloud/terraform.tfvars${NC} — fill them, then:"
-      info "  cd infra/$cloud && terraform init && terraform apply"
-      info "  cd ../.. && unoverse deploy"
+      info "Once that is sorted, run ${BOLD}unoverse deploy${NC} again. It picks up right here."
       echo ""
       exit 1
-    fi
-    ok "terraform.tfvars is complete"
-
-    # SIZE IS NOT A ONE-WAY DOOR. small is the POC box, and the plan below is about to
-    # quote its monthly cost — the moment someone wonders whether they are committing to
-    # it. One line, here, rather than a discovery later.
-    local cur_size
-    cur_size=$(grep -E '^size[[:space:]]*=' "$tfv" 2>/dev/null | sed -E 's/.*"([^"]+)".*/\1/')
-    [ -n "$cur_size" ] && info "Size: ${BOLD}${cur_size}${NC} ${DIM}(small · medium · large — change it in terraform.tfvars and deploy again whenever you outgrow it)${NC}"
-
-    # STRAIGHT INTO TERRAFORM. Its plan plus its own typed "yes" IS the decision gate
-    # for billable infrastructure; a [Y/n] in front of it was asking permission to ask
-    # permission. Answering "no" is terraform's "no".
-    echo ""
-    # Terraform is one static binary: install it directly from the official release
-    # rather than sending anyone to brew (whose compile chain can demand Xcode Command
-    # Line Tools updates for a tool that needs no compiling).
-    if ! command -v terraform >/dev/null 2>&1; then
-      local REPLY2 tf_arch tf_os tf_v="1.9.8" tf_dir
-      read -r -p "  Terraform is needed. Install it now (official binary, ~30 MB)? [Y/n] " REPLY2
-      [[ "$REPLY2" =~ ^[Nn]$ ]] && { fail "terraform is needed to continue"; exit 1; }
-      tf_arch=$(uname -m); [ "$tf_arch" = "arm64" ] || [ "$tf_arch" = "aarch64" ] && tf_arch=arm64 || tf_arch=amd64
-      [ "$(uname -s)" = "Darwin" ] && tf_os=darwin || tf_os=linux
-      tf_dir=$(mktemp -d)
-      curl -fsSL -o "$tf_dir/tf.zip" "https://releases.hashicorp.com/terraform/${tf_v}/terraform_${tf_v}_${tf_os}_${tf_arch}.zip"         && unzip -o -q "$tf_dir/tf.zip" -d "$tf_dir" || { fail "download failed"; exit 1; }
-      if [ -w /usr/local/bin ]; then mv "$tf_dir/terraform" /usr/local/bin/terraform
-      else sudo mv "$tf_dir/terraform" /usr/local/bin/terraform || { fail "could not install to /usr/local/bin"; exit 1; }
-      fi
-      rm -rf "$tf_dir"
-      ok "terraform $(terraform version | head -1 | awk '{print $2}') installed"
-    fi
-    _ground_apply "$cloud" || exit 1
+    }
+  else
+    # SAY WHERE THIS IS GOING, first and unmissably. An existing ground already names
+    # the cloud, so re-asking every deploy would be noise — but a one-line mention
+    # buried above other output reads as never having been asked at all.
+    local pretty
+    [ "$cloud" = "aws" ] && pretty="AWS" || pretty="DigitalOcean"
     echo ""
-    ok "Infrastructure is up. Shipping the platform onto it..."
+    echo -e "  ${CYAN}${BOLD}⬡ Deploying to $pretty${NC} ${DIM}(infra/$cloud — delete that folder's terraform.tfvars to choose again)${NC}"
     echo ""
-    cmd_deploy init
-    return $?
   fi
 
+  _ensure_ground_config "$cloud" || exit 1
+  _ensure_terraform || exit 1
+
+  _ground_apply "$cloud"; rc=$?
+  [ "$rc" = "1" ] && exit 1
+  if [ "$rc" = "0" ] || [ ! -f "$env_prod" ]; then
+    terraform -chdir="$ROOT/infra/$cloud" output -raw env_production > "$env_prod" 2>/dev/null \
+      && ok "Rendered .env.production from your $cloud ground"
+  fi
+
+  if [ ! -f "$env_prod" ]; then
+    fail ".env.production could not be rendered — has the ground been applied?"
+    exit 1
+  fi
+
+
   # Read deploy target from .env.production
   local deploy_host deploy_user
   deploy_host=$(grep '^DEPLOY_HOST=' "$env_prod" | cut -d= -f2- | tr -d '\r\n' | xargs)

package/operator/lib/init.sh

@@ -334,7 +334,7 @@ cmd_init() {
 
   # Node vendor keys, OPTIONAL: only the matching nodes need them, nothing platform-level
   # does. Asked so compose stops warning about them and so they land in .env with names.
-  local cur_hb cur_sa
+  local cur_hb
   cur_hb=$(_env_cur HYPERBROWSER_API_KEY)
   if [ -n "$cur_hb" ]; then
     read -p "  HYPERBROWSER_API_KEY [keep current]: " HYPERBROWSER_API_KEY
@@ -342,13 +342,7 @@ cmd_init() {
   else
     read -p "  HYPERBROWSER_API_KEY (browser nodes, blank to skip): " HYPERBROWSER_API_KEY
   fi
-  cur_sa=$(_env_cur SEARCHAPI_KEY)
-  if [ -n "$cur_sa" ]; then
-    read -p "  SEARCHAPI_KEY [keep current]: " SEARCHAPI_KEY
-    SEARCHAPI_KEY="${SEARCHAPI_KEY:-$cur_sa}"
-  else
-    read -p "  SEARCHAPI_KEY (web-search nodes, blank to skip): " SEARCHAPI_KEY
-  fi
+
 
   # A silent fact, not a question: the encryption key is GENERATED (a human never types
   # one) and kept verbatim on re-runs — a new key orphans every stored credential.
@@ -378,7 +372,6 @@ OPENAI_API_KEY=${OPENAI_API_KEY}
 # back it up with the database. Kept on re-runs.
 CREDENTIAL_ENCRYPTION_KEY=${CREDENTIAL_ENCRYPTION_KEY}
 HYPERBROWSER_API_KEY=${HYPERBROWSER_API_KEY}
-SEARCHAPI_KEY=${SEARCHAPI_KEY}
 DOMAIN=
 ENVEOF
 

package/operator/operator.sh

@@ -73,6 +73,23 @@ case "${1:-}" in
     elif ! docker info >/dev/null 2>&1; then
       info "Docker is not running. Images refresh on the next unoverse start"
     else
+      # The ground definitions first: they are code, and they update like code.
+      # NO `local` HERE: a case branch in the dispatch is not a function body, and bash
+      # errors "local: can only be used in a function" straight to the developer's screen.
+      _vinfra="$GRAVITY_LIB/../infra"
+      if [ -d "$_vinfra" ]; then
+        for _g in digitalocean aws; do
+          [ -d "$ROOT/infra/$_g" ] && [ -d "$_vinfra/$_g" ] || continue
+          _changed=0
+          for _f in "$_vinfra/$_g"/*.tf "$_vinfra/$_g"/*.example; do
+            [ -f "$_f" ] || continue
+            _base=$(basename "$_f")
+            cmp -s "$_f" "$ROOT/infra/$_g/$_base" || { cp "$_f" "$ROOT/infra/$_g/$_base"; _changed=1; }
+          done
+          [ "$_changed" = "1" ] && ok "Refreshed the $_g ground ${DIM}(your terraform.tfvars and state untouched)${NC}"
+        done
+      fi
+
       info "Checking for newer platform images..."
       if ! docker compose -f "$ROOT/docker-compose.yml" --env-file "$ROOT/.env" pull; then
         # A failed pull must not be followed by "everything is up to date". Timeouts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "unoverse",
-  "version": "0.1.69",
+  "version": "0.1.71",
   "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
   "license": "SEE LICENSE IN README.md",
   "type": "module",