Failed to load url ../.vscode/extensions/vitest.explorer-0.5.15/dist/setupFile.mjs even though that file exists?

[rhefner]

Updating to the pre-release v0.5.15 I get the following when using in-source testing:

But the file exists:

$ ls -ltrah /Users/richard.hefner/.vscode/extensions/vitest.explorer-0.5.15/dist/setupFile.mjs
-rw-r--r--  1 richard.hefner  staff   203B Apr 11 11:06 /Users/richard.hefner/.vscode/extensions/vitest.explorer-0.5.15/dist/setupFile.mjs

The in-source test is similar to:

if (import.meta.vitest) {
  const { render, screen } = await import('@testing-library/react')
  const { createRemixStub } = await import('@remix-run/testing')
  const { ErrorBoundaryThatThrows } = await import('@myorg/remix/test-utils')

  let App: ReturnType<typeof createRemixStub>

  beforeEach(() => {
    App = createRemixStub([
      {
        path: '/',
        Component: Index,
        ErrorBoundary: ErrorBoundaryThatThrows,
      },
    ])
  })

  describe('home', () => {
    test('renders home page', () => {
      render(<App initialEntries={['/']} />)
    })
  })
}

When attempting to run the file, nothing is output in the "Vitest" output channel. Running the test manually with vitest works as expected.

Anyone else observed this?

[rhefner]

Hmm... This seems to happen even moving the test out into it's own file. :-\

[sheremet-va]

Just to test a theory, does adding server.fs.strict: false to the config helps?

export default defineConfig({
  server: {
    fs: {
      strict: false,
    }
  }
})

[rhefner]

Your theory was the fix for this issue. Thank you, @sheremet-va!

[sheremet-va]

Please, don't disable it just to fix vscode issue. I will release a patch where we do something similar in a more secure way. In the meantime, you can safely disable it if process.env.VITEST_VSCODE is present for example.

[rhefner]

Understood. 👍🏻