Keep ES module syntax when bundling connectors for web

[MattiasBuelens]

Summary

The e2e app's webpack config runs babel-loader with @react-native/babel-preset over @theoplayer/**/*.js, which rewrites import/export into CommonJS. The web connectors are published as "type": "module" packages, so webpack parses their prebuilt bundles as strict ESM, where exports/require/module don't exist — the transpiled bundle then throws Uncaught ReferenceError: exports is not defined at Object.defineProperty(exports, "__esModule", …).

The existing workaround excluded the offending bundles by filename, which has to be extended for every new connector (and only worked because webpack previously resolved the UMD bundle, whose typeof exports === 'object' guards fail silently). Instead, tell the preset to leave module syntax alone:

-exclude: [/\.d\.ts$/, /cmcd-connector\.esm\.js$/, /conviva-connector\.esm\.js$/],
+exclude: [/\.d\.ts$/],
-presets: ['module:@react-native/babel-preset'],
+presets: [['module:@react-native/babel-preset', { disableImportExportTransform: true }]],

Customers with their own webpack config hit the same failure, so the root README documents the required option.

Verified with npx webpack --config ./web/webpack.config.js --mode development in apps/e2e: compiles clean, no exports is not defined and no "module has no exports" warning (only the pre-existing useTVEventHandler warnings from react-native-web).

No changeset: no published package changes.

Link to Devin session: https://dolby.devinenterprise.com/sessions/181afa65caf6457a820e64cc3d87ddb5
Open in Devin Desktop: https://dolby.devinenterprise.com/desktop/session/181afa65caf6457a820e64cc3d87ddb5?variant=devin
Requested by: @MattiasBuelens

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[changeset-bot]

⚠️ No Changeset found

Latest commit: f40b97c

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

[devin-ai-integration]

Review: LGTM ✅ (approve)

• Correct root-cause fix: disableImportExportTransform: true keeps ESM syntax so webpack handles the "type": "module" web-connector bundles itself, replacing the brittle per-connector filename excludes that would need extending for every new connector.
• The README section is a good addition, since customers with their own webpack config hit the same exports is not defined error.
• Scope is minimal (e2e webpack config + docs only, no published package changes), so no changeset is correctly needed. CI, including the web e2e suite, is green after the rebase on main.

[MattiasBuelens]

@tvanlaerhoven Not sure if this is the best place to put this? We don't actually render this root README on the documentation website... 🤷

[devin-ai-integration]

Agreed, it's not great here. The rendered surfaces are the per-package READMEs (typedoc's packages strategy picks them up for the API site, and npm shows them), so the alternative is a short "Web support" section in the READMEs of the connectors that pull in a web connector: conviva, nielsen and yospace. Downside is triplicating the same paragraph; upside is customers find it where they installed from.

Happy to do either — move it into those three READMEs, or drop it from this PR and document it on the documentation website instead. Which do you prefer?