chore: throw error object

[incognitojam]

It's best practice to throw Error objects - will include stacktrace and more details could be attached

[Copilot]

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

Comments suppressed due to low confidence (4)

src/workers/image.worker.js:52

• [nitpick] Consider including the original error as a cause (if supported by your runtime) by using the Error constructor option (e.g., throw new Error(Error opening file handle: ${e}, { cause: e })).

throw new Error(`Error opening file handle: ${e}`)

src/workers/image.worker.js:78

• [nitpick] Consider including the original error as a cause by passing it in the Error constructor options (e.g., { cause: e }) for better debugging.

throw new Error(`Error unpacking archive: ${e}`)

src/workers/image.worker.js:95

• [nitpick] Consider preserving the original error by using the cause option in the Error constructor (e.g., { cause: e }) to include additional debugging information.

throw new Error(`Error getting file handle: ${e}`)

src/utils/manager.js:192

• [nitpick] If this throw is within a try-catch block, consider including the caught error as a cause (e.g., { cause: err }) to ensure full error context is preserved.

throw new Error('Manifest is empty')