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
{{ message }}
Repository navigation
workflow build fails with "No loader is configured for .md files" with aliased paths #724
After upgrading to the latest version of workflow (specifically following the changes in PR 705), the workflow build fails during the "Discovering workflow directives" phase if a scanned TypeScript file imports a Markdown (.md) file with an aliased path.
This is the turbopack config in next.config.js that used to work before beta.40
changed the title [-]workflow build fails with "No loader is configured for .md files"[/-][+]workflow build fails with "No loader is configured for .md files" with aliased paths[/+]on Jan 4, 2026
Activity
[-]workflow build fails with "No loader is configured for .md files"[/-][+]workflow build fails with "No loader is configured for .md files" with aliased paths[/+]pranaygp commentedon Jan 12, 2026
fyi @ijjk for vis
ijjk commentedon Jan 12, 2026
Hi, could you provide a link to minimal reproduction that was working before and isn't anymore?
gdaybrice commentedon Jan 12, 2026
next.config.tsmarkdown.d.tsand simply import an md file with an absolute path from within your code (e.g.
import prompt from '@/ai/prompts/prompt.md';)ijjk commentedon Jan 12, 2026
A link to a repo with this setup would be great!
Initial reproduction for vercel/workflow#724
gdaybrice commentedon Jan 13, 2026
@ijjk here you go https://github.com/gdaybrice/workflow-md-bug
gdaybrice commentedon Jan 23, 2026
I've simplified the approach on my PR (#766) can this be looked at please?
NathanColosimo commentedon Jul 15, 2026
Should be fixed in #2546 @gdaybrice let us know if you're having any other issues!