wmonk/create-react-app-typescript

vscode jest not getting env=jsdom?

Open

#139 建立於 2017年8月14日

在 GitHub 查看
 (4 留言) (1 反應) (0 負責人)JavaScript (3,725 star) (506 fork)batch import
help wantedquestion

描述

Sorry this is kind of specific to my IDE (VSCode) but I hope many of you are using it too. I really like the Jest VSC extension but I haven't gotten it to work w/ my ejected CRA-typescript app yet. When I run the jest command from command line it works fine, but the IDE jest runner responds with:

 FAIL  src/routes/App.test.tsx
  ● renders without crashing

    ReferenceError: document is not defined
      
      at Object.<anonymous> (src/routes/App.test.tsx:6:15)
          at Promise (<anonymous>)
      at Promise.resolve.then.el (node_modules/p-map/index.js:42:16)
          at <anonymous>
      at process._tickCallback (internal/process/next_tick.js:188:7)


  ✕ renders without crashing (36ms)

I've tried changing my .vscode/settings.json in the project root folder to

{
   "jest.pathToJest": "node_modules/.bin/jest --env=jsdom"
}

貢獻者指南

技術棧
javascripttypescriptreactjest
領域
developer experiencetesting
議題類型
bug
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
under 1 hour
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
stale
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
clear
前置要求
Jest configurationVSCode settings
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
40
研究方向
The user reports that the VSCode Jest extension does not respect the env=jsdom flag when set via jest.pathToJest in settings.json, leading to 'document is not defined' error. To resolve, investigate how the VSCode Jest extension loads environment settings. The solution may involve creating a jest.config.js file with testEnvironment: 'jsdom' or using the extension's dedicated environment configuration option. Since the repository is deprecated, consider linking to relevant documentation or suggesting migration to updated CRA with TypeScript support.
vscode jest not getting env=jsdom? · wmonk/create-react-app-typescript#139 | Good First Issue