Expose webpacked dependency for peer dependency












0















I'm working on two different JS packages that have the following dependency layout:




  • Library A


    • Library C (third-party)



  • Library B


    • Library A

    • Library C (as a peer dependency, i.e. use whatever A uses)




I currently build a webpack bundle for A that also includes C. So far so good. Now, I also want to build a bundle for B, but one that declares A and C as externals. This is also possible, but as far as I can see, there is currently no way of having the bundle from A expose its bundled version of C to B.



Are there any existing solutions here? I control the bundling config and entry point for both A and B, but also need to compile/bundle the libraries with different configs, so the underlying code should avoid any special casing.










share|improve this question



























    0















    I'm working on two different JS packages that have the following dependency layout:




    • Library A


      • Library C (third-party)



    • Library B


      • Library A

      • Library C (as a peer dependency, i.e. use whatever A uses)




    I currently build a webpack bundle for A that also includes C. So far so good. Now, I also want to build a bundle for B, but one that declares A and C as externals. This is also possible, but as far as I can see, there is currently no way of having the bundle from A expose its bundled version of C to B.



    Are there any existing solutions here? I control the bundling config and entry point for both A and B, but also need to compile/bundle the libraries with different configs, so the underlying code should avoid any special casing.










    share|improve this question

























      0












      0








      0








      I'm working on two different JS packages that have the following dependency layout:




      • Library A


        • Library C (third-party)



      • Library B


        • Library A

        • Library C (as a peer dependency, i.e. use whatever A uses)




      I currently build a webpack bundle for A that also includes C. So far so good. Now, I also want to build a bundle for B, but one that declares A and C as externals. This is also possible, but as far as I can see, there is currently no way of having the bundle from A expose its bundled version of C to B.



      Are there any existing solutions here? I control the bundling config and entry point for both A and B, but also need to compile/bundle the libraries with different configs, so the underlying code should avoid any special casing.










      share|improve this question














      I'm working on two different JS packages that have the following dependency layout:




      • Library A


        • Library C (third-party)



      • Library B


        • Library A

        • Library C (as a peer dependency, i.e. use whatever A uses)




      I currently build a webpack bundle for A that also includes C. So far so good. Now, I also want to build a bundle for B, but one that declares A and C as externals. This is also possible, but as far as I can see, there is currently no way of having the bundle from A expose its bundled version of C to B.



      Are there any existing solutions here? I control the bundling config and entry point for both A and B, but also need to compile/bundle the libraries with different configs, so the underlying code should avoid any special casing.







      webpack webpack-4






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 20 '18 at 15:11









      VidarVidar

      723511




      723511
























          0






          active

          oldest

          votes











          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%2f53395996%2fexpose-webpacked-dependency-for-peer-dependency%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          0






          active

          oldest

          votes








          0






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          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%2f53395996%2fexpose-webpacked-dependency-for-peer-dependency%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

          android studio warns about leanback feature tag usage required on manifest while using Unity exported app?

          SQL update select statement

          WPF add header to Image with URL pettitions [duplicate]