Something wrong with catching errors from realtime subscriptions

[geoguide]

Bug report

• [x] I confirm this is a bug with Supabase, not with my own application.
• [x] I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

When a table doesn't exist or realtime isn't enabled you cannot get errors without having typescript errors.

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

From help on the discord I found I can do this to get the errors:

.on(
  ..
)
  .subscribe((status, error) => console.info(status, error))
  .on('system', { event: 'error' }, (error: any) => {
      console.info('system', JSON.stringify(error))
})

but this doesn't appear to be documented and throws this typescript error:

Expected behavior

At least allow the typescript to accept the 'system' in this case so that I can get the errors in my code, and at best show how to handle this in the docs

Screenshots

System information

• OS: macOS
• Browser Any
• Version of supabase-js: 2.40
• Version of Node.js: 20.4

Additional context

Add any other context about the problem here.

[filipecabaco]

Will close since it's available in version 2.10.5 - https://github.com/supabase/realtime-js/issues/121

[geoguide]

Thanks @filipecabaco !!!