workflow build fails with "No loader is configured for .md files" with aliased paths

[gdaybrice]

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

  turbopack: {
    rules: {
      '*.md': {
        loaders: ['raw-loader'],
        as: '*.js',
      },
    },
  },

Environment
Workflow Version: 4.0.1-beta.41
Next.js Version: 15.x / 16.x
Package Manager: bun
OS: macOS (Darwin 24.6.0)

[pranaygp]

fyi @ijjk for vis

[ijjk]

Hi, could you provide a link to minimal reproduction that was working before and isn't anymore?

[gdaybrice]

next.config.ts

import type { NextConfig } from 'next';
import { withWorkflow } from 'workflow/next';

const config: NextConfig = {
  poweredByHeader: false,
  devIndicators: false,
  experimental: {
    turbopackFileSystemCacheForDev: true,
    authInterrupts: true,
  },
  turbopack: {
    rules: {
      '*.md': {
        loaders: ['raw-loader'],
        as: '*.js',
      },
    },
  },
};

export default withWorkflow(config);

markdown.d.ts

declare module '*.md' {
  const content: string;
  export default content;
}

and simply import an md file with an absolute path from within your code (e.g. import prompt from '@/ai/prompts/prompt.md';)

[ijjk]

A link to a repo with this setup would be great!

[gdaybrice]

@ijjk here you go https://github.com/gdaybrice/workflow-md-bug

[gdaybrice]

I've simplified the approach on my PR (#766) can this be looked at please?