fix: improve browser/GraalVM compatibility of the parser bundle

[armorbreak001]

Fixes #1131

Problem

The browser bundle (browser/index.js) could not be used in GraalVM's JavaScript engine or other non-browser/non-Node environments because:

1. node-fetch was bundled inline, which tries to access Node.js globals that don't exist in GraalVM
2. The webpack globalObject fallback chain didn't include globalThis, causing TypeError: Cannot set property 'X' of undefined
3. When no fetch implementation was available, the error message was a cryptic module resolution failure

Changes

1. webpack.config.js

• Externalize node-fetch: Marked as external (commonjs2 null) so it's not bundled. In environments with native fetch (browsers, modern GraalVM), the global fetch API is used instead.
• Improved globalObject fallback: Added globalThis to the fallback chain (self → globalThis → this) for broader environment support.

2. from.ts

• Better error handling: When neither global fetch nor node-fetch is available, throw a clear error message explaining what's needed:

  "No fetch implementation available. In Node.js, install 'node-fetch'. In browsers or GraalVM, ensure the global fetch API is available."

How to verify

# Build the browser bundle
cd packages/parser && npm run build:browser

# The bundle should not include node-fetch internals
grep -c "node-fetch" browser/index.js  # should be 0 or minimal

# Test in Node.js (should work as before)
node -e "const p = require('./browser'); console.log(typeof p);"

# For GraalVM: load browser/index.js in GraalVM Context
# and call new AsyncAPIParser().parse('{ asyncapi: "3.0.0", ... }')

Note: For full GraalVM support, users still need to ensure a fetch polyfill is available if their GraalVM version doesn't include one natively. This change makes that integration straightforward by removing the hard dependency on node-fetch.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 1529667

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[sonarqubecloud]

Quality Gate passed

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud