@angular-devkit/core v0.7.5 published with broken typescript declarations

[vladimiry]

Bug Report or Feature Request (mark with an x)

- [x] bug report -> please search issues before submitting
- [ ] feature request

Versions

node v8.9.4
yarn v1.9.4
typescript v3.0.1

Repro steps

Just run the build that uses @angular-devkit/core in any way.

The log given by the failure

Error output:

ERROR in node_modules/@angular-devkit/core/src/virtual-fs/host/test.d.ts(36,41): error TS2307: Cannot find module '../../../../../../../../../../../Users/hansl/Sources/hansl/angular-cli/packages/angular_devkit/core/src/virtual-fs/path'.
node_modules/@angular-devkit/core/src/virtual-fs/host/test.d.ts(44,33): error TS2307: Cannot find module '../../../../../../../../../../../Users/hansl/Sources/hansl/angular-cli/packages/angular_devkit/core/src/virtual-fs/path'.

Desired functionality

Declarations were not broken with previous v0.7.4 version.

Mention any other details that might be useful

Here is the workaround, tsconfig.json:

{
  "compilerOptions": {
    "skipLibCheck": true
  },
}

[vladimiry]

cc @hansl

[alan-agius4]

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.

[alan-agius4]

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[];