JSX Support doesn't work anymore with gulp-eslint 5.0.0












0















I have upgraded to current gulp-eslint version 5.0.0.



When i now try to lint my code i get usual errors at the beginning of my JSX code:



127:26 error Parsing error: Unexpected token =



I assumed it's an issue with eslint by itself. So i tried to lint my code with a global installed eslint (5.9.0) and got no errors on jsx part. All other linting is identical.



My eslintrc.json's:



{
"extends": "eslint:recommended",
"parserOptions": {
"ecmaVersion": 6
},
"rules": {
},
"env": {
"node": true
}
}


And a folder downwards:



{
"extends": ["../.eslintrc.json", "plugin:react/recommended"],
"settings": {
"react": {
"pragma": "React",
"version": "15.0"
}
},
"plugins": ["react"],
"parserOptions": {
"ecmaVersion": 5,
"ecmaFeatures": {
"jsx": true
}
},
"env": {
"node": false,
"browser": true
},
"globals": {
"angular": true,
"React": true,
"ReactDOM": true,
"Uint8Array": true
},
"rules": {
"jsx-quotes": [1, "prefer-single"],
"react/prop-types": 0,
"react/no-deprecated": 0
}
}


Additional info: gulp-eslint 3.x and 4.x works fine with the same configuration.



Any tips or suggestions?










share|improve this question



























    0















    I have upgraded to current gulp-eslint version 5.0.0.



    When i now try to lint my code i get usual errors at the beginning of my JSX code:



    127:26 error Parsing error: Unexpected token =



    I assumed it's an issue with eslint by itself. So i tried to lint my code with a global installed eslint (5.9.0) and got no errors on jsx part. All other linting is identical.



    My eslintrc.json's:



    {
    "extends": "eslint:recommended",
    "parserOptions": {
    "ecmaVersion": 6
    },
    "rules": {
    },
    "env": {
    "node": true
    }
    }


    And a folder downwards:



    {
    "extends": ["../.eslintrc.json", "plugin:react/recommended"],
    "settings": {
    "react": {
    "pragma": "React",
    "version": "15.0"
    }
    },
    "plugins": ["react"],
    "parserOptions": {
    "ecmaVersion": 5,
    "ecmaFeatures": {
    "jsx": true
    }
    },
    "env": {
    "node": false,
    "browser": true
    },
    "globals": {
    "angular": true,
    "React": true,
    "ReactDOM": true,
    "Uint8Array": true
    },
    "rules": {
    "jsx-quotes": [1, "prefer-single"],
    "react/prop-types": 0,
    "react/no-deprecated": 0
    }
    }


    Additional info: gulp-eslint 3.x and 4.x works fine with the same configuration.



    Any tips or suggestions?










    share|improve this question

























      0












      0








      0








      I have upgraded to current gulp-eslint version 5.0.0.



      When i now try to lint my code i get usual errors at the beginning of my JSX code:



      127:26 error Parsing error: Unexpected token =



      I assumed it's an issue with eslint by itself. So i tried to lint my code with a global installed eslint (5.9.0) and got no errors on jsx part. All other linting is identical.



      My eslintrc.json's:



      {
      "extends": "eslint:recommended",
      "parserOptions": {
      "ecmaVersion": 6
      },
      "rules": {
      },
      "env": {
      "node": true
      }
      }


      And a folder downwards:



      {
      "extends": ["../.eslintrc.json", "plugin:react/recommended"],
      "settings": {
      "react": {
      "pragma": "React",
      "version": "15.0"
      }
      },
      "plugins": ["react"],
      "parserOptions": {
      "ecmaVersion": 5,
      "ecmaFeatures": {
      "jsx": true
      }
      },
      "env": {
      "node": false,
      "browser": true
      },
      "globals": {
      "angular": true,
      "React": true,
      "ReactDOM": true,
      "Uint8Array": true
      },
      "rules": {
      "jsx-quotes": [1, "prefer-single"],
      "react/prop-types": 0,
      "react/no-deprecated": 0
      }
      }


      Additional info: gulp-eslint 3.x and 4.x works fine with the same configuration.



      Any tips or suggestions?










      share|improve this question














      I have upgraded to current gulp-eslint version 5.0.0.



      When i now try to lint my code i get usual errors at the beginning of my JSX code:



      127:26 error Parsing error: Unexpected token =



      I assumed it's an issue with eslint by itself. So i tried to lint my code with a global installed eslint (5.9.0) and got no errors on jsx part. All other linting is identical.



      My eslintrc.json's:



      {
      "extends": "eslint:recommended",
      "parserOptions": {
      "ecmaVersion": 6
      },
      "rules": {
      },
      "env": {
      "node": true
      }
      }


      And a folder downwards:



      {
      "extends": ["../.eslintrc.json", "plugin:react/recommended"],
      "settings": {
      "react": {
      "pragma": "React",
      "version": "15.0"
      }
      },
      "plugins": ["react"],
      "parserOptions": {
      "ecmaVersion": 5,
      "ecmaFeatures": {
      "jsx": true
      }
      },
      "env": {
      "node": false,
      "browser": true
      },
      "globals": {
      "angular": true,
      "React": true,
      "ReactDOM": true,
      "Uint8Array": true
      },
      "rules": {
      "jsx-quotes": [1, "prefer-single"],
      "react/prop-types": 0,
      "react/no-deprecated": 0
      }
      }


      Additional info: gulp-eslint 3.x and 4.x works fine with the same configuration.



      Any tips or suggestions?







      node.js gulp jsx eslint gulp-eslint






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 28 '18 at 7:36









      smonkeysmonkey

      664




      664
























          1 Answer
          1






          active

          oldest

          votes


















          0














          Solved it after hours of searching! It seems there were old dependencies in the package-lock.json.



          I've deleted the package-lock.json und reinstalled all packages with npm i. Now it works as expected.






          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%2f53514367%2fjsx-support-doesnt-work-anymore-with-gulp-eslint-5-0-0%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown

























            1 Answer
            1






            active

            oldest

            votes








            1 Answer
            1






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            0














            Solved it after hours of searching! It seems there were old dependencies in the package-lock.json.



            I've deleted the package-lock.json und reinstalled all packages with npm i. Now it works as expected.






            share|improve this answer




























              0














              Solved it after hours of searching! It seems there were old dependencies in the package-lock.json.



              I've deleted the package-lock.json und reinstalled all packages with npm i. Now it works as expected.






              share|improve this answer


























                0












                0








                0







                Solved it after hours of searching! It seems there were old dependencies in the package-lock.json.



                I've deleted the package-lock.json und reinstalled all packages with npm i. Now it works as expected.






                share|improve this answer













                Solved it after hours of searching! It seems there were old dependencies in the package-lock.json.



                I've deleted the package-lock.json und reinstalled all packages with npm i. Now it works as expected.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 28 '18 at 11:05









                smonkeysmonkey

                664




                664
































                    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%2f53514367%2fjsx-support-doesnt-work-anymore-with-gulp-eslint-5-0-0%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

                    A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

                    Calculate evaluation metrics using cross_val_predict sklearn

                    Insert data from modal to MySQL (multiple modal on website)