Security error accessing local mjs after upgrading from 1.3.1

[Mike1020]

Hello,
this is very likely a problem on my side, but I just can't figure it out: I've used alphatab version 1.3.1 with great success and without any problems in my react app built with create-react-app, both on Win and Linux. Now that I've upgraded to 1.6.3, the browser is throwing a security error:
Security Error: Content at http://localhost:3000/ may not load data from file:///C://webapp/node_modules/@coderline/alphatab/dist/alphaTab.worker.mjs.
I think it has something to do with the (meanwhile outdated) webpack config from create-react-app, and I've tried the plugin config given in the docs, but I just don't get it to work. My knowledge of webpack might also not be deep enough. Anybody has any ideas where this error comes from and why it's not in the old version? As soon as I downgrade to 1.3.1, everything works fine again.
Many thanks
Mike

[Mike1020]

I've rewritten the react app to use Vite and all the latest packages, and it seems to work now. So my guess is it had something to do with the outdated webpack implementation of create-react-app, but I'm not sure what.

[Danielku15]

Hey there.

Without seeing any code its a bit hard to troubleshoot. Can you share a repository showing the problem?

It definitely feels strange that the browser tries to load files from disk via file-urls. Have you added the webpack plugin to your config?

https://alphatab.net/docs/getting-started/installation-webpack

Otherwise you might check how things look in the sample repository:
https://github.com/CoderLine/alphaTabSamplesWeb

[Mike1020]

I thought I had configured the plugin, but now that I recreated a minimal example starting from https://create-react-app.dev I realize that it wasn't actually called, as this tool doesn't use the standard webpack config. So I'm pretty sure that'll be the problem, but since create-react-app is outdated anyways (probably for that reason :) ), and I have moved away from it, it's probably not worth investigating further. Thanks for your help, and alphatab of course!

[Danielku15]

Great to hear. If the custom webpack config is not applied this will eventually lead to errors when launching the alphaTab background workers.

I added #2314 as an improvement for the future. It should be possible to detect that alphaTab was "bundled" and our plugins were not active. This way we can warn devs that something is wrong.