Skip to content

Conversation

@code-pace
Copy link

Description

Replaced new URL(import.meta.url).pathname with fileURLToPath(import.meta.url) when setting the __filename variable during QA-Shadow report generation.
This ensures Windows-compatible file paths.

Issue fixed

Fixes #110


Type of change

  • Bug fix

Related Tickets & Documents

Fixes #110


How Has This Been Tested?

  • Test 1: Ran npm test on Windows 10 and confirmed that report generation no longer produces backslash-prefixed paths.
  • Test 2: Manual execution of qa-shadow-report CLI to confirm successful report generation.

Any Blocked Test?

  • Test 1: Verify on macOS/Linux that fileURLToPath continues to resolve correctly without regressions.

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own code
  • My changes generate no new warnings, run: npm test
  • My changes generate no new lint errors, run: npm run lint
  • New and existing unit tests pass locally with my changes, run: npm test

Screenshot:

Error thrown before fix
491990761-c4ca815f-bb3b-46bf-9f21-0ef85f403ad4
No error thrown after fix
Screenshot 2025-09-21 154004
Generated report
Screenshot 2025-09-21 154055

Replaced new URL(import.meta.url).pathname with fileURLToPath(import.meta.url) when setting __filename variable during qa-shadow report generation. This ensures compatible Windows OS path
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant