Turbopack build feedback #77721
Replies: 59 comments 82 replies
-
|
when creating a standalone build and starting with just |
Beta Was this translation helpful? Give feedback.
-
|
This is no longer the case when using the latest canary release (that is going out as 15.3 soon). |
Beta Was this translation helpful? Give feedback.
-
|
why does with running however, running |
Beta Was this translation helpful? Give feedback.
-
|
Are you asking about the larger bundle size or the |
Beta Was this translation helpful? Give feedback.
-
thanks that explains it. |
Beta Was this translation helpful? Give feedback.
-
|
btw will turbopack have a replacement for webpack's bundle-analyzer? |
Beta Was this translation helpful? Give feedback.
-
|
@stefanprobst, we need a more polished long-term solution, but for now you can run See #81318 for details. |
Beta Was this translation helpful? Give feedback.
-
|
turbopack build does not correctly resolve fonts from next/font - #77861 |
Beta Was this translation helpful? Give feedback.
-
|
Did some digging into this and it seems to only happen with |
Beta Was this translation helpful? Give feedback.
-
|
next build --turbo with nextjs 15.3.0 generates chunks with invalid filenames on Windows. |
Beta Was this translation helpful? Give feedback.
-
|
This is good feedback, thanks! We'll get it fixed. |
Beta Was this translation helpful? Give feedback.
-
|
@timneutkens any advance on this topic ? I encounter the same error with a chunk related to node:inspector |
Beta Was this translation helpful? Give feedback.
-
import jackson from "@/server/services/jackson";
import { redirect } from "next/navigation";
export async function POST(req: Request) {
const { oauthController } = await jackson();
const formData = await req.formData();
const { redirect_url } = await oauthController.samlResponse({
RelayState: formData.get("RelayState") as string,
SAMLResponse: formData.get("SAMLResponse") as string,
});
redirect(redirect_url as string);
}import { clientEnv } from "@/env/client";
import { createUrl } from "@/lib/utils";
import jackson, {
type IConnectionAPIController,
type IDirectorySyncController,
type IOAuthController,
type ISPSSOConfig,
type JacksonOption,
type OIDCAuthzResponsePayload,
} from "@boxyhq/saml-jackson";
import config from "../db/config";
export type { OIDCAuthzResponsePayload };
interface Global {
apiController?: IConnectionAPIController;
oauthController?: IOAuthController;
directorySync?: IDirectorySyncController;
spConfig?: ISPSSOConfig;
}
const g: Global = global as unknown as Global;
const externalUrl = createUrl.subdomain("admin-cms").path();
const opts: JacksonOption = {
externalUrl: externalUrl,
samlAudience: clientEnv.NEXT_PUBLIC_APP_NAME,
samlPath: "/api/sso/acs",
oidcPath: "/api/sso/callback",
db: {
engine: "sql",
type: "mysql",
url: config.primary,
},
openid: {},
noAnalytics: true,
};
let apiController: IConnectionAPIController;
let oauthController: IOAuthController;
let directorySync: IDirectorySyncController;
let spConfig: ISPSSOConfig;
export default async function init() {
if (
!g.apiController ||
!g.oauthController ||
!g.directorySync ||
!g.spConfig
) {
const ret = await jackson(opts);
apiController = ret.apiController;
oauthController = ret.oauthController;
directorySync = ret.directorySyncController;
spConfig = ret.spConfig;
g.apiController = apiController;
g.oauthController = oauthController;
g.directorySync = directorySync;
g.spConfig = spConfig;
} else {
apiController = g.apiController;
oauthController = g.oauthController;
directorySync = g.directorySync;
spConfig = g.spConfig;
}
return {
apiController,
oauthController,
directorySync,
spConfig,
};
} |
Beta Was this translation helpful? Give feedback.
-
|
I'm having the same issue. Next 15.3.1 |
Beta Was this translation helpful? Give feedback.
-
|
Any update on this? I'm also having the same issue on Next 15.3.2. |
Beta Was this translation helpful? Give feedback.
-
|
I tested in the Next.js 15.4.0-canary.63 version, and it's now working properly. next build --turbopack builds in 36 seconds. 
next build uncached builds in 1 minute 23 seconds. 
|
Beta Was this translation helpful? Give feedback.
-
|
We are from LobeHub Team and building LobeChat with nextjs. I have tested the building with turbopack now and It's amazing fast! 
And Here is a compare of webpack and turbopack:
You can see turbopack reduce 60% building time! But there still an issue with integate with serwist: serwist/serwist#54 . Can wait to move to turbopack after this integration! |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Turbo build production fails with Prisma (tried on both 6.5.0 and 6.6.0 using the prisma-client-js generator): prisma schema folder structure prisma loaded in the frontend like this builds all ok without the turbo flag, and next dev --turbo also works fine |
Beta Was this translation helpful? Give feedback.
-
|
can you confirm that downgrading to 15.4.0-canary.35 breaks it again ? Be interested to know which commit fixes it ! |
Beta Was this translation helpful? Give feedback.
-
|
My build was completed successfully on 15.4.0-canary.35. |
Beta Was this translation helpful? Give feedback.
-
|
you know what my next comment will be haha |
Beta Was this translation helpful? Give feedback.
-
|
looks possibly like it was this commit in canary-28 this hopefully fixes it |
Beta Was this translation helpful? Give feedback.
-
|
I've checked, it's fixed in canary-28. |
Beta Was this translation helpful? Give feedback.
-
Build Performance Comparison
|
Beta Was this translation helpful? Give feedback.
-
|
خیلیییی سریعه 🔥🔥 |
Beta Was this translation helpful? Give feedback.
-
|
I with my small project don't see any performance benefits. Are we only supposed to see the benefits in bigger projects? I have even tried running the build command multiple times to see if i would get better results without any luck. I ran each of these with a clean build first. Hardware: running without > next build
▲ Next.js 15.3.0
- Experiments (use with caution):
✓ useCache
Creating an optimized production build ...
✓ Compiled successfully in 1000ms
✓ Linting and checking validity of types
✓ Collecting page data
✓ Generating static pages (6/6)
✓ Collecting build traces
✓ Finalizing page optimization
Route (app) Size First Load JS
┌ ƒ / 572 B 372 kB
├ ƒ /_not-found 990 B 105 kB
└ ƒ /login 572 B 372 kB
+ First Load JS shared by all 104 kB
├ chunks/1684-3cc8d39bf08bda7e.js 46.4 kB
├ chunks/4bd1b696-79901f1c062801da.js 53.2 kB
└ other shared chunks (total) 4.83 kB
ƒ Middleware 33.3 kB
ƒ (Dynamic) server-rendered on demand
npm run build 15.84s user 2.25s system 183% cpu 9.886 totalhyperfine benchmark running with > next build --turbopack
⚠ The config property `experimental.turbo` is deprecated. Move this setting to `config.turbopack` as Turbopack is now stable.
▲ Next.js 15.3.0 (Turbopack)
- Experiments (use with caution):
· turbo
✓ useCache
Creating an optimized production build ...
✓ Compiled successfully in 2.9s
✓ Linting and checking validity of types
✓ Collecting page data
✓ Generating static pages (6/6)
✓ Collecting build traces
✓ Finalizing page optimization
Route (app) Size First Load JS
┌ ƒ / 0 B 420 kB
├ ƒ /_not-found 0 B 420 kB
└ ƒ /login 0 B 420 kB
+ First Load JS shared by all 422 kB
├ chunks/1fa3394cc56fb597.js 77.1 kB
├ chunks/780cf8f2a2a5b7ec.js 13.1 kB
├ chunks/7e8ef395dd44ad63.js 270 kB
├ chunks/e694e57256351634.js 18.9 kB
└ other shared chunks (total) 42.9 kB
ƒ Middleware 50.5 kB
ƒ (Dynamic) server-rendered on demand
⚠ Support for Turbopack builds is experimental. We don't recommend deploying mission-critical applications to production.
- Turbopack currently always builds production sourcemaps for the browser. This will include project sourcecode if deployed to production.
- It is expected that your bundle size might be different from `next build` with webpack. This will be improved as we work towards stability.
- This build is without disk caching; subsequent builds will become faster when disk caching becomes available.
- When comparing output to webpack builds, make sure to first clear the Next.js cache by deleting the `.next` directory.
Provide feedback for Turbopack builds at https://github.com/vercel/next.js/discussions/77721
npm run build 22.58s user 3.21s system 237% cpu 10.879 totalhyperfine benchmark |
Beta Was this translation helpful? Give feedback.
-
|
Did you delete |
Beta Was this translation helpful? Give feedback.
-
|
Hi, I actually did delete the .next folder between runs. That's what I ment by "I ran each of these with a clean build first.". I had the same thoughts as you to begin with and ended up running the benchmarks more than 3 times :) |
Beta Was this translation helpful? Give feedback.
-
|
Yeah fair, given this app is super small not expecting much wins, it compiles with webpack in <1s already. Could you share the project so I can compare and check why it takes longer with Turbopack. If you have e.g. Tailwind that could be the reason because we have to boot a separate Node.js process for it. |
Beta Was this translation helpful? Give feedback.
-
|
Probably some unhandled cases in 
After investigating the reason, it is because dynamic imports in a route handler that referenced client components |
Beta Was this translation helpful? Give feedback.
-
|
Sounds like the same as #77036 |
Beta Was this translation helpful? Give feedback.
-
|
It is a vast improvement from webpack. In Webpack it takes 10 mins to compile and with |
Beta Was this translation helpful? Give feedback.
-
|
Using Turbo with Reproduction: https://github.com/remcohaszing/turbo-markdown-error |
Beta Was this translation helpful? Give feedback.
-
|
Can we turn off Source maps manually? |
Beta Was this translation helpful? Give feedback.
-
|
We ran into two problems which directly crash the build (15.3.1-canary.8) Turbopack crashes with SWC plugins when using absolute paths in swcPlugins configuration #78156 SWC plugin context in Turbopack includes only basename instead of full path #78181 |
Beta Was this translation helpful? Give feedback.
-
|
Full prefetching of dynamic routes using |
Beta Was this translation helpful? Give feedback.
-
|
When I tried to use Rust backtrace Let me know if I can share some extra details. |
Beta Was this translation helpful? Give feedback.
-
|
The following error only happens when |
Beta Was this translation helpful? Give feedback.
-
|
I am getting this issue. You can find reproduce repo in this link: https://github.com/yusifaliyevpro/FilmIsBest |
Beta Was this translation helpful? Give feedback.
-
|
Now it didn't work again. I didn't change any code or update dependency Same Error above |
Beta Was this translation helpful? Give feedback.
-
|
We haven't landed a fix for this yet. so the workaround is still to disable scope hoisting. |
Beta Was this translation helpful? Give feedback.
-
How can i disable? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks |
Beta Was this translation helpful? Give feedback.
-
|
it works fine for me but you have to have a good computer to handle the build process here is an output |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, you are right to be concerned! As a workaround you could configure some middleware to block access to This issue is fixed in the latest next@canary release as well and should go out in the next release. In fact i just deleted the scary warning text: #82591 |
Beta Was this translation helpful? Give feedback.
-
|
Thanks man! |
Beta Was this translation helpful? Give feedback.
-
@lukesandberg Is this issue ( does ship the source code on production ) fixed on 15.5.0 ? |
Beta Was this translation helpful? Give feedback.
-
|
Yep. It is fixed! |
Beta Was this translation helpful? Give feedback.
-
Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
I got this error after upgrading to v15.5.0. I'm using pages router 
|
Beta Was this translation helpful? Give feedback.
-
|
@bgub PTAL |
Beta Was this translation helpful? Give feedback.
-
|
@VictorHAS I think I've just fixed this, with #82856! It should be released in the next canary (today or tomorrow). Try it out and let me know if it works! |
Beta Was this translation helpful? Give feedback.
-
|
Ok tysm! I'll be waiting |
Beta Was this translation helpful? Give feedback.
-
|
It's working!! results: With turbopack: Without turbopack: |
Beta Was this translation helpful? Give feedback.
-
|
@VictorHAS awesome! Glad we were able to get it resolved! |
Beta Was this translation helpful? Give feedback.
-
|
I did a quick unscientific test of
Setup
|
Beta Was this translation helpful? Give feedback.
-
|
EDIT: @lukesandberg pointed out that it looks like Turbopack is in fact faster here. You need to look at wall time (the "total" number) and not CPU time (the "user" and "system" numbers). Turbopack does in fact consume more CPU time, but that shouldn't matter to most users who have 4 or more cores. Hey @tomquirk, just to verify, did you try deleting the Webpack uses a cache by default, while Turbopack persistent caching is still a canary-only experimental feature (https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopackPersistentCaching). If you're trying repeated builds with no changes, webpack might win just because everything is a cache hit. If it's still significantly slower than webpack, we can work with you on getting a trace file: https://nextjs.org/docs/app/api-reference/turbopack#generating-trace-files-for-performance-debugging |
Beta Was this translation helpful? Give feedback.
-
|
Yup, ran this between each build: |
Beta Was this translation helpful? Give feedback.
-
|
@tomquirk sorry, just updated my response, it looks like the wall time is in fact lower for Turbopack? It's just the CPU time that's higher. |
Beta Was this translation helpful? Give feedback.
-
Oh!!! You're so right. Thanks @lukesandberg ! Editing the OP |
Beta Was this translation helpful? Give feedback.
-
|
Depends on your site of course, but often the most direct comparison between webpack and turbopack is to compare the |
Beta Was this translation helpful? Give feedback.
-
|
I'm trying out Turbopack for the first time on a large project and the "First Load JS shared by all" is 3x larger with Turbopack. Turbopack takes about half the time and produces a lot more chunks, if that helps understand the issue.
Any idea what might be causing this? Stack:
|
Beta Was this translation helpful? Give feedback.
-
|
Based on #77721 (reply in thread), it looks like there is some additional code-splitting that Turbopack does not yet support. It seems likely that this is the cause of the larger bundle size. |
Beta Was this translation helpful? Give feedback.
-
|
All working fine, but build size got bigger. before and after almost doubled up artifact size Operating System:
Platform: darwin
Arch: arm64
Version: Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:26 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T8112
Available memory (MB): 16384
Available CPU cores: 8
Binaries:
Node: 22.15.0
npm: 10.9.2
Yarn: N/A
pnpm: 10.15.0
Relevant Packages:
next: 15.5.0 // Latest available version is detected (15.5.0).
eslint-config-next: 15.5.0
react: 19.1.1
react-dom: 19.1.1
typescript: 5.9.2
Next.js Config:
output: N/A |
Beta Was this translation helpful? Give feedback.
-
|
Same issues as mine. Do you use |
Beta Was this translation helpful? Give feedback.
-
|
@patik @sakib412 https://nextjs.org/docs/app/api-reference/turbopack#bundle-sizes |
Beta Was this translation helpful? Give feedback.
-
|
Here's reproduction code: import { TOTP } from 'otpauth';
export const generateTimedOTP = (secret: string) => {
const totp = new TOTP({
secret,
digits: 6,
algorithm: 'sha1',
period: 30,
});
return {
otp: totp.generate(),
expiration: new Date(Date.now() + totp.period * 1000),
};
};calling |
Beta Was this translation helpful? Give feedback.
-
|
I had to disable turbopack because I had hydration errors due to Emotion (emotion-js/emotion#3308). Sometimes the pages are loaded correctly, sometimes the hydration error occurs and I have to refresh the page multiple times until it can render the page without errors, which was very frustrating, so I disabled turbopack for now. |
Beta Was this translation helpful? Give feedback.
-
|
If I add it to the |
Beta Was this translation helpful? Give feedback.
-
|
This is not a turbopack compatibility issue; the feature is no longer experimental. As you said
so you should not “add it inside the |
Beta Was this translation helpful? Give feedback.
-
|
The previous build log was using it without the const nextConfig: NextConfig = {
typedRoutes: true
}Running the build with Copy/paste from this: https://nextjs.org/docs/app/api-reference/config/next-config-js/typedRoutes |
Beta Was this translation helpful? Give feedback.
-
|
I have |
Beta Was this translation helpful? Give feedback.
-
|
You're right, it was a cache issue with the package manager. Solved, thanks! |
Beta Was this translation helpful? Give feedback.
and others
Uh oh!
There was an error while loading. Please reload this page.
-
Thread for posting feedback about
next build --turbopack.Beta Was this translation helpful? Give feedback.
All reactions