custom keyword definition is invalid: data.errors should be boolean












6















I just created new react app using command:



create-react-app mysite.com



After installation, when I tried to open it using npm start and yarn start, I got following error. 



throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));

      ^



Error: custom keyword definition is invalid: data.errors should be boolean

    at Ajv.addKeyword (/Users/myAccount/Documents/Dev/Projects/ReactJS/mysite.com/node_modules/ajv/lib/keyword.js:65:13)


Thanks.






reactjs create-react-app ajv







share|improve this question























  • Not sure, but maybe dots are not allowed in project names? That would probably cause such an error...

    – Luan Nico
    4 hours ago











  • Thank you @Luan, I just created a new app with no dots and no capital letters: create-react-app profilesite, but it's still giving me same error.

    – Ishan Patel
    4 hours ago











  • You could also try to update your global installation of create-react-app to the latest version, or at least check in which version you are. Again, just a guess.

    – Luan Nico
    4 hours ago
















6















I just created new react app using command:



create-react-app mysite.com



After installation, when I tried to open it using npm start and yarn start, I got following error. 



throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));

      ^



Error: custom keyword definition is invalid: data.errors should be boolean

    at Ajv.addKeyword (/Users/myAccount/Documents/Dev/Projects/ReactJS/mysite.com/node_modules/ajv/lib/keyword.js:65:13)


Thanks.






reactjs create-react-app ajv







share|improve this question























  • Not sure, but maybe dots are not allowed in project names? That would probably cause such an error...

    – Luan Nico
    4 hours ago











  • Thank you @Luan, I just created a new app with no dots and no capital letters: create-react-app profilesite, but it's still giving me same error.

    – Ishan Patel
    4 hours ago











  • You could also try to update your global installation of create-react-app to the latest version, or at least check in which version you are. Again, just a guess.

    – Luan Nico
    4 hours ago














6












6








6








I just created new react app using command:



create-react-app mysite.com



After installation, when I tried to open it using npm start and yarn start, I got following error. 



throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));

      ^



Error: custom keyword definition is invalid: data.errors should be boolean

    at Ajv.addKeyword (/Users/myAccount/Documents/Dev/Projects/ReactJS/mysite.com/node_modules/ajv/lib/keyword.js:65:13)


Thanks.






reactjs create-react-app ajv







share|improve this question














I just created new react app using command:



create-react-app mysite.com



After installation, when I tried to open it using npm start and yarn start, I got following error. 



throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));

      ^



Error: custom keyword definition is invalid: data.errors should be boolean

    at Ajv.addKeyword (/Users/myAccount/Documents/Dev/Projects/ReactJS/mysite.com/node_modules/ajv/lib/keyword.js:65:13)


Thanks.






reactjs create-react-app ajv




reactjs create-react-app ajv






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 4 hours ago









Ishan PatelIshan Patel

5241721




5241721













  • Not sure, but maybe dots are not allowed in project names? That would probably cause such an error...

    – Luan Nico
    4 hours ago











  • Thank you @Luan, I just created a new app with no dots and no capital letters: create-react-app profilesite, but it's still giving me same error.

    – Ishan Patel
    4 hours ago











  • You could also try to update your global installation of create-react-app to the latest version, or at least check in which version you are. Again, just a guess.

    – Luan Nico
    4 hours ago



















  • Not sure, but maybe dots are not allowed in project names? That would probably cause such an error...

    – Luan Nico
    4 hours ago











  • Thank you @Luan, I just created a new app with no dots and no capital letters: create-react-app profilesite, but it's still giving me same error.

    – Ishan Patel
    4 hours ago











  • You could also try to update your global installation of create-react-app to the latest version, or at least check in which version you are. Again, just a guess.

    – Luan Nico
    4 hours ago

















Not sure, but maybe dots are not allowed in project names? That would probably cause such an error...

– Luan Nico
4 hours ago





Not sure, but maybe dots are not allowed in project names? That would probably cause such an error...

– Luan Nico
4 hours ago













Thank you @Luan, I just created a new app with no dots and no capital letters: create-react-app profilesite, but it's still giving me same error.

– Ishan Patel
4 hours ago





