Travis/Jest: TypeError: Cannot assign to read only property 'Symbol(Symbol.toStringTag)' of object '#'












16















All my jest typescript tests fail in my travis pipeline throwing the following error:



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


This happened suddenly without me changing anything particular in the code. And locally everything works fine.



Any ideas what could be happening ?










share|improve this question




















  • 3





    I just got the exact same error out of the blue in all of my builds.

    – JSeven
    15 hours ago
















16















All my jest typescript tests fail in my travis pipeline throwing the following error:



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


This happened suddenly without me changing anything particular in the code. And locally everything works fine.



Any ideas what could be happening ?










share|improve this question




















  • 3





    I just got the exact same error out of the blue in all of my builds.

    – JSeven
    15 hours ago














16












16








16


3






All my jest typescript tests fail in my travis pipeline throwing the following error:



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


This happened suddenly without me changing anything particular in the code. And locally everything works fine.



Any ideas what could be happening ?










share|improve this question
















All my jest typescript tests fail in my travis pipeline throwing the following error:



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


This happened suddenly without me changing anything particular in the code. And locally everything works fine.



Any ideas what could be happening ?







javascript reactjs typescript jestjs travis-ci






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 10 hours ago









Şivā SankĂr

1,1221922




1,1221922










asked 16 hours ago









FabulousCoFabulousCo

358310




358310








  • 3





    I just got the exact same error out of the blue in all of my builds.

    – JSeven
    15 hours ago














  • 3





    I just got the exact same error out of the blue in all of my builds.

    – JSeven
    15 hours ago








3




3





I just got the exact same error out of the blue in all of my builds.

– JSeven
15 hours ago





I just got the exact same error out of the blue in all of my builds.

– JSeven
15 hours ago












2 Answers
2






active

oldest

votes


















21














That is a bug that came with node v11.11. You can downgrade to v11.10 or wait for the fix which facebook has already pushed https://github.com/facebook/create-react-app/issues/6591



If your problem is TravisCI related then you can set a fixed version which works:



node_js:
- "11.10.1"





share|improve this answer





















  • 1





    the node_js: 11.10.1 worked, thanks !

    – FabulousCo
    11 hours ago





















5














You can also upgrade your version of jest to 24.3.0 which has this issue fixed. I believe this is a more future proof solution than downgrading your node.






share|improve this answer
























  • I upgraded to jest 24.3.1 and it did not work. Changed node version to 11.10.1 and it started working again

    – Nabuska
    7 hours ago













Your Answer






StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55059748%2ftravis-jest-typeerror-cannot-assign-to-read-only-property-symbolsymbol-tostr%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























2 Answers
2






active

oldest

votes








2 Answers
2






active

oldest

votes









active

oldest

votes






active

oldest

votes









21














That is a bug that came with node v11.11. You can downgrade to v11.10 or wait for the fix which facebook has already pushed https://github.com/facebook/create-react-app/issues/6591



If your problem is TravisCI related then you can set a fixed version which works:



node_js:
- "11.10.1"





share|improve this answer





















  • 1





    the node_js: 11.10.1 worked, thanks !

    – FabulousCo
    11 hours ago


















21














That is a bug that came with node v11.11. You can downgrade to v11.10 or wait for the fix which facebook has already pushed https://github.com/facebook/create-react-app/issues/6591



If your problem is TravisCI related then you can set a fixed version which works:



node_js:
- "11.10.1"





share|improve this answer





















  • 1





    the node_js: 11.10.1 worked, thanks !

    – FabulousCo
    11 hours ago
















21












21








21







That is a bug that came with node v11.11. You can downgrade to v11.10 or wait for the fix which facebook has already pushed https://github.com/facebook/create-react-app/issues/6591



If your problem is TravisCI related then you can set a fixed version which works:



node_js:
- "11.10.1"





share|improve this answer















That is a bug that came with node v11.11. You can downgrade to v11.10 or wait for the fix which facebook has already pushed https://github.com/facebook/create-react-app/issues/6591



If your problem is TravisCI related then you can set a fixed version which works:



node_js:
- "11.10.1"






share|improve this answer














share|improve this answer



share|improve this answer








edited 13 hours ago

























answered 15 hours ago









alknowsalknows

86111221




86111221








  • 1





    the node_js: 11.10.1 worked, thanks !

    – FabulousCo
    11 hours ago
















  • 1





    the node_js: 11.10.1 worked, thanks !

    – FabulousCo
    11 hours ago










1




1





the node_js: 11.10.1 worked, thanks !

– FabulousCo
11 hours ago







the node_js: 11.10.1 worked, thanks !

– FabulousCo
11 hours ago















5














You can also upgrade your version of jest to 24.3.0 which has this issue fixed. I believe this is a more future proof solution than downgrading your node.






share|improve this answer
























  • I upgraded to jest 24.3.1 and it did not work. Changed node version to 11.10.1 and it started working again

    – Nabuska
    7 hours ago


















5














You can also upgrade your version of jest to 24.3.0 which has this issue fixed. I believe this is a more future proof solution than downgrading your node.






share|improve this answer
























  • I upgraded to jest 24.3.1 and it did not work. Changed node version to 11.10.1 and it started working again

    – Nabuska
    7 hours ago
















5












5








5







You can also upgrade your version of jest to 24.3.0 which has this issue fixed. I believe this is a more future proof solution than downgrading your node.






share|improve this answer













You can also upgrade your version of jest to 24.3.0 which has this issue fixed. I believe this is a more future proof solution than downgrading your node.







share|improve this answer












share|improve this answer



share|improve this answer










answered 10 hours ago









Miroslav JonasMiroslav Jonas

1,9581227




1,9581227













  • I upgraded to jest 24.3.1 and it did not work. Changed node version to 11.10.1 and it started working again

    – Nabuska
    7 hours ago





















  • I upgraded to jest 24.3.1 and it did not work. Changed node version to 11.10.1 and it started working again

    – Nabuska
    7 hours ago



















I upgraded to jest 24.3.1 and it did not work. Changed node version to 11.10.1 and it started working again

– Nabuska
7 hours ago







I upgraded to jest 24.3.1 and it did not work. Changed node version to 11.10.1 and it started working again

– Nabuska
7 hours ago




















draft saved

draft discarded




















































Thanks for contributing an answer to Stack Overflow!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f55059748%2ftravis-jest-typeerror-cannot-assign-to-read-only-property-symbolsymbol-tostr%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

數位音樂下載

When can things happen in Etherscan, such as the picture below?

格利澤436b