-
Notifications
You must be signed in to change notification settings - Fork 34
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
chore(atomic): fix build on windows #3128
Conversation
Pull Request Report PR Title ✅ Title follows the conventional commit spec. Bundle Size
|
@lvu285 can you validate that all's well on your side? |
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.
Looks like potentially useful fix for upstream as well!
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.
Can't test on windows myself, but I think this looks good! LGTM 🎉
Agreed, I had planned to raised up the issue and discuss it with tailwind gang today. |
a9b178a
to
5aa8b08
Compare
@louis-bompart confirmed it fix the issue on my Windows. Thanks! |
Empirical fix, I didn't trace back exactly where it goes haywire.
Gut feeling: too much parallelism made using fs.promises, which in turn leads to Windows to because lower limits for opened files.
Solution: Reuse the synchronous code on Windows, and let Linux be Linux.
I prefer to not invest more, will prolly be fixed when Oxide (Tailwind not-so-secret Rust sauce that should come 🔜 ™️) will land.
https://coveord.atlassian.net/browse/KIT-2691