How to fix Missing Origin Validation error for “webpack-dev-server” in npm









up vote
5
down vote

favorite
2













npm audit




 === npm audit security report ===


Manual Review
Some vulnerabilities require your attention to resolve

Visit https://go.npm.me/audit-guide for additional guidance


High Missing Origin Validation



Package webpack-dev-server



Patched in >=3.1.6



Dependency of laravel-mix [dev]



Path laravel-mix > webpack-dev-server



More info https://nodesecurity.io/advisories/725



found 1 high severity vulnerability in 11710 scanned packages
1 vulnerability requires manual review. See the full report for details.



How to fix this i cannot use laravel
whenever i try run command "npm run dev" it shows several problem










share|improve this question

























    up vote
    5
    down vote

    favorite
    2













    npm audit




     === npm audit security report ===


    Manual Review
    Some vulnerabilities require your attention to resolve

    Visit https://go.npm.me/audit-guide for additional guidance


    High Missing Origin Validation



    Package webpack-dev-server



    Patched in >=3.1.6



    Dependency of laravel-mix [dev]



    Path laravel-mix > webpack-dev-server



    More info https://nodesecurity.io/advisories/725



    found 1 high severity vulnerability in 11710 scanned packages
    1 vulnerability requires manual review. See the full report for details.



    How to fix this i cannot use laravel
    whenever i try run command "npm run dev" it shows several problem










    share|improve this question























      up vote
      5
      down vote

      favorite
      2









      up vote
      5
      down vote

      favorite
      2






      2






      npm audit




       === npm audit security report ===


      Manual Review
      Some vulnerabilities require your attention to resolve

      Visit https://go.npm.me/audit-guide for additional guidance


      High Missing Origin Validation



      Package webpack-dev-server



      Patched in >=3.1.6



      Dependency of laravel-mix [dev]



      Path laravel-mix > webpack-dev-server



      More info https://nodesecurity.io/advisories/725



      found 1 high severity vulnerability in 11710 scanned packages
      1 vulnerability requires manual review. See the full report for details.



      How to fix this i cannot use laravel
      whenever i try run command "npm run dev" it shows several problem










      share|improve this question














      npm audit




       === npm audit security report ===


      Manual Review
      Some vulnerabilities require your attention to resolve

      Visit https://go.npm.me/audit-guide for additional guidance


      High Missing Origin Validation



      Package webpack-dev-server



      Patched in >=3.1.6



      Dependency of laravel-mix [dev]



      Path laravel-mix > webpack-dev-server



      More info https://nodesecurity.io/advisories/725



      found 1 high severity vulnerability in 11710 scanned packages
      1 vulnerability requires manual review. See the full report for details.



      How to fix this i cannot use laravel
      whenever i try run command "npm run dev" it shows several problem







      laravel-5 npm laravel-5.2






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 11 at 3:29









      Subhankar Jana

      316




      316






















          3 Answers
          3






          active

          oldest

          votes

















          up vote
          3
          down vote













          This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.



          I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.



          If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.






          share|improve this answer





























            up vote
            0
            down vote













            Quick solution:



            Turning off npm audit on package installation
            https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities






            share|improve this answer
















            • 1




              A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
              – LazerBass
              Nov 14 at 15:43

















            up vote
            0
            down vote













            Maybe you must wait to update laravel-mix.
            Ref link: https://github.com/JeffreyWay/laravel-mix/issues/1809
            Because version of webpack-dev-server < 3.1.6 in laravel-mix.






            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%2f53245592%2fhow-to-fix-missing-origin-validation-error-for-webpack-dev-server-in-npm%23new-answer', 'question_page');

              );

              Post as a guest















              Required, but never shown

























              3 Answers
              3






              active

              oldest

              votes








              3 Answers
              3






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes








              up vote
              3
              down vote













              This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.



              I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.



              If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.






              share|improve this answer


























                up vote
                3
                down vote













                This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.



                I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.



                If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.






                share|improve this answer
























                  up vote
                  3
                  down vote










                  up vote
                  3
                  down vote









                  This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.



                  I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.



                  If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.






                  share|improve this answer














                  This audit is just pointing out a vulnerability in your version of the webpack-dev-server package.



                  I don't think it's related to the other problems you're encountering when you run npm run dev as I'm currently using a vulnerable version of the same package in my dev environment as well and it works fine.



                  If you're using laravel mix, it is dependent on a vulnerable version of webpack-dev-server (2.11.1) so you can't really fix this problem and will see this annoying audit message until laravel mix is updated to use a newer, secure version.







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited Nov 19 at 2:24

























                  answered Nov 11 at 20:13









                  wheelmaker

                  1,204817




                  1,204817






















                      up vote
                      0
                      down vote













                      Quick solution:



                      Turning off npm audit on package installation
                      https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities






                      share|improve this answer
















                      • 1




                        A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
                        – LazerBass
                        Nov 14 at 15:43














                      up vote
                      0
                      down vote













                      Quick solution:



                      Turning off npm audit on package installation
                      https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities






                      share|improve this answer
















                      • 1




                        A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
                        – LazerBass
                        Nov 14 at 15:43












                      up vote
                      0
                      down vote










                      up vote
                      0
                      down vote









                      Quick solution:



                      Turning off npm audit on package installation
                      https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities






                      share|improve this answer












                      Quick solution:



                      Turning off npm audit on package installation
                      https://docs.npmjs.com/auditing-package-dependencies-for-security-vulnerabilities







                      share|improve this answer












                      share|improve this answer



                      share|improve this answer










                      answered Nov 14 at 15:19









                      Julian

                      1




                      1







                      • 1




                        A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
                        – LazerBass
                        Nov 14 at 15:43












                      • 1




                        A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
                        – LazerBass
                        Nov 14 at 15:43







                      1




                      1




                      A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
                      – LazerBass
                      Nov 14 at 15:43




                      A link to a solution is welcome, but please ensure your answer is useful without it: add context around the link so your fellow users will have some idea what it is and why it’s there, then quote the most relevant part of the page you're linking to in case the target page is unavailable. Answers that are little more than a link may be deleted.
                      – LazerBass
                      Nov 14 at 15:43










                      up vote
                      0
                      down vote













                      Maybe you must wait to update laravel-mix.
                      Ref link: https://github.com/JeffreyWay/laravel-mix/issues/1809
                      Because version of webpack-dev-server < 3.1.6 in laravel-mix.






                      share|improve this answer
























                        up vote
                        0
                        down vote













                        Maybe you must wait to update laravel-mix.
                        Ref link: https://github.com/JeffreyWay/laravel-mix/issues/1809
                        Because version of webpack-dev-server < 3.1.6 in laravel-mix.






                        share|improve this answer






















                          up vote
                          0
                          down vote










                          up vote
                          0
                          down vote









                          Maybe you must wait to update laravel-mix.
                          Ref link: https://github.com/JeffreyWay/laravel-mix/issues/1809
                          Because version of webpack-dev-server < 3.1.6 in laravel-mix.






                          share|improve this answer












                          Maybe you must wait to update laravel-mix.
                          Ref link: https://github.com/JeffreyWay/laravel-mix/issues/1809
                          Because version of webpack-dev-server < 3.1.6 in laravel-mix.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 30 at 8:46









                          Triệu Viêm

                          1




                          1



























                              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.





                              Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


                              Please pay close attention to the following guidance:


                              • 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%2f53245592%2fhow-to-fix-missing-origin-validation-error-for-webpack-dev-server-in-npm%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

                              Darth Vader #20

                              How to how show current date and time by default on contact form 7 in WordPress without taking input from user in datetimepicker

                              Ondo