-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Avoid ESLint path resolution errors on Windows #469
Conversation
size-limit report 📦
|
To work around package resolution errors Alternative to upleveled/preflight#469
So the reason that the
So if we reduce the path length, then that would be another solution |
Using |
// 5 minute timeout for pnpm installation inside test repos | ||
300000, | ||
// 7.5 minute timeout for pnpm installation inside test repos | ||
450000, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we have to increase the timeout because it takes longer for pnpm to install on Windows in tmpdir()
apparently
Avoid ESLint path resolution errors on Windows, such as this test run failure:
Funny enough, the file that it cannot resolve above (
D:\a\preflight\preflight\__tests__\fixtures\__temp\next-js-passing\node_modules\.pnpm\[email protected]_@[email protected]_@[email protected]_@ty_xvhbeu5qc6hlxssq5gmtnagbti\node_modules\eslint-plugin-jsx-expressions\package.json
) actually does exist on disk:So seems like a bug in ESLint's package resolution, opened an issue