Missing `next dev --turbo` features

[padmaia]

The Turbopack dev server is nearly feature complete, but here is a list of some outstanding issues:

• [WEB-986] Support dynamic expressions in require turborepo#4796
• [WEB-991] Support client side navigation from pages to app routes turborepo#4802
• [WEB-993] Support Next.js basePath turborepo#4805
• [WEB-994] Support Next.js assetPrefix turborepo#4806
• [WEB-990] Support Next.js server actions turborepo#4803
• [WEB-995] Support tsconfig nodenext turborepo#4807
• [WEB-996] Support Next.js TypeScript config validation turborepo#4808
• Route Interception not yet supported with Turbopack #55592

Released in 13.5

• [WEB-654] Sass loading turborepo#4794
• [WEB-985] Wasm loading turborepo#4795
• [WEB-987] Support Top Level Await turborepo#4797
• [WEB-988] Support Open Graph Image Generation turborepo#4798
• [WEB-50] Support package.json imports field turborepo#4799
• [WEB-992] Relay support turborepo#4801
• [WEB-989] Support Next.js dynamic metadata turborepo#4804
• [WEB-997] Support debugging Node.js code turborepo#4809
• [WEB-998] Support experimental swc plugins turborepo#4810

[sanny-io]

It also does not support exporting.

https://nextjs.org/docs/app/building-your-application/deploying/static-exports#configuration

[padmaia]

It also does not support exporting.

This issue is specifically for dev server features. Production builds are not supported at all yet. At one point next dev --turbo would fail if you had this option configured, but now it will ignore it since it isn't relevant.

[crusoexia]

How about "Module federation" for micro-frontend architecture?

[adamrneary]

We are really excited to get this a try over at Watershed. For now, turbopack is failing because we are employing the experimental.externalDir flag, which we seem to believe that we need for our monorepo use case with pnpm. (See #26420).

But this seems like a possible miscommunication, because Turbopack, Turborepo, Next.js…are all the same team. :)

Is there a working example of a monorepo that uses Turborepo and Turbopack with Next 13, where an app in one project is relying on, for example, UI components in another project? This seems like a bread and butter example, but we must have it wrong somewhere!

[lutfi-haslab]

I have error hydration using turbo,

Error: Text content does not match server-rendered HTML.

See more info here: https://nextjs.org/docs/messages/react-hydration-error

and warning

Error: There was an error while hydrating this Suspense boundary. Switched to client rendering.

it works normally without --turbo i am using it because much faster than dev only

[TzviPM]

Not sure if this should be included in this list: vercel/turborepo#5347

[OttlikG]

I'm getting error when importing sass file from external lib from node_modules

@import '~flexboxgrid/css/flexboxgrid.css';

unable to resolve module "~flexboxgrid" with subpath "/css/flexboxgrid.css"

[lachlanjc]

Good news, webp image support landed in today's release! #52285

[TzviPM]

I went to test the new webp support, and I'm now experiencing an issues with route groups:

Non matching path () provided for /(main)

I have a main site and a microsite that don't share much layout, so my site (minus icons and metadata) is separated into a (main) route group and a (microsite) group, each with their own top-level layout.

When I try to load the home page in (main) with next dev --turbo, I get the following error information:

Non matching path () provided for /(main)

Debug info:
- Execution of get_from_source failed
- Execution of resolve_source_request failed
- Execution of NodeRenderContentSource::get failed
- Non matching path () provided for /(main)

I don't have time to create a minimal repro right now, but if anyone has a similar issue, please feel free to tag me on any speculative work and I can try to pitch in when I have time.

I'm definitely running into the same problem as @TzviPM. Normal next dev works fine though. For the time being I'll just stick to normal webpack while NextJS team sorts this out.

[osdiab]

It also fails if you have typedRoutes FYI

[Hollayemi]

I'm running into the same problem as @TzviPM. it works fine without the parenthesis though.