Missing `next dev --turbo` features #49174

padmaia · 2023-05-03T21:42:31Z

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

Released in 13.5

The text was updated successfully, but these errors were encountered:

sanny-io · 2023-05-05T01:03:02Z

It also does not support exporting.

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

padmaia · 2023-05-05T15:51:01Z

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 · 2023-05-11T13:23:06Z

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

adamrneary · 2023-06-07T03:53:22Z

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 · 2023-06-16T04:27:34Z

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 · 2023-06-21T13:50:28Z

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

OttlikG · 2023-07-07T13:28:59Z

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 · 2023-07-14T18:06:01Z

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

TzviPM · 2023-07-15T18:48:31Z

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.

ghost · 2023-07-18T16:46:19Z

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 · 2023-07-20T06:03:14Z

It also fails if you have typedRoutes FYI

Hollayemi · 2023-07-22T21:50:56Z

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

tosave04 · 2023-07-25T11:58:52Z

Edit: Route Groups works from 13.4.13-canary.5

I get the same problem on Route Groups with turbo as @TzviPM, after testing on a minimal app, the problem occurs only in --turbo and from next version 13.4.10-canary.5
Error message

Non matching path () provided for /(site)/(pages)

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

Hollayemi · 2023-07-25T14:10:47Z

I am using webpack for now, I don't know what to do Get Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Thomas ***@***.***> Sent: Tuesday, July 25, 2023 12:59:08 PM To: vercel/next.js ***@***.***> Cc: Oluwasusi Stephen Olayemi ***@***.***>; Comment ***@***.***> Subject: Re: [vercel/next.js] Missing `next dev --turbo` features (Issue #49174) I get the same problem on Route Groups with turbo as @TzviPM</~https://github.com/TzviPM>, after testing on a minimal app, the problem occurs only in --turbo and from next version 13.4.10-canary.5 Error message Non matching path () provided for /(site)/(pages) Debug info: - Execution of get_from_source failed - Execution of resolve_source_request failed - Execution of NodeRenderContentSource::get failed - Non matching path () provided for /(site)/(pages) — Reply to this email directly, view it on GitHub<#49174 (comment)>, or unsubscribe</~https://github.com/notifications/unsubscribe-auth/AM7MNMPM5DQQCMXOQVULJ7TXR6YIZANCNFSM6AAAAAAXU7A4BE>. You are receiving this because you commented.Message ID: ***@***.***>

brianbit9 · 2023-07-26T16:55:37Z

Same issue

Non matching path (login) provided for /(pages)/login

winverse · 2023-07-28T05:35:04Z

same issue

next @13.4.6
Runing

next @13.4.7
Runing

next @13.4.8
Runing

next @13.4.9
Runing

next @ 13.4.10

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

next @ 13.4.11

Debug info:
- Execution of <NodeRenderContentSource as GetContentSourceContent>::get failed
- Non matching path () provided for /(list)

next @13.4.12

Debug info:
- Execution of <NodeRenderContentSource as GetContentSourceContent>::get failed
- Non matching path () provided for /(list)

See: /~https://github.com/velog-io/velog/tree/main/packages/velog-web

cpeaustriajc · 2023-07-28T06:33:19Z

7c67b12 Fixes the route groups issue, it landed at 13.4.13-canary.5

mattcoker · 2023-08-03T16:18:20Z

7c67b12 Fixes the route groups issue, it landed at 13.4.13-canary.5

Can confirm, 13.4.13-canary.5 fixed the route groups bug for me.

cutsoy · 2023-08-11T10:36:24Z

I'm running into some issues getting Intercepting Routes to work. Has anyone else managed to get it working with Turbo (or with SSG)?

2Senn · 2024-01-04T11:01:30Z

having the same issue as @lutfi-haslab hydration error when importing a client component into a server component. It works fine on normal dev. Anyone found a workaround for this?

wojtekmaj · 2024-04-04T09:28:23Z

It looks like we're nearing Turbo release with 99.7% tests passing, and yet, Turbo is STILL unable to resolve any modules with extensions. I'm getting hundreds and hundreds of errors like:


