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`
35 lines
627 B
Bash
35 lines
627 B
Bash
declare -a testCases=(
|
|
"with-typescript"
|
|
"with-next-sass"
|
|
# Tests @next/mdx
|
|
"with-mdx"
|
|
# Tests babel config
|
|
"with-styled-components"
|
|
)
|
|
|
|
set -e
|
|
|
|
# Speeds up testing locally
|
|
export CI=1
|
|
|
|
rm -rf ./e2e-tests
|
|
|
|
initialDir=$(pwd)
|
|
|
|
for testCase in "${testCases[@]}"
|
|
do
|
|
cd $initialDir
|
|
|
|
echo "--- Testing $testCase ---"
|
|
mkdir -p "./e2e-tests/$testCase"
|
|
cp -r "./examples/$testCase/." "./e2e-tests/$testCase"
|
|
cd "./e2e-tests/$testCase"
|
|
|
|
touch yarn.lock
|
|
yarn set version berry
|
|
yarn config set pnpFallbackMode none
|
|
yarn config set enableGlobalCache true
|
|
yarn link --all --private -r ../..
|
|
|
|
yarn build
|
|
done
|