Open richokorn opened 2 years ago
If I change the version to be install-peerdeps@2, I receive a few deprecation warnings the first time around:
CI=true npx install-peerdeps@2 --yarn --dev @upleveled/eslint-config-upleveled
And then once more seems to have the deprecation warnings mysteriously disappear:
Steps to reproduce original error:
yarn create next-app .
yarn add sharp
CI=true npx install-peerdeps@2 --yarn --dev @upleveled/eslint-config-upleveled
to produce second "error" case.Having exactly the same issue as @richokorn on Windows 11.
cc @nathanhleung a few different students using Windows have had this in our last cohorts, with different underlying errors. It seems something is undefined
in install-peerdeps
with Windows - unrelated to the actual error that happens from the command.
As it says on the tin.
Attempted to run all five lines of @upleveled ESLint config, which begins with:
CI=true npx install-peerdeps@latest --yarn --dev @upleveled/eslint-config-upleveled
Appears to run smoothly, and then thrown a cryptically short error:
OS: Windows 10 Terminal: Hyper Editor: VSCode Framework: Nextjs