I found that the files bundled from the latest version (commit 9567c0b4ba99e9bdd087f408e2904537e78f2757) have issues and throw the following error:

[goodgame365]

Uncaught ReferenceError: Cannot access 'gs' before initialization
at alphaTab.core.min.mjs:1:144714

[goodgame365]

This error might have started happening as early as commit 17bedef. But what’s for sure is that commits before April 10, 2025, didn’t have this problem:
Commits on April 10, 2025.

[Danielku15]

Can you provide a fully reproducible example somewhere? From the screenshot it does not seem to me you're consuming the alphaTab correctly. There is just alphaTab.core.min.mjs and your own 'm1.mjs`. Many alphaTab files from the dist folder are missing.

You might want to go for a more standard practices path of consuming alphaTab via NPM and then rely on the standardized imports and module resolving. The entry point for alphaTab (ESM) is dist/alphaTab.mjs https://github.com/CoderLine/alphaTab/blob/develop/package.json#L23C31-L23C44

Edit: give it a try after #2033

[goodgame365]

Thanks a lot! After testing, the final submitted version (949f9d6) works fine. However, I have quite a few changes to make—not with this version itself, but I realized I missed upgrading from the 345fc01 commit. No worries though, I’ll just follow my usual approach: pull the latest version and manually copy my changes over bit by bit. That should do the trick. Thanks again!!

[Danielku15]

Generally we aim to be backwards compatible from a public API surface (following semver). If you have customizations I'd recommend to contribute them back to the project instead of maintaining a patched fork.

[goodgame365]

My programming skills are quite basic, and I’m not very familiar with GitHub operations. The changes I make are mostly personal layout preferences, so my code can be a bit messy. Because of that, whenever there’s a new version, I usually just update directly and finish everything in about a day.

[Danielku15]

A contribution can also be a description of what customizations you need and how you are currently implementing them. 😉 This way I can think of a feature which might allow you to achieve the same without changing the code (e.g. by adding some new options)