Why is npm start (after create-react-app) failing to run?

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












11















After I create a sample react app using create-react-app, npm start fails.



I have tried this using node 11.4 and 10.4 (npm 6.4.1)



>npm install create-react-app -g
>create-react-app t2
>cd t2
>npm start


expected: to be able to start simple react server to hit in browser at localhost:3000



actual: server did not start, got this in my terminal:




Salvatores-iMac:t2 samr$ npm start

> t2@0.1.0 start /Users/samr/dev/githubs/react/t2
> react-scripts start

/Users/samr/dev/githubs/react/t2/node_modules/ajv/lib/keyword.js:65
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/samr/dev/githubs/react/t2/node_modules/ajv/lib/keyword.js:65:13)
at module.exports (/Users/samr/dev/githubs/react/t2/node_modules/ajv-errors/index.js:10:7)
at Object.<anonymous> (/Users/samr/dev/githubs/react/t2/node_modules/schema-utils/src/validateOptions.js:22:1)
at Module._compile (internal/modules/cjs/loader.js:723:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:734:10)
at Module.load (internal/modules/cjs/loader.js:620:32)
at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
at Function.Module._load (internal/modules/cjs/loader.js:552:3)
at Module.require (internal/modules/cjs/loader.js:659:17)
at require (internal/modules/cjs/helpers.js:22:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! t2@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the t2@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/samr/.npm/_logs/2019-02-09T23_19_40_848Z-debug.log










share|improve this question
























  • Looks like a known issue: github.com/webpack/webpack/issues/8768

    – Lambda Fairy
    Feb 9 at 23:47











  • I'm running into this as well. Npm start worked fine for me for an app I created last night, but today I tried to use create-react-app for a new project, and in the new project npm start is not working for me. Copying over my node_modules folder from my previous app did help as a temporary workaround, but once I tried installing react router into my new app and then running npm start, I'm running into this error once again.

    – cathamatic
    Feb 10 at 0:07











  • same here, maybe you can check this github.com/webpack/webpack/issues/8768, changing the file in file node_modulesajv-errorsindex.js as someone says here solved it for now as a quick fix

    – PepitoPompin
    Feb 10 at 0:16















11















After I create a sample react app using create-react-app, npm start fails.



I have tried this using node 11.4 and 10.4 (npm 6.4.1)



>npm install create-react-app -g
>create-react-app t2
>cd t2
>npm start


expected: to be able to start simple react server to hit in browser at localhost:3000



actual: server did not start, got this in my terminal:




Salvatores-iMac:t2 samr$ npm start

> t2@0.1.0 start /Users/samr/dev/githubs/react/t2
> react-scripts start

/Users/samr/dev/githubs/react/t2/node_modules/ajv/lib/keyword.js:65
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/samr/dev/githubs/react/t2/node_modules/ajv/lib/keyword.js:65:13)
at module.exports (/Users/samr/dev/githubs/react/t2/node_modules/ajv-errors/index.js:10:7)
at Object.<anonymous> (/Users/samr/dev/githubs/react/t2/node_modules/schema-utils/src/validateOptions.js:22:1)
at Module._compile (internal/modules/cjs/loader.js:723:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:734:10)
at Module.load (internal/modules/cjs/loader.js:620:32)
at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
at Function.Module._load (internal/modules/cjs/loader.js:552:3)
at Module.require (internal/modules/cjs/loader.js:659:17)
at require (internal/modules/cjs/helpers.js:22:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! t2@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the t2@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/samr/.npm/_logs/2019-02-09T23_19_40_848Z-debug.log










share|improve this question
























  • Looks like a known issue: github.com/webpack/webpack/issues/8768

    – Lambda Fairy
    Feb 9 at 23:47











  • I'm running into this as well. Npm start worked fine for me for an app I created last night, but today I tried to use create-react-app for a new project, and in the new project npm start is not working for me. Copying over my node_modules folder from my previous app did help as a temporary workaround, but once I tried installing react router into my new app and then running npm start, I'm running into this error once again.

    – cathamatic
    Feb 10 at 0:07











  • same here, maybe you can check this github.com/webpack/webpack/issues/8768, changing the file in file node_modulesajv-errorsindex.js as someone says here solved it for now as a quick fix

    – PepitoPompin
    Feb 10 at 0:16













11












11








11


2






After I create a sample react app using create-react-app, npm start fails.



I have tried this using node 11.4 and 10.4 (npm 6.4.1)



>npm install create-react-app -g
>create-react-app t2
>cd t2
>npm start


expected: to be able to start simple react server to hit in browser at localhost:3000



actual: server did not start, got this in my terminal:




Salvatores-iMac:t2 samr$ npm start

> t2@0.1.0 start /Users/samr/dev/githubs/react/t2
> react-scripts start

/Users/samr/dev/githubs/react/t2/node_modules/ajv/lib/keyword.js:65
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/samr/dev/githubs/react/t2/node_modules/ajv/lib/keyword.js:65:13)
at module.exports (/Users/samr/dev/githubs/react/t2/node_modules/ajv-errors/index.js:10:7)
at Object.<anonymous> (/Users/samr/dev/githubs/react/t2/node_modules/schema-utils/src/validateOptions.js:22:1)
at Module._compile (internal/modules/cjs/loader.js:723:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:734:10)
at Module.load (internal/modules/cjs/loader.js:620:32)
at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
at Function.Module._load (internal/modules/cjs/loader.js:552:3)
at Module.require (internal/modules/cjs/loader.js:659:17)
at require (internal/modules/cjs/helpers.js:22:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! t2@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the t2@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/samr/.npm/_logs/2019-02-09T23_19_40_848Z-debug.log










share|improve this question
















After I create a sample react app using create-react-app, npm start fails.



I have tried this using node 11.4 and 10.4 (npm 6.4.1)



>npm install create-react-app -g
>create-react-app t2
>cd t2
>npm start


expected: to be able to start simple react server to hit in browser at localhost:3000



actual: server did not start, got this in my terminal:




Salvatores-iMac:t2 samr$ npm start

> t2@0.1.0 start /Users/samr/dev/githubs/react/t2
> react-scripts start

/Users/samr/dev/githubs/react/t2/node_modules/ajv/lib/keyword.js:65
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/samr/dev/githubs/react/t2/node_modules/ajv/lib/keyword.js:65:13)
at module.exports (/Users/samr/dev/githubs/react/t2/node_modules/ajv-errors/index.js:10:7)
at Object.<anonymous> (/Users/samr/dev/githubs/react/t2/node_modules/schema-utils/src/validateOptions.js:22:1)
at Module._compile (internal/modules/cjs/loader.js:723:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:734:10)
at Module.load (internal/modules/cjs/loader.js:620:32)
at tryModuleLoad (internal/modules/cjs/loader.js:560:12)
at Function.Module._load (internal/modules/cjs/loader.js:552:3)
at Module.require (internal/modules/cjs/loader.js:659:17)
at require (internal/modules/cjs/helpers.js:22:18)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! t2@0.1.0 start: `react-scripts start`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the t2@0.1.0 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR! /Users/samr/.npm/_logs/2019-02-09T23_19_40_848Z-debug.log