Thank you @Luan, I just created a new app with no dots and no capital letters: create-react-app profilesite, but it's still giving me same error.

– Ishan Patel
4 hours ago













You could also try to update your global installation of create-react-app to the latest version, or at least check in which version you are. Again, just a guess.

– Luan Nico
4 hours ago





You could also try to update your global installation of create-react-app to the latest version, or at least check in which version you are. Again, just a guess.

– Luan Nico
4 hours ago












5 Answers
5






active

oldest

votes


















9














Comment out node_modules/ajv/lib/keyword.js at line 64-65 for a workaround solution:



if (!validateDefinition(definition))

  throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));


Ref: https://github.com/webpack/webpack/issues/8768






share|improve this answer































    8














    Reverting to an stable version of the ajv library also works:



    npm uninstall ajv
    
npm install ajv@6.8.1





    share|improve this answer































      4














      I thought that was something new coming with "@symfony/webpack-encore": "^0.23.0", however there's an issue with ajv lib



      Dirty fix:



      in




      node_modulesajv-errorsindex.js




      change errors: parameter at line 14 from 'full' to true



      Clean fix (temporary):



      Modify your package.json using this:



      "resolutions": {
      
    "ajv": "6.8.1"
      
  }





      share|improve this answer
























      • your clean fix should above your dirty fix imo, and this is the best answer to fix this (the clean fix version)

        – Ryan Castner
        1 hour ago



















      0














      I just tried to create app using following command:



      npx create-react-app my-app



      and it magically worked!



      Thanks.






      share|improve this answer































        0














        I get this error when I try and make a new nuxt app w/ npx



        npx create-nuxt-app <project-name>


        I did



        npm uninstall ajv
        
npm install ajv@6.8.1


        Like @robert Rodriguez It works, no errors






        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%2f54611735%2fcustom-keyword-definition-is-invalid-data-errors-should-be-boolean%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          5 Answers
          5






          active

          oldest

          votes








          5 Answers
          5






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          9














          Comment out node_modules/ajv/lib/keyword.js at line 64-65 for a workaround solution:



          if (!validateDefinition(definition))
          
  throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));


          Ref: https://github.com/webpack/webpack/issues/8768






          share|improve this answer




























            9














            Comment out node_modules/ajv/lib/keyword.js at line 64-65 for a workaround solution:



            if (!validateDefinition(definition))
            
  throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));


            Ref: https://github.com/webpack/webpack/issues/8768






            share|improve this answer


























              9












              9








              9







              Comment out node_modules/ajv/lib/keyword.js at line 64-65 for a workaround solution:



              if (!validateDefinition(definition))
              
  throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));


              Ref: https://github.com/webpack/webpack/issues/8768






              share|improve this answer













              Comment out node_modules/ajv/lib/keyword.js at line 64-65 for a workaround solution:



              if (!validateDefinition(definition))
              
  throw new Error('custom keyword definition is invalid: '  + this.errorsText(validateDefinition.errors));


              Ref: https://github.com/webpack/webpack/issues/8768







              share|improve this answer












              share|improve this answer



              share|improve this answer










              answered 3 hours ago









              mobjectmobject

              1182




              1182

























                  8














                  Reverting to an stable version of the ajv library also works:



                  npm uninstall ajv
                  
npm install ajv@6.8.1





                  share|improve this answer




























                    8














                    Reverting to an stable version of the ajv library also works:



                    npm uninstall ajv
                    
npm install ajv@6.8.1





                    share|improve this answer


























                      8












                      8








                      8







                      Reverting to an stable version of the ajv library also works:



                      npm uninstall ajv
                      
npm install ajv@6.8.1





                      share|improve this answer













                      Reverting to an stable version of the ajv library also works:



                      npm uninstall ajv
                      
