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
        2 hours 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
                            2 hours 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
                            2 hours 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
                            2 hours 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
                            2 hours 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
                          2 hours 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
                          2 hours 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 2 hours 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

                                          Сан-Квентин

                                          Image
                                          Сан-Квентин Местоположение Сан-Квентин, Калифорния Координаты 37°56′13″ с. ш. 122°29′20″ з. д. H G Я O L Текущий статус Действует Режим безопасности минимальный и максимальный Количество мест 3 302 Открытие Июнь 1852 Находится в ведомстве California Department of Corrections and Rehabilitation Начальник Mike Martel, начальник  Сан-Квентин на Викискладе Сан-Квентин (англ.  San Quentin ) — тюрьма, располагающаяся на 432 акрах (около 1,7 км²), на мысе Сан-Квентин, в округе Марин, штат Калифорния, США. Тюрьма штата Калифорния Сан-Квентин была открыта в июле 1852 года и является старейшей в штате. Она была построена заключёнными, которые проживали в течение строительства на тюремном судне Вабан. В Сан-Квентине отбывали наказание и мужчины, и женщины до 1934 года, когда построили женскую тюрьму в Техачапи и туда перевели всех заключённых женщин. В Сан-Квентине приводятся в исполнение смертные казни, для этого имеется газовая камера, но...
                                          Read more

                                          8-я гвардейская общевойсковая армия

                                          Image
                                          8-я гвардейская общевойсковая ордена Ленина армия Награды: Войска: РККА → Советская армия → СВ России Род войск: Формирование: 1943 Расформирование (преобразование): 1992 Предшественник: 62-я армия (1942—43) → 8-я гвардейская общевойсковая армия (1943—92) → 8-й гвардейский армейский корпус (1992—98) Боевой путь Изюм-Барвенковская операция Донбасская операция Запорожская операция Битва за Днепр Днепропетровская операция Березнеговато-Снигирёвская операция Одесская операция Люблин-Брестская операция Варшавско-Познанская операция Восточно-Померанская операция Берлинская наступательная операция У этого термина существуют и другие значения, см. 8-я армия. Фотография Гвардейского Красного Знамени (лицевая сторона) 8-й гвардейской армии , образца 1943 года. Фотография Гвардейского Красного Знамени (оборотная сторона) 8-й гвардейской армии , образца 1943 года. 8-я гвардейская общевойсковая ордена Ленина армия  — гвардейское фор...
                                          Read more

                                          Алькесар

                                          Image
                                          Муниципалитет Алькесар Alquézar Герб 42°10′16″ с. ш. 0°01′27″ в. д. H G Я O L Страна Испания   Испания Автономное сообщество Арагон Провинция Уэска Комарка Сомонтано-де-Барбастро Алькальд Хосе Марияно Альтемир Ласкорс (ИСРП) История и география Площадь 32,36 км² Высота НУМ 660 м Часовой пояс UTC+1, летом UTC+2 Население Население 313 человек ( 2010 ) Плотность 9,92 чел./км² Этнохороним alquezarano/-a Цифровые идентификаторы Телефонный код +34 974 Почтовые индексы 22112 Автомобильный код HU alquezar.org   (исп.) Показать/скрыть карты Алькесар Алькесар Алькесар  Аудио, фото и видео на Викискладе Алькесар (исп.  Alquézar ) — муниципалитет в Испании, входит в провинцию Уэска, в составе автономного сообщества Арагон. Муниципалитет находится в составе района (комарки) Сомонтано-де-Барбастро. Занимает площадь 32,36 км². Население — 321 челове...
                                          Read more