Supabase Studio Container Fails to Start on Windows - Invalid package.json Error

[heloineto]

Describe the bug

The Supabase Studio container fails to start with a Node.js error: Error: Invalid package config /app/package.json when running supabase start on Windows. The container repeatedly crashes and enters an unhealthy state, preventing Studio from being accessible. All other Supabase services (database, API, auth, etc.) start successfully.

To Reproduce

Steps to reproduce the behavior:

1. Install Supabase CLI v2.48.3 on Windows 10/11
2. Run supabase start or supabase start --debug in a project directory
3. Wait for containers to start
4. Observe Studio container failing with the error below

Error Output

supabase_studio_voto-a-voto container logs:
node:internal/modules/run_main:92
  const type = getNearestParentPackageJSONType(mainPath);
               ^

Error: Invalid package config /app/package.json.
    at shouldUseESMLoader (node:internal/modules/run_main:92:16)
    at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:20)
    at node:internal/main/run_main_module:36:49 {
  code: 'ERR_INVALID_PACKAGE_CONFIG'
}

Node.js v22.20.0

This error repeats multiple times, and the container is eventually marked as unhealthy and pruned.

Expected behavior

The Studio container should start successfully and be accessible on the configured port, allowing access to the Supabase web UI for database management.

System information

• Ticket ID: 3729567994ea457e9b240c89391388a6
• Version of OS: Windows 10 (Build 10.0.26100)
• Version of CLI: v2.48.3
• Version of Docker: v28.4.0, build d8eb465
• Studio Image: public.ecr.aws/supabase/studio:2025.10.01-sha-8460121
• Node.js (container): v22.20.0
• Node.js (host): v22.19.0

Services Status

All other services start successfully:

• ✅ PostgreSQL (17.4.1.043)
• ✅ GoTrue (v2.179.0)
• ✅ PostgREST (v12.2.3)
• ✅ Realtime
• ✅ Storage
• ✅ Auth
• ❌ Studio (fails to start)

Additional context

Workaround

Disabling Studio in supabase/config.toml allows all other services to start normally:

[studio]
enabled = false

Attempted Solutions

1. Pulled latest Studio image: docker pull supabase/studio:latest - Did not resolve the issue
2. Removed all containers and volumes: supabase stop followed by fresh start - Issue persists
3. Container inspection: The /app/package.json file inside the Studio container appears to be corrupted or incompatible with Node.js v22.20.0

Related Information

• The issue occurs with the latest Studio image from the official ECR repository
• No custom configuration is applied to Studio beyond the default settings
• The project is linked to a remote Supabase project (project ref exists)
• Windows Docker is running in WSL2 mode (if applicable)

[heloineto]

The problem seems to be in the lates version. I downgraded to v2.47.2 and it worked fine

[airscripts]

Props to this, same problem with 2.48.3...Supabase Studio is inaccessible on that version.
On the other hand 2.47.2 works like a charm.

[airscripts]

Hey @heloineto have you tried if this is still an issue in 2.51.0?
(I didn't see any recall to this issue in the changelog though)