Graphql fragment imports do not work

[maxsalven]

Describe the bug

If your application code imports a graphql query which itself imports a fragment, then vitest will crash:

App.tsx:

import QUERY from "./Query.gql"
console.log(QUERY)

Query.gql

#import "./Fragment.gql"

query Foo {
  currentUser {
    ...CurrentUserFields
  }
}

Fragment.gql:

fragment CurrentUserFields on User {
  id
}

yarn test:

 FAIL  src/App.test.tsx [ src/App.test.tsx ]
Error: Parse failure: Unexpected token (1:9)
Contents of line 1: fragment CurrentUserFields on User {

However, the code works correctly in the vite dev environment:

yarn dev:

Reproduction

Reproduction here:
maxsalven/vitest-gql-bug@9b0ee6e

(Based off of https://github.com/vitest-dev/vitest/tree/main/examples/react-storybook-testing but it's not Storybook specific)

System Info

System:
    OS: macOS 12.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 107.22 MB / 64.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.1 - /var/folders/0c/63_dh8t91pg75b9w6sktbpw80000gn/T/fnm_multishells/90199_1645152149094/bin/node
    Yarn: 1.22.17 - /opt/homebrew/bin/yarn
    npm: 8.1.2 - /var/folders/0c/63_dh8t91pg75b9w6sktbpw80000gn/T/fnm_multishells/90199_1645152149094/bin/npm
  Browsers:
    Chrome: 98.0.4758.102
    Safari: 15.2
  npmPackages:
    @vitejs/plugin-react: ^1.2.0 => 1.2.0
    vite: latest => 2.8.3
    vitest: latest => 0.3.6

Used Package Manager

yarn

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.