The babel configuration of next.js for the latest browsers












1















The default configuration of Next.js is compatible for IE11. Now we are only writing web app for the latest browsers (the latest version of Edge, Safari, Chrome and Firefox). So we expect babel to do as few things as possible. How can I write the ".babelrc" then?










share|improve this question



























    1















    The default configuration of Next.js is compatible for IE11. Now we are only writing web app for the latest browsers (the latest version of Edge, Safari, Chrome and Firefox). So we expect babel to do as few things as possible. How can I write the ".babelrc" then?










    share|improve this question

























      1












      1








      1








      The default configuration of Next.js is compatible for IE11. Now we are only writing web app for the latest browsers (the latest version of Edge, Safari, Chrome and Firefox). So we expect babel to do as few things as possible. How can I write the ".babelrc" then?










      share|improve this question














      The default configuration of Next.js is compatible for IE11. Now we are only writing web app for the latest browsers (the latest version of Edge, Safari, Chrome and Firefox). So we expect babel to do as few things as possible. How can I write the ".babelrc" then?







      node.js babel next.js






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 27 '18 at 4:47









      Jim JinJim Jin

      558




      558
























          1 Answer
          1






          active

          oldest

          votes


















          1














          I don't think it worth excluding IE11 support since the only polyfill is a global Promise object that makes nextJS work on IE11.



          However you can add a custom .babelrc to your project. See the documentation here: https://nextjs.org/docs/#customizing-babel-config



          and specify the supported browsers using the preset-env plugin: https://babeljs.io/docs/en/babel-preset-env#browserslist-integration



          .babelrc



          "presets": [
          ["next/babel", {
          "preset-env": {
          "useBuiltIns": "entry" //tells the preset to look for browserslist config source
          },
          ]
          ]


          package.json



          "browserslist": "> 0.25%, not dead"






          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%2f53492923%2fthe-babel-configuration-of-next-js-for-the-latest-browsers%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









            1














            I don't think it worth excluding IE11 support since the only polyfill is a global Promise object that makes nextJS work on IE11.



            However you can add a custom .babelrc to your project. See the documentation here: https://nextjs.org/docs/#customizing-babel-config



            and specify the supported browsers using the preset-env plugin: https://babeljs.io/docs/en/babel-preset-env#browserslist-integration



            .babelrc



            "presets": [
            ["next/babel", {
            "preset-env": {
            "useBuiltIns": "entry" //tells the preset to look for browserslist config source
            },
            ]
            ]


            package.json



            "browserslist": "> 0.25%, not dead"






            share|improve this answer




























              1














              I don't think it worth excluding IE11 support since the only polyfill is a global Promise object that makes nextJS work on IE11.



              However you can add a custom .babelrc to your project. See the documentation here: https://nextjs.org/docs/#customizing-babel-config



              and specify the supported browsers using the preset-env plugin: https://babeljs.io/docs/en/babel-preset-env#browserslist-integration



              .babelrc



              "presets": [
              ["next/babel", {
              "preset-env": {
              "useBuiltIns": "entry" //tells the preset to look for browserslist config source
              },
              ]
              ]


              package.json



              "browserslist": "> 0.25%, not dead"






              share|improve this answer


























                1












                1








                1







                I don't think it worth excluding IE11 support since the only polyfill is a global Promise object that makes nextJS work on IE11.



                However you can add a custom .babelrc to your project. See the documentation here: https://nextjs.org/docs/#customizing-babel-config



                and specify the supported browsers using the preset-env plugin: https://babeljs.io/docs/en/babel-preset-env#browserslist-integration



                .babelrc



                "presets": [
                ["next/babel", {
                "preset-env": {
                "useBuiltIns": "entry" //tells the preset to look for browserslist config source
                },
                ]
                ]


                package.json



                "browserslist": "> 0.25%, not dead"






                share|improve this answer













                I don't think it worth excluding IE11 support since the only polyfill is a global Promise object that makes nextJS work on IE11.



                However you can add a custom .babelrc to your project. See the documentation here: https://nextjs.org/docs/#customizing-babel-config



                and specify the supported browsers using the preset-env plugin: https://babeljs.io/docs/en/babel-preset-env#browserslist-integration



                .babelrc



                "presets": [
                ["next/babel", {
                "preset-env": {
                "useBuiltIns": "entry" //tells the preset to look for browserslist config source
                },
                ]
                ]


                package.json



                "browserslist": "> 0.25%, not dead"







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 28 '18 at 15:04









                LaszloLaszlo

                1,2091120




                1,2091120
































                    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%2f53492923%2fthe-babel-configuration-of-next-js-for-the-latest-browsers%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

                    Lallio

                    Unable to find Lightning Node

                    Futebolista