Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TypeError: Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '#<process>' #8069

Closed
juanjoDiaz opened this issue Mar 6, 2019 · 24 comments
Labels

Comments

@juanjoDiaz
Copy link

juanjoDiaz commented Mar 6, 2019

🚨 See #8069 (comment) for status 🚨

🐛 Bug Report

My jest tests works in all node versions but not node 11.11

TypeError: Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '#<process>'
  at _default (node_modules/jest-util/build/createProcessObject.js:85:34)

To Reproduce

https://travis-ci.org/juanjoDiaz/serverless-middleware/builds/502781207

Expected behavior

Jest behaves the same in all versions of Node.

Link to repl or repo (highly encouraged)

https://travis-ci.org/juanjoDiaz/serverless-middleware/builds/502781207

Issues without a reproduction link are likely to stall.

@cezaraugusto
Copy link

for those facing this issue: this happened after Node v11.11. the quickest fix is to downgrade Node to 11.10.1 in your CI lock file until further investigation

@leadegroot
Copy link

Seeing the same problem this morning - downgrading to node 11.10.1 works as a temp fix

sambehrens added a commit to dog-house-development/poodl that referenced this issue Mar 6, 2019
donatello added a commit to minio/minio that referenced this issue Mar 6, 2019
To fix jest related build failure as recommended at jestjs/jest#8069 (comment)
deekoder pushed a commit to minio/minio that referenced this issue Mar 7, 2019
To fix jest related build failure as recommended at jestjs/jest#8069 (comment)
hodgef added a commit to hodgef/simple-keyboard that referenced this issue Mar 7, 2019
@brennancheung
Copy link

brennancheung commented Mar 7, 2019

To save people using Travis some time, if you don't need the latest stable node you can modify your .travis.yml and add:

node_js:
- 8

Alternatively you can specify an earlier version of 11:

node_js:
- "11.10.1"

@SimenB
Copy link
Member

SimenB commented Mar 7, 2019

This has been fixed in #8050. Currently available as 24.2.0-alpha.0

@freezer278
Copy link

still have this issue with jest version 24.5.0, the only thing helped is downgrading node to 11.10.1

@SimenB
Copy link
Member

SimenB commented Mar 16, 2019

New version of Node is out with a fix: https://nodejs.org/en/blog/release/v11.12.0/

@naeemba
Copy link

naeemba commented Mar 16, 2019

@SimenB Seems there is no update for the current package (v11.12.0) on the arch packages yet.
https://www.archlinux.org/packages/community/x86_64/nodejs/

@SimenB
Copy link
Member

SimenB commented Mar 16, 2019

I don't know how or when arch do their updates, and that's not really relevant to this repo. The official release has dropped, when the different channels update is up to them 🙂

hanneskaeufler added a commit to hanneskaeufler/danger-plugin-mentor that referenced this issue Mar 17, 2019
@ldco2016
Copy link

None of the solutions above have helped me. You cannot upgrade Jest because react-scripts comes with version 23.x so you are just adding on top of what react-scripts would already have. You cannot upgrade react-scripts so that it will have jest@24 because the latest version has jest@23.

Changing to v11.10.1 does not help either and within my Dockerfile I have tried chainging the 'FROM' in my Dockerfile to FROM node:10.15-alpine and that has not helped.

This is so frustrating.

kiku-jw pushed a commit to kiku-jw/webpack that referenced this issue Apr 6, 2019
@github-actions
Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 12, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests