Type Declaration Files Not Found When Out of Sub-Project Directory

[sam-s4s]

🐞 Bug report

Command (mark with an x)

- [ ] new
- [ X ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?

Not that I know of

Description

When specifying a custom d.ts file anywhere other than within a project sub-directory, the declaration isn't found.

🔬 Minimal Reproduction

ng new
npm install uuid
create file "./typings/uuid.d.ts" (in the workspace root)

declare module "uuid" {
    export function v4(): string;
    export default v4;
}

then in a sub project inside the workspace...
app.component.ts -> import { v4 } from 'uuid';

🔥 Exception or Error

error TS2688: Cannot find type definition file for 'uuid'.
./app.component.ts:2:20 - error TS7016: Could not find a declaration file for module 'uuid'.

🌍 Your Environment

Angular CLI: 8.3.2
Node: 10.15.1
OS: win32 x64
Angular: 8.2.4
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.803.2
@angular-devkit/build-angular     0.803.2
@angular-devkit/build-optimizer   0.803.2
@angular-devkit/build-webpack     0.803.2
@angular-devkit/core              8.3.2
@angular-devkit/schematics        8.3.2
@angular/cli                      8.3.2
@ngtools/webpack                  8.3.2
@schematics/angular               8.3.2
@schematics/update                0.803.2
rxjs                              6.5.2
typescript                        3.5.3
webpack                           4.39.2

Anything else relevant?

Interestingly enough, even though this error shows up in the build process, the runtime code actually works correctly! It's just the compiler that thinks there's an error.

I have 4-5 projects inside my workspace, and I want this type declaration file to be above them all, so it can be shared between them. How is this intended to work?

I've tried specifying types and typeRoots in my tsconfig to no avail.

Note that intellisense in VS2017 works fine for my uuid.d.ts file no matter where I put it.

[alan-agius4]

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.

If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.

That being said, you should use @types and not create your own when there are typings available.
https://www.npmjs.com/package/@types/uuid

[sam-s4s]

@alan-agius4 thanks for the reply. I have just created a StackOverflow as per your instructions. If it is just a configuration issue then hopefully I'll get an answer there. However I may have to come back here if it does turn out to be impossible, as then it is a bug. (for example, my scenario works perfectly in normal Typescript land, without Angular, and also my IDE and the actual runtime code all are functioning correctly, it's just the compiler error that's the problem, which leads me to believe that it's a cli bug)

I agree about the @types thing, however in this case the uuid types declaration is broken (forces @types/node globals into the ecosystem, which breaks things like setTimeout, etc.) so I had to create my own un-broken version :(

[sam-s4s]

Hmm, no-one has replied to my Stack Overflow :(
https://stackoverflow.com/questions/58071305/shared-type-declaration-file-in-workspace

But still, I feel like this is a shortcoming on the cli end - no-one seems to know if this is possible, and I can't find any documentation relating to it anywhere.

[angular-automatic-lock-bot]

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.}