npm install ajv@6.8.1






                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered 2 hours ago









                      Roberto RodriguezRoberto Rodriguez

                      9131117




                      9131117























                          4














                          I thought that was something new coming with "@symfony/webpack-encore": "^0.23.0", however there's an issue with ajv lib



                          Dirty fix:



                          in




                          node_modulesajv-errorsindex.js




                          change errors: parameter at line 14 from 'full' to true



                          Clean fix (temporary):



                          Modify your package.json using this:



                          "resolutions": {
                          
    "ajv": "6.8.1"
                          
  }





                          share|improve this answer
























                          • your clean fix should above your dirty fix imo, and this is the best answer to fix this (the clean fix version)

                            – Ryan Castner
                            1 hour ago
















                          4














                          I thought that was something new coming with "@symfony/webpack-encore": "^0.23.0", however there's an issue with ajv lib



                          Dirty fix:



                          in




                          node_modulesajv-errorsindex.js




                          change errors: parameter at line 14 from 'full' to true



                          Clean fix (temporary):



                          Modify your package.json using this:



                          "resolutions": {
                          
    "ajv": "6.8.1"
                          
  }





                          share|improve this answer
























                          • your clean fix should above your dirty fix imo, and this is the best answer to fix this (the clean fix version)

                            – Ryan Castner
                            1 hour ago














                          4












                          4








                          4







                          I thought that was something new coming with "@symfony/webpack-encore": "^0.23.0", however there's an issue with ajv lib



                          Dirty fix:



                          in




                          node_modulesajv-errorsindex.js




                          change errors: parameter at line 14 from 'full' to true



                          Clean fix (temporary):



                          Modify your package.json using this:



                          "resolutions": {
                          
    "ajv": "6.8.1"
                          
  }





                          share|improve this answer













                          I thought that was something new coming with "@symfony/webpack-encore": "^0.23.0", however there's an issue with ajv lib



                          Dirty fix:



                          in




                          node_modulesajv-errorsindex.js




                          change errors: parameter at line 14 from 'full' to true



                          Clean fix (temporary):



                          Modify your package.json using this:



                          "resolutions": {
                          
    "ajv": "6.8.1"
                          
  }






                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered 3 hours ago









                          Robert NenciuRobert Nenciu

                          434




                          434













                          • your clean fix should above your dirty fix imo, and this is the best answer to fix this (the clean fix version)

                            – Ryan Castner
                            1 hour ago



















                          • your clean fix should above your dirty fix imo, and this is the best answer to fix this (the clean fix version)

                            – Ryan Castner
                            1 hour ago

















                          your clean fix should above your dirty fix imo, and this is the best answer to fix this (the clean fix version)

                          – Ryan Castner
                          1 hour ago





                          your clean fix should above your dirty fix imo, and this is the best answer to fix this (the clean fix version)

                          – Ryan Castner
                          1 hour ago











                          0














                          I just tried to create app using following command:



                          npx create-react-app my-app



                          and it magically worked!



                          Thanks.






                          share|improve this answer




























                            0














                            I just tried to create app using following command:



                            npx create-react-app my-app



                            and it magically worked!



                            Thanks.






                            share|improve this answer


























                              0












                              0








                              0







                              I just tried to create app using following command:



                              npx create-react-app my-app



                              and it magically worked!



                              Thanks.






                              share|improve this answer













                              I just tried to create app using following command:



                              npx create-react-app my-app



                              and it magically worked!



                              Thanks.







                              share|improve this answer












                              share|improve this answer



                              share|improve this answer










                              answered 3 hours ago









                              Ishan PatelIshan Patel

                              5241721




                              5241721























                                  0














                                  I get this error when I try and make a new nuxt app w/ npx



                                  npx create-nuxt-app <project-name>


                                  I did



                                  npm uninstall ajv
                                  
npm install ajv@6.8.1


                                  Like @robert Rodriguez It works, no errors






                                  share|improve this answer




























                                    0














                                    I get this error when I try and make a new nuxt app w/ npx



                                    npx create-nuxt-app <project-name>


                                    I did



                                    npm uninstall ajv
                                    
npm install ajv@6.8.1


                                    Like @robert Rodriguez It works, no errors






                                    share|improve this answer


























                                      0












                                      0








                                      0







                                      I get this error when I try and make a new nuxt app w/ npx



                                      npx create-nuxt-app <project-name>


                                      I did



                                      npm uninstall ajv
                                      
npm install ajv@6.8.1


                                      Like @robert Rodriguez It works, no errors






                                      share|improve this answer













                                      I get this error when I try and make a new nuxt app w/ npx



                                      npx create-nuxt-app <project-name>


                                      I did



                                      npm uninstall ajv
                                      
