ng packagr auto-generated path issues












0















I'm working on creating stand-alone ng-libraries to be used in a parent app. Each of these libraries have multiple model files that are being used.
But ng-packagr seems to be messing up the model file paths.



For example



import("projects/reports/src/lib/models/report.model").ReportModel


while the correct path should be the complete absolute path



export declare const selectState: import



import("../../../Users/Abhi/code/app/projects/reports/src/lib/models/report.model").ReportModel









share|improve this question



























    0















    I'm working on creating stand-alone ng-libraries to be used in a parent app. Each of these libraries have multiple model files that are being used.
    But ng-packagr seems to be messing up the model file paths.



    For example



    import("projects/reports/src/lib/models/report.model").ReportModel


    while the correct path should be the complete absolute path



    export declare const selectState: import



    import("../../../Users/Abhi/code/app/projects/reports/src/lib/models/report.model").ReportModel









    share|improve this question

























      0












      0








      0








      I'm working on creating stand-alone ng-libraries to be used in a parent app. Each of these libraries have multiple model files that are being used.
      But ng-packagr seems to be messing up the model file paths.



      For example



      import("projects/reports/src/lib/models/report.model").ReportModel


      while the correct path should be the complete absolute path



      export declare const selectState: import



      import("../../../Users/Abhi/code/app/projects/reports/src/lib/models/report.model").ReportModel









      share|improve this question














      I'm working on creating stand-alone ng-libraries to be used in a parent app. Each of these libraries have multiple model files that are being used.
      But ng-packagr seems to be messing up the model file paths.



      For example



      import("projects/reports/src/lib/models/report.model").ReportModel


      while the correct path should be the complete absolute path



      export declare const selectState: import



      import("../../../Users/Abhi/code/app/projects/reports/src/lib/models/report.model").ReportModel






      angular typescript ng-packagr






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 13 '18 at 20:10









      AbhidevAbhidev

      4,40651525




      4,40651525
























          2 Answers
          2






          active

          oldest

          votes


















          0














          One workaround for this is to inline all the models wherever they are used in the code instead of importing them as files. This is not the best solution but it works. For eg.



          export interface Report {
          fromDate: Date;
          toDate: Date;
          }

          @Component({....})
          // rest of the code





          share|improve this answer































            0














            It turns out that the issue is with Typescript v2.9.2. This get resolves after upgrading to v3+.



            But keep in mind that Typescript v3 is only supported in Angular v7+.



            Unless you don't want to upgrade to Angular v7, you can inline the models as shown in the other answer.






            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%2f53288749%2fng-packagr-auto-generated-path-issues%23new-answer', 'question_page');
              }
              );

              Post as a guest















              Required, but never shown

























              2 Answers
              2






              active

              oldest

              votes








              2 Answers
              2






              active

              oldest

              votes









              active

              oldest

              votes






              active

              oldest

              votes









              0














              One workaround for this is to inline all the models wherever they are used in the code instead of importing them as files. This is not the best solution but it works. For eg.



              export interface Report {
              fromDate: Date;
              toDate: Date;
              }

              @Component({....})
              // rest of the code





              share|improve this answer




























                0














                One workaround for this is to inline all the models wherever they are used in the code instead of importing them as files. This is not the best solution but it works. For eg.



                export interface Report {
                fromDate: Date;
                toDate: Date;
                }

                @Component({....})
                // rest of the code





                share|improve this answer


























                  0












                  0








                  0







                  One workaround for this is to inline all the models wherever they are used in the code instead of importing them as files. This is not the best solution but it works. For eg.



                  export interface Report {
                  fromDate: Date;
                  toDate: Date;
                  }

                  @Component({....})
                  // rest of the code





                  share|improve this answer













                  One workaround for this is to inline all the models wherever they are used in the code instead of importing them as files. This is not the best solution but it works. For eg.



                  export interface Report {
                  fromDate: Date;
                  toDate: Date;
                  }

                  @Component({....})
                  // rest of the code






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Nov 14 '18 at 17:37









                  AbhidevAbhidev

                  4,40651525




                  4,40651525

























                      0














                      It turns out that the issue is with Typescript v2.9.2. This get resolves after upgrading to v3+.



                      But keep in mind that Typescript v3 is only supported in Angular v7+.



                      Unless you don't want to upgrade to Angular v7, you can inline the models as shown in the other answer.






                      share|improve this answer




























                        0














                        It turns out that the issue is with Typescript v2.9.2. This get resolves after upgrading to v3+.



                        But keep in mind that Typescript v3 is only supported in Angular v7+.



                        Unless you don't want to upgrade to Angular v7, you can inline the models as shown in the other answer.






                        share|improve this answer


























                          0












                          0








                          0







                          It turns out that the issue is with Typescript v2.9.2. This get resolves after upgrading to v3+.



                          But keep in mind that Typescript v3 is only supported in Angular v7+.



                          Unless you don't want to upgrade to Angular v7, you can inline the models as shown in the other answer.






                          share|improve this answer













                          It turns out that the issue is with Typescript v2.9.2. This get resolves after upgrading to v3+.



                          But keep in mind that Typescript v3 is only supported in Angular v7+.



                          Unless you don't want to upgrade to Angular v7, you can inline the models as shown in the other answer.







                          share|improve this answer












                          share|improve this answer



                          share|improve this answer










                          answered Nov 19 '18 at 18:11









                          AbhidevAbhidev

                          4,40651525




                          4,40651525






























                              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%2f53288749%2fng-packagr-auto-generated-path-issues%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

                              Xamarin.iOS Cant Deploy on Iphone

                              Glorious Revolution

                              Dulmage-Mendelsohn matrix decomposition in Python