reactjs create-react-app






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Mar 1 at 19:23









Heretic Monkey

6,56663470




6,56663470










asked Feb 9 at 23:27









javazenjavazen

6617




6617












  • Looks like a known issue: github.com/webpack/webpack/issues/8768

    – Lambda Fairy
    Feb 9 at 23:47











  • I'm running into this as well. Npm start worked fine for me for an app I created last night, but today I tried to use create-react-app for a new project, and in the new project npm start is not working for me. Copying over my node_modules folder from my previous app did help as a temporary workaround, but once I tried installing react router into my new app and then running npm start, I'm running into this error once again.

    – cathamatic
    Feb 10 at 0:07











  • same here, maybe you can check this github.com/webpack/webpack/issues/8768, changing the file in file node_modulesajv-errorsindex.js as someone says here solved it for now as a quick fix

    – PepitoPompin
    Feb 10 at 0:16

















  • Looks like a known issue: github.com/webpack/webpack/issues/8768

    – Lambda Fairy
    Feb 9 at 23:47











  • I'm running into this as well. Npm start worked fine for me for an app I created last night, but today I tried to use create-react-app for a new project, and in the new project npm start is not working for me. Copying over my node_modules folder from my previous app did help as a temporary workaround, but once I tried installing react router into my new app and then running npm start, I'm running into this error once again.

    – cathamatic
    Feb 10 at 0:07











  • same here, maybe you can check this github.com/webpack/webpack/issues/8768, changing the file in file node_modulesajv-errorsindex.js as someone says here solved it for now as a quick fix

    – PepitoPompin
    Feb 10 at 0:16
















