Bug
loadPromptsFromDir dynamically import()s .ts files. In plain Node (no tsx/ts-node/bun), this throws a fairly cryptic ERR_UNKNOWN_FILE_EXTENSION. The LoaderError we wrap it in says "Failed to import" but doesn't tell the user why or how to fix it.
Expected
When the underlying error is ERR_UNKNOWN_FILE_EXTENSION for a .ts file, the thrown LoaderError message should include a hint:
Failed to import <file>: Node can't import .ts files directly. Run with tsx, bun, or ts-node, or pre-compile to .js.
Implementation
In src/loader.ts loadPromptFile, inspect the caught error's code (Node errors set .code). If it's ERR_UNKNOWN_FILE_EXTENSION, augment the message.
Acceptance
/label "good first issue" "area:loader" "bug"
Bug
loadPromptsFromDirdynamicallyimport()s.tsfiles. In plain Node (notsx/ts-node/bun), this throws a fairly crypticERR_UNKNOWN_FILE_EXTENSION. TheLoaderErrorwe wrap it in says "Failed to import" but doesn't tell the user why or how to fix it.Expected
When the underlying error is
ERR_UNKNOWN_FILE_EXTENSIONfor a.tsfile, the thrownLoaderErrormessage should include a hint:Implementation
In
src/loader.tsloadPromptFile, inspect the caught error'scode(Node errors set.code). If it'sERR_UNKNOWN_FILE_EXTENSION, augment the message.Acceptance
.tsfile under a plainnoderun (or simulate by stubbing).docs/getting-started.mdnote about TS loaders./label "good first issue" "area:loader" "bug"