`gen types` fails for multiple schemas with npm cli v2.22.6

[Donnerstagnacht]

Describe the bug
A clear and concise description of what the bug is.

To Reproduce
Steps to reproduce the behavior:

1. Install supabase cli v2.22.6
2. Create two schemas (for example users and users_hidden)
3. Run npx supabase start
4. Run npx supabase gen types typescript --local --schema users_hidden,users
5. Generated types are displayed for schema public, but not for users_hidden or users.

If I run

supabase gen types typescript --local --schema users_hidden,users
on windows11 with cli v2.20.12 and a global scoop installation, multi schema type generation works.

If I run

npx supabase gen types typescript --local --schema users_hidden,users
on windows11 with cli v2.22.6 and npm installation, multi schema type generation does not work while generating the types for users_hidden and users in two separate commands works.

Did someone else experience something similar? Is there a setting/version difference between scoop and npm or cli version v2.20.12 and v2.22.6 which can explain the behaviour?

I am also not able to update with scoop to 2.22.6. Does someone understand why?

Expected behavior
Running the same command with npx prefix on v2.22.6 should create the same type output as for scoop and v 2.20.12

System information
Rerun the failing command with --create-ticket flag.

• Version of OS: windows11
• Version of CLI: cli v2.22.6
• Version of Docker: v4.41.1 (191279)
• Versions of services: npx supabase services

    SERVICE IMAGE          | LOCAL                  | LINKED
  ------------------------|------------------------|--------
   supabase/postgres      | 15.8.1.069             | -
   supabase/gotrue        | v2.171.0               | -
   postgrest/postgrest    | v12.2.11               | -
   supabase/realtime      | v2.34.47               | -
   supabase/storage-api   | v1.22.6                | -
   supabase/edge-runtime  | v1.67.4                | -
   supabase/studio        | 2025.04.21-sha-173cc56 | -
   supabase/postgres-meta | v0.88.9                | -
   supabase/logflare      | 1.12.0                 | -
   supabase/supavisor     | 2.5.1                  | -

And here, for comparison, the output of supabase services from the global scoop installation (supabase services) which works (!):

   SERVICE IMAGE          | LOCAL            | LINKED
  ------------------------|------------------|--------
   supabase/postgres      | 15.8.1.060       | -
   supabase/gotrue        | v2.170.0         | -
   postgrest/postgrest    | v12.2.8          | -
   supabase/realtime      | v2.34.45         | -
   supabase/storage-api   | v1.19.3          | -
   supabase/edge-runtime  | v1.67.4          | -
   supabase/studio        | 20250317-6955350 | -
   supabase/postgres-meta | v0.88.2          | -
   supabase/logflare      | 1.12.0           | -
   supabase/supavisor     | 2.4.14           | -

Additional context

• Version of Node.js: v22.14.0
• Version of npm: v11.2.0

[Donnerstagnacht]

npx supabase gen types typescript --schema users_hidden --schema users seems to work too. Is that a recommended syntax?