fix(next): always enable absoluteRuntime when running under webpack (#19538)
**What's the problem this PR addresses?** In https://github.com/vercel/next.js/pull/18921 I enabled `absoluteRuntime` for everyone (it was only enabled for PnP users) but didn't consider that people used the babel preset outside of the webpack build. Fixes https://github.com/vercel/next.js/issues/19448 - ~~Since it doesn't contain a repro I can't be certain but based on feedback from @koshea in https://github.com/vercel/next.js/pull/18921#issuecomment-733744645 I'll assume @RossMcMillan92 is doing the same thing, because when next is building it doesn't leave absolute paths as external.~~ Confirmed in https://github.com/vercel/next.js/pull/18921#issuecomment-734224014 **How did you fix it?** Only enable `absoluteRuntime` when the preset is running under `babel-loader`
Showing
想要评论请 注册 或 登录