Looks like a known issue: github.com/webpack/webpack/issues/8768

– Lambda Fairy
Feb 9 at 23:47





Looks like a known issue: github.com/webpack/webpack/issues/8768

– Lambda Fairy
Feb 9 at 23:47













I'm running into this as well. Npm start worked fine for me for an app I created last night, but today I tried to use create-react-app for a new project, and in the new project npm start is not working for me. Copying over my node_modules folder from my previous app did help as a temporary workaround, but once I tried installing react router into my new app and then running npm start, I'm running into this error once again.

– cathamatic
Feb 10 at 0:07





I'm running into this as well. Npm start worked fine for me for an app I created last night, but today I tried to use create-react-app for a new project, and in the new project npm start is not working for me. Copying over my node_modules folder from my previous app did help as a temporary workaround, but once I tried installing react router into my new app and then running npm start, I'm running into this error once again.

– cathamatic
Feb 10 at 0:07













same here, maybe you can check this github.com/webpack/webpack/issues/8768, changing the file in file node_modulesajv-errorsindex.js as someone says here solved it for now as a quick fix

– PepitoPompin
Feb 10 at 0:16





same here, maybe you can check this github.com/webpack/webpack/issues/8768, changing the file in file node_modulesajv-errorsindex.js as someone says here solved it for now as a quick fix

– PepitoPompin
Feb 10 at 0:16












4 Answers
4






active

oldest

votes


















7














Quick fix is mentioned here https://github.com/webpack/webpack/issues/8768



Essentially go to node_modules/ajv/lib/keyword.js and comment out lines 64 and 65.






share|improve this answer


















  • 1





    There is no ajv folder in my node_modules directory

    – Abel Agoi
    Feb 10 at 0:35


















8














As @atsnam has said, you can find the resolution here https://github.com/webpack/webpack/issues/8768.



If you use yarn



add below to package.json



"resolutions": 
"ajv": "6.8.1"



then run yarn install



if you use npm



npm uninstall ajv
npm install ajv@6.8.1


That worked for me






share|improve this answer























  • it won't work if you deploy the app. i suggest adding "ajv": "6.8.1" into the dependencies instead

    – jsnewbie
    Feb 10 at 19:28











  • Just modify to npm install --save ajv@6.8.1

    – aquilesb
    Feb 10 at 23:56











  • if you're using npm 5 or newer, all installs should be saved to package.json by default

    – Lambda Fairy
    Feb 16 at 22:59


















1














just add resolutions to your package.json like this:



 
"dependencies":
...

"resolutions":
"ajv": "6.8.1"




then run npm install. if you use yarn, yarn install






share|improve this answer

























  • I added this, did the npm install, but npm start still fails the same way.

    – javazen
    Feb 10 at 1:37


















0














As per the suggestion in Github answers the below change has enabled me to work.



To fix this error, just change:
Line 14: `errors: 'full',`
to:
Line 14: `errors: true`
in file **node_modulesajv-errorsindex.js**





