Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '#<process>'
See original GitHub issueVersion
3.5.1
Environment info
System:
OS: macOS 10.14.3
CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
Binaries:
Node: 11.11.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.7.0 - /usr/local/bin/npm
Browsers:
Chrome: 72.0.3626.121
Firefox: 64.0
Safari: 12.0.3
npmPackages:
@vue/babel-helper-vue-jsx-merge-props: 1.0.0-beta.2
@vue/babel-plugin-transform-vue-jsx: 1.0.0-beta.2
@vue/babel-preset-app: 3.5.1
@vue/babel-preset-jsx: 1.0.0-beta.2
@vue/babel-sugar-functional-vue: 1.0.0-beta.2
@vue/babel-sugar-inject-h: 1.0.0-beta.2
@vue/babel-sugar-v-model: 1.0.0-beta.2
@vue/babel-sugar-v-on: 1.0.0-beta.2
@vue/cli-overlay: 3.5.1
@vue/cli-plugin-babel: ^3.5.0 => 3.5.1
@vue/cli-plugin-e2e-nightwatch: ^3.5.0 => 3.5.1
@vue/cli-plugin-eslint: ^3.5.0 => 3.5.1
@vue/cli-plugin-unit-jest: ^3.5.0 => 3.5.1
@vue/cli-service: ^3.5.0 => 3.5.1
@vue/cli-shared-utils: 3.5.1
@vue/component-compiler-utils: 2.6.0
@vue/eslint-config-standard: ^4.0.0 => 4.0.0
@vue/preload-webpack-plugin: 1.1.0
@vue/test-utils: 1.0.0-beta.29 => 1.0.0-beta.29
@vue/web-component-wrapper: 1.2.0
eslint-plugin-vue: ^5.0.0 => 5.2.2
jest-serializer-vue: 2.0.2
vue: ^2.6.6 => 2.6.9
vue-eslint-parser: 5.0.0
vue-hot-reload-api: 2.3.3
vue-jest: 3.0.4
vue-loader: 15.7.0
vue-router: ^3.0.1 => 3.0.2
vue-style-loader: 4.1.2
vue-template-compiler: ^2.5.21 => 2.6.9
vue-template-es2015-compiler: 1.9.1
vuex: ^3.0.1 => 3.1.0
npmGlobalPackages:
@vue/cli: Not Found
Steps to reproduce
Create a standard Vue Project with Jest as the unit test framework. The sample test will fail with the following message.
Test suite failed to run
TypeError: Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '#<process>'
at exports.default (node_modules/jest-environment-jsdom/node_modules/jest-util/build/create_process_object.js:15:34)
What is expected?
test to pass
What is actually happening?
Test suite failed to run
TypeError: Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '#<process>'
at exports.default (node_modules/jest-environment-jsdom/node_modules/jest-util/build/create_process_object.js:15:34)
I believe this is related to the newest version of node (11.11.0) and has been addressed by Facebook as part of Jest 24.5.0 release (https://github.com/facebook/jest/commit/800f2f803d01c8ae194d71b251e4965dd70e5bf2)
Also posted in React Git Issue log: https://github.com/facebook/create-react-app/issues/6591
Issue Analytics
- State:
- Created 5 years ago
- Reactions:11
- Comments:7 (1 by maintainers)
Top Results From Across the Web
TypeError: Cannot assign to read only property 'Symbol ...
TypeError: Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '#<process>' at _default ...
Read more >Travis/Jest: TypeError: Cannot assign to read only property ...
I used FROM node:11.10-alpine without downgrading the version of node TravisCI uses. Save this answer.
Read more >TypeError: Cannot assign to read only ... - Travis CI Community
I have a React app that uses a Node.js express server for the API endpoints with MongoDB. The create-react-app starter project comes ...
Read more >Travis/Jest: TypeError: Cannot assign to read only property ...
Coding example for the question Travis/Jest: TypeError: Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '# '-Reactjs.
Read more >Cannot assign to 'X' because it is a read-only property (TS)
The error "Cannot assign to 'X' because it is a read-only property" occurs when we try to change the value of a read-only...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
had the same issue, solved when updating node to
v11.12.0
since it works with node 11.12, I’ll close it.