Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

incorrect paths for import statement is generated

See original GitHub issue

Type of Issue

[x] Bug Report
[ ] Feature Request

Description

incorrect paths for import statement can be generated when a project has multiple library workspaces.

I think the following issue is similar to this issue. https://github.com/ng-packagr/ng-packagr/issues/1109

How To Reproduce

I created a repository for reproduce this bug.

git clone https://github.com/musou1500/test-angular-workspace
ng build lib2 && ng build lib1
open dist/lib1/lib/lib1.service.d.ts. then you can see an incorrect path for import on Lib1Service.test method.

    // should be ../../../dist/lib2/lib2
    test(): import("../../../../dist/lib2/lib2").Entity;

Expected Behaviour

the correct path for import statements should be generated.

Version Information

$ node_modules/.bin/ng-packagr --version
ng-packagr:            5.5.1
@angular/compiler:     8.2.7
rollup:                1.21.4
tsickle:               0.36.0
typescript:            3.5.3

Issue Analytics

State:
Created 4 years ago
Reactions:4
Comments:8

Top GitHub Comments

5reactions

damienwebdevcommented, Oct 22, 2019

See this as well for builds of https://github.com/graycoreio/daffodil. I was able to work around it by directly referencing the type in the child library. This appears to only happen for inferred types.

4reactions

plchampignycommented, Oct 12, 2019

We had a similar issue yesterday. Was using a sibling library in a library using it’s alias name “@somename/some-library” and imports were being transformed to relative paths. This was causing usage issues.