wmonk/create-react-app-typescript

vscode jest not getting env=jsdom?

Open

#139 opened on Aug 14, 2017

View on GitHub
 (4 comments) (1 reaction) (0 assignees)JavaScript (3,725 stars) (506 forks)batch import
help wantedquestion

Description

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"
}

Contributor guide

Tech stack
javascripttypescriptreactjest
Domain
developer experiencetesting
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Jest configurationVSCode settings
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.