1c75bf789b
**What's the problem this PR addresses?** - ~~https://github.com/vercel/next.js/pull/18768 started to ncc babel and thus it's version of resolve which breaks PnP support~~ Babel replaced `resolve` with the builtin `require.resolve` and a polyfill for older node versions in https://github.com/babel/babel/pull/12439 which was upgraded in https://github.com/vercel/next.js/pull/20586 - `next` unnecessarily bundles the `resolve` package when `require.resolve` is builtin and can do the same job **How did you fix it?** - ~~Avoid running `resolve` through ncc~~ Added a test for https://github.com/vercel/next.js/issues/19334 (closes https://github.com/vercel/next.js/issues/19334) - Replace `resolve` with `require.resolve` |
||
---|---|---|
.. | ||
typescript | ||
coalesced-function.ts | ||
constants.ts | ||
file-exists.ts | ||
find-config.ts | ||
find-pages-dir.ts | ||
get-package-version.ts | ||
is-serializable-props.ts | ||
load-custom-routes.ts | ||
non-nullable.ts | ||
oxford-comma-list.ts | ||
pretty-bytes.ts | ||
recursive-copy.ts | ||
recursive-delete.ts | ||
recursive-readdir.ts | ||
verifyTypeScriptSetup.ts |