Parser fails to throw an error when i provide an invalid asyncapi file

[AceTheCreator]

Describe the bug

The Parser doesn't throw any error when I provide an invalid asyncapi file but instead returns undefined

How to Reproduce

Here as you can see Included the test:hello which makes the following asyncapi doc invalid

asyncapi: 3.0.0
test: hello
info:
  title: Account Service
  version: 1.0.0
  description: This service is in charge of processing user signups
channels:
  user/signedup:
    address: user/signedup
    messages:
      subscribe.message:
        $ref: '#/components/messages/UserSignedUp'
operations:
  user/signedup.subscribe:
    action: send
    channel:
      $ref: '#/channels/user~1signedup'
    messages:
      - $ref: '#/components/messages/UserSignedUp'
    reply:
      channel:
        $ref: '#/channels/user~1signedup'
      messages:
        - $ref: '#/components/messages/UserSignedUp'
components:
  messages:
    UserSignedUp:
      payload:
        type: object
        properties:
          displayName:
            type: string
            description: Name of the user
          email:
            type: string
            format: email
            description: Email of the user

Expected behavior

I expect the Parser to return an error not undefined

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[kouzitech]

I have fixed this issue in PR #1168

The root cause was that createUncaghtDiagnostic() in src/utils.ts returns an empty array [] for non-Error values (strings, null, undefined, etc.). This means when the parser encounters an invalid document that causes a non-Error exception, the error is silently swallowed and the parser returns undefined instead of meaningful diagnostics.

The fix handles non-Error values by converting them to string diagnostic messages, ensuring the parser always returns diagnostic information.

I am participating in the MICROGRANT Program 2026-06 #1167

[Guciolek]

Hi! I ran into this exact issue while integrating the parser into another project. I've opened a PR (#1182) that adds an opt-in throwOnError option to Parser#parse(). When enabled, the parser throws a new AsyncAPIParseError carrying the diagnostics instead of silently returning { document: undefined, diagnostics: [...] }.

The default behavior is preserved (throwOnError: false), so this is fully backward compatible. The fix is small (~40 lines in parse.ts + 6 new tests, 2472 total pass). Happy to iterate on the design if the maintainers would prefer a different approach (e.g. flip the default and bump a major version, or expose it on Parser only and not on parseOptions).