Why do i see npm installing error after needle update

Since I updated needle engine, I see the error npm error code EPERM.
npm error the command again as root/Administrator.
npm error permissions of the file and its containing directories, or try running.

It was running perfectly fine before the update. I have my windows defender antivirus disabled.

Hello Saad! The error you’re experiencing with npm (error code EPERM) after updating Needle Engine could be due to permission issues or the file system format of your drive.

Here’s a step-by-step approach to troubleshoot this problem:

  1. Check Drive Formatting: Ensure that your project is located on an NTFS formatted drive. Node.js requires this for symlinks, which are crucial for npm installations. Other formats like exFAT or FAT32 might cause issues (see faq).

  2. Run as Administrator: Since you’re encountering a permissions error (EPERM), try running your command prompt or terminal as an Administrator. Right-click on your terminal program and select ‘Run as Administrator’.

  3. Node.js and npm Version: Make sure you are using a compatible version of npm. Needle Engine may now require a newer version. You might need to update npm by running npm install -g npm in your terminal (see releases).

  4. Check for Locked Files or Directories: Make sure there are no files or directories open in other programs that might be locking your npm directory.

  5. Re-install Node Modules: Sometimes, a clean reinstallation helps. Delete your node_modules folder and package-lock.json file, and then run npm install again.

  6. Antivirus Software: While you’ve mentioned disabling Windows Defender, ensure that it or other third-party antivirus programs aren’t interfering with your install. Temporarily disabling them might help identify if they’re the cause.

  7. Permissions on Project Directory: Verify that you have full access to the directories you’re working in. You can check this by going to the folder properties in Windows and navigating to the Security tab.

If the steps above don’t resolve your issue, could you confirm the versions of Node.js, npm, and Unity you’re using? This information will help in diagnosing the problem further.

24 replies left
thread_RDDj36iiRmXMy4dfPsdtZxXe
Reply to this message to continue the conversation

Did you solve the issue?

Yes I solved it. turns out the folder it was trying to install in was “hidden”. I removed it from hidden and changed its security properties. I still dont understand why it happened after updating needle engine. But this fixed it for me.

Interesting, which folder was that? Good to hear it’s solved!

it was a user folder in C:/Users/

This topic was automatically closed 13 days after the last reply. New replies are no longer allowed.