Open Anyatsu opened 5 months ago
I'm also facing the same issue, not even sure what caused it because I think it was working fine before.
Also facing this. Not sure why we even got angular devkit in the mix as there's no angular code in the repo. I guess nx is using some code from angular to handle its monorepo orchestration
Hi, I think this is an issue with Next.js / turbopack and not necessarily Nx. I opened an issue on Next.js GH about it: https://github.com/vercel/next.js/issues/66602
Waiting for the Vercel team to address it or communicate about what can be done.
Thanks @ndcunningham - however the issue you linked seems to be purely related to Tailwind.
In this case the logs are showing errors importing Angular modules within a nx adaptar, for a repo that does not have any angular projects in it.
So is this a different issue?
Is turbopack not working for NX at the moment? Do we know which one was the last version on which it was supported? Is there a known workaround?
bumping this, same issue
same issue with next-i18next package
Just ran into this as well after upgrading to NextJs 15 where Turbo is supposed to be stable for dev
can I ask if the issue is solved for now?
can I ask if the issue is solved for now?
Not working for us yet.
Same issue here, next v15 & nx v20
hook.js:608 ./node_modules/.pnpm/nx@20.0.3_@swc-node+register@1.9.2_@swc+core@1.5.7_@swc+helpers@0.5.11__@swc+types@0.1.7_type_cxohwuiq2lf5alcyvrfldxcl4e/node_modules/nx/src/tasks-runner
Module not found: Can't resolve '/ROOT/node_modules/.pnpm/nx@20.0.3_@swc-node+register@1.9.2_@swc+core@1.5.7_@swc+helpers@0.5.11__@swc+types@0.1.7_type_cxohwuiq2lf5alcyvrfldxcl4e/node_modules/nx/src/tasks-runner/batch/run-batch.js'
server relative imports are not implemented yet. Please try an import relative to the file you are importing from.
+1
So the summary is that: https://github.com/vercel/next.js/issues/60363#issuecomment-1890480269 which basically means NX doesn't play nicely with CJS at the moment
Is there a plan to resolve this? If so, I propose removing the blocked:third-party
label since we cannot blame the NextJS nor tailwind on this anymore.
Not resolving this means future NextJS users cannot consider NX as viable option since the --turbo
that speeds up development is broken in NX
@FrozenPandaz @jaysoo @ndcunningham
+1 Highly waiting for any final resolution
Any updates, seems to be a common issue
Getting Same issue with nx, Any updates, seems to be a common issue
Same issue here. Waiting for updates.
Just want to share that we were able to resolve that on a relatively large project, it was not related NX even though the error message suggests that. For us it was mostly about some commonjs module, and we were able to resolve those after replacing. The way we debug was removing almost all dependancies from our project and then adding page by page to see which is bringing up the error.
@nurulhudaapon, very interesting! Would you mind sharing which packaged caused the issues for you?
@nurulhudaapon, very interesting! Would you mind sharing which packaged caused the issues for you?
For us it was https://github.com/MONEI/Shopify-api-node and https://github.com/adelsz/pgtyped. Mostly you do go through that path I mentioned to figure out what's causing issue.
Current Behavior
Running a NextJS app with the --turbo flag fails to compile when entering any page
Expected Behavior
The --turbo flag should work
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
Same result using both WSL Fedora Remix 39.01 and Windows