electron/muon: require not defined in renderer












0














I'm currently working on an IPFS/Ethereum dapp in Muon.
Because i need Metamask i started with this Boilerplate: https://github.com/SwapyNetwork/electron-metamask-boilerplate



Everything is working fine so far.
However i can not use require('anything') in the renderer process or in html script tags. (See below)



There seems to be a problem with the boilerplate code but i can't find it.
Or is node code in renderer not supported in Muon?



My only change in testing is setting node-integration explicitly to true and
inserting require('fs') in index.js. (i installed fs of course).



I tried many different solutions from stackoverflow and other sites but couldn't find a solution yet.



Error Message



Thank you










share|improve this question



























    0














    I'm currently working on an IPFS/Ethereum dapp in Muon.
    Because i need Metamask i started with this Boilerplate: https://github.com/SwapyNetwork/electron-metamask-boilerplate



    Everything is working fine so far.
    However i can not use require('anything') in the renderer process or in html script tags. (See below)



    There seems to be a problem with the boilerplate code but i can't find it.
    Or is node code in renderer not supported in Muon?



    My only change in testing is setting node-integration explicitly to true and
    inserting require('fs') in index.js. (i installed fs of course).



    I tried many different solutions from stackoverflow and other sites but couldn't find a solution yet.



    Error Message



    Thank you










    share|improve this question

























      0












      0








      0







      I'm currently working on an IPFS/Ethereum dapp in Muon.
      Because i need Metamask i started with this Boilerplate: https://github.com/SwapyNetwork/electron-metamask-boilerplate



      Everything is working fine so far.
      However i can not use require('anything') in the renderer process or in html script tags. (See below)



      There seems to be a problem with the boilerplate code but i can't find it.
      Or is node code in renderer not supported in Muon?



      My only change in testing is setting node-integration explicitly to true and
      inserting require('fs') in index.js. (i installed fs of course).



      I tried many different solutions from stackoverflow and other sites but couldn't find a solution yet.



      Error Message



      Thank you










      share|improve this question













      I'm currently working on an IPFS/Ethereum dapp in Muon.
      Because i need Metamask i started with this Boilerplate: https://github.com/SwapyNetwork/electron-metamask-boilerplate



      Everything is working fine so far.
      However i can not use require('anything') in the renderer process or in html script tags. (See below)



      There seems to be a problem with the boilerplate code but i can't find it.
      Or is node code in renderer not supported in Muon?



      My only change in testing is setting node-integration explicitly to true and
      inserting require('fs') in index.js. (i installed fs of course).



      I tried many different solutions from stackoverflow and other sites but couldn't find a solution yet.



      Error Message



      Thank you







      node.js electron muon






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 20 at 21:32









      Sauseee

      64




      64
























          1 Answer
          1






          active

          oldest

          votes


















          0














          As per the muon's github repo:




          Some of Muons goals include:




          1. Use the Chromium source directly (eliminating electron's copy of chrome_src) with minor patches


            • make integrating chrome components less painful

            • faster and more streamlined end-to-end build process (see browser-laptop-bootstrap).



          2. add support for Chrome extensions

          3. add security focused features for the renderer:


            • remove node completely (from the renderer process)

            • full sandbox

            • scriptable window.opener support








          As you can see there, muon does not supports node code in the rendered. It is by design for security purpose. Muon may be great for certain applications, but I recommend switching on to electron if you really need to use require in the renderer.






          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%2f53401881%2felectron-muon-require-not-defined-in-renderer%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














            As per the muon's github repo:




            Some of Muons goals include:




            1. Use the Chromium source directly (eliminating electron's copy of chrome_src) with minor patches


              • make integrating chrome components less painful

              • faster and more streamlined end-to-end build process (see browser-laptop-bootstrap).



            2. add support for Chrome extensions

            3. add security focused features for the renderer:


              • remove node completely (from the renderer process)

              • full sandbox

              • scriptable window.opener support








            As you can see there, muon does not supports node code in the rendered. It is by design for security purpose. Muon may be great for certain applications, but I recommend switching on to electron if you really need to use require in the renderer.






            share|improve this answer


























              0














              As per the muon's github repo:




              Some of Muons goals include:




              1. Use the Chromium source directly (eliminating electron's copy of chrome_src) with minor patches


                • make integrating chrome components less painful

                • faster and more streamlined end-to-end build process (see browser-laptop-bootstrap).



              2. add support for Chrome extensions

              3. add security focused features for the renderer:


                • remove node completely (from the renderer process)

                • full sandbox

                • scriptable window.opener support








              As you can see there, muon does not supports node code in the rendered. It is by design for security purpose. Muon may be great for certain applications, but I recommend switching on to electron if you really need to use require in the renderer.






              share|improve this answer
























                0












                0








                0






                As per the muon's github repo:




                Some of Muons goals include:




                1. Use the Chromium source directly (eliminating electron's copy of chrome_src) with minor patches


                  • make integrating chrome components less painful

                  • faster and more streamlined end-to-end build process (see browser-laptop-bootstrap).



                2. add support for Chrome extensions

                3. add security focused features for the renderer:


                  • remove node completely (from the renderer process)

                  • full sandbox

                  • scriptable window.opener support








                As you can see there, muon does not supports node code in the rendered. It is by design for security purpose. Muon may be great for certain applications, but I recommend switching on to electron if you really need to use require in the renderer.






                share|improve this answer












                As per the muon's github repo:




                Some of Muons goals include:




                1. Use the Chromium source directly (eliminating electron's copy of chrome_src) with minor patches


                  • make integrating chrome components less painful

                  • faster and more streamlined end-to-end build process (see browser-laptop-bootstrap).



                2. add support for Chrome extensions

                3. add security focused features for the renderer:


                  • remove node completely (from the renderer process)

                  • full sandbox

                  • scriptable window.opener support








                As you can see there, muon does not supports node code in the rendered. It is by design for security purpose. Muon may be great for certain applications, but I recommend switching on to electron if you really need to use require in the renderer.







                share|improve this answer












                share|improve this answer



                share|improve this answer










                answered Nov 21 at 3:42









                Nishkal Kashyap

                23719




                23719






























                    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%2f53401881%2felectron-muon-require-not-defined-in-renderer%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

                    404 Error Contact Form 7 ajax form submitting

                    How to know if a Active Directory user can login interactively

                    TypeError: fit_transform() missing 1 required positional argument: 'X'