Cannot find name ... errors when using programmatically with declarations

[felixfbecker]

c:/Users/felix/git/Projekte/registerex/node_modules/typedoc/lib/converter/types/intrinsic.d.ts(5,105): error TS2305: Module 'ts' has no exported member 'IntrinsicType'.
c:/Users/felix/git/Projekte/registerex/node_modules/typedoc/lib/converter/types/intrinsic.d.ts(6,45): error TS2305: Module 'ts' has no exported member 'IntrinsicType'.
c:/Users/felix/git/Projekte/registerex/node_modules/typedoc/lib/converter/types/intrinsic.d.ts(7,44): error TS2305: Module 'ts' has no exported member 'IntrinsicType'.
c:/Users/felix/git/Projekte/registerex/node_modules/typedoc/lib/output/events.d.ts(20,15): error TS2304: Cannot find name 'HandlebarsTemplateDelegate'.
c:/Users/felix/git/Projekte/registerex/node_modules/typedoc/lib/output/utils/resources/templates.d.ts(4,20): error TS2304: Cannot find name 'HandlebarsTemplateDelegate'.

Seems like there are some dependencies typedoc can't live without - should the declarations be published on typings/registry instead?

[joaogarin]

Having simillar issue, where you able to fix this?

[felixfbecker]

Just ignoring it for now. @blakeembrey could you comment on this?

[joaogarin]

My issue is opened in #268

Also have been ignoring it as the app runs fine, but because I am using with angular2 there is actually a big list of things I need to include, so its quite a list of warnings;P

[blakeembrey]

Most likely both are from global definitions. At least the Handlebars one is. It may be possible to switch to using Typings, or to @types when 2.0 is stable.

[felixfbecker]

@blakeembrey I tried installing the definitions with typings install npm:typedoc, but typedoc is still using tsd: https://github.com/TypeStrong/typedoc/blob/master/tsd.json. Would be nice if we could add a typings.json until @types is ready.

[blakeembrey]

I believe there's a PR for @types, finishing that up ASAP.

[christopherthielen]

These errors might go away if you

npm install --save-dev @types/handlebars

[blakeembrey]

@christopherthielen It doesn't fix the private properties we have exposed from TypeScript though, which are the first three errors.

[christopherthielen]

oh, right, now I understand. sorry for the noise!