826a237b18
This updates the default tracing root used when one isn't manually provided to be the directory of the closest lockfile. Previously it defaulted to the directory of the project being built which is incorrect in monorepos as any top-level dependencies wouldn't be traced correctly. Our tests were previously passing without this handling due to the env variable being manually set which this removes. x-ref: https://github.com/vercel/next.js/discussions/39432 x-ref: https://github.com/vercel/vercel/pull/9402 x-ref: [slack thread](https://vercel.slack.com/archives/C03S8ED1DKM/p1675821643786319) ## Bug - [x] Related issues linked using `fixes #number` - [x] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) |
||
---|---|---|
.. | ||
browsers | ||
next-modes | ||
amp-test-utils.js | ||
create-next-install.js | ||
e2e-utils.ts | ||
flat-map-polyfill.js | ||
mocks-require-hook.js | ||
next-test-utils.js | ||
next-webdriver.ts | ||
react-channel-require-hook.js | ||
use-temp-dir.ts |