share|improve this answer





















    protected by Community Feb 10 at 0:16



    Thank you for your interest in this question.
    Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



    Would you like to answer one of these unanswered questions instead?














    4 Answers
    4






    active

    oldest

    votes








    4 Answers
    4






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    7














    Quick fix is mentioned here https://github.com/webpack/webpack/issues/8768



    Essentially go to node_modules/ajv/lib/keyword.js and comment out lines 64 and 65.






    share|improve this answer


















    • 1





      There is no ajv folder in my node_modules directory

      – Abel Agoi
      Feb 10 at 0:35















    7














    Quick fix is mentioned here https://github.com/webpack/webpack/issues/8768



    Essentially go to node_modules/ajv/lib/keyword.js and comment out lines 64 and 65.






    share|improve this answer


















    • 1





      There is no ajv folder in my node_modules directory

      – Abel Agoi
      Feb 10 at 0:35













    7












    7








    7







    Quick fix is mentioned here https://github.com/webpack/webpack/issues/8768



    Essentially go to node_modules/ajv/lib/keyword.js and comment out lines 64 and 65.






    share|improve this answer













    Quick fix is mentioned here https://github.com/webpack/webpack/issues/8768



    Essentially go to node_modules/ajv/lib/keyword.js and comment out lines 64 and 65.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Feb 10 at 0:16









    atsnamatsnam

    16417




    16417







    • 1





      There is no ajv folder in my node_modules directory

      – Abel Agoi
      Feb 10 at 0:35












    • 1





      There is no ajv folder in my node_modules directory

      – Abel Agoi
      Feb 10 at 0:35







    1




    1





    There is no ajv folder in my node_modules directory

    – Abel Agoi
    Feb 10 at 0:35





    There is no ajv folder in my node_modules directory

    – Abel Agoi
    Feb 10 at 0:35













    8














    As @atsnam has said, you can find the resolution here https://github.com/webpack/webpack/issues/8768.



    If you use yarn



    add below to package.json



    "resolutions": 
    "ajv": "6.8.1"



    then run yarn install



    if you use npm



    npm uninstall ajv
    npm install ajv@6.8.1


    That worked for me






    share|improve this answer























    • it won't work if you deploy the app. i suggest adding "ajv": "6.8.1" into the dependencies instead

      – jsnewbie
      Feb 10 at 19:28











    • Just modify to npm install --save ajv@6.8.1

      – aquilesb
      Feb 10 at 23:56











    • if you're using npm 5 or newer, all installs should be saved to package.json by default

      – Lambda Fairy
      Feb 16 at 22:59















    8














    As @atsnam has said, you can find the resolution here https://github.com/webpack/webpack/issues/8768.



    If you use yarn



    add below to package.json



    "resolutions": 
    "ajv": "6.8.1"



    then run yarn install



    if you use npm



    npm uninstall ajv
    npm install ajv@6.8.1


    That worked for me






    share|improve this answer























    • it won't work if you deploy the app. i suggest adding "ajv": "6.8.1" into the dependencies instead

      – jsnewbie
      Feb 10 at 19:28











    • Just modify to npm install --save ajv@6.8.1

      – aquilesb
      Feb 10 at 23:56











    • if you're using npm 5 or newer, all installs should be saved to package.json by default

      – Lambda Fairy
      Feb 16 at 22:59













    8












    8








    8







    As @atsnam has said, you can find the resolution here https://github.com/webpack/webpack/issues/8768.



    If you use yarn



    add below to package.json



    "resolutions": 
    "ajv": "6.8.1"



    then run yarn install



    if you use npm



    npm uninstall ajv
    npm install ajv@6.8.1


    That worked for me






    share|improve this answer













    As @atsnam has said, you can find the resolution here https://github.com/webpack/webpack/issues/8768.



    If you use yarn



    add below to package.json



    "resolutions": 
    "ajv": "6.8.1"



    then run yarn install



    if you use npm



    npm uninstall ajv
    npm install ajv@6.8.1


    That worked for me







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Feb 10 at 2:03









    aquilesbaquilesb

    36116




    36116












    • it won't work if you deploy the app. i suggest adding "ajv": "6.8.1" into the dependencies instead

      – jsnewbie
      Feb 10 at 19:28











    • Just modify to npm install --save ajv@6.8.1

      – aquilesb
      Feb 10 at 23:56











    • if you're using npm 5 or newer, all installs should be saved to package.json by default

      – Lambda Fairy
      Feb 16 at 22:59

















    • it won't work if you deploy the app. i suggest adding "ajv": "6.8.1" into the dependencies instead

      – jsnewbie
      Feb 10 at 19:28











    • Just modify to npm install --save ajv@6.8.1

      – aquilesb
      Feb 10 at 23:56











    • if you're using npm 5 or newer, all installs should be saved to package.json by default

      – Lambda Fairy
      Feb 16 at 22:59
















    it won't work if you deploy the app. i suggest adding "ajv": "6.8.1" into the dependencies instead

    – jsnewbie
    Feb 10 at 19:28





    it won't work if you deploy the app. i suggest adding "ajv": "6.8.1" into the dependencies instead

    – jsnewbie
    Feb 10 at 19:28













    Just modify to npm install --save ajv@6.8.1

    – aquilesb
    Feb 10 at 23:56





    Just modify to npm install --save ajv@6.8.1

    – aquilesb
    Feb 10 at 23:56













    if you're using npm 5 or newer, all installs should be saved to package.json by default

    – Lambda Fairy
    Feb 16 at 22:59





    if you're using npm 5 or newer, all installs should be saved to package.json by default

    – Lambda Fairy
    Feb 16 at 22:59











    1














    just add resolutions to your package.json like this:



     
    "dependencies":
    ...

    "resolutions":
    "ajv": "6.8.1"




    then run npm install. if you use yarn, yarn install






    share|improve this answer

























    • I added this, did the npm install, but npm start still fails the same way.

      – javazen
      Feb 10 at 1:37















    1














    just add resolutions to your package.json like this:



     
    "dependencies":
    ...

    "resolutions":
    "ajv": "6.8.1"




    then run npm install. if you use yarn, yarn install






    share|improve this answer

























    • I added this, did the npm install, but npm start still fails the same way.

      – javazen
      Feb 10 at 1:37













    1












    1








    1







    just add resolutions to your package.json like this:



     
    "dependencies":
    ...

    "resolutions":
    "ajv": "6.8.1"




    then run npm install. if you use yarn, yarn install






    share|improve this answer















    just add resolutions to your package.json like this:



     
    "dependencies":
    ...

    "resolutions":
    "ajv": "6.8.1"




    then run npm install. if you use yarn, yarn install







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Feb 10 at 13:23









    jsnewbie

    32926




    32926










    answered Feb 10 at 0:01









    nik.ssnik.ss

    113




    113












    • I added this, did the npm install, but npm start still fails the same way.

      – javazen
      Feb 10 at 1:37

















    • I added this, did the npm install, but npm start still fails the same way.

      – javazen
      Feb 10 at 1:37
















    I added this, did the npm install, but npm start still fails the same way.

    – javazen
    Feb 10 at 1:37





    I added this, did the npm install, but npm start still fails the same way.

    – javazen
    Feb 10 at 1:37











    0














    As per the suggestion in Github answers the below change has enabled me to work.



    To fix this error, just change:
    Line 14: `errors: 'full',`
    to:
    Line 14: `errors: true`
    in file **node_modulesajv-errorsindex.js**





    share|improve this answer



























      0














      As per the suggestion in Github answers the below change has enabled me to work.



      To fix this error, just change:
      Line 14: `errors: 'full',`
      to:
      Line 14: `errors: true`
      in file **node_modulesajv-errorsindex.js**





      share|improve this answer

























        0












        0








        0







        As per the suggestion in Github answers the below change has enabled me to work.



        To fix this error, just change:
        Line 14: `errors: 'full',`
        to:
        Line 14: `errors: true`
        in file **node_modulesajv-errorsindex.js**





        share|improve this answer













        As per the suggestion in Github answers the below change has enabled me to work.



        To fix this error, just change:
        Line 14: `errors: 'full',`
        to:
        Line 14: `errors: true`
        in file **node_modulesajv-errorsindex.js**






        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Feb 10 at 0:17









        VaradVarad

        495413




        495413















            protected by Community Feb 10 at 0:16



            Thank you for your interest in this question.
            Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).



            Would you like to answer one of these unanswered questions instead?


            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?