./packages/site-structure/index.ts:1:0
Module not found: Can't resolve './src/siteStructure.js'
> 1 | import { getSiteStructure } from './src/siteStructure.js';
    | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  2 |
  3 | import type {
  4 |   IPageEntryCollectionPartial,

https://nextjs.org/docs/messages/module-not-found

This is easily resolved with a hack on Webpack's side:

  webpack: (config) => {
    config.resolve.extensionAlias = {
      '.js': ['.js', '.ts', '.tsx'],
    };
    return config;
  },

which is also ridiculous, but at least it works.

timneutkens · 2024-05-01T09:33:39Z

Going to close this specific issue as we no longer need a larger tracking issue, please report bugs / changes you'd like in a new issue.

In case of @wojtekmaj we already chatted on X but .js resolving as .ts is planned, that is not supported with Next.js out of the box today with webpack either so there's no tests for it. In this case you edited webpack configuration to change the resolving.

pawelblaszczyk5 · 2024-05-01T09:34:55Z

Going to close this specific issue as we no longer need a larger tracking issue, please report bugs / changes you'd like in a new issue.

In case of @wojtekmaj we already chatted on X but .js resolving as .ts is planned, that is not supported with Next.js out of the box today with webpack either so there's no tests for it. In this case you edited webpack configuration to change the resolving.

Any plans for experimental.typedRoutes in turbo?

timneutkens · 2024-05-01T09:38:58Z

Eventually yes, but right now we're focusing on stable features and bugfixes first as there's only so much time in day 🙂

pawelblaszczyk5 · 2024-05-01T09:40:07Z

Understandable 😃 Just wanted to know whether it’s planned at all, thank you very much for the answer, awesome job!

github-actions · 2024-05-15T12:01:48Z

This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

padmaia added bug Issue was opened via the bug report template. Turbopack Related to Turbopack with Next.js. and removed bug Issue was opened via the bug report template. labels May 3, 2023

timneutkens closed this as completed May 1, 2024

github-actions bot added the locked label May 15, 2024

github-actions bot locked as resolved and limited conversation to collaborators May 15, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Missing `next dev --turbo` features #49174

Missing `next dev --turbo` features #49174

padmaia commented May 3, 2023 •

edited

Loading

sanny-io commented May 5, 2023 •

edited

Loading

padmaia commented May 5, 2023 •

edited

Loading

crusoexia commented May 11, 2023

adamrneary commented Jun 7, 2023

lutfi-haslab commented Jun 16, 2023

TzviPM commented Jun 21, 2023

OttlikG commented Jul 7, 2023

lachlanjc commented Jul 14, 2023

TzviPM commented Jul 15, 2023

ghost commented Jul 18, 2023

osdiab commented Jul 20, 2023

Hollayemi commented Jul 22, 2023

tosave04 commented Jul 25, 2023 •

edited

Loading

Hollayemi commented Jul 25, 2023 via email

brianbit9 commented Jul 26, 2023

winverse commented Jul 28, 2023

cpeaustriajc commented Jul 28, 2023

mattcoker commented Aug 3, 2023

cutsoy commented Aug 11, 2023

2Senn commented Jan 4, 2024

wojtekmaj commented Apr 4, 2024 •

edited

Loading

timneutkens commented May 1, 2024

pawelblaszczyk5 commented May 1, 2024

timneutkens commented May 1, 2024 •

edited

Loading

pawelblaszczyk5 commented May 1, 2024

github-actions bot commented May 15, 2024

Missing next dev --turbo features #49174

Missing next dev --turbo features #49174

Comments

padmaia commented May 3, 2023 • edited Loading

sanny-io commented May 5, 2023 • edited Loading

padmaia commented May 5, 2023 • edited Loading

crusoexia commented May 11, 2023

adamrneary commented Jun 7, 2023

lutfi-haslab commented Jun 16, 2023

TzviPM commented Jun 21, 2023

OttlikG commented Jul 7, 2023

lachlanjc commented Jul 14, 2023

TzviPM commented Jul 15, 2023

ghost commented Jul 18, 2023

osdiab commented Jul 20, 2023

Hollayemi commented Jul 22, 2023

tosave04 commented Jul 25, 2023 • edited Loading

Hollayemi commented Jul 25, 2023 via email

brianbit9 commented Jul 26, 2023

winverse commented Jul 28, 2023

cpeaustriajc commented Jul 28, 2023

mattcoker commented Aug 3, 2023

cutsoy commented Aug 11, 2023

2Senn commented Jan 4, 2024

wojtekmaj commented Apr 4, 2024 • edited Loading

timneutkens commented May 1, 2024

pawelblaszczyk5 commented May 1, 2024

timneutkens commented May 1, 2024 • edited Loading

pawelblaszczyk5 commented May 1, 2024

github-actions bot commented May 15, 2024

Missing `next dev --turbo` features #49174

Missing `next dev --turbo` features #49174

padmaia commented May 3, 2023 •

edited

Loading

sanny-io commented May 5, 2023 •

edited

Loading

padmaia commented May 5, 2023 •

edited

Loading

tosave04 commented Jul 25, 2023 •

edited

Loading

wojtekmaj commented Apr 4, 2024 •

edited

Loading

timneutkens commented May 1, 2024 •

edited

Loading