Infinite compile loop in turbopack
Unanswered
Almond stone wasp posted this in #help-forum
Almond stone waspOP
Does anyone know how to debug a infinite compile loop in turbopack? Is there a flag or something we can set a trace?
My app works fine in --webpack but recently if you visit both a public route and a private route in localhost, I get the "Compiling..." all the time on the Next tools icon in Chrome and basically it'll try to recompile any page you are on over and over.
Curious if anyone else also has similar issues.
My app works fine in --webpack but recently if you visit both a public route and a private route in localhost, I get the "Compiling..." all the time on the Next tools icon in Chrome and basically it'll try to recompile any page you are on over and over.
Curious if anyone else also has similar issues.
6 Replies
Pacific sand lance
yep, same thing happened to me in monorepo after rapid code changes
+hit anormous allocation (i assume it was allocating memory and not releasing it until end of compilation)
what helped for me was cleaning workspace cache
Almond stone waspOP
Hey thanks for responding man. Like deleting the .next folder? Or is this something in VSC?
Pacific sand lance
in my case
git clean -xdf .cache .next .turbo node_modules.cache and .turbo are related to my turborepo setup so deleting .next and node_modules should be fine