kentcdodds / kentcdodds/react-jest-workshop

Yarn Run Setup failing at react-jest-workshop@1.0.0 validate script: receives object (where only string or buffer accepted)

Open
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
198
Forks
36
PR merge metrics
No merged PRs in 30d

Description

Your learning materials appear carefully thought out and very well constructed, and I am interested in working through the exercises in this workshop.

Should I be specifying a selection for the REGEX 'state' to allow just one of the either workshop or final states to build?

$ yarn run setup
yarn run v1.7.0
$ node ./scripts/verify && node ./scripts/install && npm run validate

📦 Installing dependencies via yarn install
[1/4] Resolving packages...
success Already up-to-date.

react-jest-workshop@1.0.0 validate C:\Users\MyUserName\Documents\react-jest-workshop
npm run generate -s && npm run lint -s && npm run test:final -s

(node:11748) UnhandledPromiseRejectionWarning: TypeError [ERR_INVALID_ARG_TYPE]: The "chunk" argument must be one of type string or Buff
er. Received type object
at validChunk (_stream_writable.js:258:10)
at WriteStream.Writable.write (_stream_writable.js:292:21)
at C:\Users\MyUserName\Documents\react-jest-workshop\node_modules\split-guide\dist\bin\index.js:41:20
(node:11748) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async
function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:11748) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not h
andled will terminate the Node.js process with a non-zero exit code.
Error: Jest: Failed to parse config file C:\Users\MYUserName\Documents\react-jest-workshop\exercises-final\jest.config.jso
n.
at parse (C:\Users\MyUserName\Documents\react-jest-workshop\node_modules\jest-config\build\loadFromFile.js:22:15)
at promisify.then.data (C:\Users\MyUserName\Documents\react-jest-workshop\node_modules\jest-config\build\loadFromFile.
js:26:20)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! react-jest-workshop@1.0.0 validate: npm run generate -s && npm run lint -s && npm run test:final -s
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the react-jest-workshop@1.0.0 validate script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\MyUserName\AppData\Roaming\npm-cache_logs\2018-07-22T16_50_19_715Z-debug.log
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Contributor guide

No contributing guide indexed for this repository

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 scripts/verify, scripts/install, the validate command shown in the log, and exercises-final/jest.config.json; reproduce yarn run setup and inspect the split-guide stack trace. Done means setup completes, the generated Jest configuration parses, and the validate script finishes successfully.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
testing, tooling
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.