[Bug]: next_js_binary failing on NextJS 16

[jfernbaugh-apex]

What happened?

NextJS 16 is failing to build utilizing the next_js_binary call due to failures with Turbopack symlinks.

Error documented here:
#2573

Version

Development (host) and target OS/architectures:

Output of bazel --version:
7.7.1

Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
2.0.0``

Language(s) and/or frameworks involved:
NextJS 16.X

How to reproduce

Upgrade a passing NextJS 15.X build to 16.X

Any other information?

No response

[kirkobyte]

It looks like this is because NextJS expects to have access to the rootDir of the project, which it expects to find via package-lock.json. https://nextjs.org/docs/app/api-reference/config/next-config-js/turbopack#root-directory

I'm curious whether this will work together with how node_modules are handled:

Turbopack uses the root directory to resolve modules. Files outside of the project root are not resolved.

The reason files are not resolved outside of the project root is to improve cache validation, reduce filesystem watching overhead, and reduce the number of resolving steps needed.

It seems like this could also be an issue for Next.js, to allow opting out of this feature

[jonaseriksson84]

FWIW I've created a (so far unanswered) issue on the Next.js repository here: vercel/next.js#91896