chore: drop prompt registry codegen for stable raw imports #26
No reviewers
Labels
No labels
agent
blocked
agent
new
agent
review
agent
working
complexity
high
complexity
low
priority
high
priority
low
priority
medium
risk
high
risk
low
risk
medium
type
bug
type
chore
type
feature
type
security
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
tfks/fjx!26
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "chore/cleanup-raw-imports-hack"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs: #17
Summary
Deno 2.8.0 stabilized raw imports (
with { type: "text" }), so the workaround that inlined prompt markdown into a generated TypeScript file is no longer needed.src/prompts/registry.tsnow imports each*.mddirectly withtype: "text"and exportsprompts/Rolefrom there.src/prompts/registry.gen.tsandscripts/gen-prompts.ts.just gen-promptsrecipe, theregistry.gen.tsdrift check fromtest::gen-drift, and thejust gen-promptsstep frompublish/publish-check.src/prompts/*.mdentry from the JSR publish exclude list so consumers can resolve the text imports.Test plan
just validate(format, lint, types, gen-drift, coverage, audit, secrets, sast)deno run -A src/main.ts dev prompt simplerenders the expected prompt at runtimeDeno 2.8.0 stabilized raw imports (`with { type: "text" }`), so the gen-prompts.ts workaround and the inlined registry.gen.ts are no longer needed. Replace registry.ts with direct text imports, delete the generator and its drift check, and stop excluding src/prompts/*.md from the JSR publish so downstream consumers can resolve the imports.