weird warnings

[levino]

our users get such warnings during build (server mode):

2026-Jan-22 16:54:58.830309
#13 11.20 16:54:58 [WARN] [vite] Export "getTagLabel" of module "node_modules/@levino/shipyard-blog/src/tags.ts" was reexported through module "node_modules/@levino/shipyard-blog/src/index.ts" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
2026-Jan-22 16:54:58.836281
#13 11.20 Either change the import in "node_modules/@levino/shipyard-blog/astro/BlogTagPage.astro" to point directly to the exporting module or reconfigure "output.manualChunks" to ensure these modules end up in the same chunk.
2026-Jan-22 16:54:58.983932
#13 11.20 16:54:58 [WARN] [vite] Export "getTagDescription" of module "node_modules/@levino/shipyard-blog/src/tags.ts" was reexported through module "node_modules/@levino/shipyard-blog/src/index.ts" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
2026-Jan-22 16:54:58.983932
#13 11.20 Either change the import in "node_modules/@levino/shipyard-blog/astro/BlogTagPage.astro" to point directly to the exporting module or reconfigure "output.manualChunks" to ensure these modules end up in the same chunk.
2026-Jan-22 16:54:58.983932
#13 11.20 16:54:58 [WARN] [vite] Export "getTagDescription" of module "node_modules/@levino/shipyard-blog/src/tags.ts" was reexported through module "node_modules/@levino/shipyard-blog/src/index.ts" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
2026-Jan-22 16:54:58.983932
#13 11.20 Either change the import in "node_modules/@levino/shipyard-blog/astro/BlogTagsIndex.astro" to point directly to the exporting module or reconfigure "output.manualChunks" to ensure these modules end up in the same chunk.
2026-Jan-22 16:54:58.983932
#13 11.20 16:54:58 [WARN] [vite] Export "getTagLabel" of module "node_modules/@levino/shipyard-blog/src/tags.ts" was reexported through module "node_modules/@levino/shipyard-blog/src/index.ts" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
2026-Jan-22 16:54:58.983932
#13 11.20 Either change the import in "node_modules/@levino/shipyard-blog/astro/BlogTagsIndex.astro" to point directly to the exporting module or reconfigure "output.manualChunks" to ensure these modules end up in the same chunk.
2026-Jan-22 16:54:58.983932
#13 11.20 16:54:58 [WARN] [vite] Export "getTagPermalink" of module "node_modules/@levino/shipyard-blog/src/tags.ts" was reexported through module "node_modules/@levino/shipyard-blog/src/index.ts" while both modules are dependencies of each other and will end up in different chunks by current Rollup settings. This scenario is not well supported at the moment as it will produce a circular dependency between chunks and will likely lead to broken execution order.
2026-Jan-22 16:54:58.983932
#13 11.20 Either change the import in "node_modules/@levino/shipyard-blog/astro/BlogTagsIndex.astro" to point directly to the exporting module or reconfigure "output.manualChunks" to ensure these modules end up in the same chunk.

This is unacceptable. We need to make sure that our code produces no warnings. This we need to enforce with CI checks! Add ci checks and then make sure we do not produce any more warnings. @claude

[claude]

Claude finished @levino's task in 9m 28s —— View job • claude/issue-182-20260122-1656 • Create PR ➔

---

Fixed Circular Dependency Warnings

• Analyze the circular dependency warnings
• Fix the circular dependency in @levino/shipyard-blog
  • Move tagSchema to tags.ts to break the cycle
  • Update BlogTagPage.astro to import directly from ../src/tags
  • Update BlogTagsIndex.astro to import directly from ../src/tags
• Verify changes locally (circular dependency warnings are gone!)
• Add CI checks for build warnings (see note below)
• Run E2E tests (214 passed, 1 skipped)
• Create changeset
• Commit and push changes

---

Summary: Fixed the circular dependency warning by restructuring the imports in @levino/shipyard-blog. The root cause was that tags.ts imported tagSchema from index.ts, while index.ts re-exported from tags.ts. The solution:

1. Moved tagSchema and Tag type to tags.ts (where they logically belong)
2. Updated index.ts to import and re-export from tags.ts
3. Updated Astro components to import tag utilities directly from tags.ts

Regarding CI checks for warnings: I cannot modify .github/workflows files due to GitHub App permission limitations. You'll need to add CI checks for build warnings manually if desired.

|