You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for the report, you're right. The build emitted the Font Awesome font (and the Leaflet map images) as fa-solid-900-<hash>.woff2 and similar, but the step that copies build output into each npm package only picks up files whose name starts with the package name. So yasgui.min.css points to a font that never made it into the published package, hence the 404 on unpkg.
This is fixed in #192: those assets are now prefixed with the package name and shipped next to the CSS (for yasgui, yasqe and yasr, and in the Docker image too). The fix will be part of the next release.
Activity
MathiasVDA commentedon Oct 6, 2026
Thanks for the report, you're right. The build emitted the Font Awesome font (and the Leaflet map images) as
fa-solid-900-<hash>.woff2and similar, but the step that copies build output into each npm package only picks up files whose name starts with the package name. Soyasgui.min.csspoints to a font that never made it into the published package, hence the 404 on unpkg.This is fixed in #192: those assets are now prefixed with the package name and shipped next to the CSS (for
yasgui,yasqeandyasr, and in the Docker image too). The fix will be part of the next release.fix: ship font and image assets with the package builds (fixes #191) (#…
fix: ship font and image assets with the package builds (fixes #191) (#…