npm install ajv@6.8.1


                                      Like @robert Rodriguez It works, no errors







                                      share|improve this answer












                                      share|improve this answer



                                      share|improve this answer










                                      answered 1 hour ago









                                      JustinJustin

                                      1277




                                      1277






























                                          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%2f54611735%2fcustom-keyword-definition-is-invalid-data-errors-should-be-boolean%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

                                          Knooppunt Holsloot

                                          Image
                                          Knooppunt Holsloot Kenmerken Wegen A37 × N34 Type knooppunt klaverblad Portaal     Verkeer & Vervoer Knooppunt Holsloot is een verkeersknooppunt op de kruising van de autosnelweg A37 en de N34 in Drenthe, tussen Emmen en Coevorden. Oorspronkelijk was deze aansluiting een afritconstructie van het type Haarlemmermeeraansluiting, zoals bij Knooppunt Hooipolder. Sinds 2002 is het knooppunt omgebouwd tot een volledig klaverblad. Als noviteit werd hier voor het eerst gebruikgemaakt van dimbare verlichting in plaats van de normale vaste tijden waarop de verlichting aan en uit gaat, wat een grote kostenbesparing opleverde. [1] Dat Holsloot als volwaardig knooppunt is uitgevoerd, waarbij alle verkeersstromen en afbuigingen ononderbroken kunnen doorgaan, is uitzonderlijk. Het betreft hier namelijk een aansluiting tussen een autosnelweg en niet-snelweg. Een vergelijkbare situatie treft men nabij Hoensbroek bij het knooppunt Ten Esschen.     Aa
                                          Read more

                                          Altaar (religie)

                                          Image
                                          Deel van de serie over kerkelijk gerei waaronder paramenten en liturgisch vaatwerk gebruikt in de liturgie Liturgisch vaatwerk Vasa sacra Miskelk · Pateen Kelklepeltje Ciborie · Monstrans Pyxis · Custodiale Vasa non sacra Ampullen · Wijwatervat Olievaatje Wierookvat · Ablutievat Paramenten Amict · Albe · Baarkleed · Cingel Tuniek · Dalmatiek · Fanon Kazuifel · Manipel · Stola Gremiale · Benedictievelum Mijter Koorkledij Rochet · Superplie Koorkap · Cappa magna Kovel Kelkgerei Bursa · Kelkvelum Ciborievelum Kerklinnen Corporale · Kelkdoekje Lavabodoekje · Palla Altaardwaal Kerkinterieur Altaar · Ambo Biechtstoel · Communiebank Doksaal · Doopvont Faldistorium Godslamp · Hoogaltaar Heilig Kruisaltaar Katheder · Preekstoel Sedilia Tabernakel · Volksaltaar Liturgische boeken Altaarmissaal Benedictionale · Brevier Evangeliarium · Evangelistarium Graduale · Kyriale Lectionarium Psalter · Rituaal Sacramentarium · Volksmissaal Overige Flambou
                                          Read more

                                          Gregoriusmis

                                          Image
                                          Een afbeelding van de Gregoriusmis uit een getijdenboek gemaakt in de zuidelijke Nederlanden tussen 1500 en 1525 Gregoriusmis, Meester van het Akense Altaar, ca. 1500-1525. Collectie Museum Catharijneconvent De Gregoriusmis of de Mis van Sint Gregorius is een motief in katholieke kunst, dat het eerst verscheen in de late Middeleeuwen en dat nog steeds werd gebruikt tijdens de contrareformatie. Paus Gregorius I (ca. 540-604) is afgebeeld, de H. Mis opdragend, terwijl Christus als de Man van Smarten verschijnt op het altaar dat voor Sint Gregorius staat. Volgens de legende had St. Gregorius gebeden om een teken voor een betwijfelaar van de transsubstantiatieleer, waarop de lijdende Christus tijdens het opdragen van de Mis verscheen om hem te overtuigen en waarbij zijn bloed in de altaarkelk liep. Vaak zijn ook de passiewerktuigen afgebeeld. Zie de categorie Mass of Saint Gregory van Wikimedia Commons voor mediabestanden over dit onderwerp. This page is onl
                                          Read more