feat: add EPERM error handling to getErrorMessage

Signed-off-by: leocavalcante <leo@cavalcante.dev>

Author: leocavalcante

src/paths.mjs

@@ -64,6 +64,8 @@ export function getErrorMessage(error, file, targetPath) {
 	switch (code) {
 		case "EACCES":
 			return `Permission denied. Check write permissions for ${dirname(targetPath)}`
+		case "EPERM":
+			return "Operation not permitted. The file may be in use or locked"
 		case "ENOSPC":
 			return "Disk full. Free up space and try again"
 		case "ENOENT":

tests/paths.test.ts

@@ -111,6 +111,12 @@ describe("paths.mjs exports", () => {
 			)
 		})
 
+		it("should return operation not permitted message for EPERM error", () => {
+			const error = Object.assign(new Error("EPERM"), { code: "EPERM" })
+			const result = getErrorMessage(error, testFile, testTargetPath)
+			expect(result).toBe("Operation not permitted. The file may be in use or locked")
+		})
+
 		it("should return disk full message for ENOSPC error", () => {
 			const error = Object.assign(new Error("ENOSPC"), { code: "ENOSPC" })
 			const result = getErrorMessage(error, testFile, testTargetPath)