New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
9.0.0-rc.8 build failed #34720
Comments
@gkalpak Not the OP but I still encounter this error when I use the artifacts you mentioned. For me, the issue is as follows:
This results in the following error when trying to compile App A with Ivy:
I will try to provide a reproduction soon if I have time. |
@benelliott - did you manage to get round to creating a reproduction of this issue? |
I looked into this... the cause of the problem is that the I'll update my PR tomorrow. |
I can confirm this bug... i am getting the same error.. update: |
@petebacondarwin I hadn't yet, would that still be useful to you? |
Don't worry @benelliott - I managed to reproduce your problem locally. |
When searching the typings program for a package for imports a distinction is drawn between missing entry-points and deep imports. Previously in the `DtsDependencyHost` these deep imports may be marked as missing if there was no typings file at the deep import path. Instead there may be a javascript file instead. In practice this means the import is "deep" and not "missing". Now the `DtsDependencyHost` will also consider `.js` files when checking for deep-imports, and it will also look inside `@types/...` for a suitable deep-imported typings file. Fixes angular#34720
When searching the typings program for a package for imports a distinction is drawn between missing entry-points and deep imports. Previously in the `DtsDependencyHost` these deep imports may be marked as missing if there was no typings file at the deep import path. Instead there may be a javascript file instead. In practice this means the import is "deep" and not "missing". Now the `DtsDependencyHost` will also consider `.js` files when checking for deep-imports, and it will also look inside `@types/...` for a suitable deep-imported typings file. Fixes angular#34720
@benelliott - I have updated my PR to fix this issue. |
@petebacondarwin Thanks, is there an easy way for me to download the shippable artifacts and give it a spin? |
Sorry - both of your links give me a 404 |
Try https://circleci.com/gh/angular/angular/585697#artifacts/containers/0. |
Sorry both :-) |
When searching the typings program for a package for imports a distinction is drawn between missing entry-points and deep imports. Previously in the `DtsDependencyHost` these deep imports may be marked as missing if there was no typings file at the deep import path. Instead there may be a javascript file instead. In practice this means the import is "deep" and not "missing". Now the `DtsDependencyHost` will also consider `.js` files when checking for deep-imports, and it will also look inside `@types/...` for a suitable deep-imported typings file. Fixes angular#34720
When searching the typings program for a package for imports a distinction is drawn between missing entry-points and deep imports. Previously in the `DtsDependencyHost` these deep imports may be marked as missing if there was no typings file at the deep import path. Instead there may be a javascript file instead. In practice this means the import is "deep" and not "missing". Now the `DtsDependencyHost` will also consider `.js` files when checking for deep-imports, and it will also look inside `@types/...` for a suitable deep-imported typings file. Fixes #34720 PR Close #34695
Thanks @petebacondarwin, I just tried your artifacts and can confirm they fixed my build issues. |
I'm getting the same error as the creator of the issue, since rc.8, first with mobiscroll. So I created this issue: acidb/mobiscroll#475 So I don't know if I should create an issue @fullcalendar too, and all other librarys that eventually can get the same error, or here.
With me, this error only occurs if Ivy is enabled, or, always with ng test. |
@luthor77 - would you be able to create a minimal repository that reproduces this error and share it in a new issue here? |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
馃悶 bug report
Affected Package
@angular/compiler": "9.0.0-rc.8
Is this a regression?
Yes, the previous version(9.0.0-rc.7) in which this bug was not present was: ....
Description
Not building anymore
馃敩 Minimal Reproduction
Issues that don't have enough info and can't be reproduced will be closed.
You can read more about issue submission guidelines here: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-submitting-an-issue
-->
馃敟 Exception or Error
馃實 Your Environment
Angular Version:
Anything else relevant?
The text was updated successfully, but these errors were encountered: