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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Offline compiler broken by --stripInternal
#8819
Comments
@alexeagle I have a fix for this pending already |
I assume your fix does not address the problem with the test? I'll do that On Wed, May 25, 2016 at 8:29 AM Igor Minar notifications@github.com wrote:
|
What makes you think this is the only @internal symbol that breaks it? On Wed, May 25, 2016 at 9:42 AM Igor Minar notifications@github.com wrote:
|
There is no other top level symbol in our codebase marked as internal +1 for adding e2e tests though. do you plan to resurrect the old typings On Wed, May 25, 2016 at 9:55 AM Alex Eagle notifications@github.com wrote:
|
I think the bug is the offline compiler integration test is using the We separately need a typings test that our NPM distro can type-check On Wed, May 25, 2016 at 10:27 AM Igor Minar notifications@github.com
|
This symbol is no longer reexported at the top level, so it's safe to not mark it as internal. This fixes the offline compilation which got broken by this symbol not being present in the d.ts files when the compiler tries to do a deep import. Closes angular#8819
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. |
0035575 turned on
--stripInternal
and now eg.
https://github.com/angular/core-builds/blob/master/esm/src/application_ref.metadata.json contains
PLATFORM_CORE_PROVIDERS
but https://github.com/angular/core-builds/blob/master/esm/src/application_ref.d.ts does not.This causes the compiler to try to locate the declaration of the symbol but fail with
Root cause is that the integration test for compiler-cli is running against the wrong
.d.ts
files.cc @IgorMinar
The text was updated successfully, but these errors were encountered: