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
// For newer Next.js versions outputFileTracingRoot is not written to the output directly anymore, but we can use appDir and relativeAppDir to compute it.
102
+
// This assumes that relative app dir will never contain '..' segments. Some monorepos support workspaces outside of the monorepo root (verified with pnpm)
103
+
// However Next.js itself have some limits on it:
104
+
// - turbopack by default would throw "Module not found: Can't resolve '<name_of_package_outside_of_root>'"
105
+
// forcing user to manually set `outputFileTracingRoot` in next.config which will impact `appDir` and `relativeAppDir` preserving the lack of '..' in `relativeAppDir`
106
+
// - webpack case depends on wether dependency is marked as external or not:
107
+
// - if it's marked as external then standalone while working locally, it would never work when someone tries to deploy it (and not just on Netlify, but also in fully self-hosted scenarios)
108
+
// because parts of application would be outside of "standalone" directory
109
+
// - if it's not marked as external it will be included in next.js produced chunks
// due to changes in https://github.com/vercel/next.js/pull/86591 , this global is specific to instance of application and we to clean it up
110
+
// from any previous function invocations that might have run in the same process
0 commit comments