vitest-dev / vitest-dev/vitest

Vite-node fails with "SyntaxError: The requested module ... does not provide an export named ..."

Open
#7,971 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

pending triage
Dominant language
TypeScript
Stars
17.1k
Forks
2k
Avg merge
1d 22h
Merged PRs (30d)
94

Description

Describe the bug

When importing the library "@raydium-io/raydium-sdk-v2" in vite-node, it fails with "SyntaxError: The requested module 'lodash' does not provide an export named 'get'"

This does not happen when running via TSX or Bun.

Reproduction

https://stackblitz.com/edit/vitejs-vite-3mj8wbsg?file=README.md

System Info
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Memory: 0 Bytes / 0 Bytes
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 20.19.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - /usr/local/bin/npm
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    vite: ^6.3.5 => 6.3.5
Used Package Manager

npm

Validations

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the linked StackBlitz reproduction and the vite-node import of @raydium-io/raydium-sdk-v2 that fails on lodash.get. Compare the vite-node behavior with TSX and Bun, then identify the relevant Vitest or Vite-node entry point; done means the reproduction imports successfully without the export error.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript, vite
Domain
testing-qa, tooling
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.