Bug Report for 1.7.1:

[AvaTheArchitect]

I have updated now from 1.6.3 but having issues. Not sure if there is a webpack that is needed now, as I don't remember having installed one before to make it work?
I also work in in VS-Code if that matters.

The package.json exports reference /dist/webpack/alphaTab.webpack.mjs which doesn't exist in the package. This breaks Next.js applications.
Error:
Cannot find module '.../dist/webpack/alphaTab.webpack.mjs'
Environment:

Next.js 15.4.8
Node.js v22.16.0
npm clean install

Workaround: Downgrade to 1.6.3

Complete error message:

⨯ Failed to load next.config.mjs, see more info here https://nextjs.org/docs/messages/next-config-error
node:internal/modules/esm/resolve:275
throw new ERR_MODULE_NOT_FOUND(
^

Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/Users/brettbolzenthal/Desktop/maestro-ai/node_modules/@coderline/alphatab/dist/webpack/alphaTab.webpack.mjs' imported from /Users/brettbolzenthal/Desktop/maestro-ai/node_modules/@coderline/alphatab/dist/alphaTab.webpack.mjs
at finalizeResolution (node:internal/modules/esm/resolve:275:11)
at moduleResolve (node:internal/modules/esm/resolve:860:10)
at defaultResolve (node:internal/modules/esm/resolve:984:11)
at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:780:12)
at #cachedDefaultResolve (node:internal/modules/esm/loader:704:25)
at ModuleLoader.resolve (node:internal/modules/esm/loader:687:38)
at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:305:38)
at ModuleJob._link (node:internal/modules/esm/module_job:137:49) {
code: 'ERR_MODULE_NOT_FOUND',
url: 'file:///Users/brettbolzenthal/Desktop/maestro-ai/node_modules/@coderline/alphatab/dist/webpack/alphaTab.webpack.mjs'
}

Node.js v22.16.0

[Danielku15]

Without any code there is not much I can do to help you. Seems to me you are wrongly including a @coderline/alphatab/webpack/alphaTab.webpack.mjs instead of (a) @coderline/alphatab/webpack or (b) using the new package @coderline/alphatab-webpack (docs update pending)

[AvaTheArchitect]

Hi Daniel, Found the issue below it’s a packaging bug! 🐛 I'm NOT explicitly importing the webpack version. The error is coming from AlphaTab 1.7.1's own internal imports. We found the smoking Gun below- its the new package! v1.7.1 Here's my actual AlphaTab import code: Share your initAlphaTab.ts file: My only AlphaTab imports are: 1. In initAlphaTab.ts: import * as alphaTab from ***@***.***/alphatab'; 2. In components: import { initAlphaTab, loadGuitarProFile } from '@/lib/alphaTab/initAlphaTab'; I'm NOT importing: ❌ @coderline/alphatab/webpack ❌ @coderline/alphatab-webpack ❌ @coderline/alphatab/webpack/alphatab.webpack.mjs The error happens when Next.js tries to load the package during startup. The broken import is INSIDE AlphaTab's dist/alphaTab.webpack.mjs file. Error trace: → Next.js loads next.config.mjs → Next.js loads @coderline/alphatab package → AlphaTab's dist/alphaTab.webpack.mjs tries to import: './webpack/alphaTab.webpack.mjs' → That file doesn't exist in ***@***.***/alphatab/dist/webpack/ → Error: Cannot find module Environment: - Next.js 15.4.8 - Node.js v22.16.0 - npm install @***@***.*** - macOS This works fine with @***@***.*** 🔎 Let Me Verify Quickly What's in the Package for V1.7.1. BINGO!!! bash # Check what's actually in the published package ls -R ***@***.***/alphatab/dist/ # Should show if webpack/ folder exists and what's in it aha this is what is in the NEW v1.7.1 package I just ran: maestro-ai % ls -R ***@***.***/alphatab/dist/ alphaTab.core.min.mjs alphaTab.mjs alphaTab.webpack.mjs <— Here it is// alphaTab.worklet.mjs alphaTab.core.mjs alphaTab.vite.d.ts alphaTab.worker.d.ts font alphaTab.d.ts alphaTab.vite.js alphaTab.worker.min.mjs soundfont alphaTab.js alphaTab.vite.mjs alphaTab.worker.mjs alphaTab.min.js alphaTab.webpack.d.ts alphaTab.worklet.d.ts alphaTab.min.mjs alphaTab.webpack.js alphaTab.worklet.min.mjs ***@***.***/alphatab/dist//font: Bravura-FONTLOG.txt Bravura-OFL.txt Bravura.otf Bravura.woff Bravura-OFL-FAQ.txt Bravura.eot Bravura.svg Bravura.woff2 ***@***.***/alphatab/dist//soundfont: LICENSE README.md sonivox.sf2 sonivox.sf3 Next I ran: cat ***@***.***/alphatab/package.json | grep -A 20 "exports" MBP maestro-ai % cat ***@***.***/alphatab/package.json | grep -A 20 "exports" "exports": { ".": { "types": "./dist/alphaTab.d.ts", "import": "./dist/alphaTab.mjs", "require": "./dist/alphaTab.js" }, "./webpack": { "types": "./dist/alphaTab.webpack.d.ts", "import": "./dist/alphaTab.webpack.mjs", "require": "./dist/alphaTab.webpack.js" }, "./vite": { "types": "./dist/alphaTab.vite.d.ts", "import": "./dist/alphaTab.vite.mjs", "require": "./dist/alphaTab.vite.js" }, "./soundfont/*": "./dist/soundfont/*", "./font/*": "./dist/font/*" }, "engines": { "node": ">=6.0.0" ***@***.*** maestro-ai % 🔍 The Smoking Gun What EXISTS in the package (v1.7.1): bash dist/alphaTab.webpack.mjs ← File EXISTS ✅ What DOESN'T exist: bash dist/webpack/alphaTab.webpack.mjs ← Missing! ❌ dist/webpack/ ← This folder doesn't exist at all! The Bug: The file dist/alphaTab.webpack.mjs contains a broken import inside it. It's trying to import from a webpack/ subfolder that doesn't exist. 🐛 The Broken Import Inside AlphaTab Check what's inside the webpack file: bash head -50 ***@***.***/alphatab/dist/alphaTab.webpack.mjs Look for this broken line: javascript import something from './webpack/alphaTab.webpack.mjs'; // OR import something from './webpack/alphaTab.webpack.js'; ``` That's the line that's failing! I found the exact issue, appears it's a packaging bug: FILES THAT EXIST: ✅ dist/alphaTab.webpack.mjs ✅ dist/alphaTab.webpack.js ✅ dist/alphaTab.webpack.d.ts FILES THAT DON'T EXIST: ❌ dist/webpack/alphaTab.webpack.mjs ← This is what's being imported! ❌ dist/webpack/ folder doesn't exist at all THE BUG: dist/alphaTab.webpack.mjs contains a broken relative import that references the non-existent webpack/ subfolder. EVIDENCE: $ ls -R ***@***.***/alphatab/dist/ [your output - no webpack/ folder] $ cat ***@***.***/alphatab/package.json | grep -A 20 "exports" [your output - package.json points to the correct files] ERROR: Cannot find module '.../dist/webpack/alphaTab.webpack.mjs' imported from '.../dist/alphaTab.webpack.mjs' MY IMPORTS (NOT using webpack): import * as alphaTab from ***@***.***/alphatab'; ← Just the main package NEXT.JS VERSION: 15.4.8 NODE VERSION: 22.16.0 THE FIX: Inside dist/alphaTab.webpack.mjs, change: import X from './webpack/alphaTab.webpack.mjs'; To: import X from './alphaTab.core.mjs'; (or whatever the correct path is) Can you check the source code that generates alphaTab.webpack.mjs and fix the broken relative import? This works fine in 1.6.3 but breaks in 1.7.1. 🔍 Why This Is Happening: Next.js 15 is likely auto-detecting webpack in your environment and trying to use the optimized webpack version. But that version has a broken import inside it. BUG LOCATION: File: dist/alphaTab.webpack.mjs Line 1: import { AlphaTabWebPackPlugin } from './webpack/alphaTab.webpack.mjs'; PROBLEM: This file doesn't exist: dist/webpack/alphaTab.webpack.mjs The webpack/ folder is completely missing from the published package. EVIDENCE: $ head -50 ***@***.***/alphatab/dist/alphaTab.webpack.mjs import { AlphaTabWebPackPlugin } from './webpack/alphaTab.webpack.mjs'; console.warn('[alphaTab] The use of alphaTab.webpack.mjs via @coderline/alphatab is deprecated. Please use the new @coderline/alphatab-webpack npm package.'); export { AlphaTabWebPackPlugin }; $ ls -R ***@***.***/alphatab/dist/ [no webpack/ folder exists] THE ISSUE: - alphaTab.webpack.mjs imports from a non-existent file - Next.js 15 auto-detects webpack and tries to use this entry point - Import fails immediately, crashes the app - This worked in 1.6.3 SUGGESTED FIXES: Option A: Remove alphaTab.webpack.mjs from 1.7.1 entirely (it's deprecated anyway) Option B: Make alphaTab.webpack.mjs just export the deprecation warning without importing anything: console.warn('[alphaTab] Use @coderline/alphatab-webpack instead'); export const AlphaTabWebPackPlugin = null; Option C: Include the missing dist/webpack/ folder with the actual plugin file WORKAROUND FOR USERS: Stay on 1.6.3 until 1.7.2 is released Environment: - Next.js 15.4.8 - Node.js v22.16.0 - macOS - Clean npm install of @***@***.*** Can you release a 1.7.2 hotfix that removes or fixes alphaTab.webpack.mjs?

…

On Thu, Dec 25, 2025 at 1:20 AM Daniel Kuschny ***@***.***> wrote: Without any code there is not much I can do to help you. Seems to me you are wrongly including a @coderline/alphatab/webpack/alphaTab.webpack.mjs instead of (a) @coderline/alphatab/webpack or (b) using the new package @coderline/alphatab-webpack ***@***.***/alphatab-webpack> (docs update pending) — Reply to this email directly, view it on GitHub <#2461 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNLESQDZI4DQ5HCH746HNV34DOT6DAVCNFSM6AAAAACP7FYFJOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMZUGAYDINQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>