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

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;








47















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
    Mar 8 at 9:41

















47















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
    Mar 8 at 9:41













47












47








47


4






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 Mar 8 at 14:29









Şivā SankĂr

1,29011022




1,29011022










asked Mar 8 at 9:00









FabulousCoFabulousCo

533612




533612







  • 3





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

    – JSeven
    Mar 8 at 9:41












  • 3





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

    – JSeven
    Mar 8 at 9:41







3




3





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

– JSeven
Mar 8 at 9:41





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

– JSeven
Mar 8 at 9:41












6 Answers
6






active

oldest

votes


















59














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
    Mar 8 at 13:52












  • I'm also experiencing this issue. Thanks it works for me.

    – Vince Llauderes
    Mar 9 at 6:34


















21














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
    Mar 8 at 17:40












  • Worked for me: travis-ci.com/ghengeveld/react-async/builds/103781190

    – Gert Hengeveld
    Mar 9 at 16:14


















4














This was fixed for me by just upgrading node to v11.12.0






share|improve this answer






























    2














    For those of you who can't fix the problem with either of the above answers, try upgrading your jest to ^24.3.0 and downgrading the node version in your docker image of your client container. I used FROM node:11.10-alpine without downgrading the version of node TravisCI uses.






    share|improve this answer






























      1














      There were mainly two solutions for this problem



      • Upgrade your jest version to 24.3.0 ( which didn't worked for me)

      • Downgrade your node version to 11.10.1

      I know that downgrading node version is not a good solution but for those who want to run your tests anyways can try it. By downgrading their node version from 11.11.1 to 11.10.1
      Install package call "n" .
      This n package helps you to Interactively Manage Your Node.js Versions



      npm install -g n


      After installing it you just run



      sudo n 11.10.1


      and your node version will get changed you can check the node version by running



      node --version


      And later can run there test



      npm test


      It worked for me
      I hope it will be helpful :)






      share|improve this answer






























        1














        if you use nvm (node version manager),



        nvm install v11


        nvm use v11





        share|improve this answer























          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

























          6 Answers
          6






          active

          oldest

          votes








          6 Answers
          6






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          59














          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
            Mar 8 at 13:52












          • I'm also experiencing this issue. Thanks it works for me.

            – Vince Llauderes
            Mar 9 at 6:34















          59














          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
            Mar 8 at 13:52












          • I'm also experiencing this issue. Thanks it works for me.

            – Vince Llauderes
            Mar 9 at 6:34













          59












          59








          59







          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 Mar 8 at 11:36

























          answered Mar 8 at 10:03









          alknowsalknows

          1,24111622




          1,24111622







          • 1





            the node_js: 11.10.1 worked, thanks !

            – FabulousCo
            Mar 8 at 13:52












          • I'm also experiencing this issue. Thanks it works for me.

            – Vince Llauderes
            Mar 9 at 6:34












          • 1





            the node_js: 11.10.1 worked, thanks !

            – FabulousCo
            Mar 8 at 13:52












          • I'm also experiencing this issue. Thanks it works for me.

            – Vince Llauderes
            Mar 9 at 6:34







          1




          1





          the node_js: 11.10.1 worked, thanks !

          – FabulousCo
          Mar 8 at 13:52






          the node_js: 11.10.1 worked, thanks !

          – FabulousCo
          Mar 8 at 13:52














          I'm also experiencing this issue. Thanks it works for me.

          – Vince Llauderes
          Mar 9 at 6:34





          I'm also experiencing this issue. Thanks it works for me.

          – Vince Llauderes
          Mar 9 at 6:34













          21














          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
            Mar 8 at 17:40












          • Worked for me: travis-ci.com/ghengeveld/react-async/builds/103781190

            – Gert Hengeveld
            Mar 9 at 16:14















          21














          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
            Mar 8 at 17:40












          • Worked for me: travis-ci.com/ghengeveld/react-async/builds/103781190

            – Gert Hengeveld
            Mar 9 at 16:14













          21












          21








          21







          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 Mar 8 at 14:59









          Miroslav JonasMiroslav Jonas

          2,2551428




          2,2551428












          • 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
            Mar 8 at 17:40












          • Worked for me: travis-ci.com/ghengeveld/react-async/builds/103781190

            – Gert Hengeveld
            Mar 9 at 16:14

















          • 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
            Mar 8 at 17:40












          • Worked for me: travis-ci.com/ghengeveld/react-async/builds/103781190

            – Gert Hengeveld
            Mar 9 at 16:14
















          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
          Mar 8 at 17:40






          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
          Mar 8 at 17:40














          Worked for me: travis-ci.com/ghengeveld/react-async/builds/103781190

          – Gert Hengeveld
          Mar 9 at 16:14





          Worked for me: travis-ci.com/ghengeveld/react-async/builds/103781190

          – Gert Hengeveld
          Mar 9 at 16:14











          4














          This was fixed for me by just upgrading node to v11.12.0






          share|improve this answer



























            4














            This was fixed for me by just upgrading node to v11.12.0






            share|improve this answer

























              4












              4








              4







              This was fixed for me by just upgrading node to v11.12.0






              share|improve this answer













              This was fixed for me by just upgrading node to v11.12.0







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered Mar 17 at 1:15









              KylerKyler

              411




              411





















                  2














                  For those of you who can't fix the problem with either of the above answers, try upgrading your jest to ^24.3.0 and downgrading the node version in your docker image of your client container. I used FROM node:11.10-alpine without downgrading the version of node TravisCI uses.






                  share|improve this answer



























                    2














                    For those of you who can't fix the problem with either of the above answers, try upgrading your jest to ^24.3.0 and downgrading the node version in your docker image of your client container. I used FROM node:11.10-alpine without downgrading the version of node TravisCI uses.






                    share|improve this answer

























                      2












                      2








                      2







                      For those of you who can't fix the problem with either of the above answers, try upgrading your jest to ^24.3.0 and downgrading the node version in your docker image of your client container. I used FROM node:11.10-alpine without downgrading the version of node TravisCI uses.






                      share|improve this answer













                      For those of you who can't fix the problem with either of the above answers, try upgrading your jest to ^24.3.0 and downgrading the node version in your docker image of your client container. I used FROM node:11.10-alpine without downgrading the version of node TravisCI uses.







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Mar 10 at 19:41









                      Dariell VasquezDariell Vasquez

                      212




                      212





















                          1














                          There were mainly two solutions for this problem



                          • Upgrade your jest version to 24.3.0 ( which didn't worked for me)

                          • Downgrade your node version to 11.10.1

                          I know that downgrading node version is not a good solution but for those who want to run your tests anyways can try it. By downgrading their node version from 11.11.1 to 11.10.1
                          Install package call "n" .
                          This n package helps you to Interactively Manage Your Node.js Versions



                          npm install -g n


                          After installing it you just run



                          sudo n 11.10.1


                          and your node version will get changed you can check the node version by running



                          node --version


                          And later can run there test



                          npm test


                          It worked for me
                          I hope it will be helpful :)






                          share|improve this answer



























                            1














                            There were mainly two solutions for this problem



                            • Upgrade your jest version to 24.3.0 ( which didn't worked for me)

                            • Downgrade your node version to 11.10.1

                            I know that downgrading node version is not a good solution but for those who want to run your tests anyways can try it. By downgrading their node version from 11.11.1 to 11.10.1
                            Install package call "n" .
                            This n package helps you to Interactively Manage Your Node.js Versions



                            npm install -g n


                            After installing it you just run



                            sudo n 11.10.1


                            and your node version will get changed you can check the node version by running



                            node --version


                            And later can run there test



                            npm test


                            It worked for me
                            I hope it will be helpful :)






                            share|improve this answer

























                              1












                              1








                              1







                              There were mainly two solutions for this problem



                              • Upgrade your jest version to 24.3.0 ( which didn't worked for me)

                              • Downgrade your node version to 11.10.1

                              I know that downgrading node version is not a good solution but for those who want to run your tests anyways can try it. By downgrading their node version from 11.11.1 to 11.10.1
                              Install package call "n" .
                              This n package helps you to Interactively Manage Your Node.js Versions



                              npm install -g n


                              After installing it you just run



                              sudo n 11.10.1


                              and your node version will get changed you can check the node version by running



                              node --version


                              And later can run there test



                              npm test


                              It worked for me
                              I hope it will be helpful :)






                              share|improve this answer













                              There were mainly two solutions for this problem



                              • Upgrade your jest version to 24.3.0 ( which didn't worked for me)

                              • Downgrade your node version to 11.10.1

                              I know that downgrading node version is not a good solution but for those who want to run your tests anyways can try it. By downgrading their node version from 11.11.1 to 11.10.1
                              Install package call "n" .
                              This n package helps you to Interactively Manage Your Node.js Versions



                              npm install -g n


                              After installing it you just run



                              sudo n 11.10.1


                              and your node version will get changed you can check the node version by running



                              node --version


                              And later can run there test



                              npm test


                              It worked for me
                              I hope it will be helpful :)







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered Mar 14 at 15:09









                              Ishu SinghIshu Singh

                              111




                              111





















                                  1














                                  if you use nvm (node version manager),



                                  nvm install v11


                                  nvm use v11





                                  share|improve this answer



























                                    1














                                    if you use nvm (node version manager),



                                    nvm install v11


                                    nvm use v11





                                    share|improve this answer

























                                      1












                                      1








                                      1







                                      if you use nvm (node version manager),



                                      nvm install v11


                                      nvm use v11





                                      share|improve this answer













                                      if you use nvm (node version manager),



                                      nvm install v11


                                      nvm use v11






                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered Mar 19 at 11:38









                                      AmamazzingAmamazzing

                                      1112




                                      1112



























                                          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

                                          How to check contact read email or not when send email to Individual?

                                          Displaying single band from multi-band raster using QGIS

                                          How many registers does an x86_64 CPU actually have?