Everytime I try to build, this error comes up. In the console it says, “ERR: mkdir: Permission denied”
Building to glitch does work though.
I’m I doing something wrong?
by user 264626421891072001
Hello there – we have an experimental AI bot 
that might be able to help you with your question. Would you like to try this out?
How it works:
Reply to the messages of the bot that end with a thread_id to interact with it and ask follow-up questions. You can also mention the bot directly in this channel to get help.
Help requested: please wait a moment…
Here is what I found for you 
Discord
Hello Brendanluu,
The error message “ERR: mkdir: Permission denied” indicates that the process trying to create a directory does not have the necessary permissions to do so. This can happen in various circumstances, for example when trying to write to a read-only file system, to a directory where the user does not have write permissions, or when security policies prevent the creation of directories.
If building to Glitch works but you face this issue with another destination, it suggests that the issue might be with the specific permissions of the folder or the environment where you are trying to build the project.
Here are a few steps you can take to troubleshoot and resolve the issue:
- Check the permissions of the directory you are trying to build into.
- Make sure that you have write access to that directory.
- If you are using an IDE like Visual Studio Code, make sure it is run with the necessary privileges.
- Double-check the build path specified in the build settings to ensure it is correct and writable.
- If working in a restricted environment (like a corporate or academic network), check if there are any policies that restrict directory creation.
Let me know if you need guidance on how to check or modify directory permissions so I can further assist you.
1 messages left GPT 4
thread_asoMrQ3wKfd25g4iqZVqqMMT
Thanks for your feedback!
@brendanluu which Needle version are you on? I remember that issue popped up a while ago on Mac specifically but should have been fixed already
I think this happens only the first time - when you click “Ok” the terminal should open with the local server