Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RangeError: [nuxt:components:imports] path should be a path.relative()d string, #28262

Open
treygrr opened this issue Jul 22, 2024 · 0 comments

Comments

@treygrr
Copy link

treygrr commented Jul 22, 2024

Environment


  • Operating System: Windows_NT
  • Node Version: v20.12.2
  • Nuxt Version: 3.12.4
  • CLI Version: 3.12.0
  • Nitro Version: 2.9.7
  • Package Manager: [email protected]
  • Builder: -
  • User Config: compatibilityDate, devtools
  • Runtime Modules: -
  • Build Modules: -

Reproduction

First Reproduction

Minimal Reproduction Repo:
https://github.com/treygrr/nuxt-vitest-playwright-ext-error

  1. npm i
  2. Install playwright test runner extension
Id: ms-playwright.playwright
Description: Run Playwright Test tests in Visual Studio Code.
Version: 1.1.7
Publisher: Microsoft
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=ms-playwright.playwright
  1. Run tests with play button in extension

image

Observe:
image

Second Reproduction

  1. Run npx playwright test

Observe:
Tests pass
image

Third Reproduction

  1. Run Extension "Debug Test"

Observe:
Tests pass
image

Describe the bug

Tests run with playwright extension fail with

RangeError: [nuxt:components:imports] path should be a `path.relative()`d string, but got "c:/Users/trey/Desktop/nuxt-vitest-playwright-ext-error/vite/preload-helper.js"

Additional context

Tests performed with command line pass.
Tests performed with Extension "Run Test" fails.
Additionally, to make this awkward - Tests performed with Extension "Debug Test" pass in extension. If this is a configuration issue, I am happy to update docs with necessary information to avoid this configuration mishap in the future.

Logs

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant