Open nicolassanmar opened 7 months ago
@nicolassanmar Thanks for raising an issue. As documented in the turbopack documentation, using webpack-based Next.js plugins as-is from next.config.js is not yet supported. Until we can actually write plugins for turbopack (I don't think this is possible just yet), the VE next plugin will not work with next --turbo
.
@askoufis Thanks! Seems reasonable then. It would be great if the webpack plugin got ported to turbopack. Reading this section seems to indicate that they are the ones writing these plugins, and Turbopack is not configurable yet:
Turbopack is in beta, so very few of these decisions are set in stone. In its current state, Turbopack cannot yet be configured - so plugins are not available yet.
Describe the bug
I'm trying to run my
next
app with the--turbo
flag as it drastically improves build times. This builds the project using Turbopack. This tool is still in beta, but more than 99% of its tests are passing: https://areweturboyet.com/. I never got any issues in projects that are not using vanilla extract.Unfortunately running
next dev --turbo
will cause the app to fail with the following error:I created this simple reproduction repo, where I just ran
create-next-app
and installed vanilla extract: https://github.com/nicolassanmar/vanilla-extract-turbopack-issue/tree/mainReproduction
https://github.com/nicolassanmar/vanilla-extract-turbopack-issue/tree/main
System Info
Used Package Manager
pnpm
Logs
Validations