Replies: 1 comment
-
Seems there is still a slight problem with the copying of assets (web and sound fonts). The WebPack plugin copies the files (to the output directory) and registers them as assets into WebPack. Normally this ensures they are served by the dev server. In case of next.js
This is a known problem in next.js: vercel/next.js#32836 I updated the sample at https://github.com/CoderLine/alphaTabSamplesWeb/tree/main/src/webpack-nextjs to work. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Link to the "webpack-nextjs" sample project in question
Related update: #1539
Recently found out the update that fixes the next.js implementation and the sample project along with it and I'm really happy it works! Doesn't work straight out the box, though. I originally made this discussion trying to find out how to fix it but I figured it out, so just here to share.
The fix involves simply moving the font and soundfont to the public folder. I'm not sure if I was missing anything but this fixed all the problems with the project.
It seems there might a missing file
src/alphaTab.ts
in the sample project as mentioned in the README.md, or at least I can't find them. I can't find it in alphaTab/src/webpack either. Wonder what it does, but the project seems to work fine.Initial Setup:
Initial Output:
Fixed Output
Beta Was this translation helpful? Give feedback.
All reactions