Skip to content

fix: register atma font bundle in tsdown build entries - #69

Merged
gkurt merged 1 commit into
gkurt:mainfrom
2u841r:fix/atma-tsdown-entry
Jul 12, 2026
Merged

fix: register atma font bundle in tsdown build entries#69
gkurt merged 1 commit into
gkurt:mainfrom
2u841r:fix/atma-tsdown-entry

Conversation

@2u841r

@2u841r 2u841r commented Jul 12, 2026

Copy link
Copy Markdown
Contributor

Summary

Follow-up to #67. The renderer's tsdown.config.ts hardcodes each bundled font as a build entry (and in the .ttf copy list in writeBundle), so a new font bundle isn't picked up by bun --filter tegaki build unless it's added there too. The Atma bundle from #67 was missing from both lists, so dist/fonts/atma was never generated — this broke the docs site build (Rolldown failed to resolve import "tegaki/fonts/atma" in HomePageExamples.tsx), which is why the last two Deploy Docs to GitHub Pages runs failed.

  • Add 'fonts/atma/bundle': 'fonts/atma/bundle.ts' to the entry map
  • Add 'atma' to the .ttf copy list in writeBundle()

Test plan

  • rm -rf packages/renderer/dist packages/website/dist && bun --filter tegaki build now emits dist/fonts/atma/*
  • cd packages/website && bun run build succeeds (previously failed resolving tegaki/fonts/atma)
  • bun checks passes

The renderer's tsdown config hardcodes each font bundle as a build
entry and in the .ttf copy list, so a new bundle isn't picked up by
`bun --filter tegaki build` unless it's added there too — CI's
deploy-docs build failed resolving `tegaki/fonts/atma` because dist/
never got the atma output.
@gkurt

gkurt commented Jul 12, 2026

Copy link
Copy Markdown
Owner

Thank you. I was going to apply the same fix.

@gkurt
gkurt merged commit 2cf85d1 into gkurt:main Jul 12, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants