magic-string error

[ferparra]

Describe the bug

Getting the following error after pnpm exec vitest

Error: Cannot use replaced character 610 as slice start anchor.
 ❯ MagicString.slice node_modules/.pnpm/[email protected]/node_modules/magic-string/dist/magic-string.es.mjs:924:10
 ❯ Object.transform node_modules/.pnpm/[email protected]_@[email protected]/node_modules/vite/dist/node/chunks/dep-V3BH7oO1.js:64060:62
 ❯ loadAndTransform node_modules/.pnpm/[email protected]_@[email protected]/node_modules/vite/dist/node/chunks/dep-V3BH7oO1.js:49741:29

Reproduction

Try using vi.hoisted in your code. I am not able to identify how to reproduce exactly because I'm unsure how to debug properly.

System Info

System:
    OS: macOS 14.2.1
    CPU: (8) arm64 Apple M2
    Memory: 59.13 MB / 16.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 21.5.0 - /opt/homebrew/bin/node
    npm: 10.2.4 - /opt/homebrew/bin/npm
    pnpm: 8.14.0 - /opt/homebrew/bin/pnpm
  Browsers:
    Safari: 17.2.1
  npmPackages:
    @vitejs/plugin-react: ^4.2.1 => 4.2.1 
    vitest: ^1.1.3 => 1.1.3

Used Package Manager

pnpm

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.

[github-actions]

Hello @ferparra. Please provide a minimal reproduction using a GitHub repository or StackBlitz. Issues marked with need reproduction will be closed if they have no activity within 3 days.

[getriebesand]

Reproduction
https://stackblitz.com/edit/vitest-dev-vitest-uqbyyy?file=test%2Fbasic.test.ts&initialPath=__vitest__/

[sheremet-va]

Reproduction stackblitz.com/edit/vitest-dev-vitest-uqbyyy?file=test%2Fbasic.test.ts&initialPath=vitest

This should give an error, but a different one. Is there a reason why you are calling vi.mock inside vi.hoisted? It's already hoisted. vi.hoisted is meant to be used to define variables that should be used inside vi.mock

[ferparra]

You are correct @sheremet-va. It was unnecessary.

Now the error is gone :)

[getriebesand]

my case I wanted to debug a problem with nuxt test-utils. This was probably not the right way, but I came across this error message, which I couldn't do anything with.

[sheremet-va]

We should define a better error message, so I will keep the issue open for now, if it's ok with you.