Repository navigation
feat: rework the samples for alphaTab 1.9 and its bundler plugins - #4
Open
Danielku15 wants to merge 5 commits into
Open
Danielku15 wants to merge 5 commits into
Danielku15 wants to merge 5 commits into
Conversation
Samples for every supported framework major and bundler, named <framework>-<major>-<bundler> and bundler-<name>-<major>, each with a README describing the alphaTab-specific setup and its limits. The plugin-based samples use @coderline/alphatab-webpack and @coderline/alphatab-vite; esbuild, Rollup and Parcel use the core, worker and worklet entries. Superseded samples and the per-sample lockfiles are removed.
…sample alphaTab detects Turbopack, so the sample imports @coderline/alphatab, drops its own worker entry and initialization, and points core.scriptFile to the copied ES module for the Audio Worklet.
Next.js applies basePath to its routes and bundles, so the workers Turbopack bundles load from the sub-path, but not to the URLs the client builds for files in public/. The config exposes basePath as NEXT_PUBLIC_BASE_PATH and ScoreViewer prefixes the score, font directory, worklet script file and SoundFont with it.
The minified entry files now import alphaTab.core.min.mjs and start the minified worker and worklet, so the samples copy and import-map alphaTab.min.mjs, alphaTab.core.min.mjs, alphaTab.worker.min.mjs and alphaTab.worklet.min.mjs. The READMEs describe the minified set and how to switch to the unminified one for debugging.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Note
AI-authored disclosure (
alphatab-ai-authored-v1)Portions of this content were authored by an AI agent. The agent has read
AGENTS.md and the human submitter accepts responsibility for
compliance with the rules in that document.
Issues
Companion to CoderLine/alphaTab#2998 (bundler integration rework for 1.9).
Proposed changes
Why: The samples should show verified setups for every supported major of the common bundlers and frameworks, using the proper plugin packages. Several old samples were outdated (Angular 17, Vite 6, Next.js workarounds) or relied on the
@coderline/alphatab/webpack|vitere-exports./core+/worker+/workletrecipe: esbuild, Rollup, Parcel;vite-react,vite-vue,webpack-plain,webpack-angular-17,webpack-nextjs-15,webpack-nextjs-16.Checklist
AI authorship disclosure
(
alphatab-ai-authored-v1) is present at the top of this body, and I havepersonally reviewed every change and can explain each one
Further details
^1.9.0-alpha.1965. No lockfiles are committed yet: they should be generated once the next 1.9 alpha with the new plugins is published. Merge after that.