h3imdall / ftp-remote-edit

Edit files on ftp servers with Atom editor and without a workspace.
MIT License
178 stars 26 forks source link

Installing “ftp-remote-edit@0.18.2” failed. #428

Open Ideomania opened 3 years ago

Ideomania commented 3 years ago

Hello all.

Windows 10, newest atom (1.58.0).

Output:

npm ERR! code EPERM
npm ERR! syscall mkdir
npm ERR! path C:\Users\Bartek
npm ERR! errno -4048
npm ERR! Error: EPERM: operation not permitted, mkdir 'C:\Users\Bartek'
npm ERR!  [OperationalError: EPERM: operation not permitted, mkdir 'C:\Users\Bartek'] {
npm ERR!   cause: [Error: EPERM: operation not permitted, mkdir 'C:\Users\Bartek'] {
npm ERR!     errno: -4048,
npm ERR!     code: 'EPERM',
npm ERR!     syscall: 'mkdir',
npm ERR!     path: 'C:\\Users\\Bartek'
npm ERR!   },
npm ERR!   isOperational: true,
npm ERR!   stack: "Error: EPERM: operation not permitted, mkdir 'C:\\Users\\Bartek'",
npm ERR!   errno: -4048,
npm ERR!   code: 'EPERM',
npm ERR!   syscall: 'mkdir',
npm ERR!   path: 'C:\\Users\\Bartek'
npm ERR! }

This is because stupid windows, when installing and using on-line account, creates user account (folder to be exact) based on user email. So in the end, my user folder on windows is "c:\users\bartk".

I assume, path for installation of ftp-remote-edit is preselected from (pseudo macros) c:\users\%USERNAME%, and since my user name is "bartek", but my account data is stored in "bartk" it fails.

In that case, solution would be to get user's home folder from environment, rather then trying to re-create it (guess it).