fix: esbuild md loader

[gdaybrice]

Fixing #724

[changeset-bot]

🦋 Changeset detected

Latest commit: a767ea2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 15 packages

Name	Type
@workflow/builders	Patch
@workflow/next	Patch
@workflow/astro	Patch
@workflow/cli	Patch
@workflow/nest	Patch
@workflow/nitro	Patch
@workflow/sveltekit	Patch
@workflow/docs-typecheck	Patch
workflow	Patch
@workflow/world-testing	Patch
@workflow/example-nest	Patch
@workflow/nuxt	Patch
@workflow/ai	Patch
@workflow/core	Patch
@workflow/web-shared	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[vercel]

@gdaybrice is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

[pranaygp]

supporting markdown loading "by default" seems odd to me. Maybe the better option is to allow people to provide their own loaders. wdyt @ijjk ?

[gdaybrice]

@pranaygp agree it's not ideal, would be better to support the turbopack configuration if any custom loader is setup.

[gdaybrice]

@pranaygp made some changes, is this a simpler approach?

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm/​raw-loader@​4.0.2

View full report

[gdaybrice]

@pranaygp @ijjk can this be reviewed please? it's been blocking me for a while, happy to make changes if you don't like the approach.

[ijjk]

Hi sorry for the delay here, any chance you could try upgrading to latest workflow package and Next.js v16.2.0-canary.48 and then enabling this flag in workflows

workflow/workbench/nextjs-turbopack/next.config.ts

Line 10 in 5e06a7c

export default withWorkflow(nextConfig, { workflows: { lazyDiscovery: true } });

That will no longer use esbuild for bundling steps and discovery workflows/steps so the loader customizing should no longer be necessary separate of Next.js' config.