You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What package manager are you using / does the bug impact?
Yarn v2/v3/v4 (node_modules linker only)
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
2.0.14
Describe the Bug
Hi @timneutkens - wanted to move the conversation from our thread on X so it'll be easier for you to track. Apologies for not including a minimal reproduction - it's a busy morning. Let me know if you need one and I can find some time to get you one this week.
FYI - this is not a huge issue that we're in a rush for you to solve. Just wanted to share my experience/feedback since you guys asked for it on X.
Here's the trace you asked for. I'm not sure if this is right, because it ends up in a trace (not trace.log). When I followed the documentation and tried to do "dev": "next dev --turbo NEXT_TURBOPACK_TRACING=1", I would get an error ⨯ Invalid project directory provided, no such directory: /Users/wl/personalprojects/friends-and-fables/apps/next/NEXT_TURBOPACK_TRACING=1. So I tried to set the env with export NEXT_TURBOPACK_TRACING=1, but even if I set it to 0, I noticed that there was a trace file in my .next that was getting logs appended regardless of the env.
We're using turbo@2.0.14 and tailwind@3.3.2. We do have a postcss.config.js but I don't see postcss in my package.json, so assuming it gets bundled with tailwind.
I'm actually not sure how fast turborepo is supposed to be, but I just know that my hot reloads feel about the same as before. I have not collected a ton of data on this, but I just know anecdotally that my old hot reload times were often between 4-8s and turborepo hot reload times are similar. Pre/post turbo, the reload times would always vary though, so its hard to say.
To Reproduce
Run yarn dev and make updates to code.
Additional context
No response
The text was updated successfully, but these errors were encountered:
Verify canary release
Link to code that reproduces this issue
https://github.com/vercel/turborepo
What package manager are you using / does the bug impact?
Yarn v2/v3/v4 (node_modules linker only)
What operating system are you using?
Mac
Which canary version will you have in your reproduction?
2.0.14
Describe the Bug
Hi @timneutkens - wanted to move the conversation from our thread on X so it'll be easier for you to track. Apologies for not including a minimal reproduction - it's a busy morning. Let me know if you need one and I can find some time to get you one this week.
FYI - this is not a huge issue that we're in a rush for you to solve. Just wanted to share my experience/feedback since you guys asked for it on X.
Here's the trace you asked for. I'm not sure if this is right, because it ends up in a
trace
(not trace.log). When I followed the documentation and tried to do"dev": "next dev --turbo NEXT_TURBOPACK_TRACING=1"
, I would get an error⨯ Invalid project directory provided, no such directory: /Users/wl/personalprojects/friends-and-fables/apps/next/NEXT_TURBOPACK_TRACING=1
. So I tried to set the env withexport NEXT_TURBOPACK_TRACING=1
, but even if I set it to 0, I noticed that there was atrace
file in my .next that was getting logs appended regardless of the env.We're using turbo@2.0.14 and tailwind@3.3.2. We do have a postcss.config.js but I don't see postcss in my package.json, so assuming it gets bundled with tailwind.
Expected Behavior
I'm actually not sure how fast turborepo is supposed to be, but I just know that my hot reloads feel about the same as before. I have not collected a ton of data on this, but I just know anecdotally that my old hot reload times were often between 4-8s and turborepo hot reload times are similar. Pre/post turbo, the reload times would always vary though, so its hard to say.
To Reproduce
Run
yarn dev
and make updates to code.Additional context
No response
The text was updated successfully, but these errors were encountered: