cc @hansl

Note: From the look of it it's due the import types which was introduced in TypeScript 2.9. A quick fix would be to import the type rather than inferring it.

Some more context about this issue;
#11893 (comment)

Ill will also double check, if this issue is fixed in the next versions of TypeScript, As it looks to me like it might be generated by the use of yarn workspaces or bazel build.

I tried to build angular core locally with Bazel and it looks like the types are being generated correctly even with the current version of TypeScript.

example;

protected _list(path: Path): import("@angular-devkit/core/src/virtual-fs/path").PathFragment[];

Hi @hansl, will there be a 0.7.6 release with this fixed? If yes, approximately when will that be?

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}