Skip to content

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

@gdaybrice

Description

@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)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions