Maia Teegarden

I dream of helping humanity peacefully coexist on Earth to build a better world 🐝 I get paid to write code that helps other coders peacefully coexist in a repo to build better apps 👩‍💻🛠️ One day I hope to self-actualize

@AndrewPierno @vitelabs @nextjs would love to dig deeper on this. would you be willing to share the source for the template or a profile so we can take a closer look? 🙏

I've had enough 😩 ... I'm moving all noco.io templates to @vitelabs + express. Was an avid @nextjs fan but they are cpu hungry and it's slow AF even with turbopack. Loved the DX but ... just too damn slow for my users :( Load times went from 30s to <5s🫣

I'm stepping into a new role, which means this awesome opportunity could be yours!

@perryraskin @rauchg @nextjs can you share what you ran into on the feedback discussion? 🙏 github.com/vercel/next.js…

@rauchg @nextjs Can’t wait to get that working in our super large internal nextjs codebase. While it works well in dev, my first try building with turbopack alpha failed. Looking for guidance on getting that set up properly if anyone is able to 🙏

Faire.com, the world's largest wholesale marketplace, is seeing @nextjs prod builds go from 6.3 minutes → 75s after adopting Turbopack 😳

@lewiscarhart @dobroslav_dev ah gotcha. just wanted to clarify because they get confused all the time. just so others are aware, the perf wins in the comment you were replying to would be the same with or without turborepo 👍

@padmaia @dobroslav_dev yes i was asking if he was using turbopack with turborepo

ngmi + we're already on nextjs 15.3 what are we doing wrong chat

@lewiscarhart @dobroslav_dev technically turbopack not turborepo turbopack is the bundler that is a dependency of Next.js turborepo is a separate monorepo tool

@dobroslav_dev w/ turborepo?

@Brooooook_lyn still a big fan of your work and super stoked to see how far napi-rs has come ❤️

@Brooooook_lyn our main blocker for compiling to wasm at the time was tokio, but that may no longer be the case. again, it's been a matter of priorities. we do plan to support it eventually, but adopting napi-rs wouldn't help in this case.

While I was still on the Vercel Turbopack team, I proposed using NAPI-RS to create a plugin system for Turbopack, allowing us to be somewhat compatible with the plugins already available in the community. However, this proposal was rejected at the time because compiling to wasm couldn’t tightly bind to Node-API. I had already planned to build the functionality for compiling NAPI-RS to wasm, but since I hadn’t started yet, I couldn’t counter the argument. Now, bundlers based on NAPI-RS like @rolldown_rs , and @rspack_dev can all run in the browser—what about Turbopack? areweturboyet?

It's happening 🙌 faster builds coming at ya one milestone at a time 🔜

@jimmeyer @rauchg @nextjs yep, still working on that! have you tried out 15.2 yet, though? it's significantly faster even with out disk caching yet.

@rauchg @nextjs Will the incremental builds shorten the time to restart the dev server? For your `ai-chatbot` template project, I'm seeing the same 6 second turbo build time for the root page regardless of whether it's the first run or restarts with the `.next` folder already present.

Huge milestone on @nextjs Turbopack production builds achieved internally. Vercel has one of the largest Next.js monorepos in the world. It's 8+ years old, has 65,000 modules, 7,800 dependencies, 70 active committers in Feb. The unlock: build speed scales with number of cores. We're building a gigantic app, cold, in ~1 minute. The bet on 🦀 @rustlang's support for shared-memory parallelism (an Achilles heel of JS-based tooling) is paying off wonderfully. Where do we go from here? • Keep an eye on areweturboyet⁠.com for progress • Incremental builds will be another dramatic speedup – the other reason we bet on a new compiler architecture • More memory and cold perf optimizations

Say it louder for the people in the back

@ag_dubs I thought $94 for joggers was ridiculous, but then I tried them on at REI and now I’m hooked. How do they make them so soft?!

@dmythro @nextjs @turborepo @vercel Turbopack uses LightningCSS which is more strict about using spec-compliant syntax. You'll have to follow the suggestion in the error message if you want to use Turbopack.

Well, my portfolio with PDF generation didn't break with the recent @nextjs and @turborepo. Everything seems pretty fast and built successfully via @vercel. Great DX :) I use this web app mainly to test new things. The only issue is `next dev --turbo` doesn't work with CSS modules for some reason. Only happens with `--turbo`. Wondering when Turbopack will finally pass 100% tests.

Next.js 14.2 ◆ Turbopack (RC): 99.8% of tests passing for `next dev --turbo` ◆ Build / Production Improvements: Reduced memory usage ◆ Caching Improvements: Configurable client-side cache revalidation ◆ Errors DX: Better hydration mismatch messages nextjs.org/blog/next-14-2

So close we can taste it! Building a bundler is a huge lesson in patience 🧘‍♀️ I'm so proud of my team for staying on course and iterating to greatness. There's still so much to do, but this is one milestone I can't wait to celebrate 🍾

@diegohaz @shadcn Can you share what Turbopack was having trouble importing? Or even better create/link a GitHub issue?

@shadcn I couldn’t even get the server to start due to import errors the last time I tried.

Going full turbo this year!

@GiancarlosIO @rspack_dev This is something we're aware of and will be significantly improving soon once we iron out some more basic bugs and features. I can reach out when that happens if you're willing to try it out again.

I learned this the hard way After migrating a project to Vite, we got a decrease in the speed of our dev server 😞 Turbopack make our computers consume a lot of ram which end up freezing/crashing the web browser 😟 Probably our next experiment would be try to use @rspack_dev

📢 Are you a Rust + Wasm expert? We'd love to discuss a @nextjs-related project with you! If you wanna work with us, send us a DM at @stackblitz or @elmd_ 👋

@tomus_sherman Sorry we were weren't able to get this fix into yesterday's patch, but I do want to note that it was published in another patch today within about 16 hours. Let us know how it goes 🙏

It wouldn't be so bad, but they reverted the fix _and then released a patch update_. As a Next.js user impacted by this bug in this very common feature it's left me feeling kinda burned

Next.js broke layouts in 404 pages, pushed a fix, but reverted it because it broke Turborepo apps Excuse me? Isn't turbo supposed to be alpha, why are users shipping on stable features being de-prioritised over experimental features?

Lot's of hard work in this one 💪 super proud of the team!

@TkDodo What version are you using? The message should include unsupported options you have configured in recent releases.

Trying out Turbopack. First impression: the error messages are not very helpful. It doesn't tell me which config is unsupported - only the ones which ARE supported....