3 commits

Author	SHA1	Message	Date
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
Kristoffer K	104b8d4732	fix(next-mdx): resolve webpack loader (#17983) ... **What's the problem this PR addresses?** `@next/mdx` adds the webpack loader `@mdx-js/loader` without resolving it to an absolute path Depends on https://github.com/vercel/next.js/pull/17606 **How did you fix it?** `require.resolve` the webpack loader before adding it	2021-01-04 16:24:16 +00:00
Kristoffer K	e848a9e504	fix(next): add missing peer dependencies for sass support (#17606)	2021-01-04 10:30:46 -05:00