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
I am looking for an honest answer on what can we expect regarding usage of Turbopack and NX.
This issue has been open for a while: #26510 but I was unable to find a formal response.
Is it something that we can expect to have in the near future? Or is there some kind of commercial/non-technical issue that prevents it and we should we start considering other options?
Honestly, we are too invested in the NX ecosystem to move away from it due to this issue. But we do need to look at alternatives to our current DX situation for Next.js. I'd love to read an honest take from the NX team.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello NX Team!
I am looking for an honest answer on what can we expect regarding usage of Turbopack and NX.
This issue has been open for a while: #26510 but I was unable to find a formal response.
Is it something that we can expect to have in the near future? Or is there some kind of commercial/non-technical issue that prevents it and we should we start considering other options?
Honestly, we are too invested in the NX ecosystem to move away from it due to this issue. But we do need to look at alternatives to our current DX situation for Next.js. I'd love to read an honest take from the NX team.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions