Fixes #1 using fileURLToPath to properly resolve windows file path

[hsb-tonmoy]

Fixes Issue #1

[betomoedano]

Hi @hsb-tonmoy,

Thanks for the PR, I released a fix for that this morning. Please let me know if that works for you.

Otherwise, I'm happy to revisit this PR.

Thanks

[Copilot]

Pull Request Overview

Fixes Windows path resolution by converting import.meta.url to a file system path for the execute command’s dir parameter.

• Suppress punycode deprecation warnings with updated quoting style
• Import and use fileURLToPath and dirname from Node core modules
• Compute __dirname and pass it to execute instead of import.meta.url

Comments suppressed due to low confidence (3)

src/index.ts:19

• [nitpick] The name __dirname may be confused with the CommonJS global; consider renaming it to something like currentDir or projectDir to clarify its purpose.

const __dirname = dirname(fileURLToPath(import.meta.url));

src/index.ts:19

• Add a brief comment explaining why fileURLToPath and dirname are used to compute the directory path for cross-platform compatibility.

const __dirname = dirname(fileURLToPath(import.meta.url));

src/index.ts:21

• Add tests to verify that Windows-style paths are correctly resolved and passed to execute, ensuring the fix addresses the original issue.

await execute({ dir: __dirname });

[Copilot]

Removing all listeners for the 'warning' event can inadvertently disable other handlers; consider filtering only punycode deprecation warnings or document this side effect.

Suggested change

process.removeAllListeners("warning");