Skip to content
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

fs.mkdir already exists error is still hapenning #16536

Closed
mohas opened this issue Jan 19, 2025 · 6 comments
Closed

fs.mkdir already exists error is still hapenning #16536

mohas opened this issue Jan 19, 2025 · 6 comments
Labels
bug Something isn't working needs triage

Comments

@mohas
Copy link

mohas commented Jan 19, 2025

What version of Bun is running?

1.1.45

What platform is your computer?

Linux 6.1.0-22-amd64 x86_64 unknown

What steps can reproduce the bug?

running in my project:

bunx tailwindcss -i ./packages/project/public/styles/input.css -o ./packages/project/public/styles/theme.css -c ./packages/project/tailwind.config.js

What is the expected behavior?

should ignore mkdir call as the folder exists

What do you see instead?

EEXIST: file already exists, mkdir './packages/project/public/styles'                            
    path: "./packages/project/public/styles",                                                                                                                                                                          
 syscall: "mkdir",                                                                                                                                                                                                                          
   errno: -17,                                                                                                        
    code: "EEXIST"

Additional information

tailwindcss is throwing this error on this line:
https://github.com/tailwindlabs/tailwindcss/blob/a51b214c133da316583edd018102b236114a96ac/packages/%40tailwindcss-cli/src/commands/build/utils.ts#L22

we upgraded bun from 1.1.43 to 1.1.45 if that helps

@mohas mohas added bug Something isn't working needs triage labels Jan 19, 2025
@TiBianMod
Copy link

i think is fixed here: #16497

@RiskyMH
Copy link
Member

RiskyMH commented Jan 20, 2025

Fixed by @dylan-conway in #16497. The fix will be included in Bun v1.1.46 which releases very soon.

You can also try update via canary bun upgrade --canary if can't wait

@whjvenyl
Copy link

same.. seems the changelog for 1.1.45 is wrong then

mildronize added a commit to mildronize/blog-v8 that referenced this issue Jan 21, 2025
@lgarron
Copy link
Contributor

lgarron commented Jan 21, 2025

same.. seems the changelog for 1.1.45 is wrong then

I was also very confused about this. Our CI was failing due to this issue with 1.1.45+196621f25: 196621f25

@Jarred-Sumner, are you amenable to including an edit or errata to the release notes blog post at https://bun.sh/blog/bun-v1.1.45#fixed-fs-mkdir-recursive-regression ?

@lgarron
Copy link
Contributor

lgarron commented Jan 23, 2025

For anyone keeping track of this: this is fixed in bun 1.2. 🥳

@iamTanTanTan
Copy link

iamTanTanTan commented Mar 5, 2025

This problem is still exist on windows 11 24h2. (bun version 1.2.4)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs triage
Projects
None yet
Development

No branches or pull requests

6 participants