Kristoffer K 1c75bf789b perf(next): use require.resolve instead of resolve (#19518) ... **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`		2021-01-11 14:43:08 +00:00
..
global.d.ts	Add TypeScript Definitions for Sass (#10363)	2020-02-03 00:03:42 -05:00
index.d.ts	Extend IncomingMessage type to include cookies from middleware (#19724)	2020-12-18 11:29:49 +00:00
misc.d.ts	perf(next): use require.resolve instead of resolve (#19518)	2021-01-11 14:43:08 +00:00
webpack.d.ts	Remove tslint disables (#16116)	2020-08-12 14:39:07 +00:00