Current Situation: If a developer integrates alphaTab without reading the bundler docs, or if for unknown reasons a custom bundler config is not picked up, it can easily happen that alphaTab is "bundled" in the wrong way without the developer knowing what's going on.
Proposed improvement: We have some means of detecting that alphaTab is being bundled with WebPack or Vite thanks to some globals being injected by plugins. We should additionally inject some metadata into the bundler which allows us to detect if the respective alphaTab bundler plugin is active.
If the alphaTab plugin is missing, we should emit a warning during runtime that the plugin is missing so devs can act accordingly.
Current Situation: If a developer integrates alphaTab without reading the bundler docs, or if for unknown reasons a custom bundler config is not picked up, it can easily happen that alphaTab is "bundled" in the wrong way without the developer knowing what's going on.
Proposed improvement: We have some means of detecting that alphaTab is being bundled with WebPack or Vite thanks to some globals being injected by plugins. We should additionally inject some metadata into the bundler which allows us to detect if the respective alphaTab bundler plugin is active.
If the alphaTab plugin is missing, we should emit a warning during runtime that the plugin is missing so devs can